UI Designs (Dropbox Link)
The billing module is designed to be replacement and improvement for the existing billing module in use at JSS.
These are questions we don't know answers to... need input from JSS, others to answer them. Once answered, should update this document with the answer and track it here.
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?
Discuss views, controllers, models, stores you'll need. How will you build these in the ExtJS app?
Discuss REST resources you'll need to call on the back-end.
Per an initial discussion, the database model may include the following tables. This needs more investigation before being confirmed. Please research existing billing tools and how they model financial transactions, bills, partial payments, discounts, etc.
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)
Backend Resources go into RaxaCore - https://github.com/Raxa/raxacore
Front-end Resources go into Raxa-JSS - https://github.com/Raxa/Raxa-JSS