Hi Bert, hi Tim, thanks for the quick reply.
Bert Verhees wrote: > > You also need a service/API-layer, from which an application can connect > to your kernel. Like the persistence-layer, you must design and write > this yourself. > In short, that is about it, and then you have your OpenEhr application. > ;-) > Yes, you're right, that's basically what makes a real app, but since everybody probably seems to write it himself, I was just wondering if somebody has actually published some of the codes/approaches or some people have joint developments. Of course, in some cases this kind of work is how IT consultants and sw engineers make a living and/or due to legal/contract reasons, developments cannot be published. But I want to make sure that I don't start from scratch if there's already something out there I am missing, that already builts on top of openEHR. Thanks for the offer regarding questioning. I will let you know if specific questions come up. I am actually still studying the docs in more detail at the moment. It might keep me busy for a while. @Tim: I will probably go with the java implementation, since it's my language for quite some years now. Mathias -- View this message in context: http://www.nabble.com/How-to-start-an-application-with-openEHR-tp18247023p19458745.html Sent from the openehr-technical mailing list archive at Nabble.com.
