GlobalHealthUSA would like to design and implement an EHR system for their disease management system platform. We would like to use OpenEHR but have the following questions:
Can OpenEHR be implemented in a windows(MS) .NET environment?
Can OpenEHR be used to develop an ISP version so several doctors can use it?
Has any one done such an implementation before, if so is there any web documentation?
Can we use our existing SQL 2005(MS) database?
Is there an existing client used to access OpenEHR?
Besides the .Net C# implementation by Ocean, there is an open source implementation in Java. It is not as complete or advanced as the Ocean implementation, but it does provide the Java implementation of nearly all published specifications. More details see the project page: http://svn.openehr.org/ref_impl_java/TRUNK/project_page.htm
There is an active community gathered around the Java project, from both academic and commercial side. You are welcome to contribute to the Java project.
In so far, not because I like to disagree, but regrettable, many of the
function/method-bodies in the Eiffel-code are empty. Eiffel seems merely
to be/have been used as a kind of case-tool instead of really building
a openehr kernel-implementation.
Which is a good use for Eiffel, but it is something else then writing an
implementation
One must take care when reading the this code because Eiffel supports
multiple inheritance, which is not supported by Java or C#. So
translating the Eiffel-skeleton to Java or C# causes at some places
code-redundancy and tricky coding.
But besides that Openehr is a great concept, and Ron's Java-kernel is a
great piece of work, the C# kernel is to, I am sure, it is build close
to the source of design.
I am building a Java-implementation too, based on Rong's kernel, he has
solved many problems and set directions, I am now using, and extending
this to an (for my purpose) applicable product.
In so far, not because I like to disagree, but regrettable, many of the
function/method-bodies in the Eiffel-code are empty. Eiffel seems merely
to be/have been used as a kind of case-tool instead of really building
a openehr kernel-implementation.
Which is a good use for Eiffel, but it is something else then writing an
implementation
I don't know what you're referring to, Bert. The Eiffel code has most
definitely been written as an implementation. We are using it. ADL Workbench
is built entirely in Eiffel. The Ocean Archetype Editor, which is written in
VB.NET, uses the Eiffel kernel classes in the form of a .NET assembly.
Maybe you've been looking at the Eiffel code via EiffelStudio's "contract"
or "interface" views: these views hide the implementation of the classes.
In so far, not because I like to disagree, but regrettable, many of the
function/method-bodies in the Eiffel-code are empty. Eiffel seems merely
to be/have been used as a kind of case-tool instead of really building
a openehr kernel-implementation.
Which is a good use for Eiffel, but it is something else then writing an
implementation
I don't know what you're referring to, Bert. The Eiffel code has most
definitely been written as an implementation. We are using it. ADL
Workbench
is built entirely in Eiffel. The Ocean Archetype Editor, which is written
in
VB.NET, uses the Eiffel kernel classes in the form of a .NET assembly.
Maybe you've been looking at the Eiffel code via EiffelStudio's "contract"
or "interface" views: these views hide the implementation of the classes.
- Peter
Sad is that I cannot get the EiffelStudio (Linux-version) to run on my
Linux-machine, some vague errors and nothing to find on the Internet.
The ADLworkbench has another problem, in Wine, it does not refresh the
treeviews (after clicking on it). Too bad, both things, so I don't use
them both, which I regret. But I hate working on Windows. There are other
advantages on my Linux-environment which I enjoy very much.
So I was looking at the website, I did (also in the past) take a look in
the SVN TRUNK tree, because I wanted to check something, I use it as a
case tool, so for me it is no problem. Yesterday I looked at three files,
all had empty function bodies (f.e. ) in composition.e which is a rather
crucial file.
That class, like most classes in the "rm" cluster, isn't compiled into
ADL Workbench or our .NET DLL. I'm not sure why. Sounds like a question
for Thomas
That is why you can't really talk of an available reference
implementation in Eiffel, but it is a skeleton for case-tool-purposes
