The openEHR Java Reference Implementation Project

1
The openEHR Java Reference Implementation Project

• Rong Chen
• The openEHR Implementation Tutorial and
• Software Workshop
• Medinfo 2007 Brisbane

2
Overview History

• Year 2004 - started from scratch in Sweden
• End of 2004 - released under GPL
• March 2005 - adopted by openEHR as the Reference
  Kernel Implementation in Java
• October 2006 Release 1.0.1 RC1
• August 2007 Aiming for Release 1.0.1 RC2
• Implemented specs but a moving target!
• 0.9 gt 0.95 gt 1.0 gt 1.0.1

3
Licensing

• Released under multiple licenses
• Mozilla Public License (MPL)
• GNU General Public License (GPL)
• GNU Lesser General Public License (LGPL)
• Open source software license
• Public source repository
• Business friendly

4
Goals

• Validate design specifications
• Lead to improvement of the design
• Provide a reference implementation
• Educational purpose
• Explore new design ideas
• prototyping EHR systems
• Provide reusable software components
• Synergies between companies research teams
• Ultimate goal gt Quality, interoperable EHRs

5
Road Map

• Core components
• RM, AOM, ADL parser serializer
• Presentation layer
• GUI, templates
• Persistence
• Storage, EHR Query

6
Presentation Layer
Templates (Screen Forms)
GUI Logic
Business Logic Layer
Kernel
Archetypes (Domain Concepts)
Object Creation Validation
Application Logic
ADL Parser
Generic EHR Client
Reference Model
Archetype Model
Generic Services
EHR Service
Demographics Service
Archetype Service
Terminology Service
Security Service
Identity Service
Persistence Layer
OR Mapping (Hibernate)
RDBMS
Data Access Objects
7
2 years from now..

• Full blown EHR demonstrator
• Web-based user interface
• archetype/template enabled kernel
• Query supported scalable persistence layer
• openEHR/13606 EHR Extracts
• Sensible archetyped EHR content
• More better reusable components
• Establish sustainable development process and
  engage more developers

8
Status

• Release 1.0.1 RC1
• openehr-rm-core 0.1, common, support, data types,
  data structure
• openehr-rm-domain 0.1, ehr demographics
• openehr-aom 0.1, archtype object model (AOM)
• openehr-ap 0.1, openEHR archetype profile
• adl-parser 1.0.5, ADL gt AOM, AP
• adl-serializer 0.1, AOM, AP gt ADL
• xml-serializer 0.1, AOM, AP gt XML
• And other supporting components..
• Release 1.0.1 RC2
• Will be announced this month!

9
Development Process Tools

• Unit testing JUnit
• gt 300 testcases for features bug fixes
• Project management system Maven 2
• Continuous Integration server Contiuum
• Version control system Subversion
• no commit should break a successful build
• Online javadocs jar download
• Will be automated nightly builts etc
• Lacking a meeting schedule for the committers and
  a common work plan, release plan and roadmap

10
Related projects

• Child Leukemia Treatment Management System, Acode
  Karolinska University Hospital, Sweden
• Archetype Editor other research projects,
  Linköping University, Sweden
• Intensive Care Unit application, Uraguay
• Integrated elderly care system, the Netherlands
• Archetype Finder, Central Queensland University
• RD activities at Cambio

11
Java community

• Research teams
• UCL team from the UK
• Dipak Kalra, David Lloyd, Yinsu Lim, Nathan Le
• LiU team from Sweden
• Erik Sundvall, Mattias Forss, Mikael Nyström
• Central Queensland University
• Sebasitian Garde
• Manchester University
• Rahil Qamar
• Commercial entities
• Ocean Informatics
• Thomas Beale, Sam Heard, Heath Frank
• ACODE (Ice Medical Informatics)
• Göran Pestana, Tore Fjaertoft
• Cambio Healthcare Systems
• currently sponsoring the Java project through
  Rong Chen
• Individuals
• Bert Verhees, Rodrigo Filgueira, Johan
  Hjalmarsson, Jonas Andersson, Joakim Fredriksson,
  Routis Haralampos

12
The openEHR Java Implementation Technology
Specification

• http//svn.openehr.org/specification/TAGS/Release-
  1.0.1/publishing/its/Java/openEHR-JavaITS.pdf
• Mapping between openEHR assumed types and Java
  native types
• Camel case naming convention
• Generics support (jdk 1.5 required)
• Design by Contract
• Value objects and immutable objects
• Based on the Java implementation experience and
  serve as guidelines for the Java project

13
You are invited!!

• Download and work with the software
• Java project discussion list
• Maybe still be closed
• Receive svn commit alerts
• openEHR implementer / technical lists
• Implementation issues
• Design specs issues
• Project page
• http//svn.openehr.org/ref_impl_java/TRUNK/project
  _page.htm
• Coming online tutorial material based on the
  following coding exercise

14
(No Transcript)