Gentlemen:
I feel it necessary to correct Alvin's research here.
"So far, these are the only open source projects I see that have these
combinations (feel free to correct me):"
The are additional projects that have had:
1. formal adoption of an extensible information model
2. existing code
3. actual implementation (in a real life setting)
I believe we need to ask Alvin re-research this so you do not rely on this
information
Franklin M. Valier
Freemed Project Coordinator
Freemed Making It Happen!
[EMAIL PROTECTED]
-----Original Message-----
From: Alvin B. Marcelo [SMTP:[EMAIL PROTECTED]]
Sent: Friday, November 26, 1999 10:37 AM
To: [EMAIL PROTECTED]
Subject: So far (week three)..a proposal
Wayne gave a very concise sum up of the tech-speak for the past week.
I will attempt to do the same thing -- organization-wise.
We have heard from the most of the developers of the models: GEHR, HL7,
VistA, CORBAmed (not from CEN).
It seems that instead of getting them to agree on their commonalities, they
preferred to signify their positively unique qualities (and sometimes their
shortcomings).
One, the bottomline is: the models will not merge. We can spend our whole
lives talking about which is better than which but only a viable
implementation can prove that.
Two, for an open source EMR to flourish, it needs three things:
1. formal adoption of an extensible information model
2. existing code
3. actual implementation (in a real life setting)
So far, these are the only open source projects I see that have these
combinations (feel free to correct me):
a. LittleFish (GEHR, Australia)
b. Circare (Corbamed, Canada)
c. Telemed (Corbamed, Los Alamos)
d. VistA (VistA, VA)
Now, the OSHA (or whatever it will be called) will have two primary jobs:
1. coordinate development of projects (to monitor forking)
2. recruit OpenEMR enthusiasts as they arise (to minimize de novo forking
by referring new enthusiasts to an existing project/model that may fit
their needs)
With the above points, from now on, there may be four big groups in the list:
1. individuals who will join any of the three above and implement
(LittleFish, Circare, Telemed)
2. ongoing projects that will adopt a model and implement (maybe FreeMed
and FreePM)
3. new developers who will start their own projects (but will adopt one of
the models above -- eg, HL7 with Gunther) *and* implement
4. projects that will go on without adopting a model and implement
It is in the interest of the alliance to "discourage" further forking than
what there is right now, ie, if we "pick up" a new enthusiast, they should
be guided to any of the above models/projects and be encouraged to adopt
one of them.
In return, the models must commit to interoperability as much as possible.
Of course, there is always CORBA as a last resort.
The modelling topic has reached its limit (does anyone agree?). It's time
to shift to implementations and start testing the models to see which one
can stand the test of reality. Let us set AMIA November 2000 as the
presentation of the implementations (lessons learned session c/o Rob Hausam).
Please send me your comments.
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
