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

Difference between revisions of "2017 ARB SanAntonio WGM"

From HL7Wiki
Jump to navigation Jump to search
m
 
(31 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
==Sunday Q3 with SGB==
 
==Sunday Q3 with SGB==
−
*ISM _ Interoperability Specification Matrix
+
*[http://wiki.hl7.org/index.php?title=2017-01-15_SGB_WGM_Agenda January 15, 2017 SGB/ARB Agenda]
  
 
==Sunday Q5 with TSC==
 
==Sunday Q5 with TSC==
−
*TBD
+
*[http://tscwiki.hl7.org/wiki/index.php?title=2017-01-15_TSC_WGM_Agenda January 15, 2017 TSC Sunday Evening Meeting]
  
−
==Monday Q2==
+
=== Monday Q2 ===
 
#Maverick A
 
#Maverick A
−
[[v3_support_discussion | V3 Support Discussion]]
+
#*[[v3_support_discussion | V3 Support Discussion]] ARB Joint with interested parties:
−
*Tentative: Joint with interested parties:
 
−
**what v3 artifacts do we care about (RIM? Vocabulary? Datatypes? Core Principles?)
 
−
**what energy do we have to work on them, both within the workgroup and organizationally
 
−
**how do we support existing Normative and STU v3 artifacts
 
−
**how do we support any future balloted v3 artifacts
 
  
 
===Thursday Q3===
 
===Thursday Q3===
−
#*Planning based on Monday Q2 V3 Discussion  
+
#[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FHL7%2520Project%2520Scope%2520Statement%2520v2016_OO_LOI_NDBS_20161222.doc PSS for LOI]
−
#*Things that came up this week.
+
#Planning based on Monday Q2 V3 Discussion  
 +
#Things that came up this week.
 
#Other business and planning
 
#Other business and planning
 
#*[http://gforge.hl7.org/gf/project/arbgeneral/tracker/?action=TrackerItemBrowse&tracker_id=871 Open issues]
 
#*[http://gforge.hl7.org/gf/project/arbgeneral/tracker/?action=TrackerItemBrowse&tracker_id=871 Open issues]
Line 26: Line 22:
  
 
==Minutes==
 
==Minutes==
−
__NOTOC__<!--
 
  
−
EDITORS:
+
==Meeting Information Monday Q2==
−
1) To prepare the AGENDA, simply complete the prior minute approval line and
 
−
  then add any items you wish in the agenda.
 
−
 
 
−
2) To Post the MINUTES, DELETE the {{:ARB Logistics}} below.
 
−
  This will drop the meeting logistics and list of work Groups from the minutes.
 
−
 
 
−
3) Change YYYYMMDD in the following sections to the correct YYYYMMDD
 
−
  A) In the AGENDA section change YYYYMMDD_arb_minutes | Minutes
 
−
  B) In the Meeting Information Section change '''Date: YYYYMMDD'''
 
−
Now, save it!
 
−
 
 
−
-->
 
−
=ARB - Meeting (Date in Title)=
 
−
#Other business and planning
 
−
#*[http://gforge.hl7.org/gf/project/arbgeneral/tracker/?action=TrackerItemBrowse&tracker_id=871 Open issues]
 
−
#Adjournment
 
−
 
 
−
==Meeting Information==
 
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
−
| width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 ArB Work Group   Meeting Minutes''' <br/>
+
| width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 ArB/MnM Work Group Meeting Minutes''' <br/>
−
'''Location:  [[spring_ARB_Logistics| Telcon]]'''
+
'''Location:  Maverick-A, Hyatt Riverwalk, San Antonio, TX, US'''
−
| width="50%" colspan="3" align="left" style="background:#f0f0f0;"|'''Date: CCYYMMDD'''<br/> '''Time: 3:00pm U.S. Eastern'''
+
| width="50%" colspan="3" align="left" style="background:#f0f0f0;"|'''Date: 20170116'''<br/> '''Time: 11:00am U.S. Eastern'''
 
|-
 
|-
 
| 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"|[[Duteau, Jean]]/[[User:Lconstab |Constable, Lorraine]]     
 
| 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 63: Line 40:
 
|colspan="2"|'''Affiliation'''  
 
|colspan="2"|'''Affiliation'''  
 
|-
 
|-
−
|.||Bond,Andy           
+
|R||Bond,Andy           
 
|colspan="2"|NEHTA
 
|colspan="2"|NEHTA
 
|-  
 
