20110608 SAIF AP ConCall

SAIF Architecture Program – 2011-06-08 Meeting

Return to SAIF Architecture Program Wiki Home Page<br\> Return to SAIF AP Meeting Minutes and Agendas

Meeting Logistics

• Dates: Weekly on Wednesdays
• Time: 10:00 - 11:00 Eastern
• Phone Number: +1 (770) 657 9270
• Participant Passcode: 124466
• Web Coordinates: https://www2.gotomeeting.com/join/768017802 Meeting ID: 768-017-802

Agenda

1. Role Call
2. Agenda Review
3. Rick to present a summary of Marc Koehn’s SAIF Pilot project report
4. Governance Discussion
5. Recurring Agenda Items
   1. Tooling/Enterprise Architecture Update (Jane Curry)
   2. Pilot Coordination updates (Rick Haddorff)
      1. Any new Coordination items? (Team)
6. Action item review (see below)
7. Next steps

Action Items to Review

1865: Determine what steps needs to be completed to acquire the EA software<br\> Jane, is this complete? What is the next step?<br\> Today's Update: <br\> Jane gathered TSC approval for the proposed process.<br\> Joshua Carmody (HQ Staff) owns the key management duties.<br\> Breifly summarizing some of the tasks in the process:<br\> A project scope statement is required.<br\> Request a key from Josh<br\> A permanent key will be provided to the appropriate people.<br\> OO Example: OO co-chair sends an email of the name of the project, names and emails for the people that need a permanent key.<br\> For now, it will reside in Tooling, in GForge, with other Tooling document. It may be a cochair resource.<br\> Lorraine: As part of the OO work, she started a document of how to get EA for a project. This document may also need to reside with Tooling project documents<br\> <br\> 1868: Determine how to actually get the EA Software to the modelers. <br\> Dave has Patrick as the owner. Is this correct or should it be Jane based on her work with Sparx?<br\> Today's Update: This can be closed. The process is documented in the EA Process document (tracker 1865)<br\> <br\> 1894: Team to review the SAIF and Sound White paper <br\> Last update: From 2011-05-11 meeting: Perhaps defer publication of this until the SAIF Artifacts definition has been completed (targeted for May), since the Artifacts are referenced in the White Paper.<br\> Jane: What is the status of the SAIF Artifacts Definition?<br\> Today's Update: New target completion date: September, 2011.<br\> <br\> 1914: Talk to publishing regarding a quality dashboard visible for the balloted item - Austin/Gregg<br\> Gregg: What is the status? Raised on the May 6 Publishing Call<br\> Today's Update: Issues were raised in the Publishing call, but not addressed. Continued work with between Publishing TSC is needed.<br\> <br\> 1944: Should a SAIF Governance document be created via the SAIF Pilot Coordination Project? <br\> While detailing out the SAIF Coordination project schedule, Rick and Dave wanted the team to discuss if we need to create a new project or GForge tracker item to create a SAIF Governance document. If so, what should the document create?<br\> Team: Thoughts?<br\> Today's Update: No update

Link to the Complete List of Action Items/Issues/Risks (GForge)

Meeting Attendees

X=Present on Call

Facilitator	Austin Kreisler	Note taker(s)	David Hamill
Attendee	Name	Affiliation
	Austin Kreisler	TSC Chair
	Brian Pech	Interested Participant
X	David Hamill	HL7 HQ / Program Manager
	Ed Tripp	Domain Experts SD \ TSC
X	Gregg Seppala	Product Quality Plan Project
X	Jane Curry	Tooling
	Jim McClay	Emergency Care
	John Moehrke	Security Cookbook
	John Quinn	HL7 CTO
X	Lloyd McKenzie	MnM Work Group / SAIF Implementation Guide Pjt
X	Lorraine Constable	Composite Order Pjt \ OO Behavioral Framework Pjt
	Patrick Loyd	OO Work Group / Composite Order Pjt
X	Rick Haddorff	Project Services WG / SAIF Pilot Coordination Pjt
	Robert Lario	Object Management
	Steve Hufnagel	ArB / SAIF Book Project / SOA
X	Wendy Huang	Implementation Conformance WG
	Gary Dickinson	EHR WG
	Pat Van Dyke	EHR WG
Quorum Requirements Met: Yes

Minutes

Minutes/Conclusions Reached:

SAIF Pilot Coordination Pilot

• SAIF Pilot project has been closed. Marc Koehn produced a wrap up report for that project.
• Perhaps a quick summary of the report presented to the SAIF AP team is a good step.

• Dave has entered the SAIF Pilot Coordination project schedule. He has exported it into an Excel file, which is available in the SAIF AP GForge docs area, linked from the SAIF AP Wiki page.

Review Project List

• The group felt they weren’t ready to evaluate the project list as we’re not clear of how the functional models and informational models will change.
• Rick: It may be better to focus on one or two projects, because at some point, everything should fall under SAIF in some way.
• Steve: If you ask a project to be a candidate to be a SAIF AP project, what is the objective to be a SAIF AP project? What are you expected to do? We ran into the same problem last year with the SAIF Alpha projects…people weren’t sure of what they were supposed to do. Do we as a SAIF AP team, have a clear understanding (say like a checklist) of what would indicate a project would be a good candidate to be a SAIF project?
• EHR Functional Model seems to be a good candidate project.

• Next Step: Wait to discuss with Austin and present the concerns brought forward today.
  • What is the criteria for a project to be a candidate under the SAIF projects? Perhaps we need to create a checklist that will result in listing the criteria.
  • What is the expected product (or exit criteria) from the projects brought in under the SAIF umbrella.

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

Adjourned 10:55 AM Eastern Time