Imaging Modality Extension¶
| Canonical | ../StructureDefinition/nexus-imaging-modality |
|---|---|
| Status | draft · 1.26.0 |
| Base | Extension (constraint) |
| Context | DiagnosticReport (element) |
| Source | FSH · JSON |
The acquisition modality this imaging report came from -- DX, US, CT, MR, MG.
Overview
On the report, not on a study. R4 puts modality on ImagingStudy, which this guide does not
profile: the estate models the imaging REPORT and holds no DICOM acquisition metadata. Saying a
report came from a CT asserts nothing about series, instances or SOP UIDs.
Not derivable from DiagnosticReport.code in practice. The study code names the study, and a
human reader can infer modality from it; a results list filtering "CT reports" cannot, without
maintaining a procedure-to-modality mapping outside the record and getting it wrong silently.
Bound extensible to DICOM CID 29 -- the same value set and strength R4 binds
ImagingStudy.modality to, so a consumer that knows R4's imaging model needs no second rule.
Heritage feeds carrying local modality codes stay conformant.
Repeats: a PET-CT report says two.
Terminology bindings
| Path | Strength | Value set |
|---|---|---|
Extension.value[x] |
extensible | sect_CID_29.html |