Cair Health

Cair's agents interpret clinical documentation and payer requirements to prepare, submit and repair insurance claims. Chloe checks claims against notes, eligibility and coding rules; Dennis analyzes remittances and prepares corrected submissions; Paige makes payer calls. Clark adds coding and chart review, including checks for diagnosis alignment, modifiers, telehealth requirements and coverage policies. The platform also handles eligibility requests and payment posting.

Its policy processing work extracts requirements from more than 150,000 payer documents, according to Cair. Customer rules guide the automated work, and billing staff receive worklists. Language interpretation and generation connect these functions throughout the claims lifecycle.

Customer rules and billing worklists provide controls over the automated workflow. Teams can specify modifier preferences or documentation requirements, assign staff and use Clark's chart review reports before billing. Dennis can prepare corrected claims and involve Paige for payer follow up. Cair also promises that every claim will be compliant and ready for reimbursement.

Billing teams receive both automated submissions and reports they can review, including checks for bundling, authentication and coverage requirements. No rule defines when an uncertain claim must stop for a person, leaving the boundary between automated submission and mandatory review unspecified.

Chloe uses a language model to interpret claim inputs, and AI extracts and standardizes requirements from payer policy PDFs. Policy processing includes restrictions on surgical modifiers and the reimbursement rules attached to them, illustrated with Highmark's coverage guidance. Clark produces separate reports for coding alignment, bundling, telehealth, documentation and coverage requirements.

Customer rules operate alongside those learned functions, while Dennis analyzes remittances and prepares revised claim transactions. Model identity, training data, version history and update practice are unspecified. The described workflow connects language interpretation to claim preparation without exposing the model configuration used for a particular billing team.

Outside suppliers support hosting, communications, analytics, security and AI processing. Suppliers handling PHI are subject to business associate or subcontractor agreements where required, and customer instructions govern exchanges with record systems, practice management platforms, clearinghouses and payers. Language model agents process clinical notes, claims and payer interactions, but their providers and the full subprocessor chain are unnamed in the accessible service terms.

Restrictions on training outside foundation models have contractual exceptions, making downstream use dependent on the agreement. The trust center has restricted public access; any further party list or provider specific retention commitments there remain unknown.

Cair reports use across more than 100 practices, 90% claims pipeline automation, a charge lag of one day and a gross collection rate above 99%. The company separately counts more than 15 partners across over 30 states. These figures lack a measured population, observation period and comparison method. Robert Rupp, a revenue cycle consultant at a New Jersey federally qualified health center, provides a testimonial about billing accuracy.

Clark's current chart review checks include coding alignment, modifiers and documentation requirements, with examples from orthopedics and mental health. Adoption counts and a billing consultant's endorsement do not measure the agents' error rate.

Cair's marketing says language models do not store, share or train on customer data. Its service privacy policy qualifies the training commitment: PHI is not used for general purpose or outside foundation model training unless the customer agreement, BAA or law expressly permits it. Operational data includes notes, claims, payer conversations and generated coding or denial analyses. Retention follows contracts, customer instructions and legal obligations, without a fixed schedule.

Security incidents are investigated and communicated to customers under applicable agreements. Model specific guardrails, deidentification practices and the handling of an incorrect generated claim are not detailed.

The service privacy policy explicitly places Cair in the role of business associate or subcontractor when it handles protected health information for a customer. Customer instructions and the applicable agreement govern that processing, and the business associate agreement takes precedence over the general privacy policy for PHI. The policy covers the software, integrations and support operations, including claim data, clinical records, coding documentation and payer communications.

It also describes minimum necessary access and agreements with subcontractors handling PHI. All subscription plans carry the HIPAA posture. The actual agreement and its contractual scope are not available for review before contracting.

SOC 2 compliance is claimed for Cair's own platform, and all subscription plans operate under SOC 2 controls. Service safeguards include authentication, access controls, encryption, audit logging, workforce training, monitoring and incident response. The privacy terms describe investigation, containment and remediation of security incidents, with customer notification governed by PHI agreements and applicable obligations. A dedicated trust center accompanies these commitments.

