20150624 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. Methodology
    1. Publishing Risks Task from TSC (40 minutes)
      1. Arb should not be solving the problem, but rather putting together a strategy.
      2. What does the architecture look like to get there?
      3. Include HL7 Risks for publishing practices.
      4. current publishing risks
    2. RDF Mapping
  5. Other business and planning
  6. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20150424
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.
. Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve ?????
X Julian, Tony Mayo Clinic
X Knapp, Paul Pknapp Consulting
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
R Milosevic, Zoran Deontik Pty Ltd
. Quinn, John Health Level Seven, Inc.
X Stechishin,Andy CANA Software and Service Ltd.
. Guests
X Mead, Charlie Vidal Group, Paris,France
X Hyland, Mario Aegis
. Laakso, Lynn HL7
.
. Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes

Minutes

  1. Agenda was approved by consensus
  2. Minutes approval (16June2015 minutes)
    1. Motion to approve(Andy S, Paul)
    2. Vote(5-0-0)
  3. Methodology
    1. Publishing Risks Task from TSC
      1. The slide deck was reviewed. Key points seem to be:
  • Risks: Unable to progress w/o key persons.
  • Gather what is out there
  • Principles and guidance
  • Look at a vision of the future.
  • end-state goals of sustainability, usability,
  • Look at project basis instead of enterprise basis.
  • Based on projects proponents tooling.
  • Requirements have not been spelled out. These requirements are not known by all of those involved.
  • We have a set of Requirements but not rules for application.
  • Failure of enterprise to govern the organization.
  • Other challenge is that a piece of the services are contracted and managed (Staff), deal with aspects of running the organization, but key functions are outside of that.
  • We have allowed gaps in the resource fabric to become barriers to fulfilling the intentions of the organization.
  • Need recommendations on governance to prevent inconsistency in the future.
  • Either accept as is, or mature our behaviors.
      1. Outcome1: For next week pull together a list of projects in flight.(Lorraine and Andy S.)
  • Next week put together an outline.
  • Specify requirements for publications.(Andy S. & Paul)
  • Obligations/Market requirements.
  • Assess level of risk.
  • We have work-groups that have tooling strategy, and no funding.
  • organization has funding, but no strategy.
    1. RDF Mapping PSS
  • Comment heard:FHIR core group now thinks that rim-mapping is a good thing, but no bandwidth to do so.
  • Charlie: Not their project - not just about FHIR: If the results are optimal, it would spread across FHIR, to all of our artifacts.
  • Lorraine: Assertion is that the tooling should be buried in the build tools.
  • Charlie: Ok, but the project is to develop.
  • Paul: We should for HL7 develop the architecture: there will be multiple tool sets to apply to the architecture. Market wants to know how to map/migrate from one standard to another.
  • Charlie: Initial project should be ARB.
  1. Adjournment at 4:10 pm U.S. Eastern