Patient Portal Redesign for Regional Healthcare Network
Replacing a Legacy Patient Portal With a Modern, HIPAA-Compliant Digital Front Door
0%
0%
0.0x
0.0%
The Client
Regional Healthcare Network
This regional healthcare network operates twelve hospitals, forty-seven outpatient clinics, and a growing telehealth practice across four states. With 2.4 million patients in their system, the organization had outgrown the patient portal bundled with their EHR vendor years ago. Patients were frustrated. Physicians were fielding questions that a functional portal should have answered. And the IT leadership team knew that patient experience had become a competitive differentiator.
The Challenge
The Problem
The legacy portal was built on a decade-old codebase maintained by the EHR vendor. Customization options were limited to color themes and logo placement. The mobile experience was a responsive afterthought that required pinching and zooming through desktop-designed forms on a phone screen. Appointment scheduling required seven clicks. Lab results arrived without context, leaving patients to interpret clinical shorthand on their own. Secure messaging had a 72-hour average response time because the routing logic dumped every message into a single queue regardless of department or urgency.
The deeper technical challenge involved integration. The health system ran Epic as their primary EHR, but three of the twelve hospitals were still mid-migration from a legacy Cerner installation. The telehealth platform was a third-party service with its own authentication system. Billing operated through a separate revenue cycle management platform. Any new portal had to unify these systems into a single patient-facing experience without requiring patients to understand the complexity underneath.
HIPAA compliance added a non-negotiable layer of constraint. Every data flow, every API call, every caching decision had to satisfy the Security Rule.
Our Approach
4 Phases. 18 weeks.
Flynaut conducted patient journey mapping with 36 patients across 4 demographic cohorts, designed a FHIR R4-compliant middleware layer, and built a unified portal on React Native (mobile) and Next.js (web) with integrated telehealth.
Patient Journey Mapping & Stakeholder Alignment
4 weeksConducted moderated usability sessions with 36 patients across four demographic cohorts. Interviewed 14 physicians, 8 nurses, and the call center team that fielded 4,200 portal-related calls per month.
Patients wanted lab results translated into language they could understand, appointment scheduling that felt like booking a restaurant reservation, and secure messaging with triage logic.
Architecture Design & Integration Strategy
3 weeksDesigned a modern architecture using React Native for mobile and Next.js for web, both consuming a unified API gateway on Node.js. Built a FHIR R4-compliant middleware layer normalizing patient data from Epic, legacy Cerner, and the billing platform.
Authentication federation allows patients to sign in once and access data from any system. A medical terminology mapping translates clinical codes into patient-friendly language.
Development & HIPAA-Compliant Infrastructure
8 weeksDeployed on AWS GovCloud with Terraform IaC. All PHI encrypted at rest (AES-256) and in transit (TLS 1.3). Built a real-time availability engine querying provider schedules across all 12 hospitals and 47 clinics with a three-step booking flow.
The previous portal required seven clicks and two page reloads for scheduling. The new system requires three taps on mobile.
Rollout, Training & Optimization
3 weeksPhased rollout starting with two pilot hospitals. Patient feedback during pilot drove 23 refinements before network-wide launch. Trained 140 clinical staff on the new secure messaging triage system.
The triage system uses a rules-based routing engine with an AI-assisted urgency classifier that clinicians approve or override.
The Results
Performance That Speaks
Metric
Before
After
Change
Portal Adoption (active monthly users)
18% of patient base
74% of patient base
Appointment Self-Scheduling Rate
12%
67%
Average Scheduling Clicks
7
3
Call Center Volume (portal-related)
4,200/month
1,760/month
Secure Message Response Time
72 hours avg.
11 hours avg.
Mobile App Downloads (first 90 days)
N/A
184,000
Patient Satisfaction (portal NPS)
-12
+47
Telehealth No-Show Rate
22%
9%
Platform Uptime
96.2%
99.97%
The call center volume reduction alone saved the organization an estimated $1.8 million annually in staffing costs. The telehealth no-show rate improvement (from 22% to 9%) was directly attributed to the integrated scheduling and reminder system.
Technology
The Stack
Reflections
What This Project Taught Us
Healthcare application development is not web development with a compliance checklist bolted on. The regulatory constraints, the integration complexity, and the stakes demand a fundamentally different engineering discipline.
The decision to build a FHIR-compliant middleware layer rather than point-to-point integrations added six weeks to the timeline. But when the third Cerner hospital completed its Epic migration four months after launch, the portal required zero code changes.
During a post-launch review, a patient advisory board member — a 68-year-old managing Type 2 diabetes — told the room: 'For the first time, I feel like the hospital actually wants me to understand my own health.'
Ready?
Ready to transform your digital experience?
Flynaut builds enterprise-grade digital experiences for brands that refuse to compromise.