Connect the prescription to the medicine in hand.
Bring clinical requests, dispensing activity and pharmacy stock into a coordinated workflow.
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
Prescription-linked dispensing workflow
- 02
Medicine items, batches and expiry dates
- 03
Purchases, stock movement and ward supply
- 04
Partial fulfilment, returns and reconciliation
- 05
Planned stock and financial connections
Clinical and stock information meet at the counter
The pharmacy sits between a clinician's instruction, a patient's needs and the physical availability of medicines. Those perspectives are related but not interchangeable.
A prescription is not a stock transaction, and an item on a shelf is not necessarily the medicine intended for a particular patient. Medrella's roadmap brings healthcare records together with planned stock and purchasing workflows, to be built and validated for the hospital's needs. The implementation work is to connect them carefully around the hospital's dispensing process. A useful system helps the pharmacist see the relevant instruction and inventory context without hiding the decisions that require professional review.
Keep the medicine catalogue dependable
Catalogue quality shapes almost every pharmacy interaction. Names, strengths, dosage forms, pack sizes and units must be consistent enough for prescribing, purchasing and stock movement.
The same product may be purchased in one unit and dispensed in another. Batch and expiry information need to follow the physical stock rather than being treated as optional text. Local formulary and substitution policies should be explicit, and the responsible professional should retain control over decisions affecting the patient. During discovery, examine actual catalogue duplicates and unit conversions; a clean demonstration catalogue can conceal the work needed for a real hospital pharmacy.
Record fulfilment and exceptions clearly
A prescription may be fulfilled completely, partly or not at all. The dispensing record should make that outcome understandable to the patient and the care team.
An unavailable item, a clarified instruction and a return require different actions. Where inpatient medicines are issued to a ward, the stock issue should not be confused with documented administration to the patient. Financial posting should reflect the agreed process for dispensing, returns and credit. These distinctions support traceability and reduce reliance on informal notes. Any proposed automation should preserve review points and make unresolved work visible rather than silently treating a partial action as complete.
Plan replenishment around the actual service
Purchasing and stock control should help the pharmacy maintain availability without obscuring expiry or consumption patterns. Reorder levels, supplier lead times and the needs of different stores require local configuration.
A central store and a ward stock location have different responsibilities even when they share a catalogue. Transfers should be recorded as movements rather than recreated purchases. AI-assisted operational insights are planned and would need to explain the data behind a suggestion. The core implementation should first establish reliable stock records, purchase approval and reconciliation. Predictive language is not a substitute for accurate inventory and a responsible replenishment process.
Demonstrate from prescription through reconciliation
Evaluate the pharmacy workflow with a partial dispense, a batch approaching expiry, a return and a medicine unavailable in the expected location.
Ask staff to trace the clinical request, the stock movement and the financial consequence. Review permissions for catalogue changes, substitutions and adjustments. Check whether a corrected prescription reaches the person who is fulfilling it. The release scope should identify which steps have been built and demonstrated and which still require development, configuration or integration. Success should be assessed through reconciled transactions and staff usability, not a claim that every commercial pharmacy feature is automatically present in Medrella.
Connected thinking.
What would more time
for care make possible?
Let's explore it together