HIPAA compliant online forms and e-signatures
HIPAA compliant forms operate under a signed business associate agreement, appropriate Security Rule safeguards and the practice's own policies. The vendor's BAA must be in place before the vendor stores patient answers.
Intake Pro signs a BAA before your practice collects real patient data. Staff use MFA, reads are scoped to the practice and logged, and files are encrypted at rest.
Last updated
- BAA Before real patient data
- Staff sign-in Multi-factor authentication
- Staff sessions 12 hours
- Access log Every practice read
- Files Encrypted at rest
What makes an online form HIPAA compliant?
An online form is HIPAA compliant when the vendor storing answers signs a BAA with the practice, the tool has safeguards the Security Rule asks for, and the practice uses the form under its own policies. All three parts concern the same patient-data workflow.
Under 45 CFR 160.103, a company that maintains protected health information for a covered entity is a business associate. A covered entity needs a written business associate contract under 45 CFR 164.502(e) and 45 CFR 164.504(e).
HHS says a cloud vendor storing electronic protected health information is a business associate even when the data is encrypted and the vendor has no key. Using that vendor without a BAA violates HIPAA. Read What is a BAA? alongside the patient intake software workflow.
This page gives general information. Confirm your practice's legal and compliance obligations with its own counsel or compliance lead.
What does HIPAA require of an online form tool?
HIPAA requires an online form tool and its practice customer to address contracts, technical safeguards, breach reporting and data collection. The table maps each requirement to the cited rule and the evidence a practice manager should request.
| Requirement | Where it comes from | What to look for |
|---|---|---|
| Business associate agreement | 45 CFR 164.502(e) and 164.504(e) | A signed written contract before the vendor handles patient data |
| Access control | 45 CFR 164.312 | Unique user identification and automatic logoff, with role-appropriate access |
| Audit controls | 45 CFR 164.312 | Activity records for systems holding electronic protected health information |
| Integrity | 45 CFR 164.312 | Controls for protecting electronic protected health information from improper alteration or destruction |
| Person or entity authentication | 45 CFR 164.312 | A way to verify the identity of a person or entity seeking access |
| Transmission security | 45 CFR 164.312 | Technical measures guarding electronic protected health information during transmission |
| Vendor breach notice | 45 CFR 164.410 | Notice without unreasonable delay and within 60 calendar days after discovery |
| Minimum necessary collection | 45 CFR 164.502(b) | Fields limited to the protected health information needed for the stated purpose |
How does Intake Pro handle HIPAA requirements?
Intake Pro handles patient forms with a BAA, staff identity controls, scoped access and retained signature evidence. The controls below describe product behavior; your practice remains responsible for its own HIPAA policies and use.
- Intake Pro signs a business associate agreement before your practice collects real patient data.
- Staff sign in with multi-factor authentication.
- Staff sessions end after 12 hours.
- Roles can be customized for your practice's staff assignments.
- Every read is scoped to the practice and logged.
- Files are encrypted at rest, and connections use HTTPS.
- A published form version is immutable, so later edits do not change earlier signed submissions.
- Each signed record keeps its form version, signer, signing time, signed PDF and audit trail.
- The kiosk screen clears 60 seconds after a submission, and kiosk forms work offline before sending when the tablet reconnects.
Review security and HIPAA at Intake Pro and the evidence retained in signed records and exports.
Why is there no official HIPAA certification for form software?
There is no official HIPAA certification for form software. HHS does not certify or endorse products, so a practice must assess the vendor's BAA, safeguards and operating terms instead of accepting a certification claim.
A practice manager should ask who signs the BAA, how staff identities are verified, what activity the audit records show and how signed documents are retained. Those answers describe a specific vendor relationship and workflow.
The glossary of patient intake and HIPAA terms defines the roles and records involved in that review.
Are Google Forms and other general form tools HIPAA compliant?
Google Forms and Jotform have different BAA terms that a practice must check before collecting patient data. Google requires a BAA for protected health information, while Jotform offers HIPAA features and a BAA on its Gold and Enterprise plans.
Google says customers must not use Google services with protected health information without a BAA with Google. A Workspace or Cloud Identity super administrator accepts the BAA in the Admin console, and third-party add-ons are not covered.
Google documents 12 question types, none of which is a signature. Read Is Google Forms HIPAA compliant? and the Google Forms comparison for the intake implications.
Jotform states that HIPAA features and a BAA are available on Gold and Enterprise, with plan details on its plans page. See the Jotform comparison for a focused review.
Are e-signatures on HIPAA forms valid?
HHS allows HIPAA authorizations to be obtained electronically, provided the electronic signature is valid under applicable law. That position comes from HHS FAQ 554, which addresses electronic health information.
The signature question is separate from whether the vendor may store the patient's answers. Your practice still needs the BAA and safeguards described above, together with the authorization elements in 45 CFR 164.508(c).
Read Are e-signatures valid on patient forms? for the authorization details. Intake Pro supports typed and drawn signatures for patients, representatives, staff members and witnesses.
What should you ask a form vendor about HIPAA?
A form vendor should answer specific questions about its BAA, staff access, files, audit records and signed versions. Give these questions to the practice manager or compliance lead who reviews the vendor before real patient data is collected.
- Will you sign a business associate agreement with our practice before we collect real patient data?
- Do all staff accounts use multi-factor authentication and unique user identities?
- How do staff sessions end, and can our practice limit access by role?
- Is every read of a patient response scoped to our practice and recorded in an access log?
- Where are form files stored, and are stored files and network connections encrypted?
- What happens to our signed records and patient data if we cancel, and which exports can staff retrieve?
- Can anyone change a published form version after patients sign it, and what audit trail stays with each signature?
- How will your business associate notify our practice after discovering a breach of unsecured protected health information?
What stays your practice's responsibility?
Your practice keeps responsibility for its privacy notice, staff access, training, necessary questions and record retention. A form vendor supplies parts of the technical workflow, while the practice decides how its workforce uses that workflow.
- Publish and provide your own notice of privacy practices, then make a good-faith effort to obtain written acknowledgment under 45 CFR 164.520(c)(2); build the privacy notice acknowledgment around your own notice.
- Assign staff roles, review who can open patient forms and train staff on your practice's procedures.
- Ask only for information the practice needs, following the minimum necessary standard in 45 CFR 164.502(b).
- Keep HIPAA-required documentation for six years under 45 CFR 164.530(j), and follow state law for medical record retention.
- Use the intake forms guide to review fields and the patient intake forms guide to assign signatures and chart transfer.
- Check unfamiliar contract and record terms in the patient intake and HIPAA glossary.
Sources
- 45 CFR 160.103: HIPAA definitions
- 45 CFR 164.502: uses, disclosures and minimum necessary
- 45 CFR 164.504: business associate contracts
- HHS cloud computing guidance
- 45 CFR 164.312: Security Rule technical safeguards
- 45 CFR 164.410: business associate breach notification
- 45 CFR 164.520: notice of privacy practices
- 45 CFR 164.530: documentation retention
- HHS FAQ 554 on electronic HIPAA authorizations
- 45 CFR 164.508: authorization core elements
- Google Workspace and Cloud Identity HIPAA implementation guide
- Google Forms question types
- Jotform HIPAA features and BAA
- Jotform plans
Checked on
Questions
Can my practice collect patient answers before Intake Pro signs a BAA?
No. Intake Pro signs a business associate agreement before your practice collects real patient data. Complete that agreement before sending live patient forms or placing real patient answers in the system.
Does Intake Pro log staff opening a submitted HIPAA form?
Yes. Every read is scoped to the staff member's practice and logged. Staff also sign in with multi-factor authentication, and your practice can customize roles for access.
What deadline applies to a business associate reporting a breach?
A business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovering a breach of unsecured protected health information.
Does making a HIPAA form question optional remove minimum necessary concerns?
No. An optional answer still collects protected health information when a patient responds. Your practice should ask only for information it needs for the purpose, whether the field is required or optional.
Are third-party Google Workspace add-ons covered by Google's BAA?
Google says third-party add-ons are not covered by its BAA. Your practice should assess any add-on separately before allowing it to access protected health information.
Can staff alter a published Intake Pro HIPAA form after it is signed?
Staff cannot alter the published version attached to that submission. Editing creates a new version, while the original signed PDF, signer details, signing time and audit trail stay with the earlier response.