Pay per session.

TMP uses a pay-per-use model. As a connected data provider, your solution pays per patient session that flows through TMP. No platform fee, no per-hospital fee, and no charge until a session actually starts.

€ 0.50 per patient session
billed to your organisation
€ 0.50 per patient session
billed to the hospital or practice

What is a patient session?

A session starts when a healthcare professional selects your solution inside TMP Portal and TMP delivers structured patient context to your API. It ends when you post the final result back to TMP and TMP routes it into the patient's EHR record.

A session can span days, weeks, or months. It is counted once regardless of duration, the number of status updates, or the volume of data exchanged.

One session. One price.
1
Healthcare professional starts session from EHR TMP Portal opens in context; your solution is selected from the marketplace
↓
2
TMP delivers patient context to your API Structured session payload with patient data and organisation arrives at your endpoint
↓
3
Your solution monitors and delivers care Active phase: your platform runs; TMP tracks the session state via your status updates
↓
4
You post results to TMP Results land in the patient's EHR automatically, session closed, billed at € 0.50

Patient session pricing

A single, clear rate, known before you go live.

MedTech & Data Providers
€ 0.50 / session
  • Access to TMP Hub API and Provider Console
  • Marketplace listing across all connected hospitals
  • Standardised patient context delivered to your API
  • Secure result posting directly into patient EHR records
  • Full session lifecycle management via API
  • Usage dashboard with session and billing analytics
  • Single integration reaches every connected EHR system
  • No fixed onboarding or platform fee
Hospital or GP Practice
€ 0.50 / session

Hospitals and practices also contribute € 0.50 per session for their side of the integration. This cost appears on their invoice, not yours.

Optional

TMP Proxy

TMP offers an optional proxy feature that routes all data exchange through a single TMP endpoint. Hospitals that opt in avoid per-provider firewall rules; instead, one static IP range covers every connected data provider. The proxy fee (€ 0.09 / GB) is charged to the hospital side and does not appear on your invoice.

€ 0.09 / GB transferred

What does it cost in practice?

Concrete examples for a data provider growing its hospital reach through TMP.

Swipe to view all 3 examples →

Example 1

Pilot launch: 30 sessions / month

A MedTech company integrates with TMP and goes live at two hospitals. In the first month, 30 patient sessions are started through TMP, a mix of cardiology and respiratory care paths.

Line item Calculation Monthly cost
Provider side (TMP Hub API) 30 × €0.50 €15
Your contribution / month €15
The hospitals each pay their own €0.50 / session separately; that cost does not appear on your invoice.
Example 2

Growing provider: 250 sessions / month across 8 hospitals

After 6 months the same provider has expanded to 8 hospitals with no additional integration work. Volume grows to 250 sessions per month. Some hospitals opt to use TMP Proxy for simplified firewall management; that cost is on their side.

Line item Calculation Monthly cost
Provider side (TMP Hub API) 250 × €0.50 €125
Your contribution / month €125
TMP Proxy fees are billed to the hospital, not to you. Your cost is always the session fee alone.
Example 3

Established provider: 3600 sessions / year

A provider is live across 12 hospitals. Over the course of a year, TMP delivers 3600 patient sessions across multiple care paths, all via the same single integration done once.

Line item Calculation Annual cost
Provider side (TMP Hub API) 3600 × €0.50 €1800
Your contribution / year €1800
€1800 / year to reach 12 hospitals. A single bilateral integration with one hospital typically costs a lot more in development and maintenance, before counting the next hospital.

Pricing FAQ

What exactly counts as a patient session?
A patient session is a single transmural care interaction for one patient through TMP. It starts when a healthcare professional initiates a request via TMP Portal and TMP delivers patient context to your API. It ends when the result is posted back through TMP into the patient's EHR. Duration can range from days to months; it is still counted as one session.
Is there an onboarding or integration fee?
TMP does not charge a fixed onboarding fee, platform fee, or per-hospital fee. You integrate once with the TMP Hub API and your solution becomes reachable across the entire network. You only pay when sessions happen.
Are cancelled or rejected sessions billed?
No. A session is only billed when it progresses through the full lifecycle and a result is delivered. Sessions that are cancelled before delivery or rejected by your system are not counted.
Why does TMP charge both the provider and the hospital?
Both sides benefit from the shared integration layer: hospitals get structured results into their EHR without one-off integration projects, and providers get standardised access to every connected hospital without per-hospital development. The model reflects that by splitting the contribution equally (€ 0.50 each). This means the cost per side is significantly lower than what a bilateral integration project would cost either party.
If a patient uses our platform across multiple hospitals, is each hospital visit a separate session?
Yes. Each care interaction initiated through TMP Portal at a specific hospital counts as its own session. A patient moving between hospitals generates separate sessions, each with its own patient context delivery and result posting.
What if a session spans several months?
Session duration does not affect pricing. A session that spans three months of continuous remote monitoring is still billed as one session at € 0.50. There are no time-based or data-volume components in the session fee. For continuous monitoring, a session has a maximum duration of 1 year.
How is usage reported and invoiced?
TMP generates usage reports showing sessions by hospital, care path, and time period. You can access session-level data through the Provider Console. Invoicing is done periodically based on actual session counts confirmed through TMP.
Can we test in a sandbox before going live?
Yes. TMP provides a sandbox environment where you can run the full session lifecycle against test hospital contexts before any live patients are involved. Sandbox sessions are not billed.
Is there a volume discount at scale?
The standard rate is € 0.50 per session. For providers operating at very high volume or running structural national programmes, reach out to discuss whether a tailored arrangement makes sense.
Why does TMP use a pay-per-use model?
Pay-per-use keeps the barrier to start low: no fixed platform fees means data providers can integrate and go live without upfront investment. Costs follow actual adoption rather than capacity estimates, and the price per session is fixed and known before you go live, making forecasting straightforward. Both data providers and hospitals benefit from the shared integration layer, so each side contributes equally (€ 0.50 per session) instead of funding separate one-off integrations. As more hospitals and providers join, the value of each session grows while the relative cost of access stays flat.

Ready to integrate your solution with TMP?

One integration. Every connected hospital. Pay only when sessions happen.

Contact us to get connected Read the integration guide →