Single consumer system

This represents (typically) a GP Practice with a single system hosted locally or a single instance hosted elsewhere. This topology has a single Common Management Agent (CMA) endpoint.

Supplier data centre hosted consumer

This is typical of a large GP systems supplier with many practice instances hosted in a data centre, where a message handling system (MHS) endpoint is used and each instance has its own ASID.

Acute trust portal using a trust integration engine (TIE)

This represents an acute trust acting as a GP Connect consumer via a TIE, showing the information on a clinical portal and ingested into an electronic patient record (EPR).

Notes:

• the ASID is for each system which consumes data from the GP record
• the acute systems and non-GP Connect endpoints depicted are for illustrative purposes. An e-Referral Service (e-RS) endpoint is not a prerequisite for GP Connect

Regional shared care record

A regional shared care initiative hosted by one of the participating organisations might have a similar topology. This illustrates a consuming portal deployment. The hosting organisation holds the ASID for the consumer application and (subject to the usual governance controls) the data can be shared via the portal to other organisations. However, in such scenarios it is important that the originating clinician and organisation details are provided in the request so that consumer and provider audit requirements can be met. See Cross organisation audit and provenance.

Spine endpoint terms