On Wed, 2006-01-18 at 17:20 +0100, Bert Verhees wrote:

> Thanks Ian, thanks very much, for your clear answer. When there will come no 
> further mails which state different, I take your answer for truth.
> 
> I guess I have to write it myself, or get help from people which already did.
> The row-storage as from OpenSDE looks as a good solution.
> 
> But when this is true, and also what you state below, this means that there 
> is 
> still a long way to go for OpenEhr before it will be implementable.
> 
> Is that true? Do I understand that well?


Hi Bert,

I think you are still a bit confused about "What is OpenEHR?" 

See the FAQ: http://openehr.org/FAQs/t_about_FAQ.htm 

OpenEHR is (essentially) a non-profit organization that produces
specifications for an electronic health record. The specifications are
implementation generic documents.

Eiffel is used as the reference platform in order to prove that the
model actually is implementable (at a class level). 

The questions you are asking are implementation specific.  I suggested
once before that you might join the implementers mailing list.  Granted
there is much traffic there right now but really that is where these
discussion would make more sense.
http://openehr.org/advice/contents.html
Not to say that they are not supposed to be here on the technical list.
The description does still specify "software building".

But on the implementers list you could address the fact that you want
help/collaboration with developers using Java, Hibernate and MySQL (if
those are your choices) to implement an OpenEHR server. 

Again, it will help you if you separate the concepts of the generic
model and the implementations.

Hope this helps.

Cheers,
-- 
Tim Cook

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060118/10332461/attachment.asc>

Reply via email to