Results management and diagnostic reporting

C0666Does AuroraMed provide a results inbox with acknowledgment and sign-off tracking?

The pilot covers part of this. The rest is designed, not built. Pilot detail: Basic MVP equivalent: patient banner/summary, vitals/note/I&O entries, stay/day/hour timeline, care assignment, results view; free-text, not coded or templated. For reference, REQ-0601 (a top-priority requirement, all three tiers) says the system must provide a results inbox with acknowledgment and sign-off tracking. Check: abnormal results require acknowledgment.

C0667Does AuroraMed record critical-value notification with read-back and callback documentation?

The system must record critical-value notification with read-back and callback documentation. That is REQ-0602, a top-priority requirement for all three tiers. The pilot covers part of this. The rest is designed, not built. Where the code stands: Basic MVP equivalent: patient banner/summary, vitals/note/I&O entries, stay/day/hour timeline, care assignment, results view; free-text, not coded or templated. Test in the specification: critical result unacknowledged beyond threshold escalates (file 06).

C0668Does AuroraMed route results to ordering, PCP and covering providers with rules?

Designed, not built: there is no code for this in the pilot. REQ-0603 says the system must route results to ordering, PCP and covering providers with rules. Its acceptance check: routing simulation available.

C0669Does AuroraMed track pending results at discharge and assign owners?

REQ-0604 is a top-priority requirement for the medium and large tiers: the system must track pending results at discharge and assign owners. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says owner named for each pending result.

C0670Does AuroraMed release results to the patient per Cures Act rules with configurable delay for sensitive types?

The results management and diagnostic reporting part of the specification (REQ-0605) says the system must release results to the patient per Cures Act rules with configurable delay for sensitive types. No. The specification describes it, but the pilot does not include it. Acceptance check: sensitive result delay policy is applied and logged.

C0671Does AuroraMed provide trending/graphing, reference ranges by age/sex and delta checks?

How would it be tested? The specification says graph values equal stored values. That is the check for REQ-0606: the system must provide trending/graphing, reference ranges by age/sex and delta checks. Not yet. It is designed in the specification and not built in the pilot.

C0672Does AuroraMed incorporate outside lab results discretely with LOINC mapping?

Designed, not built: there is no code for this in the pilot. For reference, REQ-0607 (a top-priority requirement, all three tiers) says the system must incorporate outside lab results discretely with LOINC mapping. Check: unmapped tests flagged.

C0673Does AuroraMed link reports to images (DiagnosticReport to ImagingStudy)?

The system must link reports to images (DiagnosticReport to ImagingStudy). That is REQ-0608, a top-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: link opens viewer.

C0674Does AuroraMed support pathology synoptic reporting and genomic/molecular results?

No. The specification describes it, but the pilot does not include it. REQ-0609 says the system must support pathology synoptic reporting and genomic/molecular results. Its acceptance check: required synoptic elements enforced.

C0675Does AuroraMed ingest point-of-care results with operator and QC checks?

REQ-0610 is a high-priority requirement for all three tiers: the system must ingest point-of-care results with operator and QC checks. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says result from device with failed QC is rejected.