Healthcare SaaS Dev - Claims Clearinghouse Integration EDI (Claim.MD / Office Ally) — Next.js

⚠️ READ FIRST — applications without a Loom video will NOT be considered. A 60-second Loom is required. No Loom = automatic pass. Please don't send a text-only proposal. We run a healthcare SaaS for audiology clinics — live on AWS. The claims module is already built: UI, forms, database, and API routes all done and working. We need a clearinghouse specialist to complete, test, and harden the integration connecting that claims flow to Claim.MD or Office Ally. Most of the groundwork is done. Your job is to finish wiring the transport layer, run every path against the clearinghouse test account, and make it production-solid. Stack: Next.js + TypeScript on AWS (ECS Fargate + Postgres). What you'll integrate: 837P submission · 277CA acks/rejections · 276/277 status · 835 ERA + auto payment posting · 275 attachments · (optional) 270/271 eligibility. Why it's clean, not build-from-scratch: UI/DB/routes all built · integration sits behind a single client/adapter, feature-flagged for one-env-var rollback · payer gotchas (taxonomy, dependent addresses, rejection-code mapping) already solved and documented · day one you get a scope brief, test account, and file-by-file pointers. This isn't one-and-done. After it ships we need ongoing maintenance and feature work — new payers, monitoring, fixes. Solid + easy to work with = steady long-term relationship. You're a fit if you've integrated Claim.MD, Office Ally, Stedi, or Availity before — ideally several times. Tell us how many. Compliance: HIPAA app. Test account + synthetic data only, no real patient data. Signed confidentiality/BAA before access. How to apply — Loom required: Record a 60-second Loom: (1) which clearinghouses you've integrated & how many times, (2) how you'd approach this one, (3) when you can start + honest hours estimate. Start your proposal with Clearing House. We pick from the Looms.