1. Journey mapping
Measure why patients visit or call the front desk and identify interactions suitable for safe self-service.
Prototype client story · Healthcare
A digital front door that removed unnecessary hospital queues.
Cedarfield Specialist Hospital wanted patients to complete routine service interactions without starting every journey at a reception desk. This fictional story shows MyHealth operating as the visible layer of a connected hospital workflow.
Project summary
The portal was not the project. The service journey was.
Cedarfield Specialist Hospital is a fictional 180-bed hospital with specialist outpatient clinics, imaging, laboratory services and managed-care patients. Its front desk handled registration, appointment questions, bill enquiries, payment confirmation, result collection and general navigation—often at the same time.
The hospital had digital systems behind many of those interactions, but patients still experienced the institution as a series of physical desks. The fictional V3C engagement used MyHealth to create a single digital access layer while preserving the hospital systems responsible for appointments, billing, results and clinical release.
Challenge
Patients queued for information that already existed digitally.
A routine follow-up could require a call to confirm a clinic day, a trip to the front desk to validate an appointment, another stop to confirm payment and a later return simply to collect an approved result. Staff spent significant time answering status questions rather than resolving exceptions.
The challenge was therefore not to “put the hospital online.” It was to identify which patient interactions were safe and useful to expose digitally, how the patient would be verified, which system remained authoritative, and what should happen when a workflow could not be completed automatically.
Operating environment
MyHealth sat in front of appointments, billing, payments, results and notifications.
The fictional design uses MyHealth for self-enrolment, appointment discovery and booking, bill visibility, online payment, release-controlled access to laboratory and imaging results, and service notifications.
The hospital systems behind those interactions remain responsible for clinical and financial state. MyHealth presents the service to the patient; it does not create a second version of the hospital record.
- Self-enrolment and verified identity
- Appointments and service scheduling
- Bill visibility and digital payment
- Approved laboratory and imaging results
- Notifications and status updates
V3C approach
Expose a service only when the hospital workflow behind it is complete.
V3C began with journeys rather than screens. For each journey—book a visit, pay a bill, view a result—the team identified the authoritative hospital system, required identity checks, success state, exception path and audit event.
That discipline prevented the portal from becoming a disconnected application. A payment had to update the hospital-side workflow. A result could appear only after the hospital marked it eligible for patient release. An appointment slot had to reflect actual scheduling rules rather than a second calendar.
The resulting architecture made MyHealth the patient-facing orchestration layer while the hospital systems remained responsible for the underlying business and clinical rules.
Architecture
Patient access connected to hospital-side workflow
Patient
MyHealth
Identity / verification
Hospital services
Payment / appointment / result state
Notification + audit
How it connects
MyHealth is highlighted because it provides the common patient experience, but every transaction resolves against an underlying hospital service and produces an auditable state change.
Prototype architecture showing a patient using MyHealth, verified identity, connected hospital services, transaction or result state, and notification/audit.
Implementation
The fictional rollout prioritised high-volume journeys first.
2. Identity & access
Define enrolment, record matching, result-release controls and short-lived access for sensitive information.
3. Service integration
Connect scheduling, billing, payments, results and notification events to the portal.
4. Adoption at the point of service
Use front desk, managed care, laboratory and imaging teams to introduce the digital route where the corresponding physical queue occurs.
Prototype outcome snapshot
What the finished story could quantify.
All figures below are invented for this prototype and demonstrate the level of specificity a published case study should aim for when verified evidence exists.
22,600patient accounts in the first six months
44%eligible outpatient payments completed digitally
31%routine follow-up bookings made through MyHealth
52%eligible results viewed without a return trip solely for collection
Operational effect
The front desk became more useful because fewer routine interactions had to start there.
The fictional impact was visible in the mix of work. Routine payment confirmation, appointment status and result-access questions increasingly moved to MyHealth, while staff spent more time on patients whose situations genuinely needed human intervention.
Patients gained a clearer view of what they could do before arriving, what had been completed and when an approved result was available. Departments gained a consistent digital channel rather than each team creating its own informal communication process.
The most important lesson in the prototype is that adoption is an operational responsibility. Digital usage rose when the same hospital departments that previously handled the physical interaction actively routed eligible patients to the digital alternative.
“We stopped thinking of MyHealth as an app launch and started treating it as another hospital service channel. That changed what every department had to own.”Fictional Chief Operating Officer, Cedarfield Specialist Hospital
Fictional prototype quotation
Related capabilities
Technology behind the prototype.
MyHealth
Patient-facing access to connected hospital services.
Digital Experience
Design the patient journey around clear tasks and service states.
Systems Integration
Connect the portal to authoritative hospital systems.
Digital Payments
Attach payment to the service workflow rather than treating it as a separate transaction.
Next prototype client story
From analyser output to clinical information without re-keying the result.
A fictional diagnostics integration story connecting laboratory instruments, order context, LIS validation and structured result flow.
Read the next story →Story standard
Specific enough to be useful.
Strong V3C stories connect an institutional problem to architecture, implementation and a measurable operational effect.
See the pattern behind the story.
The strongest V3C case studies show the operating problem first, then the system design, implementation choices and verified result.