Activity performed for or on a patient as part of the provision of care.

Data Element
Procedure Status
Description

The status of the procedure (e.g., planned, completed).
Submitted By: Maria Michaels / CDC
Data Element Information
Use Case Description(s)
Use Case Description Actively monitoring diseases, making decisions about public health threats, identifying trends in healthcare services utilization and other public health matters depend on accessible and accurate data. EHRs are a data source that can provide timely and relevant data beyond its use by health care providers. EHR data, if made more available for public health professionals and researchers, can lead to more rapid disease detection, tracking, and treatment and innovation in healthcare delivery.

Procedure information, including the coded identification and the date the procedure was performed, are important to multiple public health reporting and research use cases to track and analyze information about treatment for various health conditions.

The Making EHR Data More Available for Research and Public Health (MedMorph) project's goal is to create a reliable, scalable, and interoperable method to get electronic health record data for multiple public health and research scenarios (use cases). MedMorph has identified Cancer Reporting, Healthcare Surveys, and Multiple Chronic Conditions (MCC) eCare Plan (for date only) use cases that support the adoption of these data elements. These specific use cases are described in more depth on their respective web pages.
Estimate the breadth of applicability of the use case(s) for this data element All 50 states participate in one or more of the public health use cases that exchange these data elements. Up to 14 territorial or city jurisdictions also participate in one of these public health use cases and use these data elements.

All hospitals and physicians who diagnose or treat cancer are required to provide cancer related procedure information to state cancer registries.

Approximately 620,000 physicians in the US are active and have at least some component of ambulatory practice and thus are annually eligible to sampling and recruitment into the National Ambulatory Medical Care Survey (NAMCS), which samples from between 3,500 to 20,000 of these physicians annually. Presently each sampled physician submits one weeks' worth of patient encounters to NAMCS. Approximately 600 hospitals are in the National Hospital Care Survey (NHCS). 1/3 of that number are either in, or actively being recruited into, the EHR data submission mode for NHCS. NHCS is already receiving electronic CDA documents. When they reach their target of 200 hospitals submitting by this mode annually they will be receiving >1.2 million documents and sets including multiple sets of medication data annually. 

There were approximately 1,000,000 practicing physicians (as of 2020), approximately 120,000 certified physician assistants (as of 2019), and 290,000 licensed nurse practitioners (as of 2019). Most of these licensed clinicians interact with one of these public health use cases intermittently, annually. As of 2018, AHA reported 6,146 hospitals in the US experiencing 36,353,946 admissions. Almost all of those hospitals and at least half of the admissions interact with one or more of the public health use cases. The vast majority of these exchanges include full sets of medication data, including the data elements requested for USCDI consideration here.

Supporting Link:
MedMorph Project Page: https://www.cdc.gov/csels/phio/making-ehr-data-more-available.html

Cancer Reporting: https://www.cdc.gov/cancer/npcr/

Healthcare Surveys: https://www.cdc.gov/nchs/dhcs/nhcs_registry_landing.htm

MCC eCare Plan: https://confluence.hl7.org/display/PC/Multiple+Chronic+Conditions+%28MCC%29+eCare+Plan
Link to use case project page https://www.cdc.gov/csels/phio/making-ehr-data-more-available.html https://www.cdc.gov/cancer/npcr/ https://www.cdc.gov/nchs/dhcs/nhcs_registry_landing.htm https://confluence
Supporting Attachments MedMorph-CancerReportingUseCase-DRAFT.pdf
MedMorph-HealthCareSurveyReportingUseCase-DRAFT.pdf
Use Case Description A foundational goal of MedMorph is generalizability beyond the 10 use cases that are actively informing the MedMorph project, in order to support many more public health and research use cases. Therefore, other public health and research use cases that use the MedMorph architecture will also benefit from the adoption of these data elements.
Estimate the breadth of applicability of the use case(s) for this data element All 50 states participate in one or more of the public health use cases that exchange these data element. Up to 14 territorial or city jurisdictions also participate in one of these public health use cases and use these data elements.

