Page tree
Skip to end of metadata
Go to start of metadata

1a. Project Name

Data Elements for Emergency Department Systems Update and Revision

1b. Project ID

1570 (formerly 1072)

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


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


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

FHIR Infrastructure

2b. Co-Sponsor WG

Payer/Provider Information Exchange

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

WGM Report out

2d. Project Facilitator

James McClay

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

Susan Matney

2g. Publishing Facilitator

Laura Heerman Langford

2h. Vocabulary Facilitator

Susan Matney

2i. Domain Expert Representative

James McClay

2j. Business Requirements Analyst

Domminik Brammen

2k. Conformance Facilitator

2l. Other Facilitators

2m. Implementers

Inter-mountain Healthcare
University of Nebraska Medical Center

3a. Project Scope

Development and publication of specifications for ED patient records systems, Data Elements for Emergency Department Systems (DEEDS) ( in 1997, showed that relevant data standards can be consolidated and distributed in a single document. The DEEDS specifications have been widely used for a variety of purposes, including healthcare claims attachment specifications mandated by the federal Health Insurance Portability and Accountability Act (HIPAA); emergency care terminology additions to the Logical Observations, Identifiers, Names, and Codes (LOINC) clinical vocabulary; and data definitions and terminology for public health surveillance initiatives, such the BioSense program at the Centers for Disease Control and Prevention (CDC), the emergency department component of the North Carolina Disease Event Tracking and Epidemiologic Collection Tool (NC DETECT) and the Frontlines in Medicine Project.

Version 1.0 of the HL7 DEEDS specification was balloted in 2012. The DEEDS data specification provides the data model for the HL7 Emergency Care Domain Analysis Model. This update and revision will harmonize DEEDS with current HL7 specifications and data sets. Based on feed back from the CDC and others additional data elements may be added and some deprecated based on experience and changes to data standards.


3b. Project Need

Emergency medicine and nursing are on the frontline of care in the United States. As reported by the Institute of Medicine the Emergency Care system is at the breaking point. One major improvement in the system can be made by improving the use of information technology and sharing of patient and process information. Current emergency care data exchange specifications and external reporting requirements and recommendations are fragmented and often are developed and issued in an ad-hoc fashion with different organizations developing incompatible data standards.

3c. Security Risk


3d. External Drivers

3e. Objectives/Deliverables and Target Dates

1) represent emergency department data needs for reporting, research and operations
2) conform to current ONC and HL7 standards
Target Dates:
Informatics ballot: May 2020
STU ballot: Sept 2020

3f. Common Names / Keywords / Aliases:

Emergency Care, EDIS, DEEDS,

3g. Lineage

1. Data Elements for Emergency Department Systems published by CDC in 1996 2.HL7 Version 3 Specification: Data Elements for Emergency Department Systems (DEEDS), Health Level 7 International, May 2012: available at

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

3j. Backwards Compatibility


3k. Additional Backwards Compatibility Information (if applicable)

To existing DEEDS V1.0

3l. Using Current V3 Data Types?


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

3m. External Vocabularies


3n. List of Vocabularies

Chief Compliant Ontology

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


4a. Products

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

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

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type


5c. Additional Ballot Info

5d. Joint Copyright

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


6a. External Project Collaboration

6b. Content Already Developed


6c. Content externally developed?


6d. List Developers of Externally Developed Content

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


6f. Stakeholders

Quality Reporting Agencies, Standards Development Organizations (SDOs), Other

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6g. Other Vendors

6h. Providers

Emergency Services, Healthcare Institutions (hospitals, long term care, home care, mental 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