Is it possible to save a snapshot of a submitted iForm?

[James B]

I received a request for a feature that I could have sworn I've seen in a demo somewhere.

Is it possible to save a snapshot of a submitted iForm, in HEO?  For instance, it would be nice if I could click on a "Hospitalist PRN iForm Tracking Order" and have it display a grayed out iForm that shows all of the selections the user had made when they submitted it.

[TWessel]

I'm sure it's possible.  Not sure where you would store all of those documents if you automated this though.  If all you want to do is track what they actually ordered, there are two things you can do:

1- Output your VGR order string to the log file.  See LOG in the VGR manual.

2- Build a hidden outline first for your order set, then on your iForm for that order set use the OIS and OOS numbers from the hidden outline to track use of those orders from your iForm.  The OIS/OOS combos will be unique for each order on the outline and will distinguish these from the same orderables selected via the order completer or from other outlines.

We do both of the above.

Hope that helps!

Tom Wessel, MD

CMIO

SRHS

Spartanburg, SC

[James B]

Thank you for taking the time to reply.

Our goal is to be able to visualize what choices a user selected on an iForm.  That way, if a user submitted an iForm and then later contested that the iForm didn't work properly, we'd be able to pull up that "snap-shot" of their submitted iForm and see if the choices they selected matched up with the orders that actually came across.

Any ideas on how to go about that, or an alternate way to accomplish the same thing?  

Also, thank you for your suggestions regarding the LOG file and the hidden outlines.  We already do the outlines but I'm going to research more about the LOG file.

-James

[Scott Morris]

James,

Given your stated goal of creating an audit trail, utilizing the LOG might be your best bet.  HEO already logs what actions occur and are committed and, if you're using outlines to drive your iForms, you're already getting "iForm level" tracking of what's ordered and how.  The piece that I think you're missing is *before* the order is successfully placed.  ("Did they place the order via the iForm, but remove it before committing?" etc).  You can get some of this by logging (1) the submitted state of form elements and/or (2) the entire orderstring.

A word of caution, however - while this will give you more information about how the iForm placed orders, it will not capture certain edge cases.  For instance, if the user is correct and the iForm is not working correctly, then it will be hard or impossible to prove.  Consider the example where a med is dosed based on a drop-down field, but there is a typo on the form where it displays 15 mg, but sends 30 mg to the VGR. 

<option value="30">15 mg</option>

It will appear in the logs that the user chose 30 mg even though they may have chosen 15.  Now, if this medication is given at the wrong dosage in January, the typo is discovered and fixed in February, but an audit is performed in June, it may be next to impossible to trace the medication error to the typo unless your documentation is superb.

Just a word to the wise. Best of luck,

Scott Morris

[TWessel]

That's a little out of my league.  I think you would need to use something like PHP together with jQuery or just plain JavaScript to do that.  JavaScript alone won't allow you to write to files.  What I have done with just JavaScript is used the print() function in cases where the user =wants= to take the time to respond to the print dialog box and print a copy.  I don't think your users would tolerate that for the case that you cite.

Tom Wessel, MD

CMIO

SRHS

Spartanburg, SC

On Tuesday, January 20, 2015 at 1:28:30 PM UTC-5, James B wrote:

[James B]

Scott,

     Thanks for taking the time to reply.  I can't say I'm familiar at all with the LOG function but I'll do some research on that and speak with the other builders and see if they have any insight for using that as a tool.

Tom, your idea of using jQuery and php to hack something together is very interesting.  A quick google search seems to show ways to use jQuery to take a screenshot of current webpage.  Maybe its possible to bind that event to the clicking of the SUBMIT button.  Then would come the question of where and how to store it. I'm new to using web languages but this seems like it would be a fun puzzle to try and solve.

Thanks for the food for thought.  I'll let you know if I ever do come up with something.