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
Data Element Description The status of the procedure (e.g., planned, completed).
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 2 - Data element is captured, stored, or accessed in multiple production EHRs or other HIT modules from more than one developer.
Criterion #3
Maturity - Current Exchange		 Level 2 - Data element is electronically exchanged between more than two production EHRs or other HIT modules of different developers 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 jkegerize on

ACLA Comments: Procedure Status

The American Clinical Laboratory Association (ACLA) appreciates the opportunity to comment on Procedure Status. Laboratory results currently include Result Status, and we would appreciate clarification that procedure and procedure status are not expected to be used for any laboratory data.

Submitted by david_rocha on

Procedure Status: In Progress, Completed and Not Done SNOMED CT

The below relates to the three examples of procedure status that include in progress, completed, and not done:

 

For the example of “procedure in progress,” the SNOMED CT Situation hierarchy has coding for Procedure started (situation): 394906002, and all its descendants.

For the example of “procedure completed,” SNOMED CT Situation hierarchy has coding for Procedure carried out on subject (situation): 443938003, and all its descendants.

For the example of “procedure not done,” the SNOMED CT Situation hierarchy has coding for Procedure not done (situation): 416237000, and all its descendants.

SNOMED CT needs to be a required standard for Procedure Status to remain consistent with the CMS Quality Payment Program (QPP) technical specifications.

Submitted by CDC_DSMH_WG on

CDC's comment for inclusion in USCDI v7

The National Hospital Care Survey includes procedure information in restricted use data files and public use data files. We would only want to receive “provided” or “completed” procedures. We’ve demonstrated the utility of including procedures in analyses of restricted use data files in the following publications: National Health Statistics Reports Number 201” National Hospital Care Survey Demonstration Projects: Examination of Maternal Health Outcomes by Housing Assistance Status” at https://www.cdc.gov/nchs/data/nhsr/nhsr201.pdf. We’ve also demonstrated that procedures can be used to identify substance use disorders and selected mental health issues in National Center for Health Statistics Vital and Health Statistics Series 2 report Number 193 “Identifying co-occurring disorders among patients with an opioid-involved hospital encounter using National Hospital Care Survey data” at https://www.cdc.gov/nchs/data/series/sr_02/sr02-193.pdf. Inclusion of this data element would improve accuracy of reporting procedure information in official federal statistics produced by NHCS data.

b. Location of data element in the current HCS CDA IG V1.2: x-path /ClinicalDocument/structuredBody/section[templateId/@root="2.16.840.1.113883.10.20.22.2.7.1"][templateId/@extension="2014-06-09"]/entry/observation[templateId/@root="2.16.840.1.113883.10.20.22.4.13"][templateId/@extension="2014-06-09"]/statusCode

c. This data element is in C-CDA 4.0. Link in the C-CDA IG- Procedures Section - Consolidated CDA (C-CDA) v4.0.0 (https://hl7.org/cda/us/ccda/StructureDefinition-ProceduresSection.html)

d. Description of what the Division of Healthcare Statistics (DHCS) currently receives in production: Not available.

Submitted by CDC_DSMH_WG on

CDC's comment for proposed inclusion in USCDI v7

National Hospital Care Survey (NHCS) 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 NHCS data.

Location of data element in the current HCS CDA IG V1.2: x-path /ClinicalDocument/structuredBody/section[templateId/@root="2.16.840.1.113883.10.20.22.2.7.1"][templateId/@extension="2014-06-09"]/entry/observation[templateId/@root="2.16.840.1.113883.10.20.22.4.13"][templateId/@extension="2014-06-09"]/statusCode

This data element is in C-CDA 4.0. Link in the C-CDA IG- Procedures Section - Consolidated CDA (C-CDA) v4.0.0

Description of what DHCS currently receives in production: Not available.

Submitted by CDC_DSMH_WG 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 CDC_DSMH_WG 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

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB