The line that matters
Software that informs a clinical decision may be a regulated medical device in your jurisdiction. Software that sorts post, drafts letters and books appointments is not.
Almost all of the available time saving in a healthcare organisation sits on the administrative side of that line. Start there and the regulatory question does not arise.
Where the administrative burden is
- Referral processing — extracting details, checking completeness, routing
- Correspondence drafting from consultation notes, for clinician approval
- Coding support — suggestions a coder confirms
- Scheduling — matching appointment type, duration and clinician
- Document filing into the right part of the right record
Clinician approval is non-negotiable
Any letter or note that enters a patient record or reaches another clinician must be approved by the responsible clinician before it does. The draft saves the typing, not the responsibility.
Systems designed this way get adopted. Systems that blur the accountability do not, and should not.
Data handling requirements
- Processing location and any transfer, decided and documented
- Processor agreements covering health data specifically
- Retention aligned to your existing records policy, not a default
- Audit trail of who approved what and when
- Redaction where the task does not need identifiers
Where the value shows up
Faster correspondence turnaround, fewer incomplete referrals bouncing back, better coding capture and less clinician time on administration.
The last of those is what clinicians actually notice, and it is the reason these projects get supported rather than tolerated.