cancel
Showing results for 
Search instead for 
Did you mean: 

Delay an HL7 Message send in Workflow

Scotty_Barkley
Champ in-the-making
Champ in-the-making

I have a workflow where a coupon document is stored in OnBase.  It has a keyword "Expiration Date".  The initial Expiration date is 30 days from the time the document is created by a provider putting and order for a medication in Epic.  We receive a T02 which creates the document in OnBase.  If the provider decides to cancel the order....maybe 5 minutes after entering the order (say for example, they realize they made a mistake), once the cancellation is done in Epic, an Update T02 is sent which updates the Expiration Date and makes it equal to the current date.  We have a workflow that evaluates the Document and if the Expiration Date keyword is equal to the current date, workflow is supposed to fire a T11 to Epic to break the link to the document between Epic and OnBase.  

We are having an issue where providers will cancel an order, for whatever reason, before a minute has passed since the order was first placed.  As a result, the update T02 is making it thru workflow before the original T02 has a chance to make it out of the workflow and the T11 is overriding the sending of the Initial T02 that was supposed to go out the interface and to Epic to create the link.

As a result the document appears as follows in OnBase:

26bf08900c944be4a473bdac791bf3ac

 

Also, an error appears in Epic because of this.

I am thinking of getting around this by adding a timer in workflow to delay sending of the T11 so that the first iteration of the document from the first T02 can make it thru the workflow and the intial T02 gets sent to Epic.

I want the following step, indicated by the red selection box, to be delayed for about 3 minutes so the T11 will be delayed but I am not exactly sure how to configure the timer in the workflow.

Does anyone know how to go about doing this?

636c583e40e64a32a6b670337c36cfd5

1 REPLY 1

Hi Scotty,

 

You likely won't be able to use a timer within the CC01 - Clinical Processing queue that you have pictured without a lot of re-structuring of that workflow. This is because the work that you are highlighting is being done under "System Work" which happens as soon as a document enters workflow. You can't add timers within "System Work".

 

One way you may be able to handle this is instead of sending your T11 out of the CC01 Workflow / CC01 Clinical Processing queue you could add an action in its place to "Add Item to Other Life Cycle". This would add your document to another lifecycle. You would then set up a queue and set up a timer under "Timer Work" in this other life cycle. The timer would be set to run every minute and it would evaluate the rule "Check Date Property Value". You can use this rule to compare a document's "Queue Entry Value / Time" against the "Current Date/Time" and you could make it so that the T11 only sends if the document can pass this rule which is evaluated every minute.

 

Hopefully that can get you started. Good luck!

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.