View by category
Does ClinicalKey offer the ability to integrate with Electronic Medical Records/Electronic Health Records (EMR/EHR) or InfoButton Manager systems?
Last updated on December 13, 2022
ClinicalKey offers the ability to integrate with EMR/EHR or InfoButton Manager systems. ClinicalKey Integration is available at no extra cost with an active institutional subscription and has the following benefits:
- As a Clinical Decision Support tool, ClinicalKey can deliver meaningful improvements in quality and outcomes, increased avoidance of errors/adverse events, and also increased efficiencies in time, cost and speed to evidence.
- ClinicalKey EHR Integration empowers clinicians by reducing workflow interruption, increasing speed to answer, and minimizing clicks within the systems used every day to manage and provide care.
- Integrating ClinicalKey within your institution's EHR enables clinicians to access the latest evidence-based content relevant to each patient's care-available at the point of need.
Click on the topics below to find out more information:
ClinicalKey is capable of search integration via HL7 Context-Aware Knowledge Retrieval with every modern EMR/EHR system that is capable of creating an InfoButton search from within a patient's chart. The InfoButton search must meet the HL7 Messaging Standard criteria as outlined in the implementation documentation available to ClinicalKey customers.
Additional integration methods are available for EHR systems that meet ClinicalKey's specifications.
If you are interested in integrating ClinicalKey with your institution's EHR, please contact your Elsevier Account Manager. You also may contact us using one of the options located below. (Please be prepared to provide your institution's name, EHR, and the technical or clinical contact to expedite the integration process.)
ClinicalKey EHR Integration does not store Personal Health Information (PHI). ClinicalKey's InfoButton Integration and other such integrations that use the HL7 Messaging Standard are implementations of a context-aware Clinical Decision Support (CDS) intervention eligible to fulfill the CDS Rule of Meaningful Use Stage 2 [170.314(a)(8)].
Please note: ClinicalKey is a completely separate platform to the EHR and the only information ClinicalKey may access is the information added to the URLs that are sent by the EHR.
In the case of HL7 Messaging Standard queries, information is sent in a de-identified form by the EHR, as the HL7 Messaging Standard is inherently compliant with HIPAA (Health Insurance Portability and Accountability Act of 1996).
In the case of URLs sent as a result of a search entered into the EHR's search box by an authorized user, the same HL7 Standards are applied: all patient context is sent to ClinicalKey in a de-identified form.
Did we answer your question?
Related answers
Recently viewed answers
Functionality disabled due to your cookie preferences