This site contains tools to explore and develop GP Connect API consumer applications.
The consumer system demonstrator illustrates how the GP Connect API might be integrated with an electronic patient record (EPR) or Trust portal system.
This is a reference implementation of the GP Connect API simulating a GP system's GP Connect interface.
To interoperate with the reference implementation using your own development/test environment, use the following FHIR service root URLs:
|GP Connect API 0.7 (DSTU2)||Access Record HTML||
|GP Connect API 1.2 (STU3)||Appointment Management/ Foundations||
|Access Record Structured (v1.2)||
|GP Connect API 1.5 (STU3)||Access Record Structured (v1.5)||
Alternatively you may look the above URLs up on our Spine Directory Service.
Interactive API documentation, built using Swagger UI, is available for developers to test calls against the API reference implementation using their web browser.
Try the interactive API document'n
for Access Record HTML Try the interactive API document'n
for Appointment Management Try the interactive API document'n
for Access Rec. Structured (v1.2) Try the interactive API document'n
for Access Rec. Structured (v1.5) Try the interactive API document'n
for Access Document
Run Postman samples to test calls against the API reference implementation.
Test patients and other data held within the demonstrator is listed here.
An SDS server containing the MHS and AS records needed to discover the provider reference implementation endpoints by ODS code.
Please see here for instructions on the LDAP queries to run in order to discover the provider reference implementation endpoints.
*Please note: this SDS server contains records in order to discover the GP Connect provider reference implementation ONLY, and does not contain other records as would be found in Spine test or production environments.
Documentation for the Opentest environment can be found here.