Implementation Conformance Working Group Meeting – January 2011
Conformance and Guidance for Implementation/Testing Working Group San Antonio, Texas, USA – January 19-24, 2014
1. Monday – Q1
CGIT Meeting Minutes Date: January 20, 2014 Location: Chula Vista Boardroom Time: 9 am – 10:30 am
Chair Frank Oemig Note taker(s) Wendy Huang
Attendee Name Email Affiliation
Rob Snelick [email protected] NIST
Frank Oemig [email protected] HL7 Germany
Wendy Huang [email protected] Canada Health Infoway
American Immunization Nathan Bunker [email protected] Registry Association
Quorum Requirements Met: (yes/No)
Yes
1.1. Agenda Topics for Quarter
# Key Description Presenter Action Needed Time 1 Call to Order 9:00 2 Approve agenda Frank 3 Approve minutes (Boston) Frank 4 follow-up action items Frank 5 Project Review Frank 6 V2.8 Revisions Frank 6 Adjournment 10:30
1.2. Minutes/Conclusions Reached Approval of agenda: Moved by R. Snelick, seconded by N. Bunker. Motion passed unanimously 3-0-0. Approval of minutes: Moved by W. Huang, seconded by R. Snelick. Motion passed unanimously 3-0-0.
Conformance facilitator: add a quarter in WGM agenda for conformance facilitator roundtable. Motion to approve conformance facilitator roles & responsibilities: Moved by N. Bunker, seconded by R. Snelick. Motion passed unanimously 3-0-0.
0ac467167c735bdea0501d50a3bef89c.doc Page 1 of 11 Implementation Conformance Working Group Meeting – January 2011
Action items: R. Snelick to create a Project Scope Statement (PSS) for Conformance framework to specify system functional and behavioural requirements upon receiving a message Incorporate V2 value set specification – to be harmonized v2 tables project R. Snelick to create a PSS Explicit specification of conformance statements in v2 implementation guides and v2 standards
1.3. Supporting Documents
Agenda: http://wiki.hl7.org/index.php?title=CGITWG_January_2014_WGM_Agenda Project review: http://wiki.hl7.org/index.php?title=ICTC_Strategic_Plan
2. Monday – Q2
CGIT Meeting Minutes Date: January 20, 2014 Location: Chula Vista Boardroom Time: 11 am – 12:30 pm
Facilitator Rob Snelick Note taker(s) Frank Oemig
Attendee Name Email Affiliation
Rob Snelick [email protected] NIST
American Immunization Registry Nathan Bunker [email protected] Association
Vince McCauley [email protected] MSIA
Parimi, Sailaja [email protected] Cerner
Frank Oemig [email protected] HL7 Germany
Quorum Requirements Met: (yes/No)
Yes
2.1. Agenda Topics for Quarter
# Key Description Presenter Action Needed Time 1 Call to Order 11:00 2 Specifying explicit conformance Rob statements in the base standard and IGs
3 Adjournment 12:30
0ac467167c735bdea0501d50a3bef89c.doc Page 2 of 11 Implementation Conformance Working Group Meeting – January 2011
2.2. Minutes/Conclusions Reached
2.2.1. Specifying explicit conformance statements in the base standard and IGs Rob presents the conformance statements in the implementation guides used in the LRI framework based on HL7 V2.5.1 IG SIF Labresults. Some of the usage codes in the base standards seem to be wrong, because additional conformance statements are hidden in the narrative text. They should be made explicit.
Rob presents also the formal XML representation of the conformance statements.
Motion by Frank/Vince: Establish a PSS to support explicit conformance statements in the base standard and implementation guides: 4-0-0
Actions create PSS for May WGM (Rob)
2.2.2. Message Profile Identifiers (Managing multiple versions-OIDs) Rob presents the current handling of OIDs as message profile identifiers: Profiles undergo many revisions (DSTU, normative, errata) and change, but the OID stays the same. So it is impossible to identify to which revision the implementation is conformant to. How should this problem be solved? One option is to add a new component (“profile version”) to the EI datatype, or to create a new data type which is specific for MSH-21. On the other hand changes to the profile should lead to a new OID, whereas technical corrections do not.
Motion by Frank/Nathan: a new OID shall be issued for a profile when a published change has occurred in a specification (DSTU normative standard or errata): 4-0-0
Actions provide material for chp.2b, v2.9 (Rob)
2.3. Supporting Documents
3. Monday – Q3
CGIT Meeting Minutes Date: January 20, 2014 Location: Chula Vista Boardroom Time: 13:45 am – 15:00 pm
Facilitator Rob Snelick Note taker(s) Frank Oemig
Attendee Name Email Affiliation
Rob Snelick [email protected] NIST
American Immunization Registry Nathan Bunker [email protected] Association 0ac467167c735bdea0501d50a3bef89c.doc Page 3 of 11 Implementation Conformance Working Group Meeting – January 2011
Farkas, Attila [email protected] Canada Health Infoway
Dieterle, Robert [email protected] EMS/OFM
Frank Oemig [email protected] HL7 Germany
Frank McKinney [email protected]
Quorum Requirements Met: (yes/No)
Yes
3.1. Agenda Topics for Quarter
# Key Description Presenter Action Needed Time 1 Call to Order 13:45 2 functional and behavioural requirements Rob 3 Specification of Value Sets in V2.x Rob 4 Cardinality issues when specified as Rob unlimited ("*") in V2.x 5 Adjournment 15:00
3.2. Minutes/Conclusions Reached
3.2.1. Functional and Behavioural Requirements The LRI (Lab Results Interface) IG should harmonize with the HL7 EHR FM. Develop a generic conformance framework for specifying “incorporate” requirements. What does that mean? Incorporating lab results involves storing data elements that were received in the LRI message. It specifies how data are to be imported, attributed, associated, or stored such that the data is subsequently available for use and used such that the lab results support various clinical purposes.
From a behavioural perspective, the action options for the receiver are presented: store exactly, store exactly with translation or store translation. In combination with the translation different options exist how this should be done. Some are referring to the translation service and the corresponding original value. This may raise some issue with the use of communication servers which normally hide this kind of modification from the real system.
Actions
3.2.2. Specification of Value Sets in V2.x not discussed
Actions
0ac467167c735bdea0501d50a3bef89c.doc Page 4 of 11 Implementation Conformance Working Group Meeting – January 2011
3.2.3. Cardinality issues when specified as unlimited ("*") in V2.x not discussed
Actions
3.3. Supporting Documents
4. Monday – Q4 cancelled
5. Tuesday – Q1
CGIT Meeting Minutes Date: January 21, 2013 Location: Guest Room 1367 Time: 11:00am – 12:30pm
Facilitator Wendy Huang Note taker(s) Frank Oemig
Attendee Name Email Affiliation
CGIT Rob Snelick [email protected] NIST
CGIT Frank Oemig [email protected] HL7 Germany
Sheryl Taylor Booz Allen Hamilton
Abdul Malik Shakir Hi3
Quorum Requirements Met: (yes/No)
Yes
5.1. Agenda Topics for Quarter
# Description Presenter Action Needed Time 1 Call to Order 9:00 2 Tooling Update Rob 3 Adjournment 10:30
5.2. Minutes/Conclusions Reached
5.2.1. IGAMT Rob presents the current version of IGAMT – the Implementation Guide Authoring Management Tool.
0ac467167c735bdea0501d50a3bef89c.doc Page 5 of 11 Implementation Conformance Working Group Meeting – January 2011
This includes the proposal to handle value sets in version 2. This includes open/closed, implicit/explicit and static/dynamic.
5.2.2. MWB The newest version of the software is published on source-forge. Matthew Graham is currently maintaining it. CGIT does not have the resources to maintain it.
Actions synchronize with Abdul-Malik about the conformance tutorial (Rob, Frank)
6. Tuesday – Q2
CGIT Meeting Minutes Date: January 21, 2013 Location: Guest Room 1367 Time: 11:00am – 12:30pm
Facilitator Wendy Huang Note taker(s) Frank Oemig
Attendee Name Email Affiliation
CGIT Rob Snelick [email protected] NIST
CGIT Wendy Huang [email protected] Canada Health Infoway
CGIT Frank Oemig [email protected] HL7 Germany
Quorum Requirements Met: (yes/No)
No
6.1. Agenda Topics for Quarter
# Description Presenter Action Needed Time 1 Call to Order 11:00 2 RCnL: Revision/Update Wendy 3 Adjournment 12:30
6.2. Minutes/Conclusions Reached Wendy started to work on a Word document containing the latest release of RCnL specification. The working document should be shared via Google-Docs. It contains the complete document, ie. it will not be split into pieces. We worked on the first chapter and applied the necessary changes.
6.3. Meeting Outcomes
0ac467167c735bdea0501d50a3bef89c.doc Page 6 of 11 Implementation Conformance Working Group Meeting – January 2011
6.4. Supporting Documents
7. Wednesday – Q4 (Joint with FHIR+Templates)
CGIT Meeting Minutes Date: January 22, 2012 Location: Hyatt Regency Baltimore Time: 3:30 – 5 pm
Facilitator Lloyd McKenzie Note taker(s) Frank Oemig
WG Name Email Affiliation
CGIT Frank Oemig [email protected] HL7 Germany
CGIT Wendy Huang [email protected] Canada Health Infoway
Kai Heitmann [email protected]
MnM (FHIR) Ewout Kramer [email protected] Furore
Cahndra Shelchar [email protected] HL7 India
Leslie Sistla [email protected] Microsoft
Michael Donnelly [email protected] Epic
Youn Lee [email protected] LHLS
Joon Hyun Song [email protected] LHLS
Josh Mandel [email protected] Boston Childrens
Mark Shafarman Shafarman Consulting
Ed de Moel [email protected] HRG
Tony Mallia [email protected] Edmondsci
Lavanian [email protected] HL7 India
Quorum Requirements Met: (yes/No)
Yes
7.1. Agenda Topics for Quarter
# Key Description Presenter Time 1 Call to Order 3:30 pm 2 Conformance FHIR resources Ewout Kramer 3 Templates Kai Heitmann 4 Adjournment 5 pm
0ac467167c735bdea0501d50a3bef89c.doc Page 7 of 11 Implementation Conformance Working Group Meeting – January 2011
7.2. Minutes/Conclusions Reached
7.2.1. FHIR The two resources CGIT are responsible are: Resource profiles and Conformance. Those resources were reviewed by CGIT and MnM.
Revisit ballot item 207: consider defining search in Profile, declaring search in conformance: how should parameters for searches be declared? This must be combined with additional searches itself. It has two aspects: a) the definition of the query itself, ie. a new search operation is done in profiles and b) whether the server supports it is done in conformance. We can vote “persuasive with mod” on this.
What should the rules be for new versions of Profiles? Must they be “compatible” with the prior version (and if not, create a new profile), or are breaking changes allowed? Statements: A change of purpose must require a new profile. Different value set binding. Change of cardinality and/or conformance. Changed references to other templates/resources. Breaking backward compatibility requires a new template/resource. With templates the profile is identified by its purpose (=ID) combined with an effective date.
Is this even something LH7 should be making rules about? plans for new resources and profiles
Ewout has provided a demo of his tool for profiling resources in FHIR.
Tony Mallia als shortly introduces his ideas about doing the validation for FHIR profiles via XML schemas.
7.2.2. Templates
7.3. Meeting Outcomes
7.4. Supporting Documents Conformance: http://www.hl7.org/implement/standards/fhir/conformance.htm Resource Profiles: http://www.hl7.org/implement/standards/fhir/profile.htm
8. Thursday – Q1 (joining Vocab)
CGIT Meeting Minutes Date: January 23, 2013 Location: Seguin Time: 9 am – 10:30 am
Facilitator Note taker(s) Frank Oemig
WG Name Email Affiliation
0ac467167c735bdea0501d50a3bef89c.doc Page 8 of 11 Implementation Conformance Working Group Meeting – January 2011
Ted Klein Klein Consulting
CGIT Frank Oemig [email protected] HL7 Germany
CGIT Wendy Huang [email protected] Canada Health Infoway
CGIT Rob Snelick AIRA
Carmela Couderc Siemens
Jim Case
Parimi, Sailaja [email protected] Cerner
Sheryl Tailor BAH
Robert McClure VSAC
?????
Frank McKinney
Quorum Requirements Met: (yes/No)
Yes
8.1. Agenda Topics for Quarter
# Key Description Presenter Action Needed Time 1 Call to Order 9:00 am 2 Value Set Classification Proposal Rob 3 Adjournment 10:00 am
8.2. Minutes/Conclusions Reached Ted introduces the current status of our joint (vocab+CGIT) initiative to harmonize the vocabulary model among versions 2 and 3.
8.2.1. Value Set Classification Proposal Rob presents an update to the Cambridge presentation which includes the newest outcome on how to provide guidance value set use. Currently the table values in v2 do not provide any guidance and allow for multiple interpretations. When profiling messages all elements are listed with their datatypes, cardinality, usages etc. It only lists a reference to the tables. This normally does not include conformance requirements. This must be added: Conformance Binding: - mandatory - recommended
Combination with optionality: R + mandatory => SHALL RE + recommended => SHOULD O + mandatory => choice to implement it, but if it is a SHALL (i.e. provisional)
0ac467167c735bdea0501d50a3bef89c.doc Page 9 of 11 Implementation Conformance Working Group Meeting – January 2011
Each value in the table should also have a usage: R = required P = permitted E = excluded The vocabulary group has used a different set of terms: min/max/ignore value sets, but in principle it is the exact same thing.
This raises the discussion about the use of the datatypes CWE and CNE because they mix the use of codes with the extensibility of the value set.
The value set classification requires 2 attributes that have conformance implications and are the basis for establishing a value set classification - extensibility -- open: derived profiles may extend the value set -- closed: value set is fixed - stability -- static: member list is fixed forever -- dynamic: member list may change with new versions of the codesystem
8.3. Meeting Outcomes
8.4. Supporting Documents
9. Thursday – Q2 (joining Vocab)
CGIT Meeting Minutes Date: January 23, 2013 Location: Seguin Time: 11 am – 12:30 am
Facilitator Note taker(s) Frank Oemig
WG Name Email Affiliation
Ted Klein Klein Consulting
CGIT Frank Oemig [email protected] HL7 Germany
CGIT Wendy Huang [email protected] Canada Health Infoway
CGIT Rob Snelick AIRA
Frank McKinney
Sheryl Taylor BAH
Jim Case
Robert McClure MD Partners
Carmela Couderc Siemens 0ac467167c735bdea0501d50a3bef89c.doc Page 10 of 11 Implementation Conformance Working Group Meeting – January 2011
Parimi, Sailaja [email protected] Cerner
Salimah Shakir [email protected] Hi3
Quorum Requirements Met: (yes/No)
Yes
9.1. Agenda Topics for Quarter
# Key Description Presenter Action Needed Time 1 Call to Order 11:00 am 2 Value Set Classification Rob 3 Binding Syntax Project Wendy/Frank 4 Adjournment 12:30 am
9.2. Minutes/Conclusions Reached Ted introduces the current status of our joint (vocab+CGIT) initiative to harmonize the vocabulary model among versions 2 and 3.
9.2.1. Value Set Classification Proposal (continued) Discussion about the notion of implicit and explicit : For small tables it could be done. For big tables (Snomed CT has app. 400.000 codes) this approach is not suitable.
A constrainable profile is a profile with options. Those options can be further constrained. This may either result in another constrainable profile or an implementable profile. The latter has no options, but still allows for adding further constraints. For example, an “O” can be constrained to “RE” which is implementable then. But an “RE” can also be constrained to “R”.
Adding local codes to a value set creates a new value set with a new identifier. This use case should be reflected in the slides and further explained.
Actions create a PSS for a project to further work on vocabulary conformance, hosted by CGIT, co- sponsored by Vocabulary (Rob)
9.2.2. Binding Syntax Project Tabled for the next meeting.
9.3. Meeting Outcomes
9.4. Supporting Documents Rob’s PPT
0ac467167c735bdea0501d50a3bef89c.doc Page 11 of 11