Whether you're a hospital, a data provider, or an EHR vendor - the path to integrating with TMP starts here. Select your role below.
The integration process differs by role - select yours to see the relevant steps.
Connect your hospital to the TMP network to give clinical staff access to all compliant data providers from within the EHR.
⏱ 1-2 weeks to go-liveIntegrate your transmural monitoring platform once and reach every connected hospital - without a custom project per site.
⏱ 1-12 weeks to go-liveBuild a single reusable adapter to the TMP Portal and Hub APIs - and enable every hospital on your platform to benefit from TMP integration.
⏱ 4-16 weeks for adapterVerify whether your EHR system is already integrated with TMP. If yes, your hospital can go live on the existing adapter with minimal effort.
TMP iVZW provides the compliance framework. Your DPO reviews the standard DPIA, data processing agreements, and security documentation.
Configure your credentials with your EHR vendor to activate the TMP Portal and Hub integration for your hospital. Test with sandbox data before go-live.
Your clinical teams can begin requesting transmural data providers directly from the EHR. New providers can be added with a click - no further integration work needed.
Contact TMP to introduce your platform, describe your care pathways, and understand the integration scope. If you want to get started right away you can look at the Data Provider Integration page and reach out to us with any questions.
Contact us →Implement the TMP Hub API - REST / FHIR R4 calls. TMP provides OpenAPI documentation, a sandbox environment, and implementation support from the technical team.
View OpenAPI docs →Run an end-to-end pilot with one of the hospital consortium members. Validate the request flow, SSO handoff, and result return in a real clinical setting.
Your platform is listed in the TMP Portal marketplace and reachable by every connected hospital - without any further integration effort per site.
TMP and the EHR vendor's technical team align on the adapter architecture - TMP Portal embedding, Hub result ingestion, and FHIR / SSO approach.
Read EHR integration guide →Build the TMP Portal module within your EHR and the Hub result ingest pipeline. TMP provides sandbox access, test scripts and can help with adapter development and questions.
OpenAPI docs →Deploy the adapter at a pilot hospital and validate across at least two care pathways. Collect clinical team feedback and resolve any workflow gaps.
Every hospital customer can activate TMP integration - no custom work per site.
Full API reference for TMP Portal and TMP Hub integration endpoints.
Step-by-step integration process, technical specs, and current EHR partner status.
Requirements, onboarding steps, and provider status for Transmural Data Providers.
How integration works for hospitals - clinical workflows, IT requirements, and FAQ.
Mission, architecture, and the case for a shared transmural care integration standard.
Questions about integration, onboarding, or partnership? We're happy to help.