Sunquest to EPIC Beaker transition

Hi Christy,
  We are a large heath system going through the same transition and were also given a firm "no" from the Epic/Beaker team on the acknowledgement sendback that we currently have from Sunquest in the form of an accession number back to QML.  The response was simply "Beaker doesn't do that."   While I, like you, would prefer to have the acknowledgement received back to QML in real time to stay ahead of unsuccessful result postings, an alternative is to look for Interface (error) Messages in Beaker-Epic that indicate a result has not been successfully posted.  Not great, but it's something.

Usually someone from the LIS team monitors interface errors and reports them to operations. There is a work queue in Epic that interface errors populate to. Additionally, you could see if the analytics team can set up a report or dashboard for you to monitor independently to narrow down point of care only.

Thanks for this Sheena - we would love to make it as real-time as possible, so we may be pursuing those.

I am not familiar with SunQuest....
If I am understanding your question correctly...We completed our transition from MediTech to EPIC earlier this year. We have the interface between QML and EPIC as unsolicited. The patient's armband is scanned for the EPIC CSN which is the same as the account number or visit number. Results are sent through QML directly to EPIC where the order, accession number, and charge is generated at the time the EPIC EMR receives the result. So, in our case, there is no accession number coming FROM EPIC/Beaker prior to testing. The accession number is not generated until the result hits EPIC. Almost everything except the accession number is visible in the QML Repository.

Here is some additional information on our current and future workflows.  We currently use armbands and scan the CSN.  Plan to continue this with Beaker.  Sunquest interface is two directions.   Results are sent from QML to Sunquest.  Sunquest orders the test and creates an accession number.  The accession number is then sent back to QML and is found in the Repository with the results.  In this way we can monitor if there is an issue with interface. 

James, is the LIS team the ones who will monitor the Interface (Error) messages or will you?

Sheena, Do you use this report or dashboard to monitor this currently?  Is this in real time? We also currently use a report to know the time it takes for results to post to EPIC EMR, but this is sent to us the next day. 

I appreciate all the feedback. Thanks,