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

20121108 arb minutes

From HL7Wiki
Revision as of 21:27, 8 November 2012 by Ajulian (talk | contribs) (→‎Minutes)
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
  4. Approval of Minutes
  5. Report from Architecture Project
  6. BAM
  7. Product line Architecture
  8. Other business and planning
  9. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 2012M1108
Time: 4:00pm U.S. Eastern
Facilitator Parker, Ron Note taker(s) Julian, Tony
Attendee Name Affiliation
X Bond,Andy NEHTA
. Constable, Lorraine Constable Consulting Inc.
X Curry, Jane Health Information Strategies
. Dagnall, Bo HP Enterprise Services
. Grieve, Grahame Health Intersections Pty Ltd
X Hufnagel, Steve U.S. Department of Defense, Military Health System
X Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
X Lynch, Cecil Accenture
R Mead, Charlie National Cancer Institute
X Milosevic, Zoran NEHTA
X Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Guests
X Kriesler, Austin HL7 TSC
. Legend
X Present
. Absent
R Regrets
Quorum Requirements Met: Yes

Minutes

  1. Call to order at 16:04 Eastern.
  2. Ron will post the minutes of the last meeting.
    1. Austin:SAIF ARchitecture is Fine. Product architecture productline discussing a kickoff date. Need BAM.
    2. Ron: Have definition in the BAM.
      1. Progress on the front-end piece.
      2. Bo and Cecil no progress on the logical.
  3. BAM Product Line Planning
    1. Ron: Discussed with Jane.
      1. From product line or product family aspect? Have to start product line definition from customer requirements - product has attributes/qualities from the customer perspective. FHIR came about because an HL7 person recognized the complexity of adoption - a consumer based perspective. As we move down the stack to methodology, risk, governance, the lifecycle begin & ends with the customer. Perspective needs to also include realm.
      2. What is attractive to the community is a usable specification that can be repeated for needs - is the qualitative aspects of the technical. Utility of fit for purpose. FHIR meets their customers goals. Need coherence to solve my business problems.
      3. Drive-by interoperability addresses the technical customers. A large EHR initiative need the standards to be fit for purpose for business needs.
      4. We need to adopt BOTH sets of requirements:
        1. Utility of the product
        2. Dynamic behavior. Messaging is not a problem, but dynamic behavior is lacking, and leads to chaos, and inconsistent workflow.
      5. SAIF is about both things - goodness of the product, as well as dynamics.
      6. We are not modeling product line dynamics. - what scope and depth is enough?
      7. Zoran: HL7SI ontology we express service semantics. Follows SAIF semantics. Careplans, referals with require service semantics need the dynamic. Is 'service' a product?