Claim Submission Flow
From Manual PDF to One-Click Autofill
Web | Claude Code | B2B
Pazcare

Filing a health insurance claim should not be a test of patience. But for users on Pazcare, it often was. Every TPA had its own PDF claim form, users had to download it, fill it by hand, photograph it, and upload it back, a process with just enough steps to invite mistakes at every one of them. The support tickets that followed were predictable and frequent. This project was about fixing that at the source, replacing the PDF-and-pray workflow with a clean digital form that auto-populates the claim document and hands the user a ready-to-sign file.
This project took a different direction from the start. I worked as designer, developer, and tester across the full build, using Claude Code to execute end to end. The first step was converting the existing TPA PDF claim forms into accurate HTML replicas. This went through several iterations of verification and rework until the output was precise enough to trust. Once the form structure was solid, I moved into backend development, again through Claude Code, which already had access to the Pazcare GitHub. After a few attempts I raised a pull request, got it approved, and generated a CD link to begin testing on the developer platform.
Testing was done against real employee IDs going through the claim flow. I ran the form through multiple scenarios, caught the errors, fixed them, and refined the experience until the output was consistent and clean. The first insurer went live successfully and the results were immediate enough to justify expanding. The autofill is now being rolled out across all insurers on the platform, removing the manual step entirely and closing the loop on a category of support tickets that had been a persistent drag on the team.


Since the autofill went live, claim-related support tickets have dropped by around 65%. The average time a user spends on the claim submission step went from roughly 12 minutes of manual form filling down to under 3 minutes. Error rates on submitted forms, which previously flagged on nearly 1 in 4 claims, have come down to under 5%. The feature launched first with one insurer, validated cleanly, and is now being enabled across all TPAs on the platform. For users, it is one less thing to get wrong. For the support team, it is a significant chunk of their queue that no longer needs to exist.
