Form Packets for Multi-Form Intake

Form packets let a practice combine multiple existing EasyDocForms forms into one patient-facing workflow. Instead of sending separate links for demographics, medical history, consent, insurance, Good Faith Exam, and specialty forms, staff can create one packet and send one link.

Packets are useful when a patient should complete a complete visit workflow, but the practice still wants to keep individual forms reusable across services.

What a Packet Does

A packet:

• Combines multiple source forms into one patient-facing form.
• Preserves the order chosen by staff.
• Can be shared with a normal share link.
• Can be attached to scheduling visit types.
• Can be mapped to Square Appointments services.
• Creates one patient submission for staff review.
• Can generate response PDFs.
• Keeps packet response context so staff can see which source forms were included.

Patients experience the packet as one intake workflow instead of a pile of separate forms.

Common Packet Examples

Workflow	Packet contents
New patient medical visit	Demographics, medical history, medication list, insurance card, consent to treat, financial responsibility.
Chiropractic new patient	Demographics, pain diagram, review of systems, accident history, consent, Medicare ABN when needed.
Med spa Botox consult	Medical history, contraindication screening, Good Faith Exam, neurotoxin consent, post-care acknowledgment.
IV therapy visit	Medical screening, medication and allergy history, IV therapy consent, Good Faith Exam, provider review workflow.
Physical therapy evaluation	Demographics, injury history, ADL assessment, imaging history, consent, insurance card capture.
Pain management consult	Pain history, body diagram, medication list, imaging history, prior procedure history, consent.

Create a Packet

From All Forms:

1. Choose Create Packet.
2. Enter the packet name, category, and description.
3. Select the source forms to include.
4. Arrange the forms in the order patients should see them.
5. Resolve duplicate question names if prompted.
6. Preview the compiled packet.
7. Save the packet.
8. Create a share link or attach the packet to scheduling or Square.

Use a clear packet title such as New Patient Chiropractic Intake Packet, Botox Consultation Packet, or IV Therapy Initial Visit Packet so staff can pick the right item later.

Source Forms and Compiled Packets

A packet is built from source forms, but it is saved as its own compiled form. That means:

• The packet can be sent like a normal form.
• Staff can see that it is a packet in form lists.
• The packet stores packet metadata, source-form order, compile information, and refresh state.
• Patient responses remain tied to the packet version submitted by the patient.

This matters because form language, consent requirements, and clinical questions can change over time. A response should remain understandable even if a source form is edited later.

Updating Source Forms

If a source form changes after a packet is created, the packet may show that updates are available. This is expected.

Use packet refresh when you want future patients to receive the latest source-form content. Refreshing a packet should be treated like publishing a new form version:

1. Review the source form changes.
2. Refresh or rebuild the packet.
3. Preview the packet.
4. Submit a test response.
5. Review the generated PDF.
6. Confirm scheduling, Square, and share-link workflows still point to the intended packet.

Existing packet responses should remain preserved with their submitted response snapshot.

Duplicate Questions

When multiple forms are combined, two source forms may contain questions with the same internal name. The packet builder can prompt staff to resolve duplicates before saving or refreshing.

Examples:

• Two forms both contain patient_name.
• A consent and intake form both ask for date_of_birth.
• Multiple sections include the same signature or acknowledgment field name.

Review duplicate warnings carefully. If two questions are truly different, rename the field in one source form before adding it to the packet.

Sending Packets

Packets use the same delivery paths as forms:

• Direct share links.
• Scheduling visit types.
• Square Appointments service mapping.
• Staff-approved email, text, QR code, or portal workflows where configured.

Patients do not need to know that a packet is made from multiple forms. Staff should use packet-specific names so they do not accidentally send an individual consent when the patient needs the full packet.

Reviewing Packet Responses

When a patient submits a packet, staff can review it in Responses, PDFs, and AI Summaries.

Packet responses can show:

• Packet title.
• Submitted patient details.
• Included source-form sections.
• Form answers.
• Signatures.
• Reviewer notes.
• PDF export actions.
• Patient profile linking when enabled.

Long packets should be tested before live use, especially if they include body diagrams, consent documents, insurance card capture, Medicare ABN fields, matrix questions, or Good Faith Exam sections.

Best Practices

• Keep reusable forms modular, then combine them into visit-specific packets.
• Avoid one giant form that every patient receives regardless of service.
• Use service-specific packets for Botox, IV therapy, injury visits, Medicare visits, new patient exams, and follow-ups.
• Test packets on mobile because many patients complete intake from a phone.
• Refresh packets intentionally after source-form updates.
• Archive old packets only after confirming share links, scheduling visit types, Square mappings, and printed QR codes no longer use them.

Related Pages

• Create and Manage Healthcare Forms
• Share Links and Patient Form Delivery
• Scheduling and Appointment-Linked Intake
• Square Appointments Patient Intake Integration
• Responses, PDFs, and AI Summaries
• Good Faith Exam Forms