Merge pull request #252 from NHSDigital/feature/chsnw6-NRL-2059-Replace-STU3-ContentStability-valueSet-with-R4-reference

[NRL-2059] Replace STU3 references with FHIR R4 equivalents

Author: CHSNW6

specification/record-locator/producer.yaml

@@ -310,7 +310,7 @@ info:
     ## Related APIs
 
     NRL is primarily concerned with the registering and retrieval of pointers. As per the [registry/repository pattern](https://digital.nhs.uk/developer/architecture/integration-patterns-book/patterns#registry-repository), following the retrieval of a pointer, the retrieval of an associated document/record may take place. In some circumstances information (or documents) are held in disparate systems. The registry-repository pattern resolves this by providing pointers with details that can be used to contact the organisation where the record is held, or directly retrieve the record from source, if authorised to do so. Most documents NRL pointers point to are retrievable using the Spine Secure Proxy [(SSP)](https://digital.nhs.uk/services/gp-connect/develop-gp-connect-services/integrate-with-spine/spine-secure-proxy). For example, all pointers of the category 'care plan' currently point to unstructured PDF documents, retrievable using SSP.
-    You can also refer to the [NRL Content Stability](https://fhir.nhs.uk/STU3/ValueSet/NRL-ContentStability-1) for information on the stability of the content of a target document or record linked by an NRL pointers.
+    You can also refer to the [NRL Content Stability](https://fhir.nhs.uk/England/CodeSystem/England-NRLContentStability) for information on the stability of the content of a target document or record linked by an NRL pointers.
     To connect to the Spine Secure Proxy (SSP), you will need:
     * An ASID for your organisation
     * A FQDN and CSR for your endpoint/application
@@ -334,7 +334,7 @@ info:
 
     **Note:** When creating pointers, providers MUST NOT prefix the pointer URL property with the SSP server URL, and MUST NOT percent encode it. In other words, consumers are fully responsible for constructing the Spine proxy URL from the pointer URL.
     Providers MUST NOT include any patient-identifiable data (PID), such as the NHS number, within the retrieval URL.
-    You can also populate the [NRL Content Stability](https://fhir.nhs.uk/STU3/ValueSet/NRL-ContentStability-1) section of a pointer/document reference with information on the stability of the content of a target document or record linked by an NRL pointers.
+    You can also populate the [NRL Content Stability](https://fhir.nhs.uk/England/CodeSystem/England-NRLContentStability) section of a pointer/document reference with information on the stability of the content of a target document or record linked by an NRL pointers.
 
     ##National Document Repository (NDR)
    
@@ -410,7 +410,7 @@ info:
     | HTTP Response Body | The body of the response message returned. |
     | HTTP Status Code | Describes the response outcome: 2xx (Success), 4xx or 5xx (Failure). |
     | HTTP Verb | POST, PATCH, GET, OR DELETE. |
-    | NHS number | The patient identifier used in the pointer subject reference (for example, https://demographics.spineservices.nhs.uk/STU3/Patient/[nhsNumber]) or in a search query parameter. |
+    | NHS number | The patient identifier used in the pointer subject reference (for example, https://fhir.nhs.uk/Id/nhs-number) or in a search query parameter. |
     | ODS Code | The requesting_organization from JWT (only the ODSCode portion is required, for example, https://fhir.nhs.uk/Id/ods-organization-code\|[odsCode]). |
     | Pointer Logical ID | The logical ID of the pointer (generated by the NRL), contained in the Location response header. |
     | Request Datetime | Timestamp when the audit log entry was created. |