Run this for your condition, your state, your people

1. 1

   A patient organization or a clinic

   Share a survey link with your community

   No code, no account, nothing to install

   Type your organization’s name and get your own survey link, a QR code, a paragraph to paste, a one-page flyer and a page where your own count appears.

   Make your kit
2. 2

   A clinic, a patient organization or an agency site

   Put a button on your website

   One line of plain HTML

   A “Price your diagnostic journey” button that opens Waypoint Ledger in a new tab. No script, no cookie, any content security policy.

   Show the lineHide the lineThe HTML to paste, with a copy button

   <a href="https://waypointledger.org/" target="_blank" rel="noopener" style="display:inline-block;min-height:44px;box-sizing:border-box;padding:12px 20px;border-radius:999px;background:#0e2a3a;color:#fff;font:600 16px/1.2 system-ui,sans-serif;text-decoration:none">Price your diagnostic journey</a>

   See it on /developers
3. 3

   An agency or a team

   Run your own copy

   One download, four commands

   Source, data, migrations, tests and a README, on your own machine. One Cloudflare account runs the full stack with its database.

   Take it, in four steps

• Open sourceThe code is Apache-2.0. The data is CC0 1.0, public domain.Read the licence
• Six data filesEvery published figure with its file, year, basis and population.See the six files
• An HL7 FHIR R4 BundleEvery ledger downloads as an HL7 FHIR R4 Bundle.Open an example
• An open-data catalogDCAT-US v1.1, the metadata standard data.gov harvests.Open /data.json
• A QR code and flyer kitA survey link, QR code and one-page flyer for your community.Make yours
• 1 Cloudflare accountOne D1 database and one KV namespace run the full stack.How to run it

Take it, in four steps

This page is the procedure, not the pitch: the files you change, the command that refuses a figure that does not reproduce, and what happens when no federal file describes the people you serve.

1. Download it and run it

   No account, no request, nothing to sign. The archive is the tree this site is built from, minus the build output and our own credentials: app/, components/, lib/, data/, cf/functions/, cf/migrations/, scripts/, tests/, and a README that is these commands with the reasons attached.

   Show the commandsHide the commandsDownload, test and run it, then the full stack with its database

   # the whole application: source, data, migrations, tests, README
   curl -sL https://waypointledger.org/waypoint-ledger-source.tar.gz | tar -xz
   cd waypoint-public
   
   npm install
   npm run build:static        # the static export the size budgets measure
   npm test                    # the suite that guards every rule below
   npm run dev                 # http://localhost:3000
   
   # the full stack, with the database, on your own Cloudflare account
   npx wrangler d1 create waypoint-ledger        # put the id in cf/wrangler.toml
   npx wrangler kv namespace create LEDGER       # put the id in cf/wrangler.toml
   npm run db:migrate:local
   npm run dev:full            # http://localhost:8788

   The Cloudflare configuration ships with placeholders rather than our project’s identifiers, so a first run cannot point at somebody else’s deployment. Nothing in the archive talks to us: take it offline and every figure on this page still reproduces from the published files it cites.

2. Prove every figure reproduces

   The two commands that keep it honest, and the suite that guards every rule.

   Show the two checks and the test suiteHide the two checks and the test suiteverify_price_table.py, gen-locality-table.mjs and npm test, and what each one refuses

   python3 data/verify_price_table.py

   Re-downloads every federal file, hashes it, and re-derives every figure. Exits 1 if a row does not reproduce from the file it cites.

   node scripts/gen-locality-table.mjs

   Recomputes all 5,668 locality figures from the published RVUs and geographic indices. Exits 1 on one cent of drift, and names the row.

   npm test

   Runs the rules as tests, not as prose: that no code path can produce a dollar figure, that figures on different bases are never added, that the published catalog validates against the government’s schema, and that the licence on the page is the licence in the tree.

