Referrals into Pharmacy (Application 5) Change Log
This page will list all updates to the BaRS Application 5
| 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.1
This application moved from alpha to beta with a few minor updates.
Application Change Log
| Change | Description | Impact |
|---|---|---|
| Workflow diagram updated | Workflow amended to support new policy workflow narrative, putting the onus on the patient to contact the Pharmacist. The Pharmacist would only contact the patient first if they have concerns upon receipt of the referral. | |
| Scope change Constraint added | Added Constraint regarding reduced scope to meet delivery timeline. | |
| Additional NHS Verification Status permissable | A patient's NHS number can now be sent if it is known to be present but not traced. | |
| Safeguarding Concern no longer mandated | The inclusion of Safeguarding Concerns is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision. | |
| Individual Requirements no longer mandated | The inclusion of Individual Requirements is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| Urgency no longer mandated | Sending an urgency timeframe is not part of the scope for beta and, therefore, not being mandated in this release. Policy currently dictates the patient is responsible for contacting the Pharmacist, however, this requirement may be reinstated in the stable revision, following public beta. | |
| Cancellation no longer mandated | Cancelling a referral is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| Re-refer no longer mandated | Re-referring is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| Novel Medications no longer mandated | Including novel medications is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| Novel Allergies no longer mandated | Including novel allergies is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| SPNs no longer mandated | Sending SPNs is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
| Additional Information Sources no longer mandated | Sending reference to Additional Information Sources is not part of the scope for beta and, therefore, not being mandated in this release. This is a temporary state for beta phase only and the requirement will be reinstated in the stable revision, following public beta. | |
Payload Change Log
| FHIR Element | Previous | Current | Other | Referral/Booking | Rationale | Impact |
|---|---|---|---|---|---|---|
| Careplan.activity | SHOULD | MUST | Updated | Ref | Business logic 'Necessity' was incorrect. This value MUST always be present | correction |
| Task.description | Updated | Ref | Amended description to align with updated policy workflow narrative | non-breaking | ||
| ServiceRequest.occurencePeriod.end | Updated | Ref | Amended end time to reflect current 24hrs policy response in CPCS MI | non-breaking | ||
| ServiceRequest.requester | SHOULD | MUST | Updated | Ref | ServiceRequest.requester Necessity is SHOULD when should be a MUST. Most suppliers already conform to this | breaking |
| ServiceRequest.occurencePeriod.start | MUST | SHOULD | Updated | Ref | Amended to reflect policy change. The Sender cannot indicate urgency because the patient must make contact with the pharmacist | non-breaking |
| ServiceRequest.occurencePeriod.end | MUST | SHOULD | Updated | Ref | Amended to reflect policy change. The Sender cannot indicate urgency because the patient must make contact with the pharmacist | non-breaking |
| Bundle.meta.versionId | Updated | Ref | Updated example value to reflect use of version | non-breaking |
1.0.0-beta
This application moved from alpha to beta with a few minor updates.
Application Change Log
| 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 |