Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
STU
-
Content Sharing
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Correction
-
Compatible, substantive
Description
If an implementation doesn't obey these lower-case musts, is it still conformant to FHIRcast content sharing?
* the context.versionId does not need to follow any convention but must unique in the scope of a topic
* Clients wishing to exchange structured information must: [*iav - and all six of the bullets following this phrase]
If not, it seems like they need to be normative requirements.
Attachments
Issue Links
- is voted on by
-
BALLOT-35079 Negative - Christopher Schaut : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35722 Negative - Vassil Peytchev : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35747 Negative - Kimberly Herman : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36056 Negative - Amit Popat : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36229 Negative - Daniel Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36279 Negative - David Sundaram-Stukel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36308 Negative - Chris Courville : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36358 Negative - Danielle Friend : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36383 Negative - Cooper Thompson : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36408 Negative - Isaac Vetter : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36254 Negative - Thanos Tsiolis : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-36333 Negative - Daniel Rutz : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted