Medical Intake Form: New-Patient Template and Clinic Workflow

A medical intake form helps a clinic identify a patient, arrange communication, prepare for the visit and route information to the right team. A useful form connects each answer to a staff action. For example, “No voicemail on my shared phone” becomes a contact restriction that staff save and check in the systems used to reach that patient.

Start with the original new-patient template below. It covers adult outpatient registration, contact preferences, communication support and administrative preparation. Use the linked medical-history form for conditions, medicines, allergies and family history. Keep detailed clinical answers and staff verification separate from the patient’s registration questions.

Sources checked October 26, 2026.

Medical intake form template: print, type or copy

For patients: Use the clinic’s own new patient forms when provided. Write what you know; use unknown, not applicable or prefer to discuss privately when appropriate. Ask staff for another format or help completing it. Contact the clinical team directly about concerns needing prompt attention.

Use the two-page PDFs for handwriting or open the HTML form to type your answers. Both PDFs include heading and paragraph tags, reading order and section bookmarks. Print or save your completed HTML form before closing the tab, then return the copy using your clinic’s chosen route. Keep completed copies private.

What belongs on new patient forms?

Start with the purpose of each field. A registration form helps the clinic connect information to the correct person and organize the next step. Decide what staff need before the appointment, what can be discussed privately, and what belongs in a clinical interview.

The coverage section lets patients describe their arrangement or request help. A self-pay patient, someone with uncertain coverage and a person using a public plan need different follow-up. Add fields for the clinic’s payment process and explain what staff will use each answer for.

Use the medical history form template for past conditions, medication use, allergies, family history and relevant social history. Record the patient as the source and route the answers to the clinical team. Record medication reconciliation as a separate clinical task, with its completion status and responsible clinician.

Make contact preferences actionable

“Preferred contact: mobile” is too vague for a shared device. Ask whether calls, voicemail and appointment texts are acceptable separately. Record the destination, permitted content, restrictions and date together. A patient may accept a call but reject a voicemail that reveals the clinic’s identity. They may use a portal while sharing the email account that receives its notifications.

In the United States, HHS explains that covered providers may leave messages with reasonable safeguards and must accommodate reasonable confidential-communication requests. Record which number to use, which messages the patient accepts and any restrictions on message content. HHS guidance on messages and confidential communications

Confirm the requested arrangement with the patient and the staff who configure it. Assign any alternative-contact discussion to a named team member. Record the agreed destination, permitted content and next step alongside the review status.

Clinical messages, appointment reminders, billing statements and portal alerts may use different systems. Review each relevant destination, including any existing reminder subscription. Record the saved setting, the check performed and any remaining task so the next staff member can see exactly where the update stands.

Emergency contacts, helpers and permissions

An emergency contact is a person the patient identifies for a purpose. A helper may type answers or assist with reading. A representative may have legal authority to act for the patient. Record each role and its permissions separately, including when one person has several roles.

Under U.S. HIPAA, personal-representative status depends on applicable authority, with state law and exceptions affecting the analysis. Confirm and document that authority through the clinic’s process before creating proxy access. HHS personal-representative guidance

Record who supplied the answers. “Patient answered; partner typed” differs from “partner supplied information while patient was unavailable.” Ask the patient about sensitive contact preferences privately when appropriate. Keep unanswered preferences open and assign clarification when sources or accounts conflict.

MI-01: a completed new-patient form

Fictional example, October 26, 2026. Morgan Lee is preparing for a first adult primary-care appointment. Morgan answers the form personally. The phone is shared, and old reminder preferences exist from an earlier scheduling interaction. Morgan wants large-print instructions and plans to discuss coverage and mailing arrangements privately.

The answers below match every field in the blank form. They are requests and reports; the staff verification follows in the next section. View the completed fictional form on the same two-page layout.

Open MI-01’s completed patient form

1. About you

Full name used for your clinic record

Morgan Lee (fictional)

