Is an electronic signature valid on this form?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are legally valid when intent, consent, attribution, and record retention are satisfied.

Do I need a HIPAA BAA attached?

Yes. If the BSP will create, receive, maintain, or transmit PHI, a Business Associate Agreement is required under HIPAA; document breach notification timelines and responsibilities explicitly.

When is notarization required?

Notarization is uncommon for BSP agreements but may be required for related powers or sworn affidavits; check state rules and specific contract clauses before notarizing.

Can I use remote online notarization (RON)?

Possibly. RON availability and requirements vary by state; verify the state's RON status and applicable identity-proofing and recording requirements before proceeding.

What if a signer’s name differs from legal records?

Mismatched signer names can raise enforceability issues. Use the signer's full legal name as used on corporate filings or government ID and include title/role to show authority.

How do I correct mistakes after signing?

Use an amendment or replacement agreement; do not alter an executed original. Document the change, obtain signatures from all original parties, and retain both versions for audit.

Healthcare BSP Form

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

Healthcare BSP Form

I. Patient Information

Patient Name Date of Birth Gender Address Primary Phone Emergency Contact (Name, Relationship, Phone)

II. Insurance Information

Insurance Provider Policy Number Group Number Subscriber Name

III. Relevant Medical History

Current Medications (include dosage and schedule) Allergies and Adverse Reactions Prior Surgeries / Hospitalizations Chronic Medical or Psychiatric Conditions

IV. Referral, Assessment & Diagnosis

Reason for Referral / Presenting Concerns Current Diagnoses (DSM/ICD if available) Assessment Summary

V. Behavior Support Plan Details

Target Behaviors (operational definitions) Antecedent Triggers Consequences / Maintaining Events Replacement / Teaching Strategies Preventive Environmental Strategies De-escalation Techniques and Non-Restrictive Interventions Emergency Interventions (when behavior poses imminent risk) Medication Management Relevant to Behavior Plan

VI. Goals, Data Collection & Staffing

Short-term Goals (measurable) Long-term Goals Data Collection Methods Monitoring Frequency Primary Responsible Staff / Roles Staff Training Requirements

VII. Legal Acknowledgments, Consent & HIPAA

By signing below, the patient or legal guardian authorizes the implementation of the Behavior Support Plan (BSP) as described herein. The undersigned acknowledges that the BSP has been explained, that less restrictive alternatives were considered, and that emergency interventions will be used only when specified criteria are met. The undersigned understands that they have the right to withdraw consent at any time and to request review or modification of the BSP. The facility and providers retain the obligation to act in the patient’s best medical interest and to comply with applicable standards of care.

The undersigned consents to systematic data collection for purposes of monitoring treatment effectiveness and safety, and authorizes necessary communications among treatment team members. Information disclosed under this authorization may be documented in the medical record. This authorization does not waive any statutory privacy rights; disclosures will be made in accordance with applicable privacy laws.

Authorization Expiration Date

HIPAA Privacy Acknowledgment: I acknowledge that I have been informed of my privacy rights with respect to protected health information and that this BSP will be maintained in the clinical record. I understand who will have access to information about my care as necessary to implement this plan.

Acknowledgment I acknowledge reading and understand the HIPAA Privacy Acknowledgment and the terms of the BSP. Additional Notes / Caregiver Instructions

VIII. Review & Plan Revision

This BSP will be reviewed at the intervals specified above, or sooner if there is a significant change in behavior, health status, or medication. Any restrictive procedures not explicitly described in this plan are prohibited. Revisions require clinical justification and documentation.

Next Review Date

IX. Signature and Certification

Certification: I certify that I have received an explanation of the Behavior Support Plan, that my questions have been answered, and that I voluntarily consent to implementation of the BSP as set forth above. I understand I may withdraw consent in writing and request a clinical review.

Patient / Guardian Name:

Signature:

Relationship (if not patient):

Date:

What the Healthcare BSP Form Is and when it’s used

The Healthcare BSP Form documents an agreement between a covered entity and a business service provider (BSP) that will perform administrative or operational functions—such as billing, claims processing, eligibility checks, or IT services—on behalf of a healthcare provider. The form records the provider and vendor identities, defines permitted uses of protected health information, sets data access and retention terms, and documents responsibilities for compliance with applicable privacy and security laws. It is typically used before a BSP is granted electronic access to patient data or systems and when vendor responsibilities change.

Why completing a Healthcare BSP Form matters

A properly completed Healthcare BSP Form clarifies roles, reduces privacy risk, and establishes compliance expectations under HIPAA. It ensures all parties document permitted uses, security controls, data return or destruction procedures, and liability allocation.

Who typically completes and signs this form

Typical completing parties include people who oversee vendor relationships and data access at the provider organization.

Health system compliance officer or privacy officer responsible for HIPAA oversight and contract acceptance.
Revenue cycle manager or billing director who authorizes claim processing and payment workflows.
Vendor account manager or contract signatory who accepts operational terms and security obligations.

After internal sign-off, authorized signers from both the covered entity and the BSP must sign and retain copies for audit and retention purposes.

Primary signatories and their roles

Provider Signatory

Chief Privacy Officer or designated executive. Authorizes BSP access to PHI and confirms organizational safeguards; must be able to bind the covered entity contractually.

BSP Signatory

Vendor CEO or authorized contract representative. Accepts responsibilities for safeguarding PHI, breach notification, subcontractor oversight, and return/destruction of records.

Key compliance and security items to include

