Kevin wrote:
>I mentioned this earlier, but I have completed what I think is a cool
>project.
>My function takes a search/sort template that contains a list of record
>numbers (as would be generated by a fileman search etc.) in the TIU DOCUMENT
>file (i.e. progress notes etc.). I then creates a website of all these
>files in a fashion such that they can be browsed from a web browser.
Very good. Once you have M2Web running, it should take very little additional
effort to
make it so that these reports can be generated live on demand. Only two things
would be
required for normal HTML content:
1) Make an entry point in a MUMPS routine that will get the
parameters it needs from the local arrays htInput and
htUser and either WRITE out its content to the current
device or SET the content into the variable htReturn.
2) Fill out a simple web form to define the top-level URL
path that will respond with a call to the entry point.
>Well, my immediate goal was to provide a method for a collegue leaving our
>practice to have access to just his notes. I just dumped them out and he
>can browse them and print them out etc.
>
>But a secondary goal is the idea that I could drop just a patient's notes to
>a disk and given them to them if they wanted to carry them to their new
>doctor in another state etc.
Do the notes contain all of the data that a patient or the colleague would want
to have in
a complete portable record?
If you want, we could perhaps connect this up to one or more of the M2Web/VistA
demonstration sites.
>The format is similar to the website I created at
>www.geocities.com/kdtop3-- namely it has a table-of-contents down the
>left side that lists all the
>notes, and when one is selected it is shown in the main window. Currently
>its all very plain with no graphics etc.
>
>I've wanted to do this for awhile. I''m happy that it has become much
>easier for me to create stuff with Fileman. I am finally getting
>comfortable with the API calls that I don't have to feel like I am wading
>through sand all the time when I have to use FDA's and IENS's etc.
Although I have a good understanding of the Fileman data structures and was
once familiar
with the internals of the applications, you may well be ahead of me in learning
to work
with the Fileman API's. We (VMTH) stopped using Fileman in most production
applications
long before the silent API's were developed because "Classic" Fileman would not
play
nicely with a non-roll-and-scroll user interface. (Actually, I modified it to
make it play
nicely for a number of years, but that's another story.)
---------------------------------------
Jim Self
Systems Architect, Lead Developer
VMTH Computer Services, UC Davis
(http://www.vmth.ucdavis.edu/us/jaself)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
