How do I validate patient identity?

Confirm full legal name, MRN, and DOB. Cross-check against the EHR and use two matching identifiers to avoid misdirected moves or duplicate records.

Can the form be signed electronically under U.S. law?

Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention requirements are met.

Are HIPAA-covered records allowed to use e-signatures?

Yes, provided the eSignature platform supports HIPAA protections and a Business Associate Agreement is in place; retain audit logs consistent with 45 CFR §164.530(j).

What if the MRN is wrong on a submitted form?

Do not process the move. Return to requester for correction and re-authorization; correcting after transfer increases risk of duplicate records and billing errors.

Is notarization ever required for a move form?

Most encounter moves do not require notarization, but state or internal policies may require notarized attestations for certain legal or forensic transfers.

How long must I keep completed move forms?

Retain completed forms and their audit logs at least as long as HIPAA requires—6 years from creation or last effective date (45 CFR §164.530(j))—and longer if state law or litigation holds apply.

Electronic Signature
Templates
Healthcare
Healthcare Encounter Move Form

Healthcare Encounter Move Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

HEALTHCARE ENCOUNTER MOVE FORM

Patient Information

Patient Full Legal Name

Date of Birth:

Gender:

MRN / Patient ID:

Address

Primary Phone

Email

Emergency Contact (Name and Relationship) Emergency Contact Phone

Insurance Information

Primary Insurance Provider

Policy Number

Group Number

Subscriber Name (if different)

Original Encounter Details

Original Encounter Date:

Original Encounter ID:

Original Location / Facility Attending Provider Department / Unit Clinical Reason for Encounter Move

Destination Encounter Details

Destination Facility / Location

Destination Department / Unit

Destination Provider

Proposed New Encounter Date:

Expected Billing / Administrative Impact

Administrative Actions Required (select all that apply) Potential billing adjustment required Clinical documentation transfer required Prior authorization / payer review required

Describe required adjustments or actions

Authorization and Legal Acknowledgment

I authorize the transfer and reassignment of the above-listed encounter, including all associated clinical documentation, orders, diagnostic results, and billing information, to the destination specified. I understand that transfer of the encounter may result in changes to coding, billing, or payer responsibility and that the facility will take reasonable steps to preserve the integrity of the medical record.

I understand that sensitive health information, including but not limited to behavioral health, substance use treatment, and HIV-related information, may be included in the transferred record. I specifically authorize transfer of sensitive information where necessary for continued treatment or administrative processing.

Include sensitive information: HIV-related information Behavioral health / psychotherapy notes Substance use disorder treatment records

I acknowledge that I may revoke this authorization in writing at any time, except to the extent that action has already been taken pursuant to this authorization. This authorization will expire on the date below or one year from the signature date if no expiration date is provided.

Authorization Expiration Date

Revocation Recipient

Requester / Staff Verification

Requesting Staff Name

Department

Staff Contact Phone

Staff Verification Date:

Certification by Patient / Authorized Representative

By signing below I certify that I am the patient or the patient’s authorized representative, that the information provided on this form is true and correct to the best of my knowledge, and that I authorize the actions described in this form. I acknowledge that the receiving facility or department will use the transferred information for treatment, payment, and healthcare operations as permitted by law.

Patient Name:

Signature:

Date:

If signed by representative, print name:

Relationship to patient:

What the Healthcare Encounter Move Form Is

The Healthcare Encounter Move Form documents the authorized transfer or relocation of a patient encounter record between systems, providers, or care locations. It records identifying data, the encounter date and location, reason for move, and authorizations required to shift an encounter entry within an electronic health record (EHR) or between EHR systems. The form helps maintain clinical continuity, provides an audit trail for changes to encounter metadata, and establishes who authorized the transfer and why. It is used in clinical workflows, record-keeping audits, and system migrations where provenance of encounter data matters.

Why the Form Matters for Clinical and Compliance Workflows

The Healthcare Encounter Move Form preserves clinical integrity and legal defensibility when encounter records change location or ownership. It clarifies authorization, documents the reason for a move, and supports HIPAA-compliant recordkeeping by creating an auditable record of the action.

Who Typically Completes or Signs This Form

Common users include clinical staff, health information managers, and records administrators responsible for record movement and correction.

Clinical staff and clinicians responsible for treatment and encounter accuracy, confirming why an encounter needs moving and verifying clinical details.
Health information management (HIM) and release-of-information teams who manage EHR migrations, reconcile encounter metadata, and maintain audit trails.
IT and EHR administrators who execute system-level transfers and ensure the receiving system maps encounter metadata correctly.

Signers should have documented authority to change records; the form identifies signatory role and contact details for follow-up and audit purposes.

Step-by-Step: Completing the Healthcare Encounter Move Form

Follow these steps in order to document and complete an encounter move that maintains compliance and clinical continuity.

01

Verify Identity: Confirm patient identity via MRN and DOB before proceeding.
02

