20110914 SAIF AP Meeting

Agenda

1. Brief (1-2 minutes) SAIF AP Project Status Updates (progress made and next steps)
   1. Preparation of SAIF Book for Informative Ballot (ArB)
   2. Wrappers requirements determination (InM)
   3. SAIF Implementation Guide (MnM)
   4. SAIF Artifact Definition (MnM)
   5. Behavioral Framework (OO)
   6. Composite Order (OO)
   7. Lab Order Template (OO)
   8. SAIF Pilot Coordination Project (Pjt Services)
   9. CDA R3 Project (Struc Docs)
   10. Quality Dashboard Progress (Publishing)
   11. Cookbook for Security Considerations (Security)
       1. Tracker 1945 - How should we go about having the Security Cookbook integrate within the OO CO and CDA R3 projects?
2. Work on the RASCI charts for the SAIF sub projects (Haddorff)
3. SAIF and Sound White paper (Haddorff)
4. Update from the Tuesday Q3 CDA R3 Meeting (Kreisler)
   1. Tracker 1939 had the following from Calvin Beebe:
   2. The Structured Documents WG would like to host a session at the Sept WGM on CDA R3 and SAIF considerations. We currently have the session planned for Tuesday Q3, if your committee or members from your committee could attend this session that would be great. Given the large number of committees and their interest in the CDA R3 efforts underway, we thought that a joint session with ITS, M&M, Tooling and Publishing would be the best venue to discuss this topic. Please advise if your committee will be joining us for this session and I will post their participation on the HL7 Meeting Calendar.
6. Housekeeping
   1. Sept 21 call -- keep or cancel?
   2. Continue calls on Wednesdays at 10am or change?
   3. Next WGM Needs
   4. Upcoming vacation schedules/impacts to upcoming calls

Meeting Attendees

X=Present on Call

Facilitator	Austin Kreisler	Note taker(s)	David Hamill
Attendee	Name	Affiliation
X	Austin Kreisler	TSC Chair
X	Woody Beeler	Beeler Consulting
X	David Hamill	HL7 HQ / Program Manager
X	Anil Luhtra	HL7 Canada
X	Frank Ploeg	HL7 Netherlands
X	Andy Bond	NEHTA
X	David Hulbers	COH
X	Stacy Berger	City of Hope
X	RIki Ohira	Booz Allen Hamilton
X	Lorraine Constable	Composite Order Pjt \ OO Behavioral Framework Pjt
X	Patrick Loyd	OO Work Group / Composite Order Pjt
X	Rick Haddorff	Project Services WG / SAIF Pilot Coordination Pjt
X	Brian Davis	3rd Millenium
X	David Parker	Evolvent
X	Chan Hock Yan	HL7 Singapore
X	Mark Shafarman	Shafarman Consulting
X	Zhijing Liu	Siemens
	Freida Hall	Project Services WG
Quorum Requirements Met: Yes

Minutes

Minutes/Conclusions Reached:
Project Updates
1.Preparation of SAIF Book for Informative Ballot (ArB)
Patrick: Headed toward final first release of the SAIF CD by Friday.

2.Wrappers requirements determination (InM)
Patrick: Temporarily suspended the project. There’s a dependency matrix. Will reevaluate in January, 2012. OO not bringing forward any new requirements for Wrappers. BF is.

3.SAIF Implementation Guide (MnM)
Woody: First phase is SAIF Artifact Definition. Determine what artifacts go where and when.

4.SAIF Artifact Definition (MnM)
Woody: Struggling; just a few Artifact Definitions completed over the summer. Still have well over half to complete. Engaged the FTSD team to get volunteers to assist. Resource need is for people in the infrastructure WGs.
Conf calls are 1pm ET on FRidays

5.Behavioral Framework (OO)
Patrick: Out of Cycle meeting in Washington (state). 2-3 days of conceptual modeling on BF was done by Patrick and Lorraine

