Platform Overview
This page is the map of Tietai: how data moves through the platform, where each area is in the sidebar, which page documents it, and how mature each part is.
How the pieces fit together
Read it left to right and match it to the sidebar:
- Your systems (hospital systems, devices) send messages.
- Tiet · Connect receives them. Network → Pipes handles message channels and Device Fleet handles wearables and devices.
- Patient data lives in the FHIR server, which you browse under Tiet · Govern → FHIR Server.
- Tiet · Studio workflows and Tiet · Agentic agents read and process that data. Agents can run as nodes inside workflows.
- Apps (clinical applications) and Tiet · Govern (knowledge, imaging, dataset publication) put the results in front of people and control access.
Every area is scoped to the active organization and gated by permissions. See Key Concepts.
The sidebar map
The sidebar has six groups. An item appears only if your organization has the module and you hold one of its permissions, so your sidebar may be shorter.
| Group | Item | Sub-items |
|---|---|---|
| Tiet · Hub | Home | One entry per dashboard workspace of your organization |
| Analytics | Boards | |
| Platform | Monitor, Projects, Connectors, Egress policy, Environments | |
| Apps | Tiet · Consult, Tiet · Scribe, Patient Screening, Voice Workflows, Medical AI / Clinical Reasoning, Tiet · Coding, Clinical Processes, Tiet · Documents | |
| Tiet · Connect | Network | Mesh, Pipes, Messages & DLQ, Transformers |
| Device Fleet | Devices, Providers, Enrollment, Alerts, Automations, Settings | |
| Tiet · Studio | Workflows | Workflows, Monitor |
| Tiet · Agentic | Agents | Agent Workspace, Agents, Monitor, Reviews |
| Compliance | Systems, Policies, Gate, Watch, CAPA, Audit | |
| Tiet · Govern | Knowledge | Libraries, Documents, Web, Query |
| FHIR Server | Explorer, Editor, Patients, Server | |
| Records Viewer | DICOM Studies, DICOM Viewer, ECG / Holter, Labs | |
| EHDS Studio | Overview, Publish Dataset, My Work, Datasets, Sources, Setup & Admin, Public Catalogue | |
| System | Admin Console | Opens its own menu: Account, Organization, Platform, Security |
| Help & Support |
The Agents page has its own tabs for Agents, Agent Graphs, Agent Catalog, Models, Tools and Skills.
What each area does
| Area | What it does | Page |
|---|---|---|
| Home | Greeting, one shortcut per enabled module, dashboards, monitor tiles, service health, recent work | Using the application |
| Analytics | Dashboards and Boards | Analytics dashboard |
| Platform | Projects, Connectors, Egress policy, Environments, platform monitor | Tiet · Studio and Tiet · Agentic, Connector directory |
| Apps | Clinical applications | Tiet · Consult, Using the application |
| Network | Message pipes, mesh, dead-letter queue, transformers | Tiet · Connect, Run on Mesh |
| Device Fleet | Wearables and device data | Wearables and IoT |
| Workflows | Visual workflow builder and run monitor | Tiet · Studio Builder, Environments and promotion |
| Agents | Agents, agent graphs, models, tools | Agents and governance, Create agents |
| Compliance | AI system inventory, policies, release gate, drift watch, audit | Agents and governance |
| Knowledge | Knowledge libraries, documents, web sources, query testing | No dedicated page yet |
| FHIR Server | Browse and edit FHIR resources, patients, server operations | FHIR and interoperability, Manage patients |
| EHDS Studio | Governed health-data catalogue records | EHDS Studio |
| Admin Console | Profile, organization, users, roles, secrets, SSO, audit | Administration |
A message becomes FHIR data
The path below is the one you can build today with the workflow engine's own HL7 listener. An HL7 v2 message arrives on the workflow engine MLLP port (default 2575, set by MLLP_PORT). The workflow engine looks for saved workflows that contain an hl7-listener node on that port and runs them. A typical workflow chains hl7-to-fhir and fhir-crud.
Things that surprise people:
- A message that no workflow listens for is rejected with
ARby default (theMLLP_NO_ROUTE_ACKsetting can change the code). A message that every listener filters out is acknowledgedAAand ignored, unless the listener setsnack_on_filter(thenAR). hl7-to-fhirmaps Patient and Encounter. For a test ADT^A01 message the visit number, next of kin, allergies and diagnoses were not mapped; the node lists unmapped segments in its result.- Every message creates new resources (the Bundle uses POST). Nothing is matched or updated.
- Patient matching is not part of this path. The master patient index is a separate node (
empi) that you add to a workflow yourself. - Connect pipes can also receive HL7 on a TCP/MLLP source. The capability matrix lists the TCP/MLLP listener as generally available.
Maturity at a glance
See Capability status for the shared availability table, node maturity counts and verification dates. Check the documented limitations for the feature you plan to use.
Next steps
- Quick Start: sign in and look around
- Key Concepts: workflows, nodes, ports, connectors, executions
- Your First Workflow: build something real
Something unclear? Send documentation feedback by email.