|-  
Line 87: Line 64:
 
|colspan="2"|Accenture
 
|colspan="2"|Accenture
 
|-  
 
|-  
−
|.||Milosevic, Zoran
+
|R||Milosevic, Zoran
 
|colspan="2"|Deontik Pty Ltd
 
|colspan="2"|Deontik Pty Ltd
 
|-
 
|-
−
|.||[[User:Astechishin| Stechishin,Andy]]
+
|R||[[User:Astechishin| Stechishin,Andy]]
 
|colspan="2"|CANA Software and Service Ltd.
 
|colspan="2"|CANA Software and Service Ltd.
 
|-
 
|-
Line 121: Line 98:
 
|}
 
|}
  
−
==Minutes==
+
==Minutes Monday Q2==
−
 
+
#Call to Order
 +
#Future of V3 in HL7 - Jean Duteau
 +
#*Jean introduced the topic.
 +
#*Review Thursday Q5
 +
#*Jean will send a report to Wayne Kubrick & Ken McCaslin
 +
#*Statement of Problem
 +
#**Number of v3 artifacts being balloted is significantly reducint
 +
#***Modeling landscape has changed
 +
#***Huge focus on FHIR
 +
#***ONC has adopted C-CDA as a standard for exchange
 +
#**Expert V3 knowledge will diminish over time
 +
#**Tooling has external outdated technology dependencies, supported by volunteers
 +
#**M&M is struggling to support the foundation
 +
#*Catalog of artifacts
 +
#**Current STU
 +
#***Specifications
 +
#***Implementation guides e.g. terminfo
 +
#***Standards
 +
#**Current Balloted
 +
#***Standards
 +
#***DAMS
 +
#***Implementation guides
 +
#**Tooling artifacts
 +
#***RMIM Designer (Dale says 2013 works)
 +
#***Rosetree
 +
#***V3 PubDb Access Based
 +
#***V3 Generator - ANT/XSLT
 +
#***V3 Publishing
 +
#*Support Requirements
 +
#**Foundational Artifacts
 +
#***RIM
 +
#***Datatypes
 +
#***Vocabulary
 +
#***Core principles R2 balloted but in limbo, R3 started, but stopped do to lack of volunteers
 +
#****MIF based
 +
#****PC is looking at changes to negation indicators
 +
#***MIF Changes - EST can support
 +
#***V3 Tooling
 +
#****RMIM Designer - relies on Visio(dale says 2013 works)
 +
#****Rosetree
 +
#***V3 PubDb Access Based
 +
#***V3 Generator - ANT/XSLT
 +
#****Bound together with twine and duct-tape
 +
#***V3 Publishing - needed to build ballot, STU and Normative V3 domains
 +
#**Risk Areas:
 +
#**#What if a RIM structure change was requested?
 +
#**#Change RIM UML
 +
#**#Update RIM Core Mifs
 +
#**Support for Normative and STU standards.
 +
#***Published and support needs are minimal
 +
#***Ned to keep Foundational artifacts as Normative, e.e Extensions and re-affirmations as required
 +
#****Questions
 +
#****#Do any non-foundational Standards need updates?
 +
#****#*CDA and Common Product model need updates
 +
#****#RIM Normative Edition Balloting - how often do these need to happen?
 +
#****Hugh- to what extent do we need to keep normative.  Do we need to do reaffirmation?
 +
#****Wayne - we plan to remove the ANSI logo
 +
#****Mead - need to know what is being used.  The users may want changes to content.
 +
#****Paul - may need updates to new needs.
 +
#****Jean - need to know what is in use.  Reaffirmation is trivial.
 +
#*Communication
 +
#** Realistic Status -
 +
#** Restrict communication to modelling
 +
#** As support of tools and ballots goes, so goes support of V3 modelling
 +
#** Is there a need to push the onus on producing material out to the organizations creating it, with minimal HL7 International support?
 +
#** How do we frame the message - i.e. this isn't the death of V3, and not FHIR vs V3.
 +
===What do we need to do===
 +
#* Develop a list of known 'keepers'
 +
#* Develop a list of standards in use?
 +
#** Include affiliates
 +
#* Expose artifacts and dependencies
 +
#* Which artifacts do we need MIF? UML? HMD?
 +
#* Develop a plan to reaffirm or withdraw
 +
#** Withdraw means still a standard, but just not ANSI accredited
  
 +
