There is some basic architecture overview information in section 6 of 
http://svn.openehr.org/specification/TRUNK/publishing/architecture/overview.pdf

Otherwise the persistence notes I just uploaded may help the discussion.

- thomas


Bert Verhees wrote:
>
>> Of cause it is possible to hide everything behind a persistence layer
>> _interface_ and doesn?t talk anything about what we have behind the
>> interface. But the subject and quite many of the mails had talked 
>> about the
>> persistence layer (and not the interface), then it is necessarily to 
>> know
>> what kind of application it should support.
>>  
>>
> It was me bringing up the subject a few times, and it was because that 
> was a part which was not worked out in the openeher specs, and because 
> I am quite new here, I thought I had missed something.
> It was difficult to make myself clear, and therefore difficult to get 
> a clear answer, that is why some mails about this were sent.
>
> I thought there had to be a clear point where one could point, like 
> Lego-blocks (www.lego.com), you take a persistence layer block, and 
> put it below the reference kernel, put the archetype kernel-block on 
> top and an GUI block on top of that, and you have build an information 
> system.
>
> I could'n't find a clear spot where to put the persistence layer 
> block, nor could I find a description of the interface that openehr 
> was prepared for, and I heard in Holland people shout, just put a 
> database below and run it, and I thought, am I a fool?
>
> But now it is clear to me. Those shouting people did not have much 
> knowledge on the subject.
>
> There are no persistence layer defined in the OpenEhr specs, Thomas 
> said there will be specs for this after some time.
>
> Agree?
>
> Bert
>
>


-- 
___________________________________________________________________________________
CTO Ocean Informatics (http://www.OceanInformatics.biz)
Research Fellow, University College London (http://www.chime.ucl.ac.uk)
Chair Architectural Review Board, openEHR (http://www.openEHR.org)


Reply via email to