MnM Minutes WGM 201510 Atlanta

Return to MnM Minutes for 2015

Sunday Oct 4 Q3 - Finalize Agenda/Review Hot Topics

Attendees

Lloyd McKenzie (Gevity), Thomas Lukasik, Rebbecca Mathews (NEHTA), Grahame Grieve (Health Intersections), Austin Kreisler (Leidos), Woody Beeler (Beeler Consulting)

McKenzie Chaired. Called to order. Reviewed the calendar of agenda dates to identify likely topics and issues to be discussed this week. The results were incorporated into the draft agenda on the Wiki.

Among the issues considered:

• Desire to base CDA release 2.1 on a back-release of the RIM, and include more recent vocabulary (Beeler will join StrucDoc)
• Future directions for RIM release, as there have been few RIM class and attribute changes of late
• Need to update Core Principles (in future) to reconcile Vocabulary binding that Beeler and Klein have submitted as an ISO standard

Completed session at 2:15 PM.

Monday Oct 5 Q3 - Join Joint with O&O, FHIR, InM

OO Chairs

Discussion of the management, in FHIR, of the life-cycle events in medical events from order through to ompketion and revision. A bit of dynamic model redux.

See OO minutes

Monday Oct 5 Q4 - - Join Joint with O&O, FHIR, FM, InM

OO Chairs

Continue life cycle discussions from Q3.

See OO minutes

Tuesday Oct 6 Q3 - Hosting FHIR

McKenzie chairs

Joint meeting to consider FHIR data types issues

Attendees: Lloyd McKenzie (Gevity - chair/scribe), Michael Donnelly (Epic), Rebbecca Matthews (NEHTA departed early), Ken Lord (OHT MDMI), Paul Lomayesva (Intersystems), Michelle Miller (Cerner)

Reviewed and approved dispositions to the following tracker items:

• 8665
• 8786
• 8697
• 8695

Wednesday Oct 7 Q1 - Hosting Vocabulary and FHIR

Beeler chairs

Attendees

Baptist, Joseph (NICTIZ Nat.ICT.Inst.Healthc.Netherlands)

Beeler Jr, George (Woody) (Beeler Consulting LLC)

Case, James (National Library of Medicine)

Couderc, Carmela (Intelligent Medical Objects (IMO))

Daniels, Reuben (National eHealth Transition Authority (NEHTA))

Davis, Nathan (Intermountain Health Care)

Farkas, Attila (HL7 Canada)

Friend, Danielle (Epic)

Grieve, Grahame (Health Intersections Pty Ltd)

Hamm, Russell (Lantana Consulting Group)

Hausam, Robert (Hausam Consulting LLC)

Hay, David (HL7 New Zealand)

