Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Highest
-
US Core (FHIR)
-
4.0.0
-
Cross-Group Projects
-
US Core DiagnosticReport Profile for Report and Note Exchange
-
Profile specific implementation guidance
-
-
Isaac Vetter / Floyd Eisenberg : 13-0-0
-
Correction
-
Compatible, substantive
Description
Please clarify the "must support" note regarding DocumentReference.imagingStudy and DocumentReference.media
"• the server system is not required to support both, but SHALL support at least one of these elements. • The client application SHALL support both elements and target resources."
It would make more sense for the server system to support both, and depending on ancillary workflow and client capabilities, require the client to support one.
For example, a VNA in radiology (as a client) is likely to POST ImagingStudy, whereas a non-DICOM point of care imaging device is likely to POST media.
Attachments
Issue Links
- is voted on by
-
BALLOT-31756 Negative - Steven Nichols : 2022-Jan-FHIR US CORE R4.1 STU
- Closed
-
BALLOT-31759 Negative - Christopher Lindop : 2022-Jan-FHIR US CORE R4.1 STU
- Closed
- relates to
-
FHIR-34975 Imaging Study or Media is still unclear
- Published
-
FHIR-35759 Remove MS from DiagnosticReport.imagingStudy
- Published
-
FHIR-34975 Imaging Study or Media is still unclear
- Published
-
FHIR-35759 Remove MS from DiagnosticReport.imagingStudy
- Published