Every figure below is produced by the running system, not written by hand. The live records come from the Epic, Oracle Health and MEDITECH public FHIR sandboxes. The synthetic patients come from Synthea, an open MITRE project. Nothing here is a mock-up, and the parts that do not work say so.
CDS Hooks is a published HL7 standard. Epic supports it and lists medication ordering decision support among its own integration playbooks. Oracle Health and MEDITECH are both named contributors to Da Vinci Coverage Requirements Discovery, which is built on CDS Hooks. A service is an HTTPS endpoint, so building one requires nobody's permission, and the same engine answers any EHR that speaks it. AI MedAgent Reasoning runs inside this endpoint, after the deterministic screen and before the cards are written, and it is handed the coverage statement so that it knows which of the eight classes did not run.
The socket is drawn empty on purpose. That is the honest state of the system today, and it is the shape of what a drug data partner would fill.
order-select fires, at the moment before signing.Neither of these is a screenshot, and neither is the product. CDS Hooks specifies the card and says nothing about its appearance, so the EHR draws it however it draws it. Both frames above are rendering the identical response. What a decision support company actually ships is the object below.
Press Begin above, or call the endpoint, to fill this.
Same engine, four sources, and it cannot tell which one it is reading. Epic proves a connection and then refuses two resources whose scopes it granted, the problem list and the allergy list. Oracle Health serves both to a request carrying no credentials at all. MEDITECH serves them too, along with everything else Epic answers with 403, but only behind an interactive browser login. Synthea supplies depth no sandbox has.
| Vendor | What it costs to get in | Status | What we found |
|---|
system/Condition.read sits in the granted token. The answer came from the error text on a different endpoint: "Combination of parameters is not valid for any authorized sub-resource." Epic authorizes below the OAuth scope, at sub-resource level. Their documentation does not say so. It was found by measurement.
You cannot reason over a record you have not validated. So the integrity screen runs first and its findings are printed above the clinical section, not in a footnote.
A system that calculates perfectly and understands nothing averages these into a trend line and hands a clinician a number.
Cole Corwin's problem list. Renal dosing is decided by stage.
Not a quirk of synthetic data. Wang and Wright measured duplication in 28.3 percent of diabetes problem lists across 383,404 entries and 327,695 patients. JAMIA 2020;27(8):1190–1197.
| Analyte | LOINC | Outside possible | Observed | Possible |
|---|
These are impossibility bounds, deliberately wide, not reference ranges. Nothing here says a value is abnormal. It says a value is not a measurement of the thing its code claims. Two of these bounds were wrong on the first attempt and were corrected; the table is published as data so it can be argued with.
Every decision support product ever built goes silent when it finds nothing, and clinicians have learned to read that silence as checked, fine. It is not. It is checked whatever I happen to check, which you have never been told.
So this engine counts its own coverage, on every single run, against a taxonomy it did not invent: the eight published module names of Wolters Kluwer's Medi-Span clinical screening APIs. Measured against a vendor's own list, so anyone can check it.
Cole is 81. His most recent eGFR is . medications are active, and one of them is metformin.
The FDA label for metformin hydrochloride lists severe renal impairment, eGFR below 30 mL/min/1.73m², under CONTRAINDICATIONS.
AI MedAgent reports the eGFR. It reports the active orders. It states in writing that it cannot determine which of them are affected, because Drug Disease Contraindications has no source behind it. It finds nothing, claims nothing, and is exactly one module away from finding it.
That single line is hand-verified from the published FDA label for this demonstration. It was not returned by any drug knowledge base, and the engine does not pretend otherwise.
An alert that fires on everything is noise within a week. A card that says 1 of 8, and here are the seven I could not do is a status line, and it is the difference between trusting a tool and learning to click past it.
Coverage is reported as info, never warning. Promoting it to a warning would make it exactly the alert fatigue it exists to prevent.
CDS Hooks and SMART on FHIR. No agent on a server, no interface engine change, no database. The service stores nothing and reasons only over what the hook sends it.
Reads the same US Core resources your certified EHR already exposes. If it can fire a hook, it can call this.
One interface, one call shape, already written down. The classes it cannot perform are named in your taxonomy and counted in every output that leaves the system.
The free federal source for one of them is gone: NLM discontinued the RxNav drug interaction API on 2 January 2024 and named no replacement.
It declines to answer when the prefetch is incomplete rather than returning an empty result that reads as a clean screen. Absent allergy data produces NOT PERFORMED, never zero findings.
Four distinct states of "no allergies" are modelled, because a search returning nothing cannot distinguish a patient with none from a patient nobody asked.
| Claim | How to check it in under a minute |
|---|---|
| The endpoint is real and conformant | aimedagent.net/cds-services returns a CDS Hooks discovery document |
| It runs in somebody else's tool | Point sandbox.cds-hooks.org at https://aimedagent.net |
| The eight classes are not invented | Wolters Kluwer publishes the module list on their own site |
| Problem list duplication is common | Wang & Wright, JAMIA 2020;27(8):1190–1197, doi:10.1093/jamia/ocaa125 |
| Metformin is contraindicated below eGFR 30 | FDA prescribing information, CONTRAINDICATIONS |
| The free interaction API is gone | NLM RxNav notice, discontinued on or about 2 January 2024 |
| The synthetic patients are reproducible | MITRE Synthea public sample set, named patient identifiers |
DEMONSTRATION ONLY. NOT A MEDICAL DEVICE. NOT FOR CLINICAL USE. The CDS Hooks endpoint is unauthenticated and must not be connected to a production EHR. It stores nothing and logs no patient data.
Live records are drawn from Epic's public FHIR sandbox, which contains no real patient. Synthetic records are generated by Synthea, an open MITRE project, from population statistics; they describe no real person.
AI MedAgent · patent pending · aimedagent.net ·