Loading...
← All work
Case study · PassageDelivered
Treatment abroad, run as one journey every party can trust.
A platform that carries a patient across borders: consent, documents, partner hospitals, field staff on the ground, and a wallet, all on one auditable timeline.
- Sector
- Travel & Healthcare Coordination
- Our role
- Workflow platform, consent and audit architecture, web app, CI/CD
- Capabilities
- Platforms
- Status
- Delivered
The challenge
Treatment abroad is a chain of hand-offs, and every hand-off can stall.
Treatment abroad is a chain of hand-offs between patients, hospitals, agents and local staff, and every hand-off is a place for a case to stall. Passage models the whole journey so each party sees what they need and nothing more.
What made it hard
- 01
Multi-party state
Patients, hospitals, agents and field staff each own one part of a case that has to move as one.
- 02
Regulated data
Medical records and payments both demand a provable answer to who did what, and when.
- 03
Durable consent
Consent must be versioned and bound to the record, not a checkbox that disappears.
The approach
One case, one state machine, and an audit log on every action.
Each case advances through explicit stages on a single timeline. Consent is versioned data attached to the record, every sensitive read and write is audit-logged, and role-scoped views give each party only their slice. Schema changes ship through Alembic migrations on a CI/CD pipeline.
System map
- AI step
- Person in the loop
- Service or store
How it works
- 01
Enquire
A patient registers, verifies by one-time code and records explicit consent.
- 02
Prepare
Medical history and documents are collected and checked.
- 03
Match
A case is assigned to a partner hospital and a field coordinator.
- 04
Travel
The journey advances through stages, with notifications at each one.
- 05
Settle
A wallet tracks payments and refunds, and every action lands in an audit log.
Key decisions
Built for questions that need answers.
Decision 01
Consent is data
It is versioned and attached to the record, not a checkbox that disappears.
Decision 02
Audit by default
Every sensitive read and write is logged, because health and money both demand an answer to “who did this”.
Decision 03
Role-shaped views
Patients, partners and field staff see different slices of one case.
What shipped
One auditable journey, from enquiry to the flight home.
Verified onboarding
OTP verification and explicit, versioned consent capture.
Document intake
Medical history and documents collected and validated.
Case assignment
Matched to a partner hospital and a field coordinator.
Stage-driven workflow
Each stage transition triggers notifications to the right parties.
Wallet and audit log
Payments and refunds tracked, with every action recorded.
Architecture
A cross-section of the system.
Every layer, from what people touch down to where it runs, and the one job each layer does.
L1Interface
React+TypeScript
Role-scoped views for patients, partners and field staff.
L2Services
FastAPI+SQLAlchemy
Case state machine, consent and wallet APIs with audit hooks.
L3Data
Alembic
Versioned schema migrations for a regulated data model.
L4Infrastructure
Nginx+Docker+CI/CD
Containerised services behind a reverse proxy, shipped by pipeline.
Our scope
Workflow design/Consent and audit architecture/API design/Web application/CI/CD
Where it is now
Delivered, with an audit trail on every action.
Passage is delivered. Every action lands in an audit log, so any question about a case has a verifiable answer.
Something like this in mind?
Tell us the problem. We will tell you honestly if we are the right team to solve it.