Clinical care requirements
Inpatient, critical care, surgery and anesthesia
Hospital medicine, ICU, periop.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0727Does AuroraMed support admission H&P, hospital course auto-summary and discharge summary workflows?
No. The specification describes it, but the pilot does not include it. REQ-1101 says the system must support admission H&P, hospital course auto-summary and discharge summary workflows. Its acceptance check: discharge summary pulls meds, problems, pending results.
C0728Does AuroraMed support critical care flowsheets, ICU scores and bundles?
REQ-1102 is a high-priority requirement for the large tier only: the system must support critical care flowsheets, ICU scores and bundles. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says score inputs come from charted data.
C0729Does AuroraMed integrate telemetry/ECG alarm management?
The inpatient, critical care, surgery and anesthesia part of the specification (REQ-1103) says the system must integrate telemetry/ECG alarm management. Designed, not built: there is no code for this in the pilot. Acceptance check: alarm events logged.
C0730Does AuroraMed support ECMO, CRRT and dialysis documentation?
How would it be tested? The specification says session record exists. That is the check for REQ-1104: the system must support ECMO, CRRT and dialysis documentation. This is on the design side of the line. Nothing in v0.2.0 does it.
C0731Does AuroraMed support transplant and palliative documentation?
No. The specification describes it, but the pilot does not include it. For reference, REQ-1105 (a lower-priority requirement, the large tier only) says the system must support transplant and palliative documentation. Check: workflows exist for listing.
C0732Does AuroraMed support surgical case booking, preference cards, counts, time-outs and intraoperative records?
The system must support surgical case booking, preference cards, counts, time-outs and intraoperative records. That is REQ-1106, a top-priority requirement for the medium and large tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: count discrepancy escalates.
C0733Does AuroraMed track implants with UDI?
Designed, not built: there is no code for this in the pilot. REQ-1107 says the system must track implants with UDI. Its acceptance check: uDI parsed and stored.
C0734Does AuroraMed support operative notes with synoptic templates and anesthesia records with device integration?
REQ-1108 is a high-priority requirement for the medium and large tiers: the system must support operative notes with synoptic templates and anesthesia records with device integration. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says record time series preserved.
C0735Does AuroraMed support PACU documentation with recovery scores?
The inpatient, critical care, surgery and anesthesia part of the specification (REQ-1109) says the system must support PACU documentation with recovery scores. No. The specification describes it, but the pilot does not include it. Acceptance check: score stored.
C0736Does AuroraMed support OR scheduling optimization and block utilization analytics?
How would it be tested? The specification says utilization report available. That is the check for REQ-1110: the system must support OR scheduling optimization and block utilization analytics. Not yet. It is designed in the specification and not built in the pilot.
C0737Does AuroraMed support sterile processing instrument tracking integration?
Designed, not built: there is no code for this in the pilot. For reference, REQ-1111 (a lower-priority requirement, the large tier only) says the system must support sterile processing instrument tracking integration. Check: instrument set traceable.