TMP is built to reduce hospital integration cost to a minimum by integrating at the EHR layer. Hospitals can connect once and give HCPs access to relevant Transmural Data Providers without setting up a separate provider integration project each time.
Every hospital needs a unique TMP account. You can request that account through support@transmuralplatform.eu. TMP will provide a unique identifier and secret that need to be configured in the EHR integration.
If your hospital runs a custom EHR, the relevant implementation details are covered on the EHR integration page. If your EHR already has a TMP integration path, onboarding is mainly a matter of configuring that supported route correctly.
The goal: keep the hospital side lightweight. One account, one EHR configuration path, then controlled provider access through TMP Portal.
Each hospital receives its own identifier and secret. Those credentials are used in the EHR-side integration to establish the hospital-specific TMP context.
Hospitals follow the setup instructions that match their EHR. Some integrations are already production-ready, others are in testing or progressing with the vendor.
Once configured, HCPs launch TMP from within the EHR, see the providers relevant to the hospital, and manage previous TMP sessions from the same workflow.
Hospitals can configure data retention, group providers into domains, and optionally connect a virtual ward system to the same TMP flow.
The live TMP flow is operational rather than heavy: request a TMP account, configure the supported EHR path, validate the TMP Portal launch, and then activate the providers and policies your hospital needs.
Reach out to support@transmuralplatform.eu to receive the hospital-specific TMP identifier and secret.
Follow the route supported by your EHR vendor or TMP adapter. Hospitals on a custom EHR can use the general EHR integration guidance instead.
Confirm that the HCP sees the correct hospital context, the providers available to that hospital, and the previous telemonitoring sessions for the patient.
Configure the provider scope, retention period, optional domains, and any virtual ward integration before broader rollout.
| EHR | Status snapshot | How to start |
|---|---|---|
| KWS - Nexuzhealth | Production ready | Use the existing hospital instructions path |
| Millenium - Cerner / Oracle | Successfully tested | Reach out to Millenium and TMP support |
| HiX - ChipSoft | Successfully tested / in progress | Reach out to ChipSoft and TMP support |
| Hyperspace - Epic | Production ready / in progress | Reach out to Epic and TMP support |
| XCare / Omnipro / Meddos - Zorgi | Mixed readiness by product | Reach out to Zorgi and TMP support |
| Primuz - UZ Brussel | Production ready | Follow the Primuz hospital instructions path |
After the EHR launch path is in place, TMP Portal becomes the hospital-facing operational layer. It controls visibility, prior session access, and a small set of hospital-specific policies.
TMP Portal shows the context received from the EHR, the current prescriber or hospital, the data providers available to that hospital, and the previous telemonitoring sessions already started for the patient.
If a provider supports actions such as cancel or stop, those can also be exposed in this view.
Hospitals can configure how long TMP Portal keeps request-related information after a request has completed. The current TMP setup supports retention windows from 30 days up to 5 years.
Retention policy configuration is handled through TMP support.
Providers can be grouped into domains so HCPs only see the subset of providers relevant to their hospital workflow or specialty context.
TMP can integrate with virtual ward systems. Patient context is shared when the telemonitoring session is accepted, and telemonitoring data is shared when TMP receives the outcome data from the provider.
The hospital decides which providers are active and how that scope is grouped. That keeps rollout manageable and avoids showing every provider to every user by default.
If your hospital needs help with portal setup, provider domains, retention policy, or virtual ward behaviour, TMP directs hospitals to support@transmuralplatform.eu.
The hospital page stays intentionally lighter than the EHR and Data Provider pages: hospitals mainly need an account, a supported EHR launch path, and the right TMP Portal configuration. The deeper API mechanics remain on the EHR and provider integration pages.
Hospital teams mainly need operational clarity: how to get credentials, how to start on their EHR, and what can be configured centrally in TMP Portal. The lower-level API detail stays on the EHR and Data Provider pages.
Need a supported route into TMP and a controlled set of active providers, not another bespoke integration portfolio.
Handle launch, context, and workflow integration. Their page contains the detailed Portal and TMP Hub implementation content.
Own request handling, status updates, attachments, patient authentication, and dashboard capabilities. Their page holds those API-level details.