Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Frontend Module (esm): 

Backend Module (Java): https://github.com/openmrs/openmrs-module-cashier

esm: https://github.com/METS-Programme/esm-ugandaemr-stock-management
backend: https://github.com/METS-Programme/openmrs-module-ugandaemr-commodity

User Stories

Actors

Patient, Registration Clerk/Clerk, Consultant/Clinician, Lab Tech, Pharmacist, Hospital supervisor, Cashier, Administrator.

...

  • Role-based access. Not everyone using the billing function should be able to see everything.
  • The system should be able to always capture the service offered as a billable item. e.g. consultation, drugs, lab test etc.
  • There should be a billable menu of items that a cashier can use to bill a client.
  • The RefApp should be able to process payments done by cash, mobile money, card
  • The RefApp should also be able to process non-paying clients e.g. prisoners or those whose payment has been waived by the hospital administration. or whatever protocol has been set by the hospital. The function to waive payment is configurable and be allocated to whoever the facility prefers.
  • The system should display the mode of payment used by the patient i.e. Mobile money, Card, Cash, and non-paying clients.
  • There should be mobile money integration.
  • It should also be able to display a c
  • The teller should be able to reconcile the payments they received from the system: The display should show: the service offered, amount paid, processing officer, date, time, and the service station
  • The RefApp should be able to display a list of bills, based on payment status (paid/unpaid), new bills

Technical approach I: creating an openmrs module.

Creating an openmrs frontend/backend billing module: Adopt Kenya-EMR (Palladium) Billing Module

Generic Features to configure:

  1. Add configurations for the different payment points ie. those paying per service point/ those paying at the end of the visit.
  2. Conduct event driven creation of bills (orders create bills, lab orders, test orders, some encounters)
  3. Add ability to configure procedures and minor surgeries as part of the billable items.
  4. On the frontend, create a widget on the patient chart that shows all the patient’s current bills Add the ability to create a new bill while providing service.

Technical approach II: using 3rd party ERPs

Use case I: ERPNext/ Odoo

  • Features:

Inventory management (stock ledger, balance reports and inventory documentation)

All in one healthcare software(lab management, in-department operations, billing, prescriptions, reminders, pharmacy, accounting, asset management, payroll/ HR management, system configuration).

There will be data exchange between the EMR and the ERP depending on functionality/modules that an implementation prefers to use.