Business Project Value Templates by ani12122

VIEWS: 11 PAGES: 4

More Info
									                                                                                                   Health Level Seven®, Inc.
                                                                                                   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@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.
   HL7 Templates Registry Business Requirements Analysis                                                                  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-

     1.a. Implementation Guide
Indicate if you’re creating/modifying an implementation guide (in addition to a standard or just on it’s own). Project Insight: This information
will appear in the ―Implementation Guide?‖ radio button.
       Implementation Guide? Check this box if you’re creating an 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

     2.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):
Develop consensus about the necessary business processes and policies to register artifacts in a Template
Registry to be developed in a subsequent project.


         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).        See sections 5 and 6 below — these demonstrate the need for public documents.


3. Sponsoring Group(s)
Click here to go to Appendix A for more information regarding this section.
Primary Sponsor/Work Group (1 Mandatory)                        Templates Work Group
Co-sponsor Work Group(s)                                        Structured Documents, Patient Care, Tooling, Vocabulary
Project Team                                                                      Name and E-mail Address
Project facilitator (1 Mandatory)                               Mark Shafarman – mark.shafarman@earthlink.net
                                                                Keith Boone, Jane Curry, Ravi Natarajan, Kevin Coonan; William
                                                                Goosen, Isabelle de Jaeger, Sarah Ryan
Other interested parties
7b3d8868-3f82-4495-b221-b94f184030d3.doc                                             2009 Jan Release                                Page 1 of 4
                                                                                                 Health Level Seven®, Inc.
                                                                                                 Project Scope Statement

Multi-disciplinary project team (recommended)
  Modeling facilitator                                        Jane Curry, Keith Boone
  Publishing facilitator                                      NA at this time
  Vocabulary facilitator                                      Jane Curry, Sarah Ryan
                                                                  Jos Baptist as liaison for NICTZ
                                                                  Isabelle de Jaeger as liaison for CIDSC
                                                                  Bob Yencha as liaison for HITSP
                                                                  Ravi Natarajan as liaison for NHS
                                                                  Keith Boone as liaison for IHE
                                                                  Lisa Carnahan as liaison for NIST
                                                                  Dipak Kalra as liaison for CEN-13606
                                                                  William Goossen as liaison for ISO-new DCM project
                                                                  David Rowed as liaison for NEHTA
   Domain expert rep                                              Sarah Ryan as liaison for VHA
   Data Analyst facilitator
   Business requirement analyst
   Requirements process facilitator

Implementers (2 Mandatory for DSTU projects):
1)
2)

4. Project Scope
Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Description”.
Business Requirements Analysis sufficient to ensure template artifacts can be successfully registered and
maintained throughout their life cycle.

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”.
         Inventory and gap analysis of available ―work-in-progress‖ and a gap June 30, 2009
          analysis describing what is similar and what is missing
         Use Case diagrams with Role definitions
         Activity Diagram depicting the types of interactions between a user and a
          templates registry application and any other dependent tool components
          necessary to successful register, search for and retrieve HL7 templates.
         Information model depicting necessary metadata to register authorized
          users and then to register templates and manage them throughout their life
          cycle.
         Template artifacts of various formats must be able to be registered
         State transition diagram depicting all the states a template can go through
          and which processes invoke the state transition.
         Definition of any policies that must be agreed to before a Template
          Registry can be realized.
         Align with the output from the tooling functional requirements for a
          Templates Registry from the NLM project previously delivered and the
          Templates DSTU.
         Follow the recommendations emerging from the ArB definition of the
          Services Aware Enterprise Architecture Framework.



7b3d8868-3f82-4495-b221-b94f184030d3.doc                                           2009 Jan Release                               Page 2 of 4
                                                                                                  Health Level Seven®, Inc.
                                                                                                 Project Scope Statement

6. Project Dependencies
Click here to go to Appendix A for more information regarding this section. Project Insight: Enter into “Dependencies & IDs”.
         Output from this project will be input into a Templates Registry development project                             ID
          which may be a sub-project of a Tooling Work Group sponsored Shared Artifact
          Repository Project.
         National and international implementation initiatives (NHS, Infoway, NCTIZ, CEN,
          NEHTA, US National Interoperability Initiative-HITSP, ISO, IHE, NIST)
         OHT NHS sponsored Static Model Designer phase 2
         CDISC Meta-Data Repository / NCI caDSR
         OHT UML Modeling Project
         OHT Architecture Project specifying interfacing and integration constraints between
          OHT tools.

7. Project Approval Dates
Sponsoring Group approval Date Project Insight: Enter into “Start Date”.                            Sponsoring Group Approval Date
Steering Division Approval Date                                                                     SD Approval Date
Technical Steering Committee Approval Date                                                          TSC Approval Date
PMO Approval Date                                                                                   PMO Approval Date

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

     8.a. Project Schedule


     8.b. Project Resources


     8.c. Project Budget


     8.d. Ballot Plan - general
      Comment Only                                                             Normative
      Informative
      DSTU                                                                     Joint Ballot (with other SDOs or HL7 Work Groups)
Add any additional ballot information here. If artifacts will be jointly balloted with other HL7 Work Groups or other
SDOs, list the other groups:
     8.e. Ballot Plan for cross-cutting Projects


     8.f. Industry Outreach


     8.g. Success Criteria
Full participation from interested parties

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




7b3d8868-3f82-4495-b221-b94f184030d3.doc                                           2009 Jan Release                                Page 3 of 4
                                                                                                 Health Level Seven®, Inc.
                                                                                                Project Scope Statement

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:
http://www.hl7.org/documentcomments/index.cfm. Project Insight: Enter into “Roadmap Reference”.
Check which Roadmap Strategy best relates to your project.
      1.   Expand, reinvigorate, and streamline HL7’s production, processes, technologies and products
      2.   Evaluate HL7’s competitive environment and define HL7’s roles, positions and actions
      3.   Enhance communication and outreach: make HL7 more useable, useful and understandable and share the ideas worldwide
      4.   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
      5.   Connect to the clinicians, an essential HL7 community.




7b3d8868-3f82-4495-b221-b94f184030d3.doc                                          2009 Jan Release                                  Page 4 of 4

								
To top