E-Sign API

system · January 25, 2014, 11:58pm

bradymiller wrote on Saturday, January 25, 2014:

Hi,
Just committed the modification to sourceforge.
-brady
OpenEMR

system · January 27, 2014, 12:00pm

fsgl wrote on Monday, January 27, 2014:

Working nicely in the new 4.1.3 Demo.

system · January 30, 2014, 4:52am

arnabnaha wrote on Thursday, January 30, 2014:

Hi all…
The esign now works but there is a problem,It doesnot lock forms which are xmlformgen made…it only locks native and layout based form…why??

system · January 30, 2014, 6:35am

tmccormi wrote on Thursday, January 30, 2014:

First, what did you do that changed it from not working to working?

Can you provide a zip file of a form that does not work? Since the system signs the forms by table data the form creation model should not matter, but wierder things have happened.

–Tony

system · January 30, 2014, 6:53am

arnabnaha wrote on Thursday, January 30, 2014:

Did nothing special…i updated my openemr with the recent code from the dev tip and what I found was that esign works perfectly in the native forms but not in custom forms made by xmlformgen…u can check out my demo here:

http://nahahealthclinic.dyndns.org/openemrtest

username admin
password: pass

please send me your email ID so that I can send the xmlformgen created forms to you…

In my above mentioned demo…there is a form called follow up form created with xmlformgen…you can try the esign on that. you will see that it does nothing to it…but if you sign the native forms there…it works perfectly…

system · January 30, 2014, 6:56am

kchapple wrote on Thursday, January 30, 2014:

Please send or attach an example if a form that is not working.

Thanks
Ken@mi-squared.com

–
Please be aware that e-mail communication can be intercepted in
transmission or misdirected. Please consider communicating any sensitive
information by telephone. The information contained in this message may be
privileged and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to hipaa-security@mrsb-ltd.com and
destroy this message.

system · January 30, 2014, 2:33pm

blankev wrote on Thursday, January 30, 2014:

I am just exploring eSign so my comment might be confusing or incorrect! Stated this, I see in Arnab Demo that eSign has only crossed the first line. Should there not be more crosses at least also for:

Allows E-Signing Individual Forms…
Lock an e-signed form individually…

system · January 30, 2014, 3:55pm

tmccormi wrote on Thursday, January 30, 2014:

locking and signing individual forms is the default. check your globals
settings.

Tony McCormick

–
Please be aware that e-mail communication can be intercepted in
transmission or misdirected. Please consider communicating any sensitive
information by telephone. The information contained in this message may be
privileged and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to hipaa-security@mrsb-ltd.com and
destroy this message.

system · January 30, 2014, 9:02pm

kchapple wrote on Thursday, January 30, 2014:

Arnab,

The reason for your error is because your form directory names and form database table names don’t match. There is an “unwritten” standard in OpenEMR where form table should be named form_table_name and the directory should be table_name.

For example your Respiratory Exam Form uses database table form_resp_exam, but your form directory is respexam. It should be resp_exam.

In xmlformgen, the parameters are form dir and safe name.

This is a legacy issue with forms, and I propose a mapping in list_options to make a concrete mapping between form directories and their database tables. Then, for example, we could remove the hard-coding of checking for newpatient and re-routing to encounter form. Also, this way you could point to any custom form as your new encounter form.

Remember to backup your database before running any queries. Here is example SQL code using your Respiratory Exam Form on how to make your forms fit the standard.

1 - rename form directory
from resp_exam to respexam

2 - change directory in registry table
UPDATE registry
SET directory = ‘respexam’
WHERE directory = ‘resp_exam’

3 - change formdir in forms table
UPDATE forms
SET formdir = ‘respexam’
WHERE formdir = ‘resp_exam’

Ken

system · January 30, 2014, 11:44pm

mdsupport wrote on Thursday, January 30, 2014:

I propose a mapping in list_options to make a concrete mapping between form directories and their database tables.

We haven’t used xmlforms but if the architecture permits, couldn’t xml layout include hidden formdir? That will make form definition self-contained or portable and hopefully ‘modular’.

system · January 30, 2014, 11:55pm

