Hi Bernard I have just made post the should cover part of your question. As mentioned in this post the kernel component is central to the architecture of an openEHR system as it brings the two models together. For persistence many solutions would be possible. Like XML (that what Ocean Informatics uses in their EhrBank product) or an object-relational-mapping solution. But it should be noted that just instances of the reference model need to be persisted including references to the archetypes used to create the instances. The archetypes can be retrieved again separately when the persisted data is loaded through the kernel.
For Java kernel code have a look at http://svn.openehr.org/ref_impl_java/TRUNK/project_page.htm Thilo On 5/31/07, B21Fern at aol.com <B21Fern at aol.com> wrote: > > > Hi Thilo > > I saw your most helpful account on openEHR archetypes etc in the > technical at openehr.org. Do you know of an account describing an end to end > example of it for a medical data value, say blood pressure. How it is really > implemented in the database to the interface design and why etc. If we take > blood pressure as an example, I assume there will be many archetypes > involved and at another level certain amount of say Java classes. > > Thanks > > Bernard Fernando (GP)
