Bert Verhees wrote:
I understand more or less what you are saying about hard/soft parts, that is
the good thing of OpenEhr which you explain. Very good. But you still need to
store the soft parts, so you need a persistence layer.
This layer must interface with the kernel.
I did not find
Bert Verhees wrote:
I wonder, Ian, did you ever looked to Cache (www.intersystems.com)
It is called Post-relational, this is because it also can understand SQL.
But it is a kind of OO-database, I don't know if it has all the
OO-particularities like (multiple)inheritence, or object as field of
Message -
From: Bert Verhees bert.verhees at rosa.nl
To: openehr-technical at openehr.org
Sent: Friday, January 20, 2006 12:26 AM
Subject: Re: difficulties starting an implementation
I wonder, Ian, did you ever looked to Cache (www.intersystems.com)
It is called Post-relational
Ian McNicoll MMS wrote:
Either there is a documented interface to a persistence layer, or
there isn't.
It is quite possible I missed it in the documentations
But till now, I asked it three times in three days, is there a
documented interface to a persistence layer? Or do I have to puzzle
Bert Verhees wrote:
That is good, this means we can trust the dotnet-dll's. I already
loaded them in Borland dotnet studio, and everything seems to publish
itself as it should. The only thing is that seems to Eiffel publish a
lot more then you programmed. I am not sure what to do with it.
Ian McNicoll MMS wrote:
Hello again Rong,
Glad to hear things are progressing. Do you have any thoughts about
persistence layer options?
Hello Ian!
Well, we have been exploring the persistence layer ourself. We started
with using Prevayler for our demo application, and later chose to use
I believe that Mr. (Dr.?) Ian McNicholl is refering specifically to the fact
that implementing an EHR system solely using a relational DB is what won't
work. I believe he's not refering to the whole concept of OpenEHR, but just
to the fact that using a traditional relational system to store
Op donderdag 19 januari 2006 11:18, schreef Rong Chen:
snip
I do not know if it is useable in OpenEhr context, but I like the
ideas of Scott W. Ambler, he wrote a paper about
persistence-layers:http://www.ambysoft.com/downloads/persistenceLayer.pdf
This is about the same architecture as we
Hi JV,
Yes I am a doctor (GP) but no longer doing clinical work. I was not
saying that a relational DB would not work, just that without O-R
mapping tools or Row modelling/shredding techniques, it is very
difficult to support the extensibility/adaptability required by clinical
systems, to
Bert Verhees wrote:
I wonder, Ian, did you ever looked to Cache (www.intersystems.com)
It is called Post-relational, this is because it also can understand SQL.
But it is a kind of OO-database, I don't know if it has all the
OO-particularities like (multiple)inheritence, or object as field of
Hi William,
Pleased to oblige.
Scottish National eHealth.IM at T strategy:
http://www.ehealth.scot.nhs.uk/
Scotland is a small country pop. 5 million but which now has completely
devolved powers on Health matters and our flavour of NHS now differs
substantially from that in England. We have
On Thu, 2006-01-19 at 09:22 -0500, William E Hammond wrote:
I am writing a paper on national mandates for HIT and on nation adoptions
of the EHR. Can you point me to some documentation on Scotlands plans?
Hi Ed,
Additional resources that may be of help
Canada Health Infoway:
Of William E Hammond
Sent: 19 Ocak 2006 Per?embe 16:22
To: openehr-technical at openehr.org
Subject: Re: difficulties starting an implementation
Ian,
I am writing a paper on national mandates for HIT and on nation adoptions
of the EHR. Can you point me to some documentation on Scotlands plans
, January 19, 2006 8:58 AM
To: openehr-technical at openehr.org
Subject: Re: HIT Mandates was: difficulties starting an implementation
Thanks to Tim. Great things often happen through mistakes. I had meant to
send the email only to Ian and did not notice that I was sending to the
group. I have had
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060118/cdefb747/attachment.html
Op woensdag 18 januari 2006 01:16, schreef Sebastian Garde:
Hi Bert,
the way I understand the differences between openSDE and openEHR:
Thanks, Sebastian, really helpful answer, gives something to think of
Regards
Bert Verhees
Bert Verhees wrote:
example
A class has an interface, this what it makes visible to other classes. A
property is some characteristic of a class.
F.e a class Person has a property bodyLength. This can be in inches or
centimeters. For example bodyLength can give you centimeters or inches,
Hi,
It seems to me you are turning around a really subtle and complex concept.
Like a building, information systems must have some hard parts (to stand
up) and a flexible content (so you can live in it).
The usual way is to have the hard parts being whether a database model
or some pieces of
Op woensdag 18 januari 2006 17:10, schreef Ian McNicoll MMS:
Either there is a documented interface to a persistence layer, or there
isn't. It is quite possible I missed it in the documentations
But till now, I asked it three times in three days, is there a documented
interface to a
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
Bert Verhees wrote:
Op woensdag 18 januari 2006 17:10, schreef Ian McNicoll MMS:
Either there is a documented interface to a persistence layer, or there
isn't. It is quite possible I missed it in the documentations
But till now, I asked it three times in three days, is there a documented
Tim Cook wrote:
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
Gerard Freriks wrote:
Bert,
ITS = Implementable Technology Specification.
It is an HL7 specific term.
It is the process that translates an hierargical message specification
of a domain information model into: Edifact, HL7v2, XML (HL7v3), or
Java formats.
I don't know whether they
Bert Verhees wrote:
but as I see, there are very impressive projects in the
deploymentsector on the website.
They must have used databases, other programming languages, UML
created, component-interfaces, plans about how to follow the
OpenEhr-developments.
F.e. it does not seem effici?nt
Hi Thomas and others,
Before you start reading, I want to tell you, I think OpenEhr is a very
valuable project, and many people want to use the concepts.
There are however difficulties which I want to address. If sometimes my
writings seem unpolite or harsh, please keep in mind that English is
Of Bert Verhees
Sent: 17 Ocak 2006 Sal?? 12:43
To: openehr-technical at openehr.org
Subject: Re: difficulties starting an implementation
Hi Thomas and others,
Before you start reading, I want to tell you, I think OpenEhr is a very
valuable project, and many people want to use the concepts
Hi all,
Got some tips, just put a database under it and a GUI above, and there
is an application.
Sounds to me like a practical joke ;-)
If it is that easy? why isn't this easy piece of work not published,
somewhere on the openehr website?
I have no problem writing a GUI, or a
Tim Cook wrote:
On Wed, 2005-09-21 at 23:07 +0200, Bert Verhees wrote:
Please correct me if I am wrong,
Please take it as a request for information, or if I am wrong and need
to be corrected, as a discussion.
If you go here:
Hi all,
Some reders of this list have seen me before, I was implementing a part of the
GPICs-environment, about a year ago.
I do not do that anymore, the project stopped, it is regarded as finished.
I am now studying OpenEhr for a new project.
I spent yesterday all day on looking at the
On Fri, 2006-01-13 at 10:07 +0100, Bert Verhees wrote:
I am now studying OpenEhr for a new project.
...
Which documents should I read (first) to understand the way the thing works
(technical)
This won't help with the details of a specific implementation but it's
stuff you need to know.
Op vrijdag 13 januari 2006 16:13, schreef Tim Cook:
On Fri, 2006-01-13 at 10:07 +0100, Bert Verhees wrote:
I am now studying OpenEhr for a new project.
...
Which documents should I read (first) to understand the way the thing
works (technical)
This won't help with the details of a
While reading the docs, I stumble on the acronym ITSs. It may not be that
important, but I want to know, what does it mean, I searched on
www.acronyms.ch and found:
Incompatible Time-sharing System
Can someone tell me what it really means, thank you
regards
Bert Verhees
Bert,
ITS = Implementable Technology Specification.
It is an HL7 specific term.
It is the process that translates an hierargical message
specification of a domain information model into: Edifact, HL7v2, XML
(HL7v3), or Java formats.
Gerard
-- private --
Gerard Freriks, arts
On Wed, 2005-09-21 at 23:07 +0200, Bert Verhees wrote:
Please correct me if I am wrong,
Please take it as a request for information, or if I am wrong and need
to be corrected, as a discussion.
If you go here:
Please correct me if I am wrong,
Please take it as a request for information, or if I am wrong and need
to be corrected, as a discussion.
I will do a few statements about what I have seen around the openehr-website
- The folder in the RC 1 for ITS is a bit empty. No
database-definitions, no
36 matches
Mail list logo
