[FOSS_health] Re: interoperability

[Tom Jones]

It's the "looked like" that is the problem. There was not, to my knowledge,
true integration of information such that an allergy to a medication
registered in the CHCS DoD system triggered an alert if the medication was
ordered on the same patient in the VistA VA version. And one can go on from
there. The read only visual display was not matched by data re-use across
systems

Tom

-----Original Message-----
From: foss_health-bounces at oshca.org [mailto:foss_health-bounces at oshca.org]
On Behalf Of K.S. Bhaskar
Sent: Tuesday, May 29, 2007 3:50 PM
To: foss_health at oshca.org
Subject: Re: [FOSS_health] Re: interoperability

David --

There was a successful proof of concept showing data from both CHCS (DoD 
version) and VistA (VA version) integrated in the same browser screen 
using Esi Objects to wrap both flavors of the same application so that 
they looked like an integrated system.  I actually saw a demonstration 
of this a few years ago.

However, even though the technical feasibility was demonstrated, I 
understand that the rollout was not funded because it was not the 
officially blessed way to integrate information.

Others may have better insight into it, but perhaps too much management 
can ruin any worthwhile project, as the saying goes...  [Yes, I confess 
to being a manager!]

Regards
-- Bhaskar

David Forslund wrote, On 05/29/2007 06:19 PM:
> I agree. The original GCPR project between the VA, DOD and IHS actually
> involved the identical software at all the sites, but configured
> differently at each site and were totally non-interoperable as a result,
> even though much of it was open source (VistA).  The HDTF solution
> chosen dealt specifically to deal with this problem and it helped in the
> solution.  HL7 had been used but HL7, itself, doesn't mean systems are
> interoperable.    Low level database replication is likely to be a poor
> interoperability platform in my experience.  If one has total control of
> all the sites, one might get away with it.  Otherwise, forget it. 
> Mapping XML structures between sites should work well in this situation,
> once one knows how to do the appropriate transforms.

_______________________________________________
FOSS_health mailing list
FOSS_health at oshca.org
http://mailman.oshca.org/mailman/listinfo.cgi/foss_health