AI MedAgent reads EHR records over FHIR R4, the API federal certification requires every certified EHR to offer, and answers with CDS Hooks cards, the HL7 standard for putting advice where the clinician is working. The newest piece is live on Oracle Health's developer servers.
AI MedAgent is registered in Oracle's developer program, signs in through Oracle, reads Oracle's FHIR servers, and takes device data from OpenBedside in the cloud. The pump is simulated and the patients are synthetic; the rest is real.
See what is realThe live app inside a labeled illustration of an EHR screen, on a workstation on wheels or a nurse's phone. Change patient searches Oracle's sandbox.
Open it
What AI MedAgent read from the Epic, Oracle Health and MEDITECH developer sandboxes, and which safety checks it said in writing that it could not perform.
Read the evidenceHow it connects over FHIR R4 and CDS Hooks, what each vendor sandbox returns, and what it refuses. Measured, not asserted.
Read the datasheetThe CDS Hooks service, the eight medication screening classes, and the coverage figure reported on every invocation.
Read the datasheetThe service description any CDS Hooks client reads, straight from the running endpoint.
Open the endpointDaniel Pettus spent forty years in medical device and health IT leadership at Alaris, CareFusion and BD, contributed to IHE Patient Care Device interoperability standards, and is named on two United States patents. He writes Inside the Loop at insidetheloopdp.substack.com and is the author of The Technology Was Never the Problem, at pettusbook.com.
AI MedAgent is a research demonstration of a patent-pending method. Advisory only. Not a medical device. Not for clinical use. Synthetic data only.