As Electronic Health Records define most HCP workflows, TMP is built so EHRs can integrate once, give clinicians direct access to remote monitoring workflows, and avoid building separate connections to every Transmural Data Provider.
TMP uses straightforward REST calls and a familiar authentication model. If your EHR already has a standard integration pattern, TMP can also provide an adapter to further reduce implementation work.
Start by connecting the TMP Portal to your EHR. This gives HCPs the basic remote monitoring workflow inside the EHR with minimal implementation effort.
In this first phase an HCP can request a Transmural Data Provider, receive a basic PDF output back through TMP, and view the result in the TMP experience.
The second phase focuses on the results of remote monitoring sessions. This is often carepath-specific and raises workflow questions about long-term storage, structured FHIR data usage, alerting, visualisation, and secondary data use.
This phase can be implemented step by step per carepath, rather than all at once.
The TMP Portal streamlines context integration from the EHR towards Transmural Data Providers and shows the HCP which providers are available, even when provider-specific input does not exist in the EHR itself.
The EHR needs a button, link, or tab where the HCP can launch the TMP Portal from within the normal workflow.
Each prescriber receives a unique clientId and clientSecret. The first step is requesting an access token from the auth API.
OpenAPI documentation: /auth
With the access token, the EHR sends the required patient and prescribing context towards TMP through the request API. Only the information that is actually required is shared with the provider.
OpenAPI documentation: /request
TMP returns a URL that can be shown in the EHR. The URL is HMAC protected and expires after one hour, so a new request must be triggered once the link expires.
Once this is in place, HCPs can start requesting any compatible Data Provider from within the EHR.
TMP supports a small set of standard actions that EHRs can trigger when the connected Data Provider supports them.
Stop a session when the provider supports it. TMP only allows the stop action for sessions in status accepted or in-progress.
API documentation: stop endpoint
Cancel a session that was requested by mistake. TMP only allows the cancel action for sessions in status requested or accepted.
API documentation: cancel endpoint
Retrieve the prescriptions that already exist for a patient. The API only returns sessions for the authenticated prescriber.
API documentation: prescription listing
The TMP Hub is all about broadcasting the results of Transmural Data Providers back to the EHR. To receive data as soon as possible, TMP Hub uses an eventing mechanism that notifies the EHR when useful data is available - as a status update or new attachments. The eventing mechanism never sends the full result payload; it only links to it, keeping data transfer minimal.
When TMP receives an update from a Data Provider, it informs the EHR by calling the configured webhook endpoint. A prescriber account can have zero or more webhooks. Each webhook can be scoped to a specific carepath so that only relevant messages are forwarded.
TMP supports the following security models on the outbound API call: mTLS, Service Account, Authorization Header, and None (for IP whitelisting scenarios).
OpenAPI documentation: prescriber webhook endpoint
Attachments from a Data Provider are hosted on the provider's own infrastructure. If your hospital or EHR system cannot allow outbound firewall access to those endpoints, TMP offers a Proxy solution.
When the Proxy is enabled, every attachment URL pointing to the provider is replaced with a unique TMP URL. Accessing this URL transparently proxies the request to the provider-hosted attachment. The Proxy URL is protected via the same Authorization header used for all other TMP API calls.
To enable the Proxy for your account, configure it in the TMP Console or contact support@transmuralplatform.eu.
The EHR system can verify whether a received attachment comes from a trusted source. Each Transmural Care Data Provider can register the storage locations where their attachments are hosted. TMP exposes this list so hospitals can whitelist and verify attachment origins.
Note that the list of trusted storage links may change over time as providers add or remove asset storage locations.
OpenAPI documentation: asset storage links endpoint
TMP provides a dummy Transmural Care Data Provider for testing both TMP Portal and TMP Hub thoroughly. It can be enabled through the TMP Console or on request through support@transmuralplatform.eu.
| Status | Timing | Purpose |
|---|---|---|
| accepted | After 1 minute | Confirms request acceptance |
| in-progress | After 5 minutes, repeated every 5 minutes for 24h | Publishes a dummy WEIGHT measurement as FHIR attachment |
| completed | After 24 hours | Marks the session as finished |