Node.js/TypeScript Developer — Healthcare Platform (EDI Integration + API Work)

TITLE: Node.js/TypeScript Developer — Healthcare Platform (EDI Integration + API Work) OVERVIEW: I am building a HIPAA-compliant telehealth mental health platform in Florida. The core platform is built in Next.js 14 + TypeScript + Supabase. I need a developer to complete 4 specific integration tasks. This is project-based work with potential for ongoing maintenance once Phase 2 launches. ──────────────────────────────────────────────────────── TASK 1 — EDI Claim Submission via Stedi API (CRITICAL) ───────────────────────────────────────────────────── We have encounter data in Supabase (patient, provider, CPT code, ICD-10, dates, charges). You will build a TypeScript function that: a) Takes an encounter object from our database b) Formats it as a valid JSON payload for Stedi API (Stedi converts JSON → EDI 837P automatically) c) Submits to Office Ally clearinghouse via Stedi d) Stores the returned claim_id in our encounters table e) Handles errors and logs failures Reference: stedi.com/app/guides/healthcare We have Office Ally sandbox credentials ready for you. Expected output: services/billing/edi.ts Function signature already stubbed in codebase. ──────────────────────────────────────────────────────── TASK 2 — EDI 835 ERA Payment Parser (CRITICAL) ────────────────────────────────────────────── When insurance pays a claim, Office Ally sends back an EDI 835 file (Electronic Remittance Advice). You will build a function that: a) Receives the 835 file from Office Ally webhook b) Parses each claim line: - Payment amount - Denial code if denied - Denial reason text - Patient responsibility amount - Adjustment reason codes c) Updates the corresponding encounter record in Supabase: - amount_paid, paid_at - claim_status ('paid' or 'denied') - denial_code, denial_reason if denied d) Triggers our provider payment calculation We will provide sample 835 files for testing. ──────────────────────────────────────────────────────── TASK 3 — DocuSeal Docker on Railway ──────────────────────────────────── DocuSeal is an open-source document signing platform. We need it self-hosted on Railway (our existing server). You will: a) Set up DocuSeal Docker container on Railway b) Configure environment variables c) Set up SSL/domain routing d) Configure webhook to our Next.js app at /api/contracts/sign-webhook e) Test: send a test document, sign it, webhook fires DocuSeal docs: docuseal.co/docs Railway docs: docs.railway.app ──────────────────────────────────────────────────────── TASK 4 — Availity Insurance Verification API ───────────────────────────────────────────── We currently have a mock insurance verification endpoint. You will replace it with the real Availity API: a) Implement OAuth 2.0 authentication with Availity b) Call the eligibility endpoint: GET /availity/v1/eligibilities with: member_id, dob, payer_id, service_type c) Parse the response for: - Active status (true/false) - Plan name - Copay amount - Deductible remaining - Mental health coverage d) Update our patients table with verified data e) Handle all error codes (inactive, not found, timeout) We will provide Availity sandbox credentials. ──────────────────────────────────────────────────────── IMPORTANT REQUIREMENTS: - All work in development environment ONLY - No access to production database or credentials - You will receive a dev Supabase project with fake data - Must sign a confidentiality agreement before starting - Daily progress updates via WhatsApp or Slack - Available for 15-minute video call 3x per week - Overlap with US Eastern time (9AM-1PM EST minimum) ──────────────────────────────────────────────────────── BUDGET: $800-1,400 total project (milestone-based) Task 1 (EDI 837P): $300-400 Task 2 (EDI 835 parser): $200-300 Task 3 (DocuSeal): $150-250 Task 4 (Availity): $150-250 Timeline: 3-4 weeks ──────────────────────────────────────────────────────── TO APPLY, PLEASE ANSWER THESE: 1. Have you worked with EDI files (837P or 835)? If yes, describe what you built. 2. Have you integrated with any healthcare APIs (Availity, Office Ally, HL7, FHIR)? If yes, which ones? 3. What is your experience with Docker deployments? 4. Share a sample of TypeScript code you wrote (GitHub link or paste in proposal). 5. What hours are you available that overlap with 9AM-1PM US Eastern time? Proposals without answers to these 5 questions will not be considered.