FreeAccount Database schema draft

• FreeAccount is a medical specific accountancy manager helper.
• It is actually only available as an ALPHA RELEASE
• It should manage medical accountancy for all countries.
• FreeAccount was firstly developed by Eric Maeker, MD (2007-2008), then transformed by Pierre-Marie Desombre, MD (2008-2012). In Dec 2012, Pierre-Marie left us with an incomplete code. Christian A. Reiter and I decided to work together on the code refactoring and feature stabilization.

• FreeAccount is actually developed without any funds.
• We need help for developing this application and to detail the calculations.

We need:

• Definitions of country specific accounting schematas
• “medical procedures” data from insurances - what medical procedures are paid? We need a reliable source of electronic updateable data.

• Generally speaking, the users mentioned in the text here are FMF users, notably doctors, nurses, or receptionists, not patients.
• Quotation 1..n {[Fees (1..n? medical procedure) ] n..1 Payments } n..1 Banking 1..1 BankAcount
• Or
• X Fees (medical procedure) → X Payments → X Banking → 1 BankAcount per banking

• User may create & maintain multiple bank accounts
• User can choose the bank account to edit (for payments, bankings, amounts…)

• User may record 'fees' which point to 'medical procedures'
• One patient can have one or multiple 'fees' for one consultation / surgery from multiple users…
• one 'fee' is linked to only:
  • one user
  • one patient
  • one date of realisation

• 'fees' are different to 'payments'
  • one payment is a group of one or more 'fees' from
    • one or more users
    • one or more patients
  • one payment can cover a part of a fee (eg: paid 60% of the fees with VISA and 40% with money)

• When a user 'banks' money, he pushes it to a bank account
• User creates a banking out of a goup of payments
• One banking may contain multiple payments

• quotations are regroupments of fees:
  • for one unique patient
  • for one or multiple users (eg: surgeon, anesthetist, nurse, hospital…)
• one quotation can lead to one or multiple payments

There are many different dates in accountancy that can be in a many-to-many relation with other accounting objects. Each date object has its own type.

• Date of 'quotation'
• Date of 'medical realisation'
• Date of 'invocing'
• Date of 'payment'
• Date of 'banking'
• Date of 'accountancy'
• Date of 'creation'
• Date of 'update'
• Date of 'validation'
• Date of 'annulation'
• Date of 'validityPeriodStart'
• Date of 'validityPeriodEnd'
• …

Things to check:

• Should dates be editable? (maybe with a flag)
• dates could have additional fields like “description”, etc
• Each object owns its specific date set

• Should not be hard coded
• Suggested to create separate tables for payment type
  • VISA
  • Cheque
  • Cash
  • Bank Transfer
  • Others (please detail ideas)
• Some payments are country specific?
• Should be editable?

• Make it ULTRA simple
• prepare for categorization
• Prepare for datapacks (datapacks can contains country specific MP)

• A specific formItem must be created, it must allow user
  • to add fees to a patient inside an episode (eg at the end of SOAP)
  • to add payments
    • eg: user add 1 fee and 1 payment in one click
    • eg: user add 1 fee to 1 patient, then 1 fee to another and then 1 payment for the two unpaid fees