Difference between revisions of "MnM Minutes WGM 201601 Orlando"
| Line 89: | Line 89: | ||
*A Urn iso-astm:E1762-95:2013 | *A Urn iso-astm:E1762-95:2013 | ||
| − | == | + | ==Signature Type Value Set== |
| + | Closed. Grahame will communicate with Security work group to seek a path or alternative to the use of ASTM Code system for this Value Set | ||
=Wed Q2 - Hosting Vocabulary and FHIR Infrastructure= | =Wed Q2 - Hosting Vocabulary and FHIR Infrastructure= | ||
Revision as of 14:36, 13 January 2016
M&M Working Group Meeting - January 2016 - Orlando
Return to MnM Minutes Return to: WGM Minutes > 2016 > January Orlando
Mon Q2 - Open Business
Agenda
- Approve Minutes Prior Meeting on 12/01
- Approve Minutes Prior Meeting on 01/05
Attendees
- Woody Beeler, Beeler Consulting (chair)
- Elliot Silver, McKesson
MnM Functions
We lacked quorum, and therefor took no action on the minutes listed above and moved them to the next MnM quarter.
Elliot Silver, who is a Co-Chair of the Imaging Integration Work Group (IIWG) came to this session because he was interested in the modeling and desirous of determining how best the IIWG should interact with the modeling and terminology aspects of Vocabulary and FHIR.
Beeler provided a brief, but brilliant, overview of the history of MnM, RIM and V3 and its relationships to FHIR. In discussion we agreed he should contact McKenzie regarding the RIM-mapping of the ImagingObjectSelection resource in FHIR, might avail himself of pizza at the Facilitator's Roundtable, and should contact Vocabulary in regards to establishing a Vocabulary Facilitator role for the IIWG, if that is needed.
Tue Q3 - Hosting FHIR Infrastructure
Agenda
- TBD by FHIR
Attendees
- Lloyd McKenzie (chair/scribe)
- Bob Bishop
- Dennis Patterson
- Ewout Kramer
- Ron Shapiro
- Michael Donnelly
- Joshua Mandel
- Kevin Shekleton
- Artem Sopin
- Mead Walker
How do _include and _revinclude work?
Question from Artem. Brief discussion and explanation of how these can be used.
Artem agreed to submit a change request to include a 'complex' example showing how multiple layers of _include, _revinclude and various other search parameters could be combined
How much consistency can we expect from servers?
Question from Artem. Short answer: none. In the base spec, servers are permitted to have a wide range of capabilities. Consistency around server capabilities can only be expected if the server capabilities are standardized by agreed profiles. Clients who want to work with a wide range of servers will need to query the Conformance instance of the server and adapt to what the server can manage and handle the rest itself and/or limit its own exposed capabilities to reflect those of the server.
Grahame request
These 3 value sets: http://hl7.org/fhir/valueset-signature-type.html http://hl7.org/fhir/valueset-timing-abbreviation.html http://hl7.org/fhir/valueset-identifier-type.html
each include codes defined in a code system that is not bound to the schema. For this reason, the codes defined in these 3 value sets are supposed to moved through harmonization to elsewhere
- timing=abbreviation - add to GTSAbbrevation
- identifier-type -> add to v2 table
- signature-type: policy question
Change proposals
See trackers for votes & details
Wed Q1 - Hosting Vocabulary and FHIR Infrastructure
Agenda
- Signature type VS
- FHIR Code systems
- Expansion profile resource
- Archive Project 761 -
- Vocabulary Processes for
- V2, CDA CIMI
Attendees
- George Beeler (chair)
- Ted Klein
- Sheryl Taylor, NIST
- Sandy Stuart
- Grahame Grieve
- A Urn iso-astm:E1762-95:2013
Signature Type Value Set
Closed. Grahame will communicate with Security work group to seek a path or alternative to the use of ASTM Code system for this Value Set
Wed Q2 - Hosting Vocabulary and FHIR Infrastructure
Agenda
- TBD
Attendees
- Beeler (chair)
Agenda Item 1 Goes here
Thu Q2 - Hosting FHIR Infrastructure
Agenda
- Approve Minutes Prior Meeting on 12/01
- Approve Minutes Prior Meeting on 01/05
- TBD
Attendees
- McKenzie (chair)
Agenda Item 1 Goes here
Thu Q5 - Facilitators Roundtable
Agenda
- Introductions
- Scheduling of the 2016 Harmonization deadlines and Meetings
- Seek comments from each represented Work Group of their intended Harmonization proposals
- Other Business
Attendees & Introductions
- Shakir (chair)
Scheduling of 2016 Harmonization
The following schedule works backwards from the planned "ballot open" dates as posted on the HL7 Website. In the following, the notation T1, T2 and T3 represent the first, second and third trimesters of the HL7 year.
T1 Harmonization March 1-3 2016
- Initial Proposal Deadline January 31, 2016
- Final Proposal Deadline February 21, 2016
T2 Harmonization July 12-14 2016
- Initial Proposal Deadline June !2, 2016
- Final Proposal Deadline July 3, 2016
T3 Harmonization November 8-10 2016
- Initial Proposal Deadline October 9, 2016
- Final Proposal Deadline October 30, 2016
