Details
-
Change Request
-
Resolution: Persuasive
-
Highest
-
FHIRCast (FHIR)
-
2.1.0-ballot [deprecated]
-
Infrastructure & Messaging
-
STU
-
Event library [deprecated]
Multi-anchor considerations [deprecated] -
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Enhancement
-
Compatible, substantive
-
Yes
-
current
Description
What is the intended behavior for secondary events that are included in a close event?
The desired behavior should be defined in the next version.
Attachments
Issue Links
- is duplicated by
-
FHIR-37089 Inclusion of secondary anchors in events when not present in the resource
- Deferred
- is voted on by
-
BALLOT-35235 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35877 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36019 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36115 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36186 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36473 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35806 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35948 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted