EHRGenEHR framework based on openEHR      Ing. Pablo Pazos Gutiérrez        pablo@openehr.org.es
The EHR environment• EMR  – Clinical recording applications (input)  – Local records  – Customized applications for:     •...
The EHR environment• Terminology Server  – terminologies, classifications, codes• Content Server  – archetypes & templates...
The EHR environment
EHRGen coverage• Doesn’t cover rules  XML Rule Engine
EHRGen objectives• Provide a fast way to create & modify  openEHR-based EMR applications• Provide adaptable systems deploy...
EHRGen features• One framework to create many EMR systems• Clinical knowledge is not hardcoded in the app• Changes in the ...
EHRGen functionalities• GUI autogeneration:   – from archetypes, UI templates and terminology   – Web, I18N• DB schema aut...
EHRGen architecture
EHRGenIng. Pablo Pazos Gutiérrez    pablo@openehr.org.es
Upcoming SlideShare
Loading in …5
×

EHRGen demo presentation

3,403 views

Published on

Published in: Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,403
On SlideShare
0
From Embeds
0
Number of Embeds
2,089
Actions
Shares
0
Downloads
29
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

EHRGen demo presentation

  1. 1. EHRGenEHR framework based on openEHR Ing. Pablo Pazos Gutiérrez pablo@openehr.org.es
  2. 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. 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. 4. The EHR environment
  5. 5. EHRGen coverage• Doesn’t cover rules  XML Rule Engine
  6. 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. 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. 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. 9. EHRGen architecture
  10. 10. EHRGenIng. Pablo Pazos Gutiérrez pablo@openehr.org.es

×