Ub 04 CMS Form

Use a Ub 04 Cms Form template to make your document workflow more streamlined.

What the UB-04 CMS Form does

The UB-04 CMS Form is the institutional healthcare claim form used to report hospital and facility services to payers. It organizes billing information such as patient details, provider identifiers, payer data, diagnoses, service dates, revenue codes, charges, and claim totals. In signNow, a billing team can upload the UB-04 PDF, review detected fillable fields, assign signature or acknowledgment fields, and send it to authorized recipients. The completed form can remain paired with its audit trail, supporting controlled review and record retention without replacing payer-specific submission requirements.

Hospitals and health systems

Hospital billing departments use the UB-04 CMS Form to document institutional services for payer claims. signNow can route required acknowledgments and signatures, while HIPAA-covered organizations must establish appropriate safeguards and a business associate agreement where required.

Billing and outpatient teams

Revenue-cycle vendors and outpatient facilities use UB-04 workflows to coordinate claim documentation with authorized staff. Templates, field assignments, and audit trails help identify who completed each required section without replacing payer submission rules.

How to complete a UB-04 CMS Form

The signNow workflow moves the UB-04 from upload through field review, signature collection, and auditable storage.

Upload the form: Upload the UB-04 CMS Form PDF to signNow.
Review fields: Review detected fields and add missing signer, date, or acknowledgment fields.
Send for signing: Send the prepared claim form to authorized signers by email or link.
Store the record: Collect signatures and retain the completed form with its audit trail.

Use the signNow web app when billing staff prepare a UB-04 on a managed workstation and need to review fields before sending it for signature.
Use the signNow mobile app when authorized healthcare staff must review or sign a UB-04 from an iOS or Android device.
Use kiosk mode for supervised, on-site signing where a facility controls the device and signer handoff.
Use a shareable signing link when an approved recipient needs access without a separate email invitation.

Signer authentication:

Records the signer’s email, authentication method, and completed verification event.

Timestamp capture:

Captures the exact time each signer opens, reviews, and signs.

Document hashing:

Calculates a document hash before and after the signing session.

Tamper-evident sealing:

Binds signatures, timestamps, and actions into a tamper-evident completion record.

Action logging:

Logs field changes, reminders, refusals, and completed signing actions.

Audit export:

Lets administrators retrieve and export the completed audit trail with the document.

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.

Field detection

Upload the UB-04 PDF and review detected fields before assigning recipients, signatures, dates, or acknowledgments. This keeps preparation tied to the actual claim document rather than recreating its healthcare billing structure manually.

Role assignment

Assign specific UB-04 fields to authorized staff or recipients, reducing uncertainty about who must review patient, payer, service, and claim information before completion.

Remote signing

Route the completed UB-04 by email or signing link, allowing approved recipients to review and sign without exchanging paper copies between departments.

Audit evidence

Capture signer actions, timestamps, authentication events, and document history in an audit trail that can accompany the completed claim record.

Mobile access

Use mobile apps when authorized staff review or sign UB-04 records away from a workstation, subject to device-management and PHI policies.

Controlled storage

Keep the completed UB-04 and signing evidence together for controlled retrieval, payer inquiries, internal review, and healthcare record retention.

Security for UB-04 records

Transport encryption:

TLS 1.2/1.3 in transit

Storage encryption:

AES-256 at rest

HIPAA compliance:

HIPAA with BAA required

Security assurance:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Signing evidence:

Audit trails and timestamps

Platform requirements for UB-04 workflows

Use signNow through Chrome, Firefox, Safari, or Edge on Windows or macOS. Mobile signing is available through signNow apps for iOS and Android, with encrypted connections using TLS 1.2 or TLS 1.3.

Browsers Chrome, Firefox, Safari, and Edge
Desktop systems Windows and macOS desktop access
Mobile access iOS and Android mobile apps

Healthcare organizations should manage access through approved devices, restricted accounts, and documented permissions. Enterprise deployments may connect signNow with APIs, SSO provisioning, and controlled storage systems. Confirm certificate, retention, and HIPAA configuration requirements with your compliance team before production use.

Record-keeping practices for UB-04 forms

Preserve the completed UB-04, signing evidence, and access controls according to healthcare privacy and retention obligations.

Retain healthcare records for six years

