TMP is priced per patient session, not per message or per megabyte. This page describes what we consider customary use of the platform, as referred to in article 5.7 of the TMP service agreement. It is a reference framework: exceeding something described here is not, in itself, a breach, and does not, in itself, create an additional fee.
We do not publish our own frequency figures. The expected message frequency for a care path is defined in the HL7 Belgium patient monitoring implementation guide for that care path. Build to the frequency the guide defines for the care path you implement, and you are within customary use at the standard rate.
TMP supports near real-time notifications, and standard telemonitoring where measurements and results are forwarded periodically or near real time is ordinary use. The notification protocol carries events - a measurement, a status change, a result - and is not a transport for streaming data. We do not expect a constant flow of messages several times per second. Continuous raw signal belongs in a recording or document delivered as a result.
A care path that structurally requires a continuous, sustained stream of several notifications per minute is a real-time care path under article 2 of the agreement. Those are discussed with you individually and can carry a separate pricing model or service levels. Qualification is never unilateral, and an implementation already running in production continues at the standard rate until the parties agree otherwise in writing.
Article 5.7 sets out a process, and this is all of it. Nothing happens automatically and no fee appears on an invoice without agreement.
TMP motivates the request on the basis of objective usage data and the parties consult in good faith about appropriate technical or commercial arrangements.
During that period the implementation keeps running as it is, at the rate that already applies to it.
60 calendar daysOnly if no agreement is reached, and running patient sessions are wound down under the continuity regime of articles 4.7 and 6.5 rather than dropped.
30 calendar daysYou do not have to guess. Describe the expected usage parameters of a planned or existing implementation and TMP confirms in writing whether it falls within customary use, in principle within thirty calendar days. As long as actual use does not materially deviate from what you described, TMP cannot invoke the fair use provision for that implementation.
TMP may adjust this page subject to prior written notice of at least thirty calendar days, without retroactive effect. Enforced technical limits - request quotas, payload sizes, timeouts - live in the TMP Technical Documentation. In case of conflict, the service agreement prevails over this page.