Dear Sumit Sharma;
If you cannot do the development at or near the point of care, then you
will never got out of the problem I outlined. What you are doing is
purpetrating a system that has failed to work more times than I can count.
The people at the point of care need to be involved. The Programmers
need to see their code in operation and see where the nurses curse the
code and listen to the suggestions the doctors and nurses make. They are
the subject matter experts you need to build a meaningful system.
If you are building from rough specifications and interpreting the
business rules without having the healthcare providers involved, then
you will be making policy for the hospital without actually knowing the
business rules that these folks have to live by. The "take it or else"
approach is nearly criminal. You must find a way to get the
developers/programmers into the nurses stations and accompanying the
doctors and nurses on rounds where they need to use the systems you are
writting. The sooner that your people can clear up the rough spots, the
more satisfaction the healthcare providers will find acceptance of what
you do. The healthcare providers need to have that impact on the code
development or they will not identify with the solution and they will
subconsciously sabotage the application.
Actually, I would start looking at the M-Gateway web tools that are in
open source and start migrating away from CPRS. Keeping CPRS clients
and servers coordinated is a royal nightmare in a large facility with
lots of clients. The web interface is really the way to go, but it
will be a while for us to get the project done. The clients in the
case of the web access are thin clients and only need to be a web
browser with sufficient memory.
Best wishes; Chris Richardson
Many of the developers are doing the work in their own time and out of
their own pockets and on their own vacation time.