Supplies, claims and intake paperwork, carried across your systems.
Agents take the administrative steps between your patient administration, billing and supply systems. A named person approves each sensitive step. Decisions about care stay with your clinicians.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
The administrative load around care
AI agents for healthcare operations take on the work that keeps a hospital or clinic running but never touches a care decision: supply requisitions, claims the payer sent back, intake paperwork and contract review. Today a coordinator carries each item between the patient administration, billing and supply systems.
We design the workflow with you and run it on Ares, the platform. The agent prepares each step. Your billing lead, buyer or intake coordinator approves the ones you mark as sensitive.
- Each agent reaches only the records that the permission for that job allows.
- Identifiers you list are removed before content leaves, and the record names each one.
- It can run inside your own network, on one small machine. See the five guarantees.
Clinical work stays with your clinicians. We do not build agents that diagnose, recommend treatment or advise patients.
One returned claim, four systems, one resubmission a person approves.
The task: rework a claim the payer returned for a missing document. This workflow is designed. The requisition run in the sandbox shows the same approval step on a built workflow.
- 01In-house tool
Take the task and receive a credential for this one claim. It expires when the claim is resubmitted.
- Who approves
- No approval on this step
- On the record
- credential issued · this claim only
- 02Email
Read the payer's return notice and the reason it gives.
- Who approves
- No approval on this step
- On the record
- read-notice · allowed
- 03Documents
Find the referral letter the payer asked for in the document store.
- Who approves
- No approval on this step
- On the record
- find-referral · allowed
- 04In-house tool
Try to change the procedure code. Coding is outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- change-code · refused · outside permission
- 05Documents
Build the packet for the payer. Identifiers on your redaction list are removed on the way out.
- Who approves
- No approval on this step
- On the record
- claim-packet · redacted · listed identifiers
- 06In-house tool
Resubmit the claim. The step waits until the billing lead approves it.
- Who approves
- Billing lead
- On the record
- resubmit-claim · approved by billing lead
- 07Accounting
Update the expected payment date.
- Who approves
- No approval on this step
- On the record
- update-date · allowed
In short
- Can an agent open patient records it does not need?No. Each agent reaches only what the permission for that job allows. A request outside it is refused, on the record.
- What stops identifiers from leaving in a packet or a summary?Outbound content is checked before it leaves, and the identifiers you list are redacted. The record names what was removed.
- Who signs a resubmission, an order or a supplier change?A person you name. The agent prepares the step, and the step waits until that person approves it.
- Can it run inside our own network?Yes. It can run on one small machine in your building, with local models. Nothing leaves unless you allow it.
Administrative workflows for hospitals and clinics.
Operations and administration only. Each card carries its state.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Supply requisition with an approval threshold
The agents draft the requisition and check stock. An order above your threshold waits for the budget holder. The sandbox run orders laptops; the same steps apply to supplies.
Run it in the sandbox - Built
Supplier follow-up on a late delivery
A hidden instruction in the supplier's attachment is struck out. The buyer approves the new date.
Run it in the sandbox - Built
Supplier and service contract review
Agents summarise a contract. Identifiers are removed before the summary leaves, and counsel reviews it.
Run it in the sandbox - Designed
Returned claim rework
The steps above: the notice read, the missing letter found, a code change refused, the packet redacted, the resubmission held for the billing lead.
- Designed
Referral intake paperwork
The agent checks a referral against your intake document list and requests what is missing. A coordinator confirms the booking. It does not judge clinical urgency.
- Designed
Staff credential renewals
The agent tracks licence and training renewal dates and drafts reminders. The medical staff office approves each file.
- On request
Equipment service tickets
Service requests matched to the maintenance contract.
What your privacy officer can check
Ares does not replace your privacy officer. It gives that office evidence to check: which agent asked for which record, under which permission, what was removed on the way out, and what was refused.
We publish mappings for general guidance on AI agents, such as the Canada agentic AI guide and the EU AI Act. We have not mapped a health privacy law. Read the mappings. For storage and deployment, see security and data handling.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not make clinical decisions, give a diagnosis or advise patients. It works on operations and administration only.
- It does not certify your organization under any privacy or health records law, and we have not mapped one.
- Redaction covers the identifier patterns you list. It does not decide what a recipient needs.
- It does not decide which records an agent may reach. Your privacy officer sets that, and Ares enforces it.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Who else decides
Questions and answers
Tell us about one workflow.
Name one administrative process your coordinators carry between systems. We will say whether an agent should do it, and what the first step costs. The first step is a workflow assessment. Fixed price, quoted after one call.
A senior member of the team replies within two business days.