Data encryption: TLS 1.2/1.3 in transit; AES-256 at rest

HIPAA BAA: Business associate agreement required

Audit trail: Detailed logs of access and activity

Access controls: Role-based access and MFA

Retention policy: Documented retention and destruction timelines

Subcontractors: Flow-down obligations to subcontractors

Consequences of incomplete or incorrect forms

HIPAA civil penalties: Monetary fines and corrective action

Breach liability: Third-party claims and remediation costs

Regulatory scrutiny: OCR investigations and audits

Operational disruption: Revoked system access and downtime

Contract disputes: Indemnity and litigation exposure

Data loss risk: Potential patient harm and reputational loss

Common preparation pitfalls to avoid

Leaving access scopes vague — failing to list specific systems, databases, or APIs a BSP may access creates operational ambiguity and increases risk.
Omitting audit and logging requirements — not specifying required logs, retention periods, or log review processes impairs breach detection and evidence preservation.
Neglecting subcontractor obligations — failing to require the BSP to flow down safeguards to subcontractors can create unmonitored exposure.
Skipping signature authority checks — accepting a signature from an unauthorized person or mismatched legal name can render the agreement unenforceable.

Step-by-step: filling out the Healthcare BSP Form

Follow these sequential steps to complete the form accurately before granting vendors electronic access or starting work.

01

Identify parties: Enter full legal names and contact details for both covered entity and BSP.
02

Define services: List exact services, systems, and data elements the BSP will access.
03

Set controls: Specify security measures, audit logs, and incident reporting obligations.
04

Sign and retain: Obtain authorized signatures and store executed copies per retention rules.

Configuring electronic workflows and authentication

Configure eSubmission settings to match security and routing requirements before sending the form for signature or onboarding.

Field	Configuration
Authentication level	Email link or SMS code; use stronger MFA for PHI access
Document format	PDF/A or signed PDF for long-term retention
Access expiry	Set link expiration and signable window
Audit settings	Enable IP, timestamp, and action logging

Typical eSubmission flow for the Healthcare BSP Form

Electronic submission follows a standard sequence from upload to audit; configure each step to match your compliance needs.

Upload document: Sender uploads the completed form to the eSignature platform.
Place fields: Sender applies signature, initial, and date fields, plus required attachments.
Authenticate signer: Platform verifies signer via email, SMS code, or stronger methods as configured.
Audit record: Signed copy plus audit trail (IP, timestamp, email) is stored for retention.

Delivery options and integration considerations

Choose a delivery method that preserves auditability and meets HIPAA requirements, and integrate with your systems where practical.

Email links: Low friction; acceptable with proper authentication and audit logs
Embedded signing: Sign within an EMR portal or vendor portal for smoother workflows
API integrations: Integrate with EHR/PM systems (HL7/FHIR connectors) or with CRM/ERP for automated onboarding

eSignature vendor pricing and capability snapshot

This vendor comparison highlights starting prices and core capabilities relevant to executing Healthcare BSP Forms; signNow is listed first per vendor ordering rules.

	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	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
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

Practical tips for accurate and efficient completion

Apply consistent practices to reduce rework and streamline vendor onboarding while protecting sensitive data.

Use standardized templates

Maintain a single approved BSP template to ensure consistent BAA language, assignment of liabilities, and security requirements across vendor relationships.

Limit access by role and purpose

Grant the minimum data access required for the vendor to perform its service and document permitted activities in the Services Description field.

Require evidence of controls

Request SOC 2 or ISO 27001 reports, and document acceptance criteria for encryption, logging, and incident response.

Track renewals and expirations

Record effective and termination dates and automate reminders for renewals, revalidations, or contract transitions to avoid lapse in controls.

Real-world examples of BSP form use

These concise examples illustrate how organizations used e-signed BSP forms to document vendor responsibilities and speed onboarding.

Fertility Centers of Illinois

The clinic needed a standardized vendor agreement for multiple partners to handle scheduling and claims

Implemented a single BSP template for all vendors
John Butler, Founder, praised the responsive support and API capabilities that simplified integrations and compliance with audit trails and BAAs.

Optica Ventures LLC

A small provider network required fast onboarding for a billing vendor to avoid revenue delays

Adopted digital BSP forms to eliminate mail and scanning steps
Brian Fitzgibbons, COO, emphasized that the simple interface helped both staff and customers complete forms quickly and accurately.

Frequently asked questions and troubleshooting

Answers to common questions about validity, signatures, and compliance when completing or submitting a Healthcare BSP Form electronically.

Need help? Contact support

Is an electronic signature valid on this form?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are legally valid when intent, consent, attribution, and record retention are satisfied.
Do I need a HIPAA BAA attached?
Yes. If the BSP will create, receive, maintain, or transmit PHI, a Business Associate Agreement is required under HIPAA; document breach notification timelines and responsibilities explicitly.
When is notarization required?
Notarization is uncommon for BSP agreements but may be required for related powers or sworn affidavits; check state rules and specific contract clauses before notarizing.
Can I use remote online notarization (RON)?
Possibly. RON availability and requirements vary by state; verify the state's RON status and applicable identity-proofing and recording requirements before proceeding.
What if a signer’s name differs from legal records?
Mismatched signer names can raise enforceability issues. Use the signer's full legal name as used on corporate filings or government ID and include title/role to show authority.
How do I correct mistakes after signing?
Use an amendment or replacement agreement; do not alter an executed original. Document the change, obtain signatures from all original parties, and retain both versions for audit.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now