MethodologyPricing Sign in Create account Get your RateScore →
Trust Center · Zero PHI by architecture

Trust you can audit.

Reddenda runs on public federal data, not patient records. This page is the exact map: what enters the system, what never does, how every benchmark is computed, how the platform is secured, and the precise words we will and will not use.

Zero PHIrequired or stored for a rate snapshot. There is no patient data here to protect, lose, or audit.
100% publicfederal sources behind every benchmark: TiC filings, the NPI Registry, the CMS fee schedule.
About 15 secondsthe real Snapshot delivery promise. We round toward the truth, not toward the marketing.
Plain wordsevery compliance sentence we use is published below, with the reason we will not say more.
01Zero-PHI architecture

The line patient data never crosses.

Most reimbursement tools ask you to upload claims first and explain their safeguards second. Reddenda inverts that order. Every benchmark is computed from public federal filings, so patient data never has to be secured here because it is never requested.

What a snapshot uses

Public and practice-level inputs only

  • Your NPI, selected from the public NPI Registry
  • The 5-digit ZIP of your practice
  • Optional CPT codes and payer-mix percentages you choose to enter
  • Account basics if you sign up: name, work email, practice name
These are business identifiers under HIPAA. None of it is PHI.
What never enters the system

Not requested, not collected, not stored

  • Patient names, dates of birth, member IDs
  • Claims, remittance advice, EOB files
  • Diagnoses, chart notes, clinical records
  • Any record-level billing or clinical data
If a future workflow ever needed these, it would launch only under a signed BAA, executed first.
02Public-data methodology

How a public filing becomes your benchmark.

Every number in a snapshot can be traced backward to a federal source. The pipeline has four stages, and none of them touch a patient record.

Identify the public filings

Under federal rule 45 CFR Part 180, payers must publish machine-readable files of their negotiated rates. We have identified 314M+ raw payer-rate records across those federal Transparency-in-Coverage releases. That is the public universe this platform is built to read.

Parse and normalize

Raw files arrive in payer-specific shapes. We parse, deduplicate, and normalize them into one consistent rate row: payer, plan, procedure code, contracted rate, region. Malformed or ambiguous rows are dropped, never guessed at.

Index against federal registries

Normalized rows join the public NPI Registry and the CMS Physician Fee Schedule, so a benchmark can be traced from a provider NPI to the exact public filings behind it.

Benchmark, honestly

Your snapshot compares contracted rates against peer benchmarks computed from the same public index. Where public data is insufficient for a code or region, the snapshot says insufficient public data. No silent fill-ins, no specialty averages dressed up as your numbers.

The build-out we are indexing toward: every federal Transparency-in-Coverage release, all 50 states, refreshed on a monthly cycle as payers republish. That is a statement about scope and direction, not a count of customers.
03Data sources

Three sources. All federal. All public.

You can pull every one of these yourself, today, for free. Our work is reading them at scale and making them answer a practice-sized question.

Transparency-in-Coverage files

45 CFR Part 180 · payer-published

The machine-readable files payers are federally required to publish, listing their negotiated rates. This is the backbone of the rate index and the source of every contracted-rate comparison.

Refreshed monthly

NPI Registry (NPPES)

CMS · public provider registry

The public registry of every provider NPI in the country. It anchors a snapshot to a real provider, specialty, and location without touching a single patient record.

Public federal registry

CMS Physician Fee Schedule

CMS · public fee schedule

The public Medicare fee schedule. It gives every benchmark a stable federal reference point to stand beside the commercial rates in the index.

Public federal schedule
What we never buy, scrape, or accept: claims databases, patient records, clearinghouse feeds, or any dataset that contains PHI. The full field-by-field inventory lives at what data we use.
04Security posture

The posture as it actually stands.

No borrowed badges and no vague reassurance. Here is what protects the platform today, stated plainly enough that you can hold us to it.

Encrypted sessions

All traffic to Reddenda runs over TLS. Every session between your browser and our infrastructure is encrypted in transit, on every surface, with no unencrypted fallback.

Encryption at rest

Stored data is encrypted at rest through standard cloud-provider mechanisms. We claim the mechanism, not a marketing phrase on top of it.

No PHI stored for snapshots

A rate snapshot is computed from public filings and the inputs you type. No PHI is required or stored for it. The strongest control in this stack is the data we never collect.

Least access

Production access is limited to the founder and authorized contractors under signed confidentiality agreements. No broad internal access, because there is no broad internal team.

Named subprocessors, no borrowed badges

Our infrastructure subprocessors are named below. Each offers HIPAA-eligible service plans, and before any future PHI workflow the affected workload would move onto those plans with BAAs in place down the chain. No federal body certifies HIPAA compliance, and we do not claim third-party audits we have not completed. What you read here is the truth of the posture today.

Supabase Netlify Resend Stripe Cloudflare
05Compliance language, exact

The exact words, and where they stop.

Healthcare marketing earns distrust one inflated claim at a time. These are the compliance sentences we use, verbatim, and the line each one deliberately refuses to cross.

We sayNo PHI required.
And where it stops

The Snapshot pipeline has no PHI fields to fill, so the claim is structural, not procedural. "No PHI required" is not a claim of HIPAA certification. No federal body certifies HIPAA compliance, so we never describe ourselves as certified. The full posture, including when a BAA would be signed, lives on the HIPAA & BAA page.

We sayDocumented reimbursement opportunity.
And where it stops

Every dollar figure on this platform is an estimate identified from public contracted rates and peer benchmarks, and we never present it as a promised outcome.

The qualifier we publish next to it, verbatim: Reddenda identifies documented opportunity based on public contracted rates and submitted practice inputs. Actual recovery depends on payer response, contract terms, documentation, and negotiation outcome.

We sayResults appear in your browser in about 15 seconds. No email required. No credit card. No PHI.
And where it stops

The pipeline genuinely runs in seconds, not milliseconds, so we say about 15 seconds and nothing faster. There is no required email gate, no drip sequence, no sales call, and no card on the Free Snapshot. If a delivery promise on any surface ever drifts from this sentence, this page is the one that wins.

We say314M+ public payer-rate records identified.
And where it stops

That number counts raw public rate records identified across federal Transparency-in-Coverage files: the public universe we are indexing toward, across all 50 states, on a monthly refresh cycle. It describes the data build-out and its direction. It is never a claim about customers, revenue, or traction, and we do not imply every raw record is a live queryable row.

06Verify it yourself

Do not take this page's word for it either.

Every claim above has a longer, public write-up. Read them, or write to us and ask the hard version of the question.

Ask us directly

Security questionnaires, BAA template requests for your counsel, data-source questions, or anything on this page you want evidenced: write to us and a human answers. The BAA rule we follow is simple: it is executed before any PHI moves, or the PHI does not move.

Why this page exists

The data was always public. We made it answer to you.

Independent practices have been asked to trust a payment system they were never allowed to read. We will not ask you to trust us the same way. Everything here is built to be checked, and we would rather lose a sale than inflate a claim.

Verify us the way you would verify a payer.

Run the Free Snapshot on your own NPI and trace what comes back against the public filings. No credit card. No email gate. No PHI.

Run my free Practice Snapshot Read the methodology

15 seconds · no PHI · no card · no account