...
AT-01.1 - Recommended Referrals | |
---|---|
DCF Core Capability | |
As a Healthcare or Clinical Professional, I want to see system automated recommended referral routes for internal referrals and, have these integrated into the clinical workflow So that, I can accept, amend or override referral routes in clinical workflows Acceptance criteria 1:Given the need for an internal referral When the clinical need for another service is required Then recommended referral routes are shown and integrated into to clinical workflow | |
Application Function | Description |
AF340 Review Recommended Referrals | The system displays recommended internal referral routes within a clinical workflow and allows the clinician to choose an appropriate referral route |
AF193 Create Patient Referral | This is the ability of the system to enable an authorised clinician to initiate an electronic referral via a standardised referral form which will be sent to the applicable clinical service for review and stored against the Patient record. The form must support conditional logic to only display fields relevant to the speciality where the referral is being made. |
AF194 Referral Validation | This is the ability of the system to ensure that all relevant information has been provided and that the referral is not a duplicate. |
Standards Compliance | |
STD124 Clinical referral information - https://data.standards.nhs.uk/published-standards/clinical-referral-information |
AT-01.2 - Digital Handover | |
---|---|
DCF Core Capability | |
As a Healthcare or Clinical Professional I want to produce digital handovers of care between care settings onsite and remotely So that, I can support both inbound and outbound referrals Acceptance criteria 1:Given the need to handover the patient between care settings (internal or external) When a handover is required Then I am able to handover a patient without the need for paperwork Acceptance criteria 2:Given the identify a patient using their NHS number When accessing or sharing patient data Then all patient data must be associated with an NHS number Acceptance criteria 3:Given the need to process patient data When accessing or sharing patient data Then all appropriate information governance standards will be adhered to Acceptance criteria 4:Given the need to share data with third party systems When sharing data Then the appropriate minimum dataset(s) must be used Acceptance criteria 5:Given the need to transfer care to other care settings When creating the digital handover Then the system must adhere to Transfer of Care - Acute Inpatient Discharge Standard (DAPB 4042) Acceptance criteria 6:Given the risk from allergies to and intolerances of medications When transferring patient data Then any known allergies and/or intolerances should be sent in compliance with DAPB4013 | |
Application Function | Description |
AF193 Create Patient Referral | This is the ability of the system to enable an authorised clinician to initiate an electronic referral via a standardised referral form which will be sent to the applicable clinical service for review and stored against the Patient record. The form must support conditional logic to only display fields relevant to the speciality where the referral is being made. |
AF204 Create external Patient referral | The ability of the system to enable a clinician to refer a patient to an external service via an electronic notification (Messaging, Email, API call to target system) |
AF195 Review Patient Referral | The ability of a receiving service/clinician to review new referrals that have been made which they can accept, reject or request further information. Where a referral is rejected or further information is required the sender must be notified and be able to provide additional supporting information in a resubmission of the referral. |
Standards Compliance | |
Data Set - Emergency care | |
| |
| |
| |
| |
| |
|
...