Standing Watch · room 1 of 5 · ICU

The ICU watch board: every finding carries its own follow-through.

Five synthetic patients, one unit. When AI MedAgent finds something, it does not just say it. It sends it to a named role, sets how urgent it is and says why, reminds if nobody answers, escalates to the next person, and writes down every step. That object is the mediator. Watch it work, then answer as the nurse, the pharmacist or the doctor would.

How to use this page

The clock is simulated. One second here is one minute on the unit, so a ten-minute reminder takes ten seconds. Speed it up, pause it, or reset.
Click a finding to see who it went to, why it is urgent, what the watch read, and the exact FHIR resources it is carried in. Then respond, defer or reject it, or do nothing and watch it escalate.
Click a bed, then ask the live reasoning. The four findings that appear on their own were written for this demonstration. The button sends that bed's synthetic chart to the live AI MedAgent reasoning on this site, and whatever it finds is wrapped in a mediator the same way.

Synthetic patients and a simulated pump feed. Nothing is stored on a server; reset the page and it is gone. Not a medical device. Not for clinical use.

Beds

Open watch items, most urgent first

The watch is reading. Findings appear here as the clock runs.

Closed items

Click a finding or a bed to see the detail.

Unit audit trail

Every step of every mediator, in order. Each line is an AuditEvent in the detail view.

How the mediator maps to published standards

Nothing here is a private format. The finding, the work and the trail are standard HL7 FHIR R4 resources; device-originated alerts have a published IHE path of their own.

Mediator step	FHIR R4 (what this page emits)	IHE ACM, for device-originated alerts
The finding	DetectedIssue: code, severity, detail, evidence	Report Alert [PCD-04]
Who should hear it, and how urgent	Task.owner (a PractitionerRole), Task.priority, CommunicationRequest.recipient and payload	Disseminate Alert [PCD-06]
Reminder and escalation timers	Task.restriction.period.end; the chain and minutes in Task.input	Set by the alert manager; delivery status returns in Report Dissemination Alert Status [PCD-07]
Respond, defer, reject	Task.status: completed, on-hold, rejected; Task.statusReason; Task.note	The recipient's answer returns in [PCD-07]; the alert's status goes back to the reporting device in Report Alert Status [PCD-05]
The trail	AuditEvent, one per step	Logged by the alert manager and communicator

Sources: HL7 FHIR R4 (4.0.1) resource definitions for DetectedIssue, Task, CommunicationRequest and AuditEvent. IHE Devices Technical Framework Rev 10.0, Final Text, 4 November 2024, Alert Communication Management (ACM), transactions PCD-04 to PCD-07. The timers shown are demonstration settings; a hospital sets its own. The project's own code system (https://aimedagent.net/fhir/CodeSystem/watch-event) names the audit steps, because no published code fits "escalated after no answer".

Daniel 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.