SAIF Pilot Coordination Project

03-26-2011: PAGE UNDER CONSTRUCTION - Rick Haddorff Project Services

Return to Main Page - SAIF Architecture Program wiki page - Work Group main page

• Project co-sponsors TSC and Project Services

Project Information

Link to Project Insight Searchable Database Entry (keywords SAIF Pilot Coordination), which contains:

• Brief description of project
• Project facilitators
• Summary of project scope statement

Meeting Information

Currently meeting along with SAIF Architecture Program

Status

Nothing in ballot at this time

Issues / Hot Topics

• List issues or link to issues tracking repository (wiki pages or GForge)

GForge Item	Description	Next Steps	Notes/Links
1865	Determine what steps needs to be completed to acquire the EA software	Lorraine Constable will document what steps they took to acquire EA software for the OO project and report to the team

Closed Issues / Deliverables

• List issues or link to issues tracking repository (wiki pages or GForge)

GForge Item	Description	Deliverable	Notes/Links
1868	Determine how to actually get the EA Software to the modelers	The process is documented in the Managing Sparx Enterprise Architect License Distribution (via GForge > Tooling Documenation > Files). Also Tracker 1865 is continuing work regarding this topic	Managing Sparx Enterprise Architect License Distribution
1868	Pilot Coordination Deliverable: For Orders and Observations Behavioral Framework tooling selection (Enterprise Architecture): Document the relationships for who needs to be involved so the next tool we need we know who to go to and what steps to complete to obtain the software.	RASCI chart	RASCI OO EA Tool

Project Documents

• Link to SAIF Pilot Coordination Project Schedule on GForge
• Link to project GForge
• Link to reference documentation on GForge, HL7 Web site WG Documents/Presentations page, or external web pages

Project Schedule

WORK IN PROGRESS

• Link to SAIF Pilot Coordination Project Schedule on GForge

• List issues or link to issues tracking repository (wiki pages or GForge)

