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.
Hospitals and data providers start without committing to large fixed platform fees. Lowers the threshold for pilots and gradual roll-out.
You only pay when TMP is actually used for a patient session. Pricing follows adoption, not expectations.
Caregivers and data providers both benefit from the shared integration layer. The model reflects that by splitting the contribution equally.
The price per session is known upfront. Usage can be reported clearly, making budgeting and internal reporting straightforward.
Without TMP, every hospital-provider pair builds a separate integration - repeated costs and long cycles. TMP replaces this with one standard.
As more hospitals and providers join, the cost per connection goes down while the value of each session increases for everyone.
Pricing is built around the concept of a patient session - a concrete transmural care interaction supported through TMP.
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.
A session can cover multiple days, weeks, or months depending on the care path. It is counted once for the caregiver side and once for the data provider side.
Note: Transmural Data Providers can configure their application to cover the full cost (caregiver and provider) if they prefer this model.
A single, clear rate for both sides of the integration.
| Stakeholder | Price | What it covers |
|---|---|---|
| Caregiver / Hospital | € 0.50 / session | Access to TMP Portal and TMP Console, Single Sign-On request flows, standardised patient context sharing, provider marketplace, workflow support, usage reporting. |
| Transmural Data Provider | € 0.50 / session | Access to TMP Hub, standardised data return flow, status updates, structured integration towards hospitals and EHRs, marketplace listing, usage reporting. |
TMP offers an optional proxy feature that reduces burden on IT teams - whitelisting on fixed IPs becomes static instead of dynamic per provider. Charged per gigabyte of data transferred.
| Feature | Price | Best for |
|---|---|---|
| TMP Proxy | € 0.09 / GB | Removing dynamic firewall rules, facilitating static IP whitelisting |
Two concrete examples to illustrate how TMP pricing works at different scales.
A hospital runs 100 patient sessions per month with connected providers. No proxy usage.
| Stakeholder | Calculation | Monthly cost |
|---|---|---|
| Caregiver / Hospital | 100 × € 0.50 | € 50 |
| Data Provider | 100 × € 0.50 | € 50 |
20 patient sessions measuring with 50 MB of data each. TMP Proxy feature enabled.
| Feature | Calculation | Cost |
|---|---|---|
| Caregiver / Hospital | 20 × € 0.50 | € 10.00 |
| Data Provider | 20 × € 0.50 | € 10.00 |
| TMP Proxy | € 0.09 × 0.05 GB × 20 | € 0.09 |
No hidden add-ons. The session fee covers full access to the relevant TMP layer for each stakeholder.