Date of birth (write the month in words)

14 March 1987

Name you would like us to use; pronouns if you want to share

Morgan; they/them

Who answered these questions? Who helped, if anyone?

Morgan answered; no helper.

2. How can the clinic contact you safely?

Phone number; is it shared? Best time for a call?

202-555-0147; shared phone; weekdays after 3 pm.

May we leave a voicemail? If yes, what may it say?

No voicemail. Do not leave the clinic name or appointment details.

May we send appointment texts? Which number? Any limits?

No text messages to the shared phone.

Email or portal contact preference; any limits?

Use my own portal account. No email notifications until discussed privately.

Safe mailing address, or ask staff to discuss another option

Prefer to discuss privately; do not use an old address without checking.

If we cannot reach you, what alternative should staff discuss?

Call again during the agreed time; discuss a backup route with me at check-in.

3. Communication and access

Preferred language for speaking and written information; interpreter request

English for speaking and writing; no interpreter requested.

What would help you use the form or attend? (For example: large print, reading help, step-free access)

Large-print appointment instructions.

4. People you want the clinic to know about

Emergency contact: name, relationship and phone; or discuss privately

Taylor Lee; sibling; 202-555-0182; emergency contact only.

Does someone help with forms or act for you? Name, role and what you want staff to clarify

No representative identified. Do not create portal access for Taylor from this entry.

5. Payment or coverage, when relevant

Coverage or payment arrangement: plan name, self-pay, unknown, or help requested

Coverage card to be provided privately at check-in; eligibility not yet checked.

Anything you want to discuss about billing contact or financial assistance?

Please discuss where billing communications go before using an address.

6. Visit preparation and updates

Main reason for the appointment, in your own words, or discuss privately

Establish care; discuss my health history privately with the clinical team.

Date completed; what has changed since any earlier form?

26 October 2026. Contact choices above replace my older reminder preferences.

Carry three details forward exactly: voicemail is declined, Taylor is an emergency contact only, and the coverage card is due at check-in. Each detail gives the next staff member a clear action and completion state.

Clinic workflow: from received to ready

Use statuses that describe completed work. Received means the clinic has the form. Needs clarification identifies a specific gap. Verified means a stated check has occurred. Ready means the locally defined prerequisites for the visit have been addressed, including an agreed plan for any remaining work.

MI-01 follows this sequence:

1. 09:10 — receive and match. Registration coordinator Alex matches Morgan to the intended appointment using the clinic’s identity process and records the identifiers checked. The source form and completion date are retained.
2. 09:20 — confirm contact choices. Morgan confirms the no-voicemail and no-text instructions directly and agrees to receive today’s administrative update face to face before leaving reception. The patient’s own portal is requested for later communication, but email notifications still require a private discussion. Alex holds the portal-message task until those notification settings are verified. The emergency contact remains emergency-only.
3. 09:30 — assign support and coverage work. Coordinator Priya accepts the large-print request and confirms that instructions will be available at check-in. Billing lead Casey accepts the private coverage and billing-contact discussion. No eligibility check is recorded as complete.
4. 09:40 — update and inspect destinations. Alex updates registration and checks the reminder configuration. The next section shows the problem found here and the required correction.
5. 10:15 — record the verified state. After the correction, Alex reopens both records. The no-text/no-voicemail restrictions agree. Alex explains the remaining plan to Morgan face to face before departure. The team sends no portal message, email, SMS or voicemail for this update. Portal email-alert suppression has not been verified, so portal messaging remains on hold. Alex owns notification clarification and verification at check-in; Casey owns the private mailing and billing discussion.

Set each queue’s owner, absence cover and escalation route around the clinic’s staffing and service requirements. Record who accepted outstanding work alongside the source form.

MI-02: a saved form with the wrong reminder settings

At 09:40, Alex finds that registration correctly displays no SMS, but the reminder platform still uses a previous SMS enabled value. Nothing has been sent in this fictional rehearsal. The patient form is accurate; the operational destination is wrong.

