OpenEMR

hey,
This is done (was extensive and required mods to 9 files and now have
css/html printing options along with pdf). Committed to cvs; after it gets
testing for bugs will migrate to the 3.1.0 patch.
-brady

oops, was error in previous fix. Here are fixed instructions:

Modify line 879 of openemr/interface/forms/CAMOS/new.php :

Change:
str += key + "=" + escape(form_array[key]) + "&";

To:
str += key + "=" + encodeURIComponent(form_array[key]) + "&";

-brady

Fixed primary bug (step 2 below). Comitted to cvs and will put in patch#5
for 3.1.0.
The fix was simple:
diting the following on line
879 of openemr/interface/forms/CAMOS/new.php :

Change:
str += key + "=" + escape(form_array[key]) + "&";

To:
str += key + "=" + encodeURIComponent((form_array[key]) + "&";

Not the fix discussed below is unsafe. Characters such as ? and ; will
kill it.

-brady

Plan of action:

1) Primary author of module to commit most updated CAMOS code

2) Change the escape() function call to encodeURIComponent() in javascript
ajax call
--For php to answer this ajax call it needs to decode the data, so
will bring in the following functions into the code at library directory
(these will be useful in other parts of OpenEMR as AJAX calls begin to be
used more):
http://www.captain.at/howto-php-urlencode-javascript-decodeURIComponent.php

3) While here will convert all magic quotes checks to
openemr/library/formdata.inc.php function

4) Also translate button labels and messages

hey,

A quick fix for the utf-8 character bug is editing the following on line
879 of openemr/interface/forms/CAMOS/new.php :

Change:
str += key + "=" + escape(form_array[key]) + "&";

To:
str += key + "=" + form_array[key] + "&";

Note this hasn't been fully tested. Still awating the modules author to
update newest version of CAMOS to cvs before anything further can be done
(more testing and translation of buttons)

-brady

hey,

Currently trying to pinpoint the utf-8 character bug, likely related to
the ajax call from new.php . Also, will need to internationalize the button
labels. Currently discussing this stuff with the module author, Mark
Leeds.

-brady

The point of inserting data through a Form to an Encounter is very
critical. This must be simple and fast or the user will be dissatisfied.
The Forms already included are almost useless for a large part of doctors
(eg. specialists in a specific field) as they need highly specialized ones,
which can be done either with the CAMOS-module or with the 'formmaker'.
Unfortunately both do not support internationalization which, for the whole
pakcage, is a major drawback for foreign users.

I suggest this becomes a priority if it is not too expensive.