Covered by this topic
In order to archive, close, or re-archive an encounter, users must be familiar with the security settings, buttons, toolbars, and links associated with the encounter. The buttons found in the encounter are customizable and may have different functions per practice, or per encounter, depending on the preferred workflows. Contact an Implementation Specialist to have the buttons renamed or functionality reconfigured, as needed.
To archive or re-archive encounters, users must have the necessary security permissions set. Customize the user security by updating the following settings, accordingly:
Document Permissions: Set to Edit. This allows the user edit all encounters and/or archive and re-archive them, as appropriate.
Document Signature Override: Set to Yes. Users within a security role may override a signature or request another signature if a document is already signed.
Sign Document: Set to Yes.** This allows users within a security role the ability to sign documents.
Layered toolbars appear at the top of the dynamic encounter
to assist with navigation, as well as to provide patient and encounter
details. The toolbar display is responsive and changes with scrolling and movement on the page, collapsing as users navigate the encounter. For a basic introduction to the system
or a more detailed description of working in a chart and an encounter, be sure to check out the System Anatomy
; however, here are some of the more important tools and functions that are specific to the encounter:
Encounter Info Toolbar - Provides quick links to the current encounter, allowing users quick access to the encounter while working from within an E-chart or another encounter.
Encounter Navigation Toolbar - Provides navigation tabs which allow users to jump to different sections of the encounter. Hovering over any tab will display the sections that are available from within that portion of the encounter.
Standard Encounter Buttons - Buttons related to an open encounter:
Release - This button will not only save the current progress of the encounter, but it will simply discharge, or release the current active editor from the encounter, allowing other users to modify the encounter without risk of overwriting each other’s documentation.
Save Incomplete & View - Saves current progress in the encounter but does not archive or close it. A copy of the encounter will open for users to view (preview), prior to them preliminarily archiving or closing it.
Note Complete - In addition to saving any progress in the encounter, this button also releases any transcriptions pending from sections within the encounter that have been dictated. These are sent to a Pending queue in the Dictation module. The encounter remains open until archived and closed.
button, at the bottom of each section, will also save the user’s current progress in the encounter.
As noted, every button EXCEPT Archive & Close will take the user to a view, or preview, of the encounter. When previewing the encounter, users may Archive and Close Encounter, or Create Preliminary Archive. Both of these options, for all intents and purposes, will archive the document with a designated doc ID.
Creating a preliminary archive will save the progress of the encounter and keep it open while creating a document type and archiving the doc ID in the chart, where all updates and modifications of the encounter are tracked. This allows users the ability to return to the encounter and finalize, as needed. In this common workflow, users will mark the encounter closed once the encounter is complete. The only difference between a preliminary and archived encounter is the open/closed status
When previewing the Encounter View, users may re-archive the encounter to save any changes made, updating the original encounter document. If users are viewing the preliminary archive document, the Re-Archive and Close Encounter link will display. This will re-archive the encounter and mark it closed, when selected.
As noted, E-sign rules are important tools that should be considered when working with encounters. An Implementation Specialist can set up E-sign rules for clients needing to request signatures or have encounters signed automatically, when the document is closed and archived. Similarly, Fast Tasks can be configured to send closed/archived documents to a designated department, to be faxed or sent out, as needed. Depending on the workflow, this could be used to send encounter documents to referring physicians or other interested parties, as well.
To open closed encounters, users must have the Reopen Closed Encounters security permission set to Yes. The system must also have the Show Set Open Link system setting enabled (set to 1). Users with these security settings will see a link in the Options column of the respective encounters that are closed. If the encounter is closed and these permissions are set to No, the user will not be able to view or edit the closed encounter, see the Encounter Properties, nor be able to add physicians using the Add Physician link. Users will only see links to View Details and Delete.