Handoffs by hand
Teams copy, check and reconcile the same case across systems, inboxes and spreadsheets.
Tiet · Studio
Turn manual handoffs into approved workflows your team owns.
System friction
Your data is digital. The work between systems is still manual.
Pilots that never ship
Scripts break when a screen or format changes, and generic AI pilots can't reach production systems.
No evidence trail
Every site runs the process differently, and approvals and exceptions are hard to show later.
How it works
Compose the process. Review the release. Run it with evidence.
Compose the process step by step.
Wire triggers, standards, transforms, agent, retrieval and audit steps on one canvas. Workflows act on live, normalised data from Tiet · Connect.
Read the docs (opens in a new tab)
Build from 170+ healthcare node types.
Extraction, validation, reasoning, export and review-gate steps in 16 categories, plus documented reference pipelines to start from.
Read the docs (opens in a new tab)
Release only what was reviewed.
Each workflow moves from draft to review to approved, with node tests, safety and policy checks and a changelog. The version you tested is the one that runs.
Read the docs (opens in a new tab)
See every run, step by step.
Inspect the workflow version, inputs, outputs and step log of each run. Retries, timeouts and circuit breakers contain failures, and any run can be replayed.
Read the docs (opens in a new tab)
ISO/IEC 27001Certified
Certified · HighUse cases
Start with one process your team can measure.
Referral intake
Classify and extract any referral document, check coverage and prepare the routing. A person confirms.
Prior authorisation
Assemble the evidence, check payer rules and draft the submission for your team to approve.
Discharge coordination
Run a fixed, versioned pipeline that drafts the discharge summary and holds automatically on any deviation.
ADT processing
Validate admission, discharge and transfer events, check PHI and convert them to FHIR with care-team notifications.
FHIR to OMOP export
Convert cohorts to OMOP CDM 5.4, de-identify them and export them for research.
Eligibility checks
Check eligibility and coverage across systems and route the exceptions to your team.
Operational answers
What teams ask before their first workflow.
Do we need developers to build a workflow?
You build workflows on a visual canvas from ready-made healthcare nodes, so most of the work is configuration, not code. Your IT team connects the source systems, and developers can call approved workflows through the API.
How long does a first workflow take?
An example plan runs six weeks: define, connect, compose, validate and go live, each with an exit criterion. Your source access, review and release readiness set the actual schedule.
How do you control the AI steps in a workflow?
Sandbox policies apply at every node, agent and tool boundary, and approval gates hold consequential steps until a person signs off. Agent configuration and AI-system risk are governed in Tiet · Agentic.
Is Tiet · Studio a medical device?
No. Tiet · Studio is workflow infrastructure with no medical purpose on its own. The intended purpose of each workflow you configure determines its regulatory route, and health institutions can build and use their own workflows under Article 5(5) of the EU MDR where its conditions are met.
