I have saved some of the emails in this thread - they are a good sysnthesis
of the world out there. My vision is that the complexity of the things that
we want to share will increase. We started with messaging and while it has
had a lot of success - HL7 in particular - and while there will always be
messages - the next task has been interoperability with applications
communicating more complex information - CORBAMed. In the future we will
want to share entire EHRs and that is where GEHR is aimed. I think that
systems in the future will use all three. GEHR will only come into its own
when everybody decides it is worth standardising the record architecture -
it makes the messages and interoperability so much more straight forward.
And then we can share application components that work with EHRs!
____________________________________________________
Sam Heard, Director
General Practice Education and Research Unit
NT Clinical School, Flinders University
PO Box 41326
Casuarina NT 0811
Tel: (08) 8922 7937, Fax: (08) 8922 7928
www.ntmed.flinders.edu.au
The Good Electronic Health Record
www.gehr.org
__________________________________________________
----- Original Message -----
From: "Alvin B. Marcelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, 3 March 2000 6:51
Subject: Focusing on interoperability
> It has been silent. But I know the projects have been surging on...
>
> Question:
>
> It was mentioned that most of the open source projects, being generated
> from ground up, have the unique capability to integrate interoperability
> right at the start.
>
> But has the alliance agreed on what level of interoperability this would
be?
>
> So far the interoperability solutions that have been presented were:
>
> CORBA
> CORBAmed
> HL7
> CEN
> GEHR
>
> Are all these players on the same field? meaning: can I proceed with my
EMR
> project, with my own database, with my own programming language, and with
> my own operating system, and _still_ be interoperable with the other open
> source projects?
>
> Which of the above can give me that flexibility?
>
> Shouldn't we settle this question right now or else go the way of the
> current proprietary systems?
>
> Maybe we're not looking for the best (maybe it isn't there). But we need
> something common to hold on.
>
>
> alvin
>
>
>
>
> --------------------------------------------------------------------------
--
> ----------
> Alvin B. Marcelo, M.D.
> National Library of Medicine, B1N30
> Office of High Performance Computing and Communications
> Bethesda, Maryland 20894
>
> Voice: 301-435-3278
> Fax: 301-402-4080
> eFax: 603-452-3657
>
> Work: [EMAIL PROTECTED] [EMAIL PROTECTED]
> Home: [EMAIL PROTECTED]
>
> PGP keyID: 0x6E9941D1
> PGP server: http://www.keyserver.net
>
>
