- Shipped
- August 26, 2026 at 9:47 PM UTC
- Author
- kamo
- Commit
- d258750
The chart could show all three and create none. One panel rather than three, because they are one moment: a clinician finishing a visit writes the prescription, sends the lab and records the shot in the same thirty seconds, and three screens in three places is how the third gets forgotten — usually the vaccination, which is the one the registry and the recall query need. Each tab appears only if the member's role includes it. A button that is present and refuses teaches people the system is unreliable; a button that is absent teaches them who to ask. The server enforces all three regardless. The controlled-substance switch is stated, never guessed from the drug name. A lookup would be wrong in both directions — demanding the stronger permission for a misread name, or failing to demand it for one it did not recognise — so the prescriber asserts it and the server enforces the second right on what was asserted. The switch is disabled outright for somebody without that right, with a line saying to ask an administrator rather than a refusal after typing. Writing sits above reading on the tab: a clinician arrives here to record what they just decided, and a compose box below a long problem list is one nobody scrolls to. It is keyed on the patient so a half-typed prescription cannot follow somebody from one chart to the next, and a write bumps a token that makes the list below re-read — a list one prescription out of date reads as "it didn't save". Also: a missing RIGHT no longer reports as "not enabled for clinical data". Both arrive as 403 and mean opposite things — one is fixed by an administrator in minutes, the other is a contract — so the client now reads the reason the server sends and carries its sentence, which already names the permission.