For patient-access, health-center operations, Medicaid, managed-care, revenue-cycle, billing, finance, compliance, and information-technology leaders responsible for FQHC or rural health clinic encounters from eligibility through base payment, supplemental payment, and final reconciliation.
Reconcile Every FQHC and Rural Health Clinic Encounter Through Final Payment
Give each encounter one reviewable administrative record from coverage evidence and sliding-fee assessment through provider and site validation, claim or encounter submission, remittance, Medicaid managed-care supplemental payment, Medicare Advantage supplemental payment where applicable, variance resolution, and close. The record shows what was received, what remains expected, which rule set applies, how confident each match is, and which qualified person owns the next decision.
QuickIntell organizes administrative evidence and work; it does not determine clinical necessity, eligibility, coverage, coding, encounter qualification, prospective-payment or all-inclusive-rate treatment, payer order, contract meaning, payment entitlement, patient responsibility, or the amount a payer or agency owes. Authorized patient-access, coding, billing, Medicaid, Medicare, managed-care, finance, compliance, privacy, clinical, and legal professionals retain those decisions and can stop, correct, or override the workflow.
A paid claim can still be an unreconciled encounter
Before: patient access keeps eligibility and sliding-fee evidence, billing submits the claim, a managed-care team sends encounter files, finance posts remittances, and a separate analyst compares state or plan supplemental-payment reports. Each group can finish its task while the encounter remains financially incomplete. After: the organization can trace one encounter across those systems, see the base and supplemental components separately, preserve the rule and rate version used, and route uncertainty to the right human before a variance is adjusted or closed.
Eligibility, benefits, and sliding-fee status become one answer
An electronic eligibility response can establish that a payer returned information for a date and product; it does not prove network status, authorization, encounter eligibility, final coverage, payment, or patient cost. A Health Center Program sliding-fee assessment uses a different authority and evidence path, and those HRSA requirements do not automatically apply to every rural health clinic.
Operational consequence
Staff may communicate an amount too early, skip a required review, or rebuild the same evidence after a denial. Revenue-cycle leaders cannot tell whether the problem began with stale coverage, an incomplete board-approved process, a payer rule, or a later claim decision.
FQHC and RHC payment logic is flattened into a clinic flag
Medicare uses an FQHC prospective payment system and an RHC all-inclusive-rate framework, while Medicaid FQHC and RHC payment follows federal requirements plus the applicable state plan, managed-care contract, and approved alternative methodology when used. Site type, enrollment, service, provider, date, and payer path all matter.
Operational consequence
A rule or rate can be applied to the wrong entity or period. The resulting variance may look like a payer underpayment even when the source record, site designation, covered encounter definition, or expected-payment logic needs qualified review first.
The base payment is mistaken for the complete payment
A managed-care remittance can close the plan claim while a state Medicaid supplemental-payment workflow remains open. Medicare Advantage supplemental-payment instructions for contracted FQHCs are a separate federal path and should not be copied to Medicaid, commercial coverage, or an RHC without current authority.
Operational consequence
Open supplemental amounts disappear into ordinary accounts receivable, or a team creates a duplicate expected amount. Finance then spends close cycles deciding whether an encounter is missing, excluded, already settled, offset, recouped, or simply waiting for a different reporting period.
Claim, encounter, remittance, and agency files do not share a clean key
One source may identify a visit, another a claim, another a remittance line, and another an aggregate or detail supplemental-payment record. Corrected claims, voids, replacements, split services, multiple locations, behavioral or dental activity, and changing payer identifiers make a simple exact match unreliable.
Operational consequence
Analysts use amount-and-date guesses or maintain private crosswalks. A weak match can close the wrong encounter, leave the real one outstanding, create duplicate follow-up, or erase the evidence needed to explain a later adjustment or audit sample.
Exceptions are resolved in messages instead of a controlled ledger
A payer, state agency, clearinghouse, credentialing team, coder, or clinic leader may answer one part of the variance. If the evidence, effective date, decision owner, and downstream impact are not attached to the encounter, the same exception returns during rebilling, recoupment, rate updates, grant reporting, or Uniform Data System preparation.
Operational consequence
Work is repeated, institutional knowledge stays with one person, and leaders cannot separate true collection work from data-quality, enrollment, coding, contract, or reporting work. The organization also loses a defensible record of why a human released, held, adjusted, or closed the encounter.
A named agent team with visible decision boundaries
Each agent handles a defined part of the encounter, eligibility, and wrap-payment reconciliation workflow. Confidence signals and human escalation remain visible rather than being hidden behind an automation label.
Eligibility Evidence Agent
This AI agent assembles coverage, product, service-date, provider, site, referral, and authorized sliding-fee evidence into a time-stamped intake record. It identifies missing or conflicting inputs but does not determine eligibility, coverage, network participation, authorization, patient responsibility, or sliding-fee eligibility.
Inputs
- Authorized payer eligibility and benefit responses with source and inquiry time
- Scheduled service, service date, location, rendering discipline, and responsible clinic entity
- Current provider, site, payer-product, referral, and enrollment reference tables
- Board-approved sliding-fee policy, current schedule, and authorized assessment status where the Health Center Program requirements apply
- Known other-coverage or third-party-liability indicators from approved operational sources
Checks
- Payer product, service date, clinic entity, site, and provider context align
- Eligibility, benefit, network, referral, authorization, and payment remain separate states
- The eligibility source is current for the organization's approved lookback and recheck policy
- Sliding-fee evidence is not inferred from payer eligibility or reused outside its approved period
- FQHC, Health Center Program awardee or look-alike, and RHC designations are not treated as synonyms
- Conflicting other-coverage or liability indicators create a human review hold
Outputs
- Source-linked intake evidence summary with effective dates
- Missing, stale, conflicting, or unmatched evidence queue
- Human-readable separation of coverage, sliding-fee, and payer-order questions
- Confidence method
- Confidence reflects source provenance, timestamp freshness, exact payer-product and service-date agreement, provider and site match, and consistency across authorized reference tables. It is an evidence-completeness signal, not a probability of coverage, payment, or patient responsibility.
- Low-confidence action
- A stale response, unmatched product, missing provider context, disputed clinic designation, incomplete sliding-fee record, or possible other payer keeps the affected question open. The agent shows the specific gap and does not copy a prior encounter's answer.
- Human escalation
- Patient access, financial counseling, payer enrollment, managed care, privacy, and qualified billing staff verify the exact coverage and approved assessment path. Health-center leadership and counsel interpret Health Center Program obligations; clinical teams decide whether care proceeds regardless of unresolved administration.
Encounter Definition Agent
This AI agent organizes scheduled, documented, coded, and submitted activity into a candidate FQHC or RHC encounter record. It surfaces missing evidence and conflicting service groupings but cannot decide whether a visit qualifies, select a code, establish medical necessity, or release a claim or encounter submission.
Inputs
- Authorized scheduling, registration, encounter, service, and charge metadata
- Human-approved coding, revenue-code, modifier, bill-type, and claim instructions
- Clinic entity, site, provider enrollment, taxonomy, and effective-date references
- Payer-specific encounter definitions and current state, plan, or Medicare source references
- Correction, void, replacement, split-service, behavioral, dental, care-management, and telehealth indicators
Checks
- Entity, site, provider, service date, payer, and claim route agree
- FQHC PPS, RHC AIR, Medicaid PPS or APM, and ordinary fee-schedule paths remain distinct
- Multiple services are not combined or split without a human-approved rule
- Corrected, voided, replacement, and original records preserve their lineage
- Behavioral, dental, care-management, and telehealth services use the applicable current authority rather than a generic clinic rule
- Clinical documentation sufficiency and coding decisions remain with qualified humans
Outputs
- Candidate encounter control record with source lineage
- Missing documentation, enrollment, coding, and grouping exception queue
- Human-approved submission handoff with the applicable rule-set reference
- Confidence method
- Confidence uses agreement among the designated source systems, clinic and site identity, provider effective dates, service grouping, human-approved coding instructions, and payer rule version. It never estimates medical necessity, coding correctness, claim acceptance, or payment.
- Low-confidence action
- If the service grouping, site designation, provider enrollment, coding instruction, or encounter definition is ambiguous, the record remains draft and cannot advance as reconciliation-ready. The agent identifies the competing evidence and affected downstream records.
- Human escalation
- Qualified clinicians confirm clinical documentation, certified coding professionals approve codes and grouping, enrollment staff confirm provider and site status, and authorized billers approve the claim or encounter submission. Compliance or legal reviewers handle unresolved rule applicability.
Payer Path and Rate Agent
This AI agent attaches the candidate encounter to the applicable Original Medicare, Medicare Advantage, Medicaid, commercial, self-pay, or liability work path and retrieves the human-approved rate or methodology reference. It does not interpret a contract, select a rate, decide payer order, or calculate an enforceable amount owed.
Inputs
- Human-approved encounter record and clinic designation
- Current Medicare FQHC PPS and RHC AIR references maintained by authorized staff
- State Medicaid PPS, APM, managed-care, supplemental-payment, and reporting references
- Executed payer contracts and fee exhibits available to authorized reviewers
- Coverage, other-insurance, liability, and coordination evidence
Checks
- Rate source, entity, site, service, payer product, and effective period align
- Original Medicare, Medicare Advantage, Medicaid fee-for-service, Medicaid managed care, and commercial paths are not merged
- Base claim payment and supplemental-payment expectation remain separate components
- A contract rate is not treated as a government PPS or AIR rate
- A Medicaid state or plan rule is not reused across jurisdictions
- Possible liability, no-fault, workers' compensation, or other coverage is held for qualified payer-order review
Outputs
- Human-reviewable payer-path record with source and effective date
- Candidate base and supplemental-payment component map without autonomous financial action
- Rate-source, contract, jurisdiction, and payer-order exception queue
- Confidence method
- Confidence measures exact alignment of the encounter with the approved payer path, entity and site designation, service scope, effective period, and source hierarchy. It is not an underpayment score, contract interpretation, coverage opinion, or forecast of payer behavior.
- Low-confidence action
- A missing rate exhibit, disputed state methodology, uncertain payer order, plan mismatch, or effective-date conflict prevents an expected amount from being used for close or outreach. The agent preserves each candidate source for human comparison.
- Human escalation
- Medicare and Medicaid specialists, managed-care leaders, contracting, reimbursement, finance, billing, compliance, and legal counsel approve the payer path and rate source. Payers, states, or Medicare contractors answer authoritative questions through approved channels.
Claim and Remittance Match Agent
This AI agent links the encounter to submitted claim or encounter records, acknowledgments, adjudication, remittance, payment-posting, and correction events. It proposes explainable matches and variances but cannot post cash, change a charge, submit a replacement, appeal a decision, or create patient responsibility.
Inputs
- Authorized claim and encounter submissions with acceptance and rejection states
- Electronic and manual remittance records from designated financial systems
- Payment-posting, deposit, adjustment, recoupment, void, and replacement status
- Encounter lineage, payer path, expected components, and human-approved reference amount
- Clearinghouse, payer, state, and internal crosswalks maintained by accountable owners
Checks
- Candidate matches agree on payer, entity, service date, provider, service grouping, and lineage
- Original, corrected, voided, and replacement claims are not counted together
- Claim acceptance, adjudication, remittance, deposit, and reconciliation are separate milestones
- Amount-and-date similarity alone cannot create a high-confidence match
- Denial, adjustment, offset, recoupment, and patient-balance states retain their distinct evidence
- A base remittance does not automatically close a supplemental-payment component
Outputs
- Explainable encounter-to-claim-to-remittance match set
- Unmatched, duplicate, partial, reversed, and conflicting payment queue
- Source-linked variance record for authorized posting, billing, or payer follow-up
- Confidence method
- Confidence combines exact operational keys where available with payer, entity, date, provider, service grouping, amount component, and correction lineage. Every match exposes its reasons; confidence is not a representation that adjudication or posting is correct.
- Low-confidence action
- A many-to-one candidate, incomplete remittance, weak crosswalk, corrected lineage, or amount-only similarity remains unmatched. The agent presents the candidates and forbids automatic close, posting, rebilling, or adjustment.
- Human escalation
- Authorized payment-posting, billing, coding, patient-accounting, clearinghouse, payer, and finance staff approve matches and financial actions. Compliance and legal teams review material duplicate-payment, recoupment, or disclosure questions under established policy.
Supplemental Payment Reconciliation Agent
This AI agent compares eligible human-approved encounter components with state Medicaid managed-care supplemental-payment evidence and applicable Medicare Advantage FQHC supplemental-payment evidence. It finds missing, duplicate, excluded, delayed, or conflicting records but cannot determine entitlement or direct an agency, plan, or clinic to pay.
Inputs
- Human-approved encounter, payer-path, and base-payment records
- Current state Medicaid encounter acceptance and supplemental-payment reports
- Medicare Advantage FQHC claim and supplemental-payment evidence where applicable
- Approved PPS, APM, contract, rate, reporting-period, and exclusion references
- Prior-period settlement, recoupment, correction, and open-variance history
Checks
- The supplemental-payment authority applies to the clinic type, payer, service, and period
- Medicaid and Medicare Advantage supplemental-payment paths remain separate
- RHC records are not forced through an FQHC-only Medicare Advantage instruction
- Base payment, supplemental payment, incentive, grant, patient payment, and unrelated adjustment are not combined
- Reporting period, encounter acceptance, rate version, prior settlement, and correction lineage agree
- An apparent difference is not labeled an underpayment until qualified reviewers validate every component
Outputs
- Encounter-level supplemental-payment status and explainable candidate variance
- Missing, excluded, duplicated, delayed, recouped, and rate-conflict work queues
- Human-approved outreach or correction packet with source history
- Confidence method
- Confidence reflects agreement among applicable authority, clinic and payer type, accepted encounter evidence, base remittance, reporting period, approved rate source, and settlement lineage. It is not a legal entitlement, collectible balance, or guarantee of supplemental payment.
- Low-confidence action
- If the state file is incomplete, the plan record conflicts, the clinic type is uncertain, the rate version is disputed, or a prior-period offset may apply, the variance stays provisional. The agent routes the exact missing evidence without generating a receivable or payer demand.
- Human escalation
- State Medicaid, managed-care, Medicare, billing, reimbursement, finance, contracting, compliance, and legal professionals validate the calculation and approve any report, appeal, correction, receivable, refund, or outreach. External agencies and plans make their own determinations.
Close and Reporting Agent
This AI agent assembles the completed evidence chain, open exceptions, human approvals, aggregate operational measures, and reporting-ready extracts. It does not certify a financial statement, prepare a final UDS submission, close an account, write off a balance, or decide that a compliance obligation has been satisfied.
Inputs
- Encounter, eligibility, payer-path, claim, remittance, supplemental-payment, and exception history
- Human approvals for match, adjustment, correction, outreach, and close
- Approved finance, grant, Uniform Data System, and management-report definitions
- Source-system retention, access, audit, and data-minimization rules
- Non-PHI operational event taxonomy for internal measurement
Checks
- Every closed component has source evidence, a decision owner, and an effective date
- Open payer, rate, coding, enrollment, liability, or patient-balance questions cannot be hidden by aggregate close
- Financial, grant, and UDS extracts use the accountable team's current definitions and reporting period
- Corrections preserve the earlier state instead of overwriting history
- Marketing analytics contain route and CTA context only, never encounter or operational values
- Retention, disclosure, and deletion follow approved organizational policy
Outputs
- Encounter close packet with complete decision and source lineage
- Open-exception aging and ownership view
- Human-reviewable aggregate finance, management, grant, or UDS preparation extract
- Non-PHI workflow measures separated from website analytics
- Confidence method
- Confidence reflects completion of required evidence, human approvals, balanced component states, source-system agreement, and report-definition validation. It does not certify accounting, audit, grant, UDS, legal, privacy, or compliance conclusions.
- Low-confidence action
- An open exception, missing approval, unbalanced component, definition conflict, or unclear retention rule prevents final close or report release. The agent shows the responsible owner and the evidence still required.
- Human escalation
- Finance, revenue cycle, grant administration, UDS reporting, compliance, privacy, security, internal audit, health-center leadership, and legal counsel approve close, reporting, retention, correction, and disclosure. Designated HRSA and payer contacts resolve external reporting questions.
The operating sequence, evidence by evidence
The sequence separates agent work from accountable human checkpoints so teams can see what moves forward, what stays pending, and why.
Enrollment, contracting, and reimbursement
Lock the clinic, payer, and rule identity
Start with an effective-dated catalog of legal entity, FQHC or RHC designation, Health Center Program status where relevant, site, provider, payer product, network, claim route, Medicaid jurisdiction, and approved payment source. This prevents a later match from using a rule that belongs to another clinic, plan, state, or period.
Agent actions
- Compare entity, site, provider, payer, and effective-date references
- Separate FQHC, Health Center Program, and RHC designations
- Surface missing enrollment, contract, or rate authority before intake
Evidence produced
- Effective-dated clinic and payer control table
- Approved source hierarchy for each payer path
- Enrollment, contract, and designation exception queue
Human checkpoint: Enrollment, contracting, reimbursement, compliance, and legal owners approve the control table and source hierarchy. No agent infers an entity's designation or payer participation from a name, historical claim, or another site's record.
Patient access and financial counseling
Capture eligibility and financial-assistance evidence
Collect current payer evidence for the planned service and, where applicable, the authorized sliding-fee assessment state under the health center's board-approved process. Keep benefit, network, referral, authorization, sliding-fee, other-coverage, and patient-communication questions separate.
Agent actions
- Time-stamp and match authorized eligibility responses to the exact payer product
- Check provider, site, service-date, referral, and other-coverage context
- Route stale, conflicting, or incomplete evidence without estimating patient cost
Evidence produced
- Source-linked intake evidence record
- Recheck and missing-evidence work queue
- Human-approved patient communication status
Human checkpoint: Patient access, financial counseling, managed care, and privacy staff confirm the applicable evidence and communication. Qualified leaders decide sliding-fee eligibility under current policy; unresolved administration does not authorize delaying urgent or clinically necessary care.
Clinical operations, coding, and billing
Define and release the encounter
Assemble the service into a candidate encounter with the correct entity, site, provider, date, grouping, and payer route. Behavioral, dental, care-management, referral, and telehealth activity remains visible rather than being forced into a generic visit pattern.
Agent actions
- Compare scheduled, documented, coded, charged, and submitted service metadata
- Trace correction, void, replacement, split, and combined-service lineage
- Create a blocking exception for missing documentation, coding, enrollment, or grouping authority
Evidence produced
- Human-approved encounter control record
- Claim or encounter submission instructions with source version
- Coding, documentation, grouping, and enrollment exception history
Human checkpoint: Clinicians approve clinical documentation, certified coders approve coding and grouping, and authorized billers release the submission. The software cannot decide that a service is a covered encounter or choose a code because other fields appear to match.
Billing and payment posting
Track submission, adjudication, and base payment
Follow the claim or encounter through acknowledgment, rejection, adjudication, remittance, deposit, posting, correction, and recoupment. The workflow records each milestone separately so an accepted encounter or paid claim cannot silently become a final financial close.
Agent actions
- Link submissions and remittances with explainable match evidence
- Preserve original, corrected, voided, and replacement relationships
- Surface unmatched, partial, duplicate, offset, denial, and recoupment states
Evidence produced
- Encounter-to-claim-to-remittance match record
- Base-payment component status
- Human work queue for posting, correction, appeal, or payer follow-up
Human checkpoint: Authorized billing, coding, posting, clearinghouse, finance, and payer staff approve any claim, appeal, adjustment, refund, write-off, or posting action. A match recommendation never moves money or changes patient responsibility on its own.
Medicaid, Medicare, managed care, and finance
Reconcile supplemental payment separately
For an applicable Medicaid managed-care or Medicare Advantage FQHC path, compare the accepted encounter, base payment, approved methodology, reporting period, and supplemental-payment evidence. Keep Medicaid state processes distinct from Medicare Advantage instructions and keep RHC differences explicit.
Agent actions
- Match state, plan, or Medicare supplemental records to the approved encounter lineage
- Compare base and supplemental components without blending incentives, grants, or patient payments
- Explain missing, excluded, duplicate, delayed, offset, recouped, and disputed-rate candidates
Evidence produced
- Supplemental-payment component status
- Provisional variance with source and calculation lineage
- Human-approved correction or outreach packet
Human checkpoint: Qualified Medicaid, Medicare, reimbursement, contracting, finance, billing, compliance, and legal owners determine whether a variance is valid and what action is permitted. The agent cannot establish an amount due or universal wrap rule.
Revenue-cycle operations and compliance
Resolve exceptions without erasing history
Route each exception to the team that can resolve its actual cause: patient access, enrollment, coding, billing, payer, state, contracting, finance, data, privacy, or clinical operations. A correction creates a new state linked to the old one rather than replacing the evidence that supported the earlier decision.
Agent actions
- Assign an owner and required evidence to each open variance
- Track human decisions, overrides, effective dates, and downstream impact
- Reopen dependent components after a rate, eligibility, claim, or encounter correction
Evidence produced
- Owned exception and aging record
- Before-and-after correction lineage
- Approved resolution, outreach, refund, or close evidence
Human checkpoint: The accountable operational and professional owner approves the resolution. Compliance, privacy, security, internal audit, or legal personnel review high-risk financial, disclosure, retention, liability, and systemic-control questions under established policy.
Finance, reporting, and health-center leadership
Close the encounter and prepare aggregate reporting
Close each applicable component only after required evidence and human approval are present. Prepare governed aggregate extracts for finance, management, grant, and UDS work while keeping official reporting definitions, certification, and submission with the authorized teams.
Agent actions
- Verify balanced component states and required human approvals
- Separate closed encounters from open coding, payer, supplemental, liability, and patient questions
- Produce approved aggregate measures without sending operational values to website analytics
Evidence produced
- Encounter close packet with decision lineage
- Open-exception and reconciliation-status summary
- Human-reviewable aggregate reporting preparation extract
Human checkpoint: Finance approves accounting treatment; grant and UDS professionals approve definitions and submissions; leadership accepts operational controls. No agent certifies a report, attestation, financial statement, grant condition, or compliance conclusion.
Separate payer paths instead of one universal rule
Coverage, notice, authorization, and documentation requirements vary by program, plan, jurisdiction, service, and date. These paths show where teams must verify current authoritative instructions.
medicare
Original Medicare: distinguish FQHC PPS from RHC AIR
CMS Claims Processing Manual Chapter 9 separates the RHC all-inclusive-rate system from the FQHC prospective payment system and provides distinct claims and payment instructions. The workflow therefore starts with the enrolled clinic, site, provider, service, and effective date; it never turns a generic clinic encounter into a Medicare payment expectation without qualified review.
- Confirm whether the billing entity and site are enrolled as an FQHC or RHC for the service date.
- Use the current CMS benefit and claims instructions for the exact service, practitioner, location, claim, and period.
- Keep coverage, qualifying visit, coding, deductible or coinsurance, claim adjudication, and final payment as separate states.
- Route cost-report, annual reconciliation, care-management, behavioral-health, preventive, and telehealth questions to qualified Medicare and reimbursement staff.
Human handoff: Medicare enrollment, coding, billing, reimbursement, finance, and compliance professionals approve the applicable FQHC PPS or RHC AIR path and claim action. A Medicare Administrative Contractor or CMS source resolves authoritative payment questions; the software does not interpret coverage or set a rate.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicare advantage
Medicare Advantage: contracted FQHC supplemental-payment path
CMS Claims Processing Manual Chapter 9 includes billing and payment instructions for supplemental payments to FQHCs under contract with Medicare Advantage organizations. That is a defined FQHC path, not a universal rule for every RHC, plan, service, contract, or remittance, and it is not the same as a state Medicaid managed-care wrap process.
- Verify the exact Medicare Advantage product, FQHC contract, service date, provider, site, and applicable CMS instruction.
- Keep the plan's contractual payment, Medicare supplemental component, beneficiary cost sharing, and other coverage questions separate.
- Do not infer a supplemental amount from a plan remittance alone or reuse Medicaid terminology as payment authority.
- For an RHC or an unclear clinic designation, stop and use the applicable current plan, Medicare, and contract sources rather than an FQHC-only instruction.
Human handoff: Medicare Advantage, enrollment, contracting, billing, reimbursement, finance, and compliance professionals approve the claim and supplemental-payment path. The plan and Medicare contractor answer channel-specific questions; legal counsel handles unresolved contract or regulatory interpretation.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicaid
Medicaid: state PPS or APM with managed-care supplemental payment
CMS guidance explains that FQHCs and RHCs receive Medicaid payment under the prospective-payment requirements or an agreed alternative payment methodology that meets the federal conditions. For services furnished through Medicaid managed care, the federal framework includes state supplemental-payment requirements, but each state's approved plan, contracts, encounter process, timing, exclusions, and reconciliation operations still control the real workflow.
- Identify the state, program, fee-for-service or managed-care delivery system, exact plan, clinic type, service, and reporting period.
- Use the current approved state plan or APM, managed-care instructions, encounter acceptance evidence, and payment reports.
- Separate plan base payment, state supplemental payment, incentives, grants, cost sharing, other insurance, and unrelated adjustments.
- Do not copy one state's submission deadline, file format, rate, exclusion, or reconciliation practice into another state.
- Resolve Medicaid third-party-liability and coordination evidence before finalizing payer order or supplemental components.
Human handoff: State Medicaid, managed-care, enrollment, reimbursement, billing, finance, compliance, and legal professionals confirm current requirements and approve calculations, submissions, corrections, disputes, or refunds. The state and plan make their own encounter and payment determinations.
Sources for this path: Centers for Medicare & Medicaid Services, Medicaid.gov
commercial
Commercial coverage: contract and plan terms without a universal wrap
Commercial and employer coverage follows the exact plan, network, provider agreement, service, coding, authorization, and applicable law. Standard eligibility transactions can carry eligibility and benefit information, but the response does not create a universal FQHC or RHC payment methodology and should not be represented as a guarantee of coverage, claim payment, or patient responsibility.
- Match the eligibility response to the exact product, date, provider, site, and service category.
- Verify network, referral, authorization, coding, contract, and claim requirements through approved current sources.
- Treat any negotiated encounter rate, fee schedule, value-based component, or reconciliation term as contract specific.
- Keep a Health Center Program sliding-fee assessment separate from insurer adjudication and subject to applicable legal or contractual restrictions.
Human handoff: Patient access, managed care, contracting, coding, billing, financial counseling, compliance, and legal personnel approve the commercial path and communication. The payer or administrator decides eligibility, coverage, authorization, and payment under its processes; software cannot promise an outcome.
Sources for this path: Centers for Medicare & Medicaid Services, Health Resources and Services Administration
workers comp auto liability
Other coverage, liability, no-fault, and workers' compensation
Medicare coordination-of-benefits rules and Medicaid third-party-liability requirements can change payer order and recovery work when group coverage, liability, no-fault, workers' compensation, or another responsible party is involved. Those sources do not decide causation, legal liability, coverage, or the correct payer for a specific encounter without the current facts and qualified review.
- Capture only authorized indicators needed to route coordination work; do not infer accident or liability from diagnosis or note text.
- Separate Medicare payer order, Medicaid TPL, commercial coordination, legal liability, and patient communication.
- Preserve insurer, state, plan, settlement, recovery, conditional-payment, and appeal evidence in their authorized systems.
- Do not delay emergency or clinically necessary services while administrative payer responsibility remains unresolved.
Human handoff: Coordination-of-benefits, Medicaid TPL, Medicare, payer, risk, billing, compliance, privacy, and legal professionals determine the correct actions. Clinicians address care; insurers, agencies, and courts make decisions within their authority; the agent only organizes evidence and work.
Sources for this path: Centers for Medicare & Medicaid Services, Medicaid.gov
other
Uninsured and sliding-fee path for applicable health centers
HRSA's Health Center Program Compliance Manual establishes sliding-fee and billing-and-collections requirements for Health Center Program awardees, subrecipients, and look-alikes within that authority. Those requirements should not be assumed to govern every RHC merely because it serves a rural community, and the agent cannot replace board-approved policy or a qualified eligibility determination.
- Confirm whether the organization and service fall within the applicable Health Center Program scope and current board-approved policies.
- Use the approved income, family-size, reassessment, documentation, fee-schedule, and sliding-fee process without pulling values into website analytics.
- Keep inability to pay, refusal to pay, payer eligibility, third-party coverage, grant support, and patient financial counseling as distinct questions.
- Apply current legal and contractual restrictions before changing an insured patient's out-of-pocket charge.
Human handoff: Health-center leadership, patient access, financial counseling, finance, compliance, privacy, and legal personnel administer and approve the sliding-fee and collections process. The board retains its authority, and qualified staff handle patient-specific determinations and communications.
Sources for this path: Health Resources and Services Administration, Health Resources and Services Administration
A reconciliation control room with visible human authority
The workflow is designed for explainability before autonomy. Each suggestion exposes its source, effective date, match reasons, missing evidence, confidence basis, and owner. Sensitive data stays inside approved operational boundaries, while website measurement uses a deliberately smaller non-PHI event contract.
Effective-dated source hierarchy
Every rule, rate, contract, clinic designation, state instruction, plan reference, and internal procedure has an owner, jurisdiction, scope, approval state, and effective period. Superseded sources remain reconstructable and cannot silently overwrite earlier encounter decisions.
State separation by design
Eligibility, benefit, authorization, encounter acceptance, base payment, supplemental payment, posting, and close are independent states. FQHC and RHC, Medicare and Medicaid, fee-for-service and managed care, and payer and liability paths cannot share a single undifferentiated completion flag.
Explainable matching and confidence
Every proposed match lists the exact agreements and conflicts across entity, payer, date, provider, service grouping, amount component, and correction lineage. Low confidence creates an exception; amount-and-date similarity alone never closes an encounter.
Separation of duties
The person who maintains a rate or mapping does not automatically approve the related adjustment. Buyer-defined roles control source changes, claim release, posting, supplemental-payment calculations, write-offs, refunds, outreach, reporting, and final close.
Human override with reason
Authorized reviewers can reject, correct, hold, or override an agent recommendation. The record retains the original suggestion, the evidence available at the time, the human decision and reason, the effective date, and any dependent work reopened by the change.
Non-PHI measurement boundary
GA4 may receive only the approved canonical route, page family, specialty slug, workflow slug, content cluster, CTA label, and CTA location. Search Console review uses aggregate clicks, impressions, CTR, average position, and query themes; patient, provider, payer, eligibility, encounter, claim, amount, payment, and portal values are prohibited.
- Human authority
- Patient-access, financial-counseling, enrollment, clinical, coding, billing, reimbursement, Medicaid, Medicare, managed-care, finance, grant, UDS, compliance, privacy, security, audit, and legal owners retain authority in their domains. Agents prepare evidence and work queues; they do not make clinical, coverage, coding, contractual, financial, legal, reporting, or patient-responsibility decisions.
- Audit trail
- The encounter record retains source identifiers, received times, effective periods, normalized matches, confidence reasons, missing evidence, queue transitions, human decisions, overrides, correction lineage, outbound actions, and close approvals. Access and changes are attributable under the buyer's approved identity and retention controls.
- Data boundary
- Production data is limited to the minimum necessary for the approved administrative purpose and stays within contracted, access-controlled systems and channels. De-identified or synthetic data is used for demonstrations when possible. PHI, operational identifiers, amounts, payer responses, and portal credentials never enter source code, sales content, GA4, Search Console, or DataForSEO evidence.
Connect the evidence chain without replacing the source systems
QuickIntell can work through validated APIs, standard transactions, secure files, approved messages, reports, or controlled manual review. The implementation names one system of record for each fact, proves identity and correction handling, and writes back only after authorization. No connection to a particular EHR, payer, clearinghouse, state portal, accounting platform, or HRSA system is implied by this page.
EHR, practice-management, and scheduling systems
Information in scope
Authorized entity, site, provider, appointment, encounter, service, documentation-status, charge, correction, and workflow metadata needed to assemble the administrative encounter record.
Boundary
The clinical record remains authoritative. QuickIntell does not create clinical facts, alter notes, decide medical necessity, choose codes, schedule care, or release a charge without the designated human and source-system controls.
Eligibility, payer, portal, and clearinghouse channels
Information in scope
Approved eligibility and benefit responses, network and authorization states, claim or encounter acknowledgments, rejections, status, and related provenance available through permitted channels.
Boundary
Portal credentials and payer secrets are never copied into content or analytics. Each channel requires authorized access, security review, terms review, monitoring, and a fallback process; a response is not a coverage or payment guarantee.
Claim, encounter, and remittance feeds
Information in scope
Submitted records, correction lineage, acknowledgments, adjudication, remittance, adjustments, recoupments, and posting states from the organization's designated billing and financial sources.
Boundary
The workflow proposes matches and exceptions. Authorized billing, coding, posting, and finance staff retain control over claims, adjustments, refunds, write-offs, deposits, and patient balances.
State Medicaid and managed-care reconciliation sources
Information in scope
Permitted encounter acceptance, base-payment, supplemental-payment, rate-period, exclusion, correction, settlement, and reporting evidence for the specific jurisdiction and plan.
Boundary
Availability and format vary by state and payer. A validated file or interface does not authorize QuickIntell to interpret the state plan, calculate a legal entitlement, submit a report, or contact an agency without human approval.
Finance, general-ledger, and payment-posting systems
Information in scope
Approved posting status, deposit grouping, account mapping, reconciliation period, adjustment, refund, recoupment, and close evidence needed to compare administrative and accounting states.
Boundary
Finance remains the accounting authority. The agent does not post cash, create a receivable, journal an amount, certify a reconciliation, or determine revenue recognition or collectability.
Enrollment, contracting, rate, and policy repositories
Information in scope
Effective-dated clinic designation, site and provider enrollment, payer product, contract, approved rate source, state instruction, standard operating procedure, and human owner.
Boundary
Only authorized owners approve source hierarchy and interpretation. Draft, expired, unsigned, superseded, or out-of-jurisdiction references remain visible and cannot silently drive the workflow.
Grant, UDS, and management-reporting workspaces
Information in scope
Human-approved aggregate encounter, payer, service, financial, staffing, and exception measures prepared under the current report definitions and reporting period.
Boundary
HRSA guidance and the accountable reporting team remain authoritative. QuickIntell does not certify, attest, or submit UDS, grant, cost-report, or financial data, and it does not treat every RHC as a Health Center Program reporting entity.
Model labor capacity with your own encounter volume
Use a transparent planning equation: monthly reconciliation cases × administrative minutes saved per case ÷ 60 × loaded labor rate. In this explicitly illustrative scenario, the time is limited to evidence gathering, cross-system matching, and queue preparation; it does not assume more payment, fewer denials, better compliance, faster care, or reduced staffing.
Monthly reconciliation cases
600 encounters
Illustrative input only. Replace it with the number of encounters that actually require eligibility-to-payment reconciliation in the scoped clinic, payer, and reporting period; do not use total visits if only a subset enters this workflow.
Administrative time saved per case
8 minutes
Illustrative input only. Measure the buyer's baseline and controlled pilot for comparable cases, including exception time. Count only verified administrative minutes removed from evidence gathering, matching, and queue preparation.
Loaded labor rate
38 USD per hour
Illustrative input only. Replace it with the buyer-approved loaded hourly cost for the actual staff mix. This is not a QuickIntell price, wage claim, reimbursement rate, or estimate of collectible revenue.
Formula
600 reconciliation cases × 8 minutes saved ÷ 60 × $38 loaded labor rate = $3,040 in illustrative monthly labor capacity.
Illustrative result
$3,040 of illustrative monthly labor capacity for reassignment to exceptions, payer follow-up, patient support, or reporting—not cash, revenue, savings, headcount reduction, or a guaranteed result.
Illustrative planning model—not a customer result, guarantee, or quote.
Illustrative workflow examples
These examples explain process behavior. They are not customer stories, measured outcomes, clinical advice, or promises of coverage.
Illustrative example
A Medicaid managed-care encounter has a base remit but no matched supplemental record
An FQHC's designated billing source shows a human-approved encounter and the managed-care remittance shows a base payment. The applicable state supplemental-payment report for the reporting period does not return an exact match because the external record uses a different correction lineage. This is a synthetic process example with no patient, claim, payer, or amount values.
- The Claim and Remittance Match Agent links the base payment using the approved operational keys and leaves the supplemental component open.
- The Supplemental Payment Reconciliation Agent compares clinic type, plan, accepted encounter, reporting period, rate-source version, and correction history.
- Because the external record could match either an original or replacement encounter, confidence remains low and no receivable or payer outreach is created.
- A Medicaid reconciliation specialist reviews the source files, confirms the valid lineage, and approves either the match or the appropriate correction path.
- The record keeps both candidates, the specialist's reason, and the final component status for future settlement review.
Illustrative outcome: The after-state is not an automated collection. It is one explainable exception with the correct human owner, no duplicate expected amount, and a reconstructable path from base remittance to supplemental close.
Illustrative example
A rural health clinic encounter is prevented from inheriting an FQHC rule
A multi-entity organization schedules a service at an RHC location, but a legacy mapping labels the site as an FQHC in one downstream file. The service and payer details otherwise resemble an encounter that previously followed the FQHC PPS path. This example is illustrative and contains no real site, provider, patient, or financial data.
- The Eligibility Evidence Agent records the payer response without turning it into an encounter or payment decision.
- The Encounter Definition Agent detects disagreement between the effective-dated clinic catalog and the downstream site mapping.
- The Payer Path and Rate Agent blocks the FQHC rate source and displays the current RHC and Medicare source references for human review.
- Enrollment and Medicare billing staff confirm the clinic designation, applicable service path, and required correction to the mapping.
- The corrected state is versioned, dependent work is reopened, and prior records are not silently rewritten.
Illustrative outcome: The workflow prevents a plausible-looking but wrong payment expectation from reaching reconciliation. Qualified staff still determine the correct RHC billing and payment treatment for the actual service and date.
Illustrative example
Sliding-fee and commercial-plan evidence disagree at intake
An applicable Health Center Program site has a current board-approved sliding-fee workflow, while a commercial eligibility response returns limited benefit information and no usable network answer. The financial-assistance assessment and insurer response answer different questions. The example is synthetic and includes no income, family, patient, plan, or charge values.
- The Eligibility Evidence Agent keeps the sliding-fee assessment state separate from coverage, network, authorization, and payment states.
- The agent flags the missing network evidence and does not calculate or communicate a final patient amount.
- Patient access rechecks the plan through an approved channel, while financial counseling applies the organization's authorized process.
- A qualified reviewer approves the patient communication and records any applicable contractual or legal limitation.
- Only route, page-family, specialty, workflow, content-cluster, and CTA context remain eligible for website analytics; none of the operational evidence is exported.
Illustrative outcome: The team can move each question to the correct owner without treating insurance eligibility as financial-assistance eligibility or exposing sensitive operational values to measurement systems.
Adopt the workflow one payer path and one clinic type at a time
Begin with a bounded reconciliation cohort whose source owners can inspect every record. A practical first scope is one clinic designation, one payer or state path, one reporting period, and a limited set of encounter types. Keep all actions read only until the organization proves source authority, matching, exception routing, privacy, security, and recovery procedures.
Define the control record and baseline
- Choose the clinic entity, site set, payer path, encounter types, reporting period, and accountable owners
- Document the before-state from eligibility through base and supplemental payment close
- Approve the source hierarchy, effective-date logic, correction lineage, exception taxonomy, and prohibited automation decisions
- Measure representative administrative cases and minutes using buyer-approved methods without exporting PHI
Exit criteria: Operational, clinical, coding, billing, reimbursement, finance, compliance, privacy, security, and technical owners sign off on scope, authority, baseline method, human checkpoints, data boundary, and rollback path.
Map and validate in read-only shadow mode
- Connect or securely stage minimum-necessary source data through approved methods
- Validate FQHC and RHC identity, payer-product matching, correction handling, rate versions, and reporting periods
- Run agent recommendations beside current staff work without changing claims, postings, balances, or reports
- Review every low-confidence match, false match, missing component, and source conflict with accountable owners
Exit criteria: The buyer's validation sample is reconstructable, source lineage is complete, known exceptions route correctly, and no agent recommendation can perform a financial, coverage, coding, clinical, legal, or reporting action.
Parallel-run human work queues
- Release approved evidence summaries and exception queues to designated users
- Compare queue completeness, match explanations, administrative minutes, overrides, and reopen rates with the baseline
- Test corrections, voids, replacements, missing files, payer outages, state-period changes, and access removal
- Train each team on confidence limits, human authority, escalation, audit evidence, and downtime recovery
Exit criteria: Owners accept the queue behavior and operating procedures, material mismatches are resolved, users demonstrate override and recovery, and measured time inputs are approved for the illustrative value formula or replaced with the buyer's own model.
Release narrowly scoped actions and monitor
- Enable only buyer-approved write-backs or task updates with role-based authorization and audit logging
- Retain dual review for claim, posting, adjustment, refund, write-off, rate, report, and patient-balance actions
- Monitor source freshness, match confidence, queue age, overrides, corrections, access, and rule changes
- Expand to another payer, state, clinic type, or encounter category only after a separate readiness decision
Exit criteria: Governance owners approve production boundaries, monitoring and incident paths operate as designed, staff can stop and reverse permitted automation, and expansion remains a new controlled decision rather than an assumed rollout.
Authoritative sources used for coverage context
Sources support the cited coverage and administrative context. Teams must confirm the current policy, contract, jurisdiction, and effective date for each real case.
Medicare Claims Processing Manual, Chapter 9—Rural Health Clinics and Federally Qualified Health Centers
Centers for Medicare & Medicaid Services · government · reviewed
Supports current Medicare claims context separating RHC AIR and FQHC PPS billing and payment, including the listed FQHC supplemental-payment instructions for contracted Medicare Advantage plans. Qualified staff must apply the current manual and transmittals to the exact service and date.
Federally Qualified Health Center Prospective Payment System
Centers for Medicare & Medicaid Services · government · reviewed
Supports the current CMS overview of the Medicare FQHC prospective payment system and links to methodology and payment resources. It does not establish case-specific coverage, coding, payment, or a Medicaid or commercial wrap amount.
Rural Health Clinics Information Center
Centers for Medicare & Medicaid Services · government · reviewed
Supports current Medicare RHC resources for enrollment, participation, payment, billing, cost reporting, and annual reconciliation. It reinforces that RHC operations need their own authoritative path rather than an FQHC label or rate source.
FQHC and RHC Supplemental Payment Requirements Under Medicaid and CHIP Managed Care
Centers for Medicare & Medicaid Services · government · reviewed
Supports the federal Medicaid and CHIP managed-care framework for FQHC and RHC PPS or agreed APM payment and state supplemental payments. State plans, contracts, encounter rules, timing, rates, and reconciliation details remain jurisdiction and period specific.
Health Center Program Compliance Manual, Chapter 9—Sliding Fee Discount Program
Health Resources and Services Administration · government · reviewed
Supports current Health Center Program sliding-fee requirements and the role of board-approved policy, income and family-size assessment, fee and discount schedules, third-party coverage, and applicable restrictions. Its applicability should not be inferred for every RHC.
Health Center Program Compliance Manual, Chapter 16—Billing and Collections
Health Resources and Services Administration · government · reviewed
Supports current Health Center Program billing, collections, fee-schedule, third-party payer, patient-payment, and board-policy context. The chapter applies within the Health Center Program authority and does not substitute for a payer contract or patient-specific decision.
Health Plan Eligibility and Benefits Transaction Basics
Centers for Medicare & Medicaid Services · government · reviewed
Supports the adopted electronic eligibility inquiry and response transaction context for HIPAA-covered entities. An eligibility response remains evidence from a point in time and is not presented here as a guarantee of network status, authorization, coverage, payment, or patient cost.
Coordination of Benefits and Recovery Overview
Centers for Medicare & Medicaid Services · government · reviewed
Supports current Medicare coordination and recovery context when other health insurance, liability, no-fault, or workers' compensation may affect payment order or recovery. It does not determine liability or the correct outcome for a particular encounter.
Coordination of Benefits and Third Party Liability
Medicaid.gov · government · reviewed
Supports Medicaid coordination-of-benefits and third-party-liability context, including other coverage and managed-care responsibility. State law, contracts, current facts, and qualified review determine the actual payer-order and recovery workflow.
Uniform Data System Reporting Guidance
Health Resources and Services Administration · government · reviewed
Supports the current official reporting-guidance source for Health Center Program UDS preparation and annual materials. Reporting teams must use the applicable manual and approved changes for the reporting period; this workflow does not certify or submit UDS data.
HIPAA Minimum Necessary Requirement
U.S. Department of Health and Human Services · government · reviewed
Supports the HIPAA minimum-necessary context where the standard applies, including stated exceptions. Privacy and legal professionals must determine the permitted purpose, access, disclosure, safeguards, retention, and applicable standard for each implementation.
FQHCs and Rural Health Clinics workflow FAQs
Open a question to review the answer. The disclosure controls use native browser behavior and remain available by keyboard without page JavaScript.
Is this a replacement for FQHC billing software or our EHR?
No. The page describes a focused control layer for eligibility, encounter, claim, remittance, and supplemental-payment reconciliation. The EHR, practice-management system, clearinghouse, payer, state source, finance platform, and approved policy repository remain authoritative where the buyer designates them. Any connection requires technical and security validation; no vendor integration is implied.
Can the AI decide whether a service is a billable FQHC or RHC encounter?
No. The agents can assemble the site, provider, service, documentation, coding, and payer evidence and show where it conflicts. Qualified clinicians, certified coders, enrollment staff, billers, reimbursement specialists, and compliance professionals decide whether the service meets the current encounter and claim requirements.
Why must FQHC and rural health clinic workflows stay separate?
The labels are not interchangeable. Medicare uses different FQHC PPS and RHC AIR frameworks, while Medicaid rules depend on the federal requirements plus the applicable state and managed-care arrangements. Health Center Program sliding-fee and UDS obligations also should not be assumed for every RHC. The workflow keeps clinic designation and authority effective dated.
Does a paid Medicaid managed-care claim mean the encounter is fully reconciled?
Not necessarily. The managed-care base payment may be complete while an applicable state supplemental-payment component, encounter correction, offset, recoupment, or reporting-period review remains open. The workflow keeps each component separate and requires qualified Medicaid and finance staff to approve the expected path and final close.
Are Medicare Advantage and Medicaid wrap payments the same thing?
No. CMS has a defined supplemental-payment path for contracted FQHCs in the Medicare Advantage context, while Medicaid managed-care supplemental payments arise under a different federal and state framework for FQHCs and RHCs. The responsible payer, agency, clinic type, contract, source, rate, submission, and reconciliation process must be verified separately.
Can an eligibility response be used as a guarantee of payment?
No. It is point-in-time administrative evidence tied to a payer response and request context. It does not by itself decide network, referral, authorization, encounter qualification, coding, medical necessity, final coverage, claim adjudication, supplemental payment, or patient responsibility. The workflow preserves those states and their human owners separately.
How does the workflow handle sliding-fee eligibility?
For an organization within the applicable Health Center Program authority, the workflow can organize evidence under the current board-approved policy and schedule, identify missing or stale assessment inputs, and route a decision to authorized staff. It does not determine eligibility, change patient charges, or assume that the same HRSA requirements govern every RHC.
What about behavioral health, dental, care-management, and telehealth encounters?
They remain explicit service categories with their own current payer, program, provider, location, documentation, coding, and effective-date questions. The workflow can reuse the same evidence and exception structure, but it cannot copy a generic primary-care encounter rule or infer coverage from a service label. Qualified owners approve each path.
Can QuickIntell log in to payer or state portals for us?
Only if a separately approved implementation, contract, security review, access model, and portal terms permit a specific channel. Credentials, tokens, and payer secrets never belong in page content, analytics, or research files. The workflow must include least privilege, named ownership, audit logging, access removal, outage recovery, and a controlled manual fallback.
Will the workflow submit UDS, grant, cost-report, or financial reports?
Not autonomously. It can prepare human-reviewable aggregate extracts using buyer-approved definitions and preserve source lineage. The accountable UDS, grant, reimbursement, finance, and leadership teams must apply the current official instructions, resolve definition questions, certify the data when required, and control any submission or attestation.
How does it handle corrected claims, voids, replacements, and recoupments?
Each state is versioned and linked rather than overwritten. A correction can reopen the base-payment match, supplemental component, posting, reporting, and close tasks that depend on it. Low-confidence lineage is routed to billers and finance; the software cannot choose the surviving claim, post a recoupment, rebill, refund, or write off a balance on its own.
How should an FQHC leader evaluate the business case?
Measure a bounded set of reconciliation cases before and during a controlled pilot. Use the transparent formula cases × verified administrative minutes saved ÷ 60 × the buyer's loaded labor rate. Keep time spent on exceptions and overrides in the measure, and do not convert labor capacity into promised revenue, collections, denials avoided, compliance, or staffing reduction.
How do GA4 and Search Console measurement stay non-PHI?
GA4 receives only approved route, page-family, specialty, workflow, content-cluster, CTA-label, and CTA-location context. Search Console is reviewed for aggregate clicks, impressions, CTR, average position, and query themes. Patient, provider, payer, eligibility, encounter, claim, amount, payment, state-file, and portal values are prohibited from both measurement paths.
What does the implementation offer cost, and is the software free?
The approved offer is $0 implementation fee. $0 customization charges. Software subscription and usage charges are separate and still apply, so the software itself is not free. Third-party payer, clearinghouse, interface, state, portal, data, licensing, security, travel, internal change, and out-of-scope costs may also apply and should be stated in the written agreement.
Bring one unresolved encounter from intake to final close
Use de-identified or synthetic evidence to map the clinic designation, eligibility response, sliding-fee boundary, claim or encounter lineage, base remittance, applicable supplemental-payment source, exception owner, human checkpoint, and reporting close. The goal is a bounded operating design with explainable decisions—not a demo that software can determine coverage, coding, rates, payment, liability, or patient cost.