Library

Browse and search developer information

Quickstart Steps 1-4

The 4 steps in the Quickstart process

Quickstart Steps

If you require any further implementation guidance please contact itkconformance@nhs.net

Step 1 – Functional requirements

The ITK Spine Mini Service functional specifications are available in the Requirements Pack and the first three that should be read are:

1. The ‘PDS – Spine Mini Services Provider Requirements-v1.0.pdf‘ document contains the details of the information model shown above. It also explains the provider requirements, the request message descriptions, plus behaviours of wildcards and data type format. Note: NHS Digital have implemented the Spine Mini Service as a central solution.

2. The ‘PDS – Spine Mini Services Client Requirements-v1.0.pdf‘, a document which the Client developer will need to read to ensure the application meets the requirements within.

3. The ‘SMSP Response Code – v1.0.xls’ spreadsheet, which as the name suggests contains the general service message response codes and PDS specific ones. An example being a successful query would contain an SMSP-0000 Success code< value codeSystem=”2.16.840.1.113883.2.1.3.2.4.17.285″ code=”SMSP-0000″/>

Step 2 – Message Specification

The ‘PDS Mini Services Domain Message Specification’ is also in the Requirements Pack.

The message specification contains all the details of the SOAP message requests and responses. It also includes the wsdl file (PDSMiniServices-v1-0.wsdl under \schema\wsdl), and some specific message examples under the ‘Payload’ column. It should be noted that the wsdl file has not been created for importing into frameworks capable of automatically building proxy classes.

ITK SOAP Messages contain a number of layers, as detailed below to:

SOAP Message

SOAP Message

The ‘Payload’ detailed within the message specification refers to the Payload shown within the diagram above, which is a child element within the distribution envelope.

So what does the diagram actually look like in XML? The extract below (click to zoom) shows the SOAP Envelope, the SOAP Head, SOAP Body, and within the body (under the itk namespace) the ITK Distribution Envelope. The distribution envelope is used within all ITK SOAP Web Service calls, containing a header with the audit identity (the accredited system identifier provided during the endpoint registration process, linked to the calling organisations’ ODS code).

XML SOAP Request Head and Distribution Envelope

Step 3 – Quick Test

This quick test assumes access to NHS Digital Opentest or one of the Path-to-live environments (details can be found here – N3/HSCN link required), using a template of the GetNHSNumber message and curl to access the service.

Firstly we convert the NHS Digital provided PKCS#12 file (for a specific environment) into a PEM, for use with curl: openssl pkcs12 -in pkcs_filename.p12 -out pem_filename.pem -nodes -clcerts

Using this file getNHSNumber.xml which contains a test patient example from the opentest environment, execute the following curl command, substituting the certificate name and message endpoint (Opentest url shown in example). Note: the patient search details may need to be altered depending on the environment being accessed.

$ curl -i -X POST -H “SOAPAction: urn:nhs-itk:services:201005:getNHSNumber-v1-0” -H “content-type: text/xml” –E pem_filename.pem -d @getNHSNumber.xml -k https://192.168.128.11/smsp/pds

Note: there are some variations in curl 7.43.0 on OS X, this is a working command line:

$ curl -X POST -H SOAPAction:urn:nhs-itk:services:201005:getNHSNumber-v1-0 -H content-type:text/xml -E p12_filename.p12:Password -d @getNHSNumber.xml -k https://192.168.54.6/smsp/pds

This will return:

The returned NHS number is 9473480032.

Step 4 – Transport connection

The ITK Spine Mini Service uses TLS MA (mutual authentication) to secure the connection between the client and central provider. When an endpoint is registered to the Path To Live Integration environment you will be provided with a PKCS#12 file containing the endpoint certificate, sub CA, and CA certs. This certificate is used to create the mutually authenticate connection with the service endpoint.