Can this be signed electronically?

Yes in most cases. The ESIGN Act (15 U.S.C. §7001) and state UETA laws recognize electronic signatures if intent, consent, attribution, and retention are met; confirm payer acceptance and any required consumer disclosures.

Is a BAA required for e-submission?

If the release contains PHI and a third-party platform will store or transmit it, a HIPAA Business Associate Agreement (BAA) is required to document permitted uses and safeguards.

Do payers ever require notarization?

Some payers or states require notarized or witnessed releases while others accept electronic signatures. Check payer policy and applicable state rules before choosing notarization.

What happens after I revoke a release?

Revocation stops future disclosures but does not retroactively reclaim information already obtained under a valid release; include revocation instructions on the form.

How long should I retain signed releases?

Follow HIPAA and federal standards: keep for at least 6 years from creation (45 CFR §164.530(j)) and follow IRS or state retention where relevant.

Who can sign on behalf of a provider?

An authorized agent with documented authority may sign; include agent name, relationship, and attach proof of authorization to prevent acceptance issues.

Electronic Signature
Templates
Healthcare
Healthcare CAQH Release Form

Healthcare CAQH Release Form

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

HEALTHCARE CAQH RELEASE FORM

I hereby authorize the release of my protected health information to CAQH and its participating health plans, credentialing agents, and affiliated organizations for the purpose of provider data verification and credentialing as described below. This authorization permits disclosure of the specified information to support credentialing, payer enrollment, benefits coordination, and related administrative activities.

Patient Information

Full Legal Name

Date of Birth: Gender:

Address

Primary Phone

Email

Emergency Contact

Name Phone

Insurance Information

Primary Insurance Provider

Policy / ID Number

Group Number

Subscriber Name

Purpose and Scope of Authorization

Purpose of disclosure (check all that apply): Credentialing / Provider Data Verification Billing / Claims Processing Care Coordination Other:

Information To Be Released

The following categories of information may be released unless specifically excluded by my initials below:

Entire medical record (including history, diagnoses, treatment notes, billing).
Treatment records, progress notes, and clinical summaries.
Billing, claims and insurance information.
Laboratory and test results.

Sensitive information release (initial next to each to authorize release of that specific category):

Mental health/psychotherapy notes: Initials: Substance use treatment records: Initials: HIV/AIDS-related information: Initials:

Other specific information to be released (if applicable)

Expiration and Revocation

This authorization will expire on: . If no date is provided, this authorization will expire one year from the date signed below.

I understand that I may revoke this authorization at any time by submitting a written revocation to the releasing provider. Revocation will not apply to actions already taken in reliance on this authorization prior to receipt of the revocation.

Redisclosure & Legal Notices

I understand that information disclosed pursuant to this authorization may be subject to redisclosure by the recipient and, if so, may no longer be protected by applicable federal privacy regulations. This authorization is voluntary and is not a condition of eligibility for treatment, payment, enrollment, or benefits.

I further acknowledge that I have read and understand this form and that the information provided is accurate to the best of my knowledge.

HIPAA Acknowledgment

I acknowledge that I have been informed of my rights under HIPAA and that this authorization conforms to applicable privacy law.

Certification

By signing below I certify that I am the patient or am authorized to act on behalf of the patient as the patient's personal representative. I understand that signing this form authorizes disclosure of protected health information as described herein.

Print Name:

Relationship to patient (if not self):

Signature:

Date:

If signed by representative, print representative name:

Definition and scope of the Healthcare CAQH Release Form

The Healthcare CAQH Release Form is a written authorization used by providers and their delegates to permit release of credentialing, billing, or protected health information to CAQH ProView and participating payers. It documents consent, identifies the requester, and specifies the scope and duration of release for verification and network enrollment. In many workflows the form supports electronic completion and signing; whether the form meets signature and authentication requirements depends on the receiving payer and applicable state or federal rules.

Why a clear CAQH release matters for credentialing and compliance

