For dialysis-facility operations, nephrology-practice leadership, monthly-capitation-payment teams, patient access, clinical-documentation, coding, billing, revenue-cycle, compliance, and payer-relations leaders who need treatment and visit evidence to reconcile without asking software to make a clinical, coding, coverage, or payment decision.
Turn Additional Dialysis Treatment and Monthly Visit Evidence Into a Review-Ready Record
Create one source-linked account-month record that keeps delivered dialysis treatments, planned frequency, additional-treatment support, facility claim lines, nephrology monthly assessments, qualifying visit evidence, payer instructions, and unresolved exceptions in their proper lanes. Reviewers can see what happened, which signed source supports it, what changed, and who must decide before a packet or claim moves forward.
This is administrative workflow support, not a dialysis prescription, clinical-documentation author, coding engine, or coverage authority. The software does not determine whether another treatment is clinically appropriate, establish medical necessity, count a visit as billable, choose a code or modifier, decide payer order, assign patient responsibility, or release a claim without the buyer's authorized human controls.
The month closes, but the evidence is still moving
Additional dialysis treatments and monthly practitioner services draw on overlapping records, yet they answer different questions. When schedules, treatment records, plans of care, progress notes, payer instructions, and claim lines are reconciled only at the end of the month, teams spend their time proving chronology instead of resolving the actual exception.
One account-month is split across two operational ledgers
The dialysis facility tracks prescribed and delivered treatments, while the nephrology practice tracks complete monthly assessments, ongoing management, and visit evidence. The same progress note may be relevant to both, but a facility treatment line is not a practitioner visit and a monthly visit is not proof that every additional treatment qualifies for payment.
Operational consequence
When the ledgers are collapsed, staff can attach the right document to the wrong billing question, misstate a treatment or visit count, and discover the mismatch only during claim review, a documentation request, or an audit.
The supporting reason is present, but its source and timing are unclear
A signed order, hospital record, dialysis progress note, monthly-capitation-payment note, updated plan of care, or other authenticated source may explain an additional session. Staff still have to confirm who authored it, when it applied, whether it addresses the specific treatment, and whether a later source superseded it.
Operational consequence
A folder full of relevant-looking documents is not a review-ready record. Reviewers lose time reopening charts, requesting duplicate records, and reconstructing which evidence existed before each treatment and claim version.
The planned frequency and delivered schedule diverge
Added, shortened, rescheduled, missed, cancelled, inpatient, transient, back-up, training, home, and modality-switch events can appear similar in a simple calendar count. The operational record needs a defined event type, service setting, status, source, and relationship to the active plan rather than an undifferentiated monthly total.
Operational consequence
Without an event-level ledger, billing teams can chase evidence for a treatment that was not delivered, overlook a delivered exception, or use the wrong monthly denominator when preparing a human review.
Payer product and payment order are treated as static
Original Medicare, a Medicare Advantage plan, state Medicaid fee-for-service, a Medicaid managed-care product, commercial coverage, and liability-related coverage can require different research. End-stage renal disease coordination periods, plan changes, network arrangements, authorizations, and contracts add questions that cannot be answered from a payer name alone.
Operational consequence
A familiar logo or last month's route can send evidence to the wrong destination, miss a current instruction, produce avoidable rework, or create an unsupported statement about which entity pays first or what the patient owes.
Exceptions become a late billing cleanup project
Missing notes, incomplete visit authorship, late signatures, duplicate claim lines, unresolved facility-versus-practice ownership, and payer responses often sit in different queues. No one sees the whole exception until a billing deadline, remittance, additional-documentation request, or denial forces a manual reconstruction.
Operational consequence
Specialists spend scarce time searching and forwarding rather than deciding. Work ages without a named owner, the same question is researched repeatedly, and leadership cannot distinguish preventable administrative delay from a decision that properly remains with a clinician, coder, payer, or compliance reviewer.
A named agent team with visible decision boundaries
Each agent handles a defined part of the additional-treatment and monthly-visit documentation workflow. Confidence signals and human escalation remain visible rather than being hidden behind an automation label.
Treatment Ledger Agent
Builds a source-linked chronology of planned and delivered dialysis events for the account-month while keeping treatment status, modality, setting, and source explicit. It identifies possible additional-treatment events but does not decide that a treatment was clinically required or payable.
Inputs
- Authenticated dialysis orders and plan-of-care references
- Facility scheduling and delivered-treatment records
- Treatment flow-sheet identifiers and completion states
- Facility claim-line drafts, corrections, and submission versions
- Home, transient, training, back-up, inpatient, and modality-change indicators when available
Checks
- Match each event on patient-account key, service date, modality, facility, and source identifier without copying patient values into analytics
- Separate planned, started, completed, shortened, missed, cancelled, rescheduled, and unknown events
- Compare the active plan version with the delivered chronology without inferring why a variance occurred
- Flag possible counts above the locally configured review threshold rather than declaring a coverage limit
- Preserve corrections as linked versions instead of overwriting the original event
Outputs
- Versioned treatment ledger with direct source links
- Planned-versus-delivered variance list
- Candidate additional-treatment queue with stated reasons for the flag
- Missing-event and duplicate-event exception list
- Confidence method
- Confidence rises only when identity, date, modality, setting, completion status, plan version, and source provenance agree across authenticated systems. A count derived from a single schedule, incomplete month, or unmatched external record is marked provisional rather than normalized into a complete ledger.
- Low-confidence action
- The agent leaves the event unresolved, shows the conflicting or missing fields, and routes it to the named facility operations owner. It does not guess that a scheduled event occurred, convert an unknown event into a no-show, or create an automatic billing hold with no human review.
- Human escalation
- Dialysis-facility clinical and operations staff confirm what was prescribed and furnished. Qualified coding and billing staff decide how the verified event is represented on a claim, and the payer or its authorized reviewer determines coverage and payment under the applicable source.
Monthly Visit Evidence Agent
Organizes the practitioner-side record for the calendar month: complete assessment, plan-of-care responsibility, ongoing management, visit authorship, visit setting, and partial-month conditions. It presents evidence for review without determining a qualifying visit count or selecting a monthly service code.
Inputs
- Signed nephrology notes and complete-assessment references
- Monthly progress notes and plan-of-care records
- Visit dates, setting, rendering professional, and billing-group data
- Hospitalization, transplant, death, transient status, and permanent practitioner-change indicators
- Center-based, home-dialysis, and modality-switch status
Checks
- Identify the authenticated author, signature state, service date, setting, and source for every candidate visit
- Keep a complete monthly assessment distinct from other encounters and administrative contacts
- Flag center-based, home, partial-month, transient, inpatient, observation, skilled-nursing-facility, and modality-switch contexts for separate human interpretation
- Detect duplicate notes, overlapping responsibility periods, late entries, and mismatched billing-group relationships
- Compare the record with current configured source questions without asserting that a visit qualifies for a specific code
Outputs
- Monthly practitioner evidence index
- Candidate visit chronology with provenance and uncertainty labels
- Complete-assessment and plan-of-care responsibility checklist
- Partial-month, modality, and practitioner-change exception queue
- Confidence method
- Confidence is based on authenticated authorship, signature status, date, setting, group relationship, month completeness, modality, and a source-linked assessment record. The agent reports field-level confidence and never treats a calendar entry, copied note, or unsigned draft as equivalent to a verified service.
- Low-confidence action
- Any uncertain visit remains uncounted in the agent output and is routed with the exact missing source or relationship. The agent will not fill a documentation gap, infer face-to-face status, or convert a partial-month record into a full-month recommendation.
- Human escalation
- The responsible physician or qualified practitioner confirms the clinical service and authorship. Authorized coding, billing, compliance, and group-practice leaders interpret current billing rules, practitioner relationships, visit counts, and the appropriate professional claim representation.
Justification Evidence Agent
Finds and indexes authenticated records that may support the reason for a specific additional dialysis treatment, then tests their provenance, timing, and relationship to that event. It does not invent a rationale, interpret clinical findings, or state that medical necessity is met.
Inputs
- Clinician-signed treatment orders and amendments
- Current and superseded plans of care
- Dialysis progress notes and monthly practitioner notes
- Authorized hospital, office, discharge, and outside-record references
- Payer or Medicare Administrative Contractor documentation instructions
Checks
- Link each candidate document to the exact treatment event and active account-month version
- Confirm author, signature, source system, relevant date range, and supersession status
- Distinguish a clinical source statement from an agent-generated summary or staff annotation
- Flag copied-forward language, contradictory frequency references, late evidence, and a plan with no event-specific support
- Compare packet contents with the current verified payer or contractor request without treating a checklist as clinical authority
Outputs
- Event-specific evidence index with source links
- Missing, conflicting, late, and superseded evidence list
- Human-review worksheet separating source facts from open questions
- Release-ready packet manifest after human approval
- Confidence method
- Confidence reflects source authenticity, signature state, temporal fit, event linkage, and consistency across the order, plan, progress record, and requested evidence list. Semantic similarity can help locate a record but cannot raise it to high confidence without those deterministic checks.
- Low-confidence action
- The agent labels the question unresolved and sends a focused request to the authorized record owner. It does not draft clinician language, reinterpret a laboratory result, decide that a condition supports more frequent dialysis, or backfill evidence after the fact.
- Human escalation
- Qualified clinicians own the dialysis prescription, clinical rationale, and signed documentation. Authorized utilization, coding, compliance, and payer reviewers determine whether the submitted record satisfies the controlling requirement for the specific service and date.
Payer and Payment-Order Agent
Assembles the administrative payer path for the account-month from verified eligibility, product, network, coordination, authorization, contract, and portal sources. It highlights uncertainty without deciding primary responsibility, coverage, patient liability, or legal rights.
Inputs
- Current eligibility and benefit responses
- Payer, product, group, network, and delegate identifiers
- Medicare entitlement and coordination information from authorized sources
- State Medicaid program and managed-care plan context
- Commercial contract guidance, payer policies, portal instructions, and call references
- Workers' compensation, no-fault, auto, or liability indicators when applicable
Checks
- Resolve payer and product identity for the relevant date rather than relying on a logo or prior month
- Separate coverage, authorization, network, coordination of benefits, claim routing, and patient-responsibility questions
- Identify Original Medicare, Medicare Advantage, Medicaid fee-for-service, Medicaid managed care, commercial, and liability paths as distinct
- Version every policy, portal instruction, contract reference, and human interpretation with its effective-date context
- Flag conflicting eligibility, a possible end-stage renal disease coordination period, and any legal or recovery question for qualified review
Outputs
- Payer-path map with verified source links
- Open coordination, authorization, network, and contract questions
- Current instruction and effective-date register
- Named human handoff for every unresolved payment-order issue
- Confidence method
- Confidence depends on service-date alignment across eligibility, exact product, member relationship, verified coordination source, network record, contract or policy version, and current transmission instructions. A payer brand alone has no confidence value, and portal text is not promoted to contract language.
- Low-confidence action
- The route stays pending and the conflicting evidence is shown to payer-relations, coordination-of-benefits, compliance, contracting, or legal staff. The agent does not choose the payer, calculate a coordination-period start, promise crossover, or tell a patient what is owed.
- Human escalation
- Authorized payer, coordination-of-benefits, contracting, billing, compliance, and legal professionals resolve payment order and liability. Payers and adjudicators make decisions within their authority; patient-facing financial communication follows approved policy and verified determinations.
Packet and Claim Reconciliation Agent
Compares the human-approved treatment ledger, practitioner record, evidence manifest, payer path, and claim draft before release. It detects mismatches and preserves the submission version but never chooses a code, modifier, diagnosis, billing provider, or appeal position.
Inputs
- Human-approved treatment and visit review states
- Evidence packet manifest and source hashes
- Facility and professional claim drafts
- Human-selected codes, modifiers, units, dates, and billing entities
- Authorization, documentation-request, submission, acknowledgment, and response records
Checks
- Match each claim line to the verified event, service date, setting, billing lane, and approved evidence version
- Keep facility additional-treatment lines separate from practitioner monthly-service lines
- Detect missing or duplicate lines, version drift, unsupported attachments, and mismatched submission destinations
- Confirm that the human release decision, transmission route, and fallback are present before any outbound action
- Preserve denials, corrections, replacements, and appeals as linked states rather than rewriting the original submission
Outputs
- Pre-release reconciliation report
- Claim-to-evidence crosswalk
- Human release checklist with unresolved blockers
- Immutable submission manifest and acknowledgment link
- Confidence method
- Confidence is deterministic: the approved ledger version, evidence manifest, payer route, claim fields, release authority, and destination must match. If any source version changed after approval, confidence falls and the record returns to review regardless of semantic similarity.
- Low-confidence action
- The agent blocks its own readiness recommendation, not the clinical service, and routes the exact mismatch to the designated owner. It will not silently swap an attachment, reuse an old response, infer a modifier, or transmit through an unvalidated channel.
- Human escalation
- Authorized facility and professional coding, billing, compliance, and payer-relations staff approve claim content and release. Clinicians validate clinical evidence, and qualified financial or legal staff control notices, disputes, refunds, recoupments, and patient-responsibility questions.
Exception and Audit Agent
Maintains the cross-team exception queue, source chronology, access history, and administrative follow-up after submission. It groups repeated operational defects for improvement while keeping case decisions, clinical facts, and payer determinations under human authority.
Inputs
- Open exceptions and owner assignments from all workflow agents
- Source-version, approval, access, transmission, and response events
- Additional-documentation requests, denials, remittances, and correction states
- Approved non-PHI reason taxonomy and service-level targets
- Manual override, downtime, and recovery records
Checks
- Confirm that every exception has a named owner, due-source, status, and escalation path
- Detect stale tasks, repeated missing-source patterns, unresolved version conflicts, and failed transmissions
- Separate agent suggestions, human approvals, payer responses, and system events in the audit chronology
- Exclude patient, treatment, visit, payer, claim, authorization, portal, and clinical values from public website analytics
- Require human review before a denial response, appeal, refund, rebill, write-off, or patient communication changes state
Outputs
- Prioritized exception queue with accountable owners
- Source-to-decision audit chronology
- Aggregate administrative defect and cycle-time summary
- Manual-fallback and recovery report
- Confidence method
- Confidence comes from complete event provenance, immutable timestamps, explicit human roles, and reconciliation between the source system and workflow state. Aggregate trends are reported only when the approved taxonomy and minimum cohort rules are met; missing events are disclosed rather than estimated.
- Low-confidence action
- The agent retains the last verified state, marks the audit gap, and alerts the workflow and compliance owners. It does not close an exception from elapsed time, treat silence as approval, or infer an outcome from a remittance or portal status it cannot reconcile.
- Human escalation
- Operations leaders assign work; compliance, privacy, security, coding, billing, clinical, payer-relations, finance, and legal owners make the decisions appropriate to their roles. High-risk actions remain unavailable until the required human approval is recorded.
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.
Dialysis and nephrology operations
Open a controlled account-month
Start with the service month, facility, nephrology group, modality context, expected payer path, and named owners. The workflow records source-system identifiers and responsibilities without moving patient or case values into public-page analytics or creating an unapproved duplicate clinical chart.
Agent actions
- Create a versioned administrative workspace linked to authenticated source records
- Separate the facility treatment lane from the practitioner monthly-management lane
- Record known modality, setting, payer, responsibility, and source-coverage gaps
- Assign facility, practice, coding, billing, payer, compliance, and clinical owners
Evidence produced
- Account-month scope and source map
- Responsibility matrix for both billing lanes
- Initial missing-source and payer-path questions
Human checkpoint: Operations owners confirm that the right facility, group, month, modality, and source systems are in scope. Privacy and security owners approve access, retention, and permitted data movement before live records enter the workflow.
Facility operations
Build the delivered-treatment chronology
Reconcile the active prescription and plan references with scheduled, started, completed, shortened, cancelled, missed, transient, training, back-up, home, and other treatment states. The result is an event ledger, not an automatic clinical-frequency or coverage conclusion.
Agent actions
- Match planned and delivered events across the authorized facility sources
- Classify status, setting, modality, source, and version for each event
- Flag candidate additional treatments and unexplained schedule variances
- Keep unknown external and partial-month history visibly incomplete
Evidence produced
- Source-linked treatment ledger
- Additional-treatment candidate list
- Planned-versus-delivered variance report
- Duplicate, missing, and unresolved event queue
Human checkpoint: Facility clinical and operations staff confirm what was ordered and furnished. A qualified clinician decides the treatment plan; coding and billing staff decide which verified events advance to claim review under the current payer source.
Nephrology documentation team
Reconcile visit, assessment, and justification evidence
Index the complete monthly assessment, plan-of-care responsibility, candidate visits, progress notes, and event-specific supporting records. Each item retains authorship, signature, date, setting, source, and supersession status so reviewers can distinguish located evidence from an accepted billing fact.
Agent actions
- Build the practitioner visit and complete-assessment chronology
- Link possible supporting documents to each candidate additional treatment
- Detect missing signatures, late entries, copied language, and date conflicts
- Route clinical gaps to the authorized author without drafting clinical rationale
Evidence produced
- Monthly practitioner evidence index
- Event-specific justification evidence manifest
- Source conflict and missing-document worksheet
- Partial-month and modality exception list
Human checkpoint: The responsible physician or qualified practitioner confirms the clinical record and ongoing management. Authorized coding and compliance reviewers determine which visits and documents are relevant to the exact billing and payer questions.
Patient access and payer relations
Verify the controlling payer path
Identify the program, exact product, service date, network and delegate context, coordination questions, current policy or contractor source, authorization state, contract guidance, submission channel, and manual fallback. No payer brand becomes a universal rule.
Agent actions
- Reconcile eligibility, product, network, coordination, and authorization sources
- Select the appropriate research lane for Original Medicare, Medicare Advantage, Medicaid, commercial, or liability coverage
- Version current official, payer, contractor, contract, and portal instructions
- Escalate uncertain payment order, patient liability, and legal questions
Evidence produced
- Verified payer-path and destination map
- Policy and instruction version register
- Coordination, network, authorization, and contract exception list
Human checkpoint: Authorized payer-relations, coordination-of-benefits, contracting, compliance, billing, financial, and legal staff approve the route and interpretation. The payer retains its coverage and payment authority, and no software status promises payment.
Coding, billing, and compliance
Review and release the exact version
Compare the human-approved ledgers, evidence manifest, payer path, and facility or professional claim draft. Release is version-specific: a later note, treatment correction, payer change, or claim edit reopens the affected checks instead of inheriting the old approval.
Agent actions
- Crosswalk verified events and visits to the human-prepared claim version
- Show unresolved blockers, source changes, and attachment mismatches
- Create a source index and immutable outbound manifest
- Require the configured human approvals and validated transmission route
Evidence produced
- Pre-release reconciliation report
- Claim-to-source crosswalk
- Human approval and release record
- Submission manifest, acknowledgment, and fallback reference
Human checkpoint: Qualified clinicians approve clinical content; authorized coders and billers select and attest claim content; compliance reviews higher-risk exceptions. Only a permitted human can release the packet or claim through a validated channel.
Revenue cycle and compliance
Close the loop without erasing history
Track acknowledgments, requests for information, responses, remittances, denials, corrections, recoupments, and appeals as linked states. The workflow measures administrative flow, not clinical outcomes, and preserves the evidence available at each human decision point.
Agent actions
- Match inbound events to the exact submission and claim version
- Assign requests, denials, and unresolved responses to accountable owners
- Preserve original, corrected, replaced, and appealed states
- Summarize aggregate missing-source and cycle-time patterns for process improvement
Evidence produced
- End-to-end audit chronology
- Response, correction, denial, and appeal work queue
- Aggregate non-PHI administrative performance summary
- Control and training improvement backlog
Human checkpoint: Authorized revenue-cycle, clinical, compliance, financial, contracting, and legal owners choose every correction, appeal, refund, rebill, write-off, and patient communication. Agent findings remain supporting evidence, not the final decision.
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: keep facility treatments and practitioner services separate
CMS describes the End-Stage Renal Disease Prospective Payment System as a bundled, per-treatment facility payment and states that facilities receive payment for up to three hemodialysis treatments per week unless more are medically justified. CMS's current claims manual translates the standard monthly edit to 13 treatments in a 30-day month and 14 in a 31-day month, with exceptions for medical justification. That payment framework is not software permission to prescribe, withhold, or automatically bill a treatment.
- Use the current CMS claims manual and the applicable Medicare Administrative Contractor source for the exact facility, service, date, modality, claim, and documentation question
- Treat every treatment above the routine payment edit as its own evidence-review event; do not use a monthly note, diagnosis label, or plan of care as automatic proof of payment
- Keep the facility treatment claim distinct from the practitioner Monthly Capitation Payment record, complete monthly assessment, ongoing management, and visit count
- CMS's center-based monthly-service guidance discusses one, two-to-three, and four-or-more visit levels and face-to-face visits; qualified staff must apply current code, practitioner, setting, partial-month, home, and group-practice rules
- The ESRD Conditions for Coverage require an interdisciplinary assessment and individualized plan of care and require at least a monthly visit evidenced by a monthly progress note; those care-record duties do not by themselves decide a specific claim
- A frequency LCD or billing article can be jurisdiction-specific and version-specific. Never copy its diagnoses, evidence list, modifier path, or utilization language into a national rule
Human handoff: The treating clinician determines the prescription and authors the clinical record. Facility staff confirm delivered treatments; authorized coders, billers, and compliance staff apply current CMS and MAC instructions; the Medicare contractor decides coverage and payment and controls review or appeal outcomes.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services, Electronic Code of Federal Regulations, Electronic Code of Federal Regulations
medicare advantage
Medicare Advantage: Medicare guardrails plus the exact plan path
Medicare Advantage is not handled by relabeling an Original Medicare claim. CMS requires plans to follow applicable Traditional Medicare coverage criteria for basic benefits and limits when internal coverage criteria may be used, while an exact plan can still have its own network, authorization, submission, documentation, delegate, and contract workflow. Current product and service-date research remains necessary.
- Verify the plan, product, network, delegated entity, service date, authorization status, and submission channel rather than relying on the Medicare Advantage brand
- Locate the applicable Medicare coverage source and any publicly available plan criteria, then preserve each source's version and scope separately
- Do not assume that a facility treatment response governs the nephrology practitioner's monthly service, or that one authorization covers future additional treatments
- Keep benefit coverage, medical-necessity review, prior authorization, claim payment, appeal rights, contract terms, and patient responsibility as different decisions
- CMS interoperability and prior-authorization rules apply to defined impacted payers and provisions; they do not create universal dialysis criteria, guarantee an API connection, or replace current plan instructions
Human handoff: Authorized plan, provider-contracting, patient-access, coding, billing, compliance, and clinical staff interpret the current path. The plan makes its determination; qualified appeal and legal reviewers control disputed decisions and communications.
Sources for this path: Centers for Medicare & Medicaid Services, Centers for Medicare & Medicaid Services
medicaid
Medicaid: state, delivery system, program, and plan first
Medicaid dialysis coverage and administration depend on the state, benefit design, fee-for-service or managed-care delivery system, exact plan or contractor, provider enrollment, service setting, and date. A Medicare frequency rule, monthly-service method, code assumption, or documentation list must not be imported into Medicaid without a current authoritative state and plan source.
- Identify the state program, eligibility category, delivery system, exact managed-care product when applicable, provider enrollment, network, service, modality, and date
- Research facility dialysis treatment rules and professional nephrology-service rules as separate lanes, including any authorization, visit, claim, attachment, and timely-filing requirements
- Preserve state manuals, approved state-plan materials, managed-care instructions, portal references, call records, and contract guidance with effective dates
- Do not infer coverage or payment from Medicare status, an old state route, a payer logo, or the fact that another treatment was clinically furnished
- Use the CMS prior-authorization final rule only for its defined impacted-payer process and API context; it does not standardize Medicaid dialysis benefits across states
Human handoff: Authorized state-program, plan, patient-access, enrollment, contracting, coding, billing, clinical, compliance, and legal staff resolve the path. The state or managed-care entity determines coverage and payment under its authority.
Sources for this path: Medicaid.gov, Centers for Medicare & Medicaid Services
commercial
Commercial coverage: product and contract evidence, not a copied policy
Commercial payer rules vary by employer or individual product, funding arrangement, network, delegate, policy, authorization program, facility contract, practitioner contract, and date. Aetna's public dialysis bulletin is one official-payer example that addresses more-frequent dialysis in defined circumstances; it is not evidence that the same language applies to another payer, product, member, or service.
- Verify the exact commercial payer, product, funding and network context, delegate, service, setting, provider, date, and current authorization or notification route
- Separate the facility treatment policy and claim path from the nephrology practice's monthly or encounter-based professional billing rules
- Capture policy, contract, portal, authorization, call, and response sources independently; do not promote a portal statement to contract authority
- Do not transfer Aetna's conditions, a three-treatment reference, or any other payer's frequency language into an organization-wide rule
- Keep coverage, authorization, medical necessity, claim payment, coordination of benefits, estimate, and patient responsibility visibly distinct
Human handoff: Authorized commercial-payer, contracting, patient-access, coding, billing, compliance, finance, clinical, and legal professionals select and interpret the current source. The payer makes coverage and payment decisions within the applicable plan and contract.
Sources for this path: Aetna
workers comp auto liability
Workers' compensation, auto, liability, and ESRD coordination need a separate lane
An injury or liability matter can introduce a carrier, administrator, jurisdiction, accepted-scope, utilization-review, no-fault, recovery, and legal workflow. Separately, CMS states that a group health plan can pay before Medicare during the end-stage renal disease 30-month coordination period. These are different payment-order questions and neither should be calculated from a diagnosis, accident flag, or calendar alone.
- Verify the jurisdiction, carrier or administrator, claim status as communicated, accepted scope as communicated, network, adjuster or contact, service, and date
- Keep treatment authorization, compensability, utilization review, bill review, Medicare coordination, conditional payment, recovery, settlement, and legal rights as separate questions
- For an ESRD coordination-period question, use current authorized entitlement and coverage sources and route the date calculation to trained coordination specialists
- Do not disclose unrelated dialysis, transplant, access, medication, laboratory, or psychosocial information to a liability recipient without an approved purpose and minimum-necessary review
- Do not decide causation, primary responsibility, patient liability, appeal strategy, recovery rights, or settlement impact
Human handoff: Authorized coordination-of-benefits, compensation or liability billing, clinical, compliance, privacy, finance, payer, and legal professionals control this lane. Carriers, plans, Medicare contractors, and adjudicators make decisions within their authority.
Sources for this path: Centers for Medicare & Medicaid Services
Controls that preserve clinical, payer, and billing authority
Dialysis records are longitudinal, multi-party, and operationally sensitive. Governance must make every source, transformation, confidence signal, override, and release visible while preventing an agent from turning an administrative match into a clinical or coverage conclusion.
Clinical authority stays with qualified professionals
Only authorized clinicians prescribe treatment frequency, assess the patient, establish or update the plan of care, interpret clinical findings, determine clinical rationale, and sign the medical record. Agent text is clearly labeled as an administrative summary and can never become a signed note by default.
Facility and practitioner lanes remain separate
Treatment events, facility claim lines, practitioner assessments, candidate visits, professional claim lines, and payer responses use distinct identifiers and states. A shared source can be linked to both lanes, but a state change in one does not silently approve the other.
Source hierarchy and effective dates are configurable
CMS manuals, regulations, Medicare contractor materials, plan criteria, state instructions, contracts, portals, calls, and internal procedures retain their publisher, scope, version, effective date, retrieval time, and human interpretation. No source is treated as universal outside its stated authority.
Provenance survives every correction
Original and corrected treatment records, notes, plans, claim drafts, submissions, responses, and approvals remain linked and immutable. Reviewers can reconstruct what evidence was available, what the agent suggested, who decided, what changed, and which version was transmitted.
Confidence cannot authorize a high-risk action
Confidence is field-level and evidence-based, with deterministic checks taking precedence over semantic similarity. Low confidence creates a focused human task; high confidence can prioritize review but cannot prescribe, code, release, appeal, refund, recoup, write off, or communicate liability.
Access follows purpose and minimum necessary policy
Roles, facility and practice scope, purpose, time-bound access, export rights, and sensitive-document controls are configured by the buyer. HHS guidance supports reasonable safeguards and minimum-necessary practices where applicable; this page does not certify compliance or replace legal analysis.
Safe failure and manual recovery are designed first
If a source is stale, a connection fails, a payer route changes, or an audit event is missing, the workflow retains the last verified state, stops its readiness recommendation, alerts the owner, and exposes a documented manual path. Silence and timeout never become approval.
- Human authority
- Qualified clinicians control treatment and documentation; facility staff confirm delivery; authorized coders and billers control claim content; payers and contractors determine coverage and payment; compliance, privacy, security, finance, contracting, coordination, and legal professionals control their respective high-risk decisions.
- Audit trail
- The audit record captures source identity and version, retrieval time, field-level match, agent output, confidence reason, missing evidence, human review, override rationale, claim or packet version, transmission, acknowledgment, response, correction, and closure. It distinguishes facts from summaries and never rewrites the original history.
- Data boundary
- Production data use requires the buyer's approved contracts, role design, retention, encryption, security assessment, and incident procedures. Public page measurement is non-PHI only: canonical route, page family, specialty slug, workflow slug, content cluster, CTA label, and CTA location. Search Console review stays page-scoped and aggregate; no patient, treatment, visit, payer, claim, portal, or clinician values are sent.
Connect the evidence trail, not an uncontrolled copy of the chart
A workable deployment links to the buyer's authenticated sources, moves only approved fields, and returns human-controlled administrative states. Every integration needs a source owner, direction, permitted purpose, latency expectation, failure behavior, access rule, and manual fallback. Naming a system category is not a promise of universal connectivity.
Dialysis facility EHR, treatment system, and flow-sheet repository
Information in scope
Retrieve approved references for orders, plan versions, schedules, treatment start and completion states, modality, facility progress notes, flow sheets, and source documents needed to build the event ledger and packet index.
Boundary
The facility system remains the treatment record. The workflow does not operate a dialysis machine, change a prescription, interpret treatment measurements, calculate adequacy, create a clinical note, or write back a completed treatment without the buyer's approved human process.
Nephrology EHR and document management
Information in scope
Link signed complete assessments, monthly progress notes, plan-of-care records, practitioner visits, authorized hospital or outside records, addenda, and approved administrative dispositions with authorship and version context.
Boundary
The nephrology EHR remains the clinical source of truth. Agents may locate and classify evidence but cannot draft clinician rationale, infer face-to-face status, sign a note, choose a billing practitioner, or convert an unsigned draft into accepted evidence.
Facility and practice scheduling
Information in scope
Compare planned treatment slots, delivered events, clinic rounds, candidate practitioner visits, cancellations, rescheduling, transient care, partial-month changes, and configured readiness states.
Boundary
A calendar entry is not proof that a treatment or visit occurred. The workflow never changes the clinical treatment schedule or practitioner roster on its own, and operational holds require a named human owner and recovery path.
Practice management, coding, claims, and clearinghouse
Information in scope
Exchange approved facility and professional claim drafts, human-selected claim fields, submission versions, acknowledgments, remittances, denials, corrections, and crosswalk references needed for reconciliation.
Boundary
Software does not select or attest codes, modifiers, diagnoses, units, billing providers, medical necessity, or patient responsibility. Each outbound connection and claim type must be validated in the buyer's test environment before controlled use.
Eligibility, payer, portal, and coordination channels
Information in scope
Retrieve approved eligibility, product, network, authorization, coordination, policy, instruction, submission, request, and response references for the exact payer path and service date.
Boundary
No universal payer API, portal access, real-time response, or automatic crossover is promised. Credentials stay in approved secret stores, terms and lawful use must be validated, and uncertain coverage or payment-order findings go to qualified humans.
Identity, access, audit, and approved reporting
Information in scope
Use enterprise identity, role and facility scope, access events, configuration versions, human approvals, source hashes, exception reasons, and aggregate administrative cycle-time measures needed for governance.
Boundary
Application audit data is not public web analytics. GA4 or similar page analytics may receive only approved non-PHI route and CTA context; patient, practitioner, treatment, visit, payer, claim, authorization, portal, denial, and clinical values are excluded.
Model administrative capacity with inputs your team can replace
Use a transparent planning formula: monthly review cases multiplied by administrative minutes saved per case, divided by sixty, multiplied by an illustrative loaded labor rate. Replace every input with a measured baseline from a bounded pilot; exclude approval rates, denials avoided, reimbursement, treatment volume growth, clinical outcomes, and any value the workflow cannot directly measure.
Monthly review cases
180 account-month reviews
Illustrative planning assumption for account-months routed through the additional-treatment or monthly-visit evidence workflow; it is not a published benchmark, customer volume, or forecast.
Administrative time saved per case
18 minutes
Illustrative difference between the buyer's measured baseline search-and-reconciliation time and pilot time for the same bounded task; clinician decision time and unresolved exception work stay excluded.
Loaded administrative labor rate
38 USD per hour
Illustrative fully loaded rate supplied only to show the calculation. Buyers should substitute their own finance-approved labor assumption and should not treat released capacity as guaranteed cash savings.
Formula
180 review cases × 18 administrative minutes saved ÷ 60 × $38 loaded labor rate = $2,052 per month of illustrative administrative capacity
Illustrative result
$2,052 per month, or 54 administrative hours, in this replaceable-input example; no approval, payment, revenue, denial, or clinical benefit is assumed.
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 possible fourth in-center treatment after a care transition
A facility ledger shows a delivered treatment above the routine weekly pattern during a month that also contains an authorized hospital-record reference, a signed nephrology note, a treatment-order change, and a later plan update. The example contains no real patient, order, diagnosis, treatment, payer, or claim values.
- The Treatment Ledger Agent marks the event as a candidate additional treatment and shows the delivered source, plan version, setting, and unresolved relationship to the order change.
- The Justification Evidence Agent links the authenticated records by date and source, labels the later plan separately, and flags that the plan alone cannot establish payment.
- The Payer and Payment-Order Agent identifies the current Original Medicare and contractor research path without applying a local policy outside its jurisdiction.
- A clinician confirms the prescription and source record; facility coding and compliance staff decide whether the evidence and human-selected claim representation follow the current instructions.
- The Packet and Claim Reconciliation Agent releases nothing until the approved ledger, evidence manifest, claim draft, and submission version agree.
Illustrative outcome: The team receives a review-ready chronology and a precise list of open questions. The software does not conclude that the extra treatment was medically necessary, select a modifier, or predict whether Medicare will pay.
Illustrative example
Center-based monthly visits are scattered across two records
The nephrology practice has a complete monthly assessment and several candidate encounter records, while the dialysis facility has monthly progress-note references and a rounds schedule. One candidate lacks a reconciled author relationship and another occurred during a setting change. These are illustrative facts, not a real claim.
- The Monthly Visit Evidence Agent builds a chronology with author, signature, setting, group relationship, assessment role, and source for each candidate item.
- Calendar-only entries remain unverified, and the setting change opens a separate partial-month question instead of being forced into a full-month total.
- The workflow keeps the complete assessment and ongoing-management responsibility visible beside, but distinct from, the visit candidates.
- The responsible practitioner validates the clinical record; authorized coding and compliance staff interpret current center-based, group, visit, and billing rules.
- The human-selected professional claim version is reconciled separately from facility treatment lines and receives its own release record.
Illustrative outcome: Reviewers see why each candidate is present or unresolved without an automated visit count. The workflow reduces chart hunting while preserving practitioner, coder, and payer authority.
Illustrative example
A home-to-center modality change meets a payer-order question
During one illustrative month, the record shows home-dialysis management, an in-center service reference, a modality transition, commercial group coverage, and Medicare entitlement information. The current payment order and professional billing path are not yet verified.
- The Treatment Ledger Agent preserves home and center events with their separate modalities and sources rather than treating every calendar day as the same treatment unit.
- The Monthly Visit Evidence Agent opens the modality-switch and partial-month questions and does not import center-based visit logic into the home record.
- The Payer and Payment-Order Agent flags a possible end-stage renal disease coordination-period review, shows the conflicting coverage evidence, and assigns a trained specialist.
- Coordination, contracting, coding, and compliance staff verify current payer order, product terms, professional billing rules, and claim destinations from authorized sources.
- Any later eligibility or modality correction creates a linked version and reopens only the affected approvals.
Illustrative outcome: The workflow prevents a modality assumption and a payer-order guess from propagating into both claims. Qualified humans retain every coverage, coding, coordination, and liability decision.
Adopt one bounded lane before expanding the workflow
Start with a representative account-month cohort, explicit non-goals, and a manual fallback. The first objective is not touchless billing; it is a reliable evidence index whose exceptions, boundaries, and human decisions can be tested against the buyer's real sources without creating a competing chart.
Map the current month-close process
- Choose one facility-practice relationship and one bounded additional-treatment or monthly-visit review lane
- Document source systems, owners, handoffs, payer paths, cutoffs, failure modes, and current manual fallback
- Measure baseline administrative search and reconciliation time with an approved non-PHI method
- Define prohibited decisions, required human roles, source hierarchy, retention, and web-analytics exclusions
Exit criteria: Operations, clinical, coding, billing, compliance, privacy, security, and payer owners approve the scope, decision boundaries, baseline method, source map, access model, and rollback path. No live automation is required to pass this phase.
Configure sources and acceptance tests
- Map treatment events, visit evidence, plan versions, payer sources, and claim states to authenticated identifiers
- Configure role and facility scope, version rules, confidence thresholds, exception taxonomy, and manual routing
- Validate each integration in a test environment with synthetic or buyer-approved de-identified scenarios
- Test missing source, duplicate event, late note, modality change, payer change, downtime, and recovery behavior
Exit criteria: Every required source and field has an owner, permitted purpose, test result, failure state, and manual alternative. High-risk outputs cannot prescribe, code, release, appeal, or communicate liability, even when all source fields match.
Run shadow review
- Generate ledgers, evidence indexes, confidence reasons, and payer-route questions without changing live claim or clinical states
- Compare agent findings with authorized human review using a pre-agreed sampling and discrepancy method
- Measure field completeness, provenance, false-clear risk, exception quality, administrative time, and recovery performance
- Repair mappings, language, thresholds, ownership gaps, and training before any controlled release capability
Exit criteria: Named owners accept the evidence-link accuracy and exception behavior for the bounded cohort, no prohibited action is observed, unresolved discrepancies have owners, and manual review remains available for every case.
Launch a controlled pilot and govern expansion
- Enable only the approved users, facility, workflow lane, payer paths, claim types, and release checkpoints
- Review source freshness, overrides, exceptions, failed connections, access events, and aggregate cycle-time measures on a fixed cadence
- Rehearse downtime, rollback, payer-route change, and source-version recovery with responsible teams
- Require a new risk and acceptance review before adding another modality, facility, state, payer, billing lane, or autonomous action
Exit criteria: Pilot owners document stable manual recovery, acceptable evidence and exception performance, trained users, complete audit events, and finance-approved value inputs. Expansion remains a separate 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.
End-Stage Renal Disease Prospective Payment System
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS overview of the bundled, per-treatment ESRD PPS and the up-to-three-hemodialysis-treatments-per-week payment framework unless additional treatments are medically justified; it does not authorize software to make a clinical or payment decision.
Medicare Claims Processing Manual, Chapter 8: Outpatient ESRD Claims
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS claims manual covering additional-treatment billing, the 13-or-14-treatment monthly payment edit with medical-justification exceptions, and separate Monthly Capitation Payment guidance for center-based, home, and partial-month professional services.
Local Coverage Determination: Frequency of Hemodialysis (L37475)
Centers for Medicare & Medicaid Services · government · reviewed
Official Medicare Coverage Database example of a jurisdiction-specific frequency policy and documentation context. Its scope, contractor, version, conditions, and related article must be verified and must not be treated as a national dialysis rule.
Monthly Capitation Payment for End-Stage Renal Disease: Four or More Visits per Month
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS approved recovery-audit topic identifying Monthly Capitation Payment professional-service context and affected visit-level codes; it supports duplicate-claim and visit-evidence controls without replacing the current claims manual or qualified coding review.
42 CFR 494.80: Condition—Patient Assessment
Electronic Code of Federal Regulations · government · reviewed
Current official regulation describing the dialysis facility interdisciplinary team's responsibility for an individualized, comprehensive assessment, supporting source-linked plan and assessment controls without turning the workflow into clinical authority.
42 CFR 494.90: Condition—Patient Plan of Care
Electronic Code of Federal Regulations · government · reviewed
Current official regulation addressing the individualized plan of care, implementation, adjustments, and at-least-monthly visit evidenced by a monthly progress note, among other clinical responsibilities; it does not by itself establish claim payment.
2024 Medicare Advantage and Part D Final Rule (CMS-4201-F)
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS summary of Medicare Advantage coverage-criteria, prior-authorization, continuity, and utilization-management requirements, supporting Medicare guardrails plus exact-plan research rather than an Original Medicare copy.
CMS Interoperability and Prior Authorization Final Rule CMS-0057-F
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS description of defined impacted payers, phased process provisions, and API requirements. It supports payer-specific implementation planning but does not create universal dialysis coverage criteria or guarantee connectivity.
Medicaid Managed Care
Medicaid.gov · government · reviewed
Official federal Medicaid source explaining state managed-care delivery arrangements and authorities, supporting state-, delivery-system-, program-, plan-, product-, provider-, and date-specific workflow research.
Clinical Policy Bulletin 0541: Dialysis
Aetna · official payer policy · reviewed
Official payer bulletin illustrating product-scoped commercial medical-necessity language for dialysis, including more-frequent treatment context. It is one payer source, not a universal policy or a substitute for benefit and contract review.
Medicare Secondary Payer
Centers for Medicare & Medicaid Services · government · reviewed
Official CMS overview of situations in which another entity pays before Medicare, including the end-stage renal disease 30-month coordination period and workers' compensation, no-fault, and liability contexts requiring separate qualified review.
Summary of the HIPAA Security Rule
U.S. Department of Health and Human Services · government · reviewed
Official HHS summary of the currently effective administrative, physical, and technical safeguard framework, including access and audit controls; it supports risk-based governance without claiming that this page or product proves compliance.
Minimum Necessary Requirement
U.S. Department of Health and Human Services · government · reviewed
Official HHS guidance on reasonable efforts to limit uses, disclosures, and requests for protected health information when the standard applies, supporting purpose-specific packets and buyer-controlled access without implying universal application.
Nephrology and Dialysis workflow FAQs
Open a question to review the answer. The disclosure controls use native browser behavior and remain available by keyboard without page JavaScript.
How is dialysis documentation software different from our EHR?
The facility and nephrology EHRs remain the clinical systems of record. This workflow adds an administrative reconciliation layer across treatment events, complete monthly assessments, candidate visits, evidence versions, payer paths, claim drafts, responses, and exceptions. It deep-links to authenticated sources and returns approved administrative states; it should not create a second chart, draft a clinical conclusion, or overwrite a signed record.
Can the agents decide that an additional dialysis treatment is medically necessary?
No. Agents can identify a possible additional-treatment event, locate source-linked records, check authorship and timing, and show the current payer or contractor questions. They cannot prescribe frequency, interpret clinical findings, create a rationale, determine medical necessity, or promise payment. A qualified clinician owns the prescription and clinical record; the authorized payer reviewer decides coverage.
Does a plan of care by itself justify payment for an extra treatment?
Not automatically. A plan of care is an essential clinical and regulatory source, but the applicable payment path can require additional, event-specific support and current contractor or payer instructions. The workflow links the active and superseded plan versions to each event and shows what else is requested. Qualified clinical, coding, compliance, and payer reviewers decide whether the record is sufficient.
Does the Medicare 13-or-14 treatment edit set a clinical treatment cap?
No. CMS's claims manual describes a monthly payment edit derived from the three-times-weekly framework and exceptions for medical justification. It is not a software rule for withholding clinically appropriate care. Clinicians determine treatment; facility billing and compliance staff apply current CMS and Medicare Administrative Contractor instructions; the contractor determines payment.
Why does the workflow keep monthly visits separate from treatment counts?
They represent different services and billing lanes. The facility ledger establishes what dialysis treatments were planned and furnished. The practitioner record addresses the complete monthly assessment, plan-of-care responsibility, ongoing management, candidate face-to-face visits, setting, and professional claim. A note can inform both reviews, but it does not make a treatment into a visit or a visit into proof for an additional treatment.
How are home dialysis, center-based care, and modality changes handled?
Each modality and setting keeps its own source, event type, professional-service context, and applicable review questions. A switch creates a linked version and may open partial-month, payer, visit, or claim-routing questions. The software does not import center-based visit logic into home management, treat every home day as a facility session, or choose the professional billing method.
Are Original Medicare, Medicare Advantage, Medicaid, and commercial rules the same?
No. Original Medicare uses current CMS and applicable contractor sources. Medicare Advantage combines federal guardrails with exact-plan workflows. Medicaid varies by state and delivery system. Commercial coverage varies by product and contract. One LCD, payer bulletin, visit rule, modifier path, portal instruction, or deadline must never be applied universally.
Can the workflow choose the dialysis code, modifier, unit, or billing provider?
No. It can reconcile human-selected claim fields with verified treatment, visit, payer, and evidence versions and flag mismatches before release. Qualified coding and billing professionals choose and attest codes, modifiers, units, diagnoses, billing providers, and claim formats under current sources. The system also keeps facility and professional claims from silently inheriting one another's approvals.
What happens when hospital or outside evidence is missing?
The evidence remains explicitly incomplete. The agent identifies the missing source, date range, owner, and affected event, then sends a focused request through an approved channel. It does not translate unavailable history into no event, reconstruct clinical facts from a claim, or draft a retrospective rationale. Human reviewers decide whether to wait, proceed, correct, or use an available payer process.
Can the software calculate the ESRD 30-month coordination period or decide who pays first?
It can flag that a coordination review may be needed and assemble authorized entitlement, coverage, service-date, and payer sources. It cannot calculate a legally controlling start date, decide primary responsibility, determine conditional payment or recovery rights, or assign patient liability. Trained coordination-of-benefits, payer, financial, compliance, and legal professionals make those decisions.
Does QuickIntell connect to every dialysis system and payer portal?
No universal connectivity is promised. Facility systems, nephrology EHRs, clearinghouses, payers, delegates, and portals differ in technical access, credentials, terms, fields, and reliability. Each connection must be validated for the buyer's lawful use, data scope, failure behavior, and manual fallback. A system name on this page is an integration category, not a supported-interface guarantee.
Can the agents answer a denial or additional-documentation request automatically?
They can match the request to the exact submission, retrieve the approved evidence index, identify missing sources, preserve the deadline source, and prepare a review workspace. They cannot invent clinical content, choose an appeal position, waive a right, submit an unapproved response, or interpret legal obligations. Authorized clinical, coding, payer-relations, compliance, financial, and legal staff control the response.
What does adoption cost, and must we replace our current systems?
The implementation fee and customization charges described on this page are zero, but software subscription and usage charges are separate under the commercial agreement; the software is not free. The recommended pilot links to existing authenticated sources rather than replacing them. Third-party, integration, data, or buyer-side costs and any out-of-scope work must be confirmed during scoping rather than assumed away.
How should we measure this page and workflow without exposing PHI?
For the public page, measure only approved non-PHI context such as canonical route, page family, specialty slug, workflow slug, content cluster, CTA label, and CTA location. Never send patient, practitioner, treatment, visit, modality, payer, claim, authorization, portal, denial, or clinical values to GA4. Review Search Console clicks, impressions, CTR, average position, and aggregate query mix at the page level, and keep production workflow reporting inside the governed application environment.
Bring one difficult dialysis account-month to a governed review
Use a synthetic, de-identified, or otherwise buyer-approved non-PHI example to map facility treatments, practitioner evidence, payer sources, claim versions, owners, access boundaries, exception behavior, analytics exclusions, and manual fallback. The session should end with a bounded pilot, explicit non-goals, acceptance thresholds, required connections, and named human authorities—not a promise of touchless clinical or payment decisions.