diff --git a/MessageDefinition/BARS-MessageDefinition-Booking-Request.xml b/MessageDefinition/BARS-MessageDefinition-Booking-Request.xml index aa17779a..cd3313bc 100644 --- a/MessageDefinition/BARS-MessageDefinition-Booking-Request.xml +++ b/MessageDefinition/BARS-MessageDefinition-Booking-Request.xml @@ -6,7 +6,7 @@ <status value="active" /> - <date value="2023-10-16" /> + <date value="2025-03-24" /> <useContext> <!-- We are expecting the UseContext to be a DOS ID --> <code> @@ -15,7 +15,7 @@ </code> <valueCodeableConcept> <coding> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Referral.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Referral.xml index b46205e6..cf6bcd4b 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Referral.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Referral.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Request Referral" /> <title value="BARS Message Definition ServiceRequest - Request Referral" /> <status value="active" /> - <date value="2024-04-26" /> + <date value="2025-03-24" /> <useContext> <code> <system value="http://terminology.hl7.org/CodeSystem/usage-context-type" /> @@ -15,7 +15,7 @@ <valueCodeableConcept> <coding> <!-- We are expecting the UseContext to be a DOS ID --> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Validation.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Validation.xml index 88633dcd..c5d11253 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Validation.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Request-Validation.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Request Validation" /> <title value="BARS Message Definition ServiceRequest - Request Validation" /> <status value="active" /> - <date value="2024-02-26" /> + <date value="2025-03-24" /> <useContext> <!-- We are expecting the UseContext to be a DOS ID --> <code> @@ -15,7 +15,7 @@ </code> <valueCodeableConcept> <coding> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral-Short.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral-Short.xml index abbcb0bc..9e660ae8 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral-Short.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral-Short.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Response Referral Short" /> <title value="BARS Message Definition ServiceRequest - Response Referral Short" /> <status value="active" /> - <date value="2024-06-17" /> + <date value="2025-03-24" /> <useContext> <code> <system value="http://terminology.hl7.org/CodeSystem/usage-context-type" /> @@ -15,7 +15,7 @@ <valueCodeableConcept> <coding> <!-- We are expecting the UseContext to be a DOS ID --> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral.xml index 3160f2ce..585dbeb4 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Referral.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Response Referral" /> <title value="BARS Message Definition ServiceRequest - Response Referral" /> <status value="active" /> - <date value="2023-10-16" /> + <date value="2025-03-24" /> <useContext> <code> <system value="http://terminology.hl7.org/CodeSystem/usage-context-type" /> @@ -15,7 +15,7 @@ <valueCodeableConcept> <coding> <!-- We are expecting the UseContext to be a DOS ID --> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Full.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Full.xml index a485764b..f977f105 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Full.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Full.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Response Validation Full" /> <title value="BARS Message Definition ServiceRequest - Response Validation Full" /> <status value="active" /> - <date value="2023-10-16" /> + <date value="2025-03-24" /> <useContext> <code> <system value="http://terminology.hl7.org/CodeSystem/usage-context-type" /> @@ -15,7 +15,7 @@ <valueCodeableConcept> <coding> <!-- We are expecting the UseContext to be a DOS ID --> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Interim.xml b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Interim.xml index 9a2e2850..f5eb378c 100644 --- a/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Interim.xml +++ b/MessageDefinition/BARS-MessageDefinition-ServiceRequest-Response-Validation-Interim.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Response Validation Interim" /> <title value="BARS Message Definition ServiceRequest - Response Validation Interim" /> <status value="active" /> - <date value="2024-06-17" /> + <date value="2025-03-24" /> <useContext> <code> <system value="http://terminology.hl7.org/CodeSystem/usage-context-type" /> @@ -15,7 +15,7 @@ <valueCodeableConcept> <coding> <!-- We are expecting the UseContext to be a DOS ID --> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARSMessageDefinitionBookingRequestCancelled.xml b/MessageDefinition/BARSMessageDefinitionBookingRequestCancelled.xml index 28827e43..208a1285 100644 --- a/MessageDefinition/BARSMessageDefinitionBookingRequestCancelled.xml +++ b/MessageDefinition/BARSMessageDefinitionBookingRequestCancelled.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition Booking - Request - Cancelled" /> <title value="BARS Message Definition Booking - Request - Cancelled" /> <status value="active" /> - <date value="2024-06-17" /> + <date value="2025-03-24" /> <useContext> <!-- We are expecting the UseContext to be a DOS ID --> <code> @@ -15,7 +15,7 @@ </code> <valueCodeableConcept> <coding> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/MessageDefinition/BARSMessageDefinitionServiceRequestRequestCancelled.xml b/MessageDefinition/BARSMessageDefinitionServiceRequestRequestCancelled.xml index e8ff6d2c..d3e2543f 100644 --- a/MessageDefinition/BARSMessageDefinitionServiceRequestRequestCancelled.xml +++ b/MessageDefinition/BARSMessageDefinitionServiceRequestRequestCancelled.xml @@ -6,7 +6,7 @@ <name value="BARS Message Definition ServiceRequest - Request - Cancelled" /> <title value="BARS Message Definition ServiceRequest - Request - Cancelled" /> <status value="active" /> - <date value="2024-06-17" /> + <date value="2025-03-24" /> <useContext> <!-- We are expecting the UseContext to be a DOS ID --> <code> @@ -15,7 +15,7 @@ </code> <valueCodeableConcept> <coding> - <system value="https://fhir.nhs.uk/CodeSystem/dos-id" /> + <system value="https://fhir.nhs.uk/Id/dos-service-id" /> <code value="dos-id" /> </coding> </valueCodeableConcept> diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md index 5a406e9e..fd71dcda 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Current-Releases.page.md @@ -3,9 +3,9 @@ Product Link | Version | Handle | Phase | State | Release Date | Stability | Change Log Link -----------------------|---------|---------|----------|-----------------|--------------|------------|----------------- Implementation Guide | 1.8.2 | v1 | Live | Current Release | 26/11/2024 | Stable |{{pagelink:trn-General}} -[FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.35.0) | uk.nhsdigital.bars.r4 1.35.0| v1 | Live | Current Release | 29/08/2024 | Stable | +[FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.35.0) | 1.35.0| v1 | Live | Current Release | 29/08/2024 | Stable | {{pagelink:design-core-1.1.6, text:BaRS Core}} | 1.1.6 | v1 | Live | Current Release | 26/11/2024 | Stable |{{pagelink:trn-core, text: BaRS Core Change Log}} -[API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0) | 1.1.6 | v1 | Live | Current Release | 01/04/2023 | Stable |{{pagelink:trn-api}} +[API Specification](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0) | 1.1.0 | v1 | Live | Current Release | 01/04/2023 | Stable |{{pagelink:trn-api}} {{pagelink: build-testing, text: TKW}} | 1.0.18 | v1 | Live | Current Release | 27/11/2024 | Stable |{{pagelink:trn-tkw}} {{pagelink:application1, text:BaRS-APP1}} | 1.0.7 | v1 | Live | Current Release | 26/11/2024 | Stable |{{pagelink:trn-app1,text:BaRS APP1 Change Log}} {{pagelink:application2, text:BaRS-APP2}} | 1.0.7 | v1 | Live | Current Release | 26/11/2024 | Stable |{{pagelink:trn-app2,text:BaRS APP2 Change Log}} diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md index be6a1a1e..aaa83c77 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/API-Spec-Change-Log/Global.page.md @@ -8,6 +8,8 @@ topic: TRN-API-global | Change | BaRS Version | Description | Impact | |------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Removal of use-context HTTP header | 1.8.2 |Restricted the use of the use-context header to non-write operations | <mark style="background-color: Yellow">correction</mark> | +| Improvments to header documentation | 1.8.2 |Added better explinations around most of the headers needed | <mark style="background-color: Green">Addition</mark> | | Addition of the use-context HTTP header | 1.8.1 | A new header to assist in {{pagelink:core-EndToEndWorkflow-Logging-1.0.5, text: audting and logging}} | <mark style="background-color: Green">Addition</mark> | | <div class="imgHandshake">{{render:handshake}}</div> - The DoS ID examples updated to https| 1.8.0 | The https://fhir.nhs.uk/Id/dos-service-id examples now correcly show as https. | <mark style="background-color: Yellow">correction</mark> | | <div class="imgHandshake">{{render:handshake}}</div> | 1.8.0 | The example deviceName element in NHSD-Requesting-Software now shows correctly as an Object as defined by the schema | <mark style="background-color: Yellow">correction</mark> | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.0.5.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.0.5.page.md index 0e399079..d42ff843 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.0.5.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.0.5.page.md @@ -20,6 +20,4 @@ topic: TRN-Core-1.0.5 </div> </div> <br> -<hr> - -### Previous Releases \ No newline at end of file +<hr> \ No newline at end of file diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml index 0acf544b..b5da70f7 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml @@ -2,32 +2,30 @@ filename: Index.page.md - name: 1.2.2-alpha filename: 1.2.2-alpha.page.md -- name: 1.2.1-alpha - filename: 1.2.1-alpha.page.md - name: 1.1.6 filename: 1.1.6.page.md -- name: 1.1.5 - filename: 1.1.5.page.md - name: 1.0.6 filename: 1.0.6.page.md -- name: 1.0.5 - filename: 1.0.5.page.md -- name: 1.1.4 - filename: 1.1.4.page.md -- name: 1.0.4 - filename: 1.0.4.page.md +- name: 1.2.1-alpha + filename: 1.2.1-alpha.page.md - name: 1.2.0-alpha filename: 1.2.0-alpha.page.md +- name: 1.1.5 + filename: 1.1.5.page.md +- name: 1.1.4 + filename: 1.1.4.page.md - name: 1.1.3 filename: 1.1.3.page.md -- name: 1.0.3 - filename: 1.0.3.page.md - name: 1.1.2 filename: 1.1.2.page.md - name: 1.1.1 filename: 1.1.1.page.md - name: 1.1.0 filename: 1.1.0.page.md +- name: 1.0.5 + filename: 1.0.5.page.md +- name: 1.0.4 + filename: 1.0.4.page.md - name: 1.0.3 filename: 1.0.3.page.md - name: 1.0.0 diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.12.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.12.page.md index 8737d5b8..f114d51e 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.12.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.12.page.md @@ -1,3 +1,6 @@ +<div class="bars-blg-expander"> +<div class="bars-blg-expander-entry" id="v1.0.11"> + ## {{page-title}} ### General fixes @@ -15,11 +18,12 @@ |Story |NBRS-3739 |App6 - Portal Configuration| |Story |NBRS-3740 |Update FHIR package| - +</div> +</div> <br> <hr> -### Previous Releases + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.18.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.18.page.md new file mode 100644 index 00000000..1ecd0852 --- /dev/null +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.18.page.md @@ -0,0 +1,47 @@ +## {{page-title}} + +### Workflow and payload developments +Support for Application5 TKW Receiver and Use-Case Category (UCC) functionality + + +| Issue Type | Issue key | Summary | +|------------|-----------|------------------------------------------------------------------------------| +|Story |NBRS-3962 |TKW Receiver - App5 Happy Path Request| +|Story |NBRS-3740 |Update FHIR package | +|Story |NBRS-3963 |TKW Receiver - App5 MessageDefinition response | +|Story |NBRS-3800 |TKW Receiver - include UCC in synchronous and async responses (bookings and referrals)| +|Story |NBRS-3802 |TKW Receiver - Validation Report to check for UCC existence (bookings and referrals)| +|Story |NBRS-3801 |TKW Sender - validate UCC and ServiceId in Message Definition responses - Validation Report| +|Story |NBRS-3799 |TKW Sender - include UCC in requests (booking and referral)| +|Story |NBRS-3807 |TKW Receiver - Support for new HTTP Header - use-context| +|Story |NBRS-3806 |TKW Sender - Support for new HTTP Header - use-context| +|Story |NBRS-3803 |TKW Sender - new Error tests - omitting UCC| +|Story |NBRS-3804 |TKW Sender - include UCC in GET /MessageDefinition request - New Test| +|Story |NBRS-3798 |TKW Receiver - include UCC in TKW Message Def responses| + + +### General fixes + +| Issue Type | Issue key | Summary | +|------------|-----------|------------------------------------------------------------------------------| +|Bug |NBRS-3596 |Cancel Happy Path - incorrect structure definition in cancel request | +|Bug |NBRS-3999 |TKW Sender - MessageDef validation of Service Id format| +|Bug |NBRS-4000 |TKW Sender - App5 - Add Message Definition validation for new checks| +|Bug |NBRS-3998 |TKW Receiver - Cancellation new trigger (not sentinel value)| +|Bug |NBRS-3970 |Booking Request Payload - Appointment.slot.reference must be an absolute reference| +|Bug |NBRS-3965 |TKW Receiver - MessageDefs - encoding values in responses| +|Bug |NBRS-3966 |TKW Receiver - include full path for supportedMessages in Capability Statement response| +|Bug |NBRS-3964 |TKW Receiver - Remove need for double 'context' parameter in MessageDefinition GET| + + +<br> +<hr> + +### Previous Releases + + + + + + + diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml index 03314548..15ea671e 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/toc.yaml @@ -1,5 +1,7 @@ - name: Index filename: Index.page.md +- name: 1.0.18 + filename: 1.0.18.page.md - name: 1.0.12 filename: 1.0.12.page.md - name: 1.0.11 diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Payloads-for-Requestors.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Payloads-for-Requestors.page.md index 8c3c8228..d3ae76f8 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Payloads-for-Requestors.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/BaRS-APP4/Payloads-for-Requestors.page.md @@ -10,7 +10,7 @@ The below details the specific guidance around the use of resources required to _Note that Requesters will also have to build the capability to receive and process the Validation Response payloads._ For Example Validation Request bundles see: -* [Validation Request - 999 to CAS New](https://simplifier.net/nhsbookingandreferrals/86e3371d-1c15-4862-9552-d9560f8292db) +* [Validation Request - 999 to CAS New](https://simplifier.net/nhsbookingandreferrals/86e3371d-1c15-4862-9552-d9560f8292ba-duplicate-8) * [Validation Request - 999 to CAS AMPDS](https://simplifier.net/nhsbookingandreferrals/86e3371d-1c15-4862-9552-d9560f8292ba) * [Validation Request - 999 to CAS Update to lower priority](https://simplifier.net/nhsbookingandreferrals/baebe535-9d6c-4b0f-8bc6-8f4b157d44ac) * For additional example bundles please check [BaRS Example Bundles](https://simplifier.net/nhsbookingandreferrals/~resources?category=Example&exampletype=Bundle&sortBy=LastUpdateDate_desc) diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md index 1683f389..15195b55 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Applications/Applications/Index.page.md @@ -43,10 +43,10 @@ Table detailing active versions of the latest Applications in Production (or cur </thead> <tbody> <tr> - <td>Application 1 v1.0.1</td> + <td>Application 1 v1.0.1</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.1.0" target="_blank">v1.1.0</a></td> - <td rowspan=10 style="text-align: center; vertical-align: middle;"><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Design/BaRS-Core?version=1.0.0" target="_blank">v1.0.0</a></td> - <td rowspan=10 style="text-align: center; vertical-align: middle;"><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_0_0" target="_blank">1.0.0</a></td> + <td rowspan=14 style="text-align: center; vertical-align: middle;"><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Design/BaRS-Core?version=1.0.0" target="_blank">v1.0.0</a></td> + <td rowspan=14 style="text-align: center; vertical-align: middle;"><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_0_0" target="_blank">1.0.0</a></td> </tr> <tr> <td>Application 1 v1.0.3</td> @@ -56,6 +56,14 @@ Table detailing active versions of the latest Applications in Production (or cur <td>Application 1 v1.0.5</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.0</a></td> </tr> + <tr> + <td>Application 1 v1.0.6</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.1" target="_blank">v1.8.1</a></td> + </tr> + <tr> + <td>Application 1 v1.0.7</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> <tr> <td>Application 2 v1.0.1</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.1.0" target="_blank">v1.1.0</a></td> @@ -68,6 +76,14 @@ Table detailing active versions of the latest Applications in Production (or cur <td>Application 2 v1.0.5</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.0</a></td> </tr> + <tr> + <td>Application 2 v1.0.6</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.1" target="_blank">v1.8.1</a></td> + </tr> + <tr> + <td>Application 2 v1.0.7</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> <tr> <td>Application 3 v1.0.0</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.4.0" target="_blank">v1.4.0</a></td> @@ -76,6 +92,14 @@ Table detailing active versions of the latest Applications in Production (or cur <td>Application 3 v1.0.1</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.6.0" target="_blank">v1.6.0</a></td> </tr> + <tr> + <td>Application 3 v1.0.2</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.6.0" target="_blank">v1.8.1</a></td> + </tr> + <tr> + <td>Application 3 v1.0.3</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> <tr> <td>Application 4 v1.0.0</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.4.0" target="_blank">v1.4.0</a></td> @@ -84,11 +108,19 @@ Table detailing active versions of the latest Applications in Production (or cur <td>Application 4 v1.2.0</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.0</a></td> </tr> + <tr> + <td>Application 4 v1.2.1</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.1</a></td> + </tr> + <tr> + <td>Application 4 v1.2.2</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> <tr> <td>Application 5 v1.0.0-beta.4</td> <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.4.0" target="_blank">v1.4.0</a></td> - <td rowspan=4 style="text-align: center; vertical-align: middle;"><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Core/End-to-end-workflow?version=1.4.0" target="_blank">v1.1.0</a></td> - <td rowspan=4 style="text-align: center; vertical-align: middle;"><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0" target="_blank">1.1.0</a></td> + <td rowspan=5 style="text-align: center; vertical-align: middle;"><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Core/End-to-end-workflow?version=1.4.0" target="_blank">v1.1.0</a></td> + <td rowspan=5 style="text-align: center; vertical-align: middle;"><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0" target="_blank">1.1.0</a></td> </tr> <tr> <td>Application 5 v1.0.0</td> @@ -99,8 +131,22 @@ Table detailing active versions of the latest Applications in Production (or cur <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.0</a></td> </tr> <tr> - <td>Application 6 v1.0.0-beta.2</td> - <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.0</a></td> + <td>Application 5 v1.1.1</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.0" target="_blank">v1.8.1</a></td> + </tr> + <tr> + <td>Application 5 v1.1.2</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> + <tr> + <td>Application 6 v1.0.0-beta.4</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + </tr> + <tr> + <td>Application 7 v1.0.0-alpha.3</td> + <td><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/home?version=1.8.2" target="_blank">v1.8.2</a></td> + <td rowspan=1 style="text-align: center; vertical-align: middle;"><a href="https://simplifier.net/guide/nhsbookingandreferralstandard/Home/Design/BaRS-Core?version=1.0.0" target="_blank">v1.0.0</a></td> + <td rowspan=1 style="text-align: center; vertical-align: middle;"><a href="https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_0_0" target="_blank">1.0.0</a></td> </tr> <tr> <td>Application 7 v1.0.0-alpha</td> diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md index abbc1d6c..f12a8624 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.0.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md @@ -20,7 +20,8 @@ The use case category is used in the initial content negotiation phase: When a Sender makes a request for MessageDefinitions, the MessageDefinitions returned by the Receiver will contain a use case category code (from the use case categories code system) under Message.Definition.useContext.code. The Sender **must** read this field to verify the Receiver supports the use case workflow they require. The use case category code will also be included in: * the Sender's service request under ServiceRequest.category * the Sender’s booking request under Appointment.ServiceCategory - If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). + +If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). The sequence of events occurs as follows: * the Sender requests the MessageDefinitions diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md index bf5a53cb..939affc5 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md @@ -20,7 +20,8 @@ The use case category is used in the initial content negotiation phase: When a Sender makes a request for MessageDefinitions, the MessageDefinitions returned by the Receiver will contain a use case category code (from the use case categories code system) under Message.Definition.useContext.code. The Sender **must** read this field to verify the Receiver supports the use case workflow they require. The use case category code will also be included in: * the Sender's service request under ServiceRequest.category * the Sender’s booking request under Appointment.ServiceCategory - If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). + +If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). The sequence of events occurs as follows: * the Sender requests the MessageDefinitions diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md index 07ab4a60..428580cc 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Standard-Pattern-Composite-Messages/Use-Case-Categories.page.md @@ -20,7 +20,8 @@ The use case category is used in the initial content negotiation phase: When a Sender makes a request for MessageDefinitions, the MessageDefinitions returned by the Receiver will contain a use case category code (from the use case categories code system) under Message.Definition.useContext.code. The Sender **must** read this field to verify the Receiver supports the use case workflow they require. The use case category code will also be included in: * the Sender's service request under ServiceRequest.category * the Sender’s booking request under Appointment.ServiceCategory - If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). + +If this is not a use case supported by the Receiver, they will respond with an error (Operation Outcome). The sequence of events occurs as follows: * the Sender requests the MessageDefinitions