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

Difference between revisions of "20160531 arb minutes"

From HL7Wiki
Jump to navigation Jump to search
m
 
(2 intermediate revisions by the same user not shown)
Line 38: Line 38:
 
|-
 
|-
 
| width="10%" colspan="1" align="right"|'''Facilitator'''
 
| width="10%" colspan="1" align="right"|'''Facilitator'''
| width="35%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]/[[User:Lconstab |Constable, Lorraine]]   
+
| width="35%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]  
 
| width="10%" colspan="1" align="right"|'''Note taker(s)'''
 
| width="10%" colspan="1" align="right"|'''Note taker(s)'''
| width="30%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]//[[User:Lconstab |Constable, Lorraine]]   
+
| width="30%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]  
 
|-
 
|-
 
| border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"|
 
| border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"|
Line 48: Line 48:
 
|colspan="2"|'''Affiliation'''  
 
|colspan="2"|'''Affiliation'''  
 
|-
 
|-
|.||Bond,Andy           
+
|X||Bond,Andy           
 
|colspan="2"|NEHTA
 
|colspan="2"|NEHTA
 
|-  
 
|-  
|.||[[User:Lconstab |Constable, Lorraine]]     
+
|X||[[User:Lconstab |Constable, Lorraine]]     
 
|colspan="2"|Constable Consulting Inc.
 
|colspan="2"|Constable Consulting Inc.
 
|-  
 
|-  
Line 63: Line 63:
 
|colspan="2"| AEGIS
 
|colspan="2"| AEGIS
 
|-
 
|-
|.||[[User:Ajulian | Julian, Tony]]       
+
|X||[[User:Ajulian | Julian, Tony]]       
 
|colspan="2"|Mayo Clinic
 
|colspan="2"|Mayo Clinic
 
|-  
 
|-  
|.||Knapp, Paul
+
|X||Knapp, Paul
 
|colspan="2"| Pknapp Consulting
 
|colspan="2"| Pknapp Consulting
 
|-  
 
|-  
|.||Kubick, Wayne
+
|X||Kubick, Wayne
 
|colspan="2"|HL7 CTO
 
|colspan="2"|HL7 CTO
 
|-
 
|-
Line 75: Line 75:
 
|colspan="2"| ICode Solutions
 
|colspan="2"| ICode Solutions
 
|-  
 
|-  
|.||[[User:Clynchmd | Lynch, Cecil]]       
+
|X||[[User:Clynchmd | Lynch, Cecil]]       
 
|colspan="2"|Accenture
 
|colspan="2"|Accenture
 
|-  
 
|-  
|.||Milosevic, Zoran
+
|X||Milosevic, Zoran
 
|colspan="2"|Deontik Pty Ltd
 
|colspan="2"|Deontik Pty Ltd
 
|-
 
|-
|.||Quinn, John       
+
|X||[[User:Astechishin| Stechishin,Andy]]
|colspan="2"|HL7 CTO Emeritus
 
|-
 
|.||[[User:Astechishin| Stechishin,Andy]]
 
 
|colspan="2"|CANA Software and Service Ltd.
 
|colspan="2"|CANA Software and Service Ltd.
 
|-
 
|-
Line 116: Line 113:
  
 
==Minutes==
 
==Minutes==
#**Lorraine:'''Motion''' ARB be co-sponsor of the project, with periodic reports on progress what they are doing and where they are going(Lorraine/Paul).
+
#Approval of Agenda and [[2016_ARB_Montreal_WGM | WGM Minutes]]
 +
#*'''Motion to approve''' (Lorraine/ Paul)
 +
#*'''Vote''' 7-0-0 
 +
#Governance
 +
#Methodology (60 minutes)
 +
#*[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FHL7%2520Project%2520Scope%2520Statement%2520v2015.1_CIMI_POC_d20160511.docx CIMI Proof of concept]
 +
#**Is this a new product? Family? Where does it fit?
 +
#**Lorraine: Using existing CIMI models - trying to map to Patient Care DAM, and how they would fit in the models.  Providing direction on modeling, and relation across out standards.
 +
#**Cecil: It is new - and it lack definition.  Assume 'existing clinical requirements' : they dont say the requirements are the same. Guess they are from the V3 DAM.  New ? models:  If CIMI models they are a new product.
 +