Keep each completed UB-04 and its audit trail together in a controlled repository. For HIPAA-covered records, retain documentation for six years from creation or the last effective date under 45 CFR §164.530(j). Apply any longer state or payer requirement separately.

Export the completed audit trail

Export the signed UB-04, certificate of completion, and audit trail after final signing. Preserve the export in a format that can be reproduced for a payer, auditor, or authorized patient request without relying solely on an active signNow account.

Limit access to protected health information

Restrict UB-04 access to staff who handle billing, claims, compliance, or authorized clinical administration. Use role-based permissions and review access when duties change, because the form can contain protected health information.

Archive encrypted claim records

Use encrypted storage and a documented retention schedule for UB-04 files. signNow encrypts data in transit with TLS 1.2/1.3 and at rest with AES-256; your organization remains responsible for classification, access, and deletion decisions.

Prepare the form

Prepare the UB-04 PDF and verify patient, provider, payer, and service fields before sending.

Send to signers

Deliver the assigned fields by email or a controlled signing link.

Collect signatures

Signer turnaround depends on the assigned staff member and internal review policy.

Archive the record

After completion, export the signed form and audit trail for controlled archival.

UB-04 privacy and disclosure pitfalls

Sending a UB-04 containing patient identifiers without a documented HIPAA safeguard can expose protected health information to unauthorized recipients.
Leaving payer, diagnosis, revenue-code, or charge fields incomplete can create claim delays or require manual correction before submission.
Collecting a signature without recording signer identity, intent, or authorization can weaken the organization’s evidence that the UB-04 was approved.
Giving broad template access can let unauthorized staff view or alter protected healthcare information embedded in the UB-04.

Risks of mishandling UB-04 forms

Weak attribution

Missing signer identity weakens claim evidence.

Claim rejection

Incomplete fields can delay payer review.

PHI disclosure

Unprotected PHI creates HIPAA exposure.

Audit gap

Missing audit evidence complicates investigations.

Business types using UB-04 workflows

UB-04 workflows fit healthcare organizations that coordinate institutional claims, signatures, protected information, and auditable records.

A solo medical practice can use a UB-04 workflow to route facility-service claim documentation, capture authorized acknowledgments, and keep the completed form with its audit evidence rather than coordinating paper signatures across separate offices.
A regional hospital billing department can standardize UB-04 templates, assign fields by responsibility, and restrict PHI access while coordinating signatures among revenue-cycle, clinical-administration, and compliance personnel.
An enterprise health system can connect UB-04 workflows with approved storage, identity controls, and reporting systems, giving multiple facilities a consistent process while preserving local payer and state-law requirements.

Features	signNow	DocuSign	Adobe Sign	PandaDoc
Starting annual price	$8/user/month	Not verified	Not verified	Not verified
Free trial	7 days	Not verified	Not verified	Not verified
Bulk send availability	Business Premium	Not verified	Not verified	Not verified
Audit trail	Included	Not verified	Not verified	Not verified
HIPAA availability	BAA required	Not verified	Not verified	Not verified

UB-04 form troubleshooting and FAQs

Find direct answers about UB-04 field review, HIPAA controls, signing evidence, retention, and payer submission limits.

Upload the UB-04 PDF and inspect signNow’s detected fields before sending. Auto-detection does not confirm that payer-specific boxes, revenue codes, diagnosis entries, or required acknowledgments are complete, so billing staff should compare the prepared document with internal claim procedures.

The signNow Business plan includes legally binding eSignatures, templates, audit trails, and mobile apps at $8/user/month with annual billing. Business Premium adds bulk send at $15/user/month, while Enterprise adds advanced signer authentication at $30/user/month.

For healthcare workflows involving protected health information, signNow identifies HIPAA compliance as requiring a business associate agreement. Confirm that the organization has the required BAA and controls before sending a UB-04 containing PHI.

A signer may receive an email invitation, SMS code, or another configured authentication step. If access fails, verify the recipient address, device connectivity, authentication settings, and whether the signer is authorized to handle the UB-04.

A completed UB-04 should be exported with its certificate of completion and audit trail. Store the package under the organization’s retention policy; HIPAA documentation generally requires six years under 45 CFR §164.530(j).

Electronic signing does not replace payer submission rules or claim-data validation. ESIGN and applicable UETA provisions support electronic records when intent, consent, attribution, and reproducible retention are established, but the payer determines acceptable UB-04 submission procedures.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

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.