back
Validation into CAS (Application 4) Change Log
This page will list all updates to the BaRS Application 4.
- Indicates a change inspired by provider or supplier feedback.
| Key |
Description |
| non-breaking |
Non-breaking changed introduced to the standard since the last release |
| breaking |
Breaking changed introduced to the standard since the last release |
| correction |
Correction to the standard since the last release |
1.1.1
This release includes the latest Use-Cases Category codes used by Application 4.
Application Change Log
| Change |
Description |
Impact |
| New Use-Case Category codes |
New Use-Cases Category codes added for use in Application 4. |
correction |
| Updates to Application 4 Examples |
Updates to all Application 4 Examples to include the latest Use-Case Category codes. |
non-breaking |
Payload Change Log
| FHIR Element |
Previous |
Current |
Other |
Referral/Booking |
Rationale |
Impact |
| ServiceRequest.category.code |
|
|
Update |
Validation Request / Interim Response / Final Response |
The new Use-Case Codes have been made generic |
correction |
| Patient.extension.valueCodeableConcept |
Patient.extension.url.valueCodeableConcept |
Patient.extension.valueCodeableConcept |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept.coding |
Patient.extension.url.valueCodeableConcept.coding |
Patient.extension.url.valueCodeableConcept.coding |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept.coding |
1..1 |
0..* |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept.coding.system |
Patient.extension.url.valueCodeableConcept.coding.system |
Patient.extension.valueCodeableConcept.coding.system |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept.coding.code |
Patient.extension.url.valueCodeableConcept.coding.code |
Patient.extension.valueCodeableConcept.coding.code |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept.coding.display |
Patient.extension.url.valueCodeableConcept.coding.display |
Patient.extension.valueCodeableConcept.coding.display |
Update |
Validation Request / Interim Response / Final Response |
FHIR path incorrect |
correction |
| Patient.extension.valueCodeableConcept |
Patient.extension.url.valueCodeableConcept |
Patient.extension.valueCodeableConcept |
Update |
Booking Request |
FHIR path incorrect |
correction |
Previous Releases
1.1.0
This is v1.1.0 - Validation into CAS(Application 4) which include the new requirement to reject a validation request from the CAS.
Application Change Log
| Change |
Description |
Impact |
| New Reject Validation Request functionality |
This version introduces a new requirement that allows a Responder(Receiver) to reject a validation request. e.g Failed Contact |
non-breaking |
| New Use Case Category added |
In line with the future direction of BaRS, Application 4 now requires an additional ServiceRequest.category.code. This drives workflow. |
breaking |
| New guidance for Use Case Category |
In line with the future direction of BaRS, Application 4 now requires an additional ServiceRequest.category.code in the ServiceRequest resource. This has been updated throughout the guide to include references to the new Use Case Category. Additional information about the use of Use Case Category can be found in standard pattern for BaRS operations. |
breaking |
| Bug fixes |
A number of bug fixes and corrections have been made to the implementation guidance for Application 4 |
correction |
Payload Change Log
| FHIR Element |
Previous |
Current |
Other |
Referral/Booking |
Rationale |
Impact |
| Encounter.status |
|
|
New |
Interim Response |
A status of 'cancelled' is to be used |
non-breaking |
| Encounter.reasonCode.coding.system |
FIXED |
|
New |
Interim Response |
No longer a fixed value. A new CodeSystem is used when a Rejection is sent. https://fhir.nhs.uk/CodeSystem/rejected-reasons-bars |
non-breaking |
| Encounter.reasonCode.coding.code |
FIXED |
|
New |
Interim Response |
No longer a fixed value. A Code from the relevant CodeSystem should be used. |
non-breaking |
| Encounter.reasonCode.coding.display |
FIXED |
|
New |
Interim Response |
No longer a fixed value. A Display from the relevant CodeSystem should be used. |
non-breaking |
| Encounter.reasonCode.text |
|
|
New |
Interim Response |
Supporting text for the Rejection can now be included |
non-breaking |
| ServiceRequest.category |
0..1 |
1..1 |
|
Validation Request / Interim Response / Final Response |
Updated in line with the BaRS Profile |
correction |
1.0.0
This is v1.0.0 - Validation into CAS(application 4) which supports the use case:
- for 999 Ambulance Service Trust (AST) validation requests to Clinical Assessment Service (CAS)
Application Change Log
| Change |
Description |
Impact |
|
| Application 4 released |
The release of Referral into UEC for Validation (Application 4) v1.0.0 to the guide |
breaking |
|
| - Correction to Interim Message Definition |
Correction to BaRS-messageDefinition-serviceRequest-response-validation-interim message definition in line with example and ERD, to include missing resources: HealthcareService, PractitionerRole, Practitioner, Organization |
non-breaking |
|
| Correction to Interim Response payload |
Correction to Interim Response payload in line with example and ERD to include HealthcareService resource in line with example and ERD |
non-breaking |
|
| Guidance update for Encounter |
Correction to Interim Response payload guidance for Encounter, Practitioner and PractitionerRole to reference Responder rather than Requester in line with example and ERD |
non-breaking |
|
| Interim Payload correction |
Correction to Interim Response payload to remove ServiceRequest.basedon and ServiceRequest.location.reference in line with example |
non-breaking |
|
| Corrections to Implementation Guide documentation. |
Minor text corrections to the guide to maintain consistency |
non-breaking |
|
| Correct MessageHeader.Definition for Interim and Final Response |
Update the payload implementation guidance to reference the correct Message Definition for Interim and Final Responses. |
correction |
|
| Correction to Flag (Scene Safety) guidance |
Correction to Flag (Scene Safety) guidance for Validation request and Final validation Response. |
non-breaking |
|
| Correction to scene-safety-codes-bars codesystem |
Codes referencing "trapped" have been removed from the Scene Safety Codes |
correction |
|
Payload Change Log
| FHIR Element |
Previous |
Current |
Other |
Referral/Booking |
Rationale |
Impact |
| ServiceRequest.performer.reference |
MUST |
SHOULD |
|
Interim Response |
In line with update to guidance as a non breaking change |
non-breaking |
| Encounter (Interim) |
1..3 |
2..2 |
|
Interim Response |
An Interim response includes 2 encounter resources (requester's and responder's). |
breaking |
1.0.0-beta
This is a pre-release of v1.0.0-beta - Validation into CAS(application 4) which supports the use case - for 999 Ambulance Service Trust (AST) validation requests to Clinical Assessment Service (CAS)
Application Change Log
| Change |
Description |
Impact |
| Application 4 released |
The first release of Referral into UEC for Validation (Application 4) v1.0.0-beta to the guide |
|
Payload Change Log
| FHIR Element |
Previous |
Current |
Other |
Referral/Booking |
Rationale |
Impact |
|
|
|
|
|
|
|