#**Paul: Output is models.
 +
#**Wayne: Applied to any of the standards.
 +
#**Lorraine: Generate FHIR profiles.
 +
#**Paul: Not a different product
 +
#**Lorraine: I went to the CIMI CQI project:
 +
#**Cecil: How much of the EHR is ported to CIMI?
 +
#**Lorraine: modeling to QICORE.  Orthogonal to the rest of HL7 model. Suggest tht threads be gathered and coordinated.
 +
#**Cecil: It is not new if it is a singular model, different if it crosses product families.
 +
#**Paul: Not a new thing: Isnt the DAM across families?
 +
#**Lorraine: Yes - one just finished ballot.
 +
#**Paul: DAMS across families
 +
#**Wayne:  In Section 4 it appears that this would be logical models.
 +
#**Andy B:  There are fundamental different reference models from openehr.  FHIR is a different model.  The importance is the relationship to the DAMs.  It is now HL7 work.  What is the thread that brings the models under the HL7 Banner.  It comes from a different modeling universe.  FHIR is in an HL7 universe.  It is a new variety of HL7 Model.  The trick is to create legitimization, create Governance and consistency to bring it together.
 +
#**Paul: More conceptual or concrete
 +
#**Zoran: More concrete.
 +
#**Paul: Can it be rendered into a family? Is it process for model, or rendering into content? How can these artifacts be rendered into families? Can we do so algorithmically?
 +
#**Lorraine: Another project generating FHIR profiles - rule based, automatable
 +
#**Paul:  Elements mapped to FHIR models, consistency of meaning? Coming up with the models.
 +
#**Lorraine: Relating models to DAMS, another project generating concrete content.  Should we be involved for consistency? What is our position?
 +
#**Paul: CIMI model definition or statement of ownership?
 +
#**Wayne: Just a model - can be rendered in any family. 
 +
#**Cecil: I can render FHIR in multiple ways, but its still FHIR. Purpose to have decision support models.
 +
#**Wayne: I hadnt heard of decision support.
 +
#**Lorraine: They are working with CQI.  Should we be involved, or let it run on its own.
 +
#**Paul: Makes sense to observe - it might go off into its own space unnecessarily.
 +
#**Lorraine: ARB monitor for coherence.
 +
#**Wayne: Invite CIMI to a meeting.
 +
#**'''Motion''' ARB be co-sponsor of the project, with periodic reports on progress what they are doing and where they are going.
 +
#**Zoran: On this PSS only?  Need to clarify bullet point "Demonstrate relationship between information models and logically computable expressions"
 +
#**'''Motion to table'''  (Paul/Lorraine)
 +
#**'''Vote''' 7-0-0 
 +
#** Tony will invite CIMI representatives to the next call.  
 +
#*SAIF super light
 +
#**We are asked to prepare an explanation of the ISM, and how to use it
 +
#**Lorraine: We have material, but not consumable by others?
 +
#**Lorraine will dig through what we have, and find the gaps!.
 +
#**Zoran: In doing so you will leverage your experience with ODL.
 +
#**Zoran will help.
 +
#Other business and planning
 +
##Finish Substantivity
 +
## Finish withdrawal with PIC
 +
## CIMI
 +
##* Engage with Grahame on CIMI on FHIR
 +
##* Engage Harold, Stan, or Jay on CIMI
 +
##* Evaluate CIMI architecture
 +
#Adjournment
 +
 
  
  
 
[[Category:2016 Arb Minutes]]
 
[[Category:2016 Arb Minutes]]

Latest revision as of 19:52, 7 June 2016

ARB - Meeting (Date in Title)

logistics

Teleconferences are held on Tuesday at 4:00pm U.S. Eastern Schedules may be found at HL7.org Conference Call Center


Please join my meeting from your computer, tablet or smartphone.

  1. Join the meeting:
  2. If you cant use voip then capture the PIN from the screen for the above action, then
  • Weekly conference call.
  • For 24/7 customer service please call (844) 844-1322.

