Practical software guides
A referral-coordination layer can help authorised staff track whether a request was received and what administrative information is missing. It should not replace clinical records, determine urgency or promise better care from software alone.
| Stage | Administrative view | Boundary |
|---|---|---|
| Referral received | Reference and authorised destination | Clinical content stays in approved clinical system |
| Receipt checked | Assigned coordinator confirms receipt | No automated clinical acceptance |
| Missing item | Approved request to sending team | Share minimum necessary data securely |
| Appointment coordinated | Confirmed details for authorised recipient | Urgent-care route remains independent |
| Closed | Administrative completion and retention action | Clinical outcome not inferred |
Use role-limited views, an approved basis for sharing and a documented retention policy. A public or broadly shared spreadsheet is not an appropriate substitute. Do not put diagnosis or medical images into generic messaging just to keep everyone informed.
Keep the system boundary honest
An integration must use the institution’s approved interface and identities. Duplicate, stale or unmatched referrals remain exceptions for qualified staff. Test unauthorised access, wrong-recipient delivery and downtime with synthetic records before any patient use.
The US SAFER Guides offer health-IT safety context, not Bahamian law. Clinical and privacy specialists must approve the real workflow, urgent escalation and access model. This guide removes categorical comparisons with global health platforms and makes no 45–60-day build or clinical improvement promise.