Page tree

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

 

 

Abstract Data Types R3

Project ID: 1504

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:  2019-01-16

 

X

- or -                     Direct to Normative (no STU) (includes reaffirmations)       

 

Identify ISO, IEC or ISO/IEC standard to be adopted in text box below

 

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.

 

 

Yes

 

X

No

 

 

 

 

 

Select the unit of measure used in the standard; if no measurements are in the standard, select N/A

 

X

N/A

 

 

U.S.

 

 

Metric

 

 

Both

 

 

Investigative Project (aka PSS-Lite)

Date : 

 

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

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

MnM

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

Co-sponsor Work Group(s)

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

 

Vocab

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: 

Will identify value sets to be updated

2.c. Project Team

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

Project facilitator ( 1 Mandatory )

Jean Duteau

Other interested parties and their roles

 

Multi-disciplinary project team (recommended)

 

Modeling facilitator

N/A

Publishing facilitator

Jean Duteau

Vocabulary facilitator

Ted Klein

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)  N/A

2)  N/A

  1. Project Definition

3.a. Project Scope

Re-publish the Abstract Data Types R2 unchanged except for updating value sets to reflect current content as maintained in HL7 terminology source and replacing links to external terminologies with current references.  We will conduct a limited scope normative ballot to do this.

The result will be labeled R3.

3.b. Project Need

Due to some timing issues, MnM failed to get the Abstract Data Types R2 reaffirmed prior to it expiring.  Thus, it needs to go back to ballot.  We will take advantage of that re-ballot to update terminology to be “current” but will make no other changes.  Abstract Data Types is the foundation for the RIM which is still the underlying foundation for v3, CDA and FHIR.

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

 

X

No

 

 

Unknown

 

3.d. External Drivers

N/A

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

ballot R3 as normative

2020 Feb cycle

Publish

2020 March

 

 

3.f.    Common Names / Keywords / Aliases

Datatypes

3.g. Lineage

N/A

3.h. Project Dependencies

N/A

3.i.    HL7-Managed Project Document Repository Location

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

3.j.    Backwards Compatibility

Are the items being produced by this project backward compatible?

 

Y

Yes

 

 

No

 

 

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

If you check 'Yes' please indicate the earliest prior release and/or version to which the compatibility applies: Abstract Data Types R2

 

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:

3.k. External Vocabularies

Will this project include/reference external vocabularies?

 

X

Yes

 

 

No

 

 

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies:

ISO country and language codes, Mime types

  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

 

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

 

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)

Not new product, but not currently in the list – TSC can decide what they want here

  1. Project Intent (check all that apply)

 

Create new standard

 

 

Supplement to a current standard

X

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

 

 

Balloted Informative OR

 

Non-balloted WG White Paper

 

 

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

HL7 Abstract Datatypes R2

Feb, 2013

Updating to reflect current terminology

Replace the non-reaffirmed standard but will not make any substantive changes to content

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

 

Comment (aka Comment-Only)

 

 

Joint Ballot (with other SDOs)

 

Informative

 

 

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

 

STU to Normative     - OR -

X

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

N/A

For projects that have some of their content already developed:

How much content for this project is already developed?

 

Was the content externally developed (Y/N)? 

 

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

 

 

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

X

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

 

 

 

 

6.d. Project Approval Dates

Approvals are by simple majority vote of the approving body

Sponsoring Work Group Approval Date:

2019-01-16

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Vocab

2019-01-16

Family Management Group Approval Date(s)

CIMI Projects: CIMI Management Group

N/A

CDA Projects: CDA Management Group

N/A

FHIR Projects: FHIR Management Group

N/A

V2/Publishing Projects: V2 Management Group

N/A

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

N/A

Affiliate Specific Projects: Affiliate Approval Date

N/A

Submit PSS to Steering Division after all of the above approvals are received

Steering Division (of Primary Sponsor WG) Approval Date:

2019-07-01

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)

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 Steering Division approved PSS to: tscpm@HL7.org )

TSC Approval Date CCYY-MM-DD