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


 Show Changes

Version

4

Modifier

Dave Hamill

Modify Date

Oct 17, 2019 18:58

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

No

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

No

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

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

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) (http://www.cdc.gov/ncipc/pub-res/deedspage.htm) 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

No

3e. Objectives/Deliverables and Target Dates

Objenctives:
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 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=326

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/display/EC/Emergency+Care

3j. Backwards Compatibility

Yes

3k. Additional Backwards Compatibility Information (if applicable)

To existing DEEDS V1.0

3l. Using Current V3 Data Types?

Unknown

3m. External Vocabularies

Yes

3n. List of Vocabularies

Chief Compliant Ontology

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

DEEDS V1.0

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?

FHIR R4

5a. Project Intent

Revise current standard

5a. Revising Current Standard Info

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type

Informative

6b. Content Already Developed

50%

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6h. Providers

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

6i. Realm

U.S. Realm Specific

Version

3

Modifier

James McClay

Modify Date

Sep 27, 2019 13:59

1a. Project Name

Data Elements for Emergency Department Systems Update and Revision

1b. Project ID

1072

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

No

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

No

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

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

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) (http://www.cdc.gov/ncipc/pub-res/deedspage.htm) 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

No

3e. Objectives/Deliverables and Target Dates

Objenctives:
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 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=326

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/display/EC/Emergency+Care

3j. Backwards Compatibility

Yes

3k. Additional Backwards Compatibility Information (if applicable)

To existing DEEDS V1.0

3l. Using Current V3 Data Types?

Unknown

3m. External Vocabularies

Yes

3n. List of Vocabularies

Chief Compliant Ontology

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

DEEDS V1.0

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?

FHIR R4

5a. Project Intent

Revise current standard

5a. Revising Current Standard Info

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type

Informative

6b. Content Already Developed

50%

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6h. Providers

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

6i. Realm

U.S. Realm Specific

Version

2

Modifier

James McClay

Modify Date

Sep 27, 2019 13:53

1a. Project Name

Data Elements for Emergency Department Systems Update and Revision

1b. Project ID

1072

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

No

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

No

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

2f. Modeling Facilitator

tbd

2g. Publishing Facilitator

Laura Heerman Langford

2h. Vocabulary Facilitator

tbd

2i. Domain Expert Representative

James McClay

2j. Business Requirements Analyst

tbd

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) (http://www.cdc.gov/ncipc/pub-res/deedspage.htm) 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.

We propose to expand the scope of DEEDS to harmonize with the prehospital arena, disaster response systems, and the needs of secondary data users such as the CDC and public health agencies. This comprehensive set of data elements will serve as the content for the interchange formats described above and as a basis for smooth integration between emergency response systems.

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

No

3e. Objectives/Deliverables and Target Dates

Objenctives:
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 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=326

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/display/EC/Emergency+Care

3j. Backwards Compatibility

Yes

3k. Additional Backwards Compatibility Information (if applicable)

To existing DEEDS V1.0

3l. Using Current V3 Data Types?

Unknown

3m. External Vocabularies

Yes

3n. List of Vocabularies

Chief Compliant Ontology

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

DEEDS V1.0

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?

FHIR R4

5a. Project Intent

Revise current standard

5a. Revising Current Standard Info

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type

Informative

6b. Content Already Developed

50%

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6h. Providers

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

6i. Realm

U.S. Realm Specific

Version

1

Modifier

James McClay

Modify Date

Sep 17, 2019 21:02

1a. Project Name

Data Elements for Emergency Department Systems Update and Revision

1b. Project ID

1072

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

No

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

No

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

3j. Backwards Compatibility

No

4a. Products

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

5a. Project Intent

Revise current standard

5a. Revising Current Standard Info

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type

Informative

6b. Content Already Developed

50%

6f. Stakeholders

Other

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6h. Providers

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

6i. Realm

U.S. Realm Specific


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

No

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

No

2a. Primary/Sponsor WG

Emergency Care

2b. Co-Sponsor WG

Patient Care

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

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

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) (http://www.cdc.gov/ncipc/pub-res/deedspage.htm) 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

No

3e. Objectives/Deliverables and Target Dates

Objenctives:
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 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=326

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/display/EC/Emergency+Care

3j. Backwards Compatibility

Yes

3k. Additional Backwards Compatibility Information (if applicable)

To existing DEEDS V1.0

3l. Using Current V3 Data Types?

Unknown

3m. External Vocabularies

Yes

3n. List of Vocabularies

Chief Compliant Ontology

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

DEEDS V1.0

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?

FHIR R4

5a. Project Intent

Revise current standard

5a. Revising Current Standard Info

Data Elements for Emergency Department Systems V1.0

5b. Project Ballot Type

Informative

6b. Content Already Developed

50%

6c. Content externally developed?

No

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

No

6f. Stakeholders

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

6f. Other Stakeholders

Clinicians, researchers

6g. Vendors

EHR, PHR, Clinical Decision Support Systems

6h. Providers

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

6i. Realm

U.S. Realm Specific