Details
-
Question
-
Resolution: Considered - Question answered
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
DiagnosticsReport open event [deprecated]
-
3.6.1
-
Description
Is the DiagnosticReport-open event too tailored to Radiology reporting? Are there other specialties that might want other content beyond an imagingstudy? Why is the context key "study" rather than following the "imagingstudy" pattern?
Also section 4.6.1 ("a Hub could validate that the content in a DiagnosticReport anchor context always includes at least one primary imaging study" precludes use of DiagnosticReport for non-imaging uses), section 4.6.3.2 ("These changes usually include adding/removing imaging studies"), and more.
Do we need "profiles" of events for particular uses?
(Comment 32 - imported by: Lloyd McKenzie)
Attachments
Issue Links
- is voted on by
-
BALLOT-37138 Affirmative - Elliot Silver : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted