Project Scope Statement2015 Version

Release 1

HL7 Project Management OfficeProject Services Work Group

Point of Contact Name and Email:David Hamill (pmo@hl7.org)

Co-Chairs of Project Services Work Group: http://www.hl7.org/Special/committees/projectServices/leadership.cfm

Publication Date: January, 2015

URL to download document: http://www.hl7.org/permalink/?ProjectScopeStatement

For prior versions of this document refer to:

http://www.hl7.org/Special/committees/projectServices/docs.cfm

The objective of this document is to communicate the type of activities a group is undertaking to achieve specific objectives or to produce specific work products. It’s intended for projects to produce standards or Implementation Guides as well as infrastructure projects.

document.docx 2015 Release Page 1 of 6© 2023 Health Level Seven® International.  All rights reserved

Template Usage Information: Replace Highlighted Courier New text with appropriate content. To use Track Changes, turn off “protection” by clicking on Tools > Unprotect Document; in Word 2010, select Review>Track

Changes For assistance in completing each section, refer to Appendix A. Information on 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 and ID

Click here to go to Appendix A for more information regarding this section.An ID will be assigned by Project Insight

Model Automatic eXchange (MAX) for UML Models R2 Project ID:TSC Notification Informative/DSTU to Normative Date :

2. Sponsoring Group(s) / Project TeamClick here to go to Appendix A for more information regarding this section.Primary Sponsor/Work Group (1 Mandatory) CIC WGCo-Sponsor Work Group(s) EST WG, Publishing WG

Co-Sponsor Group Approval Date Co-Sponsor Approval Date CCYY-MM-DDIndicate the level of involvement that the co-sponsor will have for this project:

Request formal content review prior to ballotRequest periodic project updates. Specify period: Monthly, at WGMs, etc.Other Involvement. Specify details here: Enter other involvement here

Project Team:Project facilitator (1 Mandatory) AbdulMalik ShakirOther interested parties and their roles EHR WG, Andy Stechishin (publishing)Multi-disciplinary project team (recommended)

Modeling facilitator Michael van der Zel (development)Publishing facilitator Andy StechishinVocabulary facilitatorDomain expert rep Anita Walden, Jay LyleBusiness requirement analyst AbdulMalik ShakirConformance facilitator (for IG projects)Other facilitators (SOA, etc) Salimah Shakir (documentation)

Implementers (2 Mandatory for DSTU projects)FHIR Project Note: The implementer requirement will be handled by the “balloting” project. Therefore work groups do not fill out the above section. However, feel free to list implementers specific to your work group’s resources if you know of any.1) Tuberculosis DAM2) Child Health DAM

3. Project Definition3.a.Project Scope

Click here to go to Appendix A for more information regarding this section and FHIR project instructions.This scope of this project is to prepare the MAX tool for deployment and use within HL7. Development of the MAX tool is complete and now needs to be documented, managed, and made generally available.

3.b.Project NeedClick here to go to Appendix A for more information regarding this section and FHIR project instructions.The Clinical Interoperability Council (CIC) and Electronic Service and Tooling (EST) Workgroups are co-sponsors of the Model Automated Exchange (MAX) toolkit project. The goal of the MAX toolkit project is to enable the import, export, and round-tripping of a user defined subset of model elements specified in a UML modeling tool.document.docx 2015 Release Page 2 of 6

© 2023 Health Level Seven® International.  All rights reserved

3.c.Success CriteriaClick here to go to Appendix A for more information regarding this section and FHIR project instructions.This project will be successful when the MAX tool is available for the HL7 community with supporting documentation.

3.d.Project RisksClick here to go to Appendix A for more information regarding this section.

Risk Description: Identify any known risks at this time.Impact: Critical Serious Significant Low

Likelihood: High Med Low

Risk Type: Requirements Resources Social-Political Technology

Risk To HL7: Internal to HL7 External to HL7

Mitigation Plan: Document the mitigation plan.Copy this entire table as needed to define multiple project risks.

3.e. Security RisksClick here to go to Appendix A for more information regarding this section.