Its public access is restricted, leaving the report type, audit period and covered environment unknown. The company makes the SOC statement for its service, while the actual attestation remains separate from the list of technical controls.

The agents perform insurance and payment administration: checking eligibility, reviewing documentation for billing requirements, preparing claims, managing denials and posting remittances. Clinical notes are inputs to coding and reimbursement checks, including whether documentation supports a billed service or meets a payer coverage policy. The privacy policy explicitly excludes medical advice, diagnosis, treatment and care from Cair's role.

Clark's chart review is presented as a prebilling function, with reports on documentation, authentication and coding alignment. The product carries no medical device claim. Its positioning stays with administrative use of existing clinical information rather than generation of a treatment decision.

Custom rules let organizations express local billing requirements, while chart review reports identify coding and documentation issues before submission. The policy processing workflow standardizes payer guidance so claims can be checked against the relevant requirements. These controls address day to day billing work. An accuracy testimonial spans any specialty or service type, without subgroup results.

A security incident process addresses information protection separately from model quality. There is no model governance framework or evaluation method for the agents' decisions across specialties, payer populations or patient groups. Orthopedic coding and mental health documentation examples illustrate supported tasks rather than tested differences in performance.

Billing staff can review Clark's reports, inspect flagged documentation issues and configure organization specific rules before claim submission. These controls create opportunities to challenge a coding or coverage suggestion inside the workflow. Support includes a dedicated Slack channel on Growth and a success team on Enterprise. Patient requests to amend medical information generally go to the healthcare organization, with Cair assisting under its agreement.

That is distinct from a customer remedy for an incorrect agent output. Pricing is a monthly minimum with usage, without a collection success fee, and no output warranty or reimbursement guarantee is stated.

APIs accept raw notes, X12 EDI files and FHIR resources, with direct record system API connections also offered. Cair reports more than 80 integrations and describes both existing connectors and connections built for a customer. Implementation includes synchronizing claims and clinical data and beginning EDI enrollments. Clark's chart review can be used through the platform or a dedicated endpoint.

Core includes an EMR integration and clearinghouse connection, while Enterprise supports multiple systems of each type. No record system is named with a production connection or directional specification, so the integration count does not identify which connection a particular organization can use.

Users access a hosted platform with accounts, a sandbox and API connections to their clinical and billing systems. Implementation centers on synchronizing claims and clinical records into Cair and configuring the team's workflow. The company targets US healthcare organizations, but its service privacy policy permits information to be stored or processed in other jurisdictions where Cair or its suppliers operate. A US headquarters therefore does not determine the processing location.

Hosting region, tenant isolation and model processing geography are unspecified in the accessible service terms. The linked trust center has restricted public access, leaving any additional deployment commitments there unknown.

Core, Growth and Enterprise are subscription packages with a monthly minimum and usage and volume determining the quote. All six agents are included, and Cair takes no share of collections. Core includes unlimited seats, an EMR connection, clearinghouse connectivity, reporting and task management. Growth adds support for multiple states and group NPIs, custom analytics and a dedicated Slack channel.

Enterprise adds multiple record systems and clearinghouses, custom agents and onsite support. A free sandbox precedes a production engagement. Integration and onboarding charges are generally waived within the chosen plan, but minimum amounts and usage rates are not stated.

Billing companies, digital health businesses, specialty EMRs and provider organizations use the platform for insurance administration. Coding covers professional, institutional, dental and case rate claims, while the chart review examples address orthopedic modifiers and mental health documentation. The company reports more than 100 practices and activity in over 30 states. These figures describe reach rather than performance within a specialty.

Its own product lineup combines eligibility, claim submission, denials, payer calling and payment posting, allowing teams to automate several stages of reimbursement. Results by specialty, payer type or organizational setting are not available.