A properly completed CAQH release expedites credentialing, reduces duplicate requests, and creates an auditable record of patient or provider consent. For healthcare records it must align with HIPAA privacy rules and esignature laws such as the ESIGN Act and UETA to ensure legal validity.

Who commonly completes or relies on the Healthcare CAQH Release Form

Common users include providers, credentialing staff, and payers; each role has different needs for the release form and supporting documentation.

Providers and clinicians — Complete personal and professional identifiers and grant permission for credential verification by payers and third parties.
Credentialing teams — Use the release to collect attestations and source documents needed for enrollment and recredentialing.
Payers and delegated vendors — Rely on the release to obtain licensure, malpractice, work history, and practice location verification.

Accurate completion by the party named in the release reduces processing delays and helps avoid rework during payer credentialing or network enrollment.

Essential sections found in a professional CAQH release

A complete CAQH release groups identification, scope, duration, authorization language, signature, and acknowledgment fields so verifiers and payers can quickly confirm consent and reproduce the record.

Provider ID

National Provider Identifier (NPI) and professional license numbers with issuing state and license expiration to enable precise identity matching during credentialing checks.

Personal Details

Full legal name, date of birth, and business and home addresses used to correlate records across payers and state licensing boards.

Scope of Release

Clear list of the records and sources to be accessed, for example licensure, malpractice claims, work history, and sanctions databases.

Effective Period

Start and end dates for the release or an explicit statement that consent remains valid until revoked, which affects how long third parties may query records.

Signature Block

Designated signature and date fields for the subject or authorized representative; must include printed name and relationship if signed by an agent.

Acknowledgment

Optional witness or notary area and a checkbox for HIPAA authorization language and revocation instructions to satisfy payer or legal requirements.

Step-by-step: filling and submitting the CAQH release

Follow this sequential checklist to prepare a complete, verifiable release before sending to CAQH or a payer.

01

Gather IDs: Collect government ID, NPI, and license documents.
02

Complete fields: Enter names, addresses, and DOB exactly.
03

Authorize scope: Specify records and duration in clear language.
04

Sign and deliver: Sign, date, and route via secure method.

Configuring an online CAQH release workflow

These settings match typical payer and credentialing workflows when building an online form or template.

Field	Configuration
Authentication	Email link or SMS code for signer validation
Field Types	Text, date, checkbox, and signature fields
Conditional Logic	Show additional fields when agent signs
Notifications	Automated alerts to credentialing and payer contacts

Where the completed release is routed and used

After signing, the release is routed to CAQH ProView, payer credentialing teams, or stored in an EHR or HR credentialing system depending on the workflow.

CAQH ProView: Upload to the provider's CAQH profile for centralized access
Payer Portals: Submit directly to a payer's credentialing intake system
EHR or HR Systems: Archive a copy in the provider record for audits
Secure Archive: Store signed PDF with audit trail for compliance

Technical constraints for secure electronic completion

Choose a platform that supports secure storage, audit trails, and the authentication level required by the payer or state law.

File Formats: PDF and DOCX are commonly accepted
Integrations: API or connectors to EHRs and CAQH
Authentication: Email, SMS, or stronger methods

Confirm payer acceptance of electronic signatures and any BAA requirements before relying on an online process for HIPAA-covered transactions.

Security and compliance features to verify

Encryption: TLS 1.2/1.3 in transit

Data at Rest: AES-256 encryption

Audit Trail: Timestamp, IP, and action log

HIPAA Support: BAA available for PHI handling

Certifications: SOC 2 Type II and ISO 27001

Accessibility: WCAG 2.0 Level AA compliance

Key risks and potential consequences of errors

Invalid Consent: Release rejected by payer

HIPAA Violation: Potential civil penalties

Credentialing Delay: Network enrollment postponed

Claim Denial: Payments withheld or rejected

Backup Withholding: Tax withholding may apply

State Sanctions: Fines or disciplinary action

Common preparation mistakes to avoid

