The follow-ups that decide the day
A lab result nobody chased. A recall list nobody worked through. A re-booking that was meant to be called yesterday. None of it is clinical work, all of it affects patients, and it lives in whoever remembered.
For a clinic or practice, Bosun tracks the administrative follow-ups that surround clinical care: lab results to chase, recall lists to work through, re-bookings to call, stock to order, equipment to service. It runs on your own server, and it is designed to be used with references rather than patient details - "chase the bloods for booking 4471", not a name and a diagnosis.
- Typical departments
- Reception, clinical, lab
- Patient details
- Not needed - use your references
- Where it runs
- Your server, your database
- Answers from
- Your own protocols
- Chases
- Recalls, lab work, re-bookings
Write it like this
- Good
- "Chase bloods, booking 4471"
- Good
- "Work the diabetic recall list"
- Good
- "Ring Thursday's cancellations"
- Avoid
- Names
- Avoid
- Conditions and results
How to use it without patient data
A clinic has obligations about patient information that a workshop does not, so this needs saying plainly. Bosun is built for internal task tracking, and the right way to use it is with your own references: "chase the bloods for booking 4471", "work the diabetic recall list", "ring back the Thursday cancellations". No names, no conditions, no results.
Two things help. It runs on your server, so nothing leaves your control except the message text sent to your AI provider for interpretation. And staff messages go through WhatsApp, which is end-to-end encrypted in transit but is still a consumer messaging app - so the discipline of keeping identifiers out is the actual safeguard, not an optional extra.
- Use your own booking or chart references, not patient names
- It runs on your server - we hold no copy and have no access
- Message text is sent to your AI provider to interpret; check their terms against your obligations
- Your data protection officer should look at this before you roll it out, and we will answer their questions
- Nothing in the product requires a patient identifier for it to work
The work around the appointments
Lab follow-ups
What is outstanding, how long it has been, and who was meant to chase it.
Recalls and re-bookings
The calling nobody gets to. Chased privately until it is actually done.
Stock and ordering
Consumables and supplies, with a job that is blocked when a supplier is late.
Equipment servicing
Calibration and maintenance set up once as recurring work, so the job appears on its own each month rather than depending on somebody remembering.
Protocol questions
"What is our procedure for a missed appointment?" answered from your own document, cited.
Who is carrying what
Reception, clinical and lab loads separately, so a gap shows before it becomes a complaint.
From nothing to running, in about a week
-
1
We talk for an hour
How your practice is divided, who does what, and the three things that get dropped most often.
-
2
We install and connect it
Your server, your WhatsApp number, your AI account, your domain. On your accounts, with the passwords handed to you.
-
3
We load your procedures
Whatever you already have written, converted and indexed. Whatever you do not, we start from a template for your trade.
-
4
You send one message
Your team gets told the number exists and what to send it. There is no training session, because there is nothing to teach.
Built for busy teams
On this page
Is this HIPAA or GDPR compliant?
Compliance is a property of how you use a system, not a badge software carries, so the honest answer is: it can be part of a compliant setup, and it is not compliant on its own. It runs on your server, we hold no copy, and it needs no patient identifier. What you must assess is your AI provider's terms and your own policy on staff messaging. We will give your data protection officer straight answers, including where the answer is unhelpful.
Does it replace our practice management system?
No. Your PMS holds appointments, records and billing. Bosun holds the follow-up work around them - the chasing and the calling that currently depends on somebody remembering.
Can I keep it to reception and admin only?
Yes, and many practices should. Put reception and administrative staff on it, leave clinical notes where they belong, and you get the chasing handled without touching clinical systems at all.
Where is the data stored?
In one file on the server you chose, in the country you chose. That is the whole answer, which is the point of self-hosting.