Application For Additional Provider Number For Allied Health Professional

Use a Application For Additional Provider Number For Allied Health Professional 2016 template to make your document workflow more streamlined.

About the additional provider number application

The Application For Additional Provider Number For Allied Health Professional is a credentialing record used when an allied health professional needs an additional provider identifier for a specified practice, location, payer, or service arrangement. The applicant supplies identifying, licensing, practice, and authorization information required by the receiving organization. The form’s exact fields and submission authority depend on the issuing payer or program, so confirm instructions before signing. signNow can convert the paper workflow into an electronic sequence: upload the application, detect or place fields, route signatures, and retain the completed record with an audit trail.

Allied health professionals

Allied health professionals use the application to request an additional provider number connected with a practice, service location, payer relationship, or organizational affiliation. They should verify license details, tax information, practice addresses, and authorized signatures against the receiving program’s instructions before submission.

Credentialing teams

Credentialing and payer-enrollment teams use the application to collect provider information, coordinate signatures, and preserve a complete submission record. signNow supports reusable templates, signer routing, and audit trails for applications requiring review by clinicians, administrators, or practice owners.

Business types using the application

The application serves allied health professionals and healthcare organizations managing additional provider identifiers across practices, locations, and payer relationships.

Solo allied health practices can prepare an additional provider number application, route it to the professional for signature, and retain the signed record without coordinating paper exchanges across office locations.
Multi-location therapy groups can reuse a controlled application template while assigning location-specific provider, practice, and authorized representative fields before sending each submission for review.
Enterprise healthcare organizations can connect credentialing workflows with role-based signers, audit trails, and records management controls, helping separate preparation, approval, signature, and archival responsibilities.

Complete the provider number application

Use this sequence to prepare the additional provider number application, route it to the required signers, and preserve the completed record.

Upload form:
Upload the provider number application PDF.
Check fields:
Review detected fields and add missing entries.
Add signers:
Assign provider and authorized representative signers.
Send application:
Send the completed application for electronic signature.
Store records:
Download the signed application and audit trail.

Use the signNow web app when credentialing staff prepare the application, verify fields, assign recipients, and monitor completion from a desktop workflow.
Use the signNow mobile app when an allied health professional reviews and signs the application away from the office using an iOS or Android device.
Use kiosk mode when a supervised staff member and provider complete the application together on one managed device; Business Premium includes kiosk mode.
Use a shareable signing link when an approved application template must be made available to an identified provider group without sending individual email invitations.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Authenticate signer:

Records signer email, authentication method, and verification event.

Capture timestamps:

Adds an exact date and time to each action.

Hash document:

Associates the completed application with an integrity hash.

Seal record:

Locks the signed record against unnoticed content changes.

Log activity:

Preserves recipient, IP, and action history for review.

Export evidence:

Exports the audit trail and certificate with the application.

Setting	Recommendation
Authentication method	Email verification with SMS OTP
Signature type	Electronic signature with completion certificate
Audit trail	Enable detailed audit trail export
Document retention	Six years for HIPAA records
Encryption	TLS 1.2 or 1.3 and AES-256 encryption

Platform requirements for signing

Complete the Application For Additional Provider Number For Allied Health Professional in a current Chrome, Firefox, Safari, or Edge browser on Windows or macOS. signNow protects connections using TLS 1.2 or TLS 1.3, and its mobile apps support iOS and Android signing.

Supported browsers Chrome, Firefox, Safari, and Edge
Desktop systems Windows and macOS computers
Mobile access iOS and Android mobile apps

Healthcare organizations should use managed Windows, macOS, iOS, or Android devices when applications contain provider identifiers or related health information. Enterprise deployments may also require API access, SSO provisioning, controlled user roles, and retention policies aligned with the receiving payer, credentialing program, and applicable HIPAA obligations.

Find and fill out the correct application for additional provider number for allied health professional

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

Versions	Form popularity	Fillable & printable
AU HW020 2018	4.8 Satisfied (698 Votes)
AU HW020 2016	4.8 Satisfied (5877 Votes)

Field preparation

Upload the provider application and place required signature, date, and text fields without recreating the document manually. Field assignments help keep professional and organizational information with the correct signer.

Signer routing

Route the application to the allied health professional, practice owner, or authorized representative in a defined signing order. Each recipient receives only the actions assigned to that role.

Signer verification

Use email authentication or stronger verification options when provider identifiers and credentialing information require additional signer assurance before completion.

Audit evidence

Preserve timestamps, recipient actions, and completion evidence with the signed application. The resulting audit trail helps reviewers evaluate how the record was executed.

