THE ENGINE
The orchestration layer underneath everything.
The Routina AI Enablement Engine is what makes agents work across a fragmented stack. It connects to your existing systems (EHRs, pharmacy and lab systems, payer portals, TMS, WMS, accounting, messaging) and runs agents on top of them. It's model-agnostic by design: the reasoning layer is swappable, so you're not locked to one AI vendor's roadmap. Your prompts, your data, your workflows stay yours.
No migration. Routina reads and writes where your data already lives.
Connects without migrating
Routina reads from and writes to the systems you already run. No data migration, no replatforming, no rip-and-replace. If your team knows the tool today, they keep using it tomorrow.
Agents with defined roles
Each agent owns a scope of work — not a chat window. Role-based access means the right people interact with the right agents, and the agent keeps context across every person who touches it.
Model-agnostic by design
The reasoning layer is swappable. When a better model ships, you switch. Your workflows, prompts, and integrations don't change. No vendor owns your AI layer but you.
Audit trail by default
Every agent action logged with who, what, when, and why. Not a feature you enable — a condition the platform was built under, because it was built inside a healthcare operation first.
APPS BY ROUTINA
Four packaged healthcare operations, built on the Engine.
Apps ship with pre-built agents, integrations, and workflows for a specific kind of operation. Deploy one, deploy several — they run on the same Engine and share the same data layer.
Imports & 3PL Management (3PMS)
FOR HEALTHCARE DISTRIBUTORS SHIPPING THROUGH THIRD-PARTY WAREHOUSES
Procurement through last-mile, tracked as one chain. Consolidation management, freight forwarder coordination, customs document assembly, warehouse activity mirroring, and delivery SLA monitoring. Routina isn't the system of record for inventory — it mirrors your 3PL's WMS so agents can act on it without replacing it.
Routes documents between supplier, freight forwarder, customs broker, and 3PL — validates the customs liquidation report and assembles the single customs packet before arrival, instead of chasing it after.
Explore app →
Last-Mile Order Management (LOMS)
FOR PHARMACY, SPECIMEN AND MEDICAL SUPPLY DELIVERY OPERATIONS
Order intake from API, email, or manual entry. Normalization, routing, pricing, and handoff to DMS or your TMS. Per-client and grouped routing parameters — route a zone of independent pharmacies together to maximize density. Client invoicing rules, locations management, and support handling with agent-assisted resolution.
Orders arrive by API, email, and phone. The app normalizes all three into one queue, applies each client's routing and pricing rules, and hands off to DMS or your TMS — dispatchers stop retyping.
Explore app →
Driver Management (DMS)
FOR HEALTHCARE COURIERS, 3PLS AND IN-HOUSE DELIVERY FLEETS
The drivers behind every delivery. Fleet and contractor roster, on-demand recruitment when volume spikes, credential and compliance tracking, live route monitoring, validated proof of delivery, and driver pay. Picks up where LOMS hands off and sends status and POD back.
Finds tomorrow's uncovered routes, offers them to qualified contractors, holds any driver whose insurance lapsed, and sends an incomplete proof of delivery back to the driver while they're still at the door.
Explore app →
Home Care Management (HCMS)
FOR HOME CARE AGENCIES · HOME HEALTH · RPM PROGRAMS
Patient intake, visit scheduling, nurse dispatch, remote patient monitoring, clinical documentation, and family communication. BAA available — the compliance posture came from running healthcare operations, not from a checklist.
Reads overnight vitals across the enrolled panel, flags what's outside threshold, contacts mild cases directly, and escalates the critical ones to nursing with the chart already pulled.
Explore app →
COMPOSITION
The AI Enablement Engine runs the agents. The apps shape the work.
Every deployment starts with the Engine. Apps layer on top based on what your operation actually does. Most customers run one or two; some run the Engine alone with custom agents built for workflows we haven't packaged yet.
Each industry page goes deeper on what deployment looks like in that operation. See industries →
COMPLIANCE
Built under real constraints, not added later.
The platform was built inside a healthcare operation handling PHI under real audits. Every app inherits that posture.
Encryption by Default
Encryption at rest and in transit. PHI access controls and logging on by default, not toggles you turn on later.
BAA Available
Standard BAA available on any tier. Custom BAA review for Enterprise.
Role-Based Access
Every agent action scoped by user permission. The dispatcher sees what they need, the clinician sees what they need, the auditor sees what they need.
Your AI Layer, Yours
Model-agnostic and portable. Your prompts, your data, your workflows stay under your control — not embedded in a vendor's roadmap.