Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Aneesh Chopra's Keynote at the Health 2.0's Provider Symposium

123 visualizaciones

Publicado el

At Health 2.0's 10th Annual Fall Conference on September 25, 2016

Publicado en: Salud y medicina
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Aneesh Chopra's Keynote at the Health 2.0's Provider Symposium

  1. 1. @aneeshchopra The Relentless Pursuit of the Health Internet ~ Call to Action on Standards
  2. 2. Hoover’s “Associative State” model boosts nascent air sector Source:; After dramatic reduction in aircraft manufacturing following WWI, then-Secretary Hoover encourages industry collaboration on engine, wing standards, commercialized on popular DC-3, Boeing 247 Commerce Convenes Private Sector on Standards
  3. 3. NIST’s “Smart Grid Interop Panel” collaborates in design of new standards Source: "Standards are absolutely essential to uniform and interoperable communication systems throughout the grid.” – John McDonald, chair of the SGIP Governing Board Applied to the “Smart Grid” Marketplace
  4. 4. Relies on colleagues, not vendors, to commit to open specifications PG&E’s CIO Leads Adoption, Use of Open APIs Source: ; “Chevrolet Volt…led to his developing the…three months…his electric bill reduced an average 20 percent;” one of 50 registered apps with open access to customer energy data without fees or IP constraint
  5. 5. Net metering policy encourages solar adoption, API-enabled tools Policy Shift to Reward Clean Energy a Driver Source:; ; Dept. of Energy 7-Day Solar Prize to “motivate local governments, communities, solar companies and electric utilities to collaborate towards improving the “going solar” experience…for all Americans;” finalist PG&E opens up customer data via “Green Button Connect” open API standard
  6. 6. Payment Models (not MU) the Driver for Exchange To succeed under APMs, providers need assessment, clinical, claims data Source:; ; CJR Bundle Data Services #Telemedicine Services#Integrated EHR Data #SNF/HH Assessments #PRO Survey (~$75/case)#Home Monitoring (~$1k/case) #CMS Claims Data CPC+ HIT Vendor Pledge Care Plan: Establish a care plan that can be updated by patients, care team members 1 2 Social Determinants: Systematically assess patients’ psychosocial needs and inventory resources and supports to meet those needs 3 Patient Reported Outcomes: Document and track patient reported outcomes, such as NIH’s PROMIS 10 survey
  7. 7. Health Information Exchange Standards Open APIs, secure “email” required under CEHRT/MU/MACRA Source:; programs-electronic-health-record-incentive-program-stage-3-and-modifications#p-1518 “The EP…provides access for patients to…retrieve their health information through an API …[patient data must be] available for the patient…to access using any application of their choice…”
  8. 8. Call to action on public/private standards to enable consumer apps Kapor’s Health Internet Vision Coming to Life Source:; releases/emerging-consensus-to-create-a-health-internet-with-broad-consumer-engagement-63755647.html “…a new "Health Internet" could arise through processes that parallel those in the personal computer and Internet revolutions. He highlighted the catalytic role that government played in defining common protocols for the Internet which enabled the Internet to be created from open source and proprietary software. He also called out the critical role of consumer applications in driving growth of the PC and the Internet...” -summary of Kapor keynote at Harvard Health IT meeting (Oct ‘09)
  9. 9. “All-in” Embrace of Open APIs for Data Exchange Regulations, industry response aligned on technical capability “The 2015 Edition includes “application access” criteria…to the Common Clinical Data Set via an application programming interface (API).” MU3: “Access to ONC-Certified API” Certification Criteria (2015 Edition) Source:;;; “The purpose…is to rapidly develop a first- generation FHIR-based API and Core Data Services specification…based on Internet standards and architectural patterns and styles.” Voluntary, Industry Consensus Effort Results to Date Consistent access to data (Common Clinical Data Set) 1 2 Consistent schema in returned data (Data Access Framework) 3 Open Implementation & Testing Framework (Sync for Science)
  10. 10. Clinical Reasoning – Quality Measures, Decision Support + CDS Hooks Technical Base – API, Types, Smart, Documents, etc Conformance – Profiles, Capabilities, Terminologies Administration – Patient, Provider, Organization, Device etc Summary Care Planning Diagnostics Medication s Payments Source: Grahame Grieve Let’s Look Under FHIR’s Hood A (modern) platform standard to achieve a true open, reliable API FHIR’s Platform + Content Standards (Data Access Framework) + Argonaut Testing Program + “Sync” Features (Sync for Science) = Formula for Dependable, Open API
  11. 11. Not so Fast…Regulatory Wrinkle in Near Term Vendors allowed to set terms & conditions, ship proprietary APIs Source: 1112; ONC Issues Aspirational Call for Open APIs: “By requiring that documentation and terms of use be open and transparent to the public by requiring a hyperlink to such documentation to be published with the product on the ONC Certified Health IT Product List, we hope to encourage an open ecosystem of diverse and innovative applications that can successfully and easily interact with different Health IT Modules’ APIs.”
  12. 12. Emerging Era of Connected Applications Can we help navigate patients towards nearest vaccination location? Boosting vaccinations an important priority for population health organizations, but understanding the breadth of patient choice limits capacity to recommend options; an open data collaboration between Children’s Hospital of Boston and CDC makes information freely available for developer use Source:
  13. 13. Call to Action for all Buyers Draft language to get us closer to an open API Require that APIs that meet MU3/CEHRT rules provide consistent access to data, returned with a consistent schema (as constrained by Argonaut IG) 1 2 Require access to conformance testing in the field to prove that the provider is getting a truly open API (using “sync for science” testing tools) 3 Require the ability to offer “ad-hoc” API access to connect any patient facing app of their choice Source:
  14. 14. @aneeshchopra