Do the agents do any clinical work?

No. They work on the back office only: intake and referrals, scheduling, claims, rosters and HR. Diagnosis, treatment and the clinical record stay with the clinicians, and an agent never changes what a clinician recorded.

Our practice system is closed. Can agents work with it?

It depends on the system, and the AI Sprint finds out. It reads what your practice information system allows, and what already runs in the mail, documents and calendars around it, and the workflow is built on what is there.

How do you handle patient data?

Patient data stays in your systems under your access rules and your information security policy. The agents see only the administrative data a workflow needs, and every action is logged. Which models may see which data is a design decision the AI Sprint makes explicit rather than a default.

Can an agent book or cancel an appointment on its own?

Not by design. Agents propose; the front desk confirms every appointment and every change before a patient hears about it. The gate is built in, so nobody can switch it off by mistake.

Which workflow should we start with?

Usually patient intake and referrals, because referrals come in every day and every new patient waits on them. The AI Sprint confirms whether that holds for your practice or whether scheduling or insurer claims come first.

What do we own at the end?

The system, its documentation, its rules and templates, and the runbooks. We hand it over so the practice runs it without us.

A pale stone seahorse with an indigo snout, an indigo fin and fine indigo circuit lines on its body stands on an oak desk in the back office of a health care practice and holds a file folder with its curled tail. Fine indigo lines run into the disc under it from the shelves of file folders, an open appointment book and a few referral letters. Its tail curls around a terracotta disc with a white check: a person's sign-off.

Who it's for

Health care practices

Agents on the back-office systems you already run.

We make the systems your front desk and back office work in fit to carry agents, then put agents on patient intake and referrals, scheduling, insurer claims and rosters, with your staff at every decision a patient or an insurer feels. The clinical work stays with the clinicians.

Start with one workflow in a week

One week. One back-office workflow. A working example on your own data.

Praxeum puts AI agents on the back office of health care practices: patient intake and referrals, scheduling, insurer claims, rosters and HR. First we fix what stops the practice's systems from carrying that work, then agents prepare it, with practice staff signing off, every action logged, and the practice owning it. Diagnosis, treatment and clinical records stay with the clinicians.

Workflows we build for health care practices.

The back office only, by department, with where most practices start.

The agent does it, on record
A person decides
What the agent knows: your company memory

Client intake and files
Where most firms start
1. A referral letter arrives
2. The agent does it, on record: Registered in the patient file
3. The agent does it, on record: Details and insurer checked
4. The agent does it, on record: Intake prepared
5. A person decides: The assistant confirms the intake
6. Patient ready for the first visit
With company memory Knows how your practice handles each kind of referral, from the procedures and notes your staff share.
Also: Practical patient questions
Planning and scheduling
1. A patient asks for an appointment
2. The agent does it, on record: Matched to the right calendar
3. The agent does it, on record: Clinician and time proposed
4. A person decides: The front desk confirms
5. Booked
With company memory Knows which appointments your front desk never books back to back, and why.
Also: Rosters
Finance and administration
1. Care is delivered
2. The agent does it, on record: Checked against the insurer's rules
3. The agent does it, on record: Rejected claims prepared again
4. A person decides: The practice manager resubmits
5. Claim paid, on record
With company memory Knows why each insurer sends claims back, and how your staff put them right.
Also: Patient invoices
HR and personnel
1. A new colleague starts next month
2. The agent does it, on record: Contract from the practice template
3. The agent does it, on record: Accounts and a first-week plan
4. A person decides: The practice manager approves each step
5. First day ready
With company memory Knows the practice's own steps for a new colleague that never made it into the checklist.
Also: Absence and leave

Where the work stalls in health care practices.

Not adopted
The practice system has portals and new features, and the front desk still types referrals in by hand and answers the same questions by email, because nobody built the features into how the practice runs its day.
Referrals by hand
Referral letters arrive by secure mail, post and portal, someone registers each one by hand, and the patient waits for an intake appointment.
Claims sent back
Every insurer has its own rules, and each claim that comes back means someone works out what went wrong and sends it again.
Hard to hire
Practice assistants and receptionists are among the hardest staff to find, and every referral, claim and roster still waits for one of them.

Three workflows that are usually the first candidates.

Examples to start your own list from, each run by agents that work alongside your team as co-workers. The AI Sprint finds the ones that fit your operation.

Patient intake and referrals

Today: A referral arrives by secure mail or post, an assistant reads it, types the patient's details and insurer into the practice system, calls about what is missing, and the patient waits for an intake.
Agents take over: Agents read each referral, take out the administrative details, check the patient's insurer and what is missing, prepare the registration and the intake forms, and propose an intake slot in the right calendar.
A person decides: Practice staff confirm every registration and every appointment; what the referral says about the patient's care is for the clinician to read and decide on.
The audit trail records: The referral, what was taken from it, what was missing, who confirmed the registration and when are recorded per referral.
Your team owns: The intake rules, the forms and the calendar rules are the practice's own.

Scheduling and rosters

Today: Appointment requests come in by email, portal and phone, the front desk fits them around each clinician's calendar, and next month's roster is built in a spreadsheet.
Agents take over: Agents read each written request, match it to the right calendar and clinician, propose a time, and draft next month's roster from availability, leave and opening hours.
A person decides: The front desk confirms every appointment; the practice manager approves the roster and every change to it.
The audit trail records: Each request, each proposed time, each roster version and who approved it are recorded.
Your team owns: The scheduling rules, the appointment types and the roster rules belong to the practice.

Insurer claims

Today: Claims go out in batches, rejections come back with a code, and someone works out per claim what went wrong and corrects it by hand.
Agents take over: Agents check each claim against the insurer's rules and the patient's cover before it goes out, read every rejection, and prepare the correction with the reason.
A person decides: A person approves every batch and every correction before it is sent, and an agent never changes the care that was recorded.
The audit trail records: Every check, every rejection, every correction and who approved it are recorded per claim.
Your team owns: The checks per insurer, the correction rules and the batch schedule are the practice's own.

What your agents need to know in health care.

Which referrals need which intake, and the details your assistants always check before booking, written down or not.
How each clinician wants their calendar run, from the appointment types to the slots kept free.
Which claims each insurer sends back and why, from the corrections your team made before.

Where practices usually start.

Patient intake and referrals, for most practices. Referrals arrive every day, the rules for what an intake needs already exist, and the judgment line is clear: staff confirm every registration, and clinicians decide on the care. It is also the step every new patient waits on.

How it would go

01The AI Sprint maps the current intake with the assistants and the front desk who do it today, and reads what your practice system, mail and calendars allow before agents can carry it.
02The working example prepares the intake for one month of real referrals, nothing registered and nothing sent.
03The build adds the staff confirmation, the intake rules, the audit trail per referral, and the handover to the practice team.
04Scheduling and insurer claims follow once intake runs.

The governed layer in health care.

Where practice staff sign off

Every registration and appointment, every roster and change to it, every claim batch and correction, and every message to a patient. Agents prepare, your staff commit, and the clinical decisions stay with the clinicians.

What the audit trail records

What was taken from each referral, every proposed appointment and roster, every claim check and correction, and who approved what. Enough to answer a patient, an insurer or a supervisor.

What the practice owns

The intake rules, the scheduling and roster rules, the claim checks and the runbooks, in the systems your practice already runs. When an insurer changes its rules, the practice changes the check.

Start with one back-office workflow.

One week, fixed scope. You leave with a working example of one back-office workflow on your own data, a read of your practice system, email and calendars, and a plan for what to build next.