1 / 21

HISI Conference – 18 th November 2010 Towards use of OpenEHR Archetypes to support views of

HISI Conference – 18 th November 2010 Towards use of OpenEHR Archetypes to support views of Cystic Fibrosis Review Records Derek Corrigan. Overview. Problems specific to developing clinical systems OpenEHR – a potential solution? A methodology for developing OpenEHR systems

deana
Télécharger la présentation

HISI Conference – 18 th November 2010 Towards use of OpenEHR Archetypes to support views of

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. HISI Conference – 18th November 2010 Towards use of OpenEHR Archetypes to support views of Cystic Fibrosis Review Records Derek Corrigan

  2. Overview Problems specific to developing clinical systems OpenEHR – a potential solution? A methodology for developing OpenEHR systems Application of methodology to a clinical case Conclusions about OpenEHR experience

  3. Clinical Systems -The Software Design Perspective Developing clinical systems is difficult! Clinical knowledge is broad and changes quickly Software developers are not domain specialists Clinical knowledge is embedded in software Cluttered, static and inflexible views of data

  4. Clinical Systems - The Clinicians Perspective The Clinical guidelines : • Increasingly demanding multi-disciplinary care teams for best practice • This requires flexible and dynamic views of data to cater for all each team member as well as the overall team. • Incompatible with previous limitations

  5. OpenEHR – A Silver Bullet? Specific implementation of 2 level information modelling employed using concepts of archetypes and templates. Courtesy of OpenEHR Foundation

  6. Cystic Fibrosis – A Case Study Why Cystic Fibrosis? • Was kindly given access to CF registry documentation • Very relevant to Ireland – highest incidence in world • Best practices demands multi-disciplinary team care relating to a number of discreet clinical areas • By implication requires dynamic views of CF patient data to support different team member requirements • Could I satisfy team data view requirements using OpenEHR archetypes and templates and provide a “how-to” guide for others?

  7. Step 1

  8. Step 1 Cystic Fibrosis Periodic Review Covers a number of clinical areas including physical functions, nutrition, physiotherapy, medication

  9. CF Registry DB Schema Step 1

  10. Steps 2 and 3

  11. OpenEHR Clinical Knowledge Manager (CKM) – Search for archetypes Step 4

  12. Step 5 Spirometry Archetype Design Key OpenEHR Goal Should be clinically complete and reusable

  13. Step 5 Spirometry Archetype Design V2

  14. Archetype Editor Step 6

  15. Step 7 Develop Templates (Views)

  16. Step 7

  17. Publish Archetypes to CKM Step 8 • Spirometry archetype submitted to OpenEHR • Aspects incorporated into new archetype they were working on • To be published on CKM and currently being used in system in paediatric hospital system in Slovenia

  18. OpenEHR - Conclusions • OpenEHR worked well – descriptive enough from a data perspective – too flexible though? • Will clinicians use this? Jury still out • Design patterns for archetypes could help • OpenEHR CKM is a very powerful tool to locate and reuse existing archetypes quickly • Global OpenEHR community - archetype features developed in Ireland being used in application in Slovenia • Publication of archetypes to CKM, and governance needs to be streamlined – most still in draft form • If not done, localised archetypes will be used – defeats the aim of supporting reuse of archetypes

  19. Questions ?

More Related