Skip to content
For complex institutions

An operation with many sites is not a bigger clinic

TGMed Enterprise is the same clinical ecosystem, prepared for hospitals and health networks with multiple sites, services and specialties — and for the decisions that only appear at that scale.

Request information See the ecosystem
01 The attributes

What makes it different at scale

Attribute What it means
Multi-site Scheduling, configuration, workflows and productivity per site, plus the consolidated view.
On-premise, cloud or hybrid The architecture is defined to fit the institution, not the other way round.
Parametric Workflows, catalogues and rules are configured; they do not need custom development for every variation.
02 Scale and consolidation

Information moves up a level without losing the detail

Each site runs with its own configuration and, at the same time, the institution sees the whole. Consolidation works at four levels.

Level What it groups
By site The operation of each point of care.
By institution All the sites of a single entity.
Regional Several institutions in one area.
National The complete view of the network.

With centralised administration, and scheduling, workflows, configuration and productivity differentiated by site.

03 Operational continuity

Every site keeps running even if the network fails

It is the least visible difference in a demonstration and the most important one in production. When communication with the central repository is cut, the site does not stop.

  1. The gateway keeps studies locally and the acquisition workflow carries on.
  2. Once communication is restored, the transfer resumes from the last block sent — it does not start over.
  3. Scheduled backups protect the repository according to the institution's policies.
  4. Recovery can be selective or bulk, depending on what needs to be restored.
The four layers of continuity Gateway, queues, protection and recovery. CONTINUITY Four layers to keep running and to recover 1 Gateway Local temporary storage when the architecture requires it. 2 Queues Retries and automatic resumption after an interruption. 3 Protection Cloud backup and protection according to the plan. 4 Recovery Restoration in line with the contracted scope. The scope of each layer is defined by the architecture and the contracted plan.
The four layers of continuity. The scope of each one is defined according to the architecture and the contracted plan.
04 Multi-site architecture

How the sites connect

TGMed Enterprise multi-site architecture Several sites, each with its local gateway, consolidating into a central repository with centralised administration, plus a continuity layer with backup and recovery. TGMED ENTERPRISE · MULTI-SITE ARCHITECTURE Every site keeps running even if the network fails Main site Modalities Laboratory Consultation Gateway Branch Modalities Laboratory Gateway Diagnostic centre Modalities Gateway CENTRAL REPOSITORY Consolidation by site by institution regional national Centralised administration CONTINUITY Scheduled backup Selective recovery Bulk recovery Synchronisation across repositories Operation during contingencies The gateway keeps studies locally when communication with the central repository is cut, and resumes the block transfer from the last block sent once it is restored.
The gateway keeps studies locally when communication with the central repository is cut, and resumes the block transfer from the last block sent once it is restored.
05 How it connects

It integrates with what your institution already has

  • HL7 and FHIR for exchange with hospital information systems and electronic health records.
  • REST APIs for integration with institutional and third-party systems.
  • Multi-vendor DICOM, handled natively and with no proprietary formats.
  • Multi-vendor analysers in the laboratory.
  • Institutional authentication, so access is administered from where it is already administered.
  • Local, SAN, NAS or cloud storage, including hybrid architectures.
06 Applied artificial intelligence

Two concrete uses, not a promise

Automatic capture of results from PDF documents

In LIS. It recognises the parameters, matches them to the corresponding tests and validates before recording, with an audit trail of the process and a record of where the capture came from.

Automatic transcription of voice notes

In Radiology. The technologist dictates and the system transcribes.

07 What is included

The seven modules of the ecosystem

The process is the same as in IRRAD Cloud. What changes is how it is implemented.

  • Q-Flow
  • Q-Pay
  • Radiology
  • LIS
  • Clinic
  • V-Med
  • Video Quirúrgico

On top of that, two components specific to this edition implement the continuity layer: Sync Gateway, which synchronises and consolidates DICOM studies across sites and repositories, and Continuity Enterprise, which manages backups, recovery and scheduled tasks.

See the full ecosystem
08 Service level

The service level is agreed with each institution

We do not publish a standard table of commitments, because a hospital network with five sites and a diagnostic centre with one do not need the same thing. Support hours, response times and the escalation path are defined during the negotiation, according to how your institution actually operates and how critical it is.

Let's talk about your service level

Let's talk about your institution

Tell us how you operate today: how many sites, which services, which systems you already have running.

Request information Compare with IRRAD Cloud