Skip to main content
The Human Bit

GuidesBy professionPractice managers, care coordinators and clinic administrators

AI for care and health administrators when the details belong to someone else

For Practice managers, care coordinators and clinic administrators.

Start here

What this helps you do
Use AI for the rostering puzzle, the family letter and the compliance paperwork, with a hard line around anything that identifies a patient or a resident, and a named clinician signing anything that touches care.
What you leave with
A repeatable workflow and a starter prompt you can adapt to your own work.
What to check before trusting it
You strip the identifying details before anything is pasted, every time, not on the days you remember
Ask Bit to set up this workflow

Best fit today: Claude or ChatGPT.Our read of the reviewed tool guides, not tested by us. Reviewed 19 September 2026. Open a tool guide for what each one does with this kind of work.

When to use this

Two carers call in sick before seven. A family wants to know why the visit time moved. The accreditation folder is out of date and somebody is coming to look at it. Every one of those jobs is attached to a real person's private health information.

  • Works through a rostering puzzle once you describe the shifts, the constraints and the qualifications required, with no names attached
  • Drafts the letter to families about a change to visiting hours or a new charge, in plain words rather than policy words
  • Reads your current policy alongside the wording of the standard it is meant to meet and lists where your version says nothing
  • Turns a long procedure into a one page version a staff member can actually follow at three in the morning

Workflow

  1. Set the boundary before you set the task. Names, dates of birth, addresses, health identifiers, next of kin numbers and anything clinical about a named person do not go into a general assistant. Google states it plainly for its own app: do not enter confidential information you would not want a reviewer to see, and human reviewers do review some of the data collected.

  2. Rewrite the problem with roles instead of people. Carer 1, first aid qualified, unavailable Thursdays, gets you the same roster answer as a real name and carries none of the exposure.

  3. For the same reason, do not connect a mailbox full of patient and family correspondence. Google's own guidance on Connected Apps is not to connect apps that hold personal or confidential information you would not want used to train generative AI models.

  4. Keep the standing paperwork in one workspace rather than re-pasting it each month. Claude Projects holds its own uploaded files and instructions alongside the chat, which suits a policy set you return to.

  5. Route anything clinical through professional sign off before it leaves the building. Anthropic's usage policy requires qualified professionals to review outputs before they are distributed for healthcare, patient care and medical guidance uses, and requires people to be told AI was involved.

  6. Note on the policy or the letter what you used a tool for. A short record turns the next audit conversation into a fact rather than a memory.

Prompts to try

Use it, adapt it, and make it your own.

I am building a staff roster. Here are the shifts to cover and the constraints, with no real names: [Carer 1: first aid qualified, unavailable Thursdays. Carer 2: night shifts only. Shift list: ...]. Produce a roster that covers every shift and meets every constraint. If a shift cannot be covered without breaking a constraint, say so and name the blocking constraint instead of solving it.

Human lens

  • You strip the identifying details before anything is pasted, every time, not on the days you remember
  • A named clinician signs anything that touches care, medication or a change in someone's condition
  • You know that a particular resident cannot be rostered alone with a particular carer, and that is not a fact any tool holds
  • You decide what families are told and when, because a correct letter sent at the wrong hour still lands badly

What to avoid

  • Removing the name is not the same as deidentifying. One street, one uncommon diagnosis and an admission date can identify a person together when none of them does alone.
  • Never paste an incident report, a wound photograph or a copy of an identity document into a general assistant, not even to have it summarised. The summary is not the risk. The upload is.
  • A roster can look complete and still break a rule it was never told about, such as a minimum number of qualified staff on a night shift. Check it against your own staffing requirements rather than against how neat it looks.
  • General tools do not know your jurisdiction's aged care, privacy or health records rules, and they will still answer with confidence. Take the requirement to whoever is accountable for compliance in your service.
  • Family correspondence is care correspondence. A warm draft that guesses at a clinical reason for a change does more damage than a plain one that does not guess.
  • Anthropic advises keeping details such as bank account numbers and login credentials out of chats, which in a practice covers the billing and payment information sitting in the same folder as the care notes.

Reviewed 19 September 2026

The Human Bit Weekly

The useful changes, not every launch.

One short issue every Monday. What changed, what it means for your work, and the part that stays yours.

The Human Bit records when and how consent was given. Subscription is confirmed only after the email provider accepts the request.