DiagnosticReport Profile¶
| Canonical | https://fhir.apps.health/StructureDefinition/nexus-emr-core-diagnosticreport |
|---|---|
| Status | draft · 1.33.0 |
| Base | DiagnosticReport (constraint) |
| Source | FSH · JSON |
Defines the Nexus EMR FHIR profile for DiagnosticReport resources, based on CA-Core constraints, for aggregating diagnostic reports (e.g., Lab, Imaging) from multiple EMRs. Today Nexus EMR writes every report received over HRM, of any class, and every laboratory feed with coded results here; documents uploaded or scanned are a DocumentReference. Which resource a received report should become is not yet settled, so a reader should expect a received report on either. See Incoming reports.
Examples
Conforming instances (each opens inside this tab):
- Abdominal Ultrasound Report — Imaging report carrying its acquisition modality in the nexus-imaging-modality extension. This guide models the imaging report rather than the DICOM study, so modality lives on th…
- Anemia Diagnostic Report — Example diagnostic report for anemia workup from April 8, 2025
- Avery INR (warfarin monitoring) — Therapeutic INR on routine warfarin monitoring. The conclusion is the passage the AI-generated pre-visit summary quotes verbatim, so the citation can be checked against the report…
- Potassium Report (awaiting a patient match) — A laboratory report whose demographics matched no chart -- subject-less, carrying the awaiting-patient tag under nexus-filing-state, as does its result. Matching it sets the subje…