Page Properties | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
Spine Mini Services is a simplified read-only interface to some Spine Services, the most common one being Personal Demographics Service (PDS).
The Spine Mini Service Provider (SMSP) provides a security bridge to the Spine services and lower entry messaging specification which removes some of the complexity of the HL7 V3 interfaces e.g. It allows consumers to query information on Patients without having to develop the full PDS interface or go through the full Common Assurance Process.
It is also a mechanism to retrieve information on:
A Solution that implements the core Patient Information Maintenance - GP Capability is required to have full PDS integration. SMSP may be a suitable alternative to full PDS integration for some Solutions that are not tightly integrated into the core GP Solution and require a read-only source of demographics from PDS.
Requirements
ID | Requirement | Level | ||||||
---|---|---|---|---|---|---|---|---|
SMS01 | Implement and maintain the 4 key requirement specifications below and the common requirements found here Requirements pack and Supplier Conformance Assessment List (SCAL) template.
|
|
Compliance, Assurance and Testing
The assurance model for Spine Mini Services is based around the Target Operating Model (TOM), a simplified approach designed to be less onerous than the full Common Assurance Process. The TOM places a higher emphasis on self-assessment and responsibility of the deploying organisation.
Suppliers should note the two assurance scenarios (with and without a customer organisation) contained within the SMSP Assurance Overview page.
For further information, guidance or support, please contact the ITK Conformance team at itkconformance@nhs.net.
Environments
Information about path-to-live environments can be accessed here: Support.
Documentation
Dependencies
Excerpt |
---|
There may be dependencies for implementing this Standard, however, there are no Interoperability Standards within the Capabilities and Standards model that are dependents. |
Roadmap
Items on the Roadmap which impact or relate to this Standard | ||||||||
---|---|---|---|---|---|---|---|---|
|