Patient Processes #628
mosesmbadi
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is the updated description of the patient processes.
There are 4 'things' done to a patient when they visit the hospital:
These are represented by the models in brackets above.

The model AttendanceProcess keeps track of all those processes.
This means if we want to retrieve all Triage information about a patient and couple it with any prescriptions, we can use the AttendanceProcess to get all the info.
Let's look at that in detail. When we create a New Visit, we send a POST to /api/patient/attendance-process with the payload below:
Below is what we get as a response.
Next we assign the patient to a doctor (Creating an appointment). That we send a POST request to: /api/patient/attendance-process?process_id=6. Below is the payload we use:
Notice we've captured the AttendanceProcess ID above. And we get the response below:
In addition to that POST we also send a POST to create an invoice, carryng the invoice id and item id (General Appointment). We then send a GET request and get the response below, which is updated with the Invoice details
Now we're not going to go through the entire patient process but the above gives you a gist of what happens.
It's important to note that a patient has to be billed before proceeding to the next process. For example, when we 'send a petient to a doctor', the doctor will not see the appointment first, until that process has been billed. In order to accommodate different patient needs and urgency, billing can be done without the patient having to pay, provided whoever bills notes that down (we still haven't implemented this on invoice).
Beta Was this translation helpful? Give feedback.
All reactions