MnM Minutes WGM 201109 San Diego
- 1 Sunday September 11 Q3
- 2 Monday September 12 Q3
- 3 Monday September 12 Q4
- 4 Tuesday September 13 Q1
- 5 Tuesday September 13 Q2
- 6 Tuesday September 13 Q3
- 7 Tuesday September 13 Q4
- 8 Wednesday September 14 Q1
- 9 Wednesday September 14 Q2
- 10 Wednesday September 14 Q3
- 11 Wednesday September 14 Q4
- 12 Thursday September 15 Q2
- 13 Thursday September 15 Q5
- 14 Friday September 16 Q1
Sunday September 11 Q3
Lloyd McKenzie (chair), Grahame Grieve, Alexander Henket, Sarah Gaunt, Steven Royce, Andy Stechishin, Woody Beeler, Jean Duteau, Hugh Glover, Patrick Lloyd, Russ Hamm, Austin Kreisler
Establish Agenda for WGM from Hot Topics and Other Items
- Reviewed the existing Hot Topics
- Determined which would be considered
Motion: MnM believes there should be a project for RFH exploration and refinement (including impacts on existing methodology) and wishes to be sponsor or co-sponsor of such a project.
Motion: Approve Agenda for week
Monday September 12 Q3
Lloyd McKenzie (chair), Sarah Gaunt, Steven Royce, Stephen Chu, Woody Beeler, Andrew McIntyre, William Goossen, Kevin Coonan
Joint with Patient Care to Discuss Detailed Clinical Models (DCM)
Discussion Opened by Dr. Goossen and ultimately centered on the "granularity" of a DCM and whether "clinical elements" are independent or not.
Patient Care concedes it is still seeking the appropriate path to represent and document their work.
Consideration of preparing SAIF Artifact Definitions to meet their needs was suggested, and they were encouraged to join that effort.
The challenge is how to accommodate the various conceptual models that groups seek.
Monday September 12 Q4
Lloyd McKenzie (chair), Sarah Gaunt, Steven Royce, Rik Smithies, Woody Beeler, Rene Spronk, Ewout Kramer
Agenda Host Clinical Statement Work Group
Discussion was based on Wiki page Design Patterns for RIM Models
Clinical Statement - Is it Model vs Pattern? - Objective was as a model that would be constrained
Tools vs. Objectives - Current tools do not enforce any derivation (except the RIM). Does not provide traceability; detection of alignment vs difference;
Could/should portions of Clinical Statement become patterns that could be used to evaluate other models? More likely that sections of CS would be identified and then form the basis for a pattern.
What is pattern?
A "model fragment" (incomplete model) made up of "incomplete classes" -- incomplete implies that further extensions that are RIM-conformant can be used in the model whose content is based on the pattern.
Ergo, a Pattern is also a template.
NOTE: The class/clone names in a pattern are NOT required to be used in instantiating the pattern.
Design Pattern Meta-data
The pattern "Sections" of Design Patterns for RIM Models lists are the "Information Model Design Pattern Definition" one component of which is the model.
Agreed to a formal name of "Information Model Design Pattern" for these and the Wiki page above needs to be edited to this end.
Agreed to build a Wiki Template for Design Pattern Definitions. LM will flesh out the sections and GB agreed to Wikify them.
Clinical Statement Work Group will undertake to consider elements of Clinical Statementthat can be proposed as Information Model Design patterns.
Tuesday September 13 Q1
Grahame Grieve(Chair), Woody Beeler, Lloyd McKenzie, Sarah Gaunt, Austin Kreisler, Ann Wrightson, Corinne Gower, Adel Ghlamallah, Rob Hausam, Brian Pech, Peter Hendler, Rene Spronk, Ewout Kramer, Alexander Henket, Mark Tucker
Agenda - Resources for Healthcare (RFH) - Governance of artifacts & managing complexity
Grahame Grieve summarized the background of RFH (starting in MnM discussions in May 2011); its value propositions in regards to V2 and V3; the challenge of dealing with the complexity of our healthcare specifications. Primarily that the complexity should be tied to a super-rich ontology rather than describing it in detail in static models or V2 segments. Resulting in a collection of small "resources" information modules that can be communicated on there own, aggregated into records, but that provide a framework in which a simpler, smaller set of choices in constructing exchanges.
Briefly jumped to the preliminary definitional documents for RFH. (Core documents for RFH are available at http://www.healthintersections.com.au/rfh/introduction.htm.)
Highlighted the linkages of the elements to RIM (if required); features for extensibility to avoid the challenge of including everyone's edge case in a single universal model. In this circumstance the governance of
Observation that the increasing complexity of issues of systems connections, bindings, etc. that lie beneath the health care content complexity are a bigger hurdle for implementations. Divergence of "local models" from "universal" models.
Expectations from Grieve:
- Work Group that manages the RFH Ontology and Methodology and delegates ontology space to other Work Groups
- Work Group that manages wire format issues
- Work Group that allocates Resources to Domain Work Group
- Work Group that manages extensibility, including the prompt issuance of extensibility codes, where required, after a proper definition has been provided.
Extensibility vs Evolution
Extensibility mechanism includes the ability to declare extensibility in the instance citing extension codes that have been defined and registered under HL7 Governance.
Observations and Modest consensus on questions
- Will be critical to be able to fold extensions into a future release of a resource, because resources that cannot evolve are too rigid.
- Discussion begs the question of whether there should be provision "Stakeholder-namespace extension code" in addition to an "HL7-namespace extension code"
- Will need to deal with issues for retiring resources.
- Agreed in re Extensions
- There is need for some extensibility mechanism such as that cited
- Need to be able to extend by defining your own concepts
- Should define relationships between your and HL7 concepts, where exist
- Be able to extend rapidly
- Extensions need to be documented and collected
- Need to understand - early on - how will one refactor and reissue the ontology?.
- How does one manage the resource space (boundaries between resources), specifically -
- Resource overlap
- Scope (size)
- Resources that are about single item but different level of detail
- Differences by realm or practice scope
- Needs to be STRONG consideration of the mechanism for grouping resources and whether these make it easier to consider how to deal with the important, but "different" realms
- How can resource definition management and maintenance be enabled and handled in multi-SDO environment.
Tuesday September 13 Q2
Grahame Grieve(Chair), Woody Beeler, Lloyd McKenzie, Sarah Gaunt, Austin Kreisler, Ann Wrightson, Brian Pech, Peter Hendler, Ewout Kramer, Cecil Lynch, Jean Duteau, Gaby Jewell, Stephen Royce, Dale Nelson, Robert Worden, Alexander Henket, Mark Tucker
Agenda - Resources for Healthcare (RFH) - RIM in OWL and RIM Ontology
Overview by GG
- Exchange specification (XML formats)
- Ontology: Formal definition of the formats
- Defines elements
- Defines Reference models
- Defines relationships between models and elements
- Makes rules about
- Kind of relationships that can exist and those that are required
- What additional attributes relationship can have
- Design Patterns,
- Domain glossaries
(Above from Grieve's slides, but is incomplete.)
Can we manage this as an Ontology?
- We believe we can embody the concepts and elements we need in an ontology
- Need to define an HL7 Reference Ontology that HL7 manages and defines the conformance to the element it defined.
OWL as Candidate Ontology Discussion
- Closed world only statements in my ontology are true
- Open world, anything not explicitly negated may be true
- LM: Cannot permit extensions to the RIM and remain conformant
- SG: Looked (in past) at how to represent models in ontology. At first rejected OWL because could not constrain in it, but later questioned decision. Should be possible to add albeit with ability of any user to recognize the "outside" extensions and skip them.
- GG: Can we make our own rules and test them - that is a key requirement
- LM: Four levels: base definition, extensions, local ontology defined against core, other stuff. Notion is that these should be considered in conformance rules, "other stuff" may be uglyu and non-conformant, but it will exist.
- CL: OWL weaknesses
- In "open world" - If I say cardinality is and must be "2", OWL will allow a cardinality of "1" because it assumes the second is "coming"
- PH: Asserts that if an Act is defined, and someone adds an attribute, all prior Acts are no longer Acts. (I am confused).
- SG: In OWL, the rules do not come from the model, they come from OWL
- GG: Question posed was can it be done in OWL? Believes answer is yes, but it is not manageable. Discussion has exposed complexity that has nothing to do with the problem we are trying to solve.
- RW: Unsure what the question is is
- MT: Actually the changed Act becomes a sub-type, it does not change Act. Is the OWL complexity actually part of the 10% that we are trying to avoid.
- CL: What's missing - make statements that are illogical in RIM and vocabulary that ??? Perhaps we just need RDF and not all of OWL (?). Believes that rules engines are a reasonable consideration along with OWL.
- LM: Does not believe we are trying to "fix" the RIM, rather trying to find a more effective way to define and use elements defined against it.
- GG: In answer to RW - wants and ontology layer to (see Requirements on Ontology below
- WB: In regards MT comment that OWL complexity is the 10% on the 90-10 solution: problem is that it goes to the question of manageability of extensibility which is the central method for allowing one to ignore the 10%
- AW: Complexity we get into will depend upon the degree of control we believe we need to have. Fear that the more open one gets is when we will see increase in complexity.
- RW: In re: LM. statement. Clarified.
- GG: Rules are PRIMARILY intended to control US and make it clear that we are following our principles
- PH: Argues for subset of OWL to address the problem, except that a new relationship to an existing class negates all prior instances of that class.
- CL: Believes there is a very steep learning curve to using OWL for this end (and more difficult then SNOMED).
- GG: It cannot be arcane to add simple extensions, given requirements. Certainly the core setup will be complex and arcane.
- AK: The whole needs to be more accessible, not less accessible to people.
- PH: If we reduce it, its no different than SNOMED. Why don't we just try it.
- WB: If its no different but raises as much angst as we've heard, why start on it. AND we do not have the bandwidth to "just try it" while we are already just trying RFH.
Requirements on Ontology
- Use concepts as a basis for Reasoning
- Define concepts
- With rich text definitions
- Relationships between concepts
- Make rules about relationships
- Define content modularly (distributed development)
- Define concepts externally and then bring them in
- Based on a standard
- Must not need a PhD to implement this stuff or request extensions
AW: Should we not revisit what we have and apply the RFH principles to what we have.
GG: Thank all for participating. The majority of the complexity we have talked about is about OWL and suggests perhaps the tool is overqualified for the problem.
(WB: I did my best on these minutes. If I miss-summarized you, it was through my ignorance and not intentional.)
Tuesday September 13 Q3
Hosted by ClinicalDocuments. Refer to their minutes
Tuesday September 13 Q4
Lloyd McKenzie, Woody Beeler (chair), Adel Ghlamallah, Karyn Harris, Andy Stechishin, Stephen Royse
- Static Model Quality Checklist
- Woody provided history and background on the Static Model checklist
- Checklist categories
- Add reference link to Use Id pattern
- Add reference to Act.text Usage notes in RIM
- Issue Usage notes in RIM document is an open issue
- First Context Conduction stays
- The ContetConductionStyle for the model MUST be 'V'and if one or both of the ActRelationship"blockedConduction...." attributes is present it must be mandatory and have a fixed value (set orf values) assigned.
- Review the Metadata for the design with V3 Publishing
- Vocabulary Constraints
- Generic concepts can be automatically detect but needs to be assessed for validity
- Concept domain specified for code needs to be assessed by human
- Tooling issue: coding strength should only be specified for model bindings not for domain bindings or fixed codes.
- Attribute Constraints
- Added to wiki page
- No changes
Motion: Endorse the changes made to the checklist and authorize Publishing to proceed to implement tests where possible (Lloyd, Andy) 5-0-0
Wednesday September 14 Q1
Woody Beeler, Kevin Brady, Ted Klein, Beverly Knight, Sandy Stuart, Stephen Royce, Asif Syed, Brian Schwallier, Lloyd McKenzie, Stacy Berger, David Halbert, Jim Case, Mark Shafarman, Carmela Couderc
- Host Vocabulary: Publishing a value set in DEF or CRIT mood
Woody Beeler, Kevin Brady, Ted Klein, Beverly Knight, Sandy Stuart, Stephen Royce, Asif Syed, Brian Schwallier, Lloyd McKenzie, Stacy Berger, David Halbert, Jim Case, Mark Shafarman, Carmela Couderc
v2 datatype issues
MnM and InM co-chairs need to discuss who has responsibility for HL7 v2.x datatypes and ensure our mission and charter reflects the responsibility. (MnM is not sure they have appropriate expertise to take it on.)
HL7 Terminology Authority
- HL7 needs to set up a terminoloy authority as per our agreement with IHTSDO
- Will have some impact on harmonization processes
- Lloyd will take on a role with the terminology authority project to coordinate w/ MnM
Follow-on from issues of HL7 harmonization in August w/ some Canadian content not being reviewed by the sponsored WG in a timely fashion.
- Proposal from Ted that Int'l committee working group approval not be required for affiliate-sponsored requirements
- Concern from Lloyd that Int'l committee engagement/review required
- Issue with some WGs stonewalling the process
- That's an issue with committee process - committee's should be expected to review proposals
Motion: Amend the existing harmonization process to include the following language -
- If the proponent believes that the WG review process is "stalled", they may bring the item forward to harmonization with documentation of the discussion thus far and the harmonization group may take a vote to consider the item not-withstanding the responsible WG's lack of final review. When this occurs, the harmonization group will note the issue of the stalled review process and forward the issue to the respective steering division.
Discussion about possibility of scheduling harmonization with two days 1 week apart to allow for review/discussion of changes requested at the first meeting.
- We already have multiple days where the second day tends to be scheduled for other things
- We need to communicate that key decision makers of affected committees must be available for discussions
We will routinely schedule the 4th day of harmonization for review of changes suggested at prior days of harmonization where the proponents felt additional consultation was required. Key decision makers will need to make themselves available for consultation during the period between initial harmonization discussions and this final review to avoid the proposal being rejected and deferred to the next cycle.
Propose that harmonization representation of eligible committees be a criteria for workgroup health. Will defer this to later as we need to figure out a process that will work for HQ.
Publishing a value set for a DEF or Criterion Act
- Essential challenge is "how do you constrain the potential answers to a question?"
- Don't send the value set - just enough information to retrieve the value set and/or expansion
- Consider conveying the value set assertion and possibly other attribute constraints (mandatory, cardinality, default, etc.)
- Concern that treating answer lists as value sets may be inappropriate.
- Lloyd will write up a proposal
Wednesday September 14 Q2
Wednesday September 14 Q3
Hosted by OO. Check their meetings
Wednesday September 14 Q4
Thursday September 15 Q2
Lloyd McKenzie (chair), Woody Beeler, Rob Hausam, Alexander Henket
Agenda SAIF Artifact Definitions & governance
Move approval of 8/19/2011 minutes - Beeler/Hausam 2-0-1
For information, walked through the SAIF Artifact List - noting its organization, then jumped to the Template and stepped through its sections and intent. The latter induced question and discussion.
No other actions.
Thursday September 15 Q5
Woody Beeler (Chair), Jean Duteau (Pharmacy), Ted Klein (Vocabulary), Rene Spronk (RIMBAA), Norman Daoust (PA), Wendy Huang (Vocabulary/PA), Andy Stechishin (ITS/Tooling), Michael Van Campen (visiting), Peter Hendler (visiting), Bob Dolin (SD), Rob (O&O), Hugh Glover (Medication), Julie James (Pharmacy Vocab), Mead Walker (RCRIM), Grahame Grieve (M&M), Lloyd McKenzie (M&M)
- Facilitators Roundtable
- Harmonization Details
- October 16 - Sunday - Initial Proposal Deadline
- October 20 - Thursday - QA Review
- November 6 - Sunday - Final Proposal
- November 15 - Tuesday - Primary
- November 16 - Wednesday - Patterns
- November 17 - Thursday - Extras
- November 18 - Friday - Revisit Session - to bring back proposals that needed changes
- There was a discussion about the Education Summit's dates being at the same time as the Harmonization. Since the Harmonization dates are dictated by the ballot which is dictated by the WGM dates, there is little that we can do with our dates. Unfortunately, the Ed Summit dates are dictated by HQ's booking and are set for the next 18-24 months. So the dates will be set as-is for the next while.
- CTS2 will be going forward as a normative standard
- Informed the group about the ongoing SNOMED use in HL7
- There will be a tooling effort towards a refinement of the OID Registry
- They will be a focus on training for vocabulary facilitators as there is a renewed interest in vocabulary.
- Working on the loose ends of bindings - documentation and education about bindings.
- Implementation Tooling will be on Tooling's agenda.
- For implementation tooling companies, there are some issues around MIF licensing.
- Managed RoleLink was brought up in previous WGMs. PA will be bringing forward a pattern to handle managed RoleLinks.
- Two harmonization proposals (Technical Corrections)
- ITS/Tooling/RIMBAA would like to make the Tuesday Q6 presentation in San Antonio an RFH roadshow - Motion was unanimously approved that MnM would co-sponsor this
- CDA R2.1 is being considered to expand the "right hand side" without changing the fundamental format of CDA
- Micro-biology Universal model was being worked on, primary brought forward by Canada, with the PSS intended for the models to be universal. There were some harmonization proposals brought forward from Canada but the group did not approve the proposals in time. That has resulted in the new harmonization process. There was a change that is reflected in the Harmonization wiki for an Affiliate Harmonization Proposal that deals with affiliates bringing new concept domains forward. (http://wiki.hl7.org/index.php?title=Vocabulary_and_RIM_Harmonization_Process)
- Six topics that will be republished and have gone Normative. Will be having an OOC meeting in Paris dealing with Institutional Use cases that is joint with IHE Pharmacy.
- Have agreed with SOA to provide content for one of their ongoing hData projects.
- Will be quite a lot of Harmonization proposals around CPM
- A RIM proposal to change the definition of containerCapAttribute
- ICSR went out to ISO balloting so the JIC project may be completed soon.
- Will be changing some of their previous DSTU messaging content to be CDA or Structured Document.
- RPS will be bringing forward some Concept Domain harmonization proposals.
- Reviewed the MnM quarters that occurred during the week
- Grahame made a presentation about RfH
Friday September 16 Q1
Lloyd McKenzie (chair), ean Duteau, Rene Spronk
- ParameterItem.semanticsText - Discussed the MnM Open Hot Topic - http://wiki.hl7.org/index.php?title=Harmonization:_turn_ParameterItem.semanticsText_into_a_mandatory_attribute. We agreed that semanticsText will be turned into a Mandatory CD. Jean will create the official Harmonization proposal and submit it, using the wiki content to provide the rationale.