MedBridge — A Credentialing & Billing Portal

A web-based platform that replaced a fragmented, manual provider onboarding and document tracking process with a single, automated system.

Industry
Healthcare
Stack
Django · Bootstrap 5 · SQLite
Role
Sole Developer, End-to-End
Live Site

Fragmented credentialing data, no automated tracking

Healthcare organisations frequently deal with provider onboarding spread across spreadsheets, email threads, and paper files. NPI numbers, DEA registrations, tax identifiers, board certifications, and insurance documents all live in different places — with no single system tracking what's complete, what's pending, and what's about to expire.

The client needed a unified platform that consolidated these identifiers into a single record per provider, and enforced document compliance automatically rather than relying on someone remembering to check expiry dates.

A structured data model, built around the provider lifecycle

We started by mapping the actual credentialing workflow — from initial provider registration through document submission, review, and ongoing compliance monitoring. This became the basis for five core models: Profile, Organisation, Provider, Document, and Insurance — each with clear relationships and validation rules.

A multi-step registration flow captures personal identifiers, specialties, and organisation data without overwhelming the user with one long form. A credentialing dashboard then shows dynamic completion percentages across Personal, Organisation, and Provider segments — so admin staff can see at a glance who still needs to submit what.

Multi-step provider registration covering personal, specialty, and organisation data
Credentialing dashboard with dynamic completion percentages
Automated status alerts — Pending, Approved, Expiring Soon, Expired
Secure file uploads for W9, DEA, board certifications, and CLIA with expiry tracking

From PDF generation to role-based access control

Beyond the core data model, the platform automates one of the most tedious parts of credentialing — state application paperwork. Using ReportLab, the system generates pre-populated PDF applications directly from the provider's record, removing a manual re-entry step that previously consumed hours per provider.

Access control is handled through Django's authentication system with @login_required middleware protecting sensitive routes, and the architecture was designed from day one for a straightforward migration from SQLite to PostgreSQL when the client is ready to scale.

One system, one source of truth

What was previously a manual, multi-spreadsheet process is now a single platform — providers register once, documents are tracked automatically, and compliance status is visible at a glance. The system is live and in active use, with a clear upgrade path to PostgreSQL as the organisation's provider roster grows.

Got a workflow that's still stuck in spreadsheets?

We'll review your current process and tell you honestly whether a custom system is worth building.

Get a Free Quote Back to Portfolio Replies within 24 hours · No commitment required