Dependencies: core

Here, the Gnumed Forms Storage definition is a great start - that definition is one of the best I've seen around. Even solutions of big players in the EMR sector are not even close to this one. Often, old versions of forms (yes, they exist in practice) are not accessible any more, because they get overwritten with newer versions.

You can find the original here.

• forms must be formally defined
• form revisions may not overwrite each other when upgrading
• form sets (eg by country) may not conflict with each other
• any form entered into the system must be reproducible at any time
• form definitions are never removed, only put out of use
• the ways of using a filled-in form may not be limited
• the way of using a filled-in form may not be fixed

The forms module should provide a central API for creating forms, e.g.

• prepscriptions
• confirmations, attestations
• reports to the health office (reporting of infectuous diseases, vaccination damages, etc.)
• disability to work
• death notice

Form fields:

• UID
• Description (e.g. referral xray)
• group (general, referrals)
• printer (where to print out) - uh-oh: maybe don't define this here?
  • paper tray
  • paper format (A4, A5, prescription, etc)
  • orientation (portrait, landscape)
  • confirmation dialog to print? (bool) (wait for paper input)
  • resolution (dpi)
  • preview? (bool)
  • pause after each page? (bool)

• Draft
• Specification
• API