> Hi all, > > Interesting discussions! I think initially we need to focus on full > interoperability between "native" openEHR implementations across different > platforms. But in the long run, we need to also make sure that all openEHR > system have unified way of doing data exchange with external formats. > > Early on, we have done a lot work just to make sure the tools - parsers, > serializers and editors have good interoperability. It's quite challenging > but it's possible and the benefits are obvious. I particularly want to > stress the need to collaborate on these matters in the open space. As a > community, we can create synergies by working on a common code base for core > components that are crucial for interoperability. > > Besides the items proposed by Tom, I would like to comment on a more > detailed level. There is an on-going work for a (nearly) platform > independent way of testing (validating) archetypes based system. Initially > the scope is targeting on the kernel, which is the essential pieces of > software in any archetypes based system. Archetypes based data creating, > validation and querying are validated using platform independent test > fixtures and test case specifications. Test runners are the only bits of > platform-specific in the framework but hopefully they can be provided as > open source implementations for each major platform. Test fixtures and test > cases are generated semi-automatically and can be created once and used by > any platform. We intend to submit this work to MIE2008 within a week or so > and will likely provide a proof-of-concept implementation within the Java > project. If it goes well, we would like to demonstrate it on a software > workshop at MIE2008. >
sounds like time for new wiki page ;-) - thomas
