NRLS Record Locator Service

NRLS-DocumentReference-1-0

The 'NRLS-DocumentReference-1-0' resource profile is used in the NRLS registry interaction to store a reference to a locally held EPaCCs record on the NRLS. Once created the NRLS will identify the type and location of an EPaCCs record. The full detail of EPaCCs Record will therefore not be stored on the NRLS.

The NRLS-DocumentReference-1-0 examples contain URLs for FHIR profiles and for locations of other FHIR resources. These are not intended to be valid at this stage, nor are they an indication of what the URLs might be. The NRLS will need to host these FHIR profiles and resources, however these are just placeholder values for the purposes only of this POC.

NameCard.TypeDescription & Constraints
..DocumentReferenceDocumentReferenceNRLS Document

...masterIdentifier1..1IdentifierMaster Version Specific Identifier

....system0..1UriThe namespace for the identifier
Example Value: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri

....value1..1StringThe value that is unique
Example Value: b18f24b7-e72c-44c0-bdf4-7e45d06db1b6

...subject1..1PatientThe subject (patient) that this record is refering to, identified using NHS number. Example: https://pds.proxy.nhs.uk/Patient/9409401122

...type1..1CodeableConceptType of document (code/type)
Binding: Type of document. (http://fhir.nhs.net/ValueSet/correspondencedocumenttype-1-0)
Binding Strength: Required

....coding1..1CodingCode defined by a terminology system

.....system1..1UriIdentity of the terminology system
Fixed Value: http://snomed.info/sct

.....code1..1CodeSymbol in syntax defined by the system
Example Value: 861421000000109

.....display1..1StringRepresentation defined by the system
Example Value: End of Life Care Coordination Summary

...author1..1PractitionerPerson that authored record

...custodian1..1OrganizationOrganization which maintains the record

....reference1..1StringRelative URL reference
Example Value: https://sds.proxy.nhs.uk/Organization/A83627

....display0..1StringText alternative for the resource

...authenticator0..1PractitionerWho/what authenticated the document

...created1..1DateTimeDocument creation time

...indexed1..1InstantWhen this document reference created

...status1..1Codecurrent
Binding: The status of the document reference. (http://hl7.org/fhir/ValueSet/document-reference-status)
Binding Strength: Required
Fixed Value: current

...description0..1StringDescription of the source document.

...securityLabel1..1CodeableConceptDocument security-tags
Binding: Security Labels from the Healthcare Privacy and Security Classification System. (http://hl7.org/fhir/ValueSet/security-labels)
Binding Strength: Extensible

....coding1..1CodingCode defined by a terminology system

.....system1..1UriIdentity of the terminology system
Example Value: http://hl7.org/fhir/ValueSet/security-labels

.....code1..1CodeSymbol in syntax defined by the system
Example Value: V

.....display1..1StringRepresentation defined by the system
Example Value: very restricted

....text0..1StringPlain text representation of the concept

...content1..1BackboneElementDocument referenced

....attachment1..1AttachmentWhere to access the document

.....contentType1..1CodeMime type of the content, with charset etc.
Binding: The mime type of an attachment. Any valid mime type is allowed. (http://www.Rfc-Editor.org/bcp/bcp13.txt)
Binding Strength: Required
Example Value: application/pdf

.....url1..1UriUri where the data can be found
Example Value: https://gpsystem.nhs.uk/epcaccs/9409401122/EOLSummary.pdf

.....size1..1UnsignedIntNumber of bytes of content

.....title1..1StringLocally defined description of document/record
Example Value: EPaCCs Place chosen to die summary

...context1..1BackboneElementClinical context of document

....facilityType1..1CodeableConceptKind of facility where patient was seen
Binding: XDS Facility Type. (http://hl7.org/fhir/ValueSet/c80-facilitycodes)
Binding Strength: Example

.....coding1..1CodingCode defined by a terminology system

......system1..1UriIdentity of the terminology system
Example Value: http://hl7.org/fhir/ValueSet/c80-facilitycodes

......code1..1CodeSymbol in syntax defined by the system
Example Value: 83891005

......display1..1StringRepresentation defined by the system
Example Value: Solo practice private office

Path Name Binding Strength ValueSet
.DocumentReference.type type Required http://fhir.nhs.net/ValueSet/correspondencedocumenttype-1-0
.DocumentReference.status status Required http://hl7.org/fhir/ValueSet/document-reference-status
.DocumentReference.securityLabel securityLabel Extensible http://hl7.org/fhir/ValueSet/security-labels
.DocumentReference.content.attachment.contentType contentType Required http://www.Rfc-Editor.org/bcp/bcp13.txt
.DocumentReference.context.facilityType facilityType Example http://hl7.org/fhir/ValueSet/c80-facilitycodes

NRLS-DocumentReference-1-0

Examples Description XML File JSON File
NRLS-DocumentReference-del-1-0-Example1 Document reference example for an EPaCCs Diagnosis Report record
NRLS-DocumentReference-del-1-0-Example2 Document reference example for an EPaCCs Resuscitation Summary record
NRLS-DocumentReference-del-1-0-Example3 Document reference example for an EPaCCs Place of chosen Death Summary record