The line to stay behind
Software that informs a clinical decision may be regulated as a medical device in your jurisdiction. Software that processes referrals, manages correspondence and administers appointments is not.
Almost all the available time saving in a healthcare organisation is on the administrative side of that line. Starting there means the regulatory question does not arise.
What we build
- Referral processing — completeness checking, routing, acknowledgement
- Correspondence workflow — drafting, clinician approval, sending, filing
- Appointment administration — scheduling rules, reminders, DNA tracking
- Document management — filing into the right part of the right record
- Administrative reporting — waiting times, throughput, capacity
Clinician approval is structural
Anything entering a patient record or reaching another clinician must be approved by the responsible clinician. The system saves the typing, not the responsibility, and that must be evident in how it works.
Systems designed this way get adopted; systems that blur accountability do not, and should not.
Data handling requirements
- Processing location and any transfers, decided and documented
- Access strictly by role, with every access audited
- Retention aligned to your records policy, not to a technical default
- Anonymisation for any test or development data
- Encryption at rest and in transit, as a baseline
Where the value shows up
| Improvement | Effect |
|---|---|
| Referral completeness checking | Fewer bounced referrals |
| Correspondence workflow | Faster turnaround, less clinician admin |
| Appointment reminders | Lower non-attendance |
| Automatic document filing | Records complete and findable |
| Waiting time reporting | Capacity managed from data |