Industries · Healthcare
AI for Canadian clinics and healthcare teams
The clinic handbook, the infection-control policy, the rostering rules — ask them in plain language and get the paragraph back. Digby is an admin assistant, not a clinical device.
01
What it does for a clinic or health team
- 01
Policy and procedure Q&A
the clinic manual, the infection-control policy, the privacy policy, the accreditation standards: uploaded once, asked about endlessly, answered with the passage.
- 02
Patient-adjacent admin
appointment reminders, referral letters, patient-education handouts, staff rosters and job descriptions.
- 03
Onboarding a locum
a new physician or nurse asks the ten questions everyone asks in week one and gets answers from the clinic’s own documents.
- 04
Scheduled briefings
a Monday summary of what changed in the policies a manager watches, or a weekly digest of the inbox.
- 05
Bilingual patient materials
plain-language handouts written in English or French, at the reading level you ask for.
02
What Digby is not
Digby is not a medical device, not a diagnostic tool, and not a clinical decision support system. It does not interpret tests, does not triage patients and does not give treatment recommendations. Nothing it produces is clinical advice.
The line we keep: it works on the paperwork around care — the policies, the letters, the schedules, the training material — and never on the clinical judgement itself.
03
PHIPA awareness, stated honestly
Ontario’s health privacy law, PHIPA, and the equivalent provincial health statutes set rules for personal health information: who may collect it, where it may be used, who is accountable. Digby stores data in Canada and gives you the controls a privacy officer will ask about — but we do not claim PHIPA certification, because there is no such certificate to hold.
Whether a particular document may go into an AI tool is a decision for the clinic’s privacy officer and custodian, under their own policy. A common and sensible line: policies, procedures and templates go in; identified patient records stay in the clinical system.
04
Clinic-controlled infrastructure
A clinic that must keep everything on its own network can run the full Digby stack on its own server with its own model endpoints — documents never leave the building and inference happens on hardware the clinic controls. Hosted Digby is the same product with Canadian storage and models served on Canadian hardware.
05
The controls a privacy officer asks about
- 01
Storage
accounts, conversations, memory and files live in the Canada Central region in Montréal.
- 02
Inference
the models that write answers are served on Canadian-located GPU hardware.
- 03
Training
your content is never used to train or fine-tune AI models.
- 04
Memory
every fact Digby remembers is visible, editable and deletable, and conversations can be deleted individually or wholesale.
- 05
Sharing
nothing is visible to anyone unless a share link is created, and every link can be revoked.
- 06
Access
projects use viewer, editor and admin roles, so people see only the projects they were invited to.
06
A sensible first month
Start with the documents nobody argues about: policies, procedures, the staff handbook, accreditation standards. Let the team ask questions about their own procedures before anything patient-adjacent is involved.
Then add drafting work — letters, handouts, rosters — with a named reviewer. Keep identified patient information in the clinical system unless the clinic’s privacy officer has decided otherwise in writing.
Frequently asked questions
Is Digby a medical device?
No. Digby is a general-purpose assistant used for administrative and policy work. It is not a medical device, does not diagnose, does not triage and does not support clinical decisions.
Can we use it with patient information?
Digby stores data in Canada and gives you deletion, memory and sharing controls, but whether identified patient information may enter any AI tool is a decision for your privacy officer under PHIPA or your provincial health law. Many clinics keep patient records in the clinical system and use Digby for policies, procedures and templates.
Is Digby PHIPA compliant?
We do not claim compliance or certification — no such certificate exists to hold. Digby is designed to support a clinic’s own PHIPA obligations: Canadian storage, Canadian inference, no training on your content, visible and deletable memory, and revocable sharing.
Can we run it inside the clinic?
Yes. Self-hosted Digby runs on the clinic’s own server with its own model endpoints through Docker Compose.
Does it read scanned documents?
Yes. PDFs, Word documents, spreadsheets and images are read directly, and a scanned page is read from the page image by the document reader.
Who can see a project?
Only the people invited to it, as viewers, editors or admins. Connected apps act as the person who connected them and can only reach what that person can reach.
Try asking Digby
Keep reading
Try Digby now.
No account needed. Models and data stay in Canada.