Record Details: Enter encounter date, original and new locations, and a clear reason for move.
03

Obtain Authorization: Collect signature from authorized clinician or HIM staff with role noted.
04

Execute Transfer: IT performs the system move and retains audit trail documentation.

How to Configure an Online Move Form Workflow

Set up fields and routing so the move request flows automatically from requestor to approver to IT, preserving audit information and attachments.

Field	Configuration
Recipient Authentication	Require role-based email or SSO and optional SMS code for approvers
Conditional Fields	Show supporting fields only when 'Other' reason is selected
Notifications	Auto-notify requester, approver, and IT on each status change
API Access	Enable webhook to trigger EHR transfer job after approval

Typical Routing and Submission Flow

A clear routing sequence reduces processing time and ensures each party receives only the actions they need to take.

Submit Request: Requester completes the form and attaches supporting notes
Approver Review: Designated clinician or HIM reviewer validates the request
IT Execution: IT runs the transfer and updates metadata
Audit Completed: System records timestamps, user IDs, and change history

Technical Requirements for eSubmission and Signing

Choose a platform that supports secure signing, audit trails, and integrations with your EHR or document repository.

Authentication Options: Email, SSO, SMS codes
File Formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace

Verify HIPAA support (BAA), audit logging, and API/webhook capabilities before enabling automated transfers to downstream systems.

Mandatory Data Elements to Include on the Form

Patient Name: Full legal name

Medical Record Number: Unique MRN

Encounter Date: MM/DD/YYYY

Original Location: Facility and unit

Receiving Location: Facility and unit

Authorizing Signer: Name and role

Key Penalties and Risks to Watch

HIPAA Breach: Civil/criminal penalties

Patient Harm: Clinical misdiagnosis risk

Record Corruption: Data integrity loss

Regulatory Audit: Fines, corrective action

Unauthorized Access: Privacy violation

Operational Delay: Care coordination impact

Common Errors to Avoid When Preparing the Form

Submitting a move without matching MRN and DOB can create duplicate records and requires time-intensive reconciliation by HIM staff.
Using vague reason codes such as 'adjustment' without explanatory notes often leads to request denials or follow-up inquiries.
Failing to record the authorizing clinician's role and contact details prevents timely validation and delays transfer execution.
Not attaching supporting documentation (audit logs, migration mapping) increases the risk of data mismatch and complicates downstream reconciliation.

Typical Deadlines and Processing Expectations

Expect different processing timelines depending on organizational policy and whether the move involves cross-system migration or simple metadata correction.

Initial Acknowledgment:

24–48 business hours to confirm receipt and assign owner

Clinical Approval Window:

Up to 5 business days for clinician or HIM approval

IT Execution Time:

7–14 business days for migration or mapping tasks

HIPAA Access Response:

Patient access requests must be fulfilled within 30 days per HIPAA rules

Record Retention Start:

Retention clock begins on action date or document creation

Real-World Examples of Encounter Move Use

The following condensed examples show how organizations document and justify encounter moves in practice.

Case Study: Fertility Centers of Illinois

A clinic corrected duplicate encounters after an EHR merge, documenting all changes and authorizations.

The HIM team used the move form to attach audit evidence.
Complete records and clear authorization resolved payer questions and preserved clinical continuity during subsequent fertility treatments.

Case Study: Martin Properties

A workplace clinic transferred an encounter after a facility relocation, noting new location and clinician assignment.

IT used the form to map identifiers between systems.
The structured form and signatory details avoided misplaced encounters and ensured billing and follow-up care continued uninterrupted.

Comparing eSignature Vendors for Healthcare Encounter Move Workflows

Key vendor features and price starting points relevant to secure healthcare workflows and HIPAA requirements. Confirm plan details with each vendor for your use case.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Available	Available	Available	Available
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

FAQs and Troubleshooting for Encounter Move Forms

Answers to common operational, legal, and technical questions about preparing, signing, and processing encounter move requests.

Need help? Contact support

How do I validate patient identity?
Confirm full legal name, MRN, and DOB. Cross-check against the EHR and use two matching identifiers to avoid misdirected moves or duplicate records.
Can the form be signed electronically under U.S. law?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention requirements are met.
Are HIPAA-covered records allowed to use e-signatures?
Yes, provided the eSignature platform supports HIPAA protections and a Business Associate Agreement is in place; retain audit logs consistent with 45 CFR §164.530(j).
What if the MRN is wrong on a submitted form?
Do not process the move. Return to requester for correction and re-authorization; correcting after transfer increases risk of duplicate records and billing errors.
Is notarization ever required for a move form?
Most encounter moves do not require notarization, but state or internal policies may require notarized attestations for certain legal or forensic transfers.
How long must I keep completed move forms?
Retain completed forms and their audit logs at least as long as HIPAA requires—6 years from creation or last effective date (45 CFR §164.530(j))—and longer if state law or litigation holds apply.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now