Agenda

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and WGM Minutes
  4. Governance
  5. Methodology (60 minutes)
    • CIMI Proof of concept
      • Is this a new product? Family? Where does it fit?
    • SAIF super light
      • We are asked to prepare an explanation of the ISM, and how to use it
  1. Other business and planning
    • Conformance Testing for ONC
  2. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20160531
Time: 4:00pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
. Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve ?????
. Hyland, Mario AEGIS
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
X Kubick, Wayne HL7 CTO
. Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
X Milosevic, Zoran Deontik Pty Ltd
X Stechishin,Andy CANA Software and Service Ltd.
Guests
. Nelson, Dale Accenture
. Grow, Richard U.S. Department of Veterans affairs
.
Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes

Minutes

  1. Approval of Agenda and WGM Minutes
    • Motion to approve (Lorraine/ Paul)
    • Vote 7-0-0
  2. Governance
  3. Methodology (60 minutes)
    • CIMI Proof of concept
      • Is this a new product? Family? Where does it fit?
      • Lorraine: Using existing CIMI models - trying to map to Patient Care DAM, and how they would fit in the models. Providing direction on modeling, and relation across out standards.
      • Cecil: It is new - and it lack definition. Assume 'existing clinical requirements' : they dont say the requirements are the same. Guess they are from the V3 DAM. New ? models: If CIMI models they are a new product.
      • Paul: Output is models.
      • Wayne: Applied to any of the standards.
      • Lorraine: Generate FHIR profiles.
      • Paul: Not a different product
      • Lorraine: I went to the CIMI CQI project:
      • Cecil: How much of the EHR is ported to CIMI?
      • Lorraine: modeling to QICORE. Orthogonal to the rest of HL7 model. Suggest tht threads be gathered and coordinated.
      • Cecil: It is not new if it is a singular model, different if it crosses product families.
      • Paul: Not a new thing: Isnt the DAM across families?
      • Lorraine: Yes - one just finished ballot.
      • Paul: DAMS across families
      • Wayne: In Section 4 it appears that this would be logical models.
      • Andy B: There are fundamental different reference models from openehr. FHIR is a different model. The importance is the relationship to the DAMs. It is now HL7 work. What is the thread that brings the models under the HL7 Banner. It comes from a different modeling universe. FHIR is in an HL7 universe. It is a new variety of HL7 Model. The trick is to create legitimization, create Governance and consistency to bring it together.
      • Paul: More conceptual or concrete
      • Zoran: More concrete.
      • Paul: Can it be rendered into a family? Is it process for model, or rendering into content? How can these artifacts be rendered into families? Can we do so algorithmically?
      • Lorraine: Another project generating FHIR profiles - rule based, automatable
      • Paul: Elements mapped to FHIR models, consistency of meaning? Coming up with the models.
      • Lorraine: Relating models to DAMS, another project generating concrete content. Should we be involved for consistency? What is our position?
      • Paul: CIMI model definition or statement of ownership?
      • Wayne: Just a model - can be rendered in any family.
      • Cecil: I can render FHIR in multiple ways, but its still FHIR. Purpose to have decision support models.
      • Wayne: I hadnt heard of decision support.
      • Lorraine: They are working with CQI. Should we be involved, or let it run on its own.
      • Paul: Makes sense to observe - it might go off into its own space unnecessarily.
      • Lorraine: ARB monitor for coherence.
      • Wayne: Invite CIMI to a meeting.
      • Motion ARB be co-sponsor of the project, with periodic reports on progress what they are doing and where they are going.
      • Zoran: On this PSS only? Need to clarify bullet point "Demonstrate relationship between information models and logically computable expressions"
      • Motion to table (Paul/Lorraine)
      • Vote 7-0-0
      • Tony will invite CIMI representatives to the next call.
    • SAIF super light
      • We are asked to prepare an explanation of the ISM, and how to use it
      • Lorraine: We have material, but not consumable by others?
      • Lorraine will dig through what we have, and find the gaps!.
      • Zoran: In doing so you will leverage your experience with ODL.
      • Zoran will help.
  4. Other business and planning
    1. Finish Substantivity
    2. Finish withdrawal with PIC
    3. CIMI
      • Engage with Grahame on CIMI on FHIR
      • Engage Harold, Stan, or Jay on CIMI
      • Evaluate CIMI architecture
  5. Adjournment