Skip to content

Implementation Guide 1.9.0 fixes to main #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cda69 merged 9 commits into from
Jun 26, 2025
Merged

Implementation Guide 1.9.0 fixes to main #494

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
d94a2ab
Making 1.0.7 appear
luci-davies Jun 25, 2025
0f1b898
Updated version and date
NaminderSoorma Jun 25, 2025
9a5b250
Merge branch 'develop' into feature/app7newcode
NaminderSoorma Jun 25, 2025
6522961
Merge pull request #492 from NHSDigital/feature/app7newcode
NaminderSoorma Jun 25, 2025
64a03fe
Cancellation typo
luci-davies Jun 26, 2025
b8d1418
Split-FindResource- Out
cda69 Jun 26, 2025
a912993
typo
cda69 Jun 26, 2025
73e5a89
Merge pull request #493 from NHSDigital/CGD-Cancel-ReOrder
cda69 Jun 26, 2025
1be1942
Merge pull request #491 from NHSDigital/20250625_LD-Bug-fixes-7
luci-davies Jun 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CodeSystem/usecases-categories-bars.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@
<system value="https://fhir.nhs.uk/identifier/CodeSystem" />
<value value="usecases-categories-bars" />
</identifier>
<version value="1.4.0" />
<version value="1.5.0" />
<name value="usecasescategoriesbars" />
<title value="Use Cases Categories BARS" />
<status value="active" />
<date value="2024-04-30" />
<date value="2025-06-25" />
<publisher value="NHS England" />
<contact>
<name value="NHS England" />
Expand Down
2 changes: 2 additions & 0 deletions ...e-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.0.7.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,10 @@ topic: TRN-Core-1.0.7
| Change | Description | Impact |
|------------------------------------------|----------------------------------------|---------------------------------|
| Standard Pattern Composite Messages - Cancellation | bundle.meta.versionID added to payload for consistency across BaRS documentation| <mark style="background-color: Yellow">correction</mark> |
| Standard Pattern Composite Messages - Cancellation | appointment.status example value updated to "cancellation" | <mark style="background-color: Yellow">correction</mark> |
| Failure Scenarios - GET /Slots | Link text <FHIR instant> update to <FHIR dateTime> for consistency| <mark style="background-color: Yellow">correction</mark> |
| Transactional Integrity | Post 409 Failure Scenario image updated to demonstrate 408 response | <mark style="background-color: Yellow">correction</mark> |

<br>
<hr>

Expand Down
2 changes: 2 additions & 0 deletions ...e-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/1.3.0.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,10 @@ topic: TRN-Core-1.3.0
| Change | Description | Impact |
|------------------------------------------|----------------------------------------|---------------------------------|
| Standard Pattern Composite Messages - Cancellation | bundle.meta.versionID added to payload for consistency across BaRS documentation| <mark style="background-color: Yellow">correction</mark> |
| Standard Pattern Composite Messages - Cancellation | appointment.status example value updated to "cancellation" | <mark style="background-color: Yellow">correction</mark> |
| Failure Scenarios - GET /Slots | Link text <FHIR instant> update to <FHIR dateTime> for consistency| <mark style="background-color: Yellow">correction</mark> |
| Transactional Integrity | Post 409 Failure Scenario image updated to demonstrate 408 response | <mark style="background-color: Yellow">correction</mark> |

<br>
<hr>

