NOTE : Please spell out all acronyms the first time the acronym occurs. 

For Reaffirmations, please refer to the FAQ within Appendix C of the PSS_with_instructions template for a list of which sections and fields should be completed.

PSS-Lite/Investigative Projects:  Sections surrounded by a BOLD OUTLINE must be completed for approval of "Investigative Projects" (a.k.a PSS-Lite).

  1. Project Name and ID

 

 

Attachments Frequently asked Questions (FAQ) living document

Project ID:

 

 

TSC Notification:  Informative/STU to Normative 

Date: 

 

 

- or -                     Direct to Normative (no STU)       

 

Check this box when the project proceeds from “Informative to Normative” or “STU to Normative” and forward it to the TSC (via tscpm@HL7.org) for notification as this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.

This box should be checked for all “Direct to Normative” ballot projects. 

 

 

Investigative Project

Date : 

Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition.  Sections in bold outline are mandatory for project approval of an investigative project; all other sections are optional. Sections 1-Project Name and Scope, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3g-Project Objective, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required.

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.

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

Primary Sponsor/Work Group
(1 (And Only 1) Allowed)

Attachments Work Group

2.b. Co-sponsor Work Group(s)

Co-sponsor Work Group(s)

(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)

 

Structured Documents Work Group

Indicate the level of involvement that the co-sponsor will have for this project:

x

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

Monthly, at WGMs, etc .

 

Other Involvement. Specify details here: 

Enter other involvement here

2.c. Project Team

All names should have confirmed their role in the project prior to submission to the TSC.

Project facilitator ( 1 Mandatory )

Christol Green

Other interested parties and their roles

 

Multi-disciplinary project team (recommended)

 

Modeling facilitator

Enter a name here (or ask MnM for a name).

Publishing facilitator

Christol Green

Vocabulary facilitator

Enter a name here (or ask Vocab for a name)

Domain expert rep

 

Business requirement analyst

 

Conformance facilitator (for IG projects)

 

Other facilitators (SOA, etc)

 

 

 

Implementers (2 Mandatory 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.

1) 

2) 

  1. Project Definition

3.a. Project Scope

Create an updated Attachments FAQ document.  It will be assembled to share information in anticipation of the potential requirements to be published in the Administrative Simplification; Health Care Claims Attachments (CMS-0053-P) proposed rule. The FAQ may include information about the adopted standards and operating rules for attachments based on statutory requirements introduced in the Health Insurance Portability and Accountability Act (HIPAA) and reinforced in the Affordable Care Act. This FAQ will be a living document with an HL7 link for members to send questions for response.

3.b. Project Need

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.

3.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. Refer to the Cookbook for Security Considerations for additional guidance, including sample spreadsheets that may be used to conduct the security risk assessment .

 

 

Yes

 

 

No

 

 

Unknown

 

3.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.

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

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

Example: Submit for Informative Ballot(First Ballot Cycle)

2018 Sept Ballot

Example: Complete Informative Reconciliation

2018 ?

Example: Submit for 2nd STU Ballot

 

Example: Request informative Publication

2018 Oct WGM

Example: STU Period – 12 months

 

Example: Submit for Normative Ballot

 

Example: Complete Normative Reconciliation

 

Example: Submit Publication Request

2019 ?

Example: Receive ANSI Approval

 

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.

Enter Project End Date

3.f.    Common Names / Keywords / Aliases

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. 

3.g. Lineage

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.

3.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

3.i.    HL7-Managed Project Document Repository Location

Projects must adhere to the TSC's guidelines (which were approved on 2016-04-04 and summarized in Appendix A ).

Enter the SPECIFIC URL of the HL7-MANAGED SITE where supporting project documents, deliverables, ballot reconciliation work and other project information will be kept. A template to create a Project Page on the HL7 Wiki is available at: http://wiki.hl7.org/index.php?title=Template:Project_Page.

3.j.    Backwards Compatibility

Are the items being produced by this project backward compatible?

 

 

Yes

 

 

No

 

 

Unknown

 

X

N/A

 

 

 

 

 

 

 

 

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)

 

 

Yes

 

 

No

 

 

Unknown

 

X

N/A

 

 

 

 

 

 

 

 

