Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.1.0-ballot [deprecated]
-
Infrastructure & Messaging
-
STU
-
DiagnosticsReport open event [deprecated]
-
-
Catie Ladd / Nick Radov : 6-0-1
-
Clarification
-
Non-substantive
-
Yes
Description
When a DiagnosticReport-open event is received by an application, the application should respond as is appropriate for its clinical use. For example, an image reading application may respond to a DiagnosticReport-open event posted by a reporting application by opening any imaging study(ies) specified in the context. A reporting application may want to respond to a DiagnosticReport-open event posted by an image reading application by creating a new or opening an existing report.
An application that listens to DiagnosticReport events is mandated to follow the requirements of this spec. Repeating this is confusing.
A diagnosticreport-open event can never trigger a new report as it refers to an existing one.
Attachments
Issue Links
- is voted on by
-
BALLOT-35239 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35802 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35873 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36015 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36111 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36182 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36469 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35944 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted