O3 Referrals
Summary:
O3 is currently lacking both simple entry of Referrals, and more complete end-to-end Referral workflows, from ordering to tracking to completion, both for Referring Clinicians and Receiving Clinicians.
But it does remind us that External Referrals often happen across different softwares, or from software-to-paper-based sites.
1. Problem
2. User Stories
First, note that there are different types of Referrals with very different implications.
Person to Person: One Clinician to Another Clinician (often from a generalist to a specialist, e.g. OPD doctor to specific Oncologist; doctor to Nutritionist/Dietician - not always a doctor:doctor referral)
Person to Service/Program: (Internal Service or External Service, inside or outside of the current location)
Clinician to a type of support service, which could be a single person or a group of people (e.g. doctor to Social Worker; or to Nutritionist; or to a group Home Health follow-up program; or to a group Specialist program like “Oncology Service”)
Site to Site: One Site to Another Level of Site (e.g. a mid-tier health centre to a large hospital, or to a smaller clinic). Increasingly common with “PCNs”.
e.g. “Cardiologist evaluation requested” is the kind of IPD referral we automatically expect, BUT, we need to confirm: are specialist clinicians really the main “referral” workflow our end users have? Or are their real-world needs more nuanced (eg “Refer to local community diabetes outreach volunteer”) or more generalized (eg “Refer to Clinic”, which in most Sri Lanka facilities means “Refer to Clinic-Day list, meaning they’ll get seen by specialist/IM doctor whenever they’re next in town, so it’s really a travelling-IM-Clinic-Day”)?
Simple Requirements Needed for an MVP:
Referring Party
Order & Add detail as-needed to Referrals
Track Status of Referral(s) for a Patient
Print a Discharge Summary or Referral Summary
Receiving Party
Track what’s been requested within a single location / distribution (e.g. one doctor referring a patient to an in-house specialist, e.g. OPD doctor to Oncologist)
More Advanced; e.g. in e-Referral-supported Ecosystem:
Referring Party
___
Receiving Party
Receive e-Referrals
Track what’s been received universally
3. Market Analysis
KenyaEMR 3.x
Has a Referrals landing page. Should investigate!!
Requirements from MoH Suriname (2025)
Theme | Requirement Description |
---|---|
Referrals: | The system shall have the ability to record referral information, including the reason for the referral, the specialist or institution to which the patient was referred, and any referral notes. |
Referrals and Prescriptions: | The system shall facilitate the documentation of referrals and prescriptions, including medication prescriptions, lab referrals, imaging referrals, etc. It should also support electronic prescribing where possible. |
Referral Creation: | The system shall allow healthcare providers to create and manage referrals, including details such as the reason for the referral, the specialist or institution to which the patient is being referred, and any relevant clinical notes |
Integration with Patient Records: | The system shall link referrals to the patient's medical record, ensuring that the referral is connected in the Health Information Exchange Platform and in the future the referred provider has access to relevant medical history, medications, allergies, lab results and other clinical information. |
Status Tracking: | The system has the possibility to track the status of each referral, from creation, through the patient's visit to the specialist, to the receipt of the specialist's report. As the digital transformation for secondary care is a future endeavor this functionality should be included in such a way that status updates are provided through the HIEP. |
| The system should support communication between referring and receiving providers through the Health Information Exchange Platform to facilitate coordinated care. |
| The system shall provide customizable referral templates, allowing for standardized and complete referral information, which can improve the efficiency of the referral process and the quality of care received by the patient |
| The system shall maintain an audit trail of all referral activities, including the creation, modification, and deletion of referrals, with a timestamp and the user's identification. |
| The system shall ensure that all referral data is stored and transmitted securely, in compliance with all relevant regulations |
Decision Support: Referral Sets: | The system shall provide standardized lab referral sets based on best practices for common conditions, which can improve efficiency and consistency in care delivery. |
HL7 Version 2 Support | The system shall initially support HL7 version 2 for the transmission of healthcare data. This includes …. referrals. |
Content for Discharge Summary / Pt Information: |
|
Requirements from Madiro / MSF (2024)
|
|
---|---|
Ability to individually track referrals and their outcomes |
|
Ability to manage custom lists of options by instance (names of external partners for referral, places of origin / living) |
|
Requirements from PIH (2024)
|
|
---|---|
As a triage staff I want to track where the patient came from (e.g. referral from) so that I can report severity of symptoms and referral location (e.g. if they came from another clinic or hospital) |
|
Requirements from MoH Rwanda (2023)
|
|
---|---|
Review Referral | The user is able to view patient referral information but limited according the user privileges. |
| The user is able to view a list of Internal and external referrals in order to follow up care. |
Discharge/ check out Patient | "The user is able to discharge a Patient and capture patient specific clinical details related to the discharge from the OPD service/ clinics. The details include discharge diagnosis, and the discharge date and time etc. If the patient is discharged to seek further services, the referral form should be filled out.” |
Email External transfer documet | "The user is able to email a formatted version of the external transfer document to the relevant recipient. The email will include relevant clinical information, dates and time and facility header etc.
The referral/transfer sheet should include: The reason for referral/transfer; Significant findings; Procedures and treatments; A list of current medications; The patient’s immediate condition; Where the patient is being transferred; The type of transportation and required monitoring during transport. The system should notify the receiving facility." |
View a list of external transfers. | The user is able to view a list of external referrals in order to follow up on their progress. |
Add counter referral notes external referrals. | The user is able to add counter referral feedback to a clinician that referred the Patient in order to maintain the continuity of care. |
Print counter referral notes external referrals. | The user is able to counter referral feedback in order to provide feedback via the Patient. |
Send follow-up comments for external referrals. | The user is able to mail follow up feedback to a clinician that referred the Patient in order to maintain the continuity of care. |
Support Telemedicine | The user is able to request a clinical review and provide a feedback report of exam result for example to obtain consults or advice from providers from referral hospitals, private or other countries |
Determine type of referral | The system will allow the clinician to conduct Individual clinical assessment prior to transfer. The outcome or a decision should be then discussed with patient or care taker and if possible there should be subjective to a consent note from the patient before transfer. |
Pre-transfer package | The system should provide clinical examination and consultation to Stabilization the patient by providing all the medical care necessary to make sure the patient's condition will not deteriorate and their vital signs are within the healthy range. Here the different |
CHW | CHW Referrals |
Patient referral | Allow for referral of patient with cancer suspect to high level of care for further investigation and treatment |
Require referral | Allow referring client to another level, the system should provide list of available referral points. |
Referral /exit | Allow for patient referral to home-based care and or other health facility based on clinical history |
Referral/ Exit: Record Referral Outcomes | Allow to record patient outcomes following treatment including death if happened |
Examples from Ampath MRS
What | Visuals | Notes |
---|---|---|
Video of the patient referral process at AMPATH |
| |
Referral Order Form |
| |
Referral Order Form: Details |
| |
Confirm Double-Check Message |
| |
Clear Success Message |
| |
Referral Tracking Dashboard | a widget on the clinic dashboard to show a list of referrals that have been made to your clinic: |
4. Technical Considerations & Dependencies
Will need some kind of config and/or admin UI to keep the list of clinicians updated.
5. Sketches
Action / Story | Visual | Notes |
---|---|---|
Order a Referral / Service |
| |
Configurable Form with Reason |
|
|
Table showing Referrals and Status | (simple table; decide on columns) Status may need to be manually update-able with notes. (e.g. patient returns and shares paper referral note, may be printed or handwritten) |
|
Left Nav area to access Referrals and Programs |
|
|
|
|
|