The patient story starts before the consultation.
A dependable identity and a well-prepared arrival give every department a better place to begin.
Explore the story
Planned core Medrella workflows, to be built from scratch using Schedula as the foundation. Availability requires development and demonstrated acceptance.
What this workflow connects.
The scope below guides discovery and demonstration. The adopted version and local configuration determine availability.
- 01
Patient demographics and local identifiers
- 02
Returning-patient search and encounter context
- 03
Contact details and authorised relationships
- 04
Registration corrections and duplicate review
- 05
Connections to appointments, clinical records and billing
An arrival is more than a new record
The front desk is often the first place where a fragmented patient journey becomes visible. A returning patient may have an old registration number, a changed phone number and reports from another facility.
A relative may be speaking on their behalf. The purpose of registration is to establish the right person and encounter without turning that moment into an interrogation. Medrella builds on documented patient records to create a shared starting point for appointments, clinical encounters and financial activity. The design question is not simply which fields to collect, but which details help the next person deliver care.
Make identity useful across departments
Patient identity, an appointment and a bill represent different things. Keeping those distinctions clear allows one person to return for several visits without acquiring unrelated charts.
Reception should be able to find the existing record, confirm the details that matter and create the appropriate visit. Clinical teams then receive the same context when they open the encounter. Duplicate detection and record-merging decisions need explicit review rules: two people with similar names are not the same patient, and a shared family phone number is not a reliable identity on its own. Local identifiers and external health IDs require deliberate mapping.
Design for the person at the desk
Good registration supports the ways people actually arrive: booked visits, walk-ins, referrals, repeat treatment and family-assisted care. The front-desk view should make the immediate next step clear without exposing unnecessary clinical information.
Contact preferences, language needs and authorised contacts can support communication, but each has a different purpose from clinical consent. A caregiver who can arrange a visit may not be entitled to read every record. These permissions belong in the workflow from the beginning. Where connectivity or identification is incomplete, teams need an agreed exception process that keeps care moving and leaves work visible for later reconciliation.
Connect registration to the next handoff
A completed form is only useful if it reaches the next step. The arrival workflow should connect the patient to the correct practitioner, service, queue and payment context.
Existing appointments should be matched rather than silently recreated. A change to contact details should not overwrite an unrelated demographic field or erase history. During discovery we map where information is entered, who corrects it and which connected system is authoritative. Medrella plans to build patient registration and appointment handoffs on Schedula; local queue displays, external identity services and other integrations will be assessed separately. The walkthrough should follow a returning patient all the way into the consulting room.
What a convincing demonstration should show
Bring examples that challenge a perfect-path demonstration: two patients with the same name, a family sharing one number, a patient without a prior identifier and an appointment made by someone else.
Ask staff to find the record, correct an error and trace the correction. Check which roles can see contact details, financial information and clinical attachments. Measure repeated questions and avoidable re-entry before setting an improvement target. The release scope should state what has been configured, what is still manual and how unresolved registrations are handled. Foundation here describes planned core product work; the exact Medrella workflow must be built and demonstrated with your team.
Connected thinking.
What would more time
for care make possible?
Let's explore it together