This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

2016-07-01 PC CIMI POC Call Minutes

From HL7Wiki
Revision as of 13:47, 6 July 2016 by Jlyle (talk | contribs) (Created page with " <!-- LOOK FOR THE APPROPRIATE SECTION ****** TO ENTER INFORMATION--> Back to PC CIMI POC Minutes ==Minutes Template== ===Meeting Information=== {|border="1" cellpadding="...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Back to PC CIMI POC Minutes

Minutes Template

Meeting Information

HL7 PC-CIMI-POC Meeting Minutes

Location: HL7 WGM, Montreal

Date: 2016-07-01
Time: 9:00-10:30 ET
Facilitator Jay Lyle Note taker(s) Jay Lyle
Attendee Name Affiliation


y Richard Esmond PenRad
y Galen Mulrooney JP Systems
y Jay Lyle JP Systems / VA
Harold Solbrig Mayo
y Susan Matney Intermountain
y Joey Coyle Intermountain
Laura Heerman Langford Intermountain
y M'Lynda Owens Intermountain
y Stephen Hufnagel Intermountain

Agenda

Agenda Topics

  1. . Semantic binding: Three concepts (model, code, observable), Five candidate slots.
  2. . root bound to "observable," to "observable descendants," or left to node model?
  3. . Observable model gaps (e.g., "technique" vs "procedure")
  4. . ADL style

Minutes

Minutes/Conclusions Reached:

  1. The three bindings in play are distinct
    1. the observable concept
    2. the thing represented by the LOINC code
    3. the entire model
  2. The entire model is represented by the archetype id
    1. This makes a root node model binding unnecessary
    2. Though a question remains: what identifier or code is used to recognize isosemantic models? Perhaps a root node binding would be useful for that purpose.
  3. The "code" element (in an observation) is where a LOINC code goes
    1. "Code" is a type, so it's not very descriptive. Perhaps this could be renamed to something expressing "observed concept that might contain properties outside the observable model"
  4. We need a place to put an "observable entity" concept.
    1. Not the "code" model binding -- that should mean "code." Ditto "result" model binding.
    2. A new node: "Observable Result"
      1. A structure node that may have children
      2. Children have model bindings to SCT Observable model
      3. A different name might be good.
        1. It's not the result, it's the thing the result describes
        2. "Observable Result" is the name of a pattern archetype
  5. We'll bring this proposal to the general CIMI meeting.
    1. Loose end: if the LOINC code does completely express the observable, do we need to repeat it?

Meeting Outcomes

Actions
  • begin construction of test classes
Next Meeting/Preliminary Agenda Items
  • Review test class progress & tooling

© 2012 Health Level Seven® International. All rights reserved.