Stedi Clearinghouse Integration
HIPAA EDI eligibility (270/271), claim status (276/277), and professional claims (837P) via Parker Apex Velocity.
- 1
Partnership overview
Parker Apex routes real-time clearinghouse transactions through Stedi — our designated HIPAA EDI partner for production go-live Thursday, June 18, 2026. Stedi accepts JSON and handles X12 translation for 270/271, 276/277, and 837P/837I.
- 2
Configure environment
Store STEDI_API_KEY in GCP Secret Manager (never commit). Set default billing provider identity used when requests omit provider details.
bash"text">-command-muted italic"># .env / Secret Manager STEDI_API_KEY=your"text-cyan-300">-stedi-api-key STEDI_BASE_URL=https://healthcare.us.stedi.com STEDI_API_VERSION=2024-04-01 STEDI_PROVIDER_NPI=your"text-cyan-300">-organization-npi STEDI_PROVIDER_ORG_NAME=Your Practice Name STEDI_PROVIDER_TAX_ID=your"text-cyan-300">-tax-id STEDI_INTEGRATION_STATUS=testing STEDI_INTEGRATION_DATE=2026-06-18 - 3
Sandbox stub (no live key)
Validate request/response shapes against the sandbox stub before using a production Stedi API key.
bash"text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://sandbox.api.parkerapex.com/insurance/sandbox/stedi/health | "text">-amber-300 font">-semibold">jq . "text">-amber-300 font">-semibold">curl "text-cyan-300">-s "text-cyan-300">-X "text">-amber-300 font">-semibold">POST 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":"MBR001","firstName":"Jane","lastName":"Doe","dateOfBirth":"19850315"}}' | "text">-amber-300 font">-semibold">jq . - 4
OAuth scopes
Partner integrations use velocity.clearinghouse.* OAuth scopes. Register a client via the developer portal or seed_oauth_clients.py.
bashvelocity.clearinghouse.eligibility "text">-command-muted italic"># "text">-amber-300 font">-semibold">POST /velocity/v1/clearinghouse/eligibility velocity.clearinghouse.claims.read "text">-command-muted italic"># "text">-amber-300 font">-semibold">POST /velocity/v1/clearinghouse/claims/status velocity.clearinghouse.claims.write "text">-command-muted italic"># "text">-amber-300 font">-semibold">POST /velocity/v1/clearinghouse/claims/submit - 5
Eligibility check (270/271)
Submit a real-time eligibility inquiry. tradingPartnerServiceId is the payer ID from your payer directory.
bash"text">-amber-300 font">-semibold">curl "text-cyan-300">-s "text-cyan-300">-X "text">-amber-300 font">-semibold">POST https://api.parkerapex.com/velocity/v1/clearinghouse/eligibility \ "text-cyan-300">-H "Authorization: Bearer YOUR_TOKEN" \ "text-cyan-300">-H "Content">-Type: application/json" \ "text-cyan-300">-d '{ "tradingPartnerServiceId": "PAYER_ID", "subscriber": { "firstName": "Jane", "lastName": "Doe", "dateOfBirth": "19850315", "memberId": "MBR001" }, "encounter": { "serviceTypeCodes": ["30"] } }' | "text">-amber-300 font">-semibold">jq . - 6
EHR session routes
Within the Parker Apex EHR, staff can trigger Stedi checks from patient insurance and claim views at /insurance/api/eligibility/check and /insurance/api/claims/{id}/submit when STEDI_API_KEY is configured.
- 7
Monitor health
Confirm partnership readiness on the developer portal status page and via the public health endpoints before go-live.
bash"text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://api.parkerapex.com/insurance/partners/stedi/health | "text">-amber-300 font">-semibold">jq . "text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://developers.parkerapex.com/api/health/stedi | "text">-amber-300 font">-semibold">jq .