There are several different types of deployment topologies for brokering API calls through the SSP:

Consumer models

Provider Models

Consumer models

Simple Model

In this model, each different Care Connect consumer systems, all connecting directly to an appointment provider 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

 see: https://developer.nhs.uk/apis/spine-core/ssp_system_topologies.html

Aggregator Model

Here, several different consumer systems connect to the Spine via a single middleware instance (Message Handling Server / MHS)

see: https://developer.nhs.uk/apis/spine-core/ssp_system_topologies.html

Provider Models

Single System Model

Here a single instance of an appointment provider system is service a single service:

see: https://developer.nhs.uk/apis/spine-core/ssp_system_topologies.html

Data Centre Hosted System Model

Finally, an appointment provider system instance hosted in a supplier’s data centre. Note each individual service has a logical CMA endpoint with its own ASID but sharing the Party Key:

see: https://developer.nhs.uk/apis/spine-core/ssp_system_topologies.html

See also:

Legend for diagrams: see: https://developer.nhs.uk/apis/spine-core/ssp_system_topologies.html

For further information and source for this page, please see here (links to core SPINE documentation)