Healthcare & Pharma · Case study

A patient app MLR and patients both approved.

Outcome

HIPAA + PIPEDA. MLR workflow inside the CMS. WCAG 2.2 AA conformance verified pre-launch by third-party audit.

IndustryHealthcare & Pharma
UpdatedApril 2026
Outcomes

Numbers the CFO will actually defend.

Enrollments · first quarter post-launch
100,000+
Third-party accessibility audit · pre-launch
WCAG 2.2 AA
Baselines documented in DPIA
HIPAA + PIPEDA
Content review + audit trail · integrated
MLR in CMS

Quick answer
A pharmaceutical manufacturer wanted a patient companion app to support adherence for a specialty therapy. NUUN Digital ran patient and clinician co-design, built the app against HIPAA and PIPEDA baselines, integrated MLR workflow for content, and shipped through App Store and Play Store review. Outcome: enrollments in the first quarter and measurable adherence lift in the follow-up study.

THE CHALLENGE

Adherence on the specialty therapy was below modelled expectations, and patient support calls were concentrated on a handful of avoidable questions. The brand team wanted a digital companion — reminders, education, side-effect tracking, easy routes to a specialty pharmacy or nurse line — without turning the app into a regulatory liability.

Internal and external barriers stacked up. The MLR (medical, legal, regulatory) committee was strict, and rightfully so. Patients living with the condition had specific accessibility needs. The commercial team wanted useful engagement metrics that didn't pretend a medical app was a marketing app. Everyone wanted it done yesterday.

THE APPROACH

  1. Patient and clinician co-design. Journey mapping with patients living with the condition plus interviews with treating clinicians surfaced the moments the app had to earn its place. Accessibility tested with screen-reader users and low-dexterity participants from day one.
  2. Regulatory-first architecture. HIPAA and PIPEDA baselines; data minimization by default; PHI handling documented in a DPIA; content review integrated into the CMS via an MLR workflow rather than bolted on.
  3. Native build on Swift and Kotlin. Performance and accessibility were decisive. Dynamic Type, VoiceOver and TalkBack, high-contrast theme, and motor-accessibility patterns tested per release.
  4. Store submission handled. App Store Review and Play Console submissions managed by the delivery team, including the medical-app review nuances that trip up first-time submitters.
  5. Measurement plan agreed up front. Enrollment, sustained use, and self-reported adherence treated as primary; engagement micro-metrics treated as diagnostic, not celebratory.

THE RESULTS

  • ** enrollments** in the first quarter post-launch.
  • 12-point adherence lift on the follow-up study (self-report, matched cohorts with enrolment status as proxy).
  • 29% 30-day retention among enrolled patients.
  • WCAG 2.2 AA conformance verified by third-party audit pre-launch; no post-launch accessibility complaints escalated.
  • MLR cycle time reduced vs. legacy email-and-PDF workflow; MLR approval logged inside the CMS for audit.
  • 4.8★ App Store / 4.8★ Play Store ratings after 90 days.

CLIENT QUOTE

"The day MLR signed off on a live content change inside the CMS, we knew we had the right team." — Senior leader, anonymized, Anonymized leadership

SERVICES INVOLVED

RELATED CASE STUDIES

METHODOLOGY & MEASUREMENT

Enrolment measured from Day 0; retention via standard cohort methodology; adherence lift derived from a pre-specified follow-up study with defined inclusion criteria. Accessibility audit by a third party. DPIA, threat model, and MLR SOP available under NDA for prospective clients and auditors.

SOURCES & FURTHER READING

Case FAQ.

What is a patient companion app?
A mobile app designed to support a patient through a specific therapy — typically covering reminders, education, side-effect tracking, and routes to a specialty pharmacy or nurse line. Distinct from a generic health app because it's tied to a prescribed therapeutic.
How do you build a HIPAA-compliant patient app?
HIPAA and PIPEDA baselines set in architecture — data minimization by default, PHI handling documented in a DPIA, encryption in transit and at rest, and audit logging on every access. Compliance is architected in, not layered on.
What is MLR review in healthcare marketing?
Medical, Legal, and Regulatory review — the approval gate every patient-facing asset from a pharmaceutical company has to clear. We integrate MLR workflow directly into the CMS so content approval has a defensible audit trail rather than living in email.
How long does App Store approval for a medical app take?
Typically 2–6 weeks depending on submission quality, but medical apps get scrutiny that first-time submitters underestimate. Our delivery team manages Apple and Google submissions end-to-end, including the medical-category nuances.
What accessibility standard should a patient app meet?
WCAG 2.2 AA, verified by third-party audit pre-launch. For patient apps specifically, that means screen-reader parity (VoiceOver and TalkBack), Dynamic Type, high-contrast theming, and motor-accessibility patterns tested with representative users.
How do you measure patient-app success without over-claiming?
Primary metrics are enrollment, sustained use, and self-reported adherence measured via a pre-specified follow-up study. Engagement micro-metrics (MAU, session count) are diagnostic, not celebratory — they're reported but never the headline.

Ship A Patient App That Lasts

Bring the therapy and the patient need. We'll bring the team that respects the regulation and the patient.