The clinician decides
The software formats and remembers. It does not diagnose, recommend or calculate. That boundary is not a limitation to be relaxed later.
About
A prescription is a small document that has to be exactly right. The product is built around that.
Why this exists
Most clinicians still write prescriptions by hand, and the ones who have moved to software often use a form that prints — no memory of what they prescribe, no reuse, no real speed gain. The interesting problem is not rendering a document. It is removing the fiftieth retyping of the same regimen.
So the medicine library is the centre of the product, not a settings page. Everything else exists to make that loop fast.
Principles
A record stays a record
Finalized prescriptions are immutable and enforced as such by the database, so history cannot be quietly rewritten.
Patient data stays where it belongs
Not in analytics, not in logs, not in URLs, not visible to our own support staff.
Say what is not built
The security page lists what is missing. The status of the build is published. Overstating readiness is how people get hurt in healthcare software.