Audiqueen is particularly well suited for seamless integration into your Electronic Medical Record (EMR). When you open your patient's record in the EMR, you will find an Audiqueen button to open the Audiqueen record of the same patient.
For EMR integration, there are 3 aspects to be considered:
- How to open Audiqueen from within the EMR?
- How to send information from the EMR to Audiqueen?
- How to send information from Audiqueen to the EMR?
How to open Audiqueen from within the EMR?
Context integration is by far the simplest and most robust. Here, your IT specialist creates an Audiqueen button or menu item in the EMR and this button launches AUDIQUEEN with a few arguments, such as patient number, first name, gender and DOB. Clicking this button opens AUDIQUEEN with the updated patient data. See the support page on Context integration (or the Audiqueen Context Integration Manual) for details.
This method also works if your EMR is a web application. In this case, your IT specialist will provide a link in the EMR to a URL that opens Audiqueen, with the URL containing the necessary arguments as query parameters, which Audiqueen will then accept as arguments.
How to send information from the EMR è Audiqueen?
There is only a limited need to send more information from the EMR to Audiqueen. This is because the most important data are the administrative patient data such as name, first name, date of birth, address, etc., and these are passed through the context integration and updated every time the patient's Audiqueen sheet is opened from the EMR.
But there are specific situations where it is useful to send information from the EMR to Audiqueen. This is then done through HL7 messages. Audiqueen can currently be set up to listen to the following HL7 messages:
- Patient Merge using HL7 ADT A40
- Patient Demographics using HL7 ADT A01, A04, A08, A28, A31, or SIU S12, S13, S14
- Patient Query: ADR A19
How to send information from the Audiqueen è EMR?
In principle, there is no need for Audiqueen to send information back to the EMR. Indeed, Audiqueen is an autonomous application with its own SQL database that stores all raw data in complete security and can be accessed from all workstations running Audiqueen.
However, the hospital's IT policy sometimes requires a copy to be kept of data in the EMR database. Although data are then stored twice in two separate databases, Audiqueen can be set up to do this. Raw Audiqueen data are then converted to pdf files and these as well as all other files are then forwarded to the EMR. This can be done automatically for each result stored in Audiqueen, or manually by the user (see the corresponding support page) if they want a single result to be sent to the EMR.
There are 2 ways to implement this (see the support page on File Dump for more details):
- Either Audiqueen saves the file under a specified name in a particular folder, where the EMR can retrieve the file and then store it in its own database;
- Or, Audiqueen sends an HL7 ORU message with the file to the EMR.
Resources:
- Audiqueen 3 Context Integration Manual for details
- Audiqueen 3 HL7 Integration Installation Manual for details