Record export

Download the signed application and certificate of completion for the receiving payer, credentialing team, or controlled records repository after every required signature is complete.

Controlled templates

Reuse an approved application template for recurring provider enrollment workflows while restricting template editing to authorized administrators and preserving the form’s field structure.

Security for provider information

TLS protection:

Transport encryption

AES-256 encryption:

Stored-data encryption

HIPAA with BAA:

Healthcare compliance

SOC 2 Type II:

Independent controls

ISO 27001 certified:

Information security

ESIGN and UETA:

Electronic signatures

Privacy controls for provider applications

Limit disclosure of provider identifiers, tax details, licenses, and contact information to people who need them for credentialing or payer enrollment. Review the completed application before sending, remove unrelated attachments, and use signNow’s access controls rather than forwarding downloaded copies.
Capture electronic consent before signing when the applicant is a consumer or patient. Explain the electronic-record process, preserve evidence that the signer could access the document, and document any withdrawal or paper-record request under ESIGN, 15 U.S.C. §7001(c).
Assign each signer only the fields required for the additional provider number application. Use role-based permissions, verify recipient email addresses, and prevent delegated senders from editing provider identifiers after signature fields have been completed.
Avoid placing the signed application in shared folders without access restrictions. Retain the certificate of completion and audit trail with the application, apply least-privilege permissions, and review download activity for sensitive allied-health records.

Rules affecting related documents

Notarization requirement

May require wet-ink or notarial handling

Wills and codicils

Excluded from electronic execution

Court orders

Court acceptance may require original filing

Real-estate deeds

State recording rules may still apply

Record-keeping practices for provider applications

Accurate retention and export practices help credentialing teams preserve a defensible record for this provider number application.

Confirm the applicable retention period

Confirm the receiving program’s retention rule before filing the signed application. If the application contains protected health information, HIPAA requires covered entities to retain required policies, procedures, and records for six years from creation or the last effective date under 45 CFR §164.530(j).

Export the complete audit evidence

Export the completed application, certificate of completion, and audit trail together after every required signature. Preserve the original file format, export date, signer identities, timestamps, and delivery evidence so reviewers can assess the complete execution history.

Archive records with restricted access

Store the application in an access-controlled repository separated from general email and shared drives. Apply least-privilege permissions, encryption, retention holds, and documented destruction procedures that match the healthcare organization’s policy and the receiving program’s requirements.

Validate fields before signature

Review provider identifiers, licenses, practice locations, payer details, and signer roles before sending. Compare the completed application against source records, document corrections before signature, and avoid altering fields after execution unless the receiving authority permits a new submission.

Retention periods for related records

Apply the rule that actually governs the completed application and its record set; the receiving payer or credentialing program may impose a longer period.

Six years for HIPAA records

HIPAA’s six-year rule applies to required policies, procedures, and records from creation or the last effective date.

Three years for tax records

Federal tax records generally follow three years from filing under IRC §6501(a), but this application has no identified IRS filing rule.

Three years for payroll records

FLSA payroll records must be retained three years under 29 CFR §516.5 when included with related employment records.

Five years for injury records

OSHA injury records require five years following the year covered under 29 CFR §1904.33.

Thirty years for exposure records

OSHA exposure records require thirty years under 29 CFR §1910.1020 when the application is part of that record set.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

Troubleshooting the provider application

Use these answers to resolve field, signer, plan, compliance, signature-evidence, and retention questions for this provider number application.

Upload the original PDF again and inspect detected fields before sending. signNow supports manual field placement when automatic detection misses a provider identifier, license field, date, or signature location. Confirm every assigned field visually before routing the application.

Review the recipient address, signing order, and assigned fields. A signer cannot complete fields assigned to another recipient. Reassign the missing provider or representative fields, then send a corrected invitation rather than editing an already signed application.

Business includes legally binding eSignatures, templates, audit trails, and mobile apps at $8/user/month when billed annually. The plan includes 100 signature invites per user per year, with overage fees; confirm capacity before sending recurring applications.

signNow supports HIPAA compliance when a Business Associate Agreement is required and configured. Confirm the organization’s HIPAA role, data handling, access controls, and receiving program requirements before placing protected health information in the application workflow.

Use signNow’s audit trail and certificate of completion to show signer identity, timestamps, actions, and document history. Under ESIGN and UETA, enforceability also depends on intent, consent, attribution, and the ability to retain and reproduce the record.

Export the signed application and audit trail after completion, then store them in an access-controlled repository. HIPAA-required records generally follow six-year retention under 45 CFR §164.530(j), while the receiving program may impose additional requirements.

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.