Expand Down
10 changes: 6 additions & 4 deletions ...lementationGuide-BaRS/Home/About-BaRS/Releases/Technical-Release-Notes/BaRS-Core/toc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,16 @@
filename: Index.page.md
- name: 1.3.0
filename: 1.3.0.page.md
- name: 1.0.7
filename: 1.0.7.page.md
- name: 1.2.2-alpha
filename: 1.2.2-alpha.page.md
- name: 1.1.6
filename: 1.1.6.page.md
- name: 1.0.6
filename: 1.0.6.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.6
filename: 1.1.6.page.md
- name: 1.1.5
filename: 1.1.5.page.md
- name: 1.1.4
Expand All @@ -24,6 +24,8 @@
filename: 1.1.1.page.md
- name: 1.1.0
filename: 1.1.0.page.md
- name: 1.0.6
filename: 1.0.6.page.md
- name: 1.0.5
filename: 1.0.5.page.md
- name: 1.0.4
Expand Down
2 changes: 1 addition & 1 deletion ...e-BaRS/Home/Core/1.0.7/Standard-Pattern-Composite-Messages/Cancellation.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -407,7 +407,7 @@ This payload is used to transmit all the necessary information that is required
| Appointment.meta | https://www.hl7.org/fhir/resource.html#Meta | MUST | 1..1 | |
| Appointment.meta.profile | This MUST be populated. Follow UK Core guidance for populating this element | MUST | 1..1 | https://fhir.hl7.org.uk/StructureDefinition/UKCore-Appointment |
| Appointment.meta.lastupdated | This MUST be populated. All resources MUST include 'lastUpdated' value, under meta section which MUST be the same timestamp for each resource when created from new, but MUST be a later timestamp on updates, if the content of a particular resource contains updated info for subsequent updates. Otherwise, maintain the timestamp originally sent. | MUST | 1..1 | 2023-03-08T12:01:08.4677672+00:00 |
| Appointment.status | This MUST be populated with 'booked' | MUST | 1..1 | cencelled |
| Appointment.status | This MUST be populated with 'cancelled' | MUST | 1..1 | cancelled |
| Appointment.description | This SHOULD be populated. It is the human readable description of the booking | SHOULD | 0..1 | Reason for calling |
| Appointment.start | This MUST be populated with the Start time of the booking | MUST | 0..1 | 2021-10-12T12:30:00+00:00 |
| Appointment.end | This MUST be populated with the End time of the booking | MUST | 0..1 | 2021-10-12T12:30:00+00:00 |
Expand Down
2 changes: 1 addition & 1 deletion ...onGuide-BaRS/Home/Core/1.3.0/Appointment-StandardPattern/Cancel-Booking.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ topic: core-StandardPattern-appointment-cancel-1.3.0

To cancel an appointment:

* 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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPCancellation-1.3.0, text:patient information}}, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* 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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPFindResource-1.3.0, text:find resource}} workflow, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* Set the Appointment.status value to "cancelled"
* 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\}

Expand Down
2 changes: 1 addition & 1 deletion ...onGuide-BaRS/Home/Core/1.3.0/Appointment-StandardPattern/Rebook-Methods.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Alternatively, rebooking an appointment can be used outside of use-cases support
* 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](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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPCancellation-1.3.0, text:patient information}}, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* 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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPFindResource-1.3.0, text:find resource}} workflow, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* Set the Appointment.status value to "cancelled"
* 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\}

Expand Down
2 changes: 1 addition & 1 deletion ...aRS/Home/Core/1.3.0/Appointment-StandardPattern/Update-Existing-Booking.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ topic: core-StandardPattern-appointment-update-1.3.0

To update an appointment:

* 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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPCancellation-1.3.0, text:patient information}}, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* 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\}. Alternatively, if the .id is not known, the read can be undertaken with [GET](https://digital.nhs.uk/developer/api-catalogue/booking-and-referral-fhir/v1_2_0#get-/Appointment), using the {{pagelink:core-SPFindResource-1.3.0, text:find resource}} workflow, and selecting the .id by the matching the required resource. NB: If a match cannot be performed, using this method, manual processes should be engaged.
* 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\}

Expand Down
1 change: 1 addition & 0 deletions guides/Live-ImplementationGuide-BaRS/Home/Core/1.3.0/Index.page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,7 @@ You will find here a set of documentation, specifications and services that desc
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-SPComposites-1.3.0 , text:Standard Pattern for Composites}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-SPMessageHeader-1.3.0 , text:Message Headers}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-SPCancellation-1.3.0 , text:Cancellation}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-SPFindResource-1.3.0, text:Find Resource Id}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-SPUseCaseCategories-1.3.0 , text:Use Case Categories}}</br>
&nbsp;&nbsp;&bull; {{pagelink:core-StandardPattern-appointment-1.3.0 , text:Standard Pattern - Appointments}}</br>
&nbsp;&nbsp;&nbsp;&nbsp;&bull; {{pagelink:core-StandardPattern-appointment-booking-1.3.0 , text:Booking}}</br>
Expand Down
Loading
Loading