If you check 'No' please explain the reason:

If desired, enter additional information regarding Backwards Compatibility.

3.k. External Vocabularies

Will this project include/reference external vocabularies?

 

 

Yes

 

 

No

 

 

Unknown

 

X

N/A

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies:

 

  1. Products (check all that apply)

 

Arden Syntax

 

 

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)

 

FHIR Extensions

 

 

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

 

FHIR Resources

 

 

V3 Foundation – RIM

X

Guidance (e.g. Companion Guide, Cookbook, etc)

 

 

V3 Foundation – Vocab Domains & Value Sets

 

Logical Model

 

 

V3 Messages - Administrative

 

New/Modified/HL7 Policy/Procedure/Process

 

 

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

X

White Paper

 

 

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?

  1. 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;

 

 

 

 

Externally developed IG is to be (select one):

 

White Paper (select one):

 

 

Adopted  - OR -

 

Endorsed

 

X

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.)

5.a. Ballot Type (check all that apply)

 

Comment (aka Comment-Only)

 

 

Joint Ballot (with other SDOs)

X

Informative

 

 

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.

5.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?

 

 

Yes

 

X

No

 

 

  1. Project Logistics

6.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:

How much content for this project is already developed?

Indicate % here

Was the content externally developed (Y/N)? 

If Yes, list developers

Is this a hosted (externally funded) project? 
(not asking for amount just if funded)

 

 

 

 

 

 

 

 

Yes

 

X

No

6.b. Realm

 

Universal     - OR -

 

X

US 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.  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.  

6.c. Stakeholders / Vendors / Providers

This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballots

 

Stakeholders

 

Vendors

 

Providers

 

Clinical and Public Health Laboratories

 

Pharmaceutical

X

Clinical and Public Health Laboratories

 

Immunization Registries

 

EHR, PHR

X

Emergency Services

 

Quality Reporting Agencies

 

Equipment

X

Local and State Departments of Health

 

Regulatory Agency

 

Health Care IT

X

Medical Imaging Service

X

Standards Development Organizations (SDOs)

 

Clinical Decision Support Systems

X

Healthcare Institutions (hospitals, long term care, home care, mental health)

X

Payors

 

Lab

 

Other (specify in text box below)

 

Other (specify in text box below)

 

HIS

 

N/A

 

N/A

X

Other (specify below)

 

 

 

 

 

N/A

 

 

Other:  Clearinghouse Vendors

 

6.d. Project Approval Dates

Approvals are by simple majority vote of the approving body

Sponsoring Work Group Approval Date:

AWG 2018-03-06

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date

 

List each Co-Sponsor and their Approval Date CCYY-MM-DD
or indicate “N/A”
 

Family Management Group Approval Date(s)

CIMI Projects: CIMI Management Group

CIMI MG Approval Date CCYY-MM-DD
or “N/A”

CDA Projects: CDA Management Group

CDA MG Approval Date CCYY-MM-DD
or “N/A”

FHIR Projects: FHIR Management Group

FMG Approval Date CCYY-MM-DD
or “N/A”

V2/Publishing Projects: V2 Management Group

V2 MG Approval Date CCYY-MM-DD
or “N/A”

US Realm Projects: US Realm Steering Committee Approval
(Email WG approved PSS to: tscpm@HL7.org )

USRSC Approval Date CCYY-MM-DD
or indicate “N/A”

Affiliate Specific Projects: Affiliate Approval Date

Affiliate Approval Date CCYY-MM-DD or indicate “N/A”

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

Last PBS Metrics Score :

 

Green

 

Yellow

 

Red

PBS Metrics Reviewed ? (required for SD Approval if not green)

 

Yes

 

No

ARB and SGB approval may be in parallel

Architectural Review Board Approval Date:

(required for externally developed content)

ARB Approval Date CCYY-MM-DD
or “N/A”

If applicable, TSC has received a Joint Copyright/Distribution Agreement (containing the verbiage outlined within the SOU),
signed by both parties.

 

 

Yes

 

No

 

N/A

Technical Steering Committee Approval Date:
(Email SD WG approved PSS to: tscpm@HL7.org )

TSC Approval Date CCYY-MM-DD