- Contact
- dhp@uhn.ca
Purpose, Vision/Mission
The DHP seeks to establish a central data service to help investigators across UHN unleash the power of technology and innovation through better data.
Background
UHN's Digital Health Platform (DHP) core is an evolution of the Digital Cardiac Health Platform (DCHP) and began from a joint effort between the Peter Munk Cardiac Centre, Ted Rogers Centre for Heart Research and UHN Digital.
The DHP aims to facilitate research, innovation and improvements in clinical care by providing access to numerous clinical and research data sources across multiple domains at UHN and looks to help research and quality improvement initiatives.
Team Members
The DHP relies on flows to ingest data from a variety of systems. Flows are the services that process data, and a flow describes a series of steps taken before data moves into the DHP. Flows can perform a variety of functions, e.g. query various data sources, perform transformations, save data in a set location, and can have time- or event-based triggers (or both).
Infrastructure Management
Kubernetes
Messaging Service
NATS,
Jetstream
Primary Development Language
Golang,
python
Query Language
graphQL
Secrets
Vault
Database
MongoDB, minIO, relational DBs
Contact us for more details.
Total Patients
Hospital Events
Lab Observations
Device readings
Quadramed EPR (ADTs, Labs, Orders), Epic (ADTs, Documents, Orders, Observations, Medications, Scheduling), GE Muse, Apollo, JDMI Cardiac PACS, OPIS, ORSOS, Philips, TAVI, WTIS, CoPath, CPET, PMCC Biobank, CaTissue, Bloodbank and more.
Some systems offer real-time or near real-time data (e.g. Epic ADTs,
orders, etc).
Contact us to request a data source
or ask us any questions.
(Coming Soon)
The DHP enforces several standard operating procedures to guide daily activities, however in all cases UHN policy takes precedence. The DHP works closely with the Data Governance Committee to ensure ongoing updates and alignment with DHP governance.
