There is a philosophical difference between XML and HTML - the first is
to represent / store information with no thought to how it is displayed.
HTML involves content and display, but the emphasis is on
presentation. Constructs involved in presentation change more rapidly
than the constructs involved in the former.
So what makes sense is to dump the data from VistA in XML, and then to
post process to HTML for presentation/viewing. But that data in XML
could be imported into another EHR system, which would be much harder to
do with an HTML file.
-- Bhaskar
Kevin Toppenberg wrote:
That's a good idea, but off track from what I want.
When I dump the file to html, I want it to be able to
go to a disk that a patient could take with them
somewhere. Then someone could view the record from
the disk with a web browser.
Kevin
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
