PING is now called Indivo (http://indivohealth.org/) and the recent conference
generated a lot of interests:
http://www.pchri.org/2006/
Best regards,
David
David H Chan, MD, CCFP, MSc, FCFP
Associate Professor
Department of Family Medicine
McMaster University
- Original Message
From:
Thomas Beale <[EMAIL PROTECTED]> wrote:
> >> Things are extremely clear.
> >> 1. Ocean informatics open source is all on subversion servers on
> >> http://svn.openEHR.org, and have been for some years.
> >
> > This requires a user name and password. This does not at all seem
> extremely
> > clear.
> Fred,
> if you were to spend 5 minutes to actually have a look at the site
> (which I agree is not wonderful, but it isn't impenetrable either), then
> you would find that under the "projects" menu you could access pages
> like the following:
> http://svn.openehr.org/knowledge_tools_java/TRUNK/pr
Thomas Beale wrote:
> Seref Arikan wrote:
>
>> Hi Tim,
>> Sorry I was not clear about the issue. I was hoping that there is an
>> existing proof of concept application for the mentioned test repository.
>> Since the repository can be the source for a "clinical document" as
>> referred in the
Fred Trotter wrote:
>> Things are extremely clear.
>> 1. Ocean informatics open source is all on subversion servers on
>> http://svn.openEHR.org, and have been for some years.
>>
>
>
> This requires a user name and password. This does not at all seem extremely
> clear.
>
Fred,
if you were t
Seref Arikan wrote:
> Hi Tim,
> Sorry I was not clear about the issue. I was hoping that there is an
> existing proof of concept application for the mentioned test repository.
> Since the repository can be the source for a "clinical document" as
> referred in the CDA docs, any simple application
Tim Churches wrote:
> Thomas Beale wrote:
>
>> Things are extremely clear.
>> 1. Ocean informatics open source is all on subversion servers on
>> http://svn.openEHR.org, and have been for some years.
>>
>
> Thomas,
>
> What is the user name and password needed to access the above Subversio
Hi Tim,
Sorry I was not clear about the issue. I was hoping that there is an
existing proof of concept application for the mentioned test repository.
Since the repository can be the source for a "clinical document" as
referred in the CDA docs, any simple application would do fine. I just
wanted
I think you are making this far more complex than it needs to be. All
open source software done under the openEHR Foundation is on the openEHR
website, and available under the licenses described here
http://www.openehr.org/about_openehr/t_licensing.htm
For software, the license is the Mozilla
Fred Trotter wrote:
> What we, as the community need from Ocean Informatics is a very clear
> commitment about
>
>- What you are releasing open source
>- When you will be releasing it
>- What license it will be under
>- Where it can be downloaded
>- What you are not releasing o
mspohr wrote:
> Yes, thank you. It does clarify things.
> I think we all need to understand the difference between an open
> standard and open software.
> If I understand correctly, your software is based on an open standard
> that anyone can use for interoperability. This is good. The software
Thomas Beale wrote:
> Things are extremely clear.
> 1. Ocean informatics open source is all on subversion servers on
> http://svn.openEHR.org, and have been for some years.
Thomas,
What is the user name and password needed to access the above Subversion
server?
Tim C
> >
> Things are extremely clear.
> 1. Ocean informatics open source is all on subversion servers on
> http://svn.openEHR.org, and have been for some years.
This requires a user name and password. This does not at all seem extremely
clear.
2. all Ocean's products are based directly on the openEH
Tim,
Thanks for the clarification. This is obviously a complex issue,
and my comments may not completely apply given the disctinction between a
standard and software. Still what I would really like out of this discussion
is for the relationship between the community and the openEHR proj
Yes, thank you. It does clarify things.
I think we all need to understand the difference between an open
standard and open software.
If I understand correctly, your software is based on an open standard
that anyone can use for interoperability. This is good. The software
itself to access this op
Seref Arikan wrote:
>
>
> Hi
> Thanks anyway, having some CDA docs to play around sounded very
> attractive, at least I tried :)
> regards
> Seref
>
I wonder if you understand that "having some CDA docs to play around"
is not a computable approach?
CDA documents are created 'by restriction' w
Hi Fred (and all),
While I do not in any way officially speak for openEHR.org, Ocean
Informatics, or other openEHR developers; I must say that I think
there is some confusion over the differences between the specification
and the software and maybe even what openEHR is and is not.
openEHR is
Fred Trotter wrote:
>
> What we, as the community need from Ocean Informatics is a very clear
> commitment about
>
>
>- What you are releasing open source
>- When you will be releasing it
>- What license it will be under
>- Where it can be downloaded
>- What you are not releasin
mspohr wrote:
> Thomas,
> We don't want to argue about open source. We just want a clear
> statement from you.
>
> Is your software open source?
>
> If yes, then there should be a place where we can download the source
> with a GPL type license.
>
> If no, then this is a proprietary system and y
Tim Churches wrote:
> Thomas, the full text of the paragraph from my post which you quote is:
> "However, after nearly 10 years of work on openEHR, or over 15 years if
> you include work on GEHR (Good Electronic Health Record, which was its
> conceptually similar predecessor), there is still no com
Hi
Thanks anyway, having some CDA docs to play around sounded very
attractive, at least I tried :)
regards
Seref
Thomas Beale wrote:
>
> Seref Arikan wrote:
> > Hi Thomas,
> > At the moment I am working on a project where I need CDA support. Would
> > it be possible to get CDA docs from the repos
I have been staying on the sidelines for this one but I think this is an
important point that does need clarifiication.
You can answer "hybrid". You can say that your product is both an open
source and a proprieatary product. What is important it that your company be
very clear about what it is c
Thomas,
We don't want to argue about open source. We just want a clear
statement from you.
Is your software open source?
If yes, then there should be a place where we can download the source
with a GPL type license.
If no, then this is a proprietary system and you shouldn't make
statements th
mspohr wrote:
> Thomas,
> Just a word of caution on "I don't want to get into arguments about
> Open Source"...
> It seems that you are asking for help in testing, debugging, and
> developing your software but you aren't willing to make this an open
> source project (at this time).
no, we already
Thomas Beale wrote:
> Tim Churches wrote:
>> their decision to make the intellectual property associated with the
>> theoretical underpinnings of openEHR freely available, and to not pursue
>> patents on the ideas behind openEHR (some of which are novel, some of
>> which are not so novel).
>>
>> Ho
Adrian Midgley wrote:
> Interested, yes.
> Capable ... perhaps less so.
> Is Python at all likely?
>
>
I would have to ask an expert about thatTim Cook - are you reading this?
> Which end of Australia is it?
>
happens to be in Adelaide. Performance is acceptable from Turkey and the
Nethe
Seref Arikan wrote:
> Hi Thomas,
> At the moment I am working on a project where I need CDA support. Would
> it be possible to get CDA docs from the repository you've mentioned? Or
> what can we do to make it happen if it does not exist at the moment?
>
the EhrBank openEHR server just does op
Tim Churches wrote:
> their decision to make the intellectual property associated with the
> theoretical underpinnings of openEHR freely available, and to not pursue
> patents on the ideas behind openEHR (some of which are novel, some of
> which are not so novel).
>
> However, after nearly 10 years
Thomas Beale wrote:
> I would like to know if anyone here is interested in being able to play
> with a demonstration system (located in Australia) over a web-service
> (published API); currently you would write C# code against a client-side
> DLL - the idea is to use the openEHR repository as a
29 matches
Mail list logo
