Page tree

2019JAN_PSS_PublicHealth_KhanGaunt_VitalRecsBirthFetalDeathRpting_CDA_IG (2).docx

VitaPSS-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

 

 

Vital Records Birth and Fetal Death Reporting CDA IG

Project ID: 1474

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: 

 

 

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

 

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

Not Applicable

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

 

 

N/A

 

 

U.S.

 

 

Metric

 

 

Both

 

 

Investigative Project (aka PSS-Lite)

Date :  NA

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

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

Public Health 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: 

 

 

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 )

Hetty Khan; Sarah Gaunt

Other interested parties and their roles

Alaina Elliott, Reviewer; Lantana Group, Partner; Mead Walker, expert consultant

Multi-disciplinary project team (recommended)

 

Modeling facilitator

Sarah Gaunt

Publishing facilitator

Sarah Gaunt

Vocabulary facilitator

Sarah Gaunt

Domain expert rep

Hetty Khan, Alaina Elliott, David Johnson, Joyce Martin, Jeff Duncan, David Justice

Business requirement analyst

 

Conformance facilitator (for IG projects)

 

Other facilitators (SOA, etc)

 

 

 

Implementers (2 Mandatory for STU projects)

1)  State/Jurisdictional Vital Records Offices (Utah and Michigan)

2)  National Center for Health Statistics

  1. Project Definition

3.a. Project Scope

The Vital Records birth and fetal death reporting (BFDR) CDA had been first published as an STU in Feb, 2015 and expired in 2017. It provided a format for using HL7's Clinical Document Architecture to transmit medical/health information on live births and fetal deaths from a birthing facility to a jurisdictional vital records electronic registration system. Since then, the suite of VR standards (V2.6 death reporting, V2.6 BFDR, and VRDR CDA) has been updated to support the expansion of the flow of information to NCHS and, in the cases of birth, death and fetal death, return coded cause of death, and race and ethnicity information back to the states. The purpose of this project is to update the HL7 CDA Birth and Fetal Death Reporting IG standard to support such expansion.

3.b. Project Need

The Vital Records birth and fetal death reporting IG standard needs to be brought in line with the other VR standards to support the expansion of information flow to and from NCHS.

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 .

 

X

Yes

 

 

No

 

 

Unknown

 

3.d. External Drivers

NA

3.e. Project Objectives / Deliverables / Target Dates

 

Target Date

Enter objective/deliverable here.

Enter Target Date

Collect new and corrected requirements

2018 September

Submit for STU Ballot

2019 January Ballot

Complete STU Reconciliation

2019 March

Submit Publication Request

2019 April

Project End Date (all objectives have been met)

2019 April

 

 

3.f.    Common Names / Keywords / Aliases

BFDR CDA, CDA for Birth and Fetal Death Reporting, Vital Records Birth and Fetal Death Reporting

3.g. Lineage

HL7 Implementation Guide for CDA® Release 2: Birth and Fetal Death Report, Release 1 – US Realm http://www.hl7.org/special/Committees/tsc/ballotmanagement/pi_index_nibs.cfm?ProjectNumber=860

 

3.h. Project Dependencies

NA

3.i.    HL7-Managed Project Document Repository Location

https://confluence.hl7.org/display/PHWG/Vital+Records

3.j.    Backwards Compatibility

Are the items being produced by this project backward compatible?

 

 

Yes

 

X

No

 

 

Unknown

 

 

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? 

 

 

Yes

 

X

No

 

 

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

If you check 'No' please explain the reason: CDA uses data types R1

If desired, enter additional information regarding Backwards Compatibility.

3.k. External Vocabularies

Will this project include/reference external vocabularies?

 

X

Yes

 

 

No

 

 

Unknown

 

 

N/A

 

 

 

 

 

 

 

 

 

 

 

 

If yes, please list the vocabularies: PHIN VS (CDC Local Coding System), GEC Country Codes, Populated Places (NCHS), International Classification of Diseases revision 10 (ICD 10-WHO), SNOMED-CT, FIPS 6-4 (County), LOINC, Race & Ethnicity (CDC), Industry CDC Census 2010, U.S. Census Occupation Code (2010), ICD-10 Place of Occurrence, ISO 3166-2 Country Subdivision, UCUM – Unified Code for Units of Measure

  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)

 

X

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)

If you checked New Product Definition or New Product Family, please define below:

  1. Project Intent (check all that apply)

 

Create new standard

 

 

Supplement to a current standard

X

Revise current standard (see text box below )

 

X

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)

 

 

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)

X

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

NAPHSIS (National Association for Public Health Statistics and Information Systems)

For projects that have some of their content already developed:

How much content for this project is already developed?

0%

Was the content externally developed (Y/N)? 

NA

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

 

 

 

 

 

 

 

X

Yes

 

 

No

6.b. Realm

 

Universal     - OR -

 

X

Realm Specific - US

 

 

X

Check here if this standard balloted or was previously approved as realm specific standard

 

US  

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

X

EHR, PHR

 

Emergency Services

 

Quality Reporting Agencies

 

Equipment

X

Local and State Departments of Health

 

Regulatory Agency

 

Health Care IT

 

Medical Imaging Service

 

Standards Development Organizations (SDOs)

 

Clinical Decision Support Systems

X

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

 

Payors

 

Lab

X

Other (specify in text box below)

X

Other (specify in text box below)

 

HIS

 

N/A

 

N/A

X

Other (specify below)

 

 

 

 

 

N/A

 

 

Other:  CDC National Center for Health Statistics; NAPHSIS; Vital Record Systems

 

6.d. Project Approval Dates

Approvals are by simple majority vote of the approving body

Sponsoring Work Group Approval Date:

PHWG Approval Date 2018-10-01

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date

 

SDWG: Approval Date 2018-10-03
 

Family Management Group Approval Date(s)

CDA Management Group

2018-10-24

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

2018-10-16

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:

SD Approval Date 2018-11-28

Last PBS Metrics Score :

x

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

TSC Approval Date CCYY-MM-DD