Entering a nickname or abbreviated name instead of the full legal name often causes verification mismatches and triggers rework from payers or CAQH.
Leaving the scope vague—using phrases like 'all records' without specifying licensure or employment history—can lead to partial responses or request denials.
Missing or expired license numbers and dates are frequent reasons for rejected submissions and slow credentialing timelines across networks.
Failing to confirm whether the payer requires a notarized or witnessed signature before submitting can result in resubmission delays or non-acceptance.

Typical timing and processing expectations

Processing times and deadlines vary by payer; understanding common timeframes helps set expectations and avoid credentialing gaps.

Response Time Frame:

Payers often process credentialing in 30–90 days

Verification Cycle:

Primary source verifications may take 7–21 days

Recredentialing Period:

Typically occurs every 2–3 years per payer policy

Signature Validity:

Effective period defined on the release controls queries

Retention Trigger:

Retention obligations begin at form execution

Key milestones in the credentialing lifecycle

Track these sequential milestones to monitor status from submission to final network onboarding.

01

Form Completion

Prepare and obtain all required signatures and identifiers

02

Submission to CAQH

Upload release and supporting documents to CAQH ProView

03

Payer Verification

Payer or delegate performs primary source checks

04

Final Determination

Payer issues network approval or requests follow-up

eSignature pricing comparison for CAQH release workflows (vendor overview)

Compare common eSignature vendor price points and capabilities relevant to healthcare releases; confirm HIPAA and BAA availability with each vendor before committing.

	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 plan	Varies by plan	Varies by plan	Varies by plan
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 limit	Varies by plan	Varies by plan	Varies by plan

Two practical examples of CAQH release usage

Representative use cases illustrate how a completed release moves through credentialing and payer onboarding processes.

Multi-Specialty Clinic

A clinic collects standardized releases from 120 providers to populate CAQH ProView

Bulk uploads reduce duplicate requests by centralizing records
As a result the clinic shortened average credentialing cycles and reduced staff follow-ups for missing IDs.

Regional Health System

A health system requires signed releases for each clinician during payer recredentialing

Payers accepted electronic signatures with a BAA and SMS authentication
The system documented a measurable decline in paper handling and fewer delayed credential renewals.

Practical tips for accurate and efficient completion

Implement these practices to reduce rejection rates, speed processing, and maintain compliance with payers and regulators.

Standardize templates

Use a controlled template with required fields and explanations to reduce variability and avoid omitted critical data that triggers payer rejections.

Validate data

Confirm NPI, license numbers, and name spelling against licensing board databases before submission to prevent verification mismatches.

Confirm acceptance

Verify with each payer whether electronic signatures and BAAs satisfy their policies to avoid later non-acceptance.

Keep audit logs

Retain timestamps, IP, and signer authentication records to support compliance, disputes, or audits.

Frequently asked questions about the Healthcare CAQH Release Form

Answers to common questions about signature validity, HIPAA, notarization, and electronic submission for CAQH and payer processes.

Need help? Contact support

Can this be signed electronically?
Yes in most cases. The ESIGN Act (15 U.S.C. §7001) and state UETA laws recognize electronic signatures if intent, consent, attribution, and retention are met; confirm payer acceptance and any required consumer disclosures.
Is a BAA required for e-submission?
If the release contains PHI and a third-party platform will store or transmit it, a HIPAA Business Associate Agreement (BAA) is required to document permitted uses and safeguards.
Do payers ever require notarization?
Some payers or states require notarized or witnessed releases while others accept electronic signatures. Check payer policy and applicable state rules before choosing notarization.
What happens after I revoke a release?
Revocation stops future disclosures but does not retroactively reclaim information already obtained under a valid release; include revocation instructions on the form.
How long should I retain signed releases?
Follow HIPAA and federal standards: keep for at least 6 years from creation (45 CFR §164.530(j)) and follow IRS or state retention where relevant.
Who can sign on behalf of a provider?
An authorized agent with documented authority may sign; include agent name, relationship, and attach proof of authorization to prevent acceptance issues.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now