The correction stops this particular failure. Prevention also requires a reliable update path, staff training and a way to identify old queued messages. Keep a record of the cause: for example, a one-time registration import may not synchronize later changes. Test that behavior with synthetic information before connecting a live patient workflow.

If a message has already reached an unsuitable destination, route the event through the clinic’s privacy response process as well as correcting future reminders. Preserve the relevant evidence and assign follow-up.

Staff review checklist and open work

Keep this internal record separate from the patient form. It records what the team checked, the evidence and the next responsible person. A status should be supported by something inspectable: a reviewed identity match, the saved contact configuration, an accepted support task or the appropriate document reference.

For MI-01, keep two open-work entries:

• Alex, registration coordinator — discuss portal email notifications privately with Morgan at check-in, then verify the agreed settings and notification behavior before releasing the portal-message task. If the requested restriction cannot be implemented, agree another route with Morgan and record it before use.
• Casey, billing lead — confirm private mailing and billing-contact arrangements with Morgan at check-in.

The duty registration lead covers absence for either task. At check-in, review each task separately. Keep unresolved contact routes on hold and consult the privacy lead. These entries give the next team member a purpose, owner and checkpoint.

Use the EHR implementation checklist when the process crosses applications. If a new patient arrives through a referral, the referral letter workflow helps distinguish receipt of a document from acceptance of responsibility. Clinical history, registration and referral tracking can share a patient identifier without sharing the same completion state.

Test the form with the people who will use it

Use visible labels, logical groups, clear instructions and feedback that identifies the next step. W3C’s form guidance addresses these mechanics, including keyboard use and programmatic labeling. WAI forms tutorial · Labeling form controls

Test a realistic task: a patient with a shared phone requests no voicemail, no text and large-print instructions. Ask the participant to find the relevant fields, record the restrictions, correct a mistaken entry and identify what happens after completion. Observe where they hesitate rather than coaching them through every field. Use fictional information and record the form version, browser or paper size, assistance provided, problems and corrections.

For a digital deployment, check keyboard-only navigation, visible focus, labels announced by assistive technology, zoom and small-screen layout. Include screen-reader and assisted-completion sessions with intended users. For paper, check writing space at actual print size and whether long answers require an extra page.

Clinics covered by the U.S. ADA must address effective communication, considering the person’s communication method and the complexity of the interaction. A family helper should not become the default substitute for an appropriate aid or service. DOJ effective-communication guidance

Privacy and local requirements

Treat names, contact restrictions and the reason for a visit as information requiring appropriate handling. Specify who receives the form, who can read it, where it is stored and how temporary copies are removed under the clinic’s retention policy. Avoid open reception trays, shared personal inboxes and unattended printouts. Collect sensitive information privately when the general form cannot support the conversation.

United States: Separate a HIPAA notice acknowledgement from treatment consent and authorizations for particular disclosures. HHS says acknowledgement records receipt; signing it does not authorize special uses or disclosures. HHS also publishes revised February 2026 model notices. Use the applicable current notice rather than treating a generic intake signature as a substitute. HHS notice explanation · Current model notices

Ontario: PHIPA has its own collection framework. The IPC describes consent as the general rule, exceptions, and the usual requirement to collect directly from the individual. Record who provided the answers and check the authority for information obtained from another person. A U.S. HIPAA acknowledgement does not establish Ontario consent requirements. IPC collection guidance

Assign the practice manager and privacy lead to approve the clinic’s actual fields, contact rules, notices, access roles and exception routes. Adapt separately for minors, substitute decision-makers and services with additional confidentiality requirements. The useful result is a short form connected to an accountable workflow: the patient can understand the questions, staff can act on the answers, and the saved system preserves the choices that matter.

For teams reviewing technology, Vero’s patient-intake page describes its product workflow. The templates here are available without a product account.