A connected foundation for the whole story of care.
Explore the plan to build Medrella from scratch with Schedula as its foundation, connecting clinical care and hospital operations.
Explore the story
Planned core Medrella workflows, to be built from scratch using Schedula as the foundation. Availability requires development and demonstrated acceptance.
Begin with the work of a hospital
Medrella is planned as a new product built from scratch, using Schedula as its foundation. The starting point is the journey of care: arranging a visit, understanding the patient, recording the consultation and following through on the next step.
Clinical records and hospital operations will be developed around that journey, with each capability given an explicit scope and acceptance plan. Our ambition is a more supportive experience for staff, patients and caregivers. This website describes the product direction; it does not establish that the proposed clinical workflows have already been built or validated in a hospital.
Keep the clinical and commercial records connected
A clinical encounter, a service request and an invoice describe different events. They need to share context without becoming interchangeable.
The planned Medrella design connects purpose-built clinical records with hospital administration, including billing, purchasing, stock and assets. These capabilities require development and validation. The implementation should define how clinical activity leads to fulfilment and financial records, including corrections and cancellations. A bill does not prove that a service occurred, and a completed clinical task does not by itself establish payment. Preserving those distinctions makes the platform easier to reconcile and gives each department a clearer account of its responsibilities.
Design the depth that care requires
A useful clinical platform needs more than a basic outpatient chart. The roadmap includes therapy plans and sessions, procedure records, nursing tasks, medication requests and insurance administration.
Each area deserves discovery with the people who perform the work. These are planned capabilities, with requirements, implementation and acceptance still to be established for each release. Patient access and medication-related assistance need their own review boundaries, permissions and clinical ownership. The development catalogue should show those dependencies clearly so a hospital can understand the proposed sequence without assuming that a broad platform description proves current availability.
Add intelligence to dependable workflows
AI assistance is most useful when the underlying records, permissions and responsibilities are already clear. A drafted note needs an encounter and a reviewer.
An extracted report needs a source document and a patient match. A voice booking needs an authoritative schedule and a reliable confirmation. Medrella's planned AI capabilities build around these relationships. They should reduce clerical work without obscuring who approved a clinical record or authorised an action. New functionality must be evaluated in the workflow where it will be used, including the manual path when assistance is unavailable or unsuitable.
Make scope inspectable
During discovery, distinguish the Schedula foundation, new Medrella development, proposed external connections and workflows that have passed acceptance.
Walk through the actual release and the settings that matter to the hospital rather than relying on a broad product label. Agree acceptance scenarios across clinical and operational teams, including exceptions and corrections. This creates a practical basis for a phased rollout and for deciding which extensions add the most value. The goal is a hospital platform that can grow without losing the clarity of its records or the trust of the people who depend on them.
Purpose-built workflows.
A clear development plan.
Consultation to action
Planned encounter records, prescriptions and investigation requests will connect the consultation to the next team's work.
Explore the planned workflowA plan across many sessions
Planned therapy records will connect goals, scheduled sessions and assessments while preserving clinical ownership of progress.
Explore the planned workflowPatient and caregiver participation
Patient access, Android participation and caregiver permissions are planned product work, with explicit authorisation and release boundaries.
Explore the planned workflowOrders with clinical ownership
Planned prescribing and fulfilment workflows need clear approvals, correction history and professional review before clinical use.
Explore the planned workflowConnected thinking.
What would more time
for care make possible?
Let's explore it together