20101003 arb cambridge wgm minutes

ArB Minutes

Meeting Information

HL7 ArB Work Group Meeting Minutes Location: Cambridge, MA		Date: 20101003 Time: 9:00am U.S. EDT
Facilitator	Ron Parker	Note taker(s)	Tony Julian
Attendee	Name	Affiliation
X	Bond,Andy	NEHTA
X	Curry, Jane	Health Information Strategies
X	Grieve, Grahame	Kestral Computing
X	Julian, Tony	Mayo Clinic
X	Koisch, John	Guidewire Architecture
.	Loyd, Patrick	Gordon point Informatics LTD.
X	Lynch, Cecil	ontoreason LLC
X	Mead, Charlie	National Cancer Institute
.	Nelson, Dale	II4SM
X	Ocasio, Wendell	Agilex Technologies
X	Parker, Ron	CA Infoway
.	Quinn, John	Health Level Seven, Inc.
.	Shakir, Abdul-Malik	Shakir Consulting
.	Guests
.	Haddorff, Richard	Mayo Clinic
X	Hufnagel, Steve	U.S. Department of Defense, Military Health System
.	Koehn, Marc	Gordon point Informatics LTD
.	Laakso, Lynn	Health Level Seven International
.	McGaughey, Skip	.
X	McKinnon, Bruce	Jassco Systems
X	Pech, Brian	Kaiser Permanente
.	Peres, Greg	CA Infoway
.	Robertson, Scott	Kaiser Permanente
.	Rospide, Eddy	Albany Medical Center
.	Smith, Karen	HL7 Technical editor
X	Thompson, Cliff(via telcon)	OntoSolutions LLC
X	VanDerZel, Michael	UMCG
.	Wrightson, Ann	HL7 UK
Quorum Requirements Met: (yes/No)

Agenda

Agenda Topics

• Sunday Q1
  • Call to order
  • Approval of Agenda for quarter
  • Approval of agenda for WGM
  • Approval of Minutes
  • Update from TSC (Ron/Charlie) (30-45 minutes)
  • Set direction for the week.
  • Arb Membership Criteria Review
  • SAIF Glossary Review
• Sunday Q2
  • Call to order
  • Approval of Agenda for quarter
  • Behavioural Framework (John Koisch) ???

• Sunday Q3
  • Call to order
  • Approval of Agenda for quarter
  • Information Framework and IFIG (Cecil Lynch)
  • Coherence ???

Supporting Documents

1. List any/all documents to be provided at the meeting, including their URL if applicable. For a WGM, indicate if hardcopies will be supplied or attendees should print off copies themselves

Minutes

Minutes/Conclusions Reached:

Sunday Q1

• Call to order
  • Called to order at 9:15am U.S. EDT.
• Approval of Agenda for quarter
  • Approved by affirmation.
• Approval of agenda for WGM
  • Approved by affirmation.
• Approval of Minutes
  • Approved by affirmation.
• Update from TSC (Ron/Charlie) (30-45 minutes)
  • Reviewed Roadmap - committe renamed to Strategic Initiatives Committee
  • Publishing facilitator will coordinate our Glossary work with Publications
  • Concern was raised that many of the HL7 leaders are consultants
  • Jane Curry agreed to be publishing facilitator
    • Discussion was held on what level the glossary should exist, as well as other HL7 content. Publishing/Tooling long term goal is to not only create a single ballot package, as well as custom view package - where all the links work.
    • We need a business process as well as a set of tools to make it real. Some people recognize the need, some do not.
    • There is a number of people who just want to get their job done, and not be concerned about the enterprise.
  • Tutorials need some form of validation
    • e.G. Security COnsiderations Cookbook is tutorial with very "Authoritative" language

MOTION: Approve Jane Curry as Publishing Facilitator: Unanimous

• • Arb to ensure the definition of what constitutes "Substantive change" is done
    • Woody suggested we delegate and include more than one other WG (MnM + ??)
    • Should include versioning/sunsetting issue as well.
    • Was a role of the old ARB.
    • Ended up clarifying rules to prevent ARB from being court of appeals for Substantive Change.
    • Original document defined substantive change as anything that breaks wire format
    • With the advent of V3 xml change in wire format was not necessarily substantive.
    • Grahame Grieve: Arb should specify a statement of value - what is substantive change at the highest level. Then create a task force to generate rules for a specific specification set.
    • John Koisch: Each specification could provide it's own substantive change rules.

Grahame's Definition: Substantive change is any change in a specification that causes changes to conformant implementations, except in as much the implementation leverages technical publication artifacts directly.

• • Replace Services with Service (change plural to singular).

MOTION: Change the S in SAIF to singular. Unanimous approval

• • SAIF transition from ALPHA to BETA+
    • Calvin Beebe's presentation on application of governance.
    • Suggested that we pick a probblem, apply SAIF end-to-end, and refine:
      • Governance
      • Implementation Guide
      • Methodology
    • Charlie Mead will discuss experience at NCI with TSC - around four/five points:

1. Value propositon
2. Have a clearly defined scope to apply SAIF
3. Come to terms with defining artifacts and meta-data
4. Governance must recognize that you cant govern everything - look at the life cycle, and the risk of not governing certain aspects.
5. There must be a notion of change management recognition.

• • • We need an architecture informed by SAIF
    • What are the working elements of SAIF that apply regardless of messaging, documents, and service metaphors and determine how to govern "that"

• • Set direction for the week.
  • Arb Membership Criteria Review
  • SAIF Glossary Review

Sunday Q2

• Sunday Q2
  • Call to order
  • Approval of Agenda for quarter
  • Behavioural Framework (John Koisch)

• • Initiate Reponsed to TSC on "Substantive change"
  • Glossary Review

Sunday Q3

• • Call to order
  • Approval of Agenda for quarter
  • Behavioural Framework (John Koisch) ???
  • Coherence ???
• Adjourned <hh:mm am/pm> <timezone>.

Meeting Outcomes

Actions (Include Owner, Action Item, and due date) .

Next Meeting/Preliminary Agenda Items .

Tony Julian 03:17, 3 October 2010 (UTC)