openEHR and DIPS Arena: the 'Best of Breed 3.0' revolution
Denunciar
Compartir
•2 recomendaciones•1,044 vistas
openEHR and DIPS Arena: the 'Best of Breed 3.0' revolution
•2 recomendaciones•1,044 vistas
Denunciar
Compartir
Descargar para leer sin conexión
Presentation given at DIPS Forum June 2016.
Más contenido relacionado
La actualidad más candente
La actualidad más candente(20)
Destacado
Destacado(17)
Similar a openEHR and DIPS Arena: the 'Best of Breed 3.0' revolution
Similar a openEHR and DIPS Arena: the 'Best of Breed 3.0' revolution(20)
Último
Último(20)
openEHR and DIPS Arena: the 'Best of Breed 3.0' revolution
- 1. Dr Ian McNicoll Co-chair openEHR Foundation freshEHR Clinical Informatics Ltd. openEHR and DIPS Arena: the ’Best of Breed 3.0’ revolution DIPS Forum Stavanger June 2016
- 2. Introduction Dr Ian McNicoll Clinician Former Scottish GP Health informatician Co-chair openEHR Foundation freshEHR Clinical Informatics Commercial software developer ‘Clinical hacker’
- 3. Health information is … Healthcare data is highly complex and ever changing Biological Cultural Political Getting good requirements from clinicians is hard “Nasty”
- 4. Anatomy of an eHealth system
- 5. the ‘information model’ Is used to manipulate information in the computer’s memory Often written in a specific program language Generally locked-in to each application Not easily shareable
- 6. Information models power the web
- 9. ‘Best of breed’ architecture
- 10. Best of breed 2.0: ’closed platform’ architecture
- 11. HSPC: SMART on FHIR on Clinical Models
- 12. openEHR CDR openEHR Rest API + AQL Best of Breed 3.0: ’open platform’ architecture open Information Model App App App
- 15. openEHR - key goal Provide specifications for an open platform where the data in any openEHR system is completely exchangeable regardless of programming language regardless of human language regardless of internal database technology
- 16. openEHR: Archetypes open source computable models of discrete clinical concepts Familiar components of a health record Blood pressure, Body weight Medication order, Family history ‘Maximal dataset’ Capture as many clinical perspectives as possible
- 18. Platform: Clinical content development
- 19. SMARTPlatforms Pluggable Webapp API HL7 FHIR Clinical Content Exchange NHS API Clinical Data Repository (CDR) Detailed Clinical Content Development Clinical leadership PRSB Terminology Centre HSCIC Non openEHR systems Archetype+ SNOMED Clinical Content definitions
- 20. Building a ‘legacy’ system Clinicians Business Analyst Technical Modeller Database Developer User Interface Designer app
- 22. User Interface Designer Building ‘Best of Breed 3.0’ Clinicians Business Analyst User Interface Designer User Interface Designer Clinicians Business Analyst Clinicians Business Analyst app app arketyper.no appShared Information Model
- 23. openEHR:’Best of Breed 3.0’ ‘free the data’ ‘commoditise clinical data handling’ ‘clinically-driven content definition’
Notas del editor
- Health information really is ‘nasty’, and its complexity presents huge challenges. Developers building apps, messages and APIs need good requirements from clinicians. We need to try and ensure that those requirements are widely applicable - we need to involve clinicians in capturing and sharing what information tools they need in their day-to-day working environment. But this is hard! (BUILD) These descriptions do sound a bit like the seven dwarfs (BUILD), but this really captures the essence.
- Medication does syntax is a particularly taxing area - how do we capture a prescription like this one, making drug name, dose amount, timing and maximum dosage computable (BUILD) - here’s an example of what that might look like (BUILD) How do we cope with product vs dose prescribing - the example demonstrates how primary / community care prescribing and inpatient prescribing use different ways of effectively saying the same thing