WhenaHospitalNetworkStoppedMakingPatientsWorkHardforTheirOwnCare
A large hospital network was drowning in phone calls and administrative backlogs, while patients were frustrated by a system that made reading a test result feel like a bureaucratic ordeal. We built a patient portal that put care management directly in patients' hands—dropping administrative workload by 60% in six months.
Business Context & Telemetry
Our client was a well-regarded hospital network operating 6 facilities and serving 400,000 registered patients. While their clinical standards were high, their administrative infrastructure belonged to a different era. Appointments were booked by phone. Test results required physical letters or an in-person visit. The staff were working beyond their bandwidth to manage routine interactions that, in any other industry, would have been digitized a decade ago. Patients were patient, until they weren't.
Large, established hospital network
1,200 clinical and administrative staff, including a 45-person patient services team
Multi-city network across a single Indian state
Web, iOS, Android, Admin Dashboard, Staff Notification System
1994
“Our patient services team takes 800 phone calls a day. We have two staff members whose entire job is reading test results over the phone. That's not a good use of anyone's time — theirs or the patient's.”
Chief Operating Officer
Managing relationships with 400,000 patients using phone lines and paper.
Patient administration in most hospitals runs on a 30-year-old model: phone lines for appointments, physical counters for registration, and paper letters for results. For a network of this scale, that model was genuinely unsustainable—crushing the staff managing it and alienating the patients depending on it.
800 phone calls a day, answerable by a website
73% of daily calls were for routine questions: appointment availability, test status, or clinic timings. Two full-time staff members did nothing but read test results aloud over the phone. This wasn't an edge case; it was a primary function of the department.
The 'Anxiety Gap' of test results
Results were sent by post or required a phone call. For time-sensitive blood work or imaging, this delay was clinically inadequate. The anxiety of knowing a result existed, but not being able to see it, eroded patient trust regardless of the actual clinical outcome.
Appointments missed because reminders failed
The network's no-show rate was 22%. Patients simply forgot or had life intervene, and a single manual phone call the day prior wasn't robust enough to prompt a reschedule. Missed appointments wasted clinical capacity and delayed care for others.
Medical records held hostage by bureaucracy
Patients wanting to share their history with an outside specialist faced a multi-day process of written requests and physical collection. Many patients gave up and simply reconstructed their medical histories from memory, risking critical omissions.
Prescription renewals wasting clinical slots
Patients on stable, unchanged long-term medications had to attend in-person consultations just to get a refill. It added zero clinical value, wasted the patient’s time, and clogged the waiting list for acutely ill patients.
They implemented SMS reminders two years prior, which slightly reduced no-shows before plateauing. They also built a static website listing clinic hours and doctor profiles. Because it offered no transactional capability, the COO aptly described it as 'an expensive way to tell people to call us.'
"The patient services team was burning out. Staff turnover was high because capable people were spending their days doing mechanical work for frustrated patients. A digital portal wasn't just an efficiency play; it was a rescue mission to redirect the team toward meaningful care coordination."
We started with the phone calls — because every call was a patient telling us what the portal needed to do.
Before discussing software architecture, we embedded with the patient services team. We listened to calls, read incoming letters, and mapped exactly why the existing systems were failing patients.
Discovery & Methods
We spent four days shadowing the call center, categorizing 800 calls. We interviewed 48 patients across demographics—because a portal that alienated 72-year-olds wasn't a solution. Finally, we audited the 10+ disjointed EHR systems across the 6 facilities, realizing the portal's success hinged entirely on messy, real-world integration.
Patients weren't resistant to digital. They were skeptical it would actually work.
We expected older patients to resist technology. Instead, we found deep skepticism about hospital competence. Patients use banking and e-commerce apps daily. What they doubted was whether an appointment booked on a hospital app would actually exist when they arrived. The design challenge wasn't adoption; it was earning trust through genuine, synchronous integration.
Design Philosophy
No fake functionality. We established a strict rule: nothing in the portal would simulate an action it didn't actually perform. No 'request an appointment' forms that just sent an email to a receptionist. If a feature couldn't definitively execute an action in the core EHR, we wouldn't build it. The COO agreed instantly.
Constraints Respected
- No rip-and-replace: The portal had to integrate with 10+ existing EHRs, including two legacy systems with zero API documentation.
- Strict compliance: Architecture had to be designed around HIPAA-equivalent data protection and Indian health regulations from day one.
- Elderly accessibility: Interface design had to clear a high usability bar for users over 65, validated through direct testing.
- Zero staff disruption: The tool had to absorb admin volume automatically, not create a new dashboard for staff to monitor.
A portal that actually connected — to the right records, the right doctors, and the right systems.
Six core capabilities built into a unified patient interface, reliably connected to every disparate EHR system across the entire hospital network.
Real-Time Appointment Scheduling
Patients view live slot inventory, book in under 2 minutes, and receive instant confirmation. Availability reflects the true hospital schedule, and bookings write back synchronously to the facility's system.
The most common phone call—'I'd like to book an appointment'—disappeared entirely. Because the portal showed live inventory rather than 'request' forms, patients quickly learned they could trust the digital confirmation.
Real-time availability API aggregating data via a unified adapter layer. Synchronous write-backs ensure slots are blocked instantly. WebSockets prevent patients from looking at stale availability.Web portal with fast load times on low bandwidth and SEO for public health info
Shared iOS/Android codebase with offline caching for low-connectivity environments
Unified API layer aggregating disparate schemas from 10+ legacy EHRs
Clinical data standard ensuring future interoperability
End-to-end encryption for secure clinical messaging
HIPAA-compliant, Indian data residency, 99.95% uptime SLA
Patient language first, clinical notation second.
“Early designs used a 'plain English' toggle that patients ignored, leaving them confused by clinical jargon. We inverted it: plain language is the primary view, with clinical notation hidden behind an 'expand' click. Both audiences get exactly what they need without friction.”
Banishing the phrase 'Your request has been received.'
“Because patients were skeptical of hospital tech, ambiguous confirmations were lethal to trust. Every action in the portal produces a definitive state—a real appointment ID, a real prescription reference—or honestly explains why it can't. We ruthlessly stripped passive 'request received' copy from the UI.”
Sixteen weeks to launch. Validated by clinical staff, not just engineers.
A patient portal is only as trustworthy as the data it surfaces. We structured the build so that every EHR integration was manually validated by the hospital's records team before any patient saw it.
Delivery Timeline
Operational Log
Discovery & EHR Audit
Weeks 1–3Call log analysis, patient research, and API feasibility audits across all 6 facilities. Security architectures were reviewed and locked by legal before a single line of code was written.
Core API & Data Validation
Weeks 4–7Unified FHIR adapters built for 10+ EHRs. The records team manually compared data pulled through our API against their legacy source systems to verify 100% accuracy before proceeding.
Scheduling & Reminder Engine
Weeks 8–10Real-time scheduling and multi-channel reminders built. We ran a soft launch with 500 opted-in patients to monitor booking completion rates and system load.
Records, Messaging & Prescriptions
Weeks 11–14Test results, plain-language translations, and secure messaging routing deployed. The medical writing team spent four weeks finalizing the translations for the 40 most common lab results.
Full Rollout & Counter Registration
Weeks 15–16Phased network launch. We deployed a 'counter registration' workflow using QR codes, allowing hospital staff to physically help elderly patients log in for the first time before they left the building.
Team Topology
Deployed Roster
Collaboration
Working Rhythm
Our most valuable collaborator was the patient services manager. She knew every edge case, every exception, and every scenario where a 'digital-first' approach would fail a vulnerable patient. Her ground-level reality checks prevented us from shipping features that looked great on a whiteboard but would have failed in the waiting room.
Course Corrections
Diagnostic Log
Two of the legacy EHRs had zero API documentation, and one was a bespoke 12-year-old system with no remaining vendor support.
We engaged the clinician who had used the bespoke system for 12 years. Her institutional memory, combined with our engineers' database schema analysis, allowed us to build read-only database adapters. We safely extracted the records without ever risking write-corruption on the fragile legacy systems.
Writing the 'patient-readable' explanations for lab results was a massive clinical and tonal challenge. It had to be accurate, calming, and universally understood.
We established a strict assembly line for the top 40 most common results (covering 85% of total volume). A medical writer drafted it, a specialist revised it, the patient services manager checked it for plain English, and the Medical Director gave final approval. Anything outside those 40 results simply prompted the patient to await a doctor's call.
Initial usability testing with patients over 65 yielded an 81% task completion rate—well below our 90% target. The appointment date picker and login flow were too complex.
We ran two targeted iteration sprints. We enlarged touch targets, simplified the result views, and added a persistent 'call us instead' button to every screen to act as a safety valve. Task completion jumped to 93%. We also built a staff-assisted QR registration flow at the physical reception desk to overcome initial login friction.
Six months later: Call volumes plummeted, and receptionists became care coordinators.
The administrative metrics moved immediately. But the most profound win was staffing: because the portal absorbed the mechanical workload, three patient services members were redeployed from answering phones to proactively managing chronic care patients.
60%
Less administrative workload
reduction in inbound calls, paper forms, and manual admin tasks
85%
active portal usage among registered patients within 3 months
35%
missed appointments dropped from 22% to 14.3%
Qualitative Objectives Reached
- The patient-readable result explanations became the most-engaged feature. Patients viewed them an average of 2.3 times, indicating they were finally understanding their health data and sharing it with family.
- Freed from the phones, three redeployed staff members identified 340 overdue chronic patients and successfully re-engaged 218 of them. Clinicians noted that several of those interventions caught deteriorating conditions that would have otherwise resulted in hospitalization.
- Digital prescription renewals reclaimed roughly 140 consultation slots per month (7 full consulting days). Reallocating this time to acutely ill patients dropped the network's average new-patient wait time from 5 weeks to 3 weeks.
"I've been a patient here for eleven years. Last month I had a blood test on Tuesday morning. By Tuesday afternoon I could read my results on my phone — and actually understand what they meant. I didn't have to wait for a letter. I didn't have to call. I cried a little, honestly, because I've been anxious about blood tests for years, and this was the first time I felt like the system was on my side."
Long-term patient, chronic condition management programme
Hospital Network Patient
Insights Gained
Valuable lessons and strategic insights uncovered through this project that inform our future work and architectural decisions.
Trust is earned through reliable integration, not pretty UI.
A beautiful app that books an appointment into an email queue rather than a live database will fail. Patients are making health decisions; the data has to be right, synchronous, and definitively confirmed, or they will revert to calling the front desk.
Good tech makes staff's jobs more meaningful.
We built the portal to cut administrative burden, but the real ROI was human. Freeing receptionists from reading lab results aloud allowed them to become proactive care coordinators—work that actually saves lives.
Medical translation is a clinical task, not a design task.
Translating clinical jargon into patient-friendly language requires extreme clinical care. The four weeks spent having doctors author and review plain-English lab results was not project overhead; it was the core value of the product.
Capabilities & Archive
Running a healthcare facility where your administrative team is drowning and patients are frustrated by ancient processes? The solution is simpler than it looks — and the return is faster than most leaders expect.
Services Leveraged
Your patients manage their banking and travel digitally. Healthcare should be no different.
We build patient portals for networks that are skeptical about digital adoption. We've proven that when the integration is real and the experience is trustworthy, patients will use it. Tell us about your admin workflows, and we'll give you an honest view of what's achievable.
"No generic digitization pitch. A real conversation about your patients and workflows."