Re: [Health] Linking work flows with Services and their payments

[Luis Falcon]

Dear Khurram

El Fri, 30 Sep 2016 18:56:08 +0500
> Thanks for the response. Your idea is good and we should go with
> it ...
> 
> But, I think we should go with following design
> Step 1: Service Request
> Step 2: Payment

Yes, step 2 is implied, since it what makes the state of the invoice to
change to "paid".

> Step 3: Start the service process
> 
> If we want to give some discount or waive the payment off that can
> also be adjusted in the work flow.
> 
> Most of the functionality is already developed. For example:
> 1. A doctor requests a laboratory test.
> 2. The service invoice is automatically generated for this request and
> linked to the service request.
> 3. The patient is sent to Cash Counter where the clerk opens the
> invoice and takes payment.
> 4. After payment the request is auto updated to status "Paid" or there
> should be user interface from where user can attach the paid invoice
> to the request and after auto-validation, the request is update to
> status "Paid". 5. Once it is in "Paid" status, then it can be further
> processed.
> 
> Now, it does not matter whether it is an Appointment or Lab Test or
> Radiology Test etc. Only the "payment status" flag should be used to
> allow further action on them.
> 
True. The appointment creation process, although is usually present, is
not needed. The service can be created and the registration officer can
generate the invoice with the selected service lines.

> Similarly, for hospitalized patients, we should first request
> "Admission Service" which requires some "Advance" payment from
> patient in order to get the admission process run. And when the
> patient gets admitted and invoice should automatically be created and
> all the services availed by patient should automatically appended to
> this invoice. These services may be the Bed, Surgical Procedure,
> Doctor's consultancy services, medicines, medical supplies, food
> and/or nursing services. This invoice should also show the advance
> deposited by the patient and current bill.

The current design should be flexible enough to include pre or
post-payment.

> 
> By the way, keeping 2nd October in view, I must write some more
> requirements:
> i. We do not have any work flow for "Walk In" patients. Should we
> first create "Appointment" for them?

In most cases, yes. 

Some emergency cases do not use appointment.

> ii. Normally, at the time of appointment, the patient registration is
> not done as it is not possible to take this much information or often
> patients do not show up. So, while saving appointment, there should
> be a field just to input patient name. And once patient arrives, then
> he/she should be registered.

That's why I stress the concept of "People before Patients". There is a
lot of things we can do at person and community level, before (and to
avoid) them being patients.

In the case they become patients, then all the demographics are already
in the system, so no need to input it at registration time. Actually,
they should have the ID card with the QR code, so things become even
faster and avoid the human error at registration time.

> 
> Sorry for mixing things. Any ideas/critical reviews for improvements
> are highly welcomed.

Thank you for your feedback. It's always welcomed !


Have a great weekend
Luis


-- 
Dr. Luis Falcon, M.D., BSc
President, GNU Solidario
GNU Health: Freedom and Equity in Healthcare
http://health.gnu.org