Sorry didnt mean to start a flame war :)
Just that I think we will have to have a complete suite of software to
be a credible alternative to current offerings - I am trying to add my
little bit of input to the process as I cant do much coding (as yet?)
If you look at the classical "waterfall" software design process it is
broadly
Planning -> analysis ->design -> implementation -> maintenance
We are probably using a more "agile" methodology which will go into a
Design -> implement -> test -> design cycle after a short initial
planning/analysis process.
Among other things planning includes feasibility (technical/financial etc)
It seems like we have decided the process is technically feasible due to
the advances in OSS and in particular the advantages of RoR and a web
framework over conventional architecture. We have sort of glossed over
the financial/sustainability issues - she'll be right.
Horst probably has as good an idea as anyone on these and he seems
convinced.
Analysis consists of gathering requirements for the process depending on
current workflow.
I sat behind our receptionist as she did a billing - there are probably
several(many?) other processes that need to be captured. I suspect the
requirements for a private account would be much the same, except that
instead of generating a M/C voucher, a receipt or account would be
generated, depending on whether the patient paid at the time
(perhaps the dialog should include a button to another dialog to allow
receipting?)
Are there any other data that need to be captured in this process?
R
ash wrote:
Ian Haywood wrote:
Ok, so private-billing is good. Fine. Now would one of you
silvertails mind describing how the process actually works? What does
the patient sign? when? I take it you don't print the invoice
yourselves in your office, how do you communicate to the
receptionist what items to put on the invoice?
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
