Pricing

Transparent pricing for scalable transmural care

TMP uses a simple pay-per-use model : you only pay when a patient session creates real integration value between a caregiver and a Transmural Data Provider.

No complex license models. No heavy upfront integration fees. No hidden platform lock-in. Just a clear usage-based price that grows with adoption.

€ 0.50 per patient session for the caregiver
€ 0.50 per patient session for the Transmural Data Provider

For high-volume data exchange and proxy usage. TMP also offers a dedicated proxy feature priced per gigabyte.

How TMP pricing works

TMP pricing is built around the concept of a patient session.

A patient session represents a concrete transmural care interaction where a caregiver requests, starts, follows up and receives information from a connected Transmural Data Provider through TMP.

Instead of charging each stakeholder large fixed fees upfront, TMP charges a small amount per actual session. This makes pricing fair, predictable and directly linked to real-world usage.

Core Pricing

Patient session pricing

Stakeholder	Price	What it covers
Caregiver / Hospital	€ 0.50 per patient session	Access to TMP Portal, TMP Console, standardized request flow, provider marketplace, secure patient context sharing and workflow support.
Transmural Data Provider	€ 0.50 per patient session	access to TMP Hub, standardized data return flow, status updates, structured integration towards hospitals and EHRs, marketplace listing

A patient session is counted once for the caregiver side and once for the data provider side. This creates a balanced model where both sides contribute equally to the shared interoperability layer.

Why pay-per-use

TMP is designed to support hospitals, caregivers, data providers and EHR vendors as transmural care becomes part of daily clinical practice. A pay-per-use model makes this transition easier.

Low barrier to start : Hospitals and data providers can start using TMP without committing to large fixed platform fees. This lowers the threshold for innovation, pilots and gradual roll-out.
Costs follow real usage : You only pay when TMP is actually used for a patient session. This means pricing follows adoption, not expectations.
Fair contribution from both sides : Caregivers and data providers both benefit from a standardized integration layer. This pricing model reflects that shared value by splitting the contribution equally.
Predictable and transparent : The price per session is known upfront. Usage can be reported clearly, making budgeting and internal reporting easier.
Better than one-off integrations : Without TMP, every hospital, EHR and data provider risks building separate integrations. That creates repeated costs, inconsistent workflows and long implementation cycles. TMP replaces this with one standardized approach.

Proxy Feature

Secure data exchange for proxy functionality

TMP offers an additional feature of proxying data. This can reduce burden on IT teams as whitelisting on fixed IP’s becomes static instead of dynamic per provider.
Enabling this feature will be charged per gigabyte that is being transferred on the proxy.

Feature	Price	Best for
TMP Proxy	€ 0.09 per GB	removing dynamic firewall rules, facilitating whitelisting

Example scenarios

Example 1 : 1000 patient sessions

A hospital uses TMP in 2026 for 1,200 patient sessions with connected Transmural Data Providers. Every month 100 patients are measured.

Stakeholder	Calculation	Monthly cost
Caregiver / Hospital	100 * € 0.50	€ 50
Data Provider	100 * € 0.50	€ 50

Total platform contribution across both sides : € 100 / month

Example 2 : 20 patient sessions measuring with 50MB of data per patient. The proxy feature is enabled.

Feature	Calculation	Cost
TMP Proxy	0,09 * 0,05GB * 20	€ 0,09
Caregiver / Hospital	20 * € 0.50	€ 10

Contribution on Hospital side with proxy enabled : € 10,09

What’s included?

For caregivers and hospitals

Access to TMP Portal and TMP Console
Single-Sign-On based request flows towards connected providers
Standardized patient context sharing
Marketplace visibility on validated Transmural Data Providers
Clear overview of carepaths, privacy, data flows and security information
Workflow support for starting and following up patient sessions
Usage reporting for invoicing and internal follow-up

For Transmural Data Providers

Access to TMP Hub
One standardized interface towards participating hospitals and EHRs
Support for request context flows
Support for status updates
Support for structured result flows
Reduced need for one-off hospital integrations
Provider listing in the TMP Marketplace
Usage reporting for invoicing and internal follow-up

For the ecosystem

A shared interoperability layer
Lower integration cost across the market
More consistent workflows between hospitals and providers
Better scalability for new carepaths
A neutral model that supports broad participation

Built for ecosystem adoption

TMP pricing is not designed to maximize short-term platform fees. It is designed to make standardized transmural care integration affordable, scalable and sustainable.
By keeping the core patient session fee low, TMP helps hospitals and data providers move from isolated pilots to operational transmural care at scale.

The result is a model where :

Hospitals can onboard more providers without rebuilding every integration.
Data providers can connect to more hospitals through one standard flow.
EHR vendors can rely on structured and predictable integration patterns.
Patients benefit from smoother care across settings.

Frequently Asked Questions

What is a patient session?
A patient session is a concrete transmural care interaction supported through TMP, linked to a patient and a connected Transmural Data Provider.
It can include the request flow, status follow-up and result availability depending on the care path and provider integration. It can cover multiple days, weeks or months.

Is the price charged to both the hospital and the data provider?
Yes. The standard model is € 0.50 per patient session for the caregiver side and € 0.50 per patient session for the Transmural Data Provider side.
Transmural Data Providers can configure their application to cover the full cost (caregiver and data provider) if they prefer this.

Why does TMP charge both sides?
Both sides benefit from the shared integration layer. Hospitals reduce integration complexity and receive standardized workflows.
Data providers avoid repeated custom integrations and gain easier access to participating hospitals. The pricing reflects that shared value.

Are there fixed onboarding costs?
The core model is usage-based and so no separate onboarding costs are asked.
TMP expects Transmural Data Providers to follow a certain interface, so development costs at the data provider’s side may occur.

Is proxy usage included in the patient session price?
No. Proxy usage is charged separately per gigabyte because it depends on the actual data volume exchanged.

Can pricing be different for very high-volume care paths?
For very high-volume or technically specific care paths, TMP may define specific pricing or contractual arrangements to keep the model fair and sustainable.

How is usage reported?
TMP can provide usage reporting based on measured patient sessions and, where applicable, proxy data volume. This supports transparent invoicing and internal reporting.

Can we start with a pilot?
Yes. The pay-per-use model is well suited for gradual onboarding, pilots and scaling from a limited number of providers or care paths towards broader deployment.
TMP can be used for any care path, reimbursed or not.