Skip to main content
QuantLab Logo
Healthcare / RCM2026·10 weeks

Custom HIPAA-aware claim portal for a regional medical billing team

A HIPAA-aware internal claim portal with bi-directional clearinghouse ETL, immutable audit logging, role-based access, and an encrypted EOB document vault — built so a four-person billing team could stop answering claim-status calls and start working denials.

Client: Regional Medical Billing Co.
60% reduction in claim-status calls
8 hours/week saved per biller
Zero PHI exposure incidents
$40K annual savings

The Situation

The client is a four-person revenue-cycle management team servicing roughly fifteen independent medical practices across the Southeast. The business had grown faster than the tooling — billers were drowning in claim-status phone calls from practice managers, manually reconciling 837/835 transactions across two separate clearinghouses, and keeping eligibility responses in shared Outlook folders. Every morning started with each biller pulling reports from two clearinghouse portals, copying claim statuses into a shared spreadsheet, and then re-keying anything that did not match. Practice managers called or emailed for status updates throughout the day, pulling billers off denial work. The owner knew the model was capped at fifteen practices unless the workflow stopped being manual.

The Challenge

Healthcare data has hard regulatory edges. The portal had to enforce HIPAA-aligned access controls (role-based, least-privilege, full audit trail), keep PHI encrypted at rest and in transit, deduplicate claim records arriving from two separate clearinghouse feeds, and give each practice tenant a view that exposed only their own data. EOB attachments had to live in an encrypted document vault with downloadable links that expired. Every meaningful action — claim view, status change, document download — needed to be captured in an immutable audit log defensible to a HIPAA auditor.

Our Approach

QuantLab ran a two-week discovery covering claim lifecycle, clearinghouse feed shapes, practice-tenant boundaries, denial reason mapping, and the team's actual day-to-day workflow. We then designed a multi-tenant Postgres data model with row-level isolation per practice, built a Next.js 16 portal on top, and wrote a scheduled ETL job that pulls 837/835 transactions from both clearinghouse APIs, normalizes them into a shared claim schema, and deduplicates against a content-addressable hash. HIPAA baseline controls — encryption at rest, encrypted S3 vault for EOB attachments, audit-log middleware, role-based session checks, and timed-expiry document URLs — were wired in before the first practice was migrated onto the system.

What We Built

  • Multi-tenant Next.js 16 internal portal with per-practice row-level isolation
  • Scheduled ETL pulling 837/835 transactions from two clearinghouse APIs with content-hash deduplication
  • Immutable audit log capturing user, action, entity, timestamp, and before/after JSON
  • Role-based access (owner, biller, viewer) with least-privilege session checks
  • Encrypted S3 document vault for EOB attachments with expiring signed URLs
  • Practice-manager read-only view so status calls drop off without exposing PHI from other tenants

Tech Stack

Next.js 16PostgreSQLDrizzle ORMVercelResendAWS S3 (encrypted)

The Outcome

Claim-status phone calls dropped by roughly sixty percent within the first six weeks of rollout because practice managers could log in and see exactly where each claim stood. Each biller recovered around eight hours per week previously spent on manual reconciliation and re-keying, which was redirected to denial follow-up — the highest-margin work in the practice. The team passed its first HIPAA-aligned internal review with zero PHI-exposure findings, and the owner has since added two more practices without adding headcount.

Like to know more about this project? Talk to William.

Have a similar problem? Let's talk.

Tell us what you're dealing with. We'll be honest about whether we can help.