Oraform

How to Move Patient Intake Online

Most practices do not fail at this because the software is hard. They fail because they move fourteen forms at once, in a week, without telling the front desk. Here is the order that works.

By The Oraform team · Published

General information about running a project, not legal advice. The HIPAA section below describes the questions to ask; whether your practice has answered them is a matter for your own privacy officer or counsel.

Start by counting what you actually hand people

Before anything else, put every form a patient touches on one table. Not the ones in the drawer labelled forms — the ones a patient is actually given. In most practices the two lists are different, and the difference is the first thing worth knowing.

For each one, write down four things: who fills it in, when, what you do with the answers, and what happens if it comes back blank. That last question is the useful one. A form where nothing happens when it is empty is a form you can cut, and almost every practice has at least one.

Expect the list to be longer than you thought. A dental new patient is typically given registration, medical and dental history, a HIPAA acknowledgment, a financial policy and a consent — five documents, often stapled into one wad, with the staple doing the work of a workflow.

  • Which forms does every new patient get, without exception?
  • Which are conditional — only for minors, only for a procedure, only for certain insurance?
  • Which get re-taken, and how often? An annual medical history update is a different project from a one-off intake.
  • Which answers does someone actually read, and which are filed unread?
  • Which questions exist because a payer or a state rule requires them, and which exist because they were on the form you inherited?

Cut before you convert

The single biggest mistake is to rebuild what you have, question for question, and call it done. Paper forms accumulate: a question gets added after an incident, another after a software change, and nothing is ever taken off because nobody owns the removal.

Converting a bloated form gives you a bloated form that is now easier to abandon halfway through, because a patient on a phone can simply stop. The clipboard at least had the social pressure of a receptionist watching.

So go through the question list once, properly, with whoever reads the answers. Three tests are enough:

  1. Does anyone read this answer? If the answer is no, cut it. If the answer is “sometimes, when it matters”, make it conditional on the thing that makes it matter.
  2. Would you rather have this answer, or a finished form? Every question costs you completions. For most practices, a patient who finishes a shorter form beats a patient who abandons a longer one at question 40.
  3. Is this question asking for something the patient cannot possibly know? “Policy group number” from memory, standing at a desk, is a question that produces wrong answers rather than no answers — which is worse. Ask for a photograph of the card instead.

Keep a note of what you cut and why. The question will come back, usually in six months, usually from someone who was not in the room, and a one-line reason is the difference between a conversation and a reversal.

Pilot with one form, not fourteen

Pick the form that is highest volume and lowest risk. For most practices that is the new patient registration: every new patient gets it, nothing on it is clinical, and if it goes wrong the failure is an address you have to ask for again rather than a missed allergy.

Run that one form, and only that one, for a fortnight. You are not testing the software — you are testing your own process. The questions you want answered are about the practice, not the product:

  • Does the link actually reach patients? Through which channel — your reminder text, your email, a QR code on the desk?
  • What proportion arrive having finished it? You will not know until you look.
  • What does the front desk do when someone turns up not having done it? There has to be an answer, and “hand them the paper one” is a perfectly good answer for a fortnight.
  • Where do people stop? If a question is costing you completions, it shows up as a cluster rather than a complaint.
  • What does your team say unprompted on day three?
An Oraform patient form on a phone asking for a first and last name, with a progress bar reading “0% · about 3 min left” and a Continue button
Short, easy screens, with a progress bar and an honest estimate. A patient who can see the end is a patient who reaches it.

Two weeks is enough to find the process problems and short enough that nobody has committed to anything. Then add the next form.

The front desk is the project, not the software

Whatever you roll out, the people who decide whether it works are the two or three at the desk. They are the ones who will be asked “what link?”, who will be standing there when a patient has no phone, and who will quietly go back to paper if the new way costs them more than it saves.

Three things make that go well. First, tell them before you launch rather than during it. Second, give them a fallback they are allowed to use — a tablet at the desk with the same link open, and paper for the person who cannot or will not. Third, make sure they can see what has come in, so “did the Hendersons do theirs?” is a glance rather than a phone call.

