Healthcare Revenue Cycle & AI Agent Glossary
This glossary defines the revenue cycle, claims, contact center, and AI terms that come up when healthcare teams evaluate automation. Each entry gives a plain-English definition and, where it helps, links to a deeper Flexbone page or article. Use it as a quick reference or a shared vocabulary across billing, operations, and technical teams.
Prior authorization
A payer's requirement that a provider get approval before delivering certain services, drugs, or procedures. Without an approved authorization on file, the resulting claim is often denied. See our prior authorization automation approach for how the calls and portal work get handled.
Eligibility verification (270/271)
Confirming a patient's active coverage and benefits with a payer before a visit. The X12 270 is the request a provider sends and the 271 is the response with coverage and cost-sharing details. Read more on eligibility verification and on automating 270/271 versus portals.
Denial management
The work of identifying, correcting, appealing, and preventing claims a payer refuses to pay. Strong denial management recovers earned revenue and feeds root causes back upstream. See AI denials management for how appeals get drafted and worked.
CARC and RARC codes
Claim Adjustment Reason Codes and Remittance Advice Remark Codes appear on a remittance to explain why a claim line was adjusted or denied. CARC states the reason for the adjustment; RARC adds supplemental detail. Reading them correctly is the first step in denial follow-up.
Clean claim rate
The share of claims that are accepted and paid on first submission, without edits, rejections, or manual rework. A higher clean claim rate means faster payment and less staff time spent reworking claims. It is a leading indicator of front-end data quality.
Days in A/R
The average number of days it takes to collect payment after a service is delivered. It is calculated from total accounts receivable divided by average daily charges. Rising days in A/R usually signals slower payer response, denials, or a backlog in follow-up.
ERA and EOB (835)
The Electronic Remittance Advice, sent in the X12 835 transaction, tells a provider how a claim was paid or adjusted. The Explanation of Benefits is the human-readable version a patient or provider reads. Both carry the CARC and RARC codes used in reconciliation.
Claim (837)
The standard electronic healthcare claim a provider submits to a payer, transmitted in the X12 837 format. It carries patient, provider, diagnosis, and service-line detail. Institutional and professional claims use different 837 variants.
Coordination of benefits (COB)
The rules that decide which payer pays first when a patient has more than one insurance plan. Getting COB right prevents denials and rework, since a claim sent to the secondary payer before the primary will usually be rejected.
Timely filing
A payer's deadline for submitting a claim after the date of service. Deadlines vary by payer and contract, and a claim filed after the limit is typically denied with little recourse. Tracking filing windows is a core revenue-protection task.
Underpayment
When a payer reimburses less than the contracted or expected rate for a service. Underpayments are easy to miss because the claim still shows as paid. Catching them requires comparing remittances against the fee schedule in the payer contract.
Charge capture
Recording every billable service a provider delivers so it can be coded and billed. Gaps in charge capture mean revenue is simply never billed. It links the clinical encounter to the claim that follows.
Payment posting
Applying payer and patient payments, adjustments, and denials from remittances to the correct patient accounts. Accurate posting keeps the accounts receivable clean and surfaces denials and underpayments for follow-up.
Credentialing
Verifying a provider's qualifications and enrolling them with payers so their services can be billed and reimbursed. It involves primary-source verification and, for many payers, CAQH profiles. Delays keep a new provider from being paid. See AI for credentialing and enrollment calls.
Coverage discovery
Finding active insurance a patient did not report, often on self-pay or unbilled accounts, so the right payer is billed. It reduces write-offs and bad debt. Our patient access intelligence work covers this front-end territory.
Clearinghouse
An intermediary that validates, formats, and routes electronic claims and remittances between providers and payers. Clearinghouses run edits that catch errors before a claim reaches the payer, which raises the clean claim rate. Availity is a widely used example.
First call resolution (FCR)
The share of contacts resolved on the first interaction, without a callback, transfer, or repeat contact. High FCR usually tracks with better patient experience and lower cost. See our guide to improving FCR in healthcare.
Average handle time (AHT)
The mean time an agent spends on a contact, including talk time, hold time, and after-call work. AHT is a staffing and efficiency measure, not a quality measure on its own. See how to calculate and reduce AHT.
Average speed of answer (ASA)
The average time a caller waits in queue before an agent answers. ASA is a core service-level measure and rises quickly when staffing falls short of call volume. See our explainer on average speed of answer.
IVR containment
The share of calls fully handled inside the interactive voice response system without transfer to a live agent. Higher containment lowers cost, but only when the contained calls are actually resolved. See IVR containment rate.
Call abandonment rate
The share of inbound calls where the caller hangs up before reaching an agent. It rises with long hold times and signals lost appointments and revenue. See call abandonment rate for how to measure and reduce it.
Occupancy vs utilization
Occupancy is the share of logged-in time an agent spends handling contacts; utilization is the share of paid time spent on customer work. The two are often confused. See occupancy versus utilization.
Schedule adherence
How closely agents follow their assigned schedule, including start times, breaks, and queue availability. Poor adherence undermines even a well-built staffing plan. It is a central workforce management measure, covered in our workforce management guide.
After-call work (ACW)
The tasks an agent completes right after a contact ends, such as notes, coding, or follow-up, before taking the next call. ACW is part of handle time and a common target for automation. See after-call work.
No-show rate
The share of scheduled appointments where the patient neither arrives nor cancels in advance. No-shows waste provider capacity and revenue. See how to calculate no-show rate for the formula and drivers.
Voice AI agent
Software that answers or places phone calls, understands speech, follows a defined workflow, and acts in connected systems such as the EHR. It differs from a simple IVR by handling open-ended conversation and completing tasks. See AI for healthcare calls.
Browser agent
An AI agent that operates web applications through the browser interface, clicking and typing the way a person would. This lets it work with payer portals and legacy tools that offer no API. See browser agents without APIs.
RPA vs AI agents
Robotic process automation follows fixed, scripted steps and breaks when a screen or workflow changes. AI agents interpret context and adapt, so they handle the variation and exceptions RPA cannot. See AI agents versus RPA versus workflow automation.
HIPAA
The U.S. law governing the privacy and security of protected health information. Vendors that touch that data must sign a business associate agreement and follow the Privacy and Security Rules. See our security and compliance overview.
EHR and PMS
The electronic health record holds clinical data, while the practice management system handles scheduling, registration, and billing. They often work together and are the core systems AI agents read from and write back to. See our EHR integrations.
Frequently asked
What is the healthcare revenue cycle?
The healthcare revenue cycle is the full financial process for a patient encounter, from scheduling and eligibility verification through coding, claim submission, payment posting, and denial follow-up. Each step has its own vocabulary and metrics, which is what this glossary defines so billing, operations, and technical teams share the same language.
What is the difference between RPA and an AI agent?
Robotic process automation follows fixed, scripted steps and breaks when a screen or workflow changes. An AI agent interprets context, reads unstructured information, and decides what to do next, so it handles the variation and exceptions that scripted automation cannot. Our note on AI agents versus RPA goes deeper.
What does eligibility verification mean in the 270/271 transaction?
Eligibility verification confirms a patient's active coverage and benefits before a visit. The 270 is the standardized X12 request a provider sends to a payer, and the 271 is the response that reports coverage, plan details, and cost-sharing such as copay and deductible. See our page on eligibility verification.
Are AI voice agents HIPAA compliant?
They can be when the vendor signs a business associate agreement and handles protected health information under the HIPAA Privacy and Security Rules, with encryption, access controls, and audit logging. Compliance depends on how a specific system is built and operated, not on the category itself.
Put these terms to work
If you are mapping any of this vocabulary to real workflows, our team can walk through where AI agents fit in your revenue cycle and contact center.