NHS Booking and Referral Standard

Guide v1.2.0 | Core v1.1.0

back

Referrals into Pharmacy (application 5) Change Log


This page will list all updates to the BaRS Application 5
  - 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.0.0-beta

Application Change Log

Releasing of v1.0.0 following the sucessful Private Beta of BaRS-UEC2. There are a number of updates that have been applied since v1.0.0-alpha that have informed by the Private Beta. These are all detailed the in the change logs.

Change Description Impact

Payload Change Log

FHIR Element Previous Current Other Referral/Booking Rationale Impact
Bundle.meta.lastUpdated Updated Ref Profile cardinality was incorrect. Updated from 1..1 to 0..1 correction
Bundle.meta.versionId MUST Added Ref The version of bundles is key to workflow and existed in examples breaking
CarePlan.status Updated Ref Incorrect status published. Updated from 'complete' to 'completed' correction
Patient.contact.telecom.rank MUST Added Ref The rank of a contact's contact number is essential to processing of a request but was omitted from the guidance. The rank existed in examples breaking
Organization.identifier MUST SHOULD Updated Ref Removed the necessity to include an identifier because these are not always available and not required to drive workflow non-breaking
Organization.identifier.system MUST SHOULD Updated Ref as above non-breaking
Organization.identifier.value MUST SHOULD Updated Ref as above non-breaking
Practitioner.identifier MUST SHOULD Updated Ref Removed the necesity to include an identifier because these are not always available and not required to drive workflow non-breaking
Practitioner.identifier.system MUST SHOULD Updated Ref as above non-breaking
Practitioner.identifier.value MUST SHOULD Updated Ref as above non-breaking
PractitionerRole.practitioner MUST SHOULD Updated Ref Removed the necesity to reference a Practitioner (in some circumstances) because the PractitionerRole may be sufficient when linked to an Organisation. Additionally,this not required to drive workflow non-breaking
PractitionerRole.practitioner.reference MUST SHOULD Updated Ref as above non-breaking
PractitionerRole.organization MUST SHOULD Updated Ref Removed the necesity to reference an Organization because the PractitionerRole may be sufficient when linked to a Practitioner. Additionally,this not required to drive workflow non-breaking
PractitionerRole.organization.reference MUST SHOULD Updated Ref as above non-breaking
PractitionerRole.healthcareService MUST SHOULD Updated Ref Removed the necessity to reference an Organization because the PractitionerRole may be sufficient when linked to a Practitioner. Additionally,this not required to drive workflow non-breaking
PractitionerRole.healthcareService.reference MUST SHOULD Updated Ref as above non-breaking
Observation.encounter MUST SHOULD Updated Ref Removed the necessity to strictly tie an Observation to an Encounter, there will be instances where relating to the patient is sufficient non-breaking
Observation.encounter.reference MUST SHOULD Updated Ref as above non-breaking
HealthcareService.Id MUST Added Ref The Id was omitted from guidance but is required to be included in the HTTP response from the Receiver. This follows the standard pattern of response by Receiver so should have already been included. breaking
HealthcareService.providedBy MUST SHOULD Updated Ref Removed the necessity to relate an Organisation to a HealthcareService. Although, it should be included if known, it is not always known and is not required to drive workflow non-breaking
HealthcareService.providedBy.reference MUST SHOULD Updated Ref as above non-breaking
Condition.Id MUST Added Ref The Id was omitted from guidance but is required to be included in the HTTP response from the Receiver. This follows the standard pattern of response by Receiver so should have already been included. breaking
Task.Id MUST Added Ref The Id was omitted from guidance but is required to be included in the HTTP response from the Receiver. This follows the standard pattern of response by Receiver so should have already been included. breaking
Task.restriction.period MUST SHOULD Updated Ref Incorrect necessity published. Updated from 'MUST' to 'SHOULD' correction


Previous Releases

1.0.0-alpha


This is a pre-release of v1.0.0-alpha - Referral into Pharmacy(application 5) which supports the use case "GP to Pharmacy CPCS Minor Illness".

Application Change Log

Releasing of v1.0.0 following the sucessful Private Beta of BaRS-UEC2. There are a number of updates that have been applied since v1.0.0-alpha that have informed by the Private Beta. These are all detailed the in the change logs.


Change Description Impact

Payload Change Log

FHIR Element Previous Current Other Referral/Booking Rationale Impact
back to top