A free, always-on payer to test your CRD, DTR, and PAS integration against

Who this is for

Built for the provider side of prior authorization — the teams whose software has to call these APIs, not the payers who host them.

• RCM (revenue cycle management) platforms
• DME suppliers — oxygen, wheelchairs, prosthetics
• Imaging centers and radiology platforms
• Home health and hospice software
• Specialty clinics — oncology, orthopedics
• Telehealth platforms with e-prescribing
• Second-tier EHR vendors

The concrete person: a tech lead who just got told “add CRD support by January” and is about to search for a test server to point their client at.

What you get

What it looks like after you sign up

The scenario catalog and the request inspector, list and detail view of each. Click any of these to zoom in.

Free, with sensible limits

This sandbox is free — no credit card, no sales call, no trial period. Sign up and you're sending requests within a minute. It runs on modest, shared infrastructure, so request volume is rate-limited per token to keep it available for everyone; that's the trade-off for it costing nothing.

What this isn't

• Not a conformance checker. Use the official Inferno test kits for that — this is a live counterparty to test against, not a certifier of your client.
• Not a real payer. Every patient, coverage, and claim here is a synthetic test fixture. Don't send real patient data (PHI) — there's nothing on the other end to protect it.
• Not a private environment. Everyone shares the same hosted instance and scenario library; there's no way yet to load your own custom scenarios.
• Not a production SLA. It's a free developer tool on shared infrastructure — expect occasional maintenance, not guaranteed uptime.

Try it in under 10 minutes

Sign up with your email first — under a minute, no password, just a magic link — to get the bearer token these commands need. Then it's three requests, one flow: CRD hook → DTR questionnaire package → PAS submit. Each feeds the next.

export TOKEN=<your token, from the dashboard>
export BASE=https://fhir-sandbox.greenice.net

# 1) CRD: ask "does this order need prior auth?" -- fetch a fixture hook call, then send it
curl -s "$BASE/api/crd/scenarios/prior-auth-required/hooks/order-sign" \
  -H "Authorization: Bearer $TOKEN" -o hook-request.json
curl -s -X POST "$BASE/cds-services/order-sign-crd" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d @hook-request.json | tee crd-response.json

# 2) DTR: fetch the questionnaire package the CRD response pointed at
curl -s "$BASE/api/dtr/scenarios/prior-auth-required/variants/prior-auth-required-canonical" \
  -H "Authorization: Bearer $TOKEN" -o dtr-request.json
curl -s -X POST "$BASE/fhir/Questionnaire/\$questionnaire-package" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/fhir+json" \
  -d @dtr-request.json | tee dtr-response.json

# 3) PAS: submit the prior-auth request, see the (corrected) decision code
curl -s "$BASE/api/pas/scenarios/prior-auth-required/variants/prior-auth-required-initial" \
  -H "Authorization: Bearer $TOKEN" -o pas-request.json
curl -s -X POST "$BASE/fhir/Claim/\$submit" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/fhir+json" \
  -d @pas-request.json | tee pas-response.json

Prefer to browse instead of copy-pasting exact ids? The scenario catalog lists every clinical module with a flow diagram, ready-made commands, and a run-in-browser button; every request shows up in the inspector.

Who built this