NOTE : To use Track Changes, turn off “protection” by clicking on (pre-MS Word 2007) Tools > Unprotect Document or (MS Word 2007 and higher) Review > Protect Document.

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

 

 

HL7 V2+

Project ID:

 

 

TSC Notification Informative/STU to Normative          

Date : 

Check this box when the project proceeds from Informative to Normative or STU to Normative status.  Forward to the TSC for notification, as this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.  

 

 

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)

Publishing

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

Co-sponsor Work Group(s)

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

 

Conformance

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

 

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

X

Other Involvement. Specify details here: 

Participate fully

Co-sponsor Work Group(s)

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

 

Vocabulary

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

 

Request formal content review prior to ballot

X

Request periodic project updates. Specify period: 

Monthly?

 

Other Involvement. Specify details here: 

 

Co-sponsor Work Group(s)

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

 

Electronic Services

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

 

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

X

Other Involvement. Specify details here: 

Participate fully

Co-sponsor Work Group(s)

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

 

Education

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

 

Request formal content review prior to ballot

 

Request periodic project updates. Specify period: 

 

X

Other Involvement. Specify details here: 

Participate fully

Co-sponsor Work Group(s)

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

 

ITS

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

 

Request formal content review prior to ballot

X

Request periodic project updates. Specify period: 

How frequently?

 

Other Involvement. Specify details 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 )

Frank Oemig, Hans Buitendijk

Other interested parties and their roles

All V2 Chapter owners

Multi-disciplinary project team (recommended)

 

Modeling facilitator

 

Publishing facilitator

 

Vocabulary facilitator

 

Domain expert rep

Rob Snelick, Brian Pech, John Garguilo, Craig Newman, Tony Julian, (at some point ask Virginia Lorenzi an Education person to participate throughout)

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

2)  OO

  1. Project Definition

3.a. Project Scope

This is a fresh-Look initiative to modernize and make it easier to the developer to create and maintain high-quality specifications, and to the implementer to access and use the specifications in their efforts.

  • Consolidate technical terminology to provide the specification (e.g., R vs. RE vs. O, etc.)
  • Improve ability to maintain consistency across “chapters” (e.g., re-use and referencing of common componentry) ensuring updates are applied everywhere.
  • Publish V2 on a website as primary source for implementers
    • Replace word and pdf with a new source of truth on a webbased tool from which everything is derived.

The project will be organized in four phases:

  • Phase I - Establish target publication format.
    • Re-organize content
    • Consider alignment with FHIR approach
    • Generate and review draft HTML
  • Phase II - Establish a plan
    • Create a development plan that addresses:
      • Overall structure
        • Ability to modularize enabling smaller, targeted publications
        • Support continuous maintenance
      • Modernizing conformance constructs.
      • Enabling mapping between IGAMT and V2+ (e.g., link back to source from IGAMT to V2+)
      • Documentation tools for source specifications
      • Maintain simplicity to maintain the specification while simplifying implementer access as well.
        • Consider IGAMT to aid in the maintenance
    • Create an internal marketing/outreach plan
  • Phase III - Implement
  • Phase IV – Education and Deployment

 

 

 

 

3.b. Project Need

V2 is difficult to be

  • Maintainable
    • Consistency across chapters is challenging to achieve (presentation, content, style)
    • Generating pdfs
    • Variations in level of activity across chapters, yet impacting others.
      • Modular updates that isolate the change and minimize publication scope.
    • Inconsistent change tracking / request proposal.
  • Accessible
    • Finding editors to perform the necessary updates.
  • Processable
    • Inability to easily/consistently create implementation guides
    • Inability to easily/consistently generate and integrate with testing tools
  • Kept current
    • Long time line between versions.
    • Dependencies across chapters requiring everything to move together rather than targeted components individually.

 

 

 

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

National programs, e.g., ONC Certification programs, that require consistency and clear, unambiguous implementation guidance to measure conformance.

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

(Dependency on Chapter “2B.A” Conformance updates)

Assume May Draft

Final September

Optional Use Phase

Immediately

Apply Chapter “2B.A” requirements to IGAMT

2018-08-01

Improve IGAMT Help (on-line/otherwise)

2018-09-01

Establish Training Program for IGAMT Users

2018-09-01

Offer Training Sessions

2018-09-01 – 12-31

Start Mandatory Phase

2019-01-01

“Integration” of V2+ with IGAMT

2019-TBD-TBD

3.f.    Common Names / Keywords / Aliases

IGAMT, IGAMT on V2

3.g. Lineage

Not Applicable

3.h. Project Dependencies

Chapter 2.B Conformance Updates

 

3.i.    Project Document Repository Location

Confluence: http://52.42.5.44:8090/display/PUB/V2+Implementation+Guide+tooling

 

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

 

 

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

 

X

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies: VSAC and others depending on what we prepopulate.

 

  1. Products (check all that apply)

 

Arden Syntax

 

 

V2 Messages – Administrative

 

Clinical Context Object Workgroup (CCOW)

 

 

V2 Messages - Clinical

 

Domain Analysis Model (DAM)

 

 

V2 Messages - Departmental

 

Electronic Health Record (EHR) Functional Profile

 

 

V2 Messages – Infrastructure

 

FHIR Extensions

 

 

V3 Domain Information Model (DIM / DMIM)

 

FHIR Implementation Guide

 

 

V3 Documents – Administrative (e.g. SPL)

 

FHIR Profiles

 

 

V3 Documents – Clinical (e.g. CDA)

 

FHIR Resources

 

 

V3 Documents - Knowledge

 

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

 

 

V3 Foundation – RIM

 

Logical Model

 

 

V3 Foundation – Vocab Domains & Value Sets

 

New/Modified/HL7 Policy/Procedure/Process

 

 

V3 Messages - Administrative

 

New Product Definition (please define below)

 

 

V3 Messages - Clinical

 

New Product Family (please define below)

 

 

V3 Messages - Departmental

 

Non Product Project - (Educ. Marketing, Elec. Services, etc.)

 

 

V3 Messages - Infrastructure

 

White Paper

 

 

V3 Rules - GELLO

 

 

 

 

V3 Services – Java Services (ITS Work Group)

X

Creating/Using a tool not listed in the HL7 Tool Inventory

 

 

V3 Services – Web Services (SOA)

 

  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;

 

Withdraw an Informative Document

 

 

Externally developed IG is to be (select one):

 

White Paper (select one):

 

 

Adopted  - OR -

 

Endorsed

 

 

Balloted Informative OR

 

Non-balloted WG White Paper

 

X

N/A  (Project not directly related to an HL7 Standard)

-          

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

 

Comment (aka Comment-Only)

 

 

Joint Ballot (with other SDOs)

 

Informative

 

X

N/A  (project won’t go through ballot)

 

STU to Normative     - OR -

 

Normative (no STU)

 

 

 

 

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

NIST, Frank Oemig

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

 

 

No

6.b. Realm

X

Universal     - OR -

 

 

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

 

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.d. 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
(for US Realm Specific Projects):

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:

(required for externally developed content)

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

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

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.

 

 

 

 

 

 

 

 

Yes

 

No

 

N/A