Will this project produce executable(s), for example, schemas, transforms, stylesheets, executable program, etc. If so the project must review and document security risks.

Yes No Unknown

3.f. External DriversClick here to go to Appendix A for more information regarding this section.Describe any external schedules or calendars which may not be known outside of the project team that are driving target dates for this project.

3.g.Project Objectives / Deliverables / Target DatesWithin each row, enter the explicit work product(s) / objective(s). Indicate their target date at the right in WGM/Ballot Cycle format. Include the project end date as the last objective (for standards projects, the end date will be the projected ANSI approval date).Click here for further information, FHIR project instructions, and an EXAMPLE

Target Date (in WGM or ballot cycle format, e.g.‘2010 Sept WGM’ or‘2010 Jan Ballot’)

Enter objective/deliverable here.All planned ballots and their target dates should be includedThe example below is a "DSTU to Normative" path Enter Target DatePrepare documentation of the tool – first draft 2015 May WGMDocumentation of the tool – final 2015 Sep WGMPrepare tutorial 2015 Sep WGMMove source code (now part of EHR project) to MAX Project @ GForge

2015 May WGM

Make it available from the (tooling page of the) HL7 main website www.hl7.org/max

2015 Sep WGM

Cleanup “old” wiki pages 2015 Sep WGMPilot it to develop a DAM TB (CIC) 2016 Jan WGM

Project End Date (all objectives have been met) 2016 Jan WGM

3.h. Common Names / Keywords / AliasesClick here to go to Appendix A for more information regarding this section.

MAX, DAM. DCM. Model Export. UML. Spreadsheet

3.i. LineageClick here to go to Appendix A for more information regarding this section.This is phase 2 of the MAX project (id: 742). The MAX project was a tool document.docx 2015 Release Page 3 of 6

© 2023 Health Level Seven® International.  All rights reserved

development project, this project is a tool deployment project.http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=742

3.j. Project RequirementsClick here to go to Appendix A for more information regarding this section.To be determined as part of project initiation.

3.k.Project DependenciesClick here to go to Appendix A for more information regarding this section.None

3.l. Project Document Repository LocationClick here to go to Appendix A for more information regarding this section.The project will update the “old” wiki page for all project related documents.http://wiki.hl7.org/index.php?title=MAX_-_Model_Automated_eXchange

3.m. Backwards CompatibilityAre the items being produced by this project backward compatible? Yes No Unknown N/A

For V3, are you using the current data types?(Refer to TSC position statement on new projects using R2B for more information on the current V3 data types)

Yes No

If you check 'No' please explain the reason:

If desired, enter additional information regarding Backwards Compatibility.

3.n.External VocabulariesWill this project include/reference external vocabularies? Yes No Unknown N/AIf yes, please list the vocabularies:

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

Non Product Project- (Educ. Marketing, Elec. Services, etc.) V3 Domain Information Model (DIM / DMIM)Arden Syntax V3 Documents – Administrative (e.g. SPL)Clinical Context Object Workgroup (CCOW) V3 Documents – Clinical (e.g. CDA)Domain Analysis Model (DAM) V3 Documents - KnowledgeElectronic Health Record (EHR) Functional Profile V3 Foundation – RIMLogical Model V3 Foundation – Vocab Domains & Value SetsV2 Messages – Administrative V3 Messages - AdministrativeV2 Messages - Clinical V3 Messages - ClinicalV2 Messages - Departmental V3 Messages - DepartmentalV2 Messages – Infrastructure V3 Messages - InfrastructureFHIR Resources V3 Rules - GELLOFHIR Profiles V3 Services – Java Services (ITS Work Group)New/Modified/HL7 Policy/Procedure/Process V3 Services – Web Services (SOA)New Product DefinitionNew Product Family

This is a new product within the electronic services family of products.

5. Project Intent (check all that apply)Click here to go to Appendix A for more information regarding this section and FHIR project instructions.

Create new standardRevise current standard (see text box below)Reaffirmation of a standardNew/Modified HL7 Policy/Procedure/ProcessWithdraw an Informative DocumentN/A (Project not directly related to an HL7 Standard)

