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

[Khurram Shahzad]

On Fri, Sep 30, 2016 at 4:21 PM, Luis Falcon <address@hidden> wrote:

Dear Khurram

El Fri, 30 Sep 2016 12:55:44 +0500
Khurram Shahzad <address@hidden> escribió:
> Dear All,
>
> During implementation of GNU Health at our hospital, we have defined
> various OPD Services like:
>
> Consultancy Service
> Lab Test Services
> Radiology Test Services
>
> Patient arrives at front desk, gets registered and chooses some
> service. Then, he is sent to Cash Counter where he pays for the
> service and then the work flow for that service runs.
>
> What we want is that "The work flow runs only when the payment has
> been received". For example, a doctor can create new evaluation for a
> patient ONLY IF the patient has already paid the charges of the
> "Consultancy Service".
>
> How can I link the work flow "Create New Evaluation" with "Consultancy
> Service" payment by a specific patient? In other words, we want tight
> integration of "Services" with "Payments" through our software.
>
> Can it be done using available modules in GNU Health? If not, can
> anybody suggest me any other Tryton module which suits in this
> scenario?
>

It seems like a common scenario in different contexts.

What we have done in some implementations is the following :

* The registration officer / clerk registers the patient and creates
  the appointment and the service

* The patient enters the doctor office

* The doctor selects the - already created - service associated to this
  visit. The services are ordered by payment status and date. So, the
  first service shown would normally be the one to pick.

We also have implemented similar things for prescription orders, to let
the pharmacist know whether the prescription item/line has been paid.

If there is consensus, we can include this functionality in the
upcoming release. But hurry, since October 2nd we enter Feature Freeze
to get ready for 3.2 ! :)

All the best,

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

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.

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. 

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? 

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.

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

--

 

Regards,

Khurram.