Hi all! We had a poster titled "REST Based Services and Storage Interfaces for openEHR Implementations" at a Swedish conference in September. I have now finally gotten around to reformatting it to be readable when read on screen or printed as a three-page booklet on normally sized (A4) paper. It is available at: http://www.imt.liu.se/~erisu/2010/EEE-Poster-multipage.pdf Some of you have already heard these ideas at Medinfo in Capetown.
Questions and discussions are very welcome (preferably on the technical list, not the clinical one that I am cross posting this announcement to). We are now in the process of writing a proper paper about this and will of course release our implementation as open source. The most interesting thing about all this is probably not our particular implementation, but rather the approach of slicing the openEHR system implementation "elephant" into smaller pieces so that different people and projects can focus on smaller parts like GUI, storage or decision support. As long as the building blocks can speak http they can be connected no matter what language or platform they are implemented in. Our hope is that this could lead to interoperability _within_ openEHR systems made by parts from different actors, in addition to the current interoperability _between_ openEHR systems. I also wonder if there are others that would be interested in helping out writing an openEHR ITS (Implementation technology specification) for openEHR service model via REST (after the proper paper is finished... need to focus...). The ITS should preferably be tested in several different systems before being considered finished - no good specification without at least two independent interoperable implementations. Best regards, Erik Sundvall erik.sundvall at liu.se http://www.imt.liu.se/~erisu/? Tel: +46-13-286733
