I think the problem is that registration is not a task normally
performed by those primarily involved in direct patient care. Maybe a
new user interface could be developed, but in spite of its name, CPRS
wasn't designed to be "all things to do with patient care", it was
designed to be a module for use by clinicians. It's a bit of a
simplification to call it a "viewer", because there are a lot of
things (like order entry) that you can do, that would hardly be
called "viewing".
This is just my opinion, but I think we're allowing ourselves to be
too limited by what is already available in VistA. If there is a need
for something new, build it!
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Design quality doesn't ensure success, but design failure can ensure
failure."
--Kent Beck
On Oct 2, 2005, at 10:39 PM, Kin Ho wrote:
That is disappointing, and I don't mean it in a negative way.
Apparently CPRS is such a fine product with extensive functionalities
in setting personal preference, entering orders, vitals and
medications, etc.
That is beyond retrieve only.
Compare with the available functions, it will be a relative small
task technically
to add an option to enter a new patient (of course, check against
existing to
avoid duplications). It is only reasonable to have data entry/edit/
retrieve all in
one place. Now it become a show stopper for me because I don't know
the old way of patient registration yet.
Wonder what is the designing philosophy keeping patient
registration away
from CPRS GUI?
Back to evaluate CPRS, how do I start patient registration in the
r&s way?
For example, <<<D Reg^FMPtEnt>>>
Thanks and regards
Kin
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