All hospitals and physicians who diagnose or treat cancer are required to provide cancer related procedure information to state cancer registries.

Approximately 620,000 physicians in the US are active and have at least some component of ambulatory practice and thus are annually eligible to sampling and recruitment into the National Ambulatory Medical Care Survey (NAMCS), which samples from between 3,500 to 20,000 of these physicians annually. Presently each sampled physician submits one weeks' worth of patient encounters to NAMCS. Approximately 600 hospitals are in the National Hospital Care Survey (NHCS). 1/3 of that number are either in, or actively being recruited into, the EHR data submission mode for NHCS. NHCS is already receiving electronic CDA documents. When they reach their target of 200 hospitals submitting by this mode annually they will be receiving >1.2 million documents and sets including multiple sets of medication data annually. 

There were approximately 1,000,000 practicing physicians (as of 2020), approximately 120,000 certified physician assistants (as of 2019), and 290,000 licensed nurse practitioners (as of 2019). Most of these licensed clinicians interact with one of these public health use cases intermittently, annually. As of 2018, AHA reported 6,146 hospitals in the US experiencing 36,353,946 admissions. Almost all of those hospitals and at least half of the admissions interact with one or more of the public health use cases. The vast majority of these exchanges include full sets of medication data, including the data elements requested for USCDI consideration here.
Healthcare Aims
  • Improving the health of populations
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) Procedure Code (same as current USCDIv1):
Health Care Financing Administration Common Procedure Coding System (HCPCS), as maintained and distributed by HHS. http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets/index.html
Current Procedural Terminology, Fourth Edition (CPT-4), as maintained and distributed by the American Medical Association, for physician services and other health care services. http://www.ama-assn.org/ama/pub/physician-resources/solutions-managing-your-practice/coding-billing-insurance/cpt.page
SNOMED International, Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT®) U.S. Edition, September 2019 Release. http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html

Optional:
International Classification of Diseases ICD-10-PCS 2020. http://www.cms.gov/Medicare/Coding/ICD10/index.html
Technology which records dental procedures: Code on Dental Procedures and Nomenclature (CDT), maintained and distributed by the American Dental Association, for dental services. http://www.ada.org/en/publications/cdt

Procedure Date: HL7 FHIR Datatypes (dateTime|Period|string|Age|Range)
http://hl7.org/fhir/datatypes.html#dateTime
http://hl7.org/fhir/datatypes.html#Period
http://hl7.org/fhir/datatypes.html#string
http://hl7.org/fhir/datatypes.html#Age
http://hl7.org/fhir/datatypes.html#Range

Procedure Status: HL7 FHIR Event Status (preparation, in-progress, not-done, on-hold, stopped, completed, entered-in-error, unknown). http://hl7.org/fhir/R4/valueset-event-status.html
http://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets/index.html http://www.ama-assn.org/ama/pub/physician-resources/solutions-managing-your-practice/coding-billing-insurance/cpt.page
Additional Specifications HL7 FHIR US Core Implementation Guide v3.1.1: https://www.hl7.org/fhir/us/core/index.html

HL7 FHIR US Core Procedure: http://hl7.org/fhir/us/core/StructureDefinition-us-core-procedure.html. MustSupport for the following elements: Procedure Code, Procedure Date, Procedure Status

HL7 CDA® R2 Implementation Guide: Consolidated CDA Templates for Clinical Notes - US Realm: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492. SHALL for the following elements: Procedure Code, Procedure Status. SHOULD for the following elements: Procedure Date

HL7 CDA ® Release 2 Implementation Guide: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1, DSTU Release 1.1 – US Realm: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=398. SHALL for the following elements: Procedure Code, Procedure Date, Procedure Status.

