1. EHRGen
EHR framework based on openEHR
Ing. Pablo Pazos Gutiérrez
pablo@openehr.org.es

2. The EHR environment
• EMR
– Clinical recording applications (input)
– Local records
– Customized applications for:
• specialties (e.g. cardiology)
• departments (e.g. emergency)
• EHR
– Shared records (search, output)
• Many medical specialties for the same patient
• Demographic
– Persons, organizations & roles

3. The EHR environment
• Terminology Server
– terminologies, classifications, codes
• Content Server
– archetypes & templates
• Rules Server (CDS & epidemiology)
– alerts, recommendations, reminders, notifications
• Process Server
– BPM, workflow mgt., task mgt.
• CPOE
– order management (send, authorization, receive)

4. The EHR environment

5. EHRGen coverage
• Doesn’t cover rules  XML Rule Engine

6. EHRGen objectives
• Provide a fast way to create & modify
openEHR-based EMR applications
• Provide adaptable systems deployable in any
healthcare environment with minimum effort
• Lower costs, minimize time to market,
formalization of the development process,
long term maintainability, …

7. EHRGen features
• One framework to create many EMR systems
• Clinical knowledge is not hardcoded in the app
• Changes in the clinical record structure without
changing the source code
• Local or remote demographic repository
• Security:
– role based user authorization
– authorization permits by clinical domain
• Supports versioned archetypes and UI templates
• Technologies: Java/Groovy/Grails/MySQL

8. EHRGen functionalities
• GUI autogeneration:
– from archetypes, UI templates and terminology
– Web, I18N
• DB schema autogeneration:
– from openEHR domain classes
• Generic business logic:
– input data validation (using archetypes)
– data binding for persistence
• creates compositions from input data
• Semantic querying & data aggregations (prototype)

9. EHRGen architecture

10. EHRGen
Ing. Pablo Pazos Gutiérrez
pablo@openehr.org.es