This project pushed me as both a Laravel and React developer. That meant security, reliability, and usability had to come first.

The platform needed to support healthcare members living with epilepsy. Sensitive data. Multiple user roles.

Complex records that needed to stay accurate and secure. And it had to be simple enough for non-technical users to interact with every day.

I started with authentication. Default packages weren’t good enough. Spam signups were a real risk, and security standards had to be strict.

I integrated Google reCAPTCHA manually, writing a custom RecaptchaServiceProvider and RecaptchaPolicy. That gave me direct control over weighting and scoring, so we could fine-tune how signups were validated.

Permissions were the next layer. Two levels of permissions were implemented: one for users, one for the state of each record. That meant editable fields, sign-off states, and access could all change dynamically as a record moved through its lifecycle. It gave the system the flexibility it needed, without sacrificing safety.

On top of that, I tightened Laravel’s defaults: correct field guarding, explicit fillable definitions, custom permission checks, and strict policy classes. These changes closed gaps that could have left sensitive health data exposed.

Each record automatically expires after seven days, but with the option to extend if needed. That ensured information stayed fresh, while still allowing flexibility in special cases.

The form system was a beast: over 150 custom inputs, with conditional options and dynamic logic. Instead of hardcoding endless variations, I built it to be flexible, forms could shift based on context without breaking structure.

To support testing, I wrote database seeders capable of generating huge sets of realistic records. That allowed me to simulate heavy use, find bottlenecks, and make sure the system stayed stable at scale.

On the frontend, I rebuilt the UI entirely in React. Each component was fresh, modular, and tied closely to the permission logic from the backend. That meant users only saw and interacted with what they were supposed to — no confusion, no dead ends. Even with complex forms and conditional logic, the UX stayed smooth.

Secure authentication, layered permissions, dynamic workflows, and a clean interface.

It handled sensitive data responsibly, scaled under load, and gave users a reliable tool to manage something that mattered in their lives.

Projects like these stand out for me because it combined technical depth with real-world impact.

It wasn’t just code but it was about trust, safety, and usability in a healthcare context. And I’m proud of how it came together.