Library

Browse and search developer information

Stage 3: Development

This section is relevant to developers when starting to build the SMS Client

Summary

The information and resources below (and in Stage 4: Test and Assurance) are for the Supplier to use during development and testing of the SMS Client, as part of the overall process to achieve NHS Digital Technical Conformance approval for the product.

SMS Cheat Sheet

SMS Developer Cheat Sheet shortcuts for the technical build of SMS clients accessing the web service APIs.

SMS Cheat Sheet

Shortcuts

Explore

Three functional requirements are included in the Requirements Pack:

  • PDS Message Specifications within the ‘PDSMiniServices.zip’
  • SMS Functional Requirements – Foundation in the ‘ITK Spine Mini Service – Common Client Requirements-v1.0.pdf’
  • SMS Functional Requirements – Demographics in the ‘PDS – Spine Mini Service Client Requirements-v1.0.pdf’

Build

  • Java Reference Implementation – see below
  • .NET Classes for ITK SOAP Services

Test

See SMS Test Environments

SMS Developer Requirements

As described in the NHS Digital compliance process, if a Supplier does not already have a conformant product (Client), Technical Conformance approval must be obtained. This begins with developing the Client in line with the necessary requirements (including specifications) and policies.

The main resource for development is the downloadable Requirements Pack, containing functional requirements, policies and guidance relevant to the technical build of SMS clients accessing the web service APIs .

Note: A blank TOM is included in the Requirements Pack but if a TOM has already been populated during the Phase 1a Usage and Settings approval process, a new TOM should not be created; the information required for Phase 1b Technical Conformance approval will simply be added to the Phase 1a information. For further guidance, click here.

SMSP Reference Implementation (Java)

The ITK API provides a Java abstraction to the ITK transport and distribution mechanics. As such it aims to simplify the task of exchanging ITK based messages between applications whilst maintaining all of the benefits that the ITK “on the wire” specifications bring.

The following reference implementation (a client accessing Spine Mini Services for PDS) provides a set of examples scenarios that show how the API can be realised and used in real world uses. One such reference implementation is a client accessing spine mini services for demographics. See more detail here: http://developer.nhs.uk/library/interoperability/nhs-interoperability-framework/

Try It: http://data.developer.nhs.uk/itk/docs/index.html

Artifacts that are direct products of the ITK, API and reference implementation project. http://developer.nhs.uk/downloads-data/reference-implementation-project/