Compounding, in balance.
One screen from order to label to clean room to ward — fast, exact and private by design.
Chemotherapy, IV admixture, TPN, batch production and non-sterile compounding — every step in one place and every rule in one tested engine.
Response time and screen time are design targets, to be measured in pilots. Zero duplicate postings is enforced by the engine and covered by automated tests.
One table, sortable by any column. Orders still pending validation are visible but locked.
Consumes stock exactly once and prints the label. Pressing again posts nothing.
Dose, pack or generic-equivalent brand, batch, calculation and label preview — no pop-ups.
Sort by drug, select the next round, and print all the labels together.
Choose the day’s lot per product and every preparation inherits it. No batch picking per preparation.
Suggested automatically, with recalled lots blocked.
Every preparation shows whether its lot came from Lot Selection or was chosen by hand.
A touch screen with big targets and only what compounders need. Scan the label when it’s done.
What’s printed and ready to make is on top, what’s next below, and what was sent today on the side.
Today’s team comes first, and the checker can never be the compounder.
Safety is built into the engine, not left to a checklist.
Each preparation consumes stock once. A second press, refresh or network retry posts nothing.
An order edited after its label is printed is quarantined until a pharmacist decides to re-make, discard or release.
Every validated order reaches the worklist. Orders still pending validation are visible but locked.
Rates are calculated before rounding, volumes are never truncated, and a beyond-use date is always printed.
Compounder and checker must be different people. Every step records who and when.
Rounding, precision exceptions and every verification step are settings — not code changes.
4 × 3 in and pure black, made for thermal printers. See the exact label before it prints.
Ingredients in mL, a peripheral vs central osmolarity check, priming volumes and a compounder file export.
Premixes planned, made, checked by a second person and released into stock with lot, beyond-use date and GS1 label.
Magic mouthwash to capsules, made ahead in batches and dispensed per order — earliest expiry first.
Master formulation records with ingredients, method, USP <795> beyond-use date and auxiliary labels.
Mizan runs alongside your hospital information system. Orders flow in, status and stock flow back — physicians and nurses change nothing.
HL7 v2 or FHIR through your integration team. Oracle Health includes Cerner Millennium and i.s.h.med on SAP IS-H.
Published APIs, with access granted by your IT team.
ZPL thermal printing, barcode scanners and documented balance protocols.
If your hospital routes messages through an engine, Mizan plugs into it.
Standard HL7 feeds, usually under the vendor’s interface licence.
Order interfaces agreed and tested with each vendor.
Through the vendor’s own order software, with their validation.
Licensed data feeds.
Logos and product names are trademarks of their owners and identify systems Mizan is designed to connect to. They do not imply partnership or endorsement. Every interface is set up and validated for your site.
Mizan is designed to run on your own servers — no cloud and no internet dependency — with role-based access and a complete audit trail.
Practical articles on IV workflow, chemotherapy dose calculation, beyond-use dates and choosing compounding software.
Mizan is compounding and IV workflow software for hospital pharmacies, made by Tigris Guardians Inc. It covers chemotherapy (CPU), IV admixture (CIVA), parenteral nutrition (TPN), batch production and non-sterile compounding in one system — from the validated order, through lot selection and preparation in the clean room, to labelling and dispatch.
Yes. Every preparation moves through a tracked workflow: pending validation, ready to prepare, label printed, compounding, sent and received. Stock is consumed exactly once, the compounder and an independent checker are recorded, and the preparation is completed by scanning its label.
Doses are calculated from body surface area or, for carboplatin, from the target AUC with the Calvert formula. Dose caps and least-waste vial combinations are applied, cytotoxic preparations carry hazard warnings on their labels, and any order changed after its label is printed is quarantined until a pharmacist decides what happens next.
Yes. TPN ingredients are entered in mL, osmolarity is checked against peripheral and central limits, priming volumes are included, and orders can be exported as a file for an automated compounder.
Yes. Master formulation records hold the ingredients, method, storage and auxiliary labels, with beyond-use dates based on USP <795>. Formulas are made ahead in batches checked by a second person, then dispensed per patient order, earliest expiry first.
Every label shows a beyond-use (“don’t use after”) date. Labels are 4 × 3 in and pure black for thermal printers such as Zebra. Pharmacies choose one of two Mizan label designs or have a label designed to their own policy, and rounding and precision rules are set per unit.
Mizan is designed to connect to hospital information systems — including SAP IS-H with i.s.h.med, Epic and Oracle Health (Cerner) — over HL7 v2 or FHIR, through the hospital’s integration team. Dispensing cabinets, IV robots and TPN compounders connect through each vendor’s own interface, with the vendor’s agreement. Every interface is set up and validated for the site.
No. Mizan is designed to run on the hospital’s own servers, with no cloud and no internet dependency, role-based access and a complete audit trail.
Request one with the form on this page. The demo takes about 60 minutes, runs on a laptop and uses fictitious patients.
A 60-minute live demo on a laptop, with fictitious patients. Tell us a little about your pharmacy and we’ll arrange a time.
We’ll email you shortly to arrange a time for your Mizan demo.