Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
STU
-
Content Sharing
-
2.10
-
-
Bas van den Heuvel / Trent Nolin: 7-0-0
-
Correction
-
Non-compatible
-
2.1.0-ballot [deprecated]
Description
Content sharing can be done in different ways. By using a FHIR server or (when one does not want one), the method explained in this section or in a various hybrid approaches.
Both alternatives should be discussed/presented in this section.
I also miss how the two approaches can be combined and I miss a section that recommends what solution to take in what situation.
Attachments
Issue Links
- is voted on by
-
BALLOT-35259 Negative - Bas van den Heuvel : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35854 Negative - Javier Espina : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35996 Negative - David Simons : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36092 Negative - Peter Kranich : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36163 Negative - Lisson Zhang : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-36450 Negative - Chris Melo : 2022-May-FHIR IG FHIRCast R1 STU
- Withdrawn
-
BALLOT-35783 Negative - Vadim Peretokin : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
-
BALLOT-35925 Negative - Olivia Bellamou-Huet : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted
- relates to
-
FHIR-37056 FHIRcast must be aligned with FHIR Subscription
- Resolved - No Change