Hello again Rong, Glad to hear things are progressing. Do you have any thoughts about persistence layer options?
In Scotland there is a hope to move to a single EHR for the whole country across all specialities. Personally I remain unconvinced that this is totally achievable, but if it is, it will demand a highly flexible and extensible architecture, backed by an equally structured complex persistence layer - the traditional relational DB will simply not work. Regards, Ian > > As I promised to reply to your post on the list, here I am. :) > > Personally I am convinced it is possible to implement the openEHR > specification even at this stage. We, at Acode, already proved it by > building a pilot EHR system which meets real-life requirement. Of > course, it wasn't easy since we started from scratch with the Java > implementation (kernel, parser, persistence, GUI), but also the > specification has been a moving target. After the version 1.0 > specification is released, the situation will be quite different. Since > then, there won't be any major changes on the reference model which > really is the foundation of interoperable EHRs. This will hopefully > encourage more open source or commercial development on openEHR in the > near future. > > Cheers, >