Complete	Task Name	Start Date	End Date	Comments
50%	Populate SAIF Pilot Coordination wiki page	May 2011 WGM	May 2011 WGM	Create SAIF Pilot Coordination wiki page
100%	Tooling: Enterprise Architecture for OO Composite Order BF project/licensing	May 2011 WGM	June 2011	GForge trackers 1865 and 1868. Jane is working on gathering this
100%	Pilot Coordination Deliverable: Document the relationships for who needs to be involved so the next tool we need we know who to go to and what steps to complete to obtain the software.
100%	Pilot Coordination Deliverable: Document what needs to be done to procure an EA license for those who need it
0%	InM: Wrappers-Need lead resources for OO CO project	Sept 2011 WGM	Oct 2011	OO CO project needs someone from INM or the Wrappers project to lead the Wrappers portion of OO CO project. Gforge Tracker 1864.
0%	Pilot Coordination Deliverable: Document the need for a Wrapper Facilitator for a future SAIF Implentation Guide
0%	Governance: Ongoing documentation as relationships discovered	Sept 2011 WGM	Oct 2011
0%	Pilot Coordination Deliverable: Will probably be suggestions for the SAIF Governance Framework (will find out more about the scope of SAIF Governance at the May 2011)
0%	Security: Include Security Cookbook in OO CO project	Sept 2011 WGM	Oct 2011	Actual target date will be determined by the OO CO project schedule
0%	Pilot Coordination Deliverable: Not sure. Need to ask the SAIF AP team how to go about this task.
0%	OO/EHR-S FP: Define functional profile for composite order and lab order	Sept 2011 WGM	Oct 2011	EHR and OO work together to do this. Actual target date will be determined by the OO CO project schedule.
0%	Project Specific Deliverable: From the OO CO project; the Functional profile is the project specific deliverable.
0%	Pilot Coordination Deliverable: Documenting how the EHR group provided input to OO for the profile in the future SAIF IG
0%	Tooling: Updating generator to create the new technical artifacts for BF	Sept 2011 WGM	Oct 2011	Tooling and OO work together to do this. Actual target date will be determined by the OO BF project schedule.
0%	Project Specific Deliverable: From the OO BF project: An updated generator.
0%	Pilot Coordination Deliverable: Document the Tooling/OO coordination work in the future SAIF IG.
0%	Publishing and MnM: What parts/pieces are in ballot	Jan 2012 WGM	Feb 2012	Part of the OO CO project, needing to know how to ballot. Actual target date will be dictated by the SAIF IG project
0%	Project Specific Deliverable:Part of the OO CO project; document this in the current SAIF IG (project being run by MnM)
0%	Pilot Coordination Deliverable: With the new SAIF artifacts, document what will need to be balloted, how will it impact preparing for balloting and balloting
0%	ITS: What do the schemas look like?	Sept 2011 WGM	Oct 2011	From the OO CO project, how are they going to get the schemas generated with SAIF? Actual target date will be determined by the OO CO project schedule.
0%	Project specific Deliverable: From the OO CO project, will be schemas that were produced.
0%	Pilot Coordination Deliverable: Document how to get the schemas generated with SAIF in the future SAIF IG.
0%	SOA: Composite order and lab order need to include services for lab ordering	Sept 2011 WGM	Oct 2011	Actual target date will be determined by the OO CO project schedule.
0%	Project Specific Deliverable: From the OO CO project, the project has requested someone from SOA to be a facilitator (called a SOA Facilitator).
0%	Pilot Coordination Deliverable: Document the relationship and reason the SOA Facilitator was needed. Not sure where the documentation will ultimately reside; perhaps in the Goveranance documentation?
0%	MnM: Maybe new fields and/or classes to support new BF	Sept 2011 WGM	Oct 2011	Coordination between MnM and OO BF project. Actual target date will be determined by the OO BF project schedule.
0%	Project Specific Deliverable: From the OO BF project; possible changes to the RIM (New fields/classes).
0%	Pilot Coordination Deliverable: The coordination between MnM and OO may need to be documented in the Governance document.
0%	ArB, MnM: New methodology, diagramming, pieces/parts that go in the ballot to define BF, including technical artifacts	Sept 2011 WGM	Oct 2011	Actual target date will be determined by the OO BF project schedule.
0%	Project Specific Deliverable: To document this in the current SAIF IG (project run by MnM).
0%	Pilot Coordination Deliverable: No real deliverable; just insure that MnM has documented it in current SAIF IG.
0%	Templates: Normative approved approach for HL7 template. OO project includes a Lab Order template which constrains the over-arching composite order model	Sept 2011 WGM	Oct 2011	Coordination between OO and Templates. Actual target date will be determined by the OO CO project schedule.
0%	Project Specific From the OO CO Project; Deliverable will be be a template
0%	Pilot Coordination Deliverable: Document the relationship between OO and Templates in the Governance document
0%	Security: Cookbook and MnM	Sept 2011 WGM	Oct 2011
0%	Project specific deliverable: From the MnM SAIF IG project Create the Security portion of the current SAIF IG.
0%	Pilot Coordination Deliverable: No real deliverable; just insure that MnM has documented it in current SAIF IG.
0%	Security, CBCC: Confidentiality codes coordination needed between CDA R3 and OO and Security/CBCC	Jan 2012 WGM	Feb 2012
0%	Project Specific Deliverable: Harmonization between the groups on how to create new confidentialy codes or use existing codes
0%	Pilot Coordination Deliverable: Document who had to be part of the process and what the process is in the future SAIF IG
0%	Structured Docs: Information model consistency (CDA R3 project)	Sept 2011 WGM	Oct 2011
0%	Project Deliverable: From CDA R3 project: One instance/example is the modeling of citizenship in CDA R3 (Coordination between CDA R3 and how it's been currently modeled by PA)
0%	Pilot Coordination Deliverable: Governance document will address information model consistency