The journey has dependent stages
Instructions, consent requests, and dates reach the patient through separate channels.
Interactive demonstrator
Patient journey portalCoordinate stages, documents, and decisions across a multi-stage patient journey
For the owner, operations manager, and coordinator of a private clinic. The demonstrator shows an example 12-step configuration for instructions, consent, tests, results, visits, documents, and follow-up. Within the offered scope, qualification and result interpretation remain with an authorized doctor.
Target interface concept
123456789101112
✓Consentrecorded
!Test resultsmissing
→Doctor reviewwaiting
Medical decision → authorized doctor
Fit check
This is worth mapping when…
Completeness is checked manually
Tests and documents arrive as PDFs, emails, or records in another system.
The team repeats the same follow-up
Coordinators call and write to explain status, collect missing items, or prompt the next step.
Workflow
From repeated handoffs to visible states.
Today
- 01First contact
The patient calls or submits a form and receives instructions separately.
- 02Consent and documents
Required items arrive through different channels and systems.
- 03Readiness check
A coordinator checks completeness before the doctor’s decision.
- 04Decision and follow-up
The clinic communicates next steps through calls and messages.
Target workflow
- 01
The team creates a patient view and assigns the agreed journey.
- 02
The patient sees the active stage, instructions, and items required to move forward.
- 03
A coordinator or agreed integration updates the visible state of consent, tests, results, visits, documents, or payments and records the source of the change.
- 04
A missing item or deadline may trigger an agreed reminder or escalation in the target system; the demonstrator shows this pattern.
- 05
The doctor makes the decision while the portal records state and presents the next instructions and follow-up.
Workflow modules
Each module is defined by a specific job.
See where the patient is
The dashboard shows their position in a 12-step journey.
Establish consent state
The demonstrator shows consent transitions without e-signature.
Check document readiness
Tests, results, and documents are grouped by visible state.
Connect the stage to a visit
Visits appear in the context of the journey rather than as an isolated calendar.
Show payment state
The UI model places payments beside other process elements.
Show how a missing item or delay is handled
The demonstrator shows reminder, escalation, history, and message patterns for exceptions.
Operating change
What changes for the person doing the work.
AreaBeforeAfter
InstructionsPhone, form, and separate messagesInstructions assigned to a visible stage
CompletenessManual checks across PDFs and systemsRequired-item states in one view
DecisionManual handoff to and from the doctorVisible handoff; the doctor makes the decision
Follow-upCalls and messages tracked manuallyReminder, escalation, and history patterns
Data and responsibility
Inputs, state changes, and exception paths.
Data and states
The model covers patient data, 12 stages, and states for consent, tests, results, visits, documents, and payments.
Missing integrations
Backend, authentication, roles, e-signature, SMS, and HIS/EMR connections require separate scope and validation.
Responsibility
Missing documents go to a coordinator; within the offered scope, qualification and result interpretation remain with a doctor.
Measurement
No target before the baseline.
The pilot compares the same workflow and keeps quality guardrails visible.
Organizational contacts per patient
Status, timing, or missing-item calls and messages / patients in the cohort.
- Baseline
- Missing — measured before pilot
- Data
- Telephony and messages; then portal history
- Comparison
- Comparable journeys before and during pilot
- Guardrail
- Unresolved missing items do not rise
- Review
- Frequency and owner agreed before pilot
- Decision
- A guardrail breach pauses the pilot; repair or scale follows review
Manual follow-up minutes
Coordinator time spent checking completeness and reminding / patient.
- Baseline
- Missing — measured before pilot
- Data
- Work sample and activity log
- Comparison
- Baseline vs pilot for the same journey
- Guardrail
- Document quality and corrections do not worsen
- Review
- Frequency and owner agreed before pilot
- Decision
- A guardrail breach pauses the pilot; repair or scale follows review
Late preparation exceptions
Missing items found after coordinator readiness confirmation / all journeys handed forward after that confirmation.
- Baseline
- Missing — measured before pilot
- Data
- Record audit and pilot events
- Comparison
- Same procedure, location, and control point
- Guardrail
- Incorrectly marked complete cases do not rise
- Review
- Frequency and owner agreed before pilot
- Decision
- A guardrail breach pauses the pilot; repair or scale follows review
Implementation
A bounded path from evidence to rollout.
- 01
Discovery
Map one journey, roles, decisions, and data sources.
- 02
Baseline
Measure contacts, manual work, and late missing items.
- 03
Prototype
Adapt stages, states, and messages.
- 04
Integrations
Design backend, roles, and selected connections.
- 05
Pilot
After privacy, security, and responsibility gates, run a bounded journey with manual fallback and doctor review.
- 06
Rollout
Expand after reviewing KPIs, exceptions, and clinic-specific requirements.
Proof and limits
What exists today, and what still needs validation.
Verified in the current material
- The published demonstrator includes a patient dashboard and 12-step journey.
- It shows consent states plus UI models for tests, results, visits, documents, and payments.
- Reminder, escalation, history, and message patterns are visible.
Not yet evidenced
- It is not an EMR, does not diagnose, and does not replace a doctor. It is not evidence of universal legal compliance.
- There is no production backend, auth, roles, e-signature, SMS, or HIS/EMR integration. Outcomes remain pilot hypotheses.
Next step
Let’s map one patient journey
We will define states, human decisions, exceptions, data, and the scope of a safe pilot from first contact to post-treatment care.
Start with the workflow