I have been trying to get the new CVS version up and active and I ran into something that didn’t happen under the old version. Under 2.8.1 say you put your vital signs in and noticed that opps, you transposed some of the numbers, you could go back in and edit it and re save it without loosing any of the old data. Now if you click on it you are presented with a blank screen and you either have to re enter everything or just leave it as is. Any comments?
OK now I find that I misspoke about the problem. It seems to only happen when I try to use the custom forms that I made up using Mark Leeds Formscript.pl. Help Mark!
Yes, these forms can be fixed. If you exit the form after saving by clicking on History I like you can go back in and few the data by clicking on the encounter date. The problem usually arises when you try to reopen the form for the edit.
That was where I was running into trouble I would be tinkering around polishing up how I wanted to have the form look under openemr and I found that if you try to go back in and edit the previously saved data it will dump the prior data and put in the new data when you go and save it. Kind of annoying but something that can be put up with. I guess that I just didn’t tinker with them enough in 2.8.1 to see that occur.
I’ve created an improved (imho) version of Mark Leed’s formscript.pl form creator. It includes the ability to edit forms you’ve created just like any other form, as you would expect to be able to by clicking on the existing form from within encounters.
If you’re interested let me know and I can e-mail it to you.
I’m really sorry, I totally forgot to commit the changes you sent emailed to me. I have been using the version you sent me since but I forgot to share it.
I just now committed it to cvs. Did you do more work on it since you emailed it to me in July?
Thanks for maintaining formscript.pl. I have been so caught up in other things recently, particularly trying to collect nearly a year’s worth of insurance money (see my zirmed.php script going up soon to contrib).
No worries Mark. I hope I didn’t come off as ungrateful for the excellent work you’ve done on the original formscript.pl.
There’s no way I could have come up with it from scratch the way you did. It’s always easier to improve on something that’s already been created than to create it from scratch.
I’m glad it’s been of use to you!
That’s for posting it to CVS.
This is for either Mark or Mike. I have used the new and improved formscript.pl that is now on CVS and it works as advertised. Thanks so much for the effort that both of you have put into this script. I do have 2 questions regarding it that I hope you can help me with. Number 1 is the don’t submit button no longer seems to be generated on the custom forms. And number 2 is when you go to print out the report 2 things seem to happen, #1 is ther is no orphan control when the data spans more than 1 page, and #2 it cuts off data on the right hand side of the report page instead of doing the equivalent of word wrap on the print out. Any thoughts?
I haven’t looked at the print.php that the formscript.pl generates a whole lot. When I was working on getting it to allow you to edit existing forms I was only concerned with the on-screen display and never got to the printing part.
I’m deep (for my knowledge level anyway) into trying to figure some things out for the calendar right now and find myself very short on time. I’m not sure what you mean by “no orphan control” when it goes over one page. I’m sure Mark will be of help with this.
The good thing is that as long as you don’t change your input file, or at least don’t make changes that affect the database structure, you can run formscript.pl again and again on your form without messing anything up. Of course be careful and back up your existing form before trying this.
This is assuming formscript.pl has been updated and has something new to offer in the way of features or bug fixes. Running the same version on the same input file will not fix anything
Thanks to both of you for your help! I’m not going to go live until I get everything pretty much just the way I want it for our practice so the pressure is low grade for formscript.pl.
Mark I was just trying out the version of CAMOS that is included with the CVS version and everything seems to work just right with the various subcategories showing up correctly all the way through report generation. That is until you click on printable version and then it shows multiple levels of the first subcategory that was submitted. I was wondering why it does that? No hurry just wondering.
It should show the category, subcategory and item on one line and then the content below.
This can be changed by commenting out one or two print statements in the report.php file. I kept this in for backwards compatibility for my own patient records. Early on, I was not repeating the item text in the content box. For example, the text under the item column might be “Amoxicillin 500mg” and the content box would have something like “#30/thirty capsules…” I no longer organize my data like this. I make my content completey self-contained so when printing reports I don’t need to show all of the levels. This is more sensible, because you don’t necessarily want people reading your reports to know how you organize your text templates. The problem is that when I changed it, older records were missing data when I printed them.
I agree that this should be taken out in the CVS version because you don’t want to share this data in generated reports. It should be in the database for your own data mining purposes, but not seen otherwise.
