Content
Summary
Translational informatics relies on a robust clinical informatics infrastructure, centered on the Electronic Health Record (EHR), to bridge laboratory findings with clinical application. Effective implementation requires user-driven governance, such as the 'gemba' principle, and specialized roles like nurse informaticists to optimize workflows without disrupting patient care. Key applications include automated cohort identification via tools like Patient Explorer and ensuring protocol adherence through CTMS integration.
Intuition
Think of clinical informatics as the bilingual translation team connecting clinical practice and translational research. The EHR is the central hub, but unlike a simple medical record, it is a complex infrastructure involving humans and technology. The 'fundamental theorem' suggests that combining humans and tech yields greater effectiveness than either alone. To make this work, you cannot just impose changes from the top down; you must use the 'gemba' principle, where those doing the work (clinicians) map the actual steps. This avoids 'obstructive governance' and ensures that tools like the Patient Explorer or CTMS integration actually fit into real-world workflows, enabling tasks like identifying CD30-positive tumor cohorts for trials.
Derivation
- Clinical informatics is defined by the acquisition, storage, and utilization of information within a specific domain, focusing on the human and organizational bodies managing these systems.
- The EHR serves as the central component, evolving from basic lab systems to comprehensive records supporting both care and research.
- The fundamental theorem posits that human-technology combinations yield greater effectiveness than either component alone.
- Governance must avoid extremes (no governance or obstructive governance) and instead use the 'gemba' principle, where workers map actual intended and unintended steps.
- Operational models require specialized roles, such as nurse informaticists coordinating small-to-moderate EHR changes under council approval.
- Applications include the Total Cancer Care (TCC) protocol for data warehousing and the Patient Explorer for automated cohort identification.
- CTMS integration into the EHR provides real-time trial status awareness, maximizing protocol adherence.
Worked example
A hospital wants to identify patients with CD30-positive tumors for a new clinical trial but struggles with manual screening. How does the described infrastructure solve this?
- Utilize the Total Cancer Care (TCC) protocol to collect patient samples and feed a data warehouse.
- Integrate the Clinical Trials Management System (CTMS) into the EHR to provide real-time enrollment data.
- Use the Patient Explorer interface to visualize patient journeys, including imaging and treatments, to automate cohort identification.
- Leverage collaboration with M2Gen to share data across cancer centers for broader cohort discovery.
Answer The infrastructure automates cohort identification by linking biobanks to data warehouses via the TCC protocol and using the Patient Explorer to visualize comprehensive patient data, while CTMS integration ensures real-time awareness of trial participation.
Common mistakes
- Assuming clinical guidelines can be seamlessly moved between disparate EHR platforms due to lack of interoperability.
- Implementing 'obstructive governance' where no changes are allowed, which hinders optimization.
- Relying solely on theoretical models for workflow assessment instead of using the 'gemba' principle to ask workers.
- Ignoring the need for specialized nurse informaticists to coordinate EHR changes.
- Treating clinical pathways as static expert systems rather than model-driven tools that adapt to new evidence.