I didn't know you were looking for a Dicom viewer in Java. Have you looked at ImageJ from the NIH. http://rsb.info.nih.gov/ij/

also, see below
At 10:03 AM 10/20/2003 -0700, Andrew Ho wrote:
On Mon, 20 Oct 2003, Elpidio Latorilla wrote:
...
> Javascript for client sided validations and Java for the dicom viewer.

Elpido,
  I just tried the Java Dicom viewer and it is fantastic!
  Does it support drawing annotations? For example, circling an area of
interest? I did not see that function.
  We are looking for an image viewer with graphical annotation
capabilities (generating SVG output). Maybe we can extend your Dicom
viewer if you don't already have this function?
  For client-side input validation, I am not sure what you are using but
we have a Javascript routine that validates any number of inputs on a
form against a set of regular expression patterns. It may be of interest
to you.

...

> > Fantastic! Have you studied FreeMed (www.freemed.org)? It is also done
> > with PHP.
>
> Yes, I have studied it but admittedly not very deeply. They have invested
> considerable efforts and resources in developing it.  That is very good. We
> are also very interested in closer cooperation with them.

Do you have some documentation describing your data model? Approximately
how many tables does it contain?

Care2x data model and FreeMed data model should be quite different.
Harmonizing the data models between Care2x, GnuMed, TORCH, TkFp, etc is
going to take quite a bit of work.

How do you think collaboration will take place between FreeMed and Care2x?

We should adopt some standard nomenclature. The COAS specification enables
arbitrary templates of data to be managed, but we need to have some standard
templates (archetypes) that each system can map to and from. Then we can
begin to have interoperability between all the various systems. If we want
to have interoperability, people need to commit to it in their development process.
As long as we have a bunch of standalone systems, each with their own
dictionaries, we will continue to contribute to the big problem in healthcare, namely
the "Tower of Babel" which seems to continue on and on without abatement.


We don't need to know anything about the tables underlying any system. We
just need to know the various logical data models and how they can be mapped
to a "standard data structure" which may be the set of OpenEHR archetypes at some point
or the HL7 CDA model.


Dave


> > What works for username and password?
>
> Use demo/demo .

Thanks, that works!

> > How can the user add additional screens/forms?
>
> Currently, there is a generic form that can be used for user defined
> department or service.

Which module gives access to this generic form? I could not find it.

> Since we want the forms to be like WSYIWYG and should be a replica of
> the hospitals real paper forms, additional special forms should be
> programmed (at least for now) for each hospital or locality.

The OIO Project tries to deliver WYSIWYG forms that any user can custom
design. However, the OIO system cannot replicate your very nice Lab test
request form yet:

http://care2x.com/foundry/modules/nursing/nursing-station-patientdaten-doconsil-chemlabor.php?sid=473c416e1c327bdca74eb1fc61773fd3&lang=en&noresize=1&user_origin=lab&target=chemlabor&checkintern=

What we can do now look more like this:
 (in pink_interface)
 http://www.txoutcome.org/screenshots/preview_recruiting_form.png
 or
 (in classic interface)
 http://www.txoutcome.org/screenshots/preview_recruiting_form_classic.png

...
> > What is this "single data format"? Could you kindly point to a description
> > of what this entails?
>
> This is actually the data model, that is, the care2x data model. It
> means that if all modules, submodules or supporting functionalities use
> the same data model, data redundacy can be avoided. Taken into a wider
> perspective, if hospitals, private practices, auxially health services
> use the same data modell, you can build a single data depot to avoid
> redundancy and facilitate data sharing without the need of cumbersome
> translators, converters, or mappers.


This sounds the same as FreeMed, GnuMed etc saying we should all agree to
use their data model. Why should we favor Care2x's data model?

...
> If you like, you can download the care2x_en.ppt presentation from here:
> http://prdownloads.sourceforge.net/care2002/care2x_en.ppt

Thanks, it is a beautiful presentation! Very impressive achievements. It
appears just as comprehensive as some of the closed-source systems that I
have seen.

> The Care2x is still in the early development stages. We are always ready to
> "throw code away" if a better one comes up.

Once I learn the details of the data model, I like to explore the
possibility of integrating OIO with Care2x. I will first try to install
it.

Best regards,

Andrew
---
Andrew P. Ho, M.D.
OIO: Open Infrastructure for Outcomes
www.TxOutcome.Org



Reply via email to