vs. legacy installs
APIs, not installs
The incumbents ship DLLs, desktop encoders, and quarterly update disks. Quantara is a POST request — always current, nothing to deploy or patch, no per-seat licenses.
Quantara Health · DRG Grouper API
MS-DRG assignment as one POST request — with severity analysis, Medicare Code Editor checks, and a step-by-step decision path behind every answer. Built for revenue cycle teams and the systems they run, from nightly claims pipelines to AI copilots. Versioned against every CMS release.
REST + MCP · Deterministic · CMS v43.1 live today · Pricing from $199/mo
Payment policy is law, and the law ships quarterly. We ship it as versioned code.
Today the rules that decide what a claim pays live in PDFs, federal registers, and desktop software with quarterly update disks. Every grouper release, code edit, and severity rule should instead be an endpoint you can call, a version you can pin, and a diff you can read. When CMS changes the rules, you bump a version string — not a work order.
And the answer doesn't care who's asking: the same deterministic result serves your claims pipeline, your analyst's afternoon script, and — when you're ready — the AI copilot your team is piloting.
vs. legacy installs
The incumbents ship DLLs, desktop encoders, and quarterly update disks. Quantara is a POST request — always current, nothing to deploy or patch, no per-seat licenses.
vs. PDFs and manuals
Pin a rule version like a dependency. Diff one grouper release against the next. Reprice last year's claims under this year's rules.
ready for what's next
When you do put an AI copilot or autonomous coder to work, it needs a tool that computes the answer the same way every time — and cites the rule version behind it. Quantara is built to be that tool.
One tool, done right: the MS-DRG grouper. The rest of the payment-policy layer follows — built in the order you ask for it.
POST /v1/group · POST /v1/group/batch
One request in, one defensible answer out. The CMS version is resolved from the discharge date, returned in the response, and reproducible forever. Try it live in the docs →
Request
curl https://api.quantarahealth.com/v1/group \
-H "Authorization: Bearer $QH_TOKEN" \
-d '{
"discharge_date": "2026-07-01",
"principal_diagnosis": "I21.4",
"secondary_diagnoses": ["E11.9"],
"secondary_diagnosis_poa": { "E11.9": "Y" },
"procedures": ["027034Z"],
"age": 67,
"sex": "F",
"discharge_status": "01"
}'
Response — 200
{
"request_id": "req_8f3a…",
"ms_drg": "322",
"title": "Percutaneous Cardiovascular
Procedures with Intraluminal
Device without MCC",
"mdc": "05",
"cms_version": "43.1",
"effective_date_range": {
"start": "2026-04-01",
"end": "2026-09-30"
},
"mce_edits": [],
"warnings": ["PYTHON_CMS_ALGORITHM_PARTIAL: …"],
"billable_units": 1
}
See it work before you write a line of code.
The same engine, in your browser: enter diagnoses, procedures, and demographics — get the DRG with severity chips, MCE edits, and the full decision path. No key, no signup. Send it to your coders and CDI team; send the API to your engineers.
What people actually do with the DRG Grouper, starting day one of the trial. Each of these is one endpoint call — no implementation project.
Group every inpatient claim pre-bill and compare against the coded DRG: mismatches, missed CC/MCC capture, and Medicare Code Editor errors surface while the claim is still fixable — not three weeks later on a denial. One pipeline pass, no per-seat encoder licenses.
Coders, CDI specialists, and the AI copilots working alongside them call /v1/group and get back the DRG plus a step-by-step decision_path — every answer cites a CMS rule version. Query a case with and without a suspected MCC to show exactly what the documentation is worth.
Push historical claims through /v1/group/batch under this year's grouper — or last year's — and quantify trend, contract, and rule-change impact before it lands. Versioned responses make every number reproducible for peer review.
Regroup submitted claims from their coded diagnoses and procedures and flag where the billed DRG doesn't match — with the severity analysis and decision path as your audit evidence.
Not a developer? The free DRG calculator runs the same engine in your browser — no key, no signup.
Transparent, usage-based, and public — no "contact us for a quote" to find out what a grouper costs.
Trial
Free
14 days · 1,000 calls · Starter
Starter
$199/mo
10,000 calls included
Growth
$499/mo
50,000 calls included
Enterprise
Custom
Volume pricing
Start a 14-day Starter trial without a card. Stripe emails you before it ends; add payment details to keep the same API key active. Every plan runs the same engine, same accuracy, and same versioning.
A real API key, in thirty seconds.
Stripe emails you before the trial ends. Add payment details from that reminder and the same key stays active. Need Growth, a BAA, or custom volume? Book a call.
Payment confirmed ·
This live key is shown once. Store it somewhere safe before leaving this page.
First production request
Open the API docs
We couldn't finish provisioning
Contact supportStateless by design.
Requests are processed and answered — grouping doesn't require us to keep your claims. Every response carries its rule version and an audit log, so whenever a pipeline, an analyst, or an agent acts on a number, you can prove exactly where it came from. Your compliance team meets no surprises.
The basics, handled
Ready for production?
Already tried your free key? Book a call to talk production volumes, usage-based pricing, BAAs, and SLAs — or tell us what you're building and we'll map the integration with you.