--- "A. Forrey" <[EMAIL PROTECTED]> wrote:
> With respect to the issue of interfaces for clinical lab > instrumentation > to VistA, my understanding is that the VA already has an interface > with > the middleware vendors (e.g. Data Innovations) so a key issue then is > how > to get interest in defining common ground among the clinical lab > instrument vendors who might be part of Physician Office Lab (POL) > configuarations for VistA. CLSI has worked with an already completed > standards effort for support of Point-of-Care Testing (POCT) and the > AACC > has a Division devoted to POCT issues (including POL) that could work > with > a WV Project team to get the uses of all of those stds (which will > include > HL7) proprerly documnetdd for both VistA Acquirers as well as > Suppliers of > VistA support. AACC's offices are located in DC so appropriate WV > contacts > can be identified to address this issue. If clarified by next July > then > the issue can be presented to the AACC Annual meeting by appropriate > forums that will get to labortaorians ans well as industry reps. If > folks > are interested, get me specific contacts in the WV Projects and I can > help > them get the right dialog going. > > Arden > I'm not sure that building an interface to a middleware product really changes things all that much. Middleware has advantages (such as reducing costs and improving scalability), but regardless of whether your build an interface between VistA and one of these products, or an interface between a middleware product and the same box, you still have to build the interface. Also, remember that there is going to need to be an interface between VistA and the middleware product, too. When using an RDBMS you can sometimes "cheat" a bit by using interface tables, but *even then* you need to carefully define the interface. === Gregory Woodhouse <[EMAIL PROTECTED]> "Einstein was a giant. He had his head in the clouds and his feet on the ground." -- Richard P. Feynman ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
