Imaging and laboratory requirements
Radiology, imaging, PACS/RIS and DICOM
Ordering to reporting for imaging; on-site image store.
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
C0756Does AuroraMed provide RIS worklists, protocoling and reading queues?
No. The specification describes it, but the pilot does not include it. For reference, REQ-1201 (a high-priority requirement, the medium and large tiers) says the system must provide RIS worklists, protocoling and reading queues. Check: radiologist queue shows priority and age.
C0757Does AuroraMed provide DICOM Modality Worklist and MPPS for modalities?
The system must provide DICOM Modality Worklist and MPPS for modalities. That is REQ-1202, 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: modality receives worklist by AE title.
C0758Does AuroraMed receive DICOM C-STORE, support C-FIND/C-MOVE/C-GET and Storage Commitment over TLS with AE allow-lists?
Designed, not built: there is no code for this in the pilot. REQ-1203 says the system must receive DICOM C-STORE, support C-FIND/C-MOVE/C-GET and Storage Commitment over TLS with AE allow-lists. Its acceptance check: unknown AE title refused; storage commit returns for stored UIDs.
C0759Does AuroraMed implement DICOMweb QIDO-RS, WADO-RS, STOW-RS and UPS-RS?
REQ-1204 is a high-priority requirement for the medium and large tiers: the system must implement DICOMweb QIDO-RS, WADO-RS, STOW-RS and UPS-RS. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says zero-footprint viewer loads a study via WADO-RS.
C0760Does AuroraMed store DICOM SR, RDSR, GSPS and KOS objects and render them?
The radiology, imaging, pacs/ris and dicom part of the specification (REQ-1205) says the system must store DICOM SR, RDSR, GSPS and KOS objects and render them. No. The specification describes it, but the pilot does not include it. Acceptance check: rDSR ingested to dose registry.
C0761Does AuroraMed reconcile patient identity between modality and ADT (IHE PIR) before filing?
How would it be tested? The specification says mismatched study lands in a reconciliation queue. That is the check for REQ-1206: the system must reconcile patient identity between modality and ADT (IHE PIR) before filing. Not yet. It is designed in the specification and not built in the pilot.
C0762Does AuroraMed provide a zero-footprint enterprise viewer inside the terminal live feed?
Designed, not built: there is no code for this in the pilot. For reference, REQ-1207 (a high-priority requirement, the medium and large tiers) says the system must provide a zero-footprint enterprise viewer inside the terminal live feed. Check: viewer renders on server; terminal receives frames only.
C0763Does AuroraMed integrate VNA/PACS and image exchange (CD import, cloud share) with quarantine and AV scanning?
The system must integrate VNA/PACS and image exchange (CD import, cloud share) with quarantine and AV scanning. That is REQ-1208, a medium-priority requirement for the medium and large tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: imported study quarantined until scan passes.
C0764Does AuroraMed support structured reporting (RSNA RadReport, BI-RADS and other -RADS systems) and follow-up recommendation tracking?
No. The specification describes it, but the pilot does not include it. REQ-1209 says the system must support structured reporting (RSNA RadReport, BI-RADS and other -RADS systems) and follow-up recommendation tracking. Its acceptance check: incidental finding recommendations create trackable tasks.
C0765Does AuroraMed record radiation dose and provide dose alerts?
REQ-1210 is a high-priority requirement for the medium and large tiers: the system must record radiation dose and provide dose alerts. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says threshold exceedance alerts.
C0766Does AuroraMed support mammography tracking and MQSA reporting?
The radiology, imaging, pacs/ris and dicom part of the specification (REQ-1211) says the system must support mammography tracking and MQSA reporting. Designed, not built: there is no code for this in the pilot. Acceptance check: lay letter timing tracked.
C0767Does AuroraMed communicate critical imaging results with closed-loop acknowledgment?
How would it be tested? The specification says unacknowledged beyond threshold escalates. That is the check for REQ-1212: the system must communicate critical imaging results with closed-loop acknowledgment. This is on the design side of the line. Nothing in v0.2.0 does it.
C0768Does AuroraMed support teleradiology and AI image triage as clearly labeled decision support?
No. The specification describes it, but the pilot does not include it. For reference, REQ-1213 (a lower-priority requirement, the large tier only) says the system must support teleradiology and AI image triage as clearly labeled decision support. Check: aI output labeled and does not alter the report.
C0769Does AuroraMed support contrast, pregnancy and renal screening at imaging scheduling?
The system must support contrast, pregnancy and renal screening at imaging scheduling. That is REQ-1214, a high-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: screen result stored with order.