Oraform

What Makes an Online Patient Form HIPAA-Ready

No software can make your practice HIPAA compliant, and any vendor who says otherwise is telling you something that is not theirs to say. Here is what a form tool can actually do, and how to check it.

By The Oraform team · Published

⚠ This is general information, not legal advice, and it is not a substitute for your own privacy officer or counsel. It is written by a vendor, which is a reason to check the sources linked at the bottom rather than take our word for any of it.

Start with the language, because it tells you a lot

There is no such thing as HIPAA certification. There is no government body that inspects software and issues one, and no accreditation that makes a product compliant. A vendor that says “HIPAA certified” on a marketing page is either confused or counting on you being.

“HIPAA compliant” is slightly better but still wrong when it is said about software. Compliance is a property of a covered entity — your practice — and it covers things no vendor touches: whether you did a risk analysis, who you granted access to, whether you removed that access when someone left, what your workforce training looks like, what you do when a laptop goes missing.

What a vendor can honestly say is that their product is built to be used in a HIPAA context: encrypted, access-controlled, logged, and covered by a business associate agreement they will sign. That is a real claim and it is checkable. We say HIPAA-ready and we sign a BAA, and we do not go further, because further is not ours to say.

This matters practically, not just semantically. A vendor careless about the claim is often careless about the thing — the ones who will not sign a BAA are frequently the ones with a compliance badge in the footer.

The business associate agreement is the first question

If a vendor handles protected health information on your behalf, they are a business associate, and you need a business associate agreement with them. This is not optional and it is not a formality — it is the document that makes the arrangement lawful and that sets out what they may do with the data.

Ask for it before anything else. Three things are worth reading rather than skimming:

  • What the vendor is permitted to use the data for. “To provide and improve the service” is doing a lot of work in some agreements; ask what “improve” means.
  • Subcontractors. A form vendor runs on somebody's infrastructure, and that somebody is a subcontractor who needs their own agreement in place. Ask who they are.
  • What happens at the end. When you stop being a customer, what is returned, in what format, and what is destroyed, and when.

A vendor who will not sign one, or who offers a BAA only on a plan several tiers above the one you need, has told you where patient data sits in their priorities. That is useful information at the point of choosing.

Encryption, said plainly

Two separate questions, and vendors sometimes answer only the first. In transit means the connection between the patient's phone and the server is encrypted — HTTPS, which at this point is table stakes and which you can check yourself by looking at the address bar. At rest means the data is encrypted where it is stored, so a stolen disk or a mis-set permission is not a readable database.

Ask both, and ask where it is hosted. You are not looking for a logo; you are looking for a plain answer like “encrypted in transit and at rest, on Google Cloud”. If the answer is vague, that is the answer.

One thing worth checking that people forget: file uploads. If patients can photograph an insurance card or attach a document, those files are protected health information too, and they need the same treatment as the answers. Ask specifically.

Who can see a submission

This is the question with the most practical consequence, and it has two halves.

On the vendor's side: who at the company can read submissions, under what circumstances, and is that access logged? Support occasionally needs to see something to fix a problem; the question is whether that is deliberate, recorded and rare, or whether everyone in engineering has a database client.

On your side: access should be per person rather than a shared login, removable the day someone leaves, and scoped so that a front desk member sees what they need to. The shared login is the most common real-world failure here — it is convenient, and it makes every audit log useless, because “who looked at this record” now has one answer for the whole practice.

  • Is every view of a submission logged, with who and when?
  • Is every export logged? Exports are the ones that leave your control.
  • Can you remove someone's access yourself, immediately, without contacting support?
  • Does the system let you see the log, or only the vendor?

Retention, export and getting your data out

Patient records have retention requirements, and they vary by state and by profession. A forms vendor is not where your legal record of retention should live, but what they hold still needs a policy.

The two questions: how long does the vendor keep a submission, and can you delete one when you need to? And separately — what happens if you leave? Get the export format in writing before you sign, not after. A PDF per submission is fine for the chart; a structured export matters if you ever want to move.

Breach notification

If a breach happens at the vendor, you are the one with notification obligations to patients and to HHS, and your clock may start when they tell you. So the question is not whether they have a plan — everyone says yes — but what their contractual timeframe for telling you is, and what information you will get.

Read that clause in the BAA specifically. “Without unreasonable delay” is standard language and it is weaker than a number. Where a number is offered, it is worth having.

The tracking scripts nobody checks

This is the item most often missed, and it is the one that has caused real enforcement problems for health organisations: third-party scripts on pages where patients enter health information.

Marketing sites carry analytics, advertising pixels, session replay and chat widgets as a matter of course. When the same stack ends up on a patient-facing form, those scripts are in a position to see what a patient types, which pages they visited, and which conditions they looked at — and to send it to a third party who has no business associate agreement with anyone.

The check is concrete and you can do it yourself. Open your form page, open the browser's developer tools, look at the network tab, and see which third-party domains it talks to. On a page where a patient answers medical questions, the honest answer is that there should be almost nothing there.

⚠ It is worth asking a vendor directly: do you run analytics, advertising or session-replay scripts on patient-facing form pages? We do not. We run them on this marketing site — where the visitor is someone reading about pricing — and nowhere near a patient form, and our own form fields are masked even here.

The checklist

Printable version, in the order worth asking:

  1. Will you sign a business associate agreement? What does it permit you to do with the data, who are your subcontractors, and what happens at termination?
  2. Is data encrypted in transit and at rest, including uploaded files, and where is it hosted?
  3. Who at your company can see submissions, in what circumstances, and is it logged?
  4. Can we manage access per person, and remove someone immediately ourselves?
  5. Is every view and export logged, and can we see the log?
  6. How long do you retain submissions, can we delete them, and what is the export format if we leave?
  7. What is your contractual breach notification timeframe, and what will you tell us?
  8. Do any third-party analytics, advertising or session-replay scripts run on patient-facing form pages?
  9. And for your own side: who has access today, is any of it a shared login, and would you know if the wrong person looked?

The last one is not about the vendor at all, and it is usually the one that needs work.

Sources

Questions

Is there such a thing as a HIPAA certified form builder?

No. There is no government certification for HIPAA and no accreditation that makes software compliant. A vendor can be built for use in a HIPAA context and will sign a business associate agreement; that is the real, checkable claim. Treat a “HIPAA certified” badge as a reason to look harder.

Does a BAA make our practice compliant?

No. It is necessary, not sufficient. Compliance is about how your practice works — your risk analysis, your access controls, your training, what you do when someone leaves. The BAA covers the relationship with the vendor and nothing else.

Can we email patient forms if we encrypt the attachment?

That is a question for your own privacy officer, and the answer depends on what you encrypt and how the patient receives the key. What is worth noting is that the common version — a completed PDF attached to ordinary email — is not encrypted end to end and leaves copies on several servers.

What should we check on our own form pages?

Open the page, open the browser's network tab, and look at which third-party domains it contacts. On a page where a patient enters health information there should be essentially nothing. It takes a minute and it is the check almost nobody does.

Get started

Get a free sample of your form.

Send us the forms you hand patients today and we'll turn them into working Oraform samples — your logo on them, finished on a phone or a computer. We rebuild all of your forms free, and free setup comes with it. No cost, no commitment, nothing to cancel.

Optional. We rebuild all of your forms free — send up to three here and email any others to forms@oraform.health. Please check those files.

Blank forms only, please. We only need the questions, not anyone's answers — and we check before anything goes near a sample.

Please confirm the forms you're sending are blank.
One business day, and free setup with it.

All guides