Hirai, Masaaki (HL7 Japan Voter #2 - Nihon Kohden Corp, Eng. Oper.)

Kavanagh, Richard (HL7 UK)

Klein, William Ted (Klein Consulting, Inc.)

Knapik, Carolyn (College of American Pathologists)

Konishi, Yukinori (HL7 Japan)

Lau, Lee Min (3M Health Information Systems)

Macumber, Caroline (Apelon, Inc.)

McClure, Robert (MD Partners, Inc.)

McKenzie, Lloyd (Gevity (HL7 Canada))

Miller, Michelle (Cerner Corporation)

Narcisi, Jean (American Dental Association)

Parker, Craig (Intermountain Healthcare)

Shapiro, Ron (Qvera)

Shaver, Dave (Corepoint Health)

Snelick, Robert (National Institute of Standards and Technology)

Stuart, Sandra (Kaiser Permanente)

Takasaka, Sadamu (HL7 Japan)

Wang, Yunwei (Intelligent Medical Objects (IMO))

Grain, Heather (HL7 Australia)

Martinez, Sandra (NIST)

Hendler, Peter (Kaiser Permanente)

Work through list of FHIR vocabulary issues

G. Grieve introduced the topics

FMM Levels

Reviewed the FHIR Maturity Model levels (see FHIR_Maturity_Model). Vocab resources are currently at Level 3 and a strong candidate for four. If some of the changes suggested below are adopted, it would drop back and and await first publication in DSTU 3, using the current form in DSTU 2.1 ballot. Agreed to defere a decision on any change to the current terminology FMM levels.

OID for URI (8630)

In FHIR URIs are used as codes. Need an OID for URI. Agreed: Grieve will request and OID from HL7 OID service.

Migration for FHIR-defined codes

Need support (volunteer?) to work through these.

Issue is what can FHIR move to the published HL7 Vocabulary Store by proposing it to Harmonization. Challenges are the time it takes anything to get through Harmonization, in order to publish it in a draft FMM document being prepared for ballot.

Suggest that the FMM be applied to Code Systems and Value sets, and then have this affect the FMM level of the resources that refer to it.

Expansion profiles

GG volunteered to draft an Expansion resource (working with other volunteers) and bring this forward for consideration as a 2.1 resource.

Consideration of a CodeSystem resource - move out of ValueSet2

Key to note is that FHIR does NOT want to define large, complex Code Systems, and hence it was encompassed in the Value Set that was all codes for the numerous, small code systems.

The notion here is to build a resource that contains the meta-date needed to identify a Code System and to navigate to a particular concept or value set thereof. The idea is not to build a complete system, including coded concepts. Agreed next step is to draft such a service to resolve the "boundaries" of this resource,

Topics not considered

The following three topics were not considered in this meeting and will be covered in future conference calls

• Terminology service API
• Catalogs and Value Sets
• Repeat bindings

Report from the Connectathon (Hausam)

Over 1/4 of group were exercising Terminology Services. Made good progress and several services being trialed. Apelon and Lantana integrated FHIR API into their products. Good test scripts resuted.

Wednesday Oct 7 Q2 - Hosting Vocabulary

Beeler chairs

MnM Issues on vocabulary, including the Value Set definitions, and the ISO Binding topics, both of which impact on Core Principles

Attendees

Baptist, Joseph (NICTIZ Nat.ICT.Inst.Healthc.Netherlands)

Beeler Jr, George (Woody) (Beeler Consulting LLC)

Case, James (National Library of Medicine)

Daniels, Reuben (National eHealth Transition Authority (NEHTA))

Farkas, Attila (HL7 Canada)

Friend, Danielle (Epic)

Hamm, Russell (Lantana Consulting Group)

Klein, William Ted (Klein Consulting, Inc.)

Lau, Lee Min (3M Health Information Systems)

McClure, Robert (MD Partners, Inc.)

McKenzie, Lloyd (Gevity (HL7 Canada))

Narcisi, Jean (American Dental Association)

Orlova, Anna (American Health Information Management Association)

Stuart, Sandra (Kaiser Permanente)

Grain, Heather (HL7 Australia)

Abher, Sheila (Lantana Group)

Binding Syntax

Publication of ISO Binding is imminent

Binding syntax project is more active again. It will involve updating the Core Principles - may move binding information out of Core Principles and have a separate document for Binding Syntax. Could go forward to ISO.

Core Principles

Reviewed proposed changes for Core Principles. Will need to align with/adjust to reference value set definition and binding syntax documents

Will put together a PSS in Orlando for Core Principles R3

Harmonization

Need to explore alternatives to current process, including taking advantage of social processes.

v2 table clean-up will fold into this. (Want to keep the content clean)

TQA

Woody agreed to step forward as MnM representative

Thursday Oct 8 Q1 - Hosting FHIR

McKenzie chairs

FHIR Methodology issues

Attendees

Lloyd McKenzie (Gevity - chair, scribe), Clem McDonals (NLM), Jeffrey Ting (Systems Made Simple), Elizabeth Newton (CICP), Richard Kavanagh (England NHS), Michel Rutten (Furore)

Tracker Items

• 8591 - approved change
• 8119 - approved change
• 7435 - categorized as workflow
• 5163 - categorized as workflow
• 5160 - deferred to release 3
• 5474 - approved change

Profiling QA Criteria

Reviewed the list of QA criteria used for resources to examine what criteria might apply to which conformance resources within the scope of a particular implementation guide.

• Extension definition StructureDefinitions
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
  • 2a (Should have at least 1 for non-trivial extensions – i.e. not for dates, numbers, etc. However good for complex multi-element extensions or for strings or unbound coded elements to show how element might be used. Can be covered by an example instance using a containing resource instance.)
  • 2b
  • 3a HL7 Int’l defined extensions must include RIM mappings or must explicitly declare they are not RIM mappable
• Constraint StructureDefinitions
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
  • 2a
  • 2b
  • 2c
  • 3a RIM mappings are only required for HL7 Int’l-defined constraint profiles if the mappings would differ from the underlying resource.
• ValueSets
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
• ImplementationGuide instance
  • 1a (Just one context)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
• ConceptMap
  • 1c
• NamingSystem
• Conformance
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
• OperationDefinition
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 1c
  • 2a (1 or more examples showing invocation & response. Examples should cover major expected parameter combinations. Every parameter should be covered at least once)
  • 2b
• SearchParameter
  • 1a (Could be multiple or just one)
  • 1b (Only in the scope of HL7 Int’l-defined artifacts)
  • 2a (At least one - Show in combination with other parameters with an explanation of intent of the search. I.e. how might this parameter be used to solve real use-cases.)
  • 2b
• TestScript
  • 1a (Just one)

Thursday Oct 8 Evening - Facilitator's Roundtable

Shakir chairs