This wiki has undergone a migration to Confluence found Here

20140401 arb minutes

From HL7Wiki
Jump to navigation Jump to search

ARB - Meeting (Date in Title)


  1. Call to order
  2. Roll Call
  3. Approval of Agenda and Minutes
  4. Methodology (30 minutes)
    1. BAM sections Review:
      1. Section 7 Business Architecture Bo, Ron, Jane
      2. Section 8 Implementation Lorraine
      3. Section 6 Organizational Precepts
        1. Tony has suggestions to review.
        2. Waiting on chapters 6 and 7
  5. Management
    1. Review to-do list
    2. Review/update Arb BAM task list
    3. Report from Architecture Project
  6. Governance
  7. Other business and planning
  8. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Time: 5: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.
R Curry, Jane Health Information Strategies
X Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve U.S. Department of Defense, Military Health System
X Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
. Milosevic, Zoran Deontik Pty Ltd
X Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
R Stechishin,Andy CANA Software and Service Ltd.
. Guests
. Kreisler, Austin HL7 TSC Chair
. Luthra, Anil NCI
. Pech, Brian Kaiser Permanente
. Shakir, Abdul Malik City of Hope National Medical Center
. Laakso, Lynn HL7
. Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes


  1. Minutes and agenda
    1. Motion to approve agenda and minutes(Lorraine/Ron)
    2. Vote 2-0-2
  2. Business Architecture
    1. FGB new cochairs dave shaver, Woody Beeler, new member Lorraine
    2. No progress to date
    3. Ron and Lorraine will be meeting to get closure and follup review session on wednesday thursday of next week.
  3. Implementation still waiting on 7.
    1. Organizational Precepts
      1. The HL7 ???has responsibility for enforcement of the policies and procedures expressed in the HL7 Governance and Operations Manual (GOM)
      2. The HL7 GOM delegates to the HL7 TSC (9.01)
        1. Establishing and maintaining an HL7 Architecture, development methodologies, and work processes to be used by The Working Group in developing HL7 protocol specifications
        2. Ensuring that the efforts of The Working Group to produce protocol specifications proceeds at a reasonable pace
        3. Ensuring that The Working Group collaborates smoothly and covers the scope of work in a consistent manner.
        4. Managing the ballot and distribution process for those HL7 Protocol Specifications identified by the Executive Committee as intended to be freely available to the public.
      3. The HL7 TSC may delegate the above authorities to the Governance, Management, or Methodology oversight groups while retaining final responsibility.
      4. The governance oversight committee is responsible for
        1. Establishing goals for the product line/family
        2. Ensuring that changes to the product line/family meet the goals for the product line/family
        3. Establishes the methodology group
        4. Establish the management group
      5. The management oversight committee is responsible for
        1. All planning aspects of product line/family changes
        2. Assessing and approving proposals
        3. Assessing and approving publishing requests
        4. Assessing and approving ballot requests
        5. Creating Product Recommendations
      6. The methodology oversight committee is responsible for the processes and working artifacts, e.g.
        1. Creating concept proposals
        2. Creating concept artifacts
        3. Creating examples
        4. Domain definitions
        5. Conformance Criteria
      7. There should be a vitality assessment process
      8. Managemement group asserts the precepts for the group.
        1. Typical consequence: If a review required is not made, the process stops.
      9. Each governance precept should include a noun, verb, and consequence.
      10. Do we provide enough guidance to do it productively, or at all
        1. Methodology is responsibility for processes and working artifacts for example
          1. Proposals,
        2. GOM 02.01
        3. The whole idea is coherence and traceability.
        4. Ken is mulling the idea of a single governance group
          1. Bo is concerned that the BAM is dead because of the long-running which is not yet done. Can we get to that point.
          2. Ron: we can nail down the first stages. Once this is done we can work out the details.
      11. ISSUE: GOM 02.01 Comprehensive Framework
The Modeling and Methodology Work Group shall undertake the development and maintenance of a
comprehensive standards development framework to define, clarify, and delineate the processes
employed by HL7. The framework shall address at least common processes, standards specific
processes, and support and governance processes in sufficient detail to act as a guide to those new
to the HL7 process and provide checkpoints to those involved in the process. The comprehensive
framework may be promulgated as a standard in order to promote the good practices inherent in the
HL7 process.

      1. Adjournment 6:00pm U.S. Eastern