The -EPICANALYSIS server completes the following steps:
-
Retrieve all documents that have a deficiency where the DocDeficiency.DirtyKey field does not equal zero.
Note:
The DirtyKey field is non-zero after a user has modified a deficiency (e.g., an analyst created a new deficiency, a physician completed his/her deficiency, etc.).
-
If OnBase is configured to send Epic deficiency status updates using HL7, load each document's deficiencies for the purpose of sending update messages.
HL7 settings are configured on the HL7 tab under Medical | Medical System Settings. For more information, see HL7 Settings.
- Update each deficiency's DirtyKey field to zero.
-
Once all the document's deficiencies have been completed (i.e., signed by the physician), burn the deficiencies onto the document. Use the DocDeficiency row to output the necessary physician information onto the document beneath the deficiency.
When burning deficiencies onto text documents, an image rendition of the text document is created as a new revision, and deficiencies are burned onto the image.
- After burning, move each deficiency to the CompletedDocDfcy table for auditing purposes.
- Burn standard notes onto the document. Notes are replaced with text stating See append note #XXX where the note was originally placed. The actual note information is printed onto the pages that are appended to the end of the document.
-
After burning, remove note database rows.
Note:
The burning of deficiencies and notes creates new revisions/renditions of the document. Previous revisions/renditions are not removed from the system.