Let every visit build on the last.
Bring the patient's history, today's conversation and the next care plan into a coherent clinical workspace.
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
Encounter history, vital signs and attachments
- 02
Complaints, diagnoses and configured medical codes
- 03
Medication prescriptions and investigation requests
- 04
Clinical procedures and therapy prescriptions
- 05
Clinician-reviewed records and patient instructions
Continuity changes the consultation
A returning patient should not have to reconstruct their history from memory at every visit. The clinician needs an understandable account of previous encounters, relevant observations, current medicines and unresolved plans.
More information is not always more useful: a crowded screen can hide the detail that matters today. Medrella's outpatient direction starts with longitudinal context and a purposeful encounter record. The planned clinical scope includes patient encounters, observations, diagnoses and clinical requests, developed around the scheduling foundation provided by Schedula. The implementation work is to organise those building blocks around how your clinicians prepare, consult, document and arrange the next step, without treating every specialty as an identical form.
Prepare the record before the conversation
Preparation may include confirming the visit reason, reviewing earlier reports and recording observations collected by the care team. These activities need clear attribution and timing so that the clinician can distinguish today's findings from historical information.
A copied note should never look like a newly observed fact. External documents should retain their source and date, and structured summaries should link back to the material from which they were prepared. The workspace should support rapid orientation while preserving the detail needed for a careful review. Patients with repeated visits benefit when outstanding requests and follow-up intentions remain visible between encounters.
Document in the language of the specialty
A general medicine visit, an ophthalmology assessment and a rehabilitation review have different documentation needs. Configurable encounter templates can reduce unnecessary navigation, but their content must be agreed with clinicians who will use them.
The goal is not to force a narrative into a collection of checkboxes. Structured fields are valuable where consistency supports ordering, reporting or follow-through; free text remains important for reasoning and context. Voice-assisted drafting is part of the planned AI roadmap. Any draft must remain distinguishable from approved documentation, with the clinician able to correct, reject and approve it before it becomes part of the clinical record.
Make the care plan actionable
The end of the consultation creates work for several people. Investigations may need scheduling, prescriptions need review and fulfilment, and the patient needs to understand what happens next.
A connected encounter should carry the context into those tasks rather than sending the patient between counters with disconnected instructions. A follow-up intention should be distinguishable from a confirmed booking. Patient-facing explanations should use clinician-approved information and avoid silently introducing new advice. Where a caregiver is involved, the shared plan should respect the patient's permissions. The important measure is whether each next step has a clear owner and an understandable status.
Demonstrate clinical continuity with your own scenarios
An EMR evaluation should include a returning patient with several encounters, an external report, a changed medicine list and an unfinished investigation.
Ask a clinician to prepare for the visit, document the current consultation, amend an error and produce the next plan. Examine attribution, access permissions and what the patient receives. Specialty templates, terminology, integrations and migration depth should be explicitly scoped. Website illustrations show the intended experience, not an acceptance-tested clinical application. The most useful proof is a clinician completing a realistic journey and explaining where the record helped, where it distracted and what must change before rollout.
Connected thinking.
What would more time
for care make possible?
Let's explore it together