Healthcare ·Confidential, US healthcare RCM provider
The revenue cycle runs from eligibility check to coded claim, and staff step in only where one stalls.
A US healthcare provider needing both a patient-facing application that scales and an internal console where staff move through patient data fast, without loosening a single control.
Where this fits
Best for healthcare platforms whose interface carries compliance logic, where a UI change is also a PHI exposure and audit decision.
18+ months in production, 20+ healthcare clients. HIPAA and SOC 2 Type II.
- Epic and ModMed over HL7/FHIR
- Role-based PHI access
- Retool to React migration
What we did
- Took ownership of the entire production frontend
- Built multi-payer eligibility verification and real-time claim status
- Enforced role-based PHI access across patient and claim data
- Migrated the internal console off Retool onto custom React
Result
The platform carries the full revenue cycle under daily clinical load, with manual touches per claim tracked as a headline metric rather than an afterthought. It has run for over 18 months across 20+ healthcare clients.
The hard part
The frontend here is not a view layer. Every screen carries compliance logic: what a role may see, what has to be logged once it is seen, and which payer rule applies before a claim can move. Nothing can be cached aggressively either, because a stale eligibility response is a denied claim. Owning an RCM frontend is a compliance job written in React.
- Stack
- ReactNext.jsTypeScriptMCPOpenAIClaude APIRetool
- Focus
- Healthcare AIHIPAASOC 2RCMEHR Integration