DOC

Project Scope Statement 2010 Jan Release - Template Only - HL7

By Kathryn Howard,2014-05-28 14:34
9 views 0
Project Scope Statement 2010 Jan Release - Template Only - HL7

    ?Health Level Seven, Inc.

    Project Scope Statement

Template Usage Information:

    ; Replace Highlighted Courier New 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@HL7.org

    1. Project Name, ID and Products

    The name should be concise, based on the objective and unique among all other projects the group takes on. An ID will be assigned Project Insight: Enter into “Project Name” and “Product Type”. by Project Insight Click here to go to Appendix A for more information regarding this section.

    Enter the name of the project here. Project ID:

     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 -

    2. Project Intent

    Click here to go to Appendix A for more information regarding this section. Indicate if/how this project affects a standard. Project Insight: Enter into “Project Intent”. Reaffirmation of a standard Create new standard Withdraw current standard Revise current standard N/A (Project not directly related to an HL7 Standard) Supplement to a current standard Implementation Guide will be created/modified

    2.a. Ballot Type

    If applicable, Indicate the type of balloting the deliverables will go through. Project Insight: Enter into “Type”; additional information can be entered into the Misc. Notes text box.

     Comment Only Normative Informative Joint Ballot (with other SDOs or HL7 Work Groups) DSTU N/A (project won’t go through ballot) Add any additional ballot information here. If artifacts will be jointly balloted

    with other HL7 Work Groups or other SDOs, list the other groups.

    2.b. Public Document

    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). 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). Project Insight: Add a comment in Project Insight‟s Misc. Notes text box indicating a public document will be created. Public Document(s) to be created?

    3. Sponsoring Group(s) / Project Team Click here to go to Appendix A for more information regarding this section.

    Enter primary Sponsor/Work Group here. Primary Sponsor/Work Group (1 Mandatory)

    Co-sponsor Work Group(s)

Project Team:

    Enter Project Facilitator name/email here. Project facilitator (1 Mandatory)

    Other interested parties

    211282320.doc 2010 Jan Release Page 1 of 3

    ?Health Level Seven, Inc.

    Project Scope Statement

Multi-disciplinary project team (recommended)

     Modeling facilitator

     Publishing facilitator

     Vocabulary facilitator

     Domain expert rep

     Data Analyst facilitator

     Business requirement analyst

     Requirements process facilitator

Implementers (2 Mandatory for DSTU projects):

    1)

    2)

    4. Project Definition

    4.a. Project Scope

    Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Description”. Enter a description of the project that delineates what it is expected to

    accomplish.

    4.b. Project Need

    This information is required by ANSI for all ballots. Project Insight: Enter into “Description”.

    Briefly explain the reason behind the need for this project. This may be related to

    legislative requirements, industry need, or similar justifications.

    4.c. Success Criteria

    Project Insight: Enter into “Objectives and Deliverables”.

    Indicate the success criteria for the project.

    4.d. Project Objectives / Deliverables / Target Dates

    Click here for further information and examples. Project Insight: Enter into “Objectives and Deliverables”. Within each row, enter the explicit work product(s) / objective(s). Indicate their target date at the right in (in WGM or Target Date WGM/Ballot Cycle format. Include the project end date as the last objective. ballot cycle format, e.g. For standards project, this date will quite frequently be the projected ANSI approval date. 2010 Sept WGM or 2010 Jan Ballot) Enter objective/deliverable here. Enter Target Date

    Project End Date (all objectives have been met) Enter Pjt End Date

    4.e. Project Dependencies

    Project Insight: Enter into “Dependencies”.

    Enter any dependencies or the name & Project Insight ID of project(s) that this

    project is dependent upon to achieve its objectives.

    4.f. Project Document Repository Location Indicate where can one go to find deliverables/documents created by the project team. Project Insight: Enter into “Misc. Notes”. Enter the location where supporting project documents and other project information will be kept, e.g. : HL7 Wiki, TSC Wiki, GForge, Project Insight, the Work Group’s

    web page on www.HL7.org, etc.

    4.g. Backwards Compatibility

    211282320.doc 2010 Jan Release Page 2 of 3

    ?Health Level Seven, Inc.

    Project Scope Statement

     Indicate the backward compatibility of the expected project artefacts/deliverables, if known. Project Insight: Backwards Compatibility; enter additional information into “Misc. Notes”.

    Yes No Don’t Know N/A Are the items being produced by this project backward compatible?

    If desired, enter any additional information regarding Backwards Compatibility. 5. Project Approval Dates

    Note that the SD and TSC Approval dates don’t need to be captured in this template; this section simply reminds project facilitators about the need to gather SD and TSC approval. SD/TSC approval dates will be entered into Project Insight as they occur.

    Work Group Approval Date Sponsoring Group Approval Date Project Insight: Enter into “Start Date”.

    SD Approval Date Steering Division Approval Date

    TSC Approval Date Technical Steering Committee Approval Date

    6. External Project Collaboration

    Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Collaboration Efforts”. Include SDOs or other external entities you are collaborating with, including

    government agencies as well as any industry outreach. Indicate the nature and

    status of the Memorandum of Understanding (MOU) if applicable.

    6.a. Stakeholders / Vendors / Providers Indicate the associated stakeholders, customers and providers for which this project is intended. Check all that apply. This information is required by ANSI for all ballots. Project Insight: Enter into “Stakeholders / Customers / Providers”.

    Stakeholders Vendors Providers Clinical and Public Health Laboratories Pharmaceutical Clinical and Public Health Laboratories Immunization Registries EHR, PHR Emergency Services Quality Reporting Agencies Equipment Local and State Departments of Health Regulatory Agency Health Care IT Medical Imaging Service Standards Development Organizations Clinical Decision Support Healthcare Institutions (hospitals, long term (SDOs) Systems care, home care, mental health) Payors Lab Other (specify in text box below) Other (specify in text box below) HIS N/A N/A Other (specify below) N/A

    Other: Indicate other stakeholders, vendors or providers not listed above.

    7. Realm

    Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Realm” Realm Specific (Enter U.S.or name of HL7 affiliate here) Universal

    8. Roadmap Reference

    Click here to go to Appendix A for more information regarding this section. For more detail regarding the Roadmap Strategies, go to: http://www.hl7.org/documentcomments/index.cfm. Project Insight: Enter into “Roadmap Reference”.

    Check which Roadmap Strategy best relates to your project. A. Lead the development of global technical and functional health informatics standards. B. Streamline the HL7 standards development process. C. Facilitate HL7 standards adoption and implementation. D. Define an overarching and internally consistent interoperability framework. E. Ensure broad and encompassing stakeholder engagement in the standards development process. F. Align HL7's business and revenue models to be responsive to national bodies while supporting global standards development. G. None of the above apply to this project.

    211282320.doc 2010 Jan Release Page 3 of 3

Report this document

For any questions or suggestions please email
cust-service@docsford.com