It also helps to be straight with them about what this does not fix. If your practice management software needs the details typed in by hand today, an online form does not change that on its own — it changes where the details come from and how legible they are, which is worth a lot, but somebody is still typing. Promising otherwise is how you lose the desk in week two.

What patients need to be told, and what they do not

Patients do not need a change-management email. They need the link to arrive at a moment when doing it is easy, and they need the form to be obviously short.

The moment matters more than the message. A link in an appointment reminder sent the evening before is answered; the same link in a welcome email sent three weeks earlier is not. If you can send it twice — once at booking and once the day before — the second one does most of the work.

Two practical things remove most of the friction. Make sure nothing requires an account: a patient who has to create a password to tell you their address will not. And make sure progress is saved, so someone who starts on the bus and stops can finish at home without retyping their name.

One sentence is worth adding to whatever message carries the link: how long it takes. An honest “about four minutes” gets answered. “Please complete your new patient paperwork” sounds like twenty.

The HIPAA checklist, before a patient sees it

Patient intake answers are protected health information from the moment they are submitted, and often from the moment the form is opened. Whatever you use to collect them, these are the questions to have answered in writing before the first real patient:

  1. Will the vendor sign a business associate agreement? If the answer is no, or “we are HIPAA compliant” without a BAA attached, stop there. A BAA is the document that makes the relationship lawful; a compliance badge on a marketing page is not.
  2. Is the data encrypted in transit and at rest, and where is it hosted? You want a plain answer, not a certification logo.
  3. Who at the vendor can see submissions, under what circumstances, and is that access logged?
  4. Who at your practice can see them? Access should be per-person, removable the day someone leaves, and logged.
  5. How long is data kept, and what happens when you stop being a customer? Get the export format in writing.
  6. What happens in a breach — who tells whom, in what timeframe?
  7. Does the form page itself carry third-party tracking? A marketing site with analytics on it is one thing; a page where a patient answers medical questions is another, and advertising or session-replay scripts do not belong there.

That last one is worth checking rather than assuming. It is an easy thing for a vendor to have switched on everywhere by default, and a patient answering a depression screener is not a page to be replaying.

⚠ Note the wording throughout. A product can be built for HIPAA — encrypted, access-controlled, logged, covered by a BAA. It cannot make your practice compliant, because compliance is about how your practice works: who you give access to, what you do when someone leaves, whether you actually did the risk analysis. Any vendor telling you their software makes you compliant is telling you something that is not theirs to say.

Decide what you are measuring before you start

The reason to do this is not that online forms are modern. It is one of a small number of specific outcomes, and it is worth writing down which one you are after before you start, because it decides what you do next.

If the goal is appointments starting on time, the number to watch is how many patients arrive with the form already done. If the goal is legibility and fewer transcription errors, the thing to watch is how often someone has to phone a patient back. If the goal is that the clinician reads a history before walking in rather than during, the test is whether they actually do.

Whatever it is, watch where people stop. Drop-off by question is the most useful thing a form can tell you, and it is almost always one or two questions rather than general fatigue. The usual culprits are a request for a photograph, a question that demands a number nobody carries, and a free-text box that looks like homework.

Then fix those two and leave the rest alone. The temptation after a successful pilot is to redesign everything; the better move is to add the next form and change nothing else.

Sources

Questions

How long does it take to move patient intake online?

The software part is days. The honest answer for the whole project is a few weeks, and most of that is deciding what to cut and getting the front desk comfortable. A practice that pilots one form for a fortnight and then adds the rest tends to finish faster than one that converts everything at once.

Do we have to retype everything into our practice management system?

Today, with Oraform, yes — there is no EHR or PMS write-back, and we would rather say that plainly than imply otherwise. What changes is that the details are legible, complete and already there when you type them, and that you have a PDF for the chart and an Excel export. If an integration is what would make this work for you, tell us; it is what we are asked for most.

What about patients who do not have a smartphone?

Keep paper for them, and keep a tablet at the desk with the form open for the ones who would rather do it there. The goal is not that every patient uses the link; it is that most of them do, so the desk has time for the ones who cannot.

Should we move every form at once?

No. One form, highest volume and lowest risk, for two weeks. You are testing your own process rather than the software, and the process problems are much cheaper to find on one form than on fourteen.

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