CMS 855B Form
Use a Cms 855b template to make your document workflow more streamlined.
What CMS 855B is and how it works
CMS 855B is the Medicare enrollment application used by institutional providers and medical groups to report organizational information for Medicare participation. The form collects details such as legal business identity, ownership, managing control, practice locations, and authorized-official information. An organization completes the applicable sections, attaches supporting documentation, obtains the authorized official’s signature, and submits the package through the required Medicare enrollment channel. signNow can prepare the PDF, detect and place fields, route it for signature, and preserve the signed record with an audit trail; it does not replace CMS or contractor submission requirements.
Who benefits from CMS 855B most
CMS 855B is most useful when Medicare enrollment data must be completed, reviewed, signed, and maintained across healthcare organizations.
Solo physician practices use CMS 855B to enroll a group practice or clinic with Medicare, coordinating ownership, reassignment, practice-location, and authorized-official information in one controlled submission. Multi-location medical groups use CMS 855B to report organizational changes, add practice locations, and maintain consistent Medicare enrollment records across clinicians, billing teams, and compliance administrators. Enterprise healthcare organizations use CMS 855B to coordinate enrollment updates across subsidiaries, delegated administrators, and compliance teams while preserving signed records and approval evidence for internal review.
These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.
Who uses CMS 855B and why
Medical groups
Medical group administrators use CMS 855B to document organizational enrollment details, practice locations, ownership, managing control, and authorized-official approval for Medicare participation.
Billing teams
Billing and compliance teams use CMS 855B records to coordinate enrollment updates, verify supporting information, and preserve signed documentation for internal controls and contractor communication.
How to complete CMS 855B in signNow
Use this sequence to prepare the CMS 855B file, obtain authorized-official approval, and preserve evidence of the completed signing event.
Upload form: Upload the CMS 855B PDF Place fields: Review detected fields and add missing responses Route signature: Send the enrollment form to the authorized official Archive record: Store the signed PDF with its audit trail
Steps for preparing CMS 855B
Prepare CMS 855B in signNow by checking the source form, assigning the authorized official, and preserving the completed record.
Upload form:
Upload the current CMS 855B PDF to signNow. Review fields:
Check detected fields against every applicable CMS 855B section. Assign signer:
Assign the authorized official’s signature and date fields. Store evidence:
Send, monitor completion, and download the audit trail.
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.
Features that support CMS 855B workflows
signNow combines document preparation, authorized-official routing, mobile signing, audit evidence, and integrations for CMS 855B enrollment administration.
Form preparation
Upload the CMS 855B PDF and place text, date, initials, and signature fields without rebuilding the enrollment form from scratch.
Signer routing
Route the completed CMS 855B to an authorized official by email or signing link, supporting controlled review before signature.
Reusable templates
Use templates for recurring CMS 855B enrollment updates while preserving the organization’s approved field arrangement and workflow.
Audit evidence
Capture signer actions, timestamps, and document history in an audit trail connected to the completed CMS 855B record.
Mobile signing
Review and sign CMS 855B from signNow mobile apps when enrollment administrators or authorized officials work away from the office.
System connections
Connect CMS 855B workflows with systems such as NetSuite, Salesforce, Google Drive, or Box when records must move between teams.
Platform requirements for CMS 855B
Complete CMS 855B in signNow using Chrome, Firefox, Safari, or Edge on Windows or macOS. signNow also provides iOS and Android mobile apps for reviewing and signing enrollment documents. Use a current browser with TLS 1.2 or 1.3 enabled for protected connections.
Browsers Chrome, Firefox, Safari, Edge Desktop systems Windows and macOS desktops Mobile apps iOS and Android apps
Healthcare organizations should deploy managed Windows, macOS, iOS, or Android devices when CMS 855B contains sensitive organizational or health information. Administrators can apply role-based access, configure SSO or API connections on eligible plans, and retain exported audit evidence with the completed enrollment record.
Signer authentication for CMS 855B
PKI support:
X.509 certificates:
Two-factor authentication:
SMS OTP:
ID verification:
Signing evidence:
CMS 855B completion challenges
Leaving ownership, managing-control, or practice-location fields incomplete can delay Medicare enrollment review and require a corrective submission. Using outdated organizational identifiers or inconsistent legal names can create mismatches between CMS 855B, Medicare records, and supporting documentation. Routing the form to the wrong authorized official can leave the submission unsigned or prevent the organization from establishing accountable approval. Uploading a scanned form without checking field placement can hide missing signatures, dates, or attachments before the organization submits its enrollment update.
Best practices for CMS 855B completion
Accurate organizational data, controlled approval, field review, and authority-based retention reduce avoidable problems with CMS 855B records.
Reconcile organizational data before signing
Review every detected field
Control authorized-official approval
Apply the correct retention rule
CMS 855B preparation and signing flow
A controlled sequence separates form preparation, authorized-official review, electronic signing, and submission or archival obligations.
Prepare the document
Deliver to signer
Obtain approval
Complete and archive
CMS 855B record retention periods
Retention depends on the record’s purpose and the applicable federal or state rule, not solely on the fact that CMS 855B was signed electronically.
Six years: HIPAA-covered records
Three years: federal tax records
Six years: substantial understatement
Three years: FLSA payroll
State-required period: verify rule
Risks from incorrect CMS 855B handling
Review delay
Invalid approval
Submission deficiency
Privacy exposure
CMS 855B signing questions answered
These answers address field preparation, authorized-official signing, privacy controls, plan limits, and evidence for CMS 855B workflows.
Upload CMS 855B as a clear PDF and use signNow’s field placement tools to add required signatures, dates, initials, and text fields. Review every page before sending because signNow cannot determine whether a missing CMS-required attachment belongs in your enrollment package.
The Business plan includes templates, mobile apps, and audit trails, while Business Premium adds bulk send. Choose a plan based on the number of organizations, signers, and repeated CMS 855B workflows rather than assuming every plan includes bulk sending.
signNow provides audit trails and is ESIGN and UETA compliant, but Medicare enrollment requirements remain separate. Confirm the authorized official, supporting documents, and submission channel required by the applicable CMS contractor before treating the signed PDF as complete.
For protected health information, signNow lists HIPAA compliance with a business associate agreement required. Configure the account and agreement appropriately, restrict access to CMS 855B records, and follow the organization’s HIPAA privacy and security procedures.
If a signer cannot open the request, verify the recipient address, resend the invitation, or use a controlled signing link. SMS authentication may require a supported phone number and should be enabled according to the organization’s access policy.
Business plans include 100 signature invites per user per year, with overage fees; the Site License uses $1.50 per signature invite. Review the selected plan before sending repeated CMS 855B enrollment packets.
Key performance indicators that demonstrate SignNow's proven track record.
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.