2012-08-23 Billing Module Meeting

Participants: John V Stoecker (Unlicensed), Nathan Leiby (Unlicensed), Surajit Nundy, Abhishek Gupta, Jatin Thapar

This document is notes from our meeting. After cleaning up, it should form the start of module documentation, too, to be placed on the Wiki.

Billing module

Team Member(s):

Mentor(s):

UI Designs:
https://www.dropbox.com/s/k76uw8rgdbsell8/billing.pdf

Database Design:

Billing
status - pending, paid, partially paid, approved
patient
provider - whoever does the billing, e.g. clerk
has many: items

BillingItem
concept (concept - drug, labTest, etc)
quantity
how much it costs (value)
link to what made it - link to order ID or Encounter
provider
has many: item adjustments

BillingItemAdjustment
BillingItem
Reason
Value

Price
-concept
-quantity
-value

(Might need more columns for any item)

Please research existing billing tools and how they model:

Schedule
Week 1: research existing OpenMRS BillingModules, other FOSS billing projects
Week 2: backend
Week 3: views
Week 4-6: connecting through REST
Week 7-11: Integrate into OPD, pharm, lab, IPD
Week 12-14: IPD/OT/Lab resources
Week 15: Finalize CSS, look

(front-load is better..
research)

throughout:
commit write tests

*blog your experiences?
*

Need to be aware of when bills were issued and when bills were paid
-Insurance RSBY
-partial payments in visit 1, follow up payment in visit 2

1 or more default prices for each item

some things covered by RSBY, some not
-medication not covered by RSBY
-"toe cut off" is covered

Can we integrate into RSBY or other payment systems (NFC)?

Approval (before bill can be issued to the patient)
-> might have "auto approve default prices"
-> might have "auto approve discounted prices"
-> might "only allow prices to be "
vs
Auditing (after the payment and everything has occured)
->
->

logging for later auditing
history of all price changes with name / date associated?

Open Issues:
(questions we don't know answers too... need input from JSS, others to answer them)

Repositories:
Backend Resources go into "RaxaCore"
Front-end Resources go into "Raxa-JSS"

TIMELINE:
Fri Aug 24: [Nathan] Complete short spec/designs on billing -- add to Wiki
Sat Aug 25 - Sun 26: Review existing billing modules in OpenMRS and lots of other billing systems... consider lots of possible alternatives
Mon Aug 27 - Tues 28: improve architecture plans (database tables needed), review UI to see if we have screens yet to meet JSS's needs
Wed Aug 29: Call with JSS - review our designs