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

2016 ARB Baltimore WGM

From HL7Wiki
Jump to navigation Jump to search

Agenda Sunday Q4 Joint with SGB

  1. Call to order
  2. Roll Call
  3. Approval of Agenda
  4. Governance
  5. Other business and planning
  6. Adjournment

Minutes Sunday Q4

While discussion was held the group did not have quorum until 4:55. It was agreed that ARB should go back to TSC to get clarification on the assignment.

Agenda Thursday Q3

  1. Call to order
  2. Roll Call
  3. Approval of Agenda and September 13, 2016 Minutes
  4. Methodology (60 minutes)
  5. Management
  6. Governance
  1. Other business and planning
  2. Adjournment

Meeting Information Thursday Q3

HL7 ArB Work Group Meeting Minutes

Location: Baltimore WGM

Date: 20160922
Q3 - Time: 1:45pm U.S. Eastern
Facilitator Julian, Tony Note taker(s) Julian, Tony
Attendee Name Affiliation
R Bond,Andy NEHTA
X Constable, Lorraine Constable Consulting Inc.
. Hyland, Mario AEGIS
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
X Kubick, Wayne HL7 CTO
X Loyd, Patrick ICode Solutions
R Lynch, Cecil Accenture
R Milosevic, Zoran Deontik Pty Ltd
X Stechishin,Andy CANA Software and Service Ltd.
Guests
X Mc Daniel, Mary Kay Cognosante, LLC
X Luensman, Genny Centers for Disease Control and Prevention/CDC
X Reed-fourquet,Lori e-HealthSign, LLC
.
Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes

Minutes Q3

  1. Management
    • Motion to approve September 13, 2016 Minutes (Patrick/Lorraine)
    • Vote (4-0-0)
  2. Methodology
  3. [ODH]
  4. Motion to approve Lorraine/Patrick
  5. Vote 4-0-0
  6. Second vote on DMP: Motion to approve (Patrick/Lorraine)
  7. Vote 4-0-0
  8. Motion to approve the following Mission:(Patrick/Lorraine)
    • The HL7 ARB seeks to define a coherent architecture for HL7 work that defines the relationships among HL7 work products, other standards and components of local implementations.
    • This architecture includes the Business Architecture by which these work products are produced and managed through their life cycle, the governance that will be enacted on these work products, and the scope of the standardization effort itself.
    • The ARB also provides review and guidance on the use, implementation and conformance of work products.
    • Motion to call the question.(Patrick/Lorraine)
    • Vote on motion to call the question 4-0-1
  9. Vote on the mission statement 5-0-0
  10. Motion to send for next GOM change to para 09.03(Patrick/Lorraine)
  11. Vote 5-0-0
  12. Motion to approve Charter below(Patrick/Andy s)
    • Charter
    • Work Products and Contributions to HL7 Processes
    • 1. The Architecture Board (ARB) defines and maintains the principles, language, and grammar of the Services Aware Interoperability Framework (SAIF) Canonical Definition (CD).
    • 2. As an extension of the SAIF CD, the ARB also defines the mechanisms to ensure consistency of and traceability across and between HL7 standards artifacts from conceptual, logical, and implementable viewpoints.
    • 3. The ARB provides guidance and support to working groups submitting artifacts or methodology using the SAIF IG to ensure they are compliant with the principles and language of the SAIF CD.
    • 4. The ARB reviews, or evaluates other reviews of, work products using the SAIF CD review methodology. It provides a report that outlines any deviations from the SAIF CD methodology or measures of quality. Where such a work product is sent to full membership ballot, the ARB report shall be included in the ballot package.
    • 5. The ARB may review the Mission and Charter and Project Scope statements of HL7 Working Groups prior to their consideration by the Technical Steering Committee(TSC). The ARB will consider whether projects undertaken are appropriately defined within HL7s mission.
    • 6. The ARB will advise the TSC and HL7 Chief Technology Officer on matters relating to architectural aspects of standards artifacts as they are produced by HL7 Working Groups.
    • 7. The ARB may review work products when requested to by HL7 Working Groups or the TSC.
    • Formal Relationships With Other HL7 Groups
    • TSC : The ARB reports to the TSC.
    • Standards Governance Board(SGB): The ARB provides guidance and support to the SGB.
  13. Vote 4-0-0
  14. Motion to adjourn at 3:00pm Eastern

Report of Decisions made last cycle

Works in progress

  1. Mission and Charter
    • Review after discussing goals
  2. Decision Making practices
    • Second vote as required by the DMP for revisions
  3. Substantivity
  4. BAM
    • Where do we go from here?
    • We started sunset, were going to review with PIC, but circumstances overcame
Retrieved from "https://wiki.hl7.org/w/index.php?title=2016_ARB_Baltimore_WGM&oldid=126527"