This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Infrastructure Minutes WGM 201805"
Jump to navigation
Jump to search
Ewoutkramer (talk | contribs) |
Ewoutkramer (talk | contribs) |
||
| Line 55: | Line 55: | ||
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16957 16957] - Discussed whether GET and POST support should both be required on search | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16957 16957] - Discussed whether GET and POST support should both be required on search | ||
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16369 16369] - Discussed semantics of "significant figure"-based equality operations when searching for decimal, integer, and quantity values | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=16369 16369] - Discussed semantics of "significant figure"-based equality operations when searching for decimal, integer, and quantity values | ||
| − | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14961] - Missing naming convention for search parameters assembling two or more words | + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14961 14961] - Missing naming convention for search parameters assembling two or more words |
Revision as of 11:55, 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"...
}
Monday Q2
Chair: Ewout Kramer
Attendance sheet: http://bit.ly/fhiri (to be turned into a PDF after meeting)
Tracker Items
- 16957 - Discussed whether GET and POST support should both be required on search
- 16369 - Discussed semantics of "significant figure"-based equality operations when searching for decimal, integer, and quantity values
- 14961 - Missing naming convention for search parameters assembling two or more words
