⌘K
Sign upSign in
All guides
Revenue Cycle· 10 min

Stedi Production Go-Live Runbook

Thursday cutover checklist — configure, smoke test, activate, and monitor Stedi clearinghouse in production.

  1. 1

    Pre-flight (before Thursday)

    Complete Stedi onboarding and receive production API key. Confirm STEDI_PROVIDER_NPI and organization name match your billing identity. Store STEDI_API_KEY in GCP Secret Manager with STEDI_INTEGRATION_STATUS=testing.

  2. 2

    Sandbox validation

    Exercise the sandbox stub and OAuth token issuance before touching production Stedi.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://sandbox.api.parkerapex.com/insurance/sandbox/stedi/eligibility \
  "text-cyan-300">-H "Content">-Type: application/json" \
  "text-cyan-300">-d '{"tradingPartnerServiceId":"SANDBOX">-PAYER","subscriber":{"memberId":"TEST"}}' | "text">-amber-300 font">-semibold">jq .
python apex/scripts/seed_oauth_clients.py  "text">-command-muted italic"># ensures velocity.clearinghouse.* scopes
  3. 3

    Production smoke (pre-activate)

    With STEDI_INTEGRATION_STATUS=testing, run eligibility and claim-status calls against production API using usageIndicator T (test). Verify audit logging and error handling.

  4. 4

    Thursday activate

    On go-live day, set STEDI_INTEGRATION_STATUS=active, redeploy the API, and run the cutover script.

    bash
    ./scripts/stedi_go_live.sh
"text">-command-muted italic"># Or manually verify:
"text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://api.parkerapex.com/velocity/v1/clearinghouse/stedi/health | "text">-amber-300 font">-semibold">jq .
  5. 5

    Post go-live verification

    Confirm /status shows Stedi operational, production eligibility returns payer responses, and EHR claim submission flows succeed. Complete the Stedi certification phase at /certification.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://developers.parkerapex.com/api/health/stedi | "text">-amber-300 font">-semibold">jq .
  6. 6

    Rollback plan

    If cutover fails: set STEDI_INTEGRATION_STATUS=testing, redeploy, and fall back to manual insurance verification in the EHR. Outbound clearinghouse calls return 503 when STEDI_API_KEY is unset.

Related