
A practical Sign.Plus guide for US front-desk leads covering intake PDFs, individual signature requests, delivery follow-up, status tracking, HIPAA setup, and clinic-managed filing.
Electronic patient intake forms are digital documents a clinic uses to gather information before a visit and, when its process requires it, obtain a patient's signature or acknowledgment. Registration pages may collect contact and billing details, while health-history pages collect information the clinic has chosen to request. A separate consent or acknowledgment page may contain signature and date lines. These intake and consent use cases show why it helps to distinguish information collection from signing. Not every intake page needs a signature.
For example, a family practice has a new patient scheduled for Thursday. On Tuesday morning, the front-desk lead has one packet containing registration and health-history pages, followed by an acknowledgment page with signature and date lines. The lead also has the patient's verified email address. The immediate task is to send that packet for signature before the visit, know what to do if the invitation remains unopened, and check the completed PDF before the clinic files it. This guide covers only that signature-request workflow. The clinic decides what information to collect and which pages require signing, and its staff handle filing.
Begin with the document the clinic has already cleared for use. A short preflight catches packet and recipient problems before fields are placed.
Use the documented sequence without skipping the final review.
An unopened invitation calls for a delivery check, not an assumption that the patient declined or finished the paperwork.

For US covered entities, this workflow may involve electronic protected health information, or ePHI. HHS cloud-computing guidance explains that covered entities and business associates using a cloud provider to handle ePHI on their behalf need a compliant Business Associate Agreement, or BAA, and must otherwise comply with the HIPAA Rules. The Sign.Plus HIPAA-compliant setup is described as requiring an Enterprise plan, Advanced Security Controls enabled, and a signed BAA. Before using the workflow for ePHI, the clinic should confirm those elements and apply its own access, workforce, and record-handling procedures. A BAA and product configuration do not replace the clinic's broader compliance responsibilities.
Next action: For the next visit on the schedule, take the current intake PDF and make a three-line checklist: version and required fields, verified individual email address, and the staff handoff for the downloaded PDF. Use it during Review, then use it again when checking the completed document before filing.
They are digital documents used to gather intake information and, when the clinic requires it, obtain signatures or acknowledgments. Examples include registration pages, health-history forms, and consent or acknowledgment pages. Information-collection pages do not automatically need signature fields.
The clinic prepares the form first. It checks the current content, page order, instructions, and signature lines, then combines pages into one PDF if that is its packet process. For sending, upload that existing PDF in Sign.Plus, choose Request Signature, and add e-signature fields such as patient signature and date. Field placement comes after document preparation, not instead of it.
No. Recipients can sign from their individual email invitation without creating a Sign.Plus account. Verify the address before sending. If the request stays unopened, check Pending, confirm the address, and ask the patient to check spam or junk folders using the clinic's usual contact route. Resolve delivery before creating another invitation.
Under Documents, open Pending to see recipient status such as opened, viewed or signed. A signed status is a workflow signal, not a final document check. Staff still download the completed PDF, confirm that it is the intended packet, and review the expected signature and date entries before filing it. Documents, More, Audit Trail provides the available activity record.
HHS explains that covered entities and business associates using a cloud provider to handle ePHI on their behalf need a compliant BAA and must otherwise comply with the HIPAA Rules. Sign.Plus describes its setup as requiring Enterprise, Advanced Security Controls enabled, and a signed BAA. The clinic should confirm those elements and apply its own HIPAA procedures before using the workflow for ePHI.