On 1/13/06, Jim Self <[EMAIL PROTECTED]> wrote:
...

 

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.

One of these days, I am going to sit down and work on getting Apache up and running etc and setting up M2Web.  I haven't had a need before.  But you are right, this job would have been easier using your functionality.
 

...
 

Do the notes contain all of the data that a patient or the colleague would want to have in
a complete portable record?


Right now, we don't have an interface to labs, and we don't have prescription writing.  So that really only leaves plain progress notes as the data stored in VistA in our site.  So a note is all I worried about.  I guess it wouldn't be too hard to add more data if needed, though.  I guess we are working with images, so maybe I should add a link for those.  Although in the case of the specific doctor I was exporting for, he had no images. 
 

If you want, we could perhaps connect this up to one or more of the M2Web/VistA
demonstration sites.


The whole web-interface chart is very alluring.  It would be fun to work on, from my perspective.  But I think that I really shouldn't.  I wouldn't add any functionality to our site (CPRS is doing fine), and I really need to get medications and e-prescribing working first.  So I guess I will put that on the back burner for now.  But sometimes things come up, and priorities change.... I can always hope. :-)

Kevin


>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

Reply via email to