Kevin wrote: >Great. > >What I want to do is to create a function where my group could drop all >progress notes >to a huge XML file in the event that they want to move to another system, and >I am not >around.
What fields do you need? If you need all of them then a different solution may be required for now. There are 70 fields defined in TIU DOCUMENT, not counting any that would be brought in from subfields and pointers. Attempting to bring them all into an adhoc format causes an error from exceeding GT.M's 2KB limit on the size of an indirection argument. I understand you can get around that by recompiling GT.M with change of configuration but I haven't tried it and we haven't actually encountered this problem with any formats that anyone (besides myself testing) has attempted to use or construct. >This would need to be a function written from M, inside the system. I would >not want >them to have to use a web browser to get the data. What exactly *is* "inside the system"? The view2 query engine is written entirely in MUMPS. It was originally developed before there was a web, but development for non-web user interfaces has been discontinued in recent years for lack of interest. >How hard would this be? Trivially easy if you use a web browser. If not, the easiest thing would be to modify the m2web.cgi script and set the environment variables that would normally be supplied by CGI so you could call it from the command line. That could be useful for generating static web pages or xml as snapshots of pretty much any VistA data. >P.S. Could you post where I can get the code from, and where the API is >documented? Basic documentation on the view2 query engine can be found at http://vista.vmth.ucdavis.edu/notebook/index/26.html If you have downloaded m2web recently then you already have the source code. If not: http://vista.vmth.ucdavis.edu/notebook/index/48.html The entry point for application programmers is go^view2ht. We assume that local variables will be defined to reflect the CGI environment, for instance htUser is the number of the current logged in user and the user's authorization code is in htUser("Auth"). If you are attempting to use the viewer from a non-web context, look in ^htCGI1 to see what MUMPS variables would be defined or look in ^view2ht and ^view2htS to see which are actually used. > >Thanks >Kevin > > >Jim Self <[EMAIL PROTECTED]> wrote: >These capabilities are available to you in M2Web. You can pick pretty much any >VistA data >file and get the data out instantly in various formats and document types, >including HTML, >XML, and Javascript. If no format is specified, the default format includes >all fields you >are allowed to access from the zero-node of the data record. The default limit >of records >per page varies with the document type. The default document type is HTML, of >course. > >examples: >http://vista.vmth.ucdavis.edu/query?dbfile=OPTION&index=Name&find=XUS >http://vista.vmth.ucdavis.edu/query.xml?dbfile=OPTION&index=Name&find=XUS >http://vista.vmth.ucdavis.edu/query.js?dbfile=OPTION&index=Name&find=XUS >http://vista.vmth.ucdavis.edu/query.js?dbfile=OPTION&index=Name&find=XUS&layout=js2 >http://vista.vmth.ucdavis.edu/query.xls?dbfile=OPTION&index=Name&find=XUS > >similarly: >http://vista.vmth.ucdavis.edu/query?dbfile=REMOTE+PROCEDURE&index=Name&find=XUS > >To see this data rendered in the different document types, insert document >type extensions >before the "?" as in the previous examples. > >This one includes a custom format with subfields: >http://vista.vmth.ucdavis.edu/query?dbfile=8994&format=TEST2&index=Name&find=XUS >This is interesting for several reasons, one of which is that it contains >tables within >tables. Unfortunately, the rendering of sub-tables in this example does not >change with >the document type. > >This example is almost the same but the format of the subfields was left open. >It renders >syntactically correct XML (I have only tested it with Mozilla so far) but the >HTML doesn't >look as good. Oh well. > >Kevin Toppenberg wrote: >>An extension of this that I would like to implement >>someday in the near future would be to allow XML or >>HTML output. I haven't played with the tool to know >>if it can do this already. >> >>Kevin >> >> >>--- Gregory Woodhouse wrote: >> >>> This is a very powerful (and much underused) tool. >>> >>> ==== >>> Gregory Woodhouse >>> [EMAIL PROTECTED] >>> On Apr 15, 2005, at 8:31 AM, James Gray wrote: >>> >>> > You might be able to do it even faster using the >>> Fileman Export to >>> > Foreign format tool. >>> > >>> > Jim Gray >>> > >>> > ----- Original Message ----- From: "Kevin >>> Toppenberg" >>> > >>> > To: >>> > Sent: Friday, April 15, 2005 5:21 AM >>> > Subject: Re: [Hardhats-members] Hospital Cost >>> analysis >>> > >>> > >>> >> >>> >> --- Eriam Schaffter >>> wrote: >>> >>> The input to this software is flat text files >>> >>> containing datas extracted >>> >>> from the HIS. That's why I think getting data >>> out of >>> >>> the db with sql >>> >>> seems to be the solution. However if you think >>> >>> thoses data text file can >>> >>> be generated in another way why not. Since i've >>> not >>> >>> been working yet >>> >>> with openvista i don't know exactly what is >>> possible >>> >>> and what is not. >>> >> >>> >> You would just write a short M routine that would >>> >> access the data you want, open a text file, and >>> write >>> >> it out. >>> >> >>> >> Kevin --------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
