Hi all,
Some notes from our openEHR implementor gathering at Maastriht MIE
conference.
Rong
TODO List
1. Roadmap for the Java land
2. Quick start doc for new developers
3. Demo application driving by archetypes
4. Dev tools / environment
* build system - make nightly build + integration tests
* binary, apidocs publishing
5. Enough description for all components on the roadmap
Component List
Existing Components
* Kernel (RM, AM, Object creation?)
* ADL Parser
* ADL Serializer
Existing Components / Applications not on the openEHR site
* Java Archetype Editor (from Linköping Univ.)
* Archetype Finder (from Queensland Univ.)
Wished Components
* Generic Persistence Layer (priority 1st) - input from Ocean
o generic API hide behind DAO interfaces
o for demo purpose (serialization or in-memory)
o for prototype applications
o solid and fast solution
o optimized hibernate mapping on coarse level
* Generic Presentation Layer (diff level) [open source: cocoon]
o Entry form generator
o Template support?
o HTML based interface
+ generic validation javascript code
+ resuable HTML code for each leaf node constraint
+ sensible widgets for data structures - list, tree,
table, history
+ widegets for high level objects (composition, entries)
+ navigations within the GUI (internal ref etc)
+ configurable!!
+ reusable archetype-level widget (e.g. blood pressure
measurement)
+ XML/XSLT based approach?
o Java Interface Swing / SWT (useful for java desktop application)
* Services Layer?
o existing interface from Acode?
o draft SM from openEHR
o minimal service implementation required by kernel
+ terminology service with openEHR vocabulary
+ measurement service
+ archetype service
+ EHR service
+ demographic service
+ security service ?
* Generic Client ?
o use cases ?
* Demonstration applications
o Standalone Desktop application that can display GUI and
validate entries based on archetypes
o Web based demo application with persistence layer