HL7 Project Scope Statement



Template Usage Information:

• Replace RED text with appropriate content; do not change the name/format/font of the template sections

• To check a box, double click on the box then select the 'Checked' Radio Button under the 'Default Value' heading.

• For assistance in completing each section, refer to Appendix A.

• The Project Approval Process is documented in Appendix B.

• For FAQs (Frequently Asked Questions), refer to Appendix C

• Submit template change requests to PMO@

1. Project Name, ID and Products

| | |

|Implementation Guide for CDA Release 2 – Level 3, |Project ID: |

|Children’s Hospitals Neonatal Consortium: Neonatal Care Report | |

| | |

|-Non Product Project- (Educ. Marketing, Elec. Services, etc.) |V3 Documents - Knowledge |

| | |

| | |

|Arden Syntax |V3 Foundation – RIM |

| | |

| | |

|Clinical Context Object Workgroup (CCOW) |V3 Foundation – Vocab Domains & Value Sets |

| | |

| | |

|Domain Analysis Model (DAM) |V3 Messages - Administrative |

| | |

| | |

|Electronic Health Record (EHR) |V3 Messages - Clinical |

| | |

| | |

|V2 Messages – Administrative |V3 Messages - Departmental |

| | |

| | |

|V2 Messages - Clinical |V3 Messages - Infrastructure |

| | |

| | |

|V2 Messages - Departmental |V3 Rules - GELLO |

| | |

| | |

|V2 Messages – Infrastructure |V3 Services – Java Services (ITS Work Group) |

| | |

| | |

|V3 Documents – Administrative (e.g. SPL) |V3 Services – Web Services |

| | |

| | |

|V3 Documents – Clinical (e.g. CDA) |- New Product Definition- |

| | |

a. Implementation Guide

| |

|Implementation Guide? |

| |

2. Project Intent

Project Insight: Enter into “Project Intent”; add notes if needed, especially for “Project Intent – Other’ (below).

| | |

|Create new standard |Supplement to a current standard |

| | |

| | |

|Revise current standard | |

| |Withdraw current standard |

| | |

| | |

a. Project Intent - Other

If not categorized above, indicate other and specify. Project Insight: This information will appear in the “Project Intent Notes”.

| |

|Other (Please Specify): DSTU |

| |

| |

| |

| |

|Public Document(s) to be created? Check this box if one of the project deliverables will be a publically available document (for example a government |

|mandated or funded specification, or otherwise subsidized publication), To track this information in Project Insight, add a comment in Project |

|Insight’s Project Intent Notes text box indicating a public document will be created. |

|NOTE: When a deliverable is specified as a Public Document, the TSC must make a determination as prescribed in the GOM Section 09.01, part (d). |

| |

3. Sponsoring Group(s)

Click here to go to Appendix A for more information regarding this section.

|Primary Sponsor/Work Group (1 Mandatory) |Structured Documents |

|Co-sponsor Work Group(s) |Child Health |

|Project Team |Name and E-mail Address |

|Project facilitator (1 Mandatory) |Liora Alschuler: liora@ |

| |Bob Dolin: bobdolin@ |

|Other interested parties |Kate Conrad: kate.conrad@ |

| |Jacqueline Kueser: jacqueline.kueser@ |

| |David J. Durand, MD: ddurand@mail. |

| |Karna Murthy, MD: k-murthy@northwestern.edu |

| |Mike Padula,MD: padula@email.chop.edu |

| |Feliciano (Pele) Yu: fyu@peds.uab.edu |

|Multi-disciplinary project team (recommended) | |

| Modeling facilitator |Bob Dolin, MD: bobdolin@ |

| Publishing facilitator |Peter Gilbert: peter.gilbert@ |

| Vocabulary facilitator |Gay Giannone MSN, RN: gay@ |

| Domain expert rep |David J. Durand, MD: ddurand@mail. |

| |Karna Murthy, MD: k-murthy@northwestern.edu |

| |Mike Padula,MD: padula@email.chop.edu |

| |Feliciano (Pele) Yu: fyu@peds.uab.edu |

| Data Analyst facilitator |Gay Giannone MSN, RN: gay@ |

| Business requirement analyst |Gay Giannone MSN, RN: gay@ |

| Requirements process facilitator |Joy Kuhl: joy@ |

| | |

|Implementers (2 Mandatory for DSTU projects): |

|1) Children’s Hospital of Philadelphia |

|2) Child Health Corporation of America |

|3) Children’s Hospitals Neonatal Consortium |

