Phase 1 of 6
Scoping & Claim Submission
Define the claim types, payer mix, billing systems, and regulatory surface (CMS-0057-F, HIPAA, No Surprises Act) that will govern every downstream modeling decision.
0/8
Phase Progress
Required Recommended Optional Open-Source Proprietary Trinidy
Claim Scope & Payer Mix
Identify claim types in scope for denial prediction
Why This Matters
Denial patterns differ materially between professional (837P) and institutional (837I) claims — institutional denials skew toward medical necessity and DRG downcoding, while professional denials cluster on coding specificity and prior auth. A single model trained across all claim types averages away the segment-specific signal. Emergency department and ancillary claims also carry No Surprises Act balance-billing exposure that changes the cost function for a false-negative denial prediction.
Note prompts — click to add
+ Which claim types represent the largest dollar-weighted denial exposure in our last 12 months?+ Have we segmented historical denial rate by 837P vs. 837I vs. prior auth to confirm modeling strategy?+ Are there claim types (e.g., emergency / NSA) that need bespoke handling because of regulatory exposure?Confirm which claim classes your model must score prior to submission.
Select all that apply
Inventory payer mix and contract count
Why This Matters
Denial behavior varies by payer more than by any other single feature — the same CPT/ICD-10 combination that one payer routinely pays will reliably deny at another. Auburn Community Hospital's documented greater-than-10x ROI on denial prediction came from payer-specific learning, not a generic model. A generic national model trained on an average payer mix is systematically wrong for any specific facility because payer contract terms are the signal.
Note prompts — click to add
+ What are our top 10 payers by denied-dollar volume, and do we have enough per-payer training data for each?+ Do we have a current payer contract matrix mapped to our claim adjustment reason codes (CARC)?+ How are Medicare Advantage vs. traditional Medicare treated — as the same payer or distinct?Count active payers, plan IDs, and commercial/government mix — payer-specific rules are the dominant denial driver.
Single choice
Trinidy — Generic national-average denial models miss your specific payer contract nuances. Trinidy trains on your facility's actual denial history with each payer — on-premises, so PHI in the training set never leaves your perimeter.
Set annual denial volume and dollar-at-risk baseline
Why This Matters
HFMA / Crowe LLP estimated US payers denied $262B in claims in 2022, and Kaufman Hall survey data puts denial impact at 1–3% of net revenue for most health systems. Without a dollar-denominated baseline, denial-prevention programs tend to optimize on denial count, which misprices the P&L impact — high-dollar DRG denials are worth disproportionately more attention than high-volume low-dollar professional denials. At $57.23 average rework cost per denial (Premier / Aptarro 2023, up 31% from $43.84 in 2022), even the administrative cost alone justifies a measured baseline.
Note prompts — click to add
+ What is our measured denied-dollar rate as a percentage of billed charges in the last 4 quarters?+ Who owns the P&L line for denial write-offs and rework cost?+ Is denial rate a board-tracked KPI alongside net patient revenue?Quantify the denial volume and dollars your model is accountable for reducing.
Single choice
Define latency SLA for pre-submission scoring
Why This Matters
CMS-0057-F formally begins phasing in January 1, 2026, including electronic prior authorization API requirements with decision-response time limits (72 hours standard / 7 days for standard requests in some contexts). The pre-submission denial check is a different latency problem — it runs inside the coder's workflow and needs to be fast enough not to break their flow, or it is simply turned off. Matching the latency budget to the actual human workflow is the single most predictive factor in whether the model gets used.
Note prompts — click to add
+ Is our scoring integration an in-workflow coder prompt, a submission gate, or an overnight scrubber?+ What is our coder's measured tolerance for wait time before they bypass the tool?+ For CMS-0057-F prior auth, are we meeting the mandated response time limits end-to-end?Select the end-to-end latency budget for scoring a claim before it leaves the billing system.
Single choice
Trinidy — Pre-submission scoring happens during coder workflow — seconds matter because coders wait. Trinidy runs the scoring ensemble on-node inside the revenue cycle perimeter; PHI in the claim never traverses a public cloud endpoint.
Map HIPAA / 45 CFR 160-164 scope boundary
Why This Matters
HIPAA Privacy and Security Rules (45 CFR Parts 160 and 164) apply any time identifiable PHI is processed, and OCR enforcement has consistently treated ML training data as in-scope when it contains names, dates of service, MRNs, or other Safe Harbor identifiers. The Change Healthcare 2024 breach — 100M+ records — illustrates the downside of scope that extends into a concentrated cloud vendor. De-identification under 164.514 Safe Harbor materially reduces scope but must be done correctly (all 18 identifiers removed, no re-identification risk) or it provides no protection.
Note prompts — click to add
+ Is our training set identifiable PHI, a Safe Harbor de-identified set, or a Limited Data Set under DUA?+ Do we have executed BAAs with every cloud component that touches the claims data path?+ When was our last OCR-style HIPAA risk assessment against the ML stack specifically?Confirm which components of the modeling, training, and inference path handle PHI under HIPAA scope.
Select all that apply
Assess CMS-0057-F prior authorization compliance exposure
Why This Matters
CMS-0057-F requires impacted payers (Medicare Advantage, Medicaid, CHIP, QHP on the exchanges) to implement FHIR-based Prior Authorization API, Patient Access API, Provider Access API, and Payer-to-Payer API, with denial transparency requirements beginning to phase in on January 1, 2026. Providers interoperating with these APIs must be able to ingest structured denial reasons and prior auth decisions, and denial prediction models that do not exploit the new structured signal are leaving a measurable accuracy lift on the table. The rule also shortens standard prior auth decision timeframes, changing the cost of a slow denial model.
Note prompts — click to add
+ Which of our payer partners are CMS-0057-F impacted and when are their API surfaces going live?+ Are we ingesting the FHIR Prior Authorization API structured denial reasons into our training data yet?+ How has the shortened prior auth decision window changed our latency SLA?Confirm readiness for CMS Interoperability and Prior Authorization Final Rule requirements beginning January 1, 2026.
✓ savedConfirm billing system integration target
Why This Matters
Integration surface dominates delivery risk in revenue cycle AI. Epic and Oracle Health (Cerner) are the dominant EHR-integrated billing platforms and are increasingly bundling commodity denial AI natively, which both defines the baseline competitive bar and determines the integration path (Epic App Orchard, Oracle Health Millennium open platform, etc.). Post-Change-Healthcare, many providers have deliberately diversified clearinghouses to Waystar or Availity — the current integration mix is often a live migration in progress rather than a steady state.
Note prompts — click to add
+ Which billing system is our source of truth for the submitted claim, and which are pass-through clearinghouses?+ Has our clearinghouse topology changed post-Change Healthcare breach, and is our integration still current?+ Are we competing with our EHR vendor's native denial AI, and how does our model need to differentiate?Identify the primary revenue cycle platform the model must integrate with.
Select all that apply
Specify deployment topology for scoring and remediation
Select the physical / logical deployment target for the scoring ensemble and GenAI remediation layer.
Single choice
Trinidy — The Change Healthcare 2024 breach (100M+ records, weeks of halted claims processing, $2.457B attributed cost to UHG, 94% of hospitals financially impacted per AHA) is the defining cautionary event for cloud-concentrated revenue cycle. Trinidy deploys on-premises with zero cloud dependency during surge events — inference continues even when clearinghouse partners are offline.