Page Properties | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Page Properties | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
...
Captures MI events across the Registrations end-to-end journey in JSON format via a RESTful API
Captures event in near-real time
Captures additional information about the registration part of the process
Captures information about placeholders, attachments and degrades
Is more extendable for the future
Full specification: https://digital.nhs.uk/developer/api-catalogue/gp-registrations-management-information
Getting Started
Read through the GP Registrations Management Information API
Login to the NHS developer portal
Add an application - GP Registrations Management Information API (Integration Testing Environment) to generate an API Key
Use the Postman examples to understand the requirements of each endpoint.
https://github.com/nhsconnect/prm-gp-registrations-mi/tree/main/doc/postmanFollow the Assurance Approach to validate the implementation.
Useful Links
Postman API Collection https://github.com/nhsconnect/prm-gp-registrations-mi/tree/main/doc/postman
Outline Plan
All Foundation Suppliers must be compliant against this specification by the effective date.
...
GP2GP: Link Removed from Supplementary Specifications |
Supplementary specificationsThe following supplemental specifications contain additional requirements and guidance for GP2GP implementation: NPFIT-FNT-TO-TIN-1087.02 GP2GP Supplementary Specification on Handling Medication Discontinuation.pdf NPFIT-PC-BLD-0069 24 GP2GP Spine Technical Design v7.1.pdf NPFIT-PC-BLD-0083.08 GP2GP Response Codes.pdf NPFIT-PC-BLD-0099.04 GP2GP Handling Missing Attachments.pdf NPFIT-PC-BLD-0132.03 GP2GP Supplementary Specification on Structured Degrade Handling.pdf NPFIT-PC-BLD-0133.02 GP2GP Supplementary Spec - Handling and Propagation of Non Consultation Data.pdf NPFIT-PC-BLD-0134.05 GP2GP Supplementary Specification Representing PMIP Data in GP2GP Messages.pdf NPFIT-PC-BLD-0158 GP2GP Supplementary Specification Attachment References.pdf NPFIT-PC-BLD-0163.02 Topic and Category Handling in GP2GP.pdf NPFIT-PC-BLD-0170.03 GP2GP SS Handling Large Messages.pdf
NPFIT-PC-BLD-0172.02 GP2GP UC1 Transfer Electronic Health Record.pdf NPFIT-PC-BLD-0173.01 GP2GP UC 2 Harvest and Prepare Management Information.pdf NPFIT-PC-BLD-0175.03 GP2GP SS Handling A-B-A Transfers v1.3.pdf NPFIT-PC-BLD-0177.01 GP2GP SS User Experience.pdf NPFIT-PC-BLD-0178 02 GP2GP Coding Scheme Translation v1.1.pdf NPFIT-PC-BLD-0180.02 GP2GP Transfer of Patient Facing Service Settings 04.pdf NPFIT-PC-BLD-181.02 GP2GP Handling the SCR indicator v03.pdf NPFIT-FNT-TO-IG-DES-0115.01 Statement on Data Retention v1.0.pdf NPFIT-FNT-TO-TAR-0017.07 Compliance Requirements for Patient Registration.pdf NPFIT-FNT-TO-TIN-0289.08 GP2GP Supplementary Specification on Handling Attachment Types.pdf |
GP2GP: Requirement GP2GP05 added |
ID | Description | Level | ||||||
---|---|---|---|---|---|---|---|---|
GP2GP05 | Suppliers must implement and maintain the GP Registrations Management Information API inline API inline with the latest specification version |
|
GP2GP: Requirement GP2GP03 updated |
ID | Description | Level | ||||||
---|---|---|---|---|---|---|---|---|
GP2GP03 | Suppliers must provide support to receivers of GP2GP messages to resolve any issues with interpreting, consuming and processing received messages |
|
Full Specification
/wiki/spaces/GPITFDS/pages/12167151617GP2GP v.4.0.0
Assurance Approach
The Assurance Approach for this service is to:
...