How To Delete An Encounter In Epic: A Clinical Informatics Guide To Record Management

How To Delete An Encounter In Epic: A Clinical Informatics Guide To Record Management

Epic FHIR API: A Developer's How-To Guide | OMOPHub Blog

Deleting an encounter in the Epic Electronic Health Record system requires specific security permissions and an understanding of the difference between "deleting" a record and "nullifying" or "voiding" an erroneous entry. Because healthcare data integrity laws mandate a permanent audit trail, true deletion is rarely available to end-users; instead, clinical staff typically utilize encounter cancellation or voiding workflows to maintain medical-legal compliance.


Prerequisites for Modifying Clinical Encounter Records

Before attempting to remove or adjust an encounter within Epic, you must confirm that your security class (User Role) contains the necessary administrative or clinical privileges. Attempting to modify records without proper authorization will trigger a security violation logged in the system audit trail.



  • Essential Prerequisites:
  • Administrative Security Access: Ensure your user template includes the "Delete/Void Encounter" security point, which is typically restricted to Health Information Management (HIM) departments or lead clinical informatics supervisors.
  • Valid Clinical Justification: You must have a verified reason for the removal, such as an accidental duplicate encounter creation, a patient registration error, or an incorrect visit type selection.
  • Audit Trail Awareness: Recognize that Epic stores all "deleted" encounters in a hidden status or permanent log for regulatory compliance under HIPAA and HITECH standards.
  • Time Window Constraints: Many organizations implement system settings that prevent the deletion of encounters containing finalized clinical documentation, lab results, or billing charges.

Step-by-Step Procedure for Encounter Cancellation or Voiding

In the Epic environment, the "Delete" button is rarely functional for end-users. The standard industry workflow involves changing the encounter status to "Canceled" or "Voided," which effectively removes the encounter from active provider lists and billing queues while retaining the metadata for legal compliance.



Step 1: Navigating to the Encounter Detail Screen

Access the patient's chart via the Patient Station or the Schedule activity. Once the patient record is open, navigate to the Encounter tab or the specific visit header. Select the encounter you intend to modify. Ensure you are looking at the correct Date of Service (DOS) to avoid accidental modifications to active, legitimate encounters.



Step 2: Verification of Encounter Status and Documentation

Before attempting a removal, review the encounter to ensure no clinical notes, orders, or charges have been associated with it. If clinical documentation exists, you must sign or revert any un-finalized notes.

Warning: Attempting to delete an encounter that has linked professional charges or finalized orders will result in a system error or a "Dependency Violation" notification. You must first void the associated orders and remove the charges via the Charge Review or Billing activity.



Step 3: Executing the Void or Cancel Action

Right-click the encounter header in the sidebar. Look for the "Void" or "Cancel Encounter" function. If the option is greyed out, your security role does not permit this action, and you must escalate the request to your department’s Epic Super User or HIM department. If the option is available, select it and choose the appropriate reason from the dropdown menu, such as "Entered in Error" or "Duplicate Encounter."



Step 4: Finalizing the Change and Documenting the Audit Trail

Once the system prompts you to confirm the action, input your password as required for electronic signature verification. Epic will then move the encounter to a "Voided" status. This status prevents the visit from appearing in standard reporting and billing workflows but preserves the entry in the system’s backend SQL database to comply with federal data retention regulations.


Epic Encounters RPG

Epic Encounters RPG

Technical Parameters of Encounter Status Types

The following table delineates the functional differences between common encounter status indicators in the Epic database architecture.



Status Type Functional Impact Visibility to Provider Billing Status
Active Allows documentation and ordering Visible in Worklist Open for Charge Capture
Canceled Stops documentation access Hidden from Worklist Blocked from Billing
Voided Terminates all associations Hidden from Worklist Permanent Exclusion
Future Placeholder for upcoming visits Visible in Schedule Pending Activation

Managing Encounter Errors and Common Workflow Failures

Clinical users frequently encounter barriers when attempting to "delete" records. Most of these issues are preventable through proper chart management and understanding Epic system dependencies.



  • Encounter Has Active Charges: If an encounter was accidentally started and billing charges were triggered, the encounter cannot be simply deleted. You must involve the Revenue Cycle team to credit the charges before the encounter can be moved to a "Voided" state.
  • Lab/Imaging Results Linked: If a patient had tests performed under the wrong encounter, you cannot delete the encounter. You must contact the Laboratory or Radiology Information System (LIS/RIS) interface team to perform a "Result Re-linking" procedure.
  • In-Progress Documentation: If a provider has an un-signed note attached to the encounter, the system will prevent deletion to preserve the medical record. You must delete or sign the note first.
  • Security Denial: If you receive an "Access Denied" error, do not attempt to bypass the system. Log the encounter ID (CSN) and submit a ticket to your organization's IT service desk with the justification for the change.

Frequently Asked Questions



Why can't I find a delete button in my Epic encounter screen?

Epic is designed as a permanent medical record system; therefore, it does not support the permanent destruction of records. Standard workflows use "Void" or "Cancel" functions to satisfy federal medical-legal requirements regarding audit trails.



What happens to the clinical notes if I void an encounter?

When an encounter is voided, any associated notes are typically moved to a "Voided/Inactive" status. They are removed from the active chart view to prevent confusion but are never actually erased from the underlying server storage.



Can I delete an encounter that has already been billed?

No, you cannot delete a billed encounter. You must perform a "Billing Adjustment" or "Void Transaction" through the professional billing module to correct the financial error before the encounter status can be updated.



Who has the authority to permanently remove an encounter?

Permanent removal is generally restricted to the Health Information Management (HIM) department or database administrators. Even then, "deletion" usually refers to moving the data to a restricted, non-queryable archive rather than permanent destruction.



How do I correct a duplicate encounter created by mistake?

The best practice is to "Void" the duplicate, enter a clear reason for the void (e.g., "Duplicate Entry"), and ensure all clinical activity is correctly documented in the original, valid encounter.

Optimize Your Clinical Informatics Workflow

Maintaining accurate patient records is critical for operational efficiency and patient safety. Consult your organization’s internal Epic training portal or contact your site-specific clinical informatics lead to request advanced access or further guidance on specialized record correction procedures.


Epic Encounters: Hall of the Orc King (PDF) - steamforged

Epic Encounters: Hall of the Orc King (PDF) - steamforged

Read also: Danielle Mazzone: Professional Insights, Career Path, and Industry Impact