This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SAIF Pilot Coordination Project Schedule"
Jump to navigation
Jump to search
| (6 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
==Project Schedule == | ==Project Schedule == | ||
| − | |||
| − | |||
*Link to [http://gforge.hl7.org/gf/project/psc/docman/?subdir=338 SAIF Pilot Coordination Project Schedule on GForge] | *Link to [http://gforge.hl7.org/gf/project/psc/docman/?subdir=338 SAIF Pilot Coordination Project Schedule on GForge] | ||
| Line 62: | Line 60: | ||
<td>Sept 2011 WGM</td> | <td>Sept 2011 WGM</td> | ||
<td>Oct 2011</td> | <td>Oct 2011</td> | ||
| − | <td> | + | <td></td> |
</tr> | </tr> | ||
<tr style="background:#f0f0f0;" > | <tr style="background:#f0f0f0;" > | ||
<td >0%</td> | <td >0%</td> | ||
| − | <td> Pilot Coordination Deliverable: The output will be Wrappers draft and Wrappers final, and will be a coordination between. | + | <td> Pilot Coordination Deliverable: The output will be Wrappers draft and Wrappers final, and will be a coordination between. </td> |
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| − | <td></td> </tr> | + | <td>OO will use the Wrappers draft and Wrappers final (OO and InM)</td> </tr> |
<tr style="background:#f0f0f0;" ><td ></td><td></td><td></td><td></td><td></td><td></td> </tr> | <tr style="background:#f0f0f0;" ><td ></td><td></td><td></td><td></td><td></td><td></td> </tr> | ||
| Line 117: | Line 115: | ||
<td>'''OO/EHR-S FP: Define functional profile for composite order and lab order'''</td> | <td>'''OO/EHR-S FP: Define functional profile for composite order and lab order'''</td> | ||
<td>EHR, OO</td> | <td>EHR, OO</td> | ||
| − | <td> | + | <td>May 2012 WGM</td> |
| − | <td> | + | <td>July 2012</td> |
| − | <td>EHR and OO work together to do this. | + | <td>EHR and OO work together to do this. Functional Profile won’t be ready to ballot by Jan 2012. |
| + | Targeting May 2012.</td> | ||
</tr> | </tr> | ||
| Line 146: | Line 145: | ||
<td>Sept 2011 WGM</td> | <td>Sept 2011 WGM</td> | ||
<td>Oct 2011</td> | <td>Oct 2011</td> | ||
| − | <td> | + | <td>REMOVE THIS ITEM FROM THE SCHEDULE?? From 8/31/11 SAIF AP CALL: Austin: No sooner than having a SAIF IG for the BF. Patrick: From a tooling perspective, it takes a long time for this work. Probably a 2013/2014 timeframe. In the meantime, until the generator is ready, manual work will create the technical artifacts. Jane: Another dependency is that there will be other balloted items coming out of the the SAIF IG, and there are other items on the tooling priority list before getting to the BF work. Austin: The generator won’t be on the critical path for moving forward. |
| + | </td> | ||
</tr> | </tr> | ||
| Line 198: | Line 198: | ||
<td>'''ITS: What do the schemas look like?'''</td> | <td>'''ITS: What do the schemas look like?'''</td> | ||
<td>ITS, OO</td> | <td>ITS, OO</td> | ||
| − | <td> | + | <td>Jan 2012 WGM</td> |
| − | <td> | + | <td>Mar 2012</td> |
| − | <td>From the OO CO project, how are they going to get the schemas generated with SAIF? | + | <td>From the OO CO project, how are they going to get the schemas generated with SAIF? Patrick: The constraint is that there are few resources that can create the schemas. OO will need to work with MnM and Tooling to create the schemas. Patrick: Dependant on the Artifact Definition project. Is computable required for 2012? Patrick: Jan 2012 will be tough to meet but perhaps possible. Keep as Jan 2012. |
| + | </td> | ||
</tr> | </tr> | ||
| Line 225: | Line 226: | ||
<td>'''SOA: Composite order and lab order need to include services for lab ordering'''</td> | <td>'''SOA: Composite order and lab order need to include services for lab ordering'''</td> | ||
<td>SOA, OO</td> | <td>SOA, OO</td> | ||
| − | <td> | + | <td>Jan 2012 WGM</td> |
| − | <td> | + | <td>Mar 2012</td> |
| − | <td>Actual target date will be determined by the OO CO project schedule.</td> | + | <td>Actual target date will be determined by the OO CO project schedule. Patrick: We will be ready to ballot traditional artifacts for Jan 2012 (Static Model and dynamic model, etc).</td> |
</tr> | </tr> | ||
| Line 236: | Line 237: | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| − | <td></td> </tr> | + | <td>Patrick: Has needed a SOA facilitatore from the beginning. Perhaps the best mechanism is for OO to finish the RMIMs (going to ballot in January 2012), and then engage a SOA facilitator for items worked on to be balloted in May 2012. Hence, keep the target date as Jan 2012. |
| + | </td> </tr> | ||
<tr style="background:#f0f0f0;" > | <tr style="background:#f0f0f0;" > | ||
| Line 263: | Line 265: | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| − | <td></td> </tr> | + | <td>Does OO or MnM think new fields and/or classes will be needed to support the new Behavioral Framework? Patrick: answer is definitely yes for BF. CO will not have any new fields; OO doesn’t have anything special. Austin: What OO needs is a draft implementation of the BF and a final implementation of the BF, which is part of the SAIF IG project by MnM |
| + | </td> </tr> | ||
<tr style="background:#f0f0f0;" > | <tr style="background:#f0f0f0;" > | ||
Latest revision as of 13:09, 7 October 2011
08-30-2011: PAGE UNDER CONSTRUCTION - Rick Haddorff Project Services
Return to SAIF Pilot Coordination main wiki page
Return to Main Page - SAIF Architecture Program wiki page - Work Group main page
- Project co-sponsors TSC and Project Services
Project Schedule
- List issues or link to issues tracking repository (wiki pages or GForge)
| % Complete | Task Name | Work Groups | Start Date | End Date | Comments |
| 100% | Project Services: Populate SAIF Pilot Coordination wiki page | Project Services | May 2011 WGM | May 2011 WGM | Create SAIF Pilot Coordination wiki page |
| 100% | Tooling: Enterprise Architecture for OO Composite Order BF project/licensing | Tooling, OO | 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, MnM: Artifact Definition coordinates with InM project for Wrappers | InM, MnM | Sept 2011 WGM | Oct 2011 | |
| 0% | Pilot Coordination Deliverable: The output will be Wrappers draft and Wrappers final, and will be a coordination between. | OO will use the Wrappers draft and Wrappers final (OO and InM) | |||
| 0% | Governance: Ongoing documentation as relationships discovered | SAIF AP Team will determine the responsible WG | Sept 2012 WGM | Oct 2012 | |
| 0% | Pilot Coordination Deliverable: Will probably be suggestions for the SAIF Governance Framework document | ||||
| 0% | Security, OO Struc Docs: Include Security Cookbook in OO CO and SDWG CDA R3 projects | Security, OO, Struc Docs | ??? | ??? | GForge Tracker 1945 focuses on determining the target date for this work |
| 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 | EHR, OO | May 2012 WGM | July 2012 | EHR and OO work together to do this. Functional Profile won’t be ready to ballot by Jan 2012. Targeting May 2012. |
| 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 | Tooling, OO | Sept 2011 WGM | Oct 2011 | REMOVE THIS ITEM FROM THE SCHEDULE?? From 8/31/11 SAIF AP CALL: Austin: No sooner than having a SAIF IG for the BF. Patrick: From a tooling perspective, it takes a long time for this work. Probably a 2013/2014 timeframe. In the meantime, until the generator is ready, manual work will create the technical artifacts. Jane: Another dependency is that there will be other balloted items coming out of the the SAIF IG, and there are other items on the tooling priority list before getting to the BF work. Austin: The generator won’t be on the critical path for moving forward. |
| 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 | Publishing, MnM | 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? | ITS, OO | Jan 2012 WGM | Mar 2012 | From the OO CO project, how are they going to get the schemas generated with SAIF? Patrick: The constraint is that there are few resources that can create the schemas. OO will need to work with MnM and Tooling to create the schemas. Patrick: Dependant on the Artifact Definition project. Is computable required for 2012? Patrick: Jan 2012 will be tough to meet but perhaps possible. Keep as Jan 2012. |
| 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 | SOA, OO | Jan 2012 WGM | Mar 2012 | Actual target date will be determined by the OO CO project schedule. Patrick: We will be ready to ballot traditional artifacts for Jan 2012 (Static Model and dynamic model, etc). |
| 0% | Project Specific Deliverable: From the OO CO project, the project has requested someone from SOA to be a facilitator (called a SOA Facilitator). | Patrick: Has needed a SOA facilitatore from the beginning. Perhaps the best mechanism is for OO to finish the RMIMs (going to ballot in January 2012), and then engage a SOA facilitator for items worked on to be balloted in May 2012. Hence, keep the target date as Jan 2012. | |||
| 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 | MnM, OO | TBD | TBD | 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). | Does OO or MnM think new fields and/or classes will be needed to support the new Behavioral Framework? Patrick: answer is definitely yes for BF. CO will not have any new fields; OO doesn’t have anything special. Austin: What OO needs is a draft implementation of the BF and a final implementation of the BF, which is part of the SAIF IG project by MnM | |||
| 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 | ArB, MnM | 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 | Templates, OO | Jan 2012 WGM | Feb 2012 | Coordination between OO and Templates. Actual target date was determined by the OO CO project #587 when the Development of Technical Artifacts step was completed. |
| 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 | Security, MnM | ??? | ??? | GForge Tracker 1945 focuses on determining the target date for this work |
| 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 | 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) | SAIF AP | Jan 2012 WGM | Feb 2012 | |
| 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 | ||||
| 0% | Quality Plan Documentation | ??? | Sept 2011 WGM | Oct 2011 | Details TBD--refer to Gregg Seppala's modified Quality Plan PSS and subsequent discussions. |
| 0% | Project Deliverable: (Phase A) Define the Artifact Quality Metrics | ||||
| 0% | Pilot Coordination Deliverable: (Phase A) Document the quality plan metrics in the quality steps of the PLCPD | ||||
| 0% | Project Deliverable: (Phase B) Identify and document process quality measures of the SAIF IG project | ||||
| 0% | Pilot Coordination Deliverable: (Phase B) Insure the quality measures are included in the Governance document | ||||
| 0% | Project Deliverable: (Phase C) Produce and ballot the SAIF IG for which the Quality Plan will define progress measures | ||||
| 0% | Pilot Coordination Deliverable: (Phase C) No real deliverable; just insure that MnM has documented it in current SAIF IG. | ||||