==Meeting Information  Thursday Q3==
 +
{|border="1" cellpadding="2" cellspacing="0"
 +
| width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 ArB Work Group  Meeting Minutes''' <br/>
 +
'''Location:  Garden Terrace #135, Hyatt Riverwalk, San Antonio, TX, US'''
 +
| width="50%" colspan="3" align="left" style="background:#f0f0f0;"|'''Date: 20170119'''<br/> '''Time: 3:00pm U.S. Eastern'''
 +
|-
 +
| width="10%" colspan="1" align="right"|'''Facilitator'''
 +
| width="35%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]
 +
| width="10%" colspan="1" align="right"|'''Note taker(s)'''
 +
| width="30%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]]
 +
|-
 +
| border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"|
 +
|-
 +
| border="1" cellpadding="2" colspan="1" align="left"|'''Attendee'''
 +
| '''Name'''
 +
|colspan="2"|'''Affiliation'''
 +
|-
 +
|R||Bond,Andy         
 +
|colspan="2"|NEHTA
 +
|-
 +
|X||[[User:Lconstab |Constable, Lorraine]]   
 +
|colspan="2"|Constable Consulting Inc.
 +
|-
 +
|X||[[User:Interopguy | Hyland, Mario]]
 +
|colspan="2"| AEGIS
 +
|-
 +
|X||[[User:Ajulian | Julian, Tony]]     
 +
|colspan="2"|Mayo Clinic
 +
|-
 +
|X||Knapp, Paul
 +
|colspan="2"| Pknapp Consulting
 +
|-
 +
|.||Kubick, Wayne
 +
|colspan="2"|HL7 CTO
 +
|-
 +
|X||[[User:Ployd|Loyd, Patrick ]]
 +
|colspan="2"| ICode Solutions
 +
|-
 +
|R||[[User:Clynchmd | Lynch, Cecil]]     
 +
|colspan="2"|Accenture
 +
|-
 +
|R||Milosevic, Zoran
 +
|colspan="2"|Deontik Pty Ltd
 +
|-
 +
|R||[[User:Astechishin| Stechishin,Andy]]
 +
|colspan="2"|CANA Software and Service Ltd.
 +
|-
 +
|colspan="4" align="center"|Guests           
 +
|-
 +
|X|| Shakir, Abdul-Malik
 +
|colspan="2"| HI3
 +
|-
 +
|X|| Duteau, Jean
 +
|colspan="2"| DDI
 +
|-
 +
|X|| McDaniel, MaryKay
 +
|colspan="2"| Cognosante, LLC
 +
|-
 +
|X|| Murphy, Erin
 +
|colspan="2"| Cognosante, LLC
 +
|-
 +
|X|| Baker, J.D.
 +
|colspan="2"| Sparx Systems
 +
|-
 +
|X||Walker, D. Mead
 +
|colspan="2"|Mead Walker Consulting
 +
|-
 +
|.||
 +
|colspan="2"|
 +
|-
 +
|colspan="4" align="center" style="background:#f0f0f0;"|Legend           
 +
|-
 +
|X||Present
 +
|colspan="2"|
 +
|-
 +
|.||Absent
 +
|colspan="2"|
 +
|-
 +
|R||Regrets
 +
|colspan="2"|
 +
|-
 +
|colspan="4" style="background:#f0f0f0;"|
 +
|-
 +
|colspan="4" |'''Quorum Requirements (Co-chair + 3) Met: '''Yes
 +
|-
 +
|}
  
 +
==Minutes Thursday Q3==
 +
#Methodology
 +
#*Motion to approve pss for (Newborn Dried Blood Spot Screening Lab Order Component/ Implementation Guide) (Patrick/Lorraine) 3-0-0
 +
#*Motion to make meeting joint with MnM (Lorraine/Patrick)3- 0-0
 +
#*V3 discussion
 +
#**What is 'V3'?
 +
#***V3 messaging is RIM, DAMS, etc.
 +
#***CDA is NOT V3 messaging, but based on RIM.
 +
#**MnM Will do inventory of v3 products.
 +
#***Withdraw unused/old content
 +
#**What does it mean to publish a new V3 Domain?
 +
#***Weak link is tooling.
 +
#***Can refactor what it means.
 +
#**We need to identify the customers for V3.
 +
#**Focus on information gathering.
 +
#**Tooling/Publishing of Lists/tools
 +
#**Methodology needs revisiting - lessons from CDA and FHIR.
 +
#***Why change the methodology?
 +
#****Identify common things.
 +
#****Each model has its own schema.
 +
