20170606 arb minutes

From HL7Wiki
Revision as of 20:13, 12 July 2017 by Ajulian (talk | contribs) (→‎Meeting Information)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

ARB - Meeting (Date in Title)

Agenda

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and May 30, 2017 Minutes
  4. Management
  5. Governance
  6. Methodology
    • Joint with SGB to discuss Interoperability Specification Matrix (ISM)
  7. Other business and planning
    • June 13 Continue Ballot Recon
    • June 20 Review Mission and Charter
    • Open issues
  8. Adjournment

Meeting Information

HL7 ARB Work Group Meeting Minutes

Location: Telcon

Date: 20160606
Time: 4:00pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
R Constable, Lorraine Constable Consulting Inc.
. 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
R Milosevic, Zoran Deontik Pty Ltd
X Stechishin,Andy CANA Software and Service Ltd.
SGB
. Kreisler, Austin Leidos
. Hamm, Russ IMO
.
Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes
  1. Approval of Agenda and May 30, 2017 Minutes
      • Agenda approved by mutual consent
    • Motion to approve the minuts(Andy S/ Austin)
    • Vote 4-0-0
  2. Methodology
    • Joint with SGB to discuss Interoperability Specification Matrix (ISM)
      • Tony presented the ISM diagram
      • Discussed task - Provide guidance to groups to map their artifacts to the ISM.
      • Depends on the work: If oriented for family instead of line. Line interested in logical models, Family interested in implementation..
      • Platform oriented see logical modeling as overhead with little value.
      • Product line has an interest in logical consistency within the line.
      • Across HL7 there is a higher order - of which Family/Lines don't concern themselves.
      • FHIR model is an abstraction, and is not implementable. From the outside you see it as core to FHIR, in implementable view.
      • Value depends on your perspective, e.g. FHIR, CDA, V2.
      • SGB is interested in the cross product family consistency, working through product families.
      • SGB is concerned with lines that need consistency.
      • Don't see those as lines - good things to do in order to have lines.
      • Looking at a domain, what is the binding conceptual foundation, so talked about together they wont create inconsistencies. CDA, FHIR see it as an inhibitor, decided by others.
      • Target audience - Product Families? families articulate their material into the grid.
      • Narrows the focus to immediate future.
      • Helps to surface what is hard.
      • Challenge is for domains - this is the issue they deal with, different product families across the domain. For a family the core interest is the implementation - technical platform has been chosen. You can grow the interest with e.g. FHIR which needs to work with other platforms. Need to reconcile a set of behaviors.
      • If the logical model is FHIR, we will take out the platform bits, and just have the information elements.
      • This group needs to map one and map it, but not FHIR.
      • There was a CDA exercise to do that. (Keith Boone facilitated).
      • Worked on PPT.
      • Next week put into the grid - may find a home, add examples, friendlier names.
  3. Other business and planning
    • June 13 Continue Ballot Recon
    • June 20 Review Mission and Charter
    • Open issues
      • Tony will send to Anne, for SGB consumption.
      • Schedule monthly
  4. Adjournment