Difference between revisions of "FHIR Infrastructure Minutes WGM 201805"
Josh mandel (talk | contribs) (Created page with "Category:2018 FHIR Infrastructure Minutes =FHIR Infrastructure 2018 May Cologne WGM Minutes= :Category:2018 FHIR Infrastructure Minutes|Return to FHIR Infrastructure Min...") |
Ewoutkramer (talk | contribs) |
||
Line 19: | Line 19: | ||
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16165 16165], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16127 16127], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17001 17001], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17002 17002] - Versioning discussion; prepared motions for voting Wednesday | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16165 16165], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16127 16127], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17001 17001], [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17002 17002] - Versioning discussion; prepared motions for voting Wednesday | ||
+ | Prepared MOTION for wed may 16 Q2: "Document the MIME-type parameter as a way to describe the version of the resource in the MIME package. | ||
+ | Grahame Grieve/Chris Grenz: 37-0-0" | ||
+ | |||
+ | Straw poll about using "Meta.fhirVersion" versus using "Meta.profile": 8 in favor of "fhirVersion", about 18 for a <profile> based approach. | ||
+ | |||
+ | Below is the example we discussed: | ||
+ | |||
+ | Content-type: application/fhir+xml;fhirVersion=3.0 | ||
+ | |||
+ | <Patient fhir-version="3.0" xmlns="hl7.org/fhir"> | ||
+ | <meta> | ||
+ | <profile value="http://hl7.org/fhir/DSTU2/StructureDefinition/Patient" /> | ||
+ | <profile value="http://hl7.org/fhir/StructureDefinition/Patient|1.0" /> | ||
+ | <!-- assuming no breaking change to patient in 4.0.... --> | ||
+ | <profile value="http://hl7.org/fhir/StructureDefinition/Patient|4.0" /> | ||
+ | <profile value="http://hl7.nz/fhir/StructureDefinition/OurNationalPatient|1.2.1" /> | ||
+ | <fhirVersion value="3.0" /> | ||
+ | </meta> | ||
+ | <!-- more interesting stuff about patient--> | ||
+ | </Patient> | ||
+ | |||
+ | { | ||
+ | "resourceType" : "Patient", | ||
+ | "fhir-version" : "3.0", | ||
+ | "status"... | ||
+ | } | ||
+ | |||
+ | <Patient2> | ||
+ | <!-- some really scary breaking change --> | ||
+ | </Patient2> | ||
==Monday Q2== | ==Monday Q2== |
Revision as of 11:24, 15 May 2018
Contents
FHIR Infrastructure 2018 May Cologne WGM Minutes
Return to FHIR Infrastructure Minutes
Agenda
Attendees
A comprehensive list for the WGM can be seen here: (TODO: extract from http://bit.ly/fhiri after WGM).
Monday Q1
Chair: Ewout Kramer
Attendance sheet: http://bit.ly/fhiri (to be turned into a PDF after meeting)
Tracker Items
Prepared MOTION for wed may 16 Q2: "Document the MIME-type parameter as a way to describe the version of the resource in the MIME package.
Grahame Grieve/Chris Grenz: 37-0-0"
Straw poll about using "Meta.fhirVersion" versus using "Meta.profile": 8 in favor of "fhirVersion", about 18 for a <profile> based approach.
Below is the example we discussed:
Content-type: application/fhir+xml;fhirVersion=3.0
<Patient fhir-version="3.0" xmlns="hl7.org/fhir">
<meta> <profile value="http://hl7.org/fhir/DSTU2/StructureDefinition/Patient" /> <profile value="http://hl7.org/fhir/StructureDefinition/Patient%7C1.0" /> <profile value="http://hl7.org/fhir/StructureDefinition/Patient%7C4.0" /> <profile value="http://hl7.nz/fhir/StructureDefinition/OurNationalPatient%7C1.2.1" /> <fhirVersion value="3.0" /> </meta>
</Patient>
{
"resourceType" : "Patient", "fhir-version" : "3.0", "status"...
}
<Patient2> </Patient2>
Monday Q2
Chair: Ewout Kramer
Attendance sheet: http://bit.ly/fhiri (to be turned into a PDF after meeting)