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 8b3cfb1c..ca675ca6 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 @@ -6,13 +6,13 @@ Implementation Guide | 1.8.2 | v1 | Live | Current Release | 01/04/ [FHIR Package](https://simplifier.net/packages/uk.nhsdigital.bars.r4/1.35.0) | 1.35.0| v1 | Live | Current Release | 01/04/2025 | Stable | {{pagelink:design-core-1.1.6, text:BaRS Core}} | 1.1.6 | v1 | Live | Current Release | 01/04/2025 | 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.0 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-api}} -{{pagelink: build-testing, text: TKW}} | 1.0.18 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-tkw}} +{{pagelink: build-testing, text: TKW}} | 1.0.19 | v1 | Live | Current Release | 28/03/2025 | Stable |{{pagelink:trn-tkw}} {{pagelink:application1, text:BaRS-APP1}} | 1.0.7 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-app1,text:BaRS APP1 Change Log}} {{pagelink:application2, text:BaRS-APP2}} | 1.0.7 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-app2,text:BaRS APP2 Change Log}} {{pagelink:application3, text:BaRS-APP3}} | 1.0.3 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-app3,text:BaRS APP3 Change Log}} {{pagelink:application4, text:BaRS-APP4}} | 1.2.2 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-app4,text:BaRS APP4 Change Log}} {{pagelink:application5, text:BaRS-APP5}} | 1.1.2 | v1 | Live | Current Release | 01/04/2025 | Stable |{{pagelink:trn-app5,text:BaRS APP5 Change Log}} -{{pagelink:application6, text:BaRS-APP6}} | 1.0.0-beta.4 | beta | Live | Current Release | 01/04/2025 | Pre-Release |{{pagelink:trn-app6,text:BaRS APP6 Change Log}} +{{pagelink:application6, text:BaRS-APP6}} | 1.0.0-beta.4 | beta | | Current Release | 01/04/2025 | Pre-Release |{{pagelink:trn-app6,text:BaRS APP6 Change Log}} {{pagelink:application7, text:BaRS-APP7}} | 1.0.0-alpha.3 | alpha | | Current Release | 01/04/2025 | Pre-Release |{{pagelink:trn-app7,text:BaRS APP7 Change Log}} 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.19.page.md similarity index 96% rename from guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.18.page.md rename to guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TKW-Change-Log/1.0.19.page.md index 1ecd0852..ecf22cd8 100644 --- 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.19.page.md @@ -32,6 +32,7 @@ Support for Application5 TKW Receiver and Use-Case Category (UCC) functionality |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| +|Bug |NBRS-3876 |Slot.id from GET /Slot not being included in booking request bundle|
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 15ea671e..7537651f 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,7 +1,7 @@ - name: Index filename: Index.page.md -- name: 1.0.18 - filename: 1.0.18.page.md +- name: 1.0.19 + filename: 1.0.19.page.md - name: 1.0.12 filename: 1.0.12.page.md - name: 1.0.11 diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/1.0.7.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/1.0.7.page.md index faa11177..2b75feeb 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/1.0.7.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP1/1.0.7.page.md @@ -9,8 +9,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| -| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | addition | -|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | addition | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | @@ -19,7 +19,7 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | +| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/1.0.7.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/1.0.7.page.md index faa11177..2b75feeb 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/1.0.7.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP2/1.0.7.page.md @@ -9,8 +9,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| -| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | addition | -|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | addition | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | @@ -19,7 +19,7 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | +| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/1.0.3.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/1.0.3.page.md index 7285cab3..4fce4dae 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/1.0.3.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP3/1.0.3.page.md @@ -9,8 +9,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| -| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | addition | -|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | addition | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | @@ -19,7 +19,7 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | +| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/1.2.2.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/1.2.2.page.md index 11f0b46c..b9723647 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/1.2.2.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP4/1.2.2.page.md @@ -9,8 +9,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| -| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | addition | -|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | addition | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | @@ -19,9 +19,9 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| encounter.class.display | | | Update | Validation Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | -| encounter.class.display | | | Update | Interim Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | -| encounter.class.display | | | Update | Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | +| encounter.class.display | | | Update | Validation Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | +| encounter.class.display | | | Update | Interim Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | +| encounter.class.display | | | Update | Validation Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.2.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.2.page.md index d33649e7..b3a03ee2 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.2.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP5/1.1.2.page.md @@ -14,6 +14,8 @@ This stable release (v1.1.2) of Application 5 sees minor corrections. | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| | SNOMED Code Updated | The SNOMED Code used to define a minor illness referral has been updated from '1577041000000100-Community Pharmacist Consultation Service for minor illness (procedure)' to '2140231000000104-Referral to Community Pharmacy Pharmacy First Service (procedure)', as requested by Pharmacy First Programme Clinical Lead | correction | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | ### Payload Change Log @@ -22,6 +24,7 @@ This stable release (v1.1.2) of Application 5 sees minor corrections. |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| | Task.code.coding.code | 1577041000000100 | 2140231000000104 | Update | Referral Request |SNOMED Code changed | non-breaking | | Task.code.coding.display | Community Pharmacist Consultation Service for minor illness (procedure) | Referral to Community Pharmacy Pharmacy First Service (procedure) | Update | Referral Request |SNOMED Code changed | non-breaking | +| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.4.page.md b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.4.page.md index bbe7b306..0ce94c21 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.4.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/TRN-APP6/1.0.0-beta.4.page.md @@ -9,8 +9,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | Change | Description | Impact | |-------------------------------------------|-------------------------------------------------|-------------------------------------------------------------------------| -| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | addition | -|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | addition | +| Implementation Guidance updated | encounter.class.display value corrected from "Emergency" to "emergency" | correction | +|NHSD-Requesting-Practioner Examples updated | FHIRPractioner corrected to FHIRPractionerRole | correction | @@ -19,8 +19,8 @@ This is a minor "patch" with clarifications to limited areas of the Implementati | FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact | |------------------------------------------------------|----------|------------|---------|------------------|-------------------------------------------------------------------------------------------------|----------| -| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | -| encounter.class.display | | | Update | Referral Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | Addition | +| encounter.class.display | | | Update | Referral Request |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction | +| encounter.class.display | | | Update | Referral Response |encounter.class.display value corrected from "Emergency" to "emergency" in Implementation Guidance | correction |
diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md index 63987f61..794eebc6 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Applications/BaRS-Pre-releases/Index.page.md @@ -40,10 +40,10 @@ Table detailing active versions of the latest Applications in Production (or cur - Application 1 v1.0.1 + Application 1 v1.0.1 v1.1.0 - v1.0.0 - 1.0.0 + v1.0.0 + 1.0.0 Application 1 v1.0.3 @@ -53,6 +53,14 @@ Table detailing active versions of the latest Applications in Production (or cur Application 1 v1.0.5 v1.8.0 + + Application 1 v1.0.6 + v1.8.1 + + + Application 1 v1.0.7 + v1.8.2 + Application 2 v1.0.1 v1.1.0 @@ -65,6 +73,14 @@ Table detailing active versions of the latest Applications in Production (or cur Application 2 v1.0.5 v1.8.0 + + Application 2 v1.0.6 + v1.8.1 + + + Application 2 v1.0.7 + v1.8.2 + Application 3 v1.0.0 v1.4.0 @@ -73,6 +89,14 @@ Table detailing active versions of the latest Applications in Production (or cur Application 3 v1.0.1 v1.6.0 + + Application 3 v1.0.2 + v1.8.1 + + + Application 3 v1.0.3 + v1.8.2 + Application 4 v1.0.0 v1.4.0 @@ -81,11 +105,19 @@ Table detailing active versions of the latest Applications in Production (or cur Application 4 v1.2.0 v1.8.0 + + Application 4 v1.2.1 + v1.8.1 + + + Application 4 v1.2.2 + v1.8.2 + Application 5 v1.0.0-beta.4 v1.4.0 - v1.1.0 - 1.1.0 + v1.1.0 + 1.1.0 Application 5 v1.0.0 @@ -96,12 +128,20 @@ Table detailing active versions of the latest Applications in Production (or cur v1.8.0 - Application 6 v1.0.0-beta.2 - v1.8.0 + Application 5 v1.1.1 + v1.8.1 - Application 7 v1.0.0-alpha - v1.8.0 + Application 5 v1.1.2 + v1.8.2 + + + Application 6 v1.0.0-beta.4 + v1.8.2 + + + Application 7 v1.0.0-alpha.3 + v1.8.2 v1.0.0 1.0.0 diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Cancel-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Cancel-Booking.page.md index 4f6da157..b08aa800 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Cancel-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Cancel-Booking.page.md @@ -6,9 +6,9 @@ topic: core-StandardPattern-appointment-cancel-1.1.6 To cancel an appointment: -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} resource returned: ```json diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Initial-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Initial-Booking.page.md index 006b4312..245c400d 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Initial-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Initial-Booking.page.md @@ -6,16 +6,16 @@ topic: core-StandardPattern-appointment-booking-1.1.6 Below are examples of each of the described interactions. The appointment resource adheres to the [UKCore-Appointment](https://simplifier.net/HL7FHIRUKCoreR4/UKCore-Appointment) definition. -Any operations that modify an existing resource must perform a read before a write. GET /Appointment/{id} +Any operations that modify an existing resource must perform a read before a write. GET /Appointment/\{id\} ### Book -The method for the initial booking of an appointment depends on the {{pagelink:Home/Applications/BaRS-Applications, text:Application}} specific guidance within BaRS. Alternatively, booking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment workflow, either way, the typical sequence of events is: +The method for the initial booking of an appointment depends on the {{pagelink:Home/Applications/BaRS-Applications, text:Application}} specific guidance within BaRS. Within BaRS Applications, making a booking will involve building a FHIR bundle and making a POST to the [$process-message](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/$process-message) endpoint. Alternatively, booking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment Management Foundation workflow against the discete [booking endpoints](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment), either way, the typical sequence of events is: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.1.6, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot). * Select a slot. -* Send a Request to book an appointment in that slot +* Send a Request to [book an appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment) in that slot diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Introduction.page.md index 3a9a5ac7..87abf1ef 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Introduction.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Introduction.page.md @@ -29,17 +29,17 @@ There are four functions that are required surrounding appointments. This sectio ## Interface -The following table describes how the BaRS API accomodates these four capabilities using the [/Appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment) endpoint and the [/Appointment/{id}](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) endpoint +The following table describes how the BaRS API accomodates these four capabilities using the [/Appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment) endpoint and the [/Appointment/\{id\}](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) endpoint | Capability | Endpoint | VERB | Description | |------------|-----------|-----|--------------| -| List | /DocumentReference | GET | Using the {{pagelink:core-StandardPattern-document-reference-Introduction-1.1.6, text:DocumentReference}} pattern, a list of existing appointments for a patient can be viewed with the central Registry. | -| View | /Appointment/{id} | GET | This action, using the id from the List capability, will allow that specific Appointment Resource to be [retrieved](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment) from the healthcare service who owns it. | -| Get Slots | /Slots | GET | Obtain a list of available booking slots from a specified receiving system using the [GET /Slots endpoint](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot) | -| Book | /Appointment or /$process-message | POST | This will be a POST operation, with a BaRS Application /$process-message is typically used, outside of supported use cases /Appointment is adopted.| -| [Cancel](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) | /Appointment/{id} | PUT| The cancel of a booking will be setting the status of the appointment to "cancelled". Cancel is also possible using /$process-message | -| [Update](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) | /Appointment/{id} | PUT / PATCH| An update to an appointment will be a direct update to the existing resource | -| Rebook | Composite of Cancel and then Book | Composite | Requesting a new booking and then cancelling the existing one will constitute a rebook | +| [List](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/DocumentReference) | /DocumentReference | GET | Using the {{pagelink:core-StandardPattern-document-reference-Introduction-1.1.6, text:DocumentReference}} pattern, a list of existing appointments for a patient can be viewed with the central Registry. | +| [View](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) | /Appointment/\{id\} | GET | This action, using the id from the List capability, will allow that specific Appointment Resource to be [retrieved](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) from the healthcare service who owns it. | +| [Get Slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot) | /Slots | GET | Obtain a list of available booking slots from a specified receiving system using the [GET /Slots endpoint](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot) | +| [Book](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment) | /Appointment or /$process-message | POST | This will be a POST operation, with a BaRS Application /$process-message is typically used, outside of supported use cases /Appointment is adopted.| +| [Cancel](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) | /Appointment/\{id\} | PUT| The cancel of a booking will be setting the status of the appointment to "cancelled". Cancel is also possible using /$process-message | +| [Update](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) | /Appointment/\{id\} | PUT / PATCH| An update to an appointment will be a direct update to the existing resource | +| [Rebook](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#post-/Appointment) | Composite of Cancel and then Book | Composite | Requesting a new booking and then cancelling the existing one will constitute a rebook | In line with the BaRS standard all operations used to modify a resource must be preceded by a read of the resource by means of a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Rebook-Methods.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Rebook-Methods.page.md index 5cc7ff28..a37078a3 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Rebook-Methods.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Rebook-Methods.page.md @@ -30,13 +30,13 @@ Use the cancel method described above. The method for the subsequent booking of an appointment depends on the Application specific guidance within BaRS. The only difference would be the Appointment Resource would include Appointment.replaces referencing the previous appointment for provenance. Alternatively, rebooking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment workflow, either way, the typical sequence of events using PUT or POST is: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.1.6, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot). * Select a slot. -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} Request Body @@ -78,13 +78,13 @@ Request Body Using PATCH: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.1.6, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Slot). * Select a slot. -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PATCH operation using the id of the appointment to /Appointment/{id} +* Perform a [PATCH](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#patch-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} ```json { diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Update-Existing-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Update-Existing-Booking.page.md index b2e5131f..af9f0eca 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Update-Existing-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.1.6/Appointment-StandardPattern/Update-Existing-Booking.page.md @@ -6,9 +6,9 @@ topic: core-StandardPattern-appointment-update-1.1.6 To update an appointment: -* Perform a GET operation using the id of the appointment to /Appointment/{id} -* Ammend or append the resource as required. -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} +* Amend or append the resource as required. +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_1_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} In this example a placeholder was created, and updated when the slot is selected. This is a hypothetical scenario. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Cancel-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Cancel-Booking.page.md index 75c3316a..507d1bcd 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Cancel-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Cancel-Booking.page.md @@ -6,9 +6,9 @@ topic: core-StandardPattern-appointment-cancel-1.2.2 To cancel an appointment: -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} resource returned: ```json diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Initial-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Initial-Booking.page.md index 1f316cfd..adf3390b 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Initial-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Initial-Booking.page.md @@ -6,16 +6,16 @@ topic: core-StandardPattern-appointment-booking-1.2.2 Below are examples of each of the described interactions. The appointment resource adheres to the [UKCore-Appointment](https://simplifier.net/HL7FHIRUKCoreR4/UKCore-Appointment) definition. -Any operations that modify an existing resource must perform a read before a write. GET /Appointment/{id} +Any operations that modify an existing resource must perform a read before a write. GET /Appointment/\{id\} ### Book -The method for the initial booking of an appointment depends on the {{pagelink:Home/Applications/BaRS-Applications, text:Application}} specific guidance within BaRS. Alternatively, booking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment workflow, either way, the typical sequence of events is: +The method for the initial booking of an appointment depends on the {{pagelink:Home/Applications/BaRS-Applications, text:Application}} specific guidance within BaRS. Within BaRS Applications, making a booking will involve building a FHIR bundle and making a POST to the [$process-message](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/$process-message) endpoint. Alternatively, booking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment Management Foundation workflow against the discete [booking endpoints](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment), either way, the typical sequence of events is: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.2.2, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot). * Select a slot. -* Send a Request to book an appointment in that slot +* Send a Request to [book an appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment) in that slot diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Introduction.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Introduction.page.md index 60691a6b..2151eafc 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Introduction.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Introduction.page.md @@ -29,17 +29,17 @@ There are four functions that are required surrounding appointments. This sectio ## Interface -The following table describes how the BaRS API accomodates these four capabilities using the [/Appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment) endpoint and the [/Appointment/{id}](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) endpoint +The following table describes how the BaRS API accomodates these four capabilities using the [/Appointment](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment) endpoint and the [/Appointment/\{id\}](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) endpoint | Capability | Endpoint | VERB | Description | |------------|-----------|-----|--------------| -| List | /DocumentReference | GET | Using the {{pagelink:core-StandardPattern-document-reference-Introduction-1.1.6, text:DocumentReference}} pattern, a list of existing appointments for a patient can be viewed with the central Registry. | -| View | /Appointment/{id} | GET | This action, using the id from the List capability, will allow that specific Appointment Resource to be [retrieved](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment) from the healthcare service who owns it. | -| Get Slots | /Slots | GET | Obtain a list of available booking slots from a specified receiving system using the [GET /Slots endpoint](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot) | -| Book | /Appointment or /$process-message | POST | This will be a POST operation, with a BaRS Application /$process-message is typically used, outside of supported use cases /Appointment is adopted.| -| [Cancel](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) | /Appointment/{id} | PUT| The cancel of a booking will be setting the status of the appointment to "cancelled". Cancel is also possible using /$process-message | -| [Update](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) | /Appointment/{id} | PUT / PATCH| An update to an appointment will be a direct update to the existing resource | -| Rebook | Composite of Cancel and then Book | Composite | Requesting a new booking and then cancelling the existing one will constitute a rebook | +| [List](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/DocumentReference) | /DocumentReference | GET | Using the {{pagelink:core-StandardPattern-document-reference-Introduction-1.2.2, text:DocumentReference}} pattern, a list of existing appointments for a patient can be viewed with the central Registry. | +| [View](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) | /Appointment/\{id\} | GET | This action, using the id from the List capability, will allow that specific Appointment Resource to be [retrieved](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) from the healthcare service who owns it. | +| [Get Slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot) | /Slots | GET | Obtain a list of available booking slots from a specified receiving system using the [GET /Slots endpoint](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot) | +| [Book](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment) | /Appointment or /$process-message | POST | This will be a POST operation, with a BaRS Application /$process-message is typically used, outside of supported use cases /Appointment is adopted.| +| [Cancel](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) | /Appointment/\{id\} | PUT| The cancel of a booking will be setting the status of the appointment to "cancelled". Cancel is also possible using /$process-message | +| [Update](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) | /Appointment/\{id\} | PUT / PATCH| An update to an appointment will be a direct update to the existing resource | +| [Rebook](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#post-/Appointment) | Composite of Cancel and then Book | Composite | Requesting a new booking and then cancelling the existing one will constitute a rebook | In line with the BaRS standard all operations used to modify a resource must be preceded by a read of the resource by means of a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Rebook-Methods.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Rebook-Methods.page.md index 7b44b769..a8436156 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Rebook-Methods.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Rebook-Methods.page.md @@ -30,13 +30,13 @@ Use the cancel method described above. The method for the subsequent booking of an appointment depends on the Application specific guidance within BaRS. The only difference would be the Appointment Resource would include Appointment.replaces referencing the previous appointment for provenance. Alternatively, rebooking an appointment can be used outside of use-cases supported by a BaRS Application, to fulfil a generic Appointment workflow, either way, the typical sequence of events using PUT or POST is: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.2.2, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot). * Select a slot. -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} Request Body @@ -78,13 +78,13 @@ Request Body Using PATCH: -* Select the service to book an appointment with. -* Confirm BaRS Capabilities. -* Request Available slots. +* {{pagelink:core-EndToEndWorkflow-ServiceDiscovery-1.2.2, text:Select the service}} to book an appointment with. +* Confirm BaRS [Capabilities](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/metadata). +* [Request Available slots](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Slot). * Select a slot. -* Perform a GET operation using the id of the appointment to /Appointment/{id} +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} * Set the Appointment.status value to "cancelled" -* Perform a PATCH operation using the id of the appointment to /Appointment/{id} +* Perform a [PATCH](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#patch-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} ```json { diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Update-Existing-Booking.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Update-Existing-Booking.page.md index 10bab0f2..8b63d342 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Update-Existing-Booking.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Appointment-StandardPattern/Update-Existing-Booking.page.md @@ -6,9 +6,9 @@ topic: core-StandardPattern-appointment-update-1.2.2 To update an appointment: -* Perform a GET operation using the id of the appointment to /Appointment/{id} -* Ammend or append the resource as required. -* Perform a PUT operation using the id of the appointment to /Appointment/{id} or POST against /$process-message, with a corresponding FHIR bundle (BaRS Applications only) +* Perform a [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} +* Amend or append the resource as required. +* Perform a [PUT](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#put-/Appointment/-id-) operation using the id of the appointment to /Appointment/\{id\} In this example a placeholder was created, and updated when the slot is selected. This is a hypothetical scenario. diff --git a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Index.page.md b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Index.page.md index 6d270ed6..84ed2ad5 100644 --- a/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Index.page.md +++ b/guides/Live-ImplementationGuide-BaRS/Home/Core/1.2.2/Index.page.md @@ -16,9 +16,9 @@ This version of core is strictly a preview of what is currently in development f - v1.2.0-alpha - v1.8.0 - v1.2.0 + v1.2.2-alpha + v1.8.2 + v1.2.0