References

Update

Provider interaction to support the update of NRL pointers. The update functionality will be used in cases where a Provider wishes to update a pointer status value, changing it from “current” to “entered-in-error”.

Pre-requisites

In addition to the requirements on this page the general guidance and requirements detailed on the Development Guidance page MUST be followed when using this interaction.

Update Request Headers

Provider API update requests support the following HTTP request headers:

Update Operation

Provider systems MUST construct a FHIRPath PATCH Parameters resource and submit this to NRL using the FHIR RESTful patch interaction.

PATCH [baseUrl]/DocumentReference/da2b6e8a-3c8f-11e8-baae-6c3be5a609f5-584d385036514c383142

Update the DocumentReference resource status for a pointer with the logical id of 'da2b6e8a-3c8f-11e8-baae-6c3be5a609f5-584d385036514c383142'.

The API supports the conditional update interaction which allows a provider to update a pointer using the masterIdentifier so they do not have to persist or query for the NRL generated logical id for the pointer. The query parameters should be used as shown:

PATCH [baseUrl]/DocumentReference?subject=https://demographics.spineservices.nhs.uk/STU3/Patient/9876543210&identifier=urn:ietf:rfc:3986%7Curn:oid:1.3.6.1.4.1.21367.2005.3.71

Update the DocumentReference resource status for a pointer with a subject and identifier.

[nhsNumber] - The NHS number of the patient whose DocumentReferences the client is requesting

[system] - The namespace of the masterIdentifier value that is associated with the DocumentReference(s)

[value] - The value of the masterIdentifier that is associated with the DocumentReference(s)

Providers systems MUST only update pointers for records where they are the pointer owner (custodian). For all update requests the custodian ODS code in the DocumentReference resource MUST be affiliated with the Client System ASID value in the fromASID HTTP request header sent to the NRL.

The FHIRPath PATCH operation must be encoded in a Parameters resource as follows:

• A single operation as a Parameter named “operation”
• The single parameter has a series of mandatory parts, with required values as listed in following table:

Only the first parameter within the Parameters resource will be used to perform a PATCH. Any additional parameters included within the request will not be processed. More details on the validation of the Parameters resource can be found in the error handling guidance.

XML and JSON eaxmples of the FHIRPath Parameters resource are shown below.

XML FHIRPath PATCH Parameters resource

<Parameters
    xmlns="http://hl7.org/fhir">
    <parameter>
        <name value="operation"/>
        <part>
            <name value="type"/>
            <valueCode value="replace"/>
        </part>
        <part>
            <name value="path"/>
            <valueString value="DocumentReference.status"/>
        </part>
        <part>
            <name value="value"/>
            <valueString value="entered-in-error"/>
        </part>
    </parameter>
</Parameters>

JSON FHIRPath PATCH Parameters resource

{
    "resourceType": "Parameters",
    "parameter": [
        {
            "name": "operation",
            "part": [
                {
                    "name": "type",
                    "valueCode": "replace"
                },
                {
                    "name": "path",
                    "valueString": "DocumentReference.status"
                },
                {
                    "name": "value",
                    "valueString": "entered-in-error"
                }
            ]
        }
    ]
}

Response

Success:

• MUST return a 200 SUCCESS HTTP status code on successful execution of the interaction and the entry has been successfully updated in the NRL.
• MUST return a response body containing a payload with an OperationOutcome resource that conforms to the ‘Operation Outcome’ core FHIR resource. See the following table.
• When a resource has been updated it will have a versionId of 2.

The table summarises the update interaction HTTP response code and the values expected to be conveyed in the successful response body OperationOutcome payload:

Failure:

The following errors can be triggered when performing this operation:

• Invalid Request Message
• Invalid Resource
• Invalid Parameter
• Resource Not Found
• Inactive Document Reference