Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Smart data, smarter healthcare

4,268 views

Published on

Presentation to China mHealth & Medical Software conference by Heather Leslie - Shanghai, April 19 2016

Published in: Data & Analytics
  • Be the first to comment

Smart data, smarter healthcare

  1. 1. SMART DATA, SMARTER HEALTHCARE Dr Heather Leslie Chief Clinical Informatician, Ocean Informatics Clinical Programme Lead, openEHR Foundation Director, Global eHealth Collaborative
  2. 2. Journey to interoperability… © Ocean Informatics 2016 paperHealth eHealth: Connectivity eHealth: Interoperability
  3. 3. The journey so far… © Ocean Informatics 2016 Maze of Monolithic Systems Forest of Many Silos Swamp of Incremental Innovation River of Fixed Messages Sea of Unsustainability Semantic Cliffs Quicksand Heights of Optimism Bay of Never-ending Negotiation eHealth: Interoperability
  4. 4. How to reach interoperability? © Ocean Informatics 2016 Bridge of ‘Smart Data’ Semantic Cliffs eHealth: Interoperability
  5. 5. What is smart health data?  Shared clinical content specifications  Clinically led  Represents how clinicians need their data  Unambiguous & fit for purpose  Implementable  Collaboratively developed & agreed  Zero cost to use; free access  Standards based  Independent of any single technology or software application © Ocean Informatics 2016
  6. 6. ALL CLINICAL CONTENT openEHR Smart Data approach © Ocean Informatics 2016 Clinicians drive this process! Templates Archetypes Terminology SNOMED CT LOINC etc openEHR information models
  7. 7. openEHR Smart Data approach © Ocean Informatics 2016 Templates Archetypes Terminology SNOMED CT LOINC etc openEHR information models Software is built independently of the content CLINICAL TECHNICAL
  8. 8. What is openEHR?  ‘openEHR’ = Open Electronic Health Record  Often pronounced as ‘open air’ or ‘open E-H-R’  Specification/schema for a complete electronic health record architecture  Open source, freely available  Managed by not for profit openEHR Foundation at University College London  www.openEHR.org © Ocean Informatics 2016
  9. 9. The openEHR community  International community  Email lists, online tools, teleconferences  5 operational areas  Specification development  Software development  Clinical models  Education  Localisation © Ocean Informatics 2016
  10. 10. International openEHR clinical model community © Ocean Informatics 2016 1500 people 87 countries • Clinicians • Informaticians • Software Engineers • Terminologists
  11. 11. Clinical Knowledge Manager  Known as ‘CKM’  Online tool - www.openEHR.org/CKM  Library of information models – ‘Archetypes’  500 archetypes = 6000 data points  23 languages, mostly English  Online collaboration portal  Governance – publication, versioning, distribution © Ocean Informatics 2016
  12. 12. Clinical Knowledge Manager © Ocean Informatics 2016www.openEHR.org/CKM
  13. 13. International CKM collaboration
  14. 14. © Ocean Informatics 2016
  15. 15. Clinical knowledgebase CKM Library CKM Archetype library Time Technology Number of archetypes © Ocean Informatics 2016
  16. 16. © Ocean Informatics 2016
  17. 17. ‘Reference Model’ = rules ‘Archetype’ = Clinical concept specification ‘Templates’ = datasets Clinical Documents/ Messages/Forms CKM Library National resource Health data patterns • Standardised • Clinically agreed • Centrally governed Aggregate & constrain  clinical diversity: • clinical domain • profession • location Smart data ecosystem © Ocean Informatics 2016
  18. 18. What is an archetype? Archetype  Building block  Computable specification for one single clinical concept  Blood pressure  Medication order  Symptom  Diagnosis  Family History  Maximal data set  Universal use-case  Design once, re-use over & over  Strong governance critical © Ocean Informatics 2016
  19. 19. Blood Pressure Archetype Archetype Definition Language (ADL)  ISO standard 13606 © Ocean Informatics 2016
  20. 20. © Ocean Informatics 2016
  21. 21. What is a template? Archetype Template  Building block  Computable specification for one single clinical concept  Blood pressure  Medication order  Symptom  Diagnosis  Family History  Maximal data set  Universal use-case  Design once, re-use over & over  Governance is critical © Ocean Informatics 2016  Data set; multiple blocks  Computable specification for a specific clinical purpose:  Message content  Document  Form  Report  Flexible expression of clinical requirements  Constrain  sensible for the specific clinical use-case  1-∞ archetypes per template  Governance NOT critical
  22. 22. Template? © Ocean Informatics 2016
  23. 23. © Ocean Informatics 2016
  24. 24. Archetype Re-use © Ocean Informatics 2016
  25. 25. Project archetype re-use  1 jurisdiction  3 projects  14 unique templates  1 Antenatal  10 Hearing Health  3 RMP on-call  81 unique archetypes
  26. 26. Templates Archetypes Data Sets Decision Support Acknowledgements: Hugh Leslie, Thomas Beale SchemasSemantic Queries One record Population health Messages Terminology SNOMED CT LOINC Forms Documents openEHR smart data ecosystem © Ocean Informatics 2016 Guideline Definition Language (GDL) Archetype Query Language (AQL)
  27. 27. © Ocean Informatics 2016
  28. 28. Smart data, smarter healthcare Its. All. About.The. Data.  Change the viewpoint  Universal Health Record (data) vs EHR/EMR (app)  Independent of Application/Technology/Vendor  Platform  data shared between applications  Change the approach  Archetypes = building blocks  Clinician-driven, collaborative  Foundation for data storage, exchange, decision support, aggregation & analysis  Templates = clinical data sets  Aggregate & constrain – cater for clinician diversity © Ocean Informatics 2016
  29. 29. Final thought… © Ocean Informatics 2016

×