Skip to end of metadata
Go to start of metadata





1a. Project Name

Vital Records Reporting Domain Analysis Model R4

1b. Project ID

1575

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?

No

1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Project Services

2d. Project Facilitator

AbdulMalik Shakir

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

AbdulMalik Shakir

2g. Publishing Facilitator

Jean Duteau

2h. Vocabulary Facilitator

Sunanda McGarvey BS

2i. Domain Expert Representative

Hetty Khan; Alaina Gregory; Cynthia Bush

2j. Business Requirements Analyst

Salimah Shakir

2k. Conformance Facilitator

2l. Other Facilitators

2m. Implementers

CDC NCHS
HL7 Public Health Workgroup

3a. Project Scope

Update and publish the next release of the VR DAM by map the HL7 v2.6 and FHIR death reporting implementation guides to release 3 of the VR DAM, identifying and reconciling mapping discrepancies, and reflecting the outcome of reconciliation as changes to the VR DAM. Ballot release 4 of the VR DAM as a standard for trail use.

Attachments

3b. Project Need

The Vital Records Domain Analysis Model (VR DAM) is the authoritative statement of foundational requirements for the design and development of health information exchange standards in HL7 related to vital records information flows. It facilitates consistency in the content and encoding of required vital records data and helps to ensure that HL7 standards developed for the vital records domain are derived from a common authoritative set of workflow and information requirements. The objective of this project is to ensure that the VR DAM continues to reflect the content of published vital records related HL7 specifications.

Since completion of the release 3 of the VR DAM two additional Vital Records related specification have completed their approval cycles. They are:
• HL7 Version 2.6 Implementation Guide: Vital Records Death Reporting, Release 1
• HL7 FHIR® Implementation Guide : Vital Records Mortality and Morbidity Reporting, Release 1

The information content and workflow profiles reflected in these specification need to be added to the VR DAM to ensure complete coverage of the domain. The harmonized terminology bindings from these specifications are especially important to anticipated subsequent work in the VR reporting domain.

3c. Security Risk

No

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

• Gap analysis and reconciliation for the two Vital Records death reporting specifications will be completed in October 2019.
• Updates to the VR DAM will be completed and prepared for review by NCHS subject matter experts and the HL7 Public Health workgroup by February 2020.
• Release 4 of the VR DAM will be prepared for inclusion in the HL7 May 2020 ballot cycle.
• Ballot reconciliation and publication will be completed in September 2020.

3f. Common Names / Keywords / Aliases:

Vital Records (VR); Domain Analysis Model (DAM);

3g. Lineage

3h. Project Dependencies

1477 - Vital Records Death Reporting V2.6
1475 - Vital Records Mortality and Morbidity Reporting FHIR IG
1432 - Vital Records Domain Analysis Model specification mapping

3i. HL7-Managed Project Document Repository URL:

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

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

Yes

3l. Reason for not using current V3 data types?

3m. External Vocabularies

Yes

3n. List of Vocabularies

Anticipated external vocabularies include SNOMED, LOINC, and RxNorm

3o. Earliest prior release and/or version to which the compatibility applies

HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 3 (http://bit.ly/2knW6W0)

4a. Products

Domain Analysis Model (DAM)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Revise current standard

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?

5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

A release update to the HL7 Cross-Paradigm Domain Analysis Model: Vital Records, Release 3 (http://bit.ly/2knW6W0) published September 2019.

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

The ballot of this specification will be the first STU release of the VR reporting DAM. However, STU is not listed among the choices of ballot types. The specification will go to normative when a subsequent STU or Normative specification documents lineage to the VR DAM as part of its specification.

5d. Joint Copyright

No

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

6b. Content Already Developed

None

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

Yes

6f. Stakeholders

Clinical and Public Health Laboratories, Standards Development Organizations (SDOs)

6f. Other Stakeholders

6g. Vendors

Health Care IT, HIS

6g. Other Vendors

6h. Providers

Clinical and Public Health Laboratories, Local and State Departments of Health

6h. Other Providers

6i. Realm

U.S. Realm Specific

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

7b. Sponsoring WG Approval Date

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

7j. TSC Approval Date