Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
Withdrawn
-
DiagnosticsReport open event [deprecated]
-
-
Catie Ladd / Nick Radov : 6-0-1
-
Clarification
-
Non-substantive
-
Yes
Description
If a Hub supports content sharing, when it distributes a DiagnosticReport-open event the Hub associates a context.versionId with the anchor context. Subscribed applications MUST submit this context.versionId in subsequent DiagnosticReport-update requests. If a client will neither make a DiagnosticReport-update request or respond to DiagnosticReport-update events, the versionId can be safely ignored.
The mandatory elements should be made part of the content sharing chapter.
Does an application participates in the network, wants to receive diagnostic-open and close events but does not participate in the context sharing have to follow this requirement? If so, this should not be the case as it breaks the generic event pattern.
ps. Is it versionId or timestamp?
Attachments
Issue Links
- is voted on by
-
BALLOT-35770 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35841 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35983 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36079 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36150 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36437 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35912 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35272 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Retracted
- relates to
-
FHIR-37296 Clarify versionId requirements
- Applied