Virtual wards, Clinical Command Centers or Transmural Care Cockpits enable hospital-level care delivery in patients' homes through continuous remote monitoring and clinical oversight. TMP can link a virtual ward system so patient context and telemonitoring data are shared automatically through TMP Hub.
TMP supports the complete virtual ward workflow, from patient enrolment through ongoing monitoring and clinical intervention.
To minimise implementation effort and accommodate different virtual ward configurations, TMP works with healthcare providers on integration solutions that fit their clinical protocols and organisational setup.
When a virtual ward system is linked with TMP, patient context is shared automatically when a data provider accepts the telemonitoring session. Later, telemonitoring data is forwarded as soon as TMP receives it from the data provider.
TMP facilitates the introduction of Virtual Wards by enabling seamless data sharing between the hospital's EHR, the telemonitoring data providers, and the virtual ward system. This integration ensures that patient context and telemonitoring data are automatically shared at key moments in the workflow, allowing for efficient setup and ongoing monitoring of patients in virtual wards.
Patient context can be sent towards the virtual ward system at the moment a data provider accepts the telemonitoring session. That gives the virtual ward system the clinical context it needs to set up its own workflow.
TMP forwards telemonitoring data directly when it is received from the data provider. The virtual ward system therefore stays aligned with the monitoring flow without polling separate systems.
To support TMP, the hospital must be able to configure the correct endpoint towards which TMP sends the relevant data for the virtual ward workflow.
TMP works with providers and healthcare organisations to shape the integration around the actual virtual ward protocol instead of a purely generic template.
The data TMP sends to the configured virtual ward endpoint is documented in the virtual ward endpoint OpenAPI spec.
Virtual ward linking can sit alongside the EHR, and data provider flows rather than replacing them. TMP gives you the caregivers the ability to coordinate when and where data is shared to EHRs or Virtual Wards.
The key requirement from the live TMP page is simple: hospitals must be able to configure the correct endpoint, and TMP needs to know where to send the virtual ward payloads.
Each hospital can configure the endpoint towards which TMP sends the relevant virtual ward data.
TMP can adapt to the local virtual ward protocol instead of a purely generic template.
The payload TMP posts is documented already, which keeps the implementation concrete rather than exploratory.
The setup is designed so hospitals can enable any virtual ward linking. Inside, or alongside their EHR and data provider flows, depending on what fits best with their internal setup and protocols.