Overview of the different types of deployment topologies for brokering API calls through the SSP
Important: The topologies depicted are illustrative rather than prescriptive.
Important: The Spine Secure Proxy includes a mechanism to filter out all requests between organisations that are not registered on the proxy as having a mutual Data Sharing Agreement. Without this then all consumers would be able to send requests to all API Providers.
In order for the filtering solution to work each consumer/provider organisation needs their Spine ASID configured on the SSP.
Consumer Topologies
Simple Model
A grouping of different GP Connect consumer systems, all connecting directly to GP Connect via the SSP. Each consumer in this example is registered as a CMA endpoint. The key point is that each consumer system has its own ASID.
Aggregator Model
Several different consumer systems connecting to GP Connect via middleware (Message Handling Server / MHS)
Provider Topologies
Single Practice System
A discrete instance of a Primary Care System serving a single GP Practice.
Data Centre Hosted Practice System
A GP Practice system instance hosted in a Primary Care System (PCS) supplier’s data centre. Note each individual practice has a logical CMA endpoint with its own ASID but sharing the Party Key.
Spine Endpoint Terms
The terms used above are explained in detail on the SDS endpoint lookup page.
