20170321 arb minutes

From HL7Wiki
Jump to navigation Jump to search

ARB - Meeting (Date in Title)

Agenda

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and Minutes
  4. Management
  5. Governance
  6. Methodology
    • TSC TASKs:
      1. At March 20, 2017 TSC, Wayne asked that we review the available product types as represented in the GOM, and define them. Specifically he was asking what is a Functional Model (since a Service Functional Model has been proposed as something different).
      2. He also asked ARB to compare to the values for Type in the Standards Master Grid, which doesn’t match the GOM values at all.
      3. Canonical DAM Line 190: A DAM is an example of a product family. - ARB will need to expound on this - it does not make sense, specially since a DAM is not in the product matrix.
        • The “Family” pull-down list of values includes things like v2, v3, CDA and FHIR, not categories of artifacts like DAMs. That’s why the statement in the canonical DAM confusing and inconsistent. It may be correct in the eyes of some, but it may seem confusing to others.
  7. Other business and planning
  8. Adjournment

Meeting Information

HL7 ARB Work Group Meeting Minutes

Location: Telcon

Date: 20170321
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.
X Hyland, Mario AEGIS
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
R Kubick, Wayne HL7 CTO
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
. 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. Management
    • Approval of Agenda and Minutes
      • Agenda and Minutes approved via general consent.
  2. Methodology
    • TSC TASKs: At March 20, 2017 TSC, Wayne asked that we review the available product types as represented in the GOM, and define them. Specifically he was asking what is a Functional Model (since a Service Functional Model has been proposed as something different).
      1. Master Grid: Type is actually Product Type:
      2. Paul: pull out of the GOM, and add the missing Families
      3. Paul: Need the list outside of the GOM of Families and types.
      4. Paul: Permalink to family, subfamily, Type.
      5. Paul: Add to SGB precepts? Is the outcome worth the spend?
      6. Paul: What is the confusion? We have conceptual Families and implementable Families.
      7. Lorraine: Family should be Lines
      8. Paul: Class of specification, not the Family or Line.
      9. Lorraine: topic is coordination of care, ordering
      10. Paul: Go back to TSC - why a DAM is a family
        • Two classes - conceptual and implementable.
        • Lorraine: more than 2.
      11. Paul: We usually discuss implementable. We could add DAM or FM to the list.
      12. Tony: What is the target of the grid.
      13. Paul: To lookup e.g. the coordination of care
      14. AndyS: Not sure even insiders know how to use the Grid.
      15. Lorraine: Designed by ES and some co-chairs. Implemented by HQ. I use combinations: Work group or search.
      16. Andy B: You have to have knowledge of the family to search by family: The lines are defined by the domain of user
      17. Paul: Topic or purpose of use.
      18. Lorraine: comment ballot material is not published.
      19. Paul:Rationale - Don't end at comment.
      20. He also asked ARB to compare to the values for Type in the Standards Master Grid, which doesn’t match the GOM values at all.
      21. Canonical DAM
    • Line 190: A DAM is an example of a product family. - ARB will need to expound on this - it does not make sense, specially since a DAM is not in the product matrix.
    • The “Family” pull-down list of values includes things like v2, v3, CDA and FHIR, not categories of artifacts like DAMs. That’s why the statement in the canonical DAM confusing and inconsistent. It may be correct in the eyes of some, but it may seem confusing to others.
  3. Other business and planning
  4. Adjournment
    • Adjourned at 5:00pm U.S. Eastern.

Tony Julian (talk)