What is an Agentic Operations System (AOS)?
A reference definition of the AOS category: what it is, what separates it from a RIS or an RCM, and the five tests that determine whether a system qualifies.
Version 1.0, August 2026. Maintained by Alpha Nodus.
The definition
An Agentic Operations System (AOS) is the system of work for a diagnostic imaging organization. Within it, AI agents perform the operational work between a physician's order and the payment for the study: intake and scheduling, eligibility, prior authorization and estimates, patient communication, claim submission, remittance and collection. Rather than queue that work up for staff, the system completes it.
A RIS is a system of orders. An RCM is a system of claims. An AOS is a system of work.
An order records what should happen. A claim records what did. An AOS makes it happen.
Every incumbent category in imaging is organized around storing and displaying operational information so a person can act on it. An AOS is organized around completing the action.
Why a new category exists now
For thirty years, imaging software has been divided along a line that does not exist in the actual work.
The RIS owns the front of the process: orders, demographics, slot inventory, scheduling. The RCM owns the back: claims, billing, collections. Both categories are mature and well understood, and the boundary between them gets treated as a fact of nature.
It isn't one. The line is an artifact of how the software was sold.
In diagnostic imaging, the front of the process determines the back. A denied claim is, overwhelmingly, a front-office mistake: a missing authorization, an unverified eligibility, a mis-keyed order. The back office finds it forty-five days later, when it is expensive and often unrecoverable. Unused capacity is the same story. An imaging center running at 60 to 65 percent utilization while patients wait weeks for an appointment is not short of scanners. It is short of the operational throughput required to fill them.
So the work between the order and the payment is one continuous process. The software that serves it is two products with a seam down the middle, and the seam is where the margin goes.
Historically the seam was staffed. Schedulers, intake coordinators, authorization specialists and eligibility clerks existed to carry information across a gap the software refused to close. That was the only available answer, because the work requires judgment, phone calls, portal navigation and the reading of badly handwritten faxes, none of which software could do.
That constraint lifted. Agents can now hold a phone conversation, read a smudged order, navigate a payer portal that has no API, and decide what to do next. Once that is true the seam no longer needs staffing. It needs a system, and that system is an AOS.
The five tests
Not everything marketed as agentic, automated or AI-powered is an Agentic Operations System. These five criteria separate the category from adjacent ones. A system that fails any of them is doing something else, which may still be useful but is not this.
1. It performs the work, not the workflow
The measure is completed transactions with no human involvement, not clicks saved or screens consolidated. Workflow software makes a person faster. An AOS removes the need for the person.
Ask: What percentage of prior authorizations complete end to end with no human touch? A vendor who answers in time saved rather than completion rate is describing workflow software.
2. It spans the order-to-payment seam
An AOS treats intake through payment as one process rather than two modules with a handoff between them. The test is not whether both functions appear on the price list. It is whether a problem discovered at one end gets resolved at the other, by the same system, without a person carrying it across.
Ask: When a coverage problem turns up at scheduling, what resolves it, and does the patient arrive with it already fixed?
3. It operates systems it does not own
Most of imaging operations runs through systems the imaging center does not control and cannot change: payer portals, clearinghouses, referring-physician fax lines, a legacy RIS with no modern interface. An AOS has to work through whatever interface exists, whether that is an API, HL7, FHIR, or driving a browser the way a person would. A system that requires every counterparty to be integrated is not an operations system. It is an integration project.
Ask: What happens when the payer has no API? "We'd need them to build one" is a disqualifying answer.
4. It scales with volume, not headcount
An AOS decouples operational capacity from staffing. Doubling volume in a week should not require hiring, and should not require notice. In this category, cost per transaction falls as volume rises. A staffed operation works the other way: fixed cost, and hiring ahead of demand.
Ask: What happens to our operating cost if volume doubles next month? A seat-based license answers this question badly.
5. It escalates by exception, not by default
Humans do not disappear from an AOS. They move. Routine work completes on its own, and genuine exceptions go to a person with the full context attached: ambiguity, clinical judgment, an angry patient, a payer behaving unusually. Maturity shows up as a falling exception rate, and a vendor should be able to state theirs.
Ask: What is your exception rate by workflow, and how has it moved over the last twelve months?
AOS compared to adjacent categories
The important rows are the last two. How many people you can hire and train is what limits both incumbent categories. Consolidating them into a single system is a real improvement (fewer products, cleaner data, better visibility) but it does not touch that limit. Consolidation makes a staffed operation more efficient. An AOS changes what the staff are for.
The AOS maturity model
Autonomy is a property of a workflow rather than of an organization. A single imaging center will usually sit at different levels for different processes at once.
Level 0, manual. A person performs the task in a system of record. The software's job is to store the result.
Level 1, assisted. The software pre-fills, suggests or flags. A person still performs and owns every transaction. Most "AI-powered" imaging software sits here.
Level 2, supervised. An agent performs the transaction end to end and a person reviews before release. Throughput rises sharply, so a scheduler who processed ten orders an hour processes fifty, but headcount is still coupled to volume.
Level 3, agentic. An agent performs and completes the transaction. No person is in the routine path. People are in the exception path, and increasingly in the design path, building and tuning and supervising the operation rather than executing it.
Most imaging organizations are at Level 0 or Level 1 today, whatever their software is marketed as. Level 3 also arrives workflow by workflow: usually document intake first, then eligibility, then scheduling, with prior authorization last because payer behavior is the least predictable input in the whole process. Any vendor claiming Level 3 across the board on day one is describing an ambition rather than a deployment.
What an AOS is not
- It is not a PACS or a reading tool. An AOS has no role in image storage, viewing or interpretation. It stops when the patient enters the scanner.
- It is not diagnostic AI. Most AI investment in radiology addresses detection and interpretation, and an AOS addresses none of it. The two are complements and do not compete for the same problem, though they frequently compete for the same budget.
- It is not, by definition, a RIS replacement. An AOS may operate on top of an existing RIS or subsume its functions, and both are valid deployments. Either way the operational work moves into the AOS, and whatever remains of the RIS becomes a store of record rather than a place where work happens.
- It is not RPA. Robotic process automation replays a recorded sequence of steps and breaks when the screen changes. An agent interprets intent and adapts. The difference becomes obvious the first time a payer redesigns its portal.
- It is not a chatbot. A conversational interface may be one surface of an AOS, but a system that answers questions without completing transactions fails test one.
How to evaluate an AOS
Eight questions worth putting to any vendor in this category, including in an RFP where the answers can be held to.
- What percentage of each workflow completes with no human touch today, in production, at a customer of our size? Ask for the number by workflow rather than in aggregate.
- What is your exception rate, and what is the trend? A vendor who cannot state it is not measuring the thing that governs the value.
- What happens when a payer or referrer has no API? The answer reveals whether the system can operate in the real world or only in an integrated one.
- How are we charged: per seat, per transaction, or per outcome? Seat-based pricing in this category signals a vendor who still assumes staff.
- What is the time to first fully autonomous workflow, as opposed to time to go-live? These are very different dates.
- Who is accountable when the system gets it wrong, and what is the audit trail? Ask to see a real one.
- What happens to our data, and can we leave with it in a usable form?
- Is the vendor also an operator of imaging centers? If so, understand clearly what governance separates your operational data from a competitor's commercial interest. This is a reasonable question, and a straightforward vendor will have a straightforward answer.
Origin of the term
The term Agentic Operations System was proposed by Alpha Nodus in 2026 to name a category that had begun to exist in practice before it had a name. We have an obvious commercial interest in the category, and we would rather state that plainly than pretend to neutrality.
We also think the category is bigger than any one vendor, and we would consider it a good outcome if others adopted the term, competitors included. Categories are more useful than acronyms. If the five tests above turn out to be the right tests, they will be applied to us too, and they should be.
This definition is versioned and will be updated as the category develops. Disagreements, corrections and additions are welcome: aos@alphanodus.com.
Gravity is an Agentic Operations System.
It runs the operation end to end for diagnostic imaging organizations, autonomously, on top of or in place of an existing RIS.
Before the study: document and referral intake, scheduling, eligibility verification, prior authorization, and patient estimates.
After the study: claim submission, remittance posting, collection from payers and third-party liability, refunds, and patient statements.
Between studies: recall and screening follow-up, including breast and lung cancer screening adherence, and referring-provider engagement.
See it run against the five tests
Agentic Operations System (AOS). Definition v1.0, August 2026. alphanodus.com/aos