3. Point it at your people

   Four kinds of change. Open the one you need.

   Another condition

   One object in data/conditions.json. No figure lives there.

   One object in data/conditions.json, pointing at a row that already exists in the price table. No figure lives in the conditions file, so adding a condition cannot introduce a number nobody checked.

   # 1. find or add the published figure, in data/prices.json
   #    a row needs the file it came from, the year, the population it describes
   #    and its basis. Nothing else may carry a dollar amount.
   
   # 2. prove the row reproduces from the file it cites
   python3 data/verify_price_table.py         # exits 1 if your row does not
   
   # 3. name the condition, in data/conditions.json
   {
     "id": "sickle-cell",
     "label": "Sickle cell disease",
     "icd10cm": "D57.1",
     "icd10cm_source": "CDC/NCHS, ICD-10-CM code descriptions, FY2026",
     "price_row_id": "your-new-row-id",     # or null, and the product says so
     "figure_kind": "condition_attributed", # or "excess"; they are not the same number
     "note": "…"
   }
   
   # 4. nothing else. The panel renders whatever that row says.

   No published figure Set price_row_id to null. The product then says, in its own voice, that no federal source publishes an annual figure for that condition, and sends the person to the gap so the absence is counted. An absence you count is data. An absence you fill with the nearest number is a fabrication.

   Another state

   Nothing to edit. All 109 CMS payment localities ship with the tool.

   Nothing to edit. All 109 CMS payment localities ship with the tool, so a person in any state sees their own locality’s figure and the drawer shows the three geographic indices that produced it. What you change is what you build on top: hand the API your state and it reprices every line without the interface.

   # every state is already priced. To check one:
   grep '^cms-99213,.*,TX-31,' public/data/locality-prices.csv
   
   # to add a service, add a row to data/prices.json with its CPT/HCPCS code,
   # then re-derive every locality figure from the CMS files:
   python3 data/build_state_prices.py <dir-with-PPRRVU2026_Jul_nonQPP.csv-and-GPCI2026.csv>
   node    scripts/gen-locality-table.mjs      # recomputes all 5,668, exits 1 on a cent of drift

   One curl returns your state’s figure with the arithmetic: GET /api/table?locality=IA-00, or /api/localities/IA-00 for every figure published for one place.

   Refused, never guessed A locality we cannot honour is refused with a sentence, never answered with the national number.

   The generator is also the audit: it recomputes every one of the 5,668 figures from the RVUs and the geographic indices on its own row and exits non-zero if a single one is off by a cent. A published number that drifts from the formula printed beside it cannot leave this repository.

   Another population

   lib/fit.ts holds the whole rule in one function.

   lib/fit.ts holds the whole rule in one function: given a published row and a person, does this figure describe them. It chooses between published figures and never computes one.

   // lib/fit.ts: fitOf() is the whole rule, in one function.
   // Add the coverage to COVERAGE_OPTIONS, then add its branch:
   
   case 'tricare':
     return base('REFERENCE PRICE',
       'TRICARE pays its own rates and they are not in this table. '
       + 'This is the federal reference figure for the same service.');
   
   // A population with no published figure returns NOT DESCRIBED with
   // offerGap: true. That is the honest answer and it is counted at /gap,
   // never filled with the nearest number.

   The API answers the same question as the screen, from the same module: POST /api/price with coverage and state returns the fitted figure and the verdict per line. See the API.

   Your own community, counted separately

   Give your organization a channel slug on the survey link.

   The burden instrument takes a channel. Give your organization a slug and every answer through your link carries it, in the public export and in the channel counts on the register. The register prints the slug exactly as it arrived and never an organization’s name, and anyone who has the link can answer through it, so read that count as answers through the link.

   https://waypointledger.org/survey?c=your-org-slug
   
   # the slug keeps lowercase letters, digits and hyphens, 24 at most. A link
   # typed as ?c=MEAction is read as meaction, and the person answering is told
   # which slug their answer is counted under. It is published as the channel
   # column of /api/export/survey.csv, so answers through your link are
   # separable from everyone else's, by you and by anyone reading the export.
   # Anyone who has the link can answer through it.

   Small cells Small cells are suppressed on the server before anything is published: a self-description held by fewer than 11 answers is counted as “fewer than 11, not shown” and never named, and the export carries no self-description at all.

   The instrument, its exact wording and every response option are in dictionary.csv, so a reviewer can read the questions without running the site.

4. Send back what your community finds

   The corrections, and the care that never entered a claims file. What we would want to know says why.

What you are starting from

Six files hold everything. Each one has an open download.

• data/prices.json

  274 published figures: 272 from federal files and 2 from a peer-reviewed analysis of a federal survey. 251 of them are priced and addable, each with its file, year, basis, population and combination rules. Version 2026-09-09.1.

  price-table.csv
• data/state-prices.json

  5,668 figures: 52 CMS codes priced for each of the 109 Medicare payment localities in 53 states and territories, every one re-derived from CMS’s own formula.

  locality-prices.csv
• data/conditions.json

  72 conditions. 68 carry an ICD-10-CM code from the CDC/NCHS file; 3 point at a published year-ahead figure and the rest carry an explicit null, because no federal file publishes one.

  /api/table
• data/synonyms.json

  Extra plain-language phrases that map to a unit of care, beyond the ones each price row already carries. This and the row synonyms are the whole matcher; there is no model behind it.

  dictionary.csv
• public/data.json

  A DCAT-US v1.1 catalog describing every open file here (the metadata standard data.gov harvests), validated against the government’s own published JSON Schema. Point a harvester at it and these files appear in a catalog beside the federal files they came from.

  /data.json
• cf/migrations/0001_init.sql

  The whole schema: journeys, corrections, gap reports, survey responses, interviews, the change log. One file, no ORM.

  what each column holds

Column meanings: price-dictionary.csv and locality-dictionary.csv. The data is CC0 1.0: the federal figures are U.S. Government works and already public domain, and our arrangement of them is dedicated to the public domain too. The code is Apache-2.0. Both are files you can read, not sentences on a page: LICENSE and NOTICE, which says line by line which licence covers what.

Every condition the tool reads, its published figures and their sources, and the schema for adding one: Conditions.