20130827 arb minutes

ARB - Meeting (Date in Title)

Agenda

1. Call to order
2. Roll Call
3. Approval of Agenda and Minutes
4. Management
   1. Glossary
   2. PSS for Tutorial
   3. 8/27 Start WGM planning
   4. Review to-do list
   5. Review/update Arb BAM task list
   6. Report from Architecture Project
5. Governance
6. Methodology
   1. FHIR review update
7. Other business and planning
   1. 9/3 Individuals review due - send to tony to consolidate. task 2623
   2. 9/10 joint review of FHIR ballot task 2623
   3. 9/17 Finalize WGM planning
   4. 9/24 WGM
   5. 10/1 FHIR ballot Recon call task 2623
   6. 10/8 BAM methodology requirements
   7. 10/15 Equip team to finish the BAM
   8. WGM planning
8. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes Location: Telcon		Date: 20130827 Time: 5:00pm U.S. Eastern
Facilitator	Parker, Ron	Note taker(s)	Julian, Tony
Attendee	Name	Affiliation
.	Bond,Andy	NEHTA
X	Constable, Lorraine	Constable Consulting Inc.
.	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
X	Loyd, Patrick
.	Lynch, Cecil	Accenture
X	Milosevic, Zoran	Deontik Pty Ltd
X	Parker, Ron	CA Infoway
.	Quinn, John	Health Level Seven, Inc.
X	Stechishin,Andy	CANA Software and Service Ltd.
.	Guests
X	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

Minutes

1. Minutes and Agenda
   1. Motion to approve agenda and Minutes:(Lorraine/Zoran)
   2. Vote 8-0-0
2. WGM Planning
   1. Sunday
      1. Q1
      2. Q2
      3. Q3
      4. Q4 Build TSC report
      5. Q5 tsc Report
   2. Tuesday
      1. Q4 TBD
   3. Wednesday
      1. CDS meets Q3 - but ArB will skip. Austin thinks correct, but ArB needs to be in the loop.
      2. Ron: Need to discuss vitality assessment in Cambridge. Have we been superceded by events, do we have to re-factor?
      3. Ron: Next few weeks FHIR ballot.Do we need to give the FHIR team time to walk through comments? Tuesday?
      4. Lorraine: Depends on the Comments they receive.
   4. Thursday Q3/Q4 Planning for January
3. Task list:
   1. Fix 2567 dependency on 2668
   2. 2689 for Sunday
   3. 2668 for Sunday - Done
   4. 2624 for Sunday
   5. 2640 on Sunday - & Tsc Content
   6. 2680 depends on Bo
   7. 2683 depends on Bo
   8. Sunday Q2/Q3 template/profile discussion.
4. Architecture Project
   1. Austin: Product family architecure session on Wednesday Q3
   2. Austin: Behavioral framework on Wednesday Q4 - and lessons learned, how to move forward (Lorraine and Patrick)
5. Glossary:
   1. Zoran: Australia has adopted SAIF. Zoran will be presenting paper at EHIC in Sydney. Have identified the issue of template. In SAIF-CD we use template to reflect HL7 version, and as specification template. Presented the content of his email of August 27, 2013 subject "Clarification of template entry in the SAIF glossary."
   2. Zoran: Do we need to specialize it?
   3. Austin: Yes, templates is defining a definition of templates used on top of the RIM. We have to call it something else.
   4. Lorraine: We are discussing the canonical definition, and the instatiation in different artifact types.
   5. Ron: We need to address that a template is an artifact that constrains a model. A Template can be reused as a pattern for reuse. Repeatability and configurabiity of the template is important. IMHO: Template as a constraint on a reference structure can be used variably to represent content, in a way so that you dont have to ballot all variations of the template.
   6. Zoran: The ODP definition states this:
      1. <X> Template: The specification of the common features of a collection of Xs in sufficient detail that an X can be instantiated using it. X can be anything that has a type (see 9.9).
      2. An X template is an abstraction of a collection of Xs. A template may specify parameters to be bound at instantiation time.
      3. The definition given here is generic; the precise form of a template will depend on the specification technique used. The parameter types (where applicable) will also depend on the specification technique used.
      4. Templates may be combined according to some calculus. The precise form of template combination will depend on the specification language used."
   7. Ron: A profile is the guidance to create the instance, the template is the pattern.
   8. Zoran: do we extend or constrain profiles?
   9. Ron: In HL7 we typically constrain the profile. FHIR: Profile would explain extenstion.
   10. Zoran: FHIR uses identity of profiles and resources.
   11. Bo: I presented the concepts - information modeling domain framework. There is a page on the FHIR wiki on how to use it.
   12. Zoran: We need to bring FHIR into this.
   13. Ron: We need to reach out to them by e-mail. We need to satisfy templating as constraint, FHIR, and by extension.
   14. Austin: Templates will be balloting a templates standard in January.
6. Saif Tutorial PSS
   1. Patrick presented the SAIF tutorial PSS.
   2. Austin: HL7 members who need to use it for HL7 work, CO-chairs and Facilitators, should get it for free.
   3. Motion to approve the PSS as amended(Tony/Patrick).
   4. Vote (Unanimous)
   5. Lorraine: Since we dont have a steering Division, does this go to the TSC?
   6. Ron: Yes.
   7. Austin: Will be presented on September 9 to the TSC
7. Adjournment
   1. Meeting was adjourned at 6:00 Pm Eastern.