On Sat, 2005-10-08 at 20:46 -0400, Greg Kreis wrote: > What about VistALink? Could it be used to support SOAP? Maybe the > latest version or a planned one will? >
Not really. My understanding of what VistALink is, is just an implementation of the client end of the RPC broker in Java instead of Delphi. You still have to talk to the actual VistA server at some point, and the transition from VistA RPC Broker to SOAP has to occur somewhere. Also, writing a RPC Broker client really is not difficult, it is easy to do in any language in an hour or so. Creating a SOAP API out of the VistA rpcs on the other hand takes a while, you have to figure out what every RPC is returning and accepting and create complex types that encapsulate the data, and then pass that across. And that is just to give you an API that is 1<->1 with the VistA RPC API, most likely not something many would find useful (A real login session requires 6+ RPCs and that still leaves you with no patient or user information). As I have said on this list before, we (Medsphere) do have such a technology that sits on a server, takes SOAP calls and returns data back from RPC calls, wrapped up in semi-coherent data structures. We actually have server technology that allows both SOAP and an alternate form of communication, and the ability to seamlessly switch back and forth between the two. --Todd ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
