Template Usage Information:
Enter the name of the project here: Characteristics of Realm Transferable Standards Specifications
Complete this section for all “Direct to Normative” ballot projects and when a project proceeds from “Informative to Normative” or “STU to Normative”.
Forward PSS to the TSC (via tscpm@HL7.org); this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.
TSC Notification: Informative/STU to Normative
Date: Submission date
- or - Direct to Normative (no STU) (includes reaffirmations)
Identify ISO, IEC or ISO/IEC standard to be adopted in text box below
Enter info here if an ISO, IEC, or ISO/IEC Standard is to be adopted as an American National Standard; Enter the designation of the standard(s) to be adopted:
Includes text from ISO, IEC or ISO/IEC standard: Check here if this standard includes excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption.
Select the unit of measure used in the standard; if no measurements are in the standard, select N/A
Investigative Project (aka PSS-Lite)
Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition. Sections 1-Project Name, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3e-Project Objectives/Deliverables/Target Dates, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required for Investigative Project. Investigative Project specific instructions are highlighted in yellow. An investigative project must advance in two WGM cycles, requiring a full scope statement. Otherwise the project will be closed.
Primary Sponsor/Work Group
Architecture Review Board
Co-sponsor Work Group(s):(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)
|Indicate the level of involvement that the co-sponsor will have for this project:|
|Y||Request formal content review prior to ballot|
|Y||Request periodic project updates. Specify period||WGM|
|?||Other Involvement. Specify details here:||Enter other involvement here|
All names should have confirmed their role in the project prior to submission to the TSC.
Project facilitator (1Mandatory)
Other interested parties and their roles
Standards Governance Board (SGB), HL7 Terminology Authority (HTA)
Multi-disciplinary project team (recommended)
Domain expert rep
Business requirement analyst
Conformance facilitator (for IG projects)
Other facilitators (SOA, etc)
Implementers (2Mandatory for STU 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.
Describe the project; include what is expected to be accomplished/delivered along with specified features and functions. Include whether the deliverable(s) are universal, realm specific or applicable to various realms. Be sure to spell out all acronyms as these are carried forward to the NIB (Notice of Intent to Ballot) for ballot announcements..
The purpose of the proposed project is to provide guidance to HL7 International on what the distinguishing characteristics are for a standards specification to be transferable, and readily implementable, across countries.
The scope of the project is the production of a guidance document for all current and future international standards work done in HL7. The intent is not to create a difficult process or barriers to standards development, but rather to make it easier for the work being done to be more internationally transferable where appropriate. The scope may also include potential criteria for assessing conformity of candidate international specifications to that guidance. It is proposed that the proposed owner / accountability for application of the document be the Standards Governance Board.
This information is required by ANSI for all ballots. Briefly explain the reason behind the need for this project. This may be related to legislative requirements, industry need, or similar justifications.
HL7, as an SDO established in the USA under ANSI rules, has encouraged international participation in order to:
- enrich the standards it produces;
- make them applicable and useful globally.
In the last two HL7 WGM's it has become increasingly clear to that there is a lack of clarity or consistent understanding on what it means to be developing standards intended for international adoption. Given that HL7 is positioned as an International SDO, many of us can be forgiven for presuming that all work done within the SDO should be developed in a way that allows the specifications to be transferable to, and usable by, other countries. However, practically speaking, it is also clear that the nature of the work being done is driven by the compelling need of participant communities to achieve strategic objectives in terms of their operational context. Given the preponderance of member representation from the United States, combined with the incentives, directives and accompanying (welcome) funding arising from ONC, and proposed rule making by HHS, this often means the business problems to be solved have a distinctly US national, rather than international, perspective to them.
While International Affiliate members play very key and supportive roles in the work being done, and while International Affiliates are able to vote on resulting work, these alone are not enough to ensure that specifications are readily "transferable" to other national realms. There seems to be a lack of organizational guidance and "mindfulness", in some cases, about what the characteristics of a truly international standards specification should be (including both what is and is not desirable).
Another side effect of this is that, while many international participants successfully and productively inform the work, other international countries still see the work as purely realm centric, and not applicable or transferable. This has a particular impact on the international adoption of FHIR.
A contributing factor may be that, while external countries are distinctly and formally recognized, the USA as a “realm” is not clearly distinguished as a distinct international member body (the US Realm Steering Committee notwithstanding).
While implementation guides are used to contextualize the implementation of specifications, these guides are also often realm-specific. While International Affiliates are responsible for implementation guides for their own realms, there are IG's that are being balloted at the international level that are not actually meant to be adopted universally. However, the International Patient Summary joint project between HL7 and CEN 251 presents one example of an HL7 project that successfully involved a broader international perspective. There are also opportunities to work with other international organizations such as IHE.
As seen in recent FHIR ballots, many IG's relevant to the United States are balloted on the normative track without considering international requirements. Building IGs from a more international perspective may reduce the number of identical implementation guides.
The goal of this project is to address the need for HL7 to:
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. Refer to the Cookbook for Security Considerations for additional guidance, including sample spreadsheets that may be used to conduct the security risk assessment.
Describe any external schedules or calendars which may not be known outside of the project team that are driving target dates for this project..
Within 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).
Target Date(in WGM or ballot cycle format, e.g.
‘2017 Sept WGM’ or
‘2017 Jan Ballot’)
Enter objective/deliverable here.
All planned ballots and their target dates should be included
The example below is a "STU to Normative" path
Enter Target Date
First draft of guidance document
2020 January Ballot
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.
What common name does your group use to refer to the product(s) produced? What alternative names, aliases and keywords does your group use to refer to the product(s) that will be produced? Some examples: C-CDA, LRI, eDOS.
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:
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
A template to create a Project Page on the HL7 Wiki is available at: http://wiki.hl7.org/index.php?title=Template:Project_Page.
|Enter the SPECIFIC URL of the HL7-MANAGED SITE where supporting project documents, deliverables, ballot reconciliation work and other project information will be kept.|
Are the items being produced by this project backward compatible?
If you check 'Yes' please indicate the earliest prior release and/or version to which the compatibility applies:
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.
Will this project include/reference external vocabularies?
If Yes, please enter the vocabularies:
V2 Messages – Administrative
Clinical Information Modeling Initiative (CIMI)
V2 Messages - Clinical
Clinical Context Object Workgroup (CCOW)
V2 Messages - Departmental
Domain Analysis Model (DAM)
V2 Messages – Infrastructure
Electronic Health Record (EHR) Functional Profile
V3 Domain Information Model (DIM / DMIM)
V3 Documents – Administrative (e.g. SPL)
FHIR Implementation Guide (enter FHIR product version below)
V3 Documents – Clinical (e.g. CDA)
FHIR Profiles (enter FHIR product version below)
V3 Documents - Knowledge
V3 Foundation – RIM
Guidance (e.g. Companion Guide, Cookbook, etc)
V3 Foundation – Vocab Domains & Value Sets
V3 Messages - Administrative
V3 Messages - Clinical
New Product Definition (please define below)
V3 Messages - Departmental
New Product Family (please define below)
V3 Messages - Infrastructure
Non Product Project - (Educ. Marketing, Elec. Services, etc.)
V3 Rules - GELLO
V3 Services – Java Services (ITS Work Group)
Creating/Using a tool not listed in the HL7 Tool Inventory
V3 Services – Web Services (SOA)
If you checked New Product Definition or New Product Family, please define below:
For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?
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;
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:||Name of the standard|
|- Date it was published (or request for publication, or ANSI designation date)||Date published ( or request for publication, or ANSI designation date)|
|- Rationale for revision||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.)||Relationship between the new standard and the current standard.|
Comment (aka Comment-Only)
Joint Ballot (with other SDOs)
N/A (project won’t go through ballot)
STU to Normative - OR -
Normative (no STU)
If necessary, add any additional ballot information here. If artifacts will be jointly balloted with other SDOs, list the other groups.
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?
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 % here
Was the content externally developed ? :
If Y, list Developers
Is this a hosted (externally funded) project? (not asking for amount just if funded)
- OR -
Check here if this standard balloted or was previously approved as realm specific standard
"U.S" or HL7 Affiliates
Enter “U.S.” or name of HL7 affiliate(s) here. Provide explanation/justification of realm selection. 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.
This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballots
Clinical and Public Health Laboratories
Clinical and Public Health Laboratories
Quality Reporting Agencies
Local and State Departments of Health
Health Care IT
Medical Imaging Service
Standards Development Organizations (SDOs)
Clinical Decision Support Systems
Healthcare Institutions (hospitals, long term care, home care, mental health)
Other (specify in text box below)
Other (specify in text box below)
Other (specify below)
Other: Indicate other stakeholders, vendors or providers not listed above.
Click here to go to HL7 Project Scope Statement Instructions#Appendix A for more information regarding this section.
Approvals are by simple majority vote of the approving body
Sponsoring Work Group Approval Date:
WG Approval Date
Administrative review – in parallel with Work Group Approval
Co-Sponsor Group Approval Date
Family Management Group Approval Date(s)
CIMI Projects: CIMI Management Group
CIMI MG Approval Date
CDA Projects: CDA Management Group
CDA MG Approval Date
FHIR Projects: FHIR Management Group
FMG Approval Date
V2/Publishing Projects: V2 Management Group
V2 MG Approval Date
US Realm Projects: US Realm Steering Committee Approval
USRSC Approval Date
Affiliate Specific Projects: Affiliate Approval Date
Affiliate Approval Date
Submit PSS to Steering Division after all of the above approvals are received
Steering Division (of Primary Sponsor WG) Approval Date:
SD Approval Date CCYY-MM-DD
|CCYY-MM-DD or indicate N/A|
ARB and Steering Division approval may be in parallel
Architectural Review Board Approval Date:
(required for externally developed content)
ARB Approval Date
|CCYY-MM-DD or indicate N/A|
If applicable, TSC has received a Joint Copyright/Distribution Agreement (containing the verbiage outlined within the SOU),
Technical Steering Committee Approval Date:
TSC Approval Date