IM1 Pairing integration

Interface mechanisms enable separate systems to:

• read patient information
• extract information in bulk
• enter data into the other system

You can find more information about each of the IM1 interfaces.

There are 2 existing suppliers, who providing the Foundation Solution set to meet the Foundation Capabilities on the Digital Care Services Framework, they each offer interfaces for consuming systems to integrate with, Optum (EMISWeb) and TPP (SystmOne).

There are also several new suppliers who will provide the foundation set capabilities once they have completed the onboarding process for the Digital Care Services Framework.  

Each supplier of foundation capabilities must provide an 'interface mechanism' for use by third party systems to support integration between the core providing systems and specialist applications, such as clinical decision,  support, patient facing services, document management or appointments.

Interface mechanisms enable separate systems to: 

• read patient information
• extract information in bulk
• enter data into the other system

The interface mechanisms for the provider suppliers offer under the digital care services framework must comply with the IM1 - Interface Mechanism - GP IT Futures Capabilities and Standards - Confluence (atlassian.net).

Any consuming supplier can apply to 'pair' their service with any provider supplier system.  

Complete the IM1 Clinical and Information Governance prerequisites form IM1 prerequisites form.

Supplier Conformance Assessment List (SCAL) will be issued if prerequisites are confirmed and in place as part of the application process. Your application will be assessed for compatibility against the provider suppliers' APIs and you will need to include some information about the product you are wanting to develop. We may also ask you to submit evidence to show you meet the SCAL requirements. 

When we have confirmed your product is compatible, you will be asked to execute a Model Interface Licence with each of the provider suppliers, this will cover your use of the provider suppliers' APIs. Once the Model Interface Licence has been executed by both consumer and provider suppliers, you will be given access to a test environment so you can develop your solution using the provider supplier guidance/documentation. 

IM1 process flow

Initiation

• identify product
• prerequisites are confirmed and in place
• complete stage one SCAL with requested product information
• NHS England IM1 team confirms if product is viable via API
• complete model interface licence
• access to provider supplier mock API

Unsupported Test Phase

• develop using Pairing and Integration Pack (PIP)
• work to fully complete SCAL in preparation for assurance

Supported Test Phase

• once development is complete, request access to Supported Test Environment (STE), by submitting your fully completed SCAL
• work directly with provider supplier to agree assurance approach

Assurance

• SCAL reviewed and agreed by NHS England
• test evidence agreed or witness test undertaken
• assurance accepted by NHS England and Recommended to Connect issued
• Plan to Connect issued by provider supplier
• live product rolled out to provider supplier estate 
• Model Interface Licence uplifted to include assured SCAL
• Suppliers are required to submit a formal Request for Change (RFC) where a product has evolved from its originally assured IM1 use case. In particular through the integration of Artificial Intelligence (AI) or other significant functional enhancements. This should be submitted along with an updated SCAL and all associated documentation

Live

• general changes to the live product, including functionality and use case, are requested via the Request for Change (RFC) process
• provider and consumer suppliers attend the IM1 supplier forum

We have listed all the suppliers who have already completed IM1 assurance in the table below.  

The IM1 onboarding process is a structured, NHS England managed pairing approach designed to ensure that products integrating with GP IT systems are subject to appropriate due diligence. This process is carried out in collaboration with Foundation GP Suppliers and covers areas such as technical conformance, clinical safety, and information governance. 

For products containing artificial intelligence (AI), this means a review of the whole product documentation will have been undertaken during pairing.

This includes: 

• DCB0129 Clinical Safety Case and Hazard Log 
• Data Protection Impact Assessment (DPIA) 
• Confirmation of medical device registration, where applicable
• Hazard Log and Safety Case documentation from any Sub Processors, may also be required as part of their assurance review 

However, it is important to note that the IM1 pairing, and the integration process does not include AI-specific technical assurance, such as assessment of the AI models, algorithms, or associated risks. This type of assurance is out of scope of the IM1 process, as defined by the Model Interface Licence. 

Until further guidance is issued by NHS England, deploying organisations remain responsible for carrying out this level of technical assurance locally, as part of their product assessment and assurance due diligence.