codemonkeys

I understand your frustration with Gravity Forms not being free and the only option since Caldera went out.

We’re currently developing a new HIPAA compliant forms and patient portal/mangement system that will have a form builder built into it. We’re shooting for an early spring release.

Unfortunately integrating the current plugin with another third party form builder is a time consuming heavy lift. When Caldera walked away 2 years ago we had to make a decison on if we would put the time into this or focus our development time on the new product we’re building. Since we do still have Gravity integration we opted to focus our effort on the new system as it will be much more capable, cleaner, easier to work with and able to use FHIR standardized data fields along with MANY more features than just accepting forms.

I know this doesn’t solve your need today but trust me when I say what we have coming soon is light years beyond our current plugin and anything else out there today.

I apologize for the delay in responding. In the future, please create a ticket here: https://codemonkeysllchelp.freshdesk.com/support/tickets/new

Here is some help with this question:

https://codemonkeysllchelp.freshdesk.com/support/solutions/articles/48001227766-ajax-error-form-not-found

I apologize for the delay in responding. In the future, please create a ticket here: https://codemonkeysllchelp.freshdesk.com/support/tickets/new

Typically there are 2 issues with notification emails. The first is that they are not working at all. SMTP plugin should resolve.

For plugin-specific issue, typically it is with the setup. Most likely the from email. Some sites will not all generic emails to be sent (gmail, for example). Others will have constraints for @domain.com to avoid spoofing.

Here is the the setup information. Please create a ticket if you still need assistance.

https://codemonkeysllchelp.freshdesk.com/support/solutions/articles/48000946433-e-mail-notification-options

Leslie,

Here is the nonce: cm-hipaa-forms-nonce.

The best way to contact us through our
https://codemonkeysllchelp.freshdesk.com/support/home HIPAA Forms Support Site

Code Monkeys, LLC

Pete,
It says this was resolved, but there is no resolution. We are getting the exact same error message. Although we are able to click on pop-ups to white list (many of them), I would like to resolved once for all (we see it everything time a plugin is upgraded).

Thanks

Cody,

With the sunset of Caldera, we will only support Gravity Forms in the future. We have no plans to integrate with any other form builder. Although Gravity is not free, 1 domain is $59 per year. Most of our clients had moved off Caldera to Gravity before the sunset announcement.

Regards,
Ed

Hi Mike,

Have you created a ticket regarding this issue? Please do that at https://codemonkeysllchelp.freshdesk.com/support/tickets/new

We have some WordFence information and I know that there many HIPAA Forms clients using WordFence.

Regards,
Ed

Hello,

Let’s please do 2 things. First, please create a ticket in our Support System (https://codemonkeysllchelp.freshdesk.com/support/tickets/new) And in that ticket, please attach a Gravity export of the form in question. It will make it much easier to test/resolve. Also, confirm the version of Gravity you are using (have you moved to V2.5+ yet?)

Thanks
Ed

If you have not yet submitted a ticket, please do so here:
https://codemonkeysllchelp.freshdesk.com/support/tickets/new

Thanks

Rebecca,

Because I was answering your questions in our Ticketing system, I did not answer here.

Regards,
Ed

I strongly doubt Contact Form 7 will sign a BAA but even if they do my bigger concern is how you will actually use those forms in a secure HIPAA compliant way?

I’m one of the developers for the HIPAA Forms plugin for WordPress which as far as I know is the only real HIPAA compliant form solution for WordPress forms.

Remember that passing form information over regular email is not secure and always an immediate violation. This violates the “in transit” aspect of HIPAA.

If you aren’t passing the data via email but are saving that data to your hosting server you have to have a BAA with your hosting company and your server/database has to be secure meaning the database needs to be encrypted and if you allow files to be uploaded the hard drive has to be encrypted. This is the “data at rest” aspect of HIPAA.

There’s other aspects to consider as well but these are the main 3 things to cover, unbroken chain of BAA agreements for all involved, securing data in transit and securing data at rest.

Yes. You create form in either Gravity or Caldera. When user submits, we encrypt and send via SSL to encrypted DB. ALL PHI is encrypted.

Yes this was resolved within a couple of hours.

The way we’re able to make these HIPAA compliant is that the form data is not stored on your server or sent via email.

Instead, our plugin over-rides the default form submission functionality, encrypts the form data, pushes the encrypted data over SSL/TLS through our API and then stores that data on our HIPAA compliant encrypted database.

In order to access the submitted forms you have to login to the WP admin dashboard with an account with the appropriate permissions/user role and go to the HIPAA Forms interface.

From there the forms are pulled back down through our API, decrypted and then displayed.

Our API-based system allows us to ensure the data remain secured both in transit and at rest and that no PHI is ever stored on your hosting server or passed through insecure email.

We also incorporate a thorough logging system into our solution. Any time a user accesses the HIPAA Forms interface it’s logged and timestamped. We also log individual form interactions such as when a submitted form is viewed, archived, deleted or exported.

Finally, in order for our solution to be activated a BAA must be in place.

Hopefully that helps answer some of your questions as to how we’re able to keep the form submissions secure and compliant.

We’re currently having an issue with AWS. We’re talking with our rep now to resolve it and should have it figured out soon.

Correct, the Gravity drag ‘n draw signature field doesn’t work with the HIPAA Forms plugin.

We actually include our own drag ‘n draw signature field in the plugin that you can enable by going to the HIPAA Forms interface in the WP admin dashboard -> Settings Tab -> Form Settings sub-tab and then click on the triangle icon next to your selected form to expand the form settings. Check the show signature box and hit save.

You should now have the signature field at the bottom of your form.