- Ya
- 27 Agosti 2026, 06:39 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 79089bb
Prescribing was added with the allergy table, the interaction-checking query and a "safety context" endpoint all sitting beside it, unread. A system that records an allergy and then writes the prescription anyway without mentioning it is worse than one that never recorded the allergy, because the practice believes it is being checked. Three checks the practice's own data can answer exactly: the drug matches a recorded allergy, the patient is already on it, or nobody has ever asked about allergies at all. That last one is its own warning — an empty list means "no known allergies" or "nobody asked", and only one of them is safe to prescribe against. A positively recorded "no known allergies" row is not treated as a substance. Warnings with a required acknowledgement, not refusals. A clinician may deliberately prescribe a drug a patient reacted mildly to years ago, and a system that forbids it is one people route around. What must not happen is prescribing in IGNORANCE, so the write is refused until the prescriber has seen the warning and says in writing why they are proceeding. That reason is logged at WARN with the member, the drug and the patient, because a later review is what it is for. 409 rather than 400: nothing is malformed. It is a valid prescription that conflicts with what is recorded, and the identical request succeeds once a reason is attached. The warnings travel in the body — a refusal that only said "unsafe" would send somebody hunting through the chart for what a computer already knew. Matching drops strengths and filler words. "Amoxicillin 500mg" and "Amoxicillin" are the same drug so a differing strength cannot hide an allergy; "tablet", "oral" and "solution" appear in half of all drug names and matching on them would flag every prescription against every allergy, which is the fastest way to make people stop reading warnings. DELIBERATELY NOT drug-drug interaction checking. That needs a licensed database (First Databank, Medi-Span) this platform does not have, and a home-grown approximation is the most dangerous thing the file could contain: it would look like interaction checking, be trusted as it, and miss most interactions. The class says so in as many words. 15 tests.