Patient intake form requirements

It is tempting to treat an intake form as the bit before the appointment. It is really the point at which a practice takes custody of the most sensitive category of personal information there is, from someone in a car park, on a phone, five minutes before a first visit. The useful way to think about it is not as one form but as three kinds of information stacked together, each with its own rule.

The three kinds of intake information

Administrative. Name, date of birth, contact details, address, preferred language, health fund and member number. Ordinary personal information, and the rule is proportionality: collect what you need to identify, contact and bill, then stop.

Clinical. Reason for the visit, symptoms, medical history, medications, allergies, family history, lifestyle. This is health information: sensitive information under the Australian Privacy Principles, protected health information under HIPAA. Both frameworks hold it to a higher standard than a name and an address, and both expect you to justify each item.

Consent. The tick boxes and the signature. Not information you hold about the patient but the record of a decision they made, and it has to be kept with the wording they agreed to. A tick with no record of what it applied to is worth very little a year later.

The split matters because it drives the section order, the access setting on the link and how long each part is kept.

The sections, and what each one carries

The table at the end of this article breaks the 25 field example into its seven sections, with the kind of information each holds, the handling rule and the access setting it justifies. Two rows deserve comment.

Emergency contact is the section people forget is unusual. You are collecting a third person’s name and phone number from someone who is not that person. Keep it to name, relationship and phone, say it is used only in an emergency, and do not extend it into an address or a date of birth.

Family history has the same shape inside the clinical block. “Has a parent, brother or sister had any of these?” is clinically valuable and it is also information about people who never filled in your form. Keep the list tied to what the clinician will act on.

The example’s medical history uses a checkbox list of twelve named conditions with a “None of these” option rather than an open text box. A bounded list is answerable in ten seconds, is consistent across patients, and does not invite a paragraph someone then has to read.

Consent wording that holds up

Three rules, and they are all about separation.

Separate the consents. The example uses one checkbox group with three distinct statements: that the Notice of Privacy Practices has been received, that the patient consents to assessment and treatment, and that they accept responsibility for fees not covered by their fund. Those are three decisions. Bundling them into one “I agree” tick makes it impossible to show which one the patient turned their mind to.

Show the wording, not a link to it. On a published classic form, a field description is rendered for file upload and photo fields only, and every other field drops it silently. So the consent paragraph cannot live in a field description. It has to be a paragraph block sitting above the checkbox, where it is part of the form the patient reads.

Record the version. If you change the consent wording in March, responses from February agreed to something different. Publishing writes a new version row and each historical version stays available at its own URL, which is what lets you answer that question later.

Privacy under the APPs and HIPAA, in plain terms

This describes the principles, not legal advice, and a practice should take its own.

Under the Australian Privacy Principles, four do most of the work here. APP 3 governs collection and applies a higher standard to sensitive information, which health information is. APP 5 requires you to tell the patient at the point of collection who you are, why you are collecting it, who you usually disclose it to and how to complain. APP 6 limits use and disclosure to that purpose. APP 11 requires reasonable steps to protect it and obliges you to destroy or de-identify it once it is no longer needed.

Under HIPAA, the rule that shapes the field list is minimum necessary: a covered entity must make reasonable efforts to limit protected health information to the minimum necessary to accomplish the intended purpose. That standard does not apply to disclosures to another provider for treatment, or to the individual themselves, but it does apply to the form you are designing, and it is a good test for every clinical question on it.

The second HIPAA rule that shows up on the form itself is the Notice of Privacy Practices. It has required contents: a specific header, a description of how information is used and disclosed, a statement of the individual’s rights, how to complain, contact details and an effective date. A provider with a direct treatment relationship must give it no later than the date of first service delivery, make a good faith effort to obtain written acknowledgement of receipt, and keep it posted prominently. The first consent tick in the example is exactly that acknowledgement.

Who can open the form: the four access types

There are four settings, and the difference between two of them is regularly misunderstood.

Public means anyone with the link. Fine for an enquiry form, wrong for a clinical history.

Secret key is a password on the link. Practical for a form sent by SMS with the key in the same message, which is convenience more than security, but it does stop a forwarded link from opening.

Login required means the person must be signed in. You can allow any signed in user, or list specific email addresses, or a whole domain such as @yourclinic.com. This is the strongest of the four.

Domain restricted is the one people pick by mistake. It does not restrict people, it restricts which sites may embed the form in an iframe, and it relies on the origin the browser reports, which can be spoofed outside a browser. The interface itself flags it as a light safeguard rather than real access control. For a clinical form use secret key or login required. The access control page covers all four, and there is a separate page on login required forms.

Signatures on intake forms

Use the inline signature field, drawn or typed by the patient as they fill the form, which prints into the response PDF next to the consents it authorises. The e-signature field is a different thing: it emails a named signer, supports a signing order and returns a certificate of completion, which suits an employment contract rather than a consent tick.

One hard constraint. Inline signing and photo upload do not work on a published conversational form. Both fall through to a plain text box, with no signature pad and no upload control. A form that needs a signature or a photo of an insurance card must be a classic form.

The example, annotated

The form below is 25 fields across seven sections, among the longest of the 55 example forms on this site, where the median is 16. It is a classic form with a welcome screen telling the patient to have their card and medication list to hand, an estimate of ten minutes, and a thank you screen asking them to arrive five minutes early.

It renders as a single scrolling page. To show one section at a time, the classic layout has a paginated mode that splits the canvas into steps with Next and Back buttons on the published form, which is worth doing at this length. There is a page on multi step forms.

Two limitations to plan around. There is no conditional logic, so a patient who ticks “None of these” still sees the follow up questions. And there is no save and resume, so the whole thing has to be finished in one sitting.

For the wording of the clinical questions, particularly the scale on “how much is it affecting your day”, the rules in how to write survey questions apply directly.