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

Difference between revisions of "2016-07-01 PC CIMI POC Call Minutes"

From HL7Wiki
Jump to navigation Jump to search
 
Line 109: Line 109:
  
 
'''Minutes/Conclusions Reached:'''<br/>
 
'''Minutes/Conclusions Reached:'''<br/>
# The three bindings in play are distinct
+
# terminology scope
## the observable concept
+
## physiological assessment of wound; not "pressure ulcer risk assessmment. Exclude adjacent but uncontrolled domains (medication, condition, device)
## the thing represented by the LOINC code
+
## items
## the entire model
+
### skin condition (coded questions)
# The entire model is represented by the archetype id
+
### Braden (ordinal, score)
## This makes a root node model binding unnecessary
+
### Ulcer existence (or negation)
## 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.
+
### Balance of wound model.
# The "code" element (in an observation) is where a LOINC code goes
+
# Assessment pattern
## "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"
+
## Complete assessment requirements before designing this
# We need a place to put an "observable entity" concept.
+
## Jay to draft, following the template used by Linda (lab) & Susan (procedure, condition)
## Not the "code" model binding -- that should mean "code." Ditto "result" model binding.
+
# root semantics
## A new node: "Observable Result"
+
## Jay to provide slides to main CIMI call
### A structure node that may have children
 
### Children have model bindings to SCT Observable model
 
### A different name might be good. 
 
#### It's not the result, it's the thing the result describes
 
#### "Observable Result" is the name of a pattern archetype
 
# We'll bring this proposal to the general CIMI meeting.
 
## Loose end: if the LOINC code does completely express the observable, do we need to repeat it?
 
  
 
===Meeting Outcomes===
 
===Meeting Outcomes===

Latest revision as of 13:52, 6 July 2016

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. review of terminology scope
  2. assessment pattern
  3. root semantics
  4. representing presence

Minutes

Minutes/Conclusions Reached:

  1. terminology scope
    1. physiological assessment of wound; not "pressure ulcer risk assessmment. Exclude adjacent but uncontrolled domains (medication, condition, device)
    2. items
      1. skin condition (coded questions)
      2. Braden (ordinal, score)
      3. Ulcer existence (or negation)
      4. Balance of wound model.
  2. Assessment pattern
    1. Complete assessment requirements before designing this
    2. Jay to draft, following the template used by Linda (lab) & Susan (procedure, condition)
  3. root semantics
    1. Jay to provide slides to main CIMI call

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.