#***Lesson from CDA starts with constrained model. - CDA is being misused.
 +
#***Are customers asking for a single schema.
 +
#**Flaws in Methodology cause lack of new development
 +
#**Sequoia/NHIN, SPL, Adverse event are using V3.
 +
#**Static schemas were good
 +
#**Connectathons are good.
 +
#**Choice in schemas is good.
 +
#**RIM ITS is a single schema.
 +
#*Library activities
 +
#*#List of artifacts from Lynn
 +
#*#Which are the ones we care about (v3 Family)
 +
#*#Ask workgroups for which we can withdraw/maintain.
 +
#*#Determine the tooling requirements
 +
#*#Determine alternative tools for essential artifacts.
 +
#*#*Consider outsourcing - let 3rd party derive schemas.
 +
#*#Why do we have 4 sets of data-types.
 +
#*#*Can we fix it - organizational will.
 +
#*#Conformance should be the same.
 +
#Meeting Schedules
 +
#*Madrid WGM
 +
#**ARB/SGB Sunday Q3
 +
#**Mon Q2 ARB only - Impromptu joint if appropriate.
 +
#**THU Q3 ARB only
 +
#*Weekly conference calls
 +
#**Continue 3:00 Eastern starting on 1/31/2017.
 +
===Todos===
 +
*Lorraine has notified Riki of ARB Approval
 +
*Mario will try to find the missing content from http://wiki.hl7.org/index.php?title=SAIF_Artifact_Definition_Project
 +
*MnM will look at those mapping from V3 into FHIR with problems with data-type variations.
 
[[Category:2016 Arb Minutes]][[Category:2017 Arb Minutes]]
 
[[Category:2016 Arb Minutes]][[Category:2017 Arb Minutes]]

Latest revision as of 22:34, 19 January 2017

2017 January WGM SanAntonio

Sunday Q3 with SGB

Sunday Q5 with TSC

Monday Q2

  1. Maverick A

Thursday Q3

  1. PSS for LOI
  2. Planning based on Monday Q2 V3 Discussion
  3. Things that came up this week.
  4. Other business and planning
    • Open issues
    • Agenda until next WGM.
    • When do we meet next WGM?
  5. Adjournment

Minutes

Meeting Information Monday Q2

HL7 ArB/MnM Work Group Meeting Minutes

Location: Maverick-A, Hyatt Riverwalk, San Antonio, TX, US

Date: 20170116
Time: 11:00am U.S. Eastern
Facilitator Duteau, Jean/Constable, Lorraine Note taker(s) Julian, Tony
Attendee Name Affiliation
R Bond,Andy NEHTA
. Constable, Lorraine Constable Consulting Inc.
. Hyland, Mario AEGIS
. Julian, Tony Mayo Clinic
. Knapp, Paul Pknapp Consulting
. Kubick, Wayne HL7 CTO
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
R Milosevic, Zoran Deontik Pty Ltd
R 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 Monday Q2

  1. Call to Order
  2. Future of V3 in HL7 - Jean Duteau
    • Jean introduced the topic.
    • Review Thursday Q5
    • Jean will send a report to Wayne Kubrick & Ken McCaslin
    • Statement of Problem
      • Number of v3 artifacts being balloted is significantly reducint
        • Modeling landscape has changed
        • Huge focus on FHIR
        • ONC has adopted C-CDA as a standard for exchange
      • Expert V3 knowledge will diminish over time
      • Tooling has external outdated technology dependencies, supported by volunteers
      • M&M is struggling to support the foundation
    • Catalog of artifacts
      • Current STU
        • Specifications
        • Implementation guides e.g. terminfo
        • Standards
      • Current Balloted
        • Standards
        • DAMS
        • Implementation guides
      • Tooling artifacts
        • RMIM Designer (Dale says 2013 works)
        • Rosetree
        • V3 PubDb Access Based
        • V3 Generator - ANT/XSLT
        • V3 Publishing
    • Support Requirements
      • Foundational Artifacts
        • RIM
        • Datatypes
        • Vocabulary
        • Core principles R2 balloted but in limbo, R3 started, but stopped do to lack of volunteers
          • MIF based
          • PC is looking at changes to negation indicators
        • MIF Changes - EST can support
        • V3 Tooling
          • RMIM Designer - relies on Visio(dale says 2013 works)
          • Rosetree
        • V3 PubDb Access Based
        • V3 Generator - ANT/XSLT
          • Bound together with twine and duct-tape
        • V3 Publishing - needed to build ballot, STU and Normative V3 domains
      • Risk Areas:
        1. What if a RIM structure change was requested?
        2. Change RIM UML
        3. Update RIM Core Mifs
      • Support for Normative and STU standards.
        • Published and support needs are minimal
        • Ned to keep Foundational artifacts as Normative, e.e Extensions and re-affirmations as required
          • Questions
            1. Do any non-foundational Standards need updates?
              • CDA and Common Product model need updates
            2. RIM Normative Edition Balloting - how often do these need to happen?
          • Hugh- to what extent do we need to keep normative. Do we need to do reaffirmation?
          • Wayne - we plan to remove the ANSI logo
          • Mead - need to know what is being used. The users may want changes to content.
          • Paul - may need updates to new needs.
          • Jean - need to know what is in use. Reaffirmation is trivial.
    • Communication
      • Realistic Status -
      • Restrict communication to modelling
      • As support of tools and ballots goes, so goes support of V3 modelling
      • Is there a need to push the onus on producing material out to the organizations creating it, with minimal HL7 International support?
      • How do we frame the message - i.e. this isn't the death of V3, and not FHIR vs V3.

