Many web sites have “contact us” pages and include web forms for receiving requests from existing or potential customers. This includes “new patient intake” forms on the web sites of healthcare providers. However, if your aren’t using a secure form solution your web forms may suffer from several serious problems:
- Spam – Getting unwanted form submissions from bots.
- Privacy – Often, sensitive data is submitted insecurely through these forms.
- Archival – You may need an archived record and backup of all submissions.
- Notices – You may need to be alerted of form submissions, even if you are not online.
Proactive privacy vs. neglect of privacy
When your web forms transmit data insecurely, store or send data insecurely, or otherwise to do not treat the data submitted with the level protection that it deserves, you are putting the users of your forms at risk.
The typical argument is that “it is up to the user of the forms to decide if they want to submit sensitive information.” In fact, many insecure forms even have disclaimers requesting people to not submit sensitive information if they have concerns … and then the forms go on to ask lots of sensitive questions. Especially without a disclaimer, but even with one, the form is actively soliciting people to submit their information insecurely and requesting them to take risks with their private data. This is not good.
In areas such as healthcare, where these forms are often collecting sensitive health data (protected health information – PHI), the fact that an organization solicits the submission of PHI through insecure, non-HIPAA-compliant means is far from a “best practice.” Why does this happen?
- Securing forms is trivial and inexpensive. As the bar is so low to collecting data in a compliant way, it could be considered neglectful to not bother with security and privacy and continue to solicit data insecurely.
- People can insecurely send you their own, personal PHI any time … when it is done of their own accord. However, when you provide them with a recommended communication channel, and when that channel is not secure, you need to get informed consent from them before you accept the data through that channel. Informed consent means:
- Training them in the risks involved.
- Getting their explicit sign off indicating their acceptance of these risks.
- Capturing and saving those signed consent forms.
Getting signed consent must be properly done and it imposes a barrier in front of your forms. There is really no reason to go though all of the work to setup informed consent when it is much simpler to just secure the forms themselves.
You can block form spam, ensure content security and privacy, archive form submissions, and even get text message notices of new submissions to your phone using LuxSci SecureForm. And it takes only a couple of minutes to integrate a secure form into any existing web site at any web hosting provider.
How does SecureForm Integrate with a Web Site Form?
How Does SecureForm deal with Spam, Encryption, Archival, and Notices?
SecureForm enables privacy and security by allowing you to ensure that the form data is encrypted from the end user all the way to your email inbox. It enables automatic use of secure email delivery, secure FTP uploads, secure online document storage, and more. You can use any or all of these data capture methods.
SecureForm enables archival by allowing you to save copies of all form posts in an online document storage area, by uploading copies to your own FTP site, and/or by saving copies in a database that you can access as needed.
SecureForm enables notices by allowing you to have text messages sent to up to 5 different mobile devices when each form post is submitted. This is in addition to the form data being emailed to where it needs to go. You and you staff can be informed in real time of new posts, no matter where you are.
LuxSci SecureForm is the swiss army knife of web and PDF form processing tools, integrating quickly with any existing web sites and providing form security even if your web site is not already secured with TLS.