Supplement to a current standard

Implementation Guide (IG) will be created/modified

Project is adopting/endorsing an externally developed IG: Specify external organization in Sec. 6 below;Externally developed IG is to be (select one):Adopted - OR - Endorsed

document.docx 2015 Release Page 4 of 6© 2023 Health Level Seven® International.  All rights reserved

If revising a current standard, indicate the following:- Name of the standard being revised- Date it was published (or request for publication, or ANSI designation date)- Rationale for revision- The relationship between the new standard and the current standard (is it

designed to replace the current standard, a supplement to the current standard, etc.)

5.a.Ballot Type (check all that apply)Click here to go to Appendix A for more information regarding this section and FHIR project instructions.

Comment OnlyInformativeDSTU to Normative

Normative (no DSTU)Joint Ballot (with other SDOs or HL7 Work Groups)N/A (project won’t go through ballot)

If necessary, add any additional ballot information here. If artifacts will be jointly balloted with other HL7 Work Groups or other SDOs, list the other groups.

5.b.Joint Copyright Click here to go to Appendix A for more information regarding this sectionCheck this box if you will be pursuing a joint copyright. Note that when this box is checked, a Joint Copyright Letter of Agreement must be submitted to the TSC in order for the PSS to receive TSC approval.

Joint Copyrighted Material will be produced

6. Project Logistics

6.a.External Project CollaborationClick here to go to Appendix A for more information regarding this section and FHIR project instructions.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.For projects that have some of their content already developed:How much content for this project is already developed? Indicate % hereWas the content externally developed (Y/N)? If Yes, list developersDate of external content review by the ARB? Approval date CCYY-MM-DDIs this a hosted (externally funded) project? (not asking for amount just if funded)

Yes No

6.b.RealmClick here to go to Appendix A for guidelines regarding choosing Universal or Realm Specific.

Universal Realm Specific Check here if this standard balloted or was previously approved as realm specific standard

Enter “U.S.” or name of HL7 affiliate(s) here. For projects producing deliverables applicable to multiple realms, document those details here.

6.c.Project Approval DatesClick here to go to Appendix A for more information regarding this section.Affiliate/US Realm Task Force Approval Date (for US Realm Specific Projects) USRTF Approval Date CCYY-MM-DDSponsoring Work Group Approval Date WG Approval Date 2015-01-22Steering Division Approval Date SD Approval Date CCYY-MM-DD

PBS Metrics and Work Group Health Reviewed? (required for SD Approval) Yes NoFHIR Project: FHIR Management Group Approval Date FMG Approval Date CCYY-MM-DD

Technical Steering Committee Approval Date TSC Approval Date CCYY-MM-DDTSC has received a Copyright/Distribution Agreement (which contains the verbiage outlined within the SOU), signed by both parties.

Yes No

document.docx 2015 Release Page 5 of 6© 2023 Health Level Seven® International.  All rights reserved

6.d.Stakeholders / Vendors / ProvidersClick here to go to Appendix A for more information regarding this section

This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballotsStakeholders 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

(SDOs) Clinical Decision Support

Systems Healthcare Institutions (hospitals, long term

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.

6.e.Synchronization With Other SDOs / ProfilersClick here to go to Appendix A for more information regarding this section Check all SDO / Profilers which your project deliverable(s) are associated with.

ASC X12 CHA LOINC AHIP DICOM NCPDP ASTM GS1 NAACCR BioPharma Association (SAFE) IEEE Object Management Group (OMG) CEN/TC 251 IHE The Health Story Project CHCF IHTSDO WEDI CLSI ISO Other (specify below)

For standards and implementation guides (IG) being developed by this project, please indicate: - Similarities to standards or IGs from the checked SDO/Profilers - How they will be different - How overlaps will be coordinated with the checked SDO/Profilers - Why coordination is not needed with other SDOs/Profilers

document.docx 2015 Release Page 6 of 6© 2023 Health Level Seven® International.  All rights reserved