Connect

hello@6bdigital.com
0113 350 1290
Contact us

Integrating with: EMIS

In the rapidly evolving landscape of digital health, seamless integration with established Electronic Health Record (EHR) systems is increasingly important.

A significant EHR system in England is EMIS. EMIS is used in more than 50% of GP Practices in England and holds a comprehensive clinical record for each associated patient. At 6B, we specialise in assisting digital health innovators and public health organisations to navigate the complexities of integrating with EMIS, ensuring they can leverage this robust data source effectively.

In our latest post we take a brief look at the various EMIS integration paths and some of the common EMIS integration requirements we come across.

Finding and Fetching Patient Data from EMIS

Integrating with EMIS often involves locating and retrieving patient data from EMIS. This requirement can either be the extraction of EMIS data in bulk (more on this later in this post), or the transactional retrieval of EMIS data.

One common route to find and fetch patient data transactionaly from EMIS is the EMIS PartnerAPI IM, which offers methods like GetMatchedPatient to find patients based on specific criteria and GetMedicalRecord to fetch detailed medical records. These methods return XML-formatted data, which requires careful handling to ensure compliance with EMIS’s data use policies.

When integrating with the EMIS Partner API, security is enforced using GUID tokens, which are essential for initialising API interactions. Each application is restricted to the API calls necessary for its function, providing a secure and controlled integration environment.

Posting Patient Data to EMIS

Another common requirement when integrating with EMIS is the ability to post structured and (SNOMED CT) coded patient data to EMIS.

For posting structured and coded patient data back to EMIS, the EMIS PartnerAPI IM FileRecord method is typically used. This process requires an API password and involves filing data, coded values, or text comments as new records against the patient record (e.g. a consultation, test result, or observation). When posting patient data to EMIS it is crucial that all data filed into the EMIS patient record is user-reviewed and adheres to EMIS formats.

Bulk Data Extraction from EMIS

EMIS also supports bulk data extraction through the EMIS Health Extraction IM (Extraction IM API).

The EMIS bulk API allows the creation of data subsets, delivering them in encrypted CSV files to a secure FTP site. When a new extract is initiated, a complete dataset is delivered in bulk, allowing subsidiary services to access up-to-date clinical records within 24 hours. EMIS Extraction IM offers two primary architectural solutions for bulk exports:

  • Single Extract for Multiple Organisations: This configuration is ideal for services that require cross-organizational data, delivered to a single secure FTP site.
  • Organisation-Specific Extract: Here, datasets are delivered to individual secure FTP sites for each organisation, suitable for services providing end-user functionality at the organisational level.

Each dataset is secured by SSH for the FTP site and PGP encryption for the CSV files, ensuring a robust security framework. The Extraction IM allows subsidiaries to configure their extract datasets, selecting the necessary tables for their service. This flexibility ensures that each subsidiary can tailor their data extracts to their specific needs, optimising the integration process.

Understanding the EMIS IM1 Integration Process

A common path to integrate with EMIS is via IM1, and integrating with IM1 involves several stages to implementation that can take several months. Below we have listed the key stages to IM1 integration conformance:

  • Initiation: Identify the product and complete the initial SCAL with product information.
  • Unsupported Test Phase: Develop using the Pairing and Integration Pack.
  • Supported Test Phase: After development, request access to the Supported Test Environment.
  • Assurance: Submit evidence and undergo testing to achieve assurance from NHS Digital.
  • Live Deployment: Roll out the live product and manage changes through the RFC process.

Find out more about the IM1 integration process on the NHS England website here: https://digital.nhs.uk/services/gp-it-futures-systems/im1-pairing-integration.

How can 6B help with EMIS integration?

At 6B, we have extensive experience developing integrations with EMIS, via IM1, via the EMIS Partner Programme, via GP Connect, as well as other routes, and we provide comprehensive support for digital health innovators looking to integrate with EMIS, from initial consultation to live deployment.

This post was just a very quick overview of EMIS integration, if your team is considering EMIS integration please contact 6B for assistance and leverage our expertise to implement your EMIS integration quickly, securely, and compliantly.

Ready to accelerate your technology project?

Chat to our team of experts and let's see how we can help you.