What do we need to do

    • Develop a list of known 'keepers'
    • Develop a list of standards in use?
      • Include affiliates
    • Expose artifacts and dependencies
    • Which artifacts do we need MIF? UML? HMD?
    • Develop a plan to reaffirm or withdraw
      • Withdraw means still a standard, but just not ANSI accredited

Meeting Information Thursday Q3

HL7 ArB Work Group Meeting Minutes

Location: Garden Terrace #135, Hyatt Riverwalk, San Antonio, TX, US

Date: 20170119
Time: 3:00pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
R Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
X Hyland, Mario AEGIS
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
. Kubick, Wayne HL7 CTO
X Loyd, Patrick ICode Solutions
R Lynch, Cecil Accenture
R Milosevic, Zoran Deontik Pty Ltd
R Stechishin,Andy CANA Software and Service Ltd.
Guests
X Shakir, Abdul-Malik HI3
X Duteau, Jean DDI
X McDaniel, MaryKay Cognosante, LLC
X Murphy, Erin Cognosante, LLC
X Baker, J.D. Sparx Systems
X Walker, D. Mead Mead Walker Consulting
.
Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes

Minutes Thursday Q3

  1. Methodology
    • Motion to approve pss for (Newborn Dried Blood Spot Screening Lab Order Component/ Implementation Guide) (Patrick/Lorraine) 3-0-0
    • Motion to make meeting joint with MnM (Lorraine/Patrick)3- 0-0
    • V3 discussion
      • What is 'V3'?
        • V3 messaging is RIM, DAMS, etc.
        • CDA is NOT V3 messaging, but based on RIM.
      • MnM Will do inventory of v3 products.
        • Withdraw unused/old content
      • What does it mean to publish a new V3 Domain?
        • Weak link is tooling.
        • Can refactor what it means.
      • We need to identify the customers for V3.
      • Focus on information gathering.
      • Tooling/Publishing of Lists/tools
      • Methodology needs revisiting - lessons from CDA and FHIR.
        • Why change the methodology?
          • Identify common things.
          • Each model has its own schema.
        • Lesson from CDA starts with constrained model. - CDA is being misused.
        • Are customers asking for a single schema.
      • Flaws in Methodology cause lack of new development
      • Sequoia/NHIN, SPL, Adverse event are using V3.
      • Static schemas were good
      • Connectathons are good.
      • Choice in schemas is good.
      • RIM ITS is a single schema.
    • Library activities
      1. List of artifacts from Lynn
      2. Which are the ones we care about (v3 Family)
      3. Ask workgroups for which we can withdraw/maintain.
      4. Determine the tooling requirements
      5. Determine alternative tools for essential artifacts.
        • Consider outsourcing - let 3rd party derive schemas.
      6. Why do we have 4 sets of data-types.
        • Can we fix it - organizational will.
      7. Conformance should be the same.
  2. Meeting Schedules
    • Madrid WGM
      • ARB/SGB Sunday Q3
      • Mon Q2 ARB only - Impromptu joint if appropriate.
      • THU Q3 ARB only
    • Weekly conference calls
      • Continue 3:00 Eastern starting on 1/31/2017.

Todos

Retrieved from "https://wiki.hl7.org/w/index.php?title=2017_ARB_SanAntonio_WGM&oldid=131931"