HL7 CDA® R2 Implementation Guide: National Health Care Surveys (NHCS), R1 STU Release 3 - US Realm: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=385
Current Use Extensively used in production environments
Supporting Artifacts Level 2 – at scale, or in more widespread production use (routinely collected already) on several different EHR/HIT systems.

Widely available in EHR systems.

These data elements exist in FHIR with a FHIR Maturity level of 3 for the Procedure Resource. FHIR Procedure Resource: http://hl7.org/fhir/procedure.html

Procedure Code: SNOMED CT, CPT-4, HCPCS are included in the ISA with an adoption level of 5 in production implementations. ICD-10-PCS and CDT are included in the ISA with an adoption level of 4 in production implementations. ISA: https://www.healthit.gov/isa/representing-medical-procedures-performed

Part of Core EHR Certification since at least 2014.

Specified in Meaningful Use/Promoting Interoperability since Stage 1.

Part of EHR Certification for Transmission to Cancer Registries (2015 and 2014 Editions).

As part of Cancer Reporting CDA IGs:
IHE Connectathons 2010-2020
HIMSS Interoperability Showcase 2010-19
Public Health Informatics Conference Interoperability Showcase 2014, 2016, 2018
NACCHO 360X Interoperability Demonstrations, 2020

As part of National Health Care Surveys CDA IGs:
IHE Connectathons 2019-2020

Promoting Interoperability Programs Eligible Hospitals and Critical Access Hospitals are required to, and Merit-based Incentive Payment System (MIPS) participants may optionally, report on any two measures under the Public Health and Clinical Data Exchange objective of these programs. The § 170.315(f)(5) – Transmission to public health agencies – electronic case reporting certification criteria in the 2015 Edition Final Rule and the ONC Cures Act Final Rule, the § 170.315(f)(7) – Transmission to public health agencies – health care surveys, and the § 170.315 (f)(4) – Transmission to Cancer Registries are three such options to meet these measures.

The current standard for § 170.315(f)(5), as listed in ONC’s 2020 Interoperability Standards Advisory Reference Edition, is HL7® CDA® R2 Implementation Guide: Public Health Case Report, Release 2: the Electronic Initial Case Report (eICR), Release 1, STU Release 1.1. ONC’s Certified Health IT Product List (CHPL) lists 73 EHR or HIT Module products certified to (f)(5) using this standard. eCR IG: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436.

The current standard for § 170.315(f)(7), as listed in ONC’s 2020 Interoperability Standards Advisory Reference Edition, is HL7® CDA® R2 Implementation Guide: National Health Care Surveys (NHCS), R1 DSTU Release 1.2 - US Realm. ONC’s Certified Health IT Product List (CHPL) lists 116 EHR or HIT Module products certified to (f)(5) using this standard. NHCS IG: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=385.

The current standard for § 170.315 (f)(4), as listed in ONC’s 2020 Interoperability Standards Advisory Reference Edition, is HL7 CDA® R2 IG: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, R1, DSTU Release 1.1 - US Realm. ONC’s Certified Health IT Product List (CHPL) lists 288 EHR or HIT Module products certified to (f)(4) using this standard. Cancer Reporting IG: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=398.

These three widely adopted CDA standards have many of the Procedure data elements contained on this form as Shall (required) or Should (best practice to include if available) conformance criteria, which demonstrates the maturity of these commonly exchanged data elements.                         

Supporting Links:
Epic APIs: https://fhir.epic.com/Specifications

Allscripts APIs: https://developer.allscripts.com/FHIR?PageTitle=Resources

Cancer Registry Test Procedure: https://www.healthit.gov/test-method/transmission-cancer-registries#test_procedure

2014 Edition Test Methods: https://www.healthit.gov/sites/default/files/2014_test_methods/2014_edition_test_methods_archived.zip
http://hl7.org/fhir/procedure.html https://www.healthit.gov/isa/representing-medical-procedures-performed https://fhir.epic.com/Specifications https://developer.allscripts.com/FHIR?PageTitle=Resources
Extent of exchange 5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.
Supporting Artifacts Level 2 – exchanged between 4 or more different EHR/HIT systems. More routinely exchanged between multiple different systems can justify adding to the next draft version.

