GP2GP Management Information MESH

Use this integration to provide information to us on the progress of the patient migration process between GP practices (GP2GP). 

This involves recording patient registration activity in the GP systems at specific stages in the patient migration process.

This integration uses MESH to send and receive messages.

For details, see NPFIT-PC-BLD-0173.01 GP2GP UC 2 Harvest and Prepare Management Information which describes the high level use case for reporting capability required by GP2GP 2.2b.

This integration can only be used where there is a legal basis to do so. Make sure you have a valid use case before you go too far with your development, by contacting us.

You must do this before you can go live (see ‘Onboarding’ below). 

The following APIs are also related to this integration:

• GP2GP - HL7 V3 API - use this to transfer patients' electronic health records, securely and quickly, between their old and new practices when they change GPs
• GP Registrations Management Information API - use this to send real-time management information about GP registrations to us (in future, replacing this integration)

This API is in production, but under review for deprecation. 

We plan to deprecate and retire it once its replacement is live. We will contact you before agreeing to a retirement date.

This integration uses MESH which is a silver service, meaning it is operational 24 hours a day, 365 days a year but only supported during business hours (8am to 6pm), Monday to Friday excluding bank holidays.

For more details, see service levels.

This is an asynchronous messaging integration.

Messages are sent and received as CSV files via MESH

For more details, see MESH.

This integration is available on the internet and on the Health and Social Care Network (HSCN).

For more details see Network access for APIs.

This integration uses MESH which is an application-restricted API.

This integration does not perform any end user authentication or authorisation checks. Rather, the calling system is expected to perform them. 

This integration uses MESH.

As a developer, you are most likely to want to connect to MESH using either the MESH client or the MESH API.

For more details about using the MESH client, see MESH client.

For the MESH API, there are several independent, externally accessible instances of MESH you can use for testing. For full details, see MESH API - Environments and testing.

You need to get your software approved by us before it can go live with this integration. We call this onboarding. The onboarding process can sometimes be quite long, so it’s worth planning well ahead.

Contact [email protected], to onboard with this integration.

This integration uses the following MESH workflow IDs to provide information to us on the progress of the patient migration process between GP practices (GP2GP):

• GP2GP_MI
• GP2GP

For a full list of interactions for this integration, see the Management Information section of the GP2GP 2.2b specification.