Carry clinical intent into the next action.
Connect investigations, medicines and procedures to the encounter that gives them meaning.
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
Service and medication requests
- 02
Test and procedure catalogue selection
- 03
Dose, route, frequency and duration context
- 04
Order changes, cancellation and fulfilment status
- 05
Connections to laboratory, pharmacy and invoicing
An order is a clinical handoff
An investigation request or prescription is more than a line item. It carries the clinician's intention into another workflow, where a laboratory, pharmacist or procedure team must interpret and fulfil it.
When that context is lost, staff compensate with calls, notes and repeated questions. Medrella plans service and medication requests to connect the order with the patient and encounter. The design should make the requested action, its status and the responsible team visible. It must also preserve the distinction between a request, a completed service and a result that has been reviewed.
Support deliberate prescribing
The prescribing workflow should help clinicians record the intended medicine, relevant instructions and duration without hiding important choices behind defaults. Medicine catalogues, units and local formulary rules need careful configuration.
A familiar product name may represent more than one strength or presentation, and substitutions need an explicit policy. Any alerts or assistance should be evaluated for their actual scope and usefulness. This website does not claim that Medrella has a validated interaction checker or autonomous prescribing capability. The clinician remains responsible for the prescription, and changes made after approval need clear attribution and a reliable route to the dispensing team.
Follow investigations beyond submission
Once a request is placed, the next question is whether it has been accepted, scheduled, collected or completed. Those states differ by service.
A laboratory order may require a specimen; an imaging request may require a scheduled appointment and preparation. Cancellation needs to reach the team performing the work, and an amended result needs to reach the responsible reviewer. A connected system should prevent the requesting encounter from becoming a dead end. Critical-result handling, acknowledgement rules and escalation timelines must be defined with the hospital. They should not be inferred from a generic order status or an unread notification.
Agree the interfaces and financial consequences
Clinical requests often connect to billing, pharmacy stock and external devices.
Those connections need explicit ownership. A requested service is not necessarily a chargeable completed service, and a cancelled request may have different consequences before and after work has begun. During implementation, map order identifiers, fulfilment states, catalogue codes and reconciliation rules between systems. Existing service and medication records provide a foundation; analyser, PACS, pharmacy or insurer interfaces require separate assessment. Start with a small set of frequently used requests and verify the complete lifecycle before scaling the catalogue. The exception handling is where confidence in integration is earned.
Test the lifecycle, including correction
A useful demonstration follows an order from creation through fulfilment, review and any resulting patient communication. Add a cancellation, a corrected instruction, an unavailable medicine and a result arriving after discharge.
Check who can amend each record and how the receiving team learns about the change. Evaluate whether clinicians can see outstanding requests without relying on memory. Measure reconciliation effort and unresolved orders using your own baseline. The aim is to make clinical intent easier to act on while keeping responsibility explicit. Planned AI may help prepare or organise information, but it must not silently create an approved prescription or final clinical instruction.
Connected thinking.
What would more time
for care make possible?
Let's explore it together