At least 38 state cancer registries have received cancer reports that include these data elements from at least one provider (per internal technical and programmatic documentation).

HL7 CDA® R2 Implementation Guide: Public Health Case Report, Release 2 - US Realm (https://www.hl7.org/implement/standards/product_brief.cfm?product_id=436) - the Electronic Initial Case Report (eICR) is currently implemented in 5,400+ reporting sites nationally and exchanges the following Problem/Condition elements: Onset Date, Abatement Date, Condition/Diagnosis Code, Condition/Diagnosis Recorded Date.

As part of Cancer Reporting CDA IGs:
IHE Connectathons 2010-2020
HIMSS Interoperability Showcase 2010-19
Public Health Informatics Conference Interoperability Showcase 2014, 2016, 2018
NACCHO 360X Interoperability Demonstrations, 2020

As part of National Health Care Surveys CDA IGs:
IHE Connectathons 2019-2020

ONC Interoperability Standards Advisory - Sending Health Care Survey Information to Public Health Agencies: https://www.healthit.gov/isa/sending-health-care-survey-information-public-health-agencies

eCase Reporting with The Council of State and Territorial Epidemiologists (CSTE) and The Association of Public Health Laboratories (APHL) - C- CDA Currently implemented in 5,400 + reporting sites nationally. https://ecr.aimsplatform.org/about-us#:~:text=A%20US%20federal%20agency%20under,the%20United%20States%20and%20internationally.

Supporting Links:
https://chpl.healthit.gov/#/search: 170.315 (f)(4): Transmission to Cancer Registries
Retired | 170.314 (f)(5): Optional - ambulatory setting only - cancer case information
Retired | 170.314 (f)(6): Optional - ambulatory setting only - transmission to cancer registries)
https://chpl.healthit.gov/#/search
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) None
Restrictions on Use (e.g. licensing, user fees) None
Privacy and Security Concerns None
Estimate of Overall Burden Low.

All providers need to capture procedure information as a basic component of patient care.

Several existing IGs, as listed, require the exchange of this data element. The Promoting Interoperability Programs Objective 8 - Public Health and Clinical Data Registry Reporting, Measures 1: Immunization Registry Reporting, 2: Syndromic Surveillance Reporting, 3: Electronic Case Reporting and 4: Public Health Registry Reporting all require these data elements.

This information is routinely communicated in HL7 CDA Documents and some FHIR API transactions.
Other Implementation Challenges None
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 2 - Data element is represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 1 - Data element is captured, stored, or accessed in at least one production EHR or HIT module.
Criterion #3
Maturity - Current Exchange		 Level 1 - Data element is electronically exchanged between two production EHRs or other HIT modules using available interoperability standards.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 2 - Use cases apply to most care settings or specialties.

Comment

Submitted by nedragarrett_CDC on

CDC's Comment for draft USCDI v6

CDC is requesting that Procedure Status be added for consideration to USCDI V6 to inform hospital and ambulatory medical care survey data collection efforts. 

Justification:  National Healthcare Surveys includes procedure information in restricted use data files and public use data files. We would only want to receive “provided” or “completed” procedures. Inclusion of this data element would improve accuracy of reporting procedure information in official federal statistics produced by National Healthcare Surveys data.

Submitted by nedragarrett_CDC on

Unified Comment from CDC

Exchange of data element: The Multiple Chronic Conditions eCare Plan project successfully tested this element at the Sep 2020 and Jan 2021 FHIR connectathons and has implemented it at the OHSU testing site.

This element is used by CMS Quality Reporting and is marked Required or Must Support in the FHIR QI Core IG

Log in or register to post comments