Written by Technical Team | Last updated 06.03.2026 | 6 minute read
In healthcare, the ability to efficiently manage and utilise data is crucial for healthcare providers and associated organisations. Seamless IM1 integration with primary care EHR systems in particular is key to unlocking the potential of patient information, driving insights, and improving patient care.
The IM1 Bulk API, originally part of the NHS Digital’s GP IT Futures framework, provides a robust solution for extracting and integrating large datasets from primary care EHR systems SystmOne and EMIS Web. In this post, we look at some of the intricacies of the IM1 Bulk API, focusing on its capabilities, setup process, and benefits for healthcare organisations.
The IM1 Bulk API facilitates the extraction of comprehensive datasets from primary care EHR systems, enabling healthcare organisations to access, analyse, and leverage patient data more effectively.
The IM1 Bulk API supports daily bulk data extraction from SystmOne and EMIS, offering a consistent and reliable method to obtain large volumes of data in a structured format. Accessing the IM1 Bulk API can be pivotal for organisations aiming to enhance data-driven decision-making and streamline reporting processes.
Key takeaway: The IM1 Bulk API enables healthcare organisations to securely extract structured data from major UK primary care EHR systems including SystmOne and EMIS. By automating large-scale GP data extraction and delivery in CSV format, organisations can power analytics, population health insights, regulatory reporting, and integrated digital health services across NHS systems while maintaining strict Information Governance and patient data security.
To extract data in bulk from SystmOne via the IM1 Bulk API, there are several steps that a SystmOne organisation must complete.
Organisations must first configure SystmOne to enable Strategic Reporting, and configure a ‘reporting unit’ to act as the central hub for configuring extracts. The reporting unit can then configure a strategic reporting organisation group (which will include the units whose data will be extracted). Once the SystmOne organisation is configured, users can configure strategic reports to tailor the data extraction to their specific needs, including selecting specific tables and fields. Configuration parameters such as the file delimiter, text qualifier, extract frequency, root directory for downloads, and a technical contact for notifications can be defined during this process too.
Following configuration, the extracted data is delivered in CSV format, with each table exported as a separate CSV file. These files are usually securely downloaded to a designated ‘Gateway PC’ or a cloud server running SystmOne. The download process occurs over a secure TCP channel, usually with redundancy and retry mechanisms in place to ensure data completeness. To enhance data integrity, files are temporarily stored and renamed upon receipt of a complete dataset, allowing for validation. Additionally, an SRManifest file is created for each download, detailing the extracted information and enabling users to monitor the process.
EMIS Health supports bulk data extraction through its Extraction IM API. Similar to SystmOne, this API provides subsets of the clinical record in encrypted CSV files, delivered to a secure FTP site. The configuration process for EMIS involves ensuring sufficient Information Governance (IG) approval for each dataset being extracted, safeguarding personal confidential information. This ensures that data extraction complies with regulatory requirements and maintains patient confidentiality.
EMIS supports two different architectural solutions for data extraction:
The first is a single extract for multiple organisations, where the datasets for each consenting organisation are delivered in a series of encrypted CSV files to a single secure FTP site. This configuration is suited to subsidiary services that report on cross-organisational data from a centrally hosted system. Data is then most commonly downloaded from the secure FTP site directly to the subsidiary supplier’s data centre.
The second solution is an organisation-specific extract, where the datasets for each consenting organisation are delivered in individually encrypted CSVs to organisation-specific secure FTP sites. This configuration is suited to subsidiary suppliers who are providing end-user functionality at an organisational level. Data is most commonly downloaded from the secure FTP site directly into an application hosted by the organisation that is the data controller.
Each dataset from EMIS is protected by a pair of security keys, ensuring secure data transfer and storage. The subsidiary service, responsible for consuming the data, holds the private keys and provides public keys to EMIS Health during the extract setup process. Depending on the configuration, data can be downloaded directly to the subsidiary supplier’s data centre or an application hosted by the organisation.
The IM1 Bulk API is a powerful interface for healthcare organisations seeking to leverage patient data for improved care and operational efficiency.
Through facilitating the extraction of large datasets from SystmOne and EMIS EHR systems, the IM1 Bulk API enables detailed analysis, reporting, and data-driven decision-making. Through proper configuration and secure data handling practices, organisations can unlock the full potential of primary care EHR data, driving better outcomes for patients and the healthcare system as a whole.
What is the difference between the IM1 Bulk API and other NHS integration APIs such as GP Connect?
The IM1 Bulk API is designed for scheduled extraction of large datasets from GP clinical systems such as EMIS Web and SystmOne. By contrast, APIs like GP Connect focus on real-time access to specific patient information for direct care scenarios. IM1 bulk extracts are typically used for analytics, population health management, reporting, and service planning rather than immediate clinical decision-making.
Who can access data through the IM1 Bulk API?
Access to the IM1 Bulk API is restricted to authorised digital suppliers and organisations that have completed NHS onboarding, including Information Governance and clinical safety requirements. GP practices must also grant explicit permission before any bulk extraction of patient data can occur, ensuring data sharing agreements and compliance processes are in place.
How often can IM1 Bulk API data extracts be generated?
Depending on the configuration agreed with the GP system supplier, organisations can request data extracts on a daily, weekly, or monthly basis. Typically, a full dataset is generated during the initial setup, followed by incremental updates (often referred to as delta extracts) that capture changes to records since the previous extraction. This helps maintain up-to-date datasets while reducing data transfer overhead.
What types of applications typically use IM1 Bulk API data?
IM1 Bulk API data is commonly used by healthcare analytics platforms, population health management systems, research initiatives, commissioning support tools, and reporting platforms. These applications use GP data extracts to identify trends in patient populations, measure service performance, and support strategic decision-making across NHS organisations.
What approvals are required before integrating with the IM1 Bulk API?
Suppliers integrating with the IM1 interface typically need to complete the IM1 pairing process, demonstrate compliance with NHS Information Governance standards, and pass technical and clinical assurance checks. This process may include completing the Supplier Conformance Assessment List (SCAL), signing interface licences with GP system suppliers, and performing witness testing before a system is approved for live integration.
Is your team looking for help with IM1 Bulk API integration? Click the button below.
Get in touch