4. Project Scope

Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Description”.

|With cooperation from the Child Health Corporation of America (CHCA) and the Children’s Hospitals Neonatal Consortium (CHNC), this project will develop|

|an implementation guide constraining CDA Release 2. The implementation guide will support electronic reporting of an initial segment of the data |

|elements in the CHNC Neonatal Intensive Care Unit (NICU) Core Data Set (CDS) from Neonatal Intensive Care providers to CHNC. |

5. Project Objectives and Deliverables

Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Project Objectives and Deliverables”.

|This project will develop: |January 2010 |

|A prose implementation guide: | |

|Defining a subset of NICU monitoring data for reporting | |

|Providing consensus among the neonatal data set developers and standards community prior to bringing the full | |

|data set into standard format | |

|A report sample file | |

|Schematron | |

|A rendering style sheet | |

6. Project Dependencies

Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Dependencies & IDs”.

|None |ID |

7. Project Approval Dates

|Sponsoring Group approval Date Project Insight: Enter into “Start Date”. |August 25, 2009 |

|Steering Division Approval Date |TBD |

|Technical Steering Committee Approval Date |TBD |

|PMO Approval Date |TBD |

8. Project Plan Click here to go to Appendix A for more information regarding this section

a. Project Schedule

|Review developing design with HL7 Structured Documents Work Group (SDWG) and HL7 Child Health WG, September 2009 – December 2009 |

|Review complete draft Implementation Guide with SDWG and Child Health WG, December 2009 |

|Draft Standard for Trial Use (DSTU) ballot submittal, December 2009 |

|Ballot reconciliation, January – February 2010 |

b. Project Resources

|CHCA and the CHNC are sponsoring this project and have recruited neonatology subject matter experts from participating hospitals. SDWG will devote |

|work group time to review the design and draft specification before ballot, as well as to support ballot reconciliation. Child Health WG will provide |

|input and feedback. No further resources will be required of HL7. |

c. Project Budget

|Additional funding not required |

d. Ballot Plan - general

| | |

|Comment Only |Normative |

| | |

| | |

|Informative | |

| | |

| | |

|DSTU |Joint Ballot (with other SDOs or HL7 Work Groups) |

| | |

| | |

| | |

|Create a prose implementation guide: |

|Defining a subset of NICU monitoring data for reporting |

|Providing consensus among the neonatal data set developers and standards community prior bringing the full data set into standard format |

|Lay the groundwork for extending the specification as needed |

|As the foundation of this effort, create or reuse templates that meet NICU reporting requirements into a set of modular definitions (templates) |

|conformant with design patterns established for EHRs and interoperable data exchange |

|Document these reusable pieces in two forms -- the format required for HL7 ballot and the template database that will ensure consistency, optimize |

|reuse and lay the foundation for extensibility |

e. Ballot Plan for cross-cutting Projects

|N/A |

f. Industry Outreach

|CHCA and CHNC participating hospitals will be involved throughout the project |

g. Success Criteria

|Adoption of Clinical Document Architecture (CDA) for Neonatal Data Reporting by CHCA and CHNC participating hospitals |

9. External Project Collaboration and Interested Parties

Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Collaboration Efforts”.

|Collaborating with |

|Agreement Status |

|Comments |

| |

|Child Health Corporation of America (CHCA) |

|Project Sponsor |

| |

| |

|Children’s Hospitals Neonatal Consortium (CHNC) |

|Project Sponsor – Subject Matter Experts |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

10. Realm

Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Realm”

| | |

|Universal |Realm Specific (if checked, select from list below) |

| | |

| | |

| |US |

| | |

| | |

| |Other [Enter name of HL7 affiliate] |

| | |

11. Roadmap Reference

Click here to go to Appendix A for more information regarding this section. For more detail regarding the Roadmap Strategies, go to: . Project Insight: Enter into “Roadmap Reference”.

|Check which Roadmap Strategy best relates to your project. |

| |

|Expand, reinvigorate, and streamline HL7’s production, processes, technologies and products |

| |

| |

|Evaluate HL7’s competitive environment and define HL7’s roles, positions and actions |

| |

| |

|Enhance communication and outreach: make HL7 more useable, useful and understandable and share the ideas worldwide |

| |

| |

|Embrace EHR/Electronic Health Record System (ERH-S)/Personal Health Record (PHR) and Public Health Management capabilities as the focal point of |

|technical development of health informatics standards |

| |

| |

|Connect to the clinicians, an essential HL7 community. |

| |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download