The solution
1) Make it easy data into electronic form:
2) Integration:
Slide 14
Slide 14 text
OpenEyes
• Web application
• Open Source
• Clinically led
• Flexible
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
OpenEyes at MEH
• In use at all 13 sites
• All prescriptions, correspondence,
operation bookings, since January 2012
• Clinical modules for cataract, glaucoma,
medical retina released, others by end of
2013
Slide 18
Slide 18 text
Prescribing
Slide 19
Slide 19 text
Correspondence
Slide 20
Slide 20 text
Clerking
Slide 21
Slide 21 text
Clerking
Slide 22
Slide 22 text
Event types
• Adding functionality
• A large collection
• Many more to come
• ‘Developer community’
Slide 23
Slide 23 text
‘Event’ store
OE Developer
Do your own!
Need a new
event type?
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
Will this approach
work outside
Moorfields?
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
Will this approach
work outside
Ophthalmology?
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
No content
Slide 31
Slide 31 text
OpenEHR Archetype
OpenEHR Template
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
The Core Team
Personnel WTE
Director 0.4
Developers 4.5
Product/Project Managers 2
Quality Assurance 1
Support 1
(Funded by MEH through to 2017)
Slide 34
Slide 34 text
Other resources
• > 50 Ophthalmologists (volunteers)
• Developers in Cardiff and Maidstone
(Funded by local host Hospital)
Slide 35
Slide 35 text
Why Open Source?
Slide 36
Slide 36 text
Open source
• Good fit for clinicians
Slide 37
Slide 37 text
Clinical development
Clinician has idea
Improved results
Tries it out
Publishes it Others modify it
Slide 38
Slide 38 text
Open source
• Good fit for clinicians
• Speed and flexibility
Slide 39
Slide 39 text
Collaboration
Slide 40
Slide 40 text
Process
• Form Group
Slide 41
Slide 41 text
Process
• Form Group
Cataract
Strabismus
Core
ARMD
Glaucoma
Adult A&E
Medical Retina
Slide 42
Slide 42 text
Process
• Form Group
• Create written
specification
(What and How)
Slide 43
Slide 43 text
Process
• Form Group
• Create written
specification
• Turn into web
‘elements’
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
Process
• Form Group
• Create written
specification
• Turn into web
‘elements’
• Discuss!
Slide 47
Slide 47 text
Open source
• Good fit for clinicians
• Speed and flexibility
• Security
Slide 48
Slide 48 text
No content
Slide 49
Slide 49 text
Open source
• Good fit for clinicians
• Speed and flexibility
• Security
• Low(er) cost
Slide 50
Slide 50 text
Licences
• GitHub ($25 per month)
• JIRA ($1200 for 25 users $600 per year
• Sauce Labs ($150 per month)
• Travis (£500 per year)
Slide 51
Slide 51 text
Open source
• Culture
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
Moorfields
Cardiff
Fife
Maidstone
Salisbury
Glasgow
Liverpool
Slide 55
Slide 55 text
Open source
• Culture
• Control
Slide 56
Slide 56 text
Users
OpenEyes
Slide 57
Slide 57 text
Users
Foundation
IMS
Data Colleges
OpenEyes OpenEHR
Industry
Slide 58
Slide 58 text
Open source
• Culture
• Control
• Funding
Slide 59
Slide 59 text
The Core Team
Personnel WTE
Director 0.4
Developers 4.5
Product/Project Managers 2
Quality Assurance 1
Support 1
(Funded £3.5million by MEH through to 2017)
Slide 60
Slide 60 text
Conclusions
• OpenEyes is an enabler for change
• Clinical leadership is vital
• Open Source is a good fit for clinical
software, but barriers remain