National Integration Adaptor - GP2GP Sending Adaptor
The existing GP2GP solution uses a legacy messaging standard and infrastructure (HL7v3 and Spine TMS). Reliance on these standards going forward presents a significant barrier to successful GP2GP implementation by new suppliers, and perpetuation of these standards in the long term presents a risk to the continued operation of GP2GP across all suppliers.
A hybrid solution approach has been selected as the best option for GP2GP adoption by NMEs and transition by existing incumbent suppliers.
The "National Integration Adaptor - GP2GP" implements a GP2GP 2.2b producer using the supplier's existing GP Connect Provider implementation to extract the Electronic Health Record. Suppliers that have not already implemented a GP2GP 2.2b producer, or those wishing to decommission their existing producer, may deploy the GP2GP adaptor in its place.
- Guidance for setting up the GP2GP adaptors in INT
- Guidance for operating the adaptor as a New Market Entrant
- Guidance on integrating with the adaptors APIs
- Documentation on how this adaptor maps GPConnect concepts to GP2GP concepts
An API is provided to query the status of GP2GP transfers that have been processed, and initiate a resend of an Electronic Health Record which has failed to transfer.
The API has been documented using the OpenAPI Specification (version 3.0.1) and includes detailed descriptions of endpoints, parameters, and data models, as well as examples of requests and responses to help developers integrate and use the API effectively.
The documentation can also be displayed using editor.swagger.io (exteral link).
If you are are New Market Entrant, please read the guidance linked from the table of contents. If you are looking to make changes to the adaptor you should first read the guidance for developing the adaptor.
All Patient data within this repository is synthetic
This code is dual licensed under the MIT license and the OGL (Open Government License). Any new work added to this repository must conform to the conditions of these licenses. In particular this means that this project may not depend on GPL-licensed or AGPL-licensed libraries, as these would violate the terms of those libraries' licenses.
The contents of this repository are protected by Crown Copyright (C).