1 / 23

Shaun J. Grannis, MD MS FAAFP FACMI The Regenstrief Institute

Obstacles to Adding Measures to EHRs and Ways to Overcome these for the Patient, Provider, System, and Society: General Principles and Real-World Experience Presented to the IOM Committee on Recommended Social and Behavioral Domains and Measures for Electronic Health Records April 8, 2014.

varick
Télécharger la présentation

Shaun J. Grannis, MD MS FAAFP FACMI The Regenstrief Institute

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Obstacles to Adding Measures to EHRs and Ways to Overcome these for the Patient, Provider, System, and Society: General Principles and Real-World ExperiencePresented to the IOM Committee on Recommended Social and Behavioral Domains and Measures for Electronic Health RecordsApril 8, 2014 Shaun J. Grannis, MD MS FAAFP FACMI The Regenstrief Institute Indiana University School of Medicine

  2. Adding EHR data and functionality is costly • Potential for increased data gathering burden • Additional time • Altered workflow • Necessary Design/Development costs • Systems must be re-configured to accommodate new data/functionality • Who absorbs these costs?

  3. “Why, What, How, and By Whom” • Why: • Well-articulated Problem/Need/Goal ... to which additional information/functionality are a clear solution • What: • Identify information needed to accomplish the goal • How: • Define process. Re-use existing resources before asking for more: Identify and leverage potential pre-existing measures that address the need.

  4. “Why, What, How, and By Whom” • Who: • Contemplate who may be optimally positioned to gather/supply new information • Physician • Nurse • Registration Clerk • Patient • Other?

  5. Examples

  6. Rwanda: Maternal Child Health

  7. ? Hospital Community Clinic

  8. Hospital Community Clinic

  9. Define Metrics to Assess Progress Toward Goal

  10. Integrating Community level and Geospatial data

  11. “Why”: Integrating Community level geospatial data • Socio-behavioral factors are important, often unrecognized determinants of health outcomes • US healthcare system is oriented to acute, hospital based, disease treatment. • Responding to the health needs of both non-hospitalized and hospitalized patients with chronic diseases is proving difficult. • Improving population level health problems like healthcare disparities is also challenging, in part because of the complex interplay of socio-behavioral, community and biologic factors within the context of the current healthcare system. • Just as IT enabled advances in sub-molecular medicine, behavioral and population sciences are on the verge of an IT based revolution.

  12. Patient Address Change 1 ADT Processor 2 Update person_address table with new address information person_address table 6 • In real-time, Address Update Detector detects and writes address changes to the post_processing table 3 post_processing table Geo-Coding Application Address Update Detector Call Polis Center web service which returns geo-coded addresses 4 5 Geo-Coding app reads the post_processing table Polis Web Service Frederickson K, Grannis SJ, Dixon B, Bodenhamer DJ, Wiehe S. Incorporating geospatial capacity within clinical data systems to address social determinants of health. Public Health Reports. 2011 126. Suppl 3: 54.

  13. Population-Level Analytics: Surveillance, Patient trends, Predictive Modeling

  14. GI Event

  15. Network Connection HL7 ADT message Hospital Interface Engine (Routing) Hospital Firewall (Encryption) Hospital ED Registration Imported into Clinical Repository Message Listener Message Processor Clinical Repository Firewall (Decryption) Information Flow: Clinical

  16. Network Connection HL7 ADT message Hospital Interface Engine (Routing) Hospital Firewall (Encryption) Hospital ED Registration Batched, delivered to ISDH every 3 hours Message Listener Message Processor Firewall (Decryption) Information Flow: PH Surveillance Public Health

  17. Multi-stream Surveillance

  18. Flu ICD9 Flu CC H1N1,Oct 2009 H1N1, April 2009 Pneumonia ICD9 Pneumonia CC ILI ICD9 ILI CC All Flu Tests Positive Flu Tests Positive Rate

  19. Population Trends

  20. A network diagram illustrating the connectedness among Indiana EDs that participate in PHESS. Circular nodes represent EDs; node size indicates the visit volume; node color indicates the centrality of the ED. The gray edges connecting nodes indicate where patient crossover occurs. EDs that share proportionally larger number of patients are clustered together. While general clusters of "medical trading areas" emerge, the myriad gray edges clearly illustrate how interconnected all EDs are to one another.

  21. Predicting Frequent ED Users 84% PPV for predicting which patients who will use ED > 16 times in two years. Wu J, Xu H, Finnell JT, Grannis SJ. A Practical Method for Predicting Frequent Use of Emergency Department Care Using Routinely Available Electronic Registration Data. AMIA AnnuSymp Proc. 2013:1524.

  22. Thank You!

More Related