Hello Bill, I can't really speak for the OpenEHR experts but I assume that much of the OpenEHR work predates the availability of Sanchez GT.M to provide an open-source M complier to run VistA on. I remember some of the Thomas Beale's papers being posted on the Open-health list before the Sanchez announcement.
If you are interested in the just the database API, then I assume that you have researched the Diamond package provided by the Hardhats. http://www.hardhats.org/projects/installs/gems.html This allows you to built pretty much what you would like and have nice infrastructure tools available. Todd Smith <todd.smith at camc.org> -----Original Message----- From: Bill Walton [mailto:[email protected]] >I apologize for not stating my question more directly. Basically, it's >this. Given that VistA exists as an open source system with an architecture >that includes a logically seperate storage subsystem with a database API >that looks, at first glance, like it could be pretty easily implemented as >an independent service, what drives this group to develop the openEHR server >rather than simply seperate and potentially extend Fileman? - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