6.Composite Order (OO)
Patrick: On schedule to produce what we used to seeing printed out in the ballot. The things that won’t be ready in time is the ECCF filled out. Need to DAM some of this, requirements analysis, etc. Plan is to going ahead with ballot the verbiage side, static models
Won’t be there are ECCF, DAM, technical artifacts (schema). In January, 2012 will be looking for resources to go off and start DAMing, requirements analysis, etc. Right now OO is guessing at some of the artifacts since they’re not completed yet.
Critical path items are to have people understand BF in a real way so they can comment on it.
7.Lab Order Template (OO)
Moving forward nicely. Same as Composite Order

8.SAIF Pilot Coordination Project (Pjt Services)
Rick: At the last conference call, the team reviewed the SAIF Pilot Coordination project schedule and reviewed some questions. Dave still needs to update the schedule based on that feedback.

9.CDA R3 Project (Struc Docs)
Austin: Not much progress through the summer. Austin has talked to some people about their availability going forward. He has some success from some Pharmacy folks. However, CDA 2.1 project may compete for these resources.

10.Quality Dashboard Progress (Publishing)
Austin: It’s not an official project yet, but Publishing is continuing to investigate it further. Woody: Not clear on the the requirements for this. Will discuss offline. Perhaps remove this from future agendas.

11.Cookbook for Security Considerations (Security)
Tracker 1945 - How should we go about having the Security Cookbook integrate within the OO CO and CDA R3 projects? No Security WG rep present.
Austin: The plan is to have SAIF AP projects go through the Security Cookbook.
Patrick: Depends on if BF project has Wrappers requirements

Work on the RASCI charts for the SAIF sub projects (Haddorff)

• Use a RASCI chart as a tool to define the roles/responsibilities of the various groups that are part of SAIF for coordination items that have been identified.
• Rick showed an example using Confidentiality Code
• The chart contains a list of tasks, then groups (WGs, TSC, HL7 HQ, SAIF AP) across, and under each W.
• RASCI charts indicate
  • Responsible (for the task)
  • Accountable (reviews work)
  • Support (a group will need to create something to support the task)
  • Consulted (about the task)
  • Informed (of the outcome)

• The Pilot Coordination Project can work on the RASCI charts, but also focus on the dependancies.
• IG Next up for RASCI work
• Work out the ones with CDA R3. (Rick/dave to join CDA R3 call)
• Work out one for CO - OO, MnM SAIF IG

SAIF and Sound White paper (Haddorff)

• Rick: Currently on hold.
• Originally created to focus on how to fast track SAIF development.
• It is linked to the SAIF AP page and comments are welcome.
• Also, the white paper documents the benefits that come out of using SAIF. This may need to be re-examined based on the latest *iteration of the SAIF CD. This white paper may get folded into the SAIF IG.

Update from the Tuesday Q3 CDA R3 Meeting (Kreisler)

• Tracker 1939 had the following from Calvin Beebe:
  • The Structured Documents WG would like to host a session at the Sept WGM on CDA R3 and SAIF considerations. We currently have the session planned for Tuesday Q3, if your committee or members from your committee could attend this session that would be great. Given the large number of committees and their interest in the CDA R3 efforts underway, we thought that a joint session with ITS, M&M, Tooling and Publishing would be the best venue to discuss this topic. Please advise if your committee will be joining us for this session and I will post their participation on the HL7 Meeting Calendar.
• Austin: A variety of infrastructure WGs were invited toattend. It ended up being a discussion of using HTML 5.
• ITS WG will be creating a PSS regarding HTML 5 and MicroData.
• Rick: Will there be a conference call with CDA R3 and SAIF.

Housekeeping

• Sept 21 call -- keep or cancel? CANCEL
• Continue calls on Wednesdays at 10am or change?
  • LC would like to change.
  • Doodle Poll for different times on Wednesday.
• Next WGM Needs
  • Same Wed Q4 time

Gforge Accounts can be requested via: http://gforge.hl7.org/gf/account/?action=UserAdd

Adjourned 5:00 PM Pacific Time

New Action Items

Dave – Update InM, OO pilot coordination task. S/B MnM, OO because OO needs to use whatever the new Wrappers are. However, the requirements for the Wrappers are coming from MnM, not InM
Austin – Invite Lorraine, Patrick, Rick and Dave to the CDA R3 call to discuss the Coordination items. (create a tracker for this) Probably will occur in the coming month.
Dave – send out a doodle poll for proposed SAIF AP time