1. Project Name and ID
Project Name:Align V2 Errata - Addenda - technical corrections
2. Sponsoring Group(s) / Project Team
2.a.Primary Sponsor/Work Group:
|Infrastructure and Messaging (InM)|
(Enter co-sponsor approval dates in Section 6.c Project Approval Dates)
Indicate the level of involvement that the co-sponsor will have for this project:
2.c Project Team
Project facilitator (1Mandatory)
<Interested Party & Role>
Multi-disciplinary project team (recommended)
Domain expert rep
Business requirement analyst
Conformance facilitator (for IG projects)
Other facilitators (SOA, etc)
Implementers (2 Mandatory for STU projects):N/A
2. Project Definition
2.a. Project Scope
V2 Errata - Addenda - technical corrections.
2.b. Project Need
As a customer I would be miffed if I searched for and downloaded the " HL7 Version 2.4 Specification Errata"
and later found out that there were two technical corrections as well as HL7 Version 2.4 Messaging Addenda that were separate.
This projects to the customer that HL7 does not have a consistent way to handle the discovered issues.
2.c. Security Risks
Will this project produce executable(s), for example, schemas, transforms, style sheets, executable program, etc.
If so the project must review and document security risks.
2.d. External Drivers
Describe any external schedules or calendars which may not be known outside of the project team that are driving target dates for this project.
2.e. Project Objectives / Deliverables / Target Dates
|Evaluate the scope of the problem|
Validate the intent with interested parties
Make corrections and Publish
Project End Date (all objectives have been met)
Note: For PSS-Lite/Investigative Project, End date must be no more than two WGM cycles, e.g. project initiated at January WGM must complete investigation by September WGM.
2.f. Common Names / Keywords / Alias
|Errata, addenda, technical correction|
If your project creates a Post-Release 1 version; indicate the name of the prior product and if it is supplanting, replacing or coexisting with a previous release.
2.h. Project Dependencies
Enter any dependencies or the name & Project Insight ID of project(s) that this project is dependent upon to achieve its objectives. Projects and their Project Insight IDs can be found via http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?ref=common
2.i. Project Document Repository Location
Enter the SPECIFIC URL where supporting project documents, deliverables, ballot reconciliation work and other project information will be kept.
2.j. Backwards Compatibility
Are the items being produced by this project backward compatible?
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)
If you check 'No' please explain the reason:
If desired, enter additional information regarding Backwards Compatibility.
2.k. External Vocabularies
Will this project include/reference external vocabularies?
If yes, please list the vocabularies:
Products (check all that apply)
Non Product Project - (Educ. Marketing, Elec. Services, etc.)
V3 Domain Information Model (DIM / DMIM)
V3 Documents – Administrative (e.g. SPL)
Clinical Context Object Workgroup (CCOW)
V3 Documents – Clinical (e.g. CDA)
Domain Analysis Model (DAM)
V3 Documents - Knowledge
Electronic Health Record (EHR) Functional Profile
V3 Foundation – RIM
V3 Foundation – Vocab Domains & Value Sets
V2 Messages – Administrative
V3 Messages - Administrative
V2 Messages - Clinical
V3 Messages - Clinical
V2 Messages - Departmental
V3 Messages - Departmental
V2 Messages – Infrastructure
V3 Messages - Infrastructure
FHIR Implementation Guide
V3 Rules - GELLO
V3 Services – Java Services (ITS Work Group)
V3 Services – Web Services (SOA)
New Product Definition
New Product Family
If you checked New Product Definition or New Product Family, please define below:
Project Intent (check all that apply)
Create new standard
Supplement to a current standard
Revise current standard (see text box below)
Implementation Guide (IG) will be created/modified
Reaffirmation of a standard
Project is adopting/endorsing an externally developed IG:
New/Modified HL7 Policy/Procedure/Process
Specify external organization in Sec. 6 below;
Withdraw an Informative Document
Externally developed IG is to be (select one):
White Paper (select one):
Adopted - OR -
Balloted Informative OR
Non-balloted WG White Paper
N/A (Project not directly related to an HL7 Standard)
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.)
4.a. Ballot Type (check all that apply)
Comment (aka Comment-Only)
Joint Ballot (with other SDOs)
N/A (project won’t go through ballot)
STU to Normative - OR -
Normative (no STU)
4.b. Joint Copyright
Check 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?
- Project Logistics
5.a. External Project Collaboration
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:N/A
How much content for this project is already developed?:N/A
Indicate % here
Was the content externally developed (Y/N)? :N/A
If Yes, list developers
Is this a hosted (externally funded) project? :N/A
Universal - OR -
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.
For Investigative projects, indicate if the project is planned to be Realm Specific or Universal, if known. Work Groups are encouraged
designating project a Universal project initially, and discover which Realms can contribute to the work effort during the discovery phase of the project.
Note: This status is subject to change during the investigative process.
5.c. Project Approval Dates
Affiliate Approval Date (for Affiliate Specific Projects):
Affiliate Approval Date CCYY-MM-DD or indicate “N/A”
US Realm Steering Committee Approval Date
USRSC Approval Date CCYY-MM-DD or indicate “N/A”
Sponsoring Work Group Approval Date:
WG Approval Date CCYY-MM-DD
Co-Sponsor Group Approval Date
(Copy this entire row for each co-sponsor; indicate the specific cosponsor that issued approval)
Co-Sponsor Approval Date CCYY-MM-DD
FHIR Project: FHIR Management Group Approval Date:
FMG Approval Date CCYY-MM-DD or “N/A”
Architectural Review Board Approval Date:
ARB Approval Date CCYY-MM-DD or “N/A”
Steering Division Approval Date :
SD Approval Date CCYY-MM-DD
Technical Steering Committee Approval Date:
TSC Approval Date CCYY-MM-DD
TSC has received a Copyright/Distribution Agreement (containing the verbiage outlined within the SOU), signed by both parties.