Saturday, April 27, 2013

Disruptive Innovation in Health IT: A Path to Acceptance (Part 8)

In this eighth post of the series on disruptive health IT (see this linkto start from beginning), I examine a key element that EHRs systems need, and a EHR good companion application should provide Patient-Centered Support (PCCS).

Here's a brief explanation of PCCS and what a PCCS-enabled EHR system would do:
  • Clinicians have a “virtual patient” in mind—a conceptual model of an actual patient that reflects their understanding of the patient’s problems and needs
  • This virtual patient model (VPM) consists of multiple submodels reflecting the interaction between biomedical and psychological subsystems in the real patient
  • New findings—raw data—are used to refine the VPM
  • PCCS-enabled software provides clinical decision support by:
    • Simulating and predicting the likely reaction of the VPM to different care interventions
    • Identifying the interventions most likely to benefit the actual patient
  • Without PCCS-enabled software to help make decisions, clinicians may:
    • Spend considerable time and energy searching and sifting through all the raw data
    • Have to integrate ill-structured, uncertain, and potentially conflicting information
    • Experience information overload, confusion, uncertainly and doubt
  • With PCCS-enabled software, a clinician:
    • Has much less cognitive burden
    • Makes decisions supported by deeper &; clearer understanding of the patient
    • Can stay focused on implementing the patient’s care plan
  • Patients should also have a version of PCCS software available.
The whole product companion applications I've described in previous posts in this thread will focus, in part, on developing, evolving, and deploying EHR companion applications that are PCCS-enabled. Toward this end, we are prepared to offer:
  • A novel, robust software development platform that uses off-the-shelf software tools to create and continually evolve next-generation analytical decision models
  • A communication architecture that promotes collaboration in loosely coupled social networks
  • The means to combine the development platform and communication architecture to provide:
    • “Technological glue” that connects companion app components via the CP Split method
    • “Model ecology networks” in which teams of collaborators build, share, evaluate, and evolve analytical decision models, which they may sell.
Implementing this strategy will be done through collaboration among a widespread alliance of business partners. We are compiling lists of people and companies we believe may be interested in receiving an invitation to join the alliance. They include clinicians of all types, informaticists, analytical decision model-builders, and EHR vendors.

I'll have more to say about the alliance in subsequent posts.

Post a Comment