20160816 arb minutes

From HL7Wiki
Jump to navigation Jump to search

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 july 26 and August 2 Minutes
  4. Methodology
    • From the TSC 20160815 TSC minutes
    • ARB suggested the following draft definition for “Guidance” Product Type: - Tony
      • A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications.
        • MOTION to accept definition: Tony/Andy
        • Discussion: Calvin asks if it's a sense that the definition precludes referencing any implementations or complete implementations? Tony: the idea is that it's not an implementation guide. Calvin: Could a guidance document apply to the writing of the standard? Or how you implement an aspect of a standard? Decision that these aspects don't change the definition. Discussion over whether past products would fall under this type.
        • MOTION to table the motion until next week: Lorraine/Paul
  5. Management
    • ARB membership Review
      • GOM ARB citations:
      • 09.03.02.01 Qualifications
      • Candidates for membership in the ARB must recognize the importance of, and have a commitment to, enterprise architecture as a critical success factor for HL7. They must be current members of HL7 or an HL7 Affiliate with strong written and verbal communication skills and expertise in at least one, but preferably both, of the following areas as assessed by the CTO:
      • 1. Large scale enterprise-level architecture contexts with a focus on achieving working interoperability between software components/interfaces in both intra- and inter-enterprise contexts. Interoperability contexts include both traditional “messaging” exchanges of static semantics as well as more complex, multi-component scenarios involving both static semantics and dynamic behavioral interactions.
      • 2. HL7 “core infrastructure” components including complex data types, vocabulary binding, structured documents, methodology and modeling, infrastructure and messaging, implementation and conformance, etc.
      • 09.03.02.02 Commitment
      • Candidates shall provide documentation of support for their participation on the ARB from their employers or a like statement of their personal commitment if individual members of HL7. Members of the ARB are expected to:
      • a. participate in 75% of weekly conference calls
      • b. dedicate 6 - 10 hours each week, in addition to conference calls, to ARB deliverables
      • c. attend at least two of the three Working Group Meetings each year
      • Given that an ARB member has met the criteria established in a. and b. above, the CTO may, at his or her discretion, grant a waiver of the Work Group Meeting attendance requirement (c. above) given suitable documentation of hardship; e.g., lack of funding.
  6. Governance
  1. Other business and planning
  2. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20160816
Time: 4:00pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
. Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
. Dagnall, Bo Chief Technologist - HP Veterans Affairs
. Hufnagel, Steve ?????
X Hyland, Mario AEGIS
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
X Kubick, Wayne HL7 CTO
X Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
X Milosevic, Zoran Deontik Pty Ltd
. 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 July 26 and August 2 Minutes
      • Motion Acceptance: Lorraine/Zoran
      • Vote 5-0-1
  2. Methodology
    • From the TSC 20160815 TSC minutes
    • ARB suggested the following draft definition for “Guidance” Product Type: - Tony
      • A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications.
        • MOTION to accept definition: Tony/Andy
        • Discussion: Calvin asks if it's a sense that the definition precludes referencing any implementations or complete implementations? Tony: the idea is that it's not an implementation guide. Calvin: Could a guidance document apply to the writing of the standard? Or how you implement an aspect of a standard? Decision that these aspects don't change the definition. Discussion over whether past products would fall under this type.
        • MOTION to table the motion until next week: Lorraine/Paul
      • Lorraine: They ran out of time for the discussion.
      • Paul: Does not preclude talking about standards. IG says how to implement that think here, whatever that thing is, and whatever here is. Guidance is more general.
      • Zoran: Problem with 'not directly related to implementation'
      • Wayne: There has to be a clear dividing line between IG and Guidance. Calvin stated that there may be an indirect relationship.
      • Zoran: use may be.
      • Wayne: maybe leaves the door open, but something is missing. Something to do with completeness.
      • An implementation guide is a ???
      • A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications.
      • Lorraine: IG formally defines how to use a standard to a use case including conformance statements.
      • Patrick: Guidance . . it is a good thing to do this,
      • Consolidated cda companion guide( an S&I document) , approach to rim objects
      • "HL7 Implementation Guide: S&I Framework Transitions of Care Companion Guide to Consolidated-CDA for Meaningful Use Stage 2, Release 1 – US Realm".
      • Zoran: Implementation Guide: set of rules defining how an existing standard may be refined either by constraint or extension for a specific context of use.
      • A Guidance is a type of informative document that describes principles, best practices, and general advice but is does not constrain to a given schema or set of schemas.
      • Does a guidance need to be used with an IG?
  3. Management
    • ARB membership Review
    • Review the charter on the next agenda.
      • GOM ARB citations:
      • 09.03.02.01 Qualifications
      • Candidates for membership in the ARB must recognize the importance of, and have a commitment to, enterprise architecture as a critical success factor for HL7. They must be current members of HL7 or an HL7 Affiliate with strong written and verbal communication skills and expertise in at least one, but preferably both, of the following areas as assessed by the CTO:
      • 1. Large scale enterprise-level architecture contexts with a focus on achieving working interoperability between software components/interfaces in both intra- and inter-enterprise contexts. Interoperability contexts include both traditional “messaging” exchanges of static semantics as well as more complex, multi-component scenarios involving both static semantics and dynamic behavioral interactions.
      • 2. HL7 “core infrastructure” components including complex data types, vocabulary binding, structured documents, methodology and modeling, infrastructure and messaging, implementation and conformance, etc.
      • 09.03.02.02 Commitment
      • Candidates shall provide documentation of support for their participation on the ARB from their employers or a like statement of their personal commitment if individual members of HL7. Members of the ARB are expected to:
      • a. participate in 75% of weekly conference calls
      • b. dedicate 6 - 10 hours each week, in addition to conference calls, to ARB deliverables
      • c. attend at least two of the three Working Group Meetings each year
      • Given that an ARB member has met the criteria established in a. and b. above, the CTO may, at his or her discretion, grant a waiver of the Work Group Meeting attendance requirement (c. above) given suitable documentation of hardship; e.g., lack of funding.
  4. Other business and planning
    • [[2016_ARB_Baltimore_WGM |Baltimore WGM]

Andy S Suggested that 23rd report on technical architecture project.

  1. Adjournment
    • adjourned at 4:00pm U.S. Eastern