References
NHS Digital Profile: NRL-DocumentReference-1 |
HL7 FHIR STU3 Resource(s): DocumentReference |
User Stories: - |
Read
Consumer interaction to support the retrieval of a single NRL pointer. The read interaction is a FHIR RESTful read interaction.
Prerequisites
In addition to the requirements on this page, the general guidance and requirements detailed on the Development Overview page MUST be followed when using this interaction.
Read Request Headers
Consumer API read requests support the following HTTP request headers:
Header | Value | Conformance |
---|---|---|
Accept |
The Accept header indicates the format of the response the client is able to understand, if set, this must be either application/fhir+json or application/fhir+xml . |
OPTIONAL |
Authorization |
The Authorization header will carry the base64url encoded JSON web token required for audit on the spine - see the JSON Web Token Guidance page for details. |
REQUIRED |
fromASID |
Client System ASID. | REQUIRED |
toASID |
The Spine ASID. | REQUIRED |
Read Operation
The read interaction allows a consumer to retrieve a single pointer (DocumentReference) by logical ID.
The consumer must issue an HTTP GET as shown:
GET [baseUrl]/STU3/DocumentReference/[id]
GET [baseUrl]/STU3/DocumentReference/da2b6e8a-3c8f-11e8-baae-6c3be5a609f5-584d385036514c383142
Read the DocumentReference resource for a pointer with the logical id of 'da2b6e8a-3c8f-11e8-baae-6c3be5a609f5-584d385036514c383142'.
Note the status of the pointer must be current
for the pointer to be retrieved.
Read Response
Success
A successful execution of the read interaction will:
- return a
200
OK HTTP status code. - return a response body containing a
DocumentReference
resource which conforms to the NRL-DocumentReference-1 FHIR profile and has the statuscurrent
.
Example Successful Response:
Failure
The following errors can be triggered when performing this operation:
Explore the NRL
You can explore and test the read interaction using Swagger in the NRL API Reference Implementation.