When a document is added to the Content Conditioning Lifecycle, it waits for a timer to transition to the evaluation and processing queues. The Clinical Processing queue ensures that the document meets certain criteria for keywords. The Clinical Processing queue ensures that the document has valid metadata and matches the values from the EMR. The lifecycle may optionally populate the MRN and assigning authority using a combination of the MPI and Capture Department values.
After a document is verified, it is added to the HL7 Sending Lifecycle. Depending on configuration, the lifecycle then either removes the document from the Content Conditioning Lifecycle, or adds the document to one of these two Capture Processes - QA Review Integrated Scans or Post Link QA. This is a completely automated process. If at any point the document fails validation it is routed to a review queue.
If the document meets certain exclusion criteria it is automatically removed from Content Conditioning and is not added to the HL7 Sending Lifecycle or added to any Capture processes. Error states or exclusion criteria include duplicate keywords, documents already linked to the EMR, or conversion documents.
When a update (MDM^T08) message is received by OnBase, an import process processes the document updates. If the customer solution includes OnBase integration for a CAC solution an additional import process is configured to send the document to Epic – T08 Document Update (CAC) lifecycle. The lifecycle checks to see if the document being updated is a type configured to be sent to CAC and if so it sends the update message to the CAC system.
When a deletion (MDM^T11) message is received by OnBase, an import process sends the document to the Epic – T11 Document Deletion lifecycle. The lifecycle perform operations similar to Healthcare Corrections when a document is deleted.