kchapple wrote on Thursday, January 30, 2014:

MD,

There are two fields in the xml. One for directory name, and one for database table name (though they are not explicitly named as such.)

The problem is that the xml user has to know to make their definitions for those two fields match up.

Ken

system · January 31, 2014, 1:45am

bradymiller wrote on Friday, January 31, 2014:

Hi,
I haven’t looked at the pertinent code in awhile, but shouldn’t there be a way to deal with discrepancies in table and dir names without mapping. For example, how does OpenEMR know to pull the correct stuff when it pulls up the encounter with the notes?
-brady
OpenEMR

system · February 1, 2014, 6:59am

kchapple wrote on Saturday, February 01, 2014:

It’s sort of like a one way street. The registry and the forms table both reference form directories. There are no explicit references to the DB table.

Please be aware that e-mail communication can be intercepted in
transmission or misdirected. Please consider communicating any sensitive
information by telephone. The information contained in this message may be
privileged and confidential. If you are NOT the intended recipient, please
notify the sender immediately with a copy to hipaa-security@mrsb-ltd.com and
destroy this message.

system · February 1, 2014, 5:01pm

mdsupport wrote on Saturday, February 01, 2014:

Ah! This is much bigger than xmlforms.

We need a encounter summary form for monthly billing that lets user review patient activities for a specified period and record total time to include in billing. This form (encounter2) will rely on data from other tables that may not even have encounter id link. Even if we were to put hard links in the form, E-sign still has a design challenge.

Alternative to list will be for e-sign to use optional e-sign form plug-in. If plug-in is not provided by the form creator, use current approach as a fallback. As an act of kindness to fellow developers, may be you can include a plugin template with standard release.

system · February 2, 2014, 5:33am

kchapple wrote on Sunday, February 02, 2014:

I’m not sure I understand your question or concern. I don’t think it’s related to the issue that Arnab had. Could you please describe the issue you’re having more clearly?

If you have forms that utilize database customizations outside of the standard OpenEMR form structure, you’ll need to implement the SignableIF interface yourself, but much of the code should be re-usable.

The E-Sign code was designed as a re-usable API, and I have provided implementations for locking encounters, standard forms and LBF forms.

Ken

system · February 2, 2014, 6:35am

arnabnaha wrote on Sunday, February 02, 2014:

Thanks Ken & Tony
I have fixed all the xmlformgen form and it works beautifully now…thank u so much!

system · February 2, 2014, 7:01am

tmccormi wrote on Sunday, February 02, 2014:

You are welcome.

system · February 2, 2014, 7:32pm

sunsetsystems wrote on Sunday, February 02, 2014:

Tony,

I think we have a problem with the license for Fancybox 2.x which you included in this commit.

http://www.fancyapps.com/fancybox/#license

The author requires paying a fee for commercial use. This is not compatible with GPL. Can you substitute 1.x or otherwise deal with it? If not we’ll have to undo the commit.

Thanks,

Rod

system · February 2, 2014, 8:58pm

bradymiller wrote on Sunday, February 02, 2014:

Hi,
Nice catch Rod. Losing my touch on the reviews…
Agree that it will need to be dealt with.
-brady

system · February 2, 2014, 9:13pm

bradymiller wrote on Sunday, February 02, 2014:

Hi,

Very nice catch, Rod. I’m losing my touch on the reviews…
Agree that this has to be dealt with.

-brady

On 2/2/2014 11:32 AM, Rod Roark wrote:

Tony,

I think we have a problem with the license for Fancybox 2.x which you
included in this commit.

Fancybox | Fancyapps UI - Robust JavaScript UI Component Library

The author requires paying a fee for commercial use. This is not
compatible with GPL. Can you substitute 1.x or otherwise deal with it?
If not we’ll have to undo the commit.

Thanks,

Rod

E-Sign API
https://sourceforge.net/p/openemr/discussion/202506/thread/9687253b/?limit=25&page=3#ecc8

Sent from sourceforge.net because you indicated interest in
OpenEMR / Discussion / Developers

To unsubscribe from further messages, please visit
SourceForge.net: Log In to SourceForge.net