The technical implementation to connect to SPINE is relatively intricate. The ITK Spine Mini Services have been created to provide a simpler route to access national services.
The Spine Mini Services specifications define how to connect to NHS National Services, commonly known as the Spine. Essentially these are a set of specifications to enable suppliers of third party software to provide solutions for a greatly simplified interface for accessing a subset of the SPINE services e.g. PDS, SCR. The intent is to lower the “barrier to entry” to the SPINE.
The Spine Mini Service Provider pack contains: Common Client Requirements, Common Provider Requirements along with specific requirements associated with the particular National Service being accessed. Currently this pack contains specific requirements for accessing Patient Demographics Service (PDS) and is being enriched to contain additional specifications for accessing other National Services e.g. Summary Care Record (SCR).
The technical implementation to connect to SPINE is relatively intricate. The ITK Spine Mini Services have been created to provide a simpler route to access national services.
The Spine Mini Services specifications define how to connect to NHS National Services, commonly known as the Spine. Essentially these are a set of specifications to enable suppliers of third party software to provide solutions for a greatly simplified interface for accessing a subset of the SPINE services e.g. PDS, SCR. The intent is to lower the “barrier to entry” to the SPINE.
The Spine Mini Service Provider pack contains: Common Client Requirements, Common Provider Requirements along with specific requirements associated with the particular National Service being accessed. Currently this pack contains specific requirements for accessing Patient Demographics Service (PDS) and is being enriched to contain additional specifications for accessing other National Services e.g. Summary Care Record (SCR).
The CP-IS Provider Requirements document has been updated with a change to the response code table to resolve ambiguity in usage of the SMSP error code response when a TMS acknowledgement message is received from Spine, and a requirement to validate the request payload assignedAuthor attributes against SDS if the client making the request is Spine RBAC enabled has also been added.
Released on Wednesday, 21 January 2015