Okay!
So, let's just pretend that I live in a country that's just
crying for a half-way decent Practice Management System for
GPs, or any sort of system of Nursing Homes, or a slightly
better than half-way decent system for hospitals... ;-)
There are a few ways to try and introduce a solution to
their problems. Here's two:
I can take a package and show them that "if they would just
try to understand that if they changed the way they worked
so that it matched the way my package worked" all their
problems would disappear into the ether...
Or. I can take the approach that says, "here's a package
that *you* can adapt to fit *your* needs but you'll need to
learn to program..." But once you've created a "prototype",
we'll refine and polish it so that it's robust and stays in
the open source community...
Right now, neither approach is going to work. :-(
Clients/customers are wary, no leary, of "packages that
solve all problems" and have little or no inclination to
learn something that is not going to contribute to reducing
their already overburdened day...
Can we come up with some approaches to "market" this?
Cheers,
Stephen
Chris Richardson wrote:
Steve;
Thisis how VistA got started. It has been slowly pulled away from the
end users and handed to 3rd party developers. Wouldn't it be nice to
re-empower the end user again? What a concept...
----- Original Message -----
From: "Stephen Hay" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Monday, January 16, 2006 9:43 PM
Subject: Re: [Hardhats-members] New Developers, MUMPS language syntax,
etal....
I'd like to pick up on this bit...
Chris Richardson wrote:
Right now, this is a tool which allows the end user to direct the
application development or we can play telegraph where they try to drescribe
the needed application, and then REAL Porgrammers go off and interpret those
requirements and force them to use an application that kind of looks like
the described application in 6 months or a year later. This is the common
model of development and it has been very disappointing to the end users.
Better the user define their need in code that can be changed quickly to
adapt to the current need, then let the REAL Programmers put in the
efficiency later, but let the end user get their job done in the mean time.
Has anyone any suggestions on how this could be used as a "selling
point" for introducing VistA?
Intuitively, it makes sense to put the "prototyping" in the hands of the
users. Give them something that will get their job done for them, then
tidy it up afterwards using all the tricks of the trade, so to speak...
Thanks,
Stephen
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
