Case study
U.S. Army E-EFMP — From Paper to the Cloud
The Exceptional Family Member Program (EFMP) supports Army families with members who have special medical or educational needs. Before E-EFMP, the workflow was largely paper-based — forms had to be physically re-submitted at every new installation, approvals moved by mail, and a family's records didn't travel with them.
The challenge
Replace a fragmented, paper-driven program with a single secure system that families, providers, and coordinators could rely on across Army installations worldwide — and automate the tedious approval chains that used to take weeks of mailed paperwork.
The team
Three developers, building the entire platform from scratch. We all wore every hat — there was no "frontend person" and "backend person," we each owned features end to end, page by page, workflow by workflow.
The solution
- Cloud-saved enrollment and screening forms — no more re-submitting paper at every PCS move
- Status-driven workflows for packets, families, providers, and policies, so every stakeholder could see exactly where a case stood
- Automated provider and doctor approval routing — replacing mailed paperwork with in-app review and sign-off
- Directory listings for every installation, wired up to the Army's existing APIs
- An in-app community forum with per-installation chat rooms, so families could talk to each other and get local updates
- Mobile-accessible via website and iOS / Android apps
My role
One of the three developers who built the whole thing from the ground up. Concretely, I:
- Built pages and their workflows end to end
- Designed and implemented the status models for packets, people, providers, and policies, and the automation that moved them through their lifecycles
- Streamlined the tedious manual work — especially getting provider and doctor approvals without anyone mailing a form
- Set up the directory listings for all installations against the Army's APIs
- Helped build the in-app community forum and installation chat rooms
Specifics on internal architecture and the exact technologies are kept deliberately high-level here. The work required a security clearance and the program was conservative about disclosing what was being built and how — so this stays at the "what we delivered" level by design, not detail by detail.
Public references: army.mil announcement.