Home » Archived » OHF » Contributors?
| Contributors? [message #2600] |
Sun, 10 July 2005 01:40  |
Eclipse User |
|
|
|
Originally posted by: jkuhnert.ekosystems.com
Having only scanned through the proposal documents that you guys have
generated I'm still a little unsure about what exactly it is that is
being built. It sounds like you want to build the whole system (which
would be very interesting, if not somewhat daunting..).
I'm interested in contributing something to the framework, it's just
hard to know how/where to do further research to see if there's anything
viable that I could provide.(ie where's the goods, or source if you will?)
I'm just a lowly engineer at an EMRS company that thought this
particular eclipse project looked pretty interesting. I have absolutely
no idea how I'll be able to justify contributing to it with my employer,
but over the past 5 years or so I think I've developed a fairly rich
framework that covers a very large spectrum of everything outlined in
your document. (We don't do everything..heh.., just the peri-operative
part.)
I guess that is the only stickler, as your document outlines, this is a
VERY competitive market, so how do I broach this with my employer? Maybe
~some~ things would be ok to work on and others not so much...
I wasn't sure if I saw it in the outline, but I was wondering if anyone
had discussed data dictionary / database persistence at all in the
discussions? I think out of all the things I've worked on and seen in
the industry, providing a better way to define these sort of "medical
terms" and how to access them in a standard SQL (or POJO) sort of way
would be nice...Much like projects based on http://protege.stanford.edu/
work. We have constructed our own data dictionary, complete with an
architecture to work with it, and I almost wanted to cry when I found
the above mentioned link at the end of the last product re-write phase
we went through..
Anyways, all of the things you guys outlined would be super cool and
all, but I think even cooler would be an additional component along the
lines of this data dictionary idea, as I think it's something EMRS
vendors would actually buy into and use, and might actually be able to
integrate into their existing products if it were designed well..We've
based our entire product architecture around this notion and it has
proven to be immeasurably helpful. Reports can be written and run in any
hospital now, billing rules are all universal(not universally used, but
the core logic can count on the same sort of data all the time..of
course drools helps us a lot too, even if it is a nasty codehaus.org
puke pile), etc etc..etc..Maybe my only contribution could be outputting
our dictionary in XML form for you, or sql, or whatever..
I hope extremely large rants that aren't well thought out before writing
each paragraph are ok here, just wanted to blurt out my initial feelings
and see if there is any code hiding away somewhere to go along with
this project.
PPS: Even better would be defining a universal "database" after having
defined the data dictionary. Then all the EMRS vendors could build their
product (as crappily or wonderfully as they want..ehh....) and the end
users won't be subjected to all manner of confusing technology choices
when it comes to at a very minnimum reviewing and analyzing data...And
of course this would very easily lead to the ultimate holy grial of
hospitals actually being able to share data ...But, much like the famous
movie quote(at least in my head) "there was once a dream that was rome,
one had only to mention it and it would all dissappear". Or something
like that. You know what I mean..
jesse
|
|
|
| Re: Contributors? [message #2659 is a reply to message #2600] |
Tue, 12 July 2005 22:36  |
| Eclipse User |
|
|
|
Originally posted by: brian.bedarra.com
Thanks for the post. Let me begin by saying that the proposal is
deliberately fluid to allow room for others to play, which is a polite way
of saying that we haven't really worked out all the details<grin>. The bad
news is it's hard to answer detailed questions like yours; the good news
that you can help construct the answer.
So let me try for at least a few answers.
>>It sounds like you want to build the whole system
Yep that's it..it is clearly a very ambitious undertaking. But our feeling
is that only by providing a common ubiquitous platform that everyone can use
to build on can we really crack the interoperability problems. No doubt
this is a large multi-year project, and it might not work out -- but then
most things worth doing (including the Eclipse Platform) start that way.
>>where's the goods, or source if you will
You're ahead of us I'm afraid, right now we're at the proposal stage,
assuming we clear that then we will over time begin to populate the site
with plan info and then early code drops. But realistically we're a few
months away from that. On the other hand if you have code you're willing to
contribute this would be a *really* good time to put it on the table as a
possibility.
>>I've developed a fairly rich framework that covers a very large spectrum
Is there any overview doc you can make available? That would help to make
the discussion more tangible. In terms of convincing your employer, everyone
has to make their own call on that. In my experience most companies get
involved because they see the open source train coming and decide it's
better to be on the train than on the tracks<grin>.
>>discussed data dictionary / database persistence at all in the discussions
Sure it shows up in several places; if you look at the architecture
diagram/description, record storage, terminology service, and archetypes all
are aspects of the persistence discussion. I'll see if I can prompt some of
the folks who have expertise in that area to post on this thread.
"Jesse Kuhnert" <jkuhnert@ekosystems.com> wrote in message
news:dapu8o$a2u$1@news.eclipse.org...
> Having only scanned through the proposal documents that you guys have
> generated I'm still a little unsure about what exactly it is that is
> being built. It sounds like you want to build the whole system (which
> would be very interesting, if not somewhat daunting..).
>
> I'm interested in contributing something to the framework, it's just
> hard to know how/where to do further research to see if there's anything
> viable that I could provide.(ie where's the goods, or source if you will?)
>
> I'm just a lowly engineer at an EMRS company that thought this
> particular eclipse project looked pretty interesting. I have absolutely
> no idea how I'll be able to justify contributing to it with my employer,
> but over the past 5 years or so I think I've developed a fairly rich
> framework that covers a very large spectrum of everything outlined in
> your document. (We don't do everything..heh.., just the peri-operative
> part.)
>
> I guess that is the only stickler, as your document outlines, this is a
> VERY competitive market, so how do I broach this with my employer? Maybe
> ~some~ things would be ok to work on and others not so much...
>
> I wasn't sure if I saw it in the outline, but I was wondering if anyone
> had discussed data dictionary / database persistence at all in the
> discussions? I think out of all the things I've worked on and seen in
> the industry, providing a better way to define these sort of "medical
> terms" and how to access them in a standard SQL (or POJO) sort of way
> would be nice...Much like projects based on http://protege.stanford.edu/
> work. We have constructed our own data dictionary, complete with an
> architecture to work with it, and I almost wanted to cry when I found
> the above mentioned link at the end of the last product re-write phase
> we went through..
>
> Anyways, all of the things you guys outlined would be super cool and
> all, but I think even cooler would be an additional component along the
> lines of this data dictionary idea, as I think it's something EMRS
> vendors would actually buy into and use, and might actually be able to
> integrate into their existing products if it were designed well..We've
> based our entire product architecture around this notion and it has
> proven to be immeasurably helpful. Reports can be written and run in any
> hospital now, billing rules are all universal(not universally used, but
> the core logic can count on the same sort of data all the time..of
> course drools helps us a lot too, even if it is a nasty codehaus.org
> puke pile), etc etc..etc..Maybe my only contribution could be outputting
> our dictionary in XML form for you, or sql, or whatever..
>
> I hope extremely large rants that aren't well thought out before writing
> each paragraph are ok here, just wanted to blurt out my initial feelings
> and see if there is any code hiding away somewhere to go along with
> this project.
>
> PPS: Even better would be defining a universal "database" after having
> defined the data dictionary. Then all the EMRS vendors could build their
> product (as crappily or wonderfully as they want..ehh....) and the end
> users won't be subjected to all manner of confusing technology choices
> when it comes to at a very minnimum reviewing and analyzing data...And
> of course this would very easily lead to the ultimate holy grial of
> hospitals actually being able to share data ...But, much like the famous
> movie quote(at least in my head) "there was once a dream that was rome,
> one had only to mention it and it would all dissappear". Or something
> like that. You know what I mean..
>
> jesse
|
|
|
| Re: Contributors? [message #2689 is a reply to message #2659] |
Wed, 13 July 2005 04:18 |
| Eclipse User |
|
|
|
Originally posted by: jkuhnert.ekosystems.com
:) That's going to be a hard sell, especially to our investors...Heh.
We'll see.
Aghh...I wrote a few paragraphs of text before deleting after feeling
guilty about divulging company assets or generally sounding like an
arrogant ass...I'll bring it up with one of my managers and see what the
reaction is...I'm sure it will be a big "pfffffffffffftttttt" but we'll
see. :( Damn ...The only open source project that I can actually commit
a reasonable amount of time to as it pertains directly to work and for
some reason I think it's going to be a conflict of interest...I don't
know how everyone else does it. Maybe their employers just have bigger
pocketbooks. :)
(I guess I could say one thing, since it's talked about on our website,
and that is the importance of getting the actual EMR gui/interactivity
between clinician and system down right...We've found the wysiwyg
presentation has done exceptionally well, and as far as I know has
probably been the largest reason why we've never lost a sale in a
vendor-off for any reason having to do with the actual product, again at
least from what I know of, I'm sure they don't tell us all the
humiliating sales where we look like monkeys typing code in a lab, but
it sounds good. )
jesse
> Is there any overview doc you can make available? That would help to make
> the discussion more tangible. In terms of convincing your employer, everyone
> has to make their own call on that. In my experience most companies get
> involved because they see the open source train coming and decide it's
> better to be on the train than on the tracks<grin>.
>
>
|
|
|
| Re: Contributors? [message #2711 is a reply to message #2600] |
Sun, 17 July 2005 19:54 |
| Eclipse User |
|
|
|
Originally posted by: cma.wimpzilla.com
Jesse Kuhnert wrote:
> Having only scanned through the proposal documents that you guys have
> generated I'm still a little unsure about what exactly it is that is
> being built. It sounds like you want to build the whole system (which
> would be very interesting, if not somewhat daunting..).
>
> I'm interested in contributing something to the framework, it's just
> hard to know how/where to do further research to see if there's anything
> viable that I could provide.(ie where's the goods, or source if you will?)
>
> I'm just a lowly engineer at an EMRS company that thought this
> particular eclipse project looked pretty interesting. I have absolutely
> no idea how I'll be able to justify contributing to it with my employer,
> but over the past 5 years or so I think I've developed a fairly rich
> framework that covers a very large spectrum of everything outlined in
> your document. (We don't do everything..heh.., just the peri-operative
> part.)
>
> I guess that is the only stickler, as your document outlines, this is a
> VERY competitive market, so how do I broach this with my employer? Maybe
> ~some~ things would be ok to work on and others not so much...
>
> I wasn't sure if I saw it in the outline, but I was wondering if anyone
> had discussed data dictionary / database persistence at all in the
> discussions? I think out of all the things I've worked on and seen in
> the industry, providing a better way to define these sort of "medical
> terms" and how to access them in a standard SQL (or POJO) sort of way
> would be nice...Much like projects based on http://protege.stanford.edu/
> work. We have constructed our own data dictionary, complete with an
> architecture to work with it, and I almost wanted to cry when I found
> the above mentioned link at the end of the last product re-write phase
> we went through..
>
> Anyways, all of the things you guys outlined would be super cool and
> all, but I think even cooler would be an additional component along the
> lines of this data dictionary idea, as I think it's something EMRS
> vendors would actually buy into and use, and might actually be able to
> integrate into their existing products if it were designed well..We've
> based our entire product architecture around this notion and it has
> proven to be immeasurably helpful. Reports can be written and run in any
> hospital now, billing rules are all universal(not universally used, but
> the core logic can count on the same sort of data all the time..of
> course drools helps us a lot too, even if it is a nasty codehaus.org
> puke pile), etc etc..etc..Maybe my only contribution could be outputting
> our dictionary in XML form for you, or sql, or whatever..
>
> I hope extremely large rants that aren't well thought out before writing
> each paragraph are ok here, just wanted to blurt out my initial feelings
> and see if there is any code hiding away somewhere to go along with
> this project.
>
> PPS: Even better would be defining a universal "database" after having
> defined the data dictionary. Then all the EMRS vendors could build their
> product (as crappily or wonderfully as they want..ehh....) and the end
> users won't be subjected to all manner of confusing technology choices
> when it comes to at a very minnimum reviewing and analyzing data...And
> of course this would very easily lead to the ultimate holy grial of
> hospitals actually being able to share data ...But, much like the famous
> movie quote(at least in my head) "there was once a dream that was rome,
> one had only to mention it and it would all dissappear". Or something
> like that. You know what I mean..
>
> jesse
Jesse,
There is quite an opportunity for working with medical terminology.
There are multiple generations and sets of semantic structures for some
domains. For example, the whole of terminology for generic and brand
name drugs used by pharmacies. There are also sets of semantics for
medical procedures.
Work is going on in HL7 which you might want to look at. hl7.org and
SNOMED are now working together on the standards for some of this.
http://hl7.org/documentcenter/public/pressreleases/20050623. pdf
There are great opportunities for innovation here. Some of the problems
are legion. For example, translating records between different
generations of semantics structures, and being able to manage healthcare
records for a typical human lifetime (100 years of medical records and
all the changes and refinements).
What is the EMRS industry? Electronic Medical Records Systems? You must
be dealing with this stuff already, right?
I can help you prepare for business case approaches that might make
sense to your company. Let me know,
Marc Erickson
|
|
|
| Re: Contributors? [message #4930 is a reply to message #2711] |
Wed, 21 September 2005 23:04 |
| Eclipse User |
|
|
|
Originally posted by: info.catmedia.us
Hi,
I found the OHF project just recently.
I would like to help and contribute both information (use cases, business
processes, etc.)
as well as artifacts and components whenever those make sense (late 2007
seems a bit late for some
actual code, but maybe more join in ?;-)
I am founder and project lead of a medical information system based on Open
Source technologies
called MedSurvey. The project and my own medical expertise goes back into
the early 1990s. Some
of our contributors and medical experts we worked together with on the
project even started earlier
(in times or Atari or Commodore !!;-)
As most of the projects so far where Windows-based, I have started to port
some components to Java
systems such as NetBeans (which had an open API and framework a bit earlier
than Eclipse) and made
a move towards Eclipse after that gained more ground (from 2002 on)
Project Paracelsus was founded to be a MIS (for GP and Small to Medium
Clinics) based on Eclipse
even before the RCP and Rich GUI wave hit the industry again.
Collecting standards and building a network however is quite tricky
(especially in countries like Germany
or Austria with lots of propriatory shit sold to doctors as if it was Oil or
Gold ;-/)
I have heard from some good examples from Scandinavia so far. So no wonder,
the only mentioned interest
from Europe comes from Finland. Mine is from Central Europe being based in
Switzerland right now (but with
roots and users mostly in Austria)
One important part which I would like to add as useful building block is the
use of Smartcards (GINA/ NETC@RDS)
though it could be seen as part of one of the Core parts (Identity,
Security/PKI, or Interoperability if viewed as a separate
system)
While being in Austria I took part in the working group for Business Process
Management for the Healthcare System (Nation-
and EU-wide) formed by the The Austrian Federal Economic Chamber.
As some of my current projects are more related to the finance sector, I am
not working in the Healthcare industry full time.
However, often my main project work was related to e-government which is at
least in some countries covered by the same
technologies (e.g. the e-card for social security is also a citizen ID for
e-Government at least in Austria and some other countries)
I would be happy to help within my capacity and being able to add some more
European knowledge into the so far mostly American
Healthcare sector dominated project (Eclipse itself is built on knowledge
and work especially from Canada, the USA and Switzerland,
mostly thanks to OTI ;-)
I was invited to speak in Bern about my work on Paracelsus and MedSurvey
regarding Eclipse and RCP so far. I guess, OHF aspects
are in a stage too early to be included, but if any of you has something
important to add (and present), you are very welcome to spread
the word and information to Europe.
Kind Regards,
Werner Keil
MedSurvey Foundation
medsurvey@hotmail.com
http://medsurvey.sf.net
supported by
Creative Arts & Technologies
http://www.catmedia.us
|
|
|
| Re: Contributors? [message #563333 is a reply to message #2600] |
Tue, 12 July 2005 22:36 |
| Eclipse User |
|
|
|
Originally posted by: brian.bedarra.com
Thanks for the post. Let me begin by saying that the proposal is
deliberately fluid to allow room for others to play, which is a polite way
of saying that we haven't really worked out all the details<grin>. The bad
news is it's hard to answer detailed questions like yours; the good news
that you can help construct the answer.
So let me try for at least a few answers.
>>It sounds like you want to build the whole system
Yep that's it..it is clearly a very ambitious undertaking. But our feeling
is that only by providing a common ubiquitous platform that everyone can use
to build on can we really crack the interoperability problems. No doubt
this is a large multi-year project, and it might not work out -- but then
most things worth doing (including the Eclipse Platform) start that way.
>>where's the goods, or source if you will
You're ahead of us I'm afraid, right now we're at the proposal stage,
assuming we clear that then we will over time begin to populate the site
with plan info and then early code drops. But realistically we're a few
months away from that. On the other hand if you have code you're willing to
contribute this would be a *really* good time to put it on the table as a
possibility.
>>I've developed a fairly rich framework that covers a very large spectrum
Is there any overview doc you can make available? That would help to make
the discussion more tangible. In terms of convincing your employer, everyone
has to make their own call on that. In my experience most companies get
involved because they see the open source train coming and decide it's
better to be on the train than on the tracks<grin>.
>>discussed data dictionary / database persistence at all in the discussions
Sure it shows up in several places; if you look at the architecture
diagram/description, record storage, terminology service, and archetypes all
are aspects of the persistence discussion. I'll see if I can prompt some of
the folks who have expertise in that area to post on this thread.
"Jesse Kuhnert" <jkuhnert@ekosystems.com> wrote in message
news:dapu8o$a2u$1@news.eclipse.org...
> Having only scanned through the proposal documents that you guys have
> generated I'm still a little unsure about what exactly it is that is
> being built. It sounds like you want to build the whole system (which
> would be very interesting, if not somewhat daunting..).
>
> I'm interested in contributing something to the framework, it's just
> hard to know how/where to do further research to see if there's anything
> viable that I could provide.(ie where's the goods, or source if you will?)
>
> I'm just a lowly engineer at an EMRS company that thought this
> particular eclipse project looked pretty interesting. I have absolutely
> no idea how I'll be able to justify contributing to it with my employer,
> but over the past 5 years or so I think I've developed a fairly rich
> framework that covers a very large spectrum of everything outlined in
> your document. (We don't do everything..heh.., just the peri-operative
> part.)
>
> I guess that is the only stickler, as your document outlines, this is a
> VERY competitive market, so how do I broach this with my employer? Maybe
> ~some~ things would be ok to work on and others not so much...
>
> I wasn't sure if I saw it in the outline, but I was wondering if anyone
> had discussed data dictionary / database persistence at all in the
> discussions? I think out of all the things I've worked on and seen in
> the industry, providing a better way to define these sort of "medical
> terms" and how to access them in a standard SQL (or POJO) sort of way
> would be nice...Much like projects based on http://protege.stanford.edu/
> work. We have constructed our own data dictionary, complete with an
> architecture to work with it, and I almost wanted to cry when I found
> the above mentioned link at the end of the last product re-write phase
> we went through..
>
> Anyways, all of the things you guys outlined would be super cool and
> all, but I think even cooler would be an additional component along the
> lines of this data dictionary idea, as I think it's something EMRS
> vendors would actually buy into and use, and might actually be able to
> integrate into their existing products if it were designed well..We've
> based our entire product architecture around this notion and it has
> proven to be immeasurably helpful. Reports can be written and run in any
> hospital now, billing rules are all universal(not universally used, but
> the core logic can count on the same sort of data all the time..of
> course drools helps us a lot too, even if it is a nasty codehaus.org
> puke pile), etc etc..etc..Maybe my only contribution could be outputting
> our dictionary in XML form for you, or sql, or whatever..
>
> I hope extremely large rants that aren't well thought out before writing
> each paragraph are ok here, just wanted to blurt out my initial feelings
> and see if there is any code hiding away somewhere to go along with
> this project.
>
> PPS: Even better would be defining a universal "database" after having
> defined the data dictionary. Then all the EMRS vendors could build their
> product (as crappily or wonderfully as they want..ehh....) and the end
> users won't be subjected to all manner of confusing technology choices
> when it comes to at a very minnimum reviewing and analyzing data...And
> of course this would very easily lead to the ultimate holy grial of
> hospitals actually being able to share data ...But, much like the famous
> movie quote(at least in my head) "there was once a dream that was rome,
> one had only to mention it and it would all dissappear". Or something
> like that. You know what I mean..
>
> jesse
|
|
| |
| Re: Contributors? [message #563378 is a reply to message #2600] |
Sun, 17 July 2005 19:54 |
| Eclipse User |
|
|
|
Originally posted by: cma.wimpzilla.com
Jesse Kuhnert wrote:
> Having only scanned through the proposal documents that you guys have
> generated I'm still a little unsure about what exactly it is that is
> being built. It sounds like you want to build the whole system (which
> would be very interesting, if not somewhat daunting..).
>
> I'm interested in contributing something to the framework, it's just
> hard to know how/where to do further research to see if there's anything
> viable that I could provide.(ie where's the goods, or source if you will?)
>
> I'm just a lowly engineer at an EMRS company that thought this
> particular eclipse project looked pretty interesting. I have absolutely
> no idea how I'll be able to justify contributing to it with my employer,
> but over the past 5 years or so I think I've developed a fairly rich
> framework that covers a very large spectrum of everything outlined in
> your document. (We don't do everything..heh.., just the peri-operative
> part.)
>
> I guess that is the only stickler, as your document outlines, this is a
> VERY competitive market, so how do I broach this with my employer? Maybe
> ~some~ things would be ok to work on and others not so much...
>
> I wasn't sure if I saw it in the outline, but I was wondering if anyone
> had discussed data dictionary / database persistence at all in the
> discussions? I think out of all the things I've worked on and seen in
> the industry, providing a better way to define these sort of "medical
> terms" and how to access them in a standard SQL (or POJO) sort of way
> would be nice...Much like projects based on http://protege.stanford.edu/
> work. We have constructed our own data dictionary, complete with an
> architecture to work with it, and I almost wanted to cry when I found
> the above mentioned link at the end of the last product re-write phase
> we went through..
>
> Anyways, all of the things you guys outlined would be super cool and
> all, but I think even cooler would be an additional component along the
> lines of this data dictionary idea, as I think it's something EMRS
> vendors would actually buy into and use, and might actually be able to
> integrate into their existing products if it were designed well..We've
> based our entire product architecture around this notion and it has
> proven to be immeasurably helpful. Reports can be written and run in any
> hospital now, billing rules are all universal(not universally used, but
> the core logic can count on the same sort of data all the time..of
> course drools helps us a lot too, even if it is a nasty codehaus.org
> puke pile), etc etc..etc..Maybe my only contribution could be outputting
> our dictionary in XML form for you, or sql, or whatever..
>
> I hope extremely large rants that aren't well thought out before writing
> each paragraph are ok here, just wanted to blurt out my initial feelings
> and see if there is any code hiding away somewhere to go along with
> this project.
>
> PPS: Even better would be defining a universal "database" after having
> defined the data dictionary. Then all the EMRS vendors could build their
> product (as crappily or wonderfully as they want..ehh....) and the end
> users won't be subjected to all manner of confusing technology choices
> when it comes to at a very minnimum reviewing and analyzing data...And
> of course this would very easily lead to the ultimate holy grial of
> hospitals actually being able to share data ...But, much like the famous
> movie quote(at least in my head) "there was once a dream that was rome,
> one had only to mention it and it would all dissappear". Or something
> like that. You know what I mean..
>
> jesse
Jesse,
There is quite an opportunity for working with medical terminology.
There are multiple generations and sets of semantic structures for some
domains. For example, the whole of terminology for generic and brand
name drugs used by pharmacies. There are also sets of semantics for
medical procedures.
Work is going on in HL7 which you might want to look at. hl7.org and
SNOMED are now working together on the standards for some of this.
http://hl7.org/documentcenter/public/pressreleases/20050623. pdf
There are great opportunities for innovation here. Some of the problems
are legion. For example, translating records between different
generations of semantics structures, and being able to manage healthcare
records for a typical human lifetime (100 years of medical records and
all the changes and refinements).
What is the EMRS industry? Electronic Medical Records Systems? You must
be dealing with this stuff already, right?
I can help you prepare for business case approaches that might make
sense to your company. Let me know,
Marc Erickson
|
|
|
| Re: Contributors? [message #563708 is a reply to message #2711] |
Wed, 21 September 2005 23:04 |
 Werner Keil
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Hi,
I found the OHF project just recently.
I would like to help and contribute both information (use cases, business
processes, etc.)
as well as artifacts and components whenever those make sense (late 2007
seems a bit late for some
actual code, but maybe more join in ?;-)
I am founder and project lead of a medical information system based on Open
Source technologies
called MedSurvey. The project and my own medical expertise goes back into
the early 1990s. Some
of our contributors and medical experts we worked together with on the
project even started earlier
(in times or Atari or Commodore !!;-)
As most of the projects so far where Windows-based, I have started to port
some components to Java
systems such as NetBeans (which had an open API and framework a bit earlier
than Eclipse) and made
a move towards Eclipse after that gained more ground (from 2002 on)
Project Paracelsus was founded to be a MIS (for GP and Small to Medium
Clinics) based on Eclipse
even before the RCP and Rich GUI wave hit the industry again.
Collecting standards and building a network however is quite tricky
(especially in countries like Germany
or Austria with lots of propriatory shit sold to doctors as if it was Oil or
Gold ;-/)
I have heard from some good examples from Scandinavia so far. So no wonder,
the only mentioned interest
from Europe comes from Finland. Mine is from Central Europe being based in
Switzerland right now (but with
roots and users mostly in Austria)
One important part which I would like to add as useful building block is the
use of Smartcards (GINA/ NETC@RDS)
though it could be seen as part of one of the Core parts (Identity,
Security/PKI, or Interoperability if viewed as a separate
system)
While being in Austria I took part in the working group for Business Process
Management for the Healthcare System (Nation-
and EU-wide) formed by the The Austrian Federal Economic Chamber.
As some of my current projects are more related to the finance sector, I am
not working in the Healthcare industry full time.
However, often my main project work was related to e-government which is at
least in some countries covered by the same
technologies (e.g. the e-card for social security is also a citizen ID for
e-Government at least in Austria and some other countries)
I would be happy to help within my capacity and being able to add some more
European knowledge into the so far mostly American
Healthcare sector dominated project (Eclipse itself is built on knowledge
and work especially from Canada, the USA and Switzerland,
mostly thanks to OTI ;-)
I was invited to speak in Bern about my work on Paracelsus and MedSurvey
regarding Eclipse and RCP so far. I guess, OHF aspects
are in a stage too early to be included, but if any of you has something
important to add (and present), you are very welcome to spread
the word and information to Europe.
Kind Regards,
Werner Keil
MedSurvey Foundation
medsurvey@hotmail.com
http://medsurvey.sf.net
supported by
Creative Arts & Technologies
http://www.catmedia.us
|
|
|
Goto Forum:
Current Time: Fri Dec 27 02:30:43 GMT 2024
Powered by FUDForum. Page generated in 0.03528 seconds |
] 
Search
Help
Register
Login
Home
