Nierman Practice Management — Implementation Playbook (DSO)

Executive Summary

Nierman Practice Management is a comprehensive revenue-cycle platform designed to optimize billing, collections, credentialing, and payer management across multi-location dental, medical, and surgical practices. For Dental Service Organizations (DSOs), Nierman accelerates centralized revenue operations while preserving local clinical autonomy—a critical balance that drives profitability without alienating acquired practices.

DSOs benefit uniquely from Nierman because they operate across fragmented billing systems, inconsistent credentialing timelines, and siloed payment posting. Implementation enables standardization without requiring clinical system replacement, reducing integration friction and deployment risk. Expect 14–16 weeks from contract signature to full operational deployment across a 15–25 location DSO footprint.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• IT Infrastructure Assessment

  • Verify bandwidth capacity at all locations (minimum 5 Mbps upload/download per site)
  • Confirm firewall and VPN compatibility with Nierman's cloud architecture
  • Document legacy EHR/EMR system versions and API capabilities
  • Audit current data security compliance (HIPAA, state privacy standards)

• Data Readiness

  • Extract 24 months of historical claims, EOBs, and AR aging from all locations
  • Reconcile patient demographic databases for duplicates and format standardization
  • Compile payer fee schedules and contract terms (primary focus: top 20 payers by claim volume)
  • Validate provider NPI, tax ID, and credentialing status across the enterprise

• System Integration

  • Map current practice management software to Nierman data specifications
  • Identify HL7/SFTP/API endpoints for claims submission and payment intake
  • Test sandbox environment connectivity from at least two geographically diverse locations
  • Plan for 30-day parallel run capability (legacy system + Nierman simultaneous operation)

Stakeholder Alignment

• Executive Steering Committee (CEO, CFO, Chief Clinical Officer, VP of Operations)

  • Define success metrics: DSO-wide AR days, clean claim rate, denial rate, net revenue per provider
  • Secure executive sponsorship and visible commitment to training attendance
  • Allocate contingency budget (10–15% of implementation cost) for unexpected system adjustments

• Departmental Leadership Buy-In

  • Billing managers: Clarify staffing model (centralize vs. hybrid local processing)
  • Collections teams: Address concerns about account assignment and workflow disruption
  • Credentialing coordinators: Establish payer enrollment timelines and dependency sequencing
  • Clinical leadership: Communicate that Nierman does not affect patient care workflows

• IT and Security Stakeholders

  • Assign dedicated IT liaison for Nierman integration support
  • Engage legal/compliance for BAA (Business Associate Agreement) finalization
  • Schedule security audit with Nierman's InfoSec team

Baseline Metrics Capture

Document these KPIs before go-live to establish control group data:

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Select two pilot locations representing operational diversity:

• Location A (Urban, high-volume): 500+ monthly claims, established payer mix, experienced billing staff
• Location B (Suburban, mid-volume): 200–300 monthly claims, legacy system familiarity, willing to adopt change

Avoid selecting struggling practices, understaffed locations, or sites with imminent turnover. Pilot sites should be proof points, not rescue operations.

Configuration and Setup

Week 3: System Build-Out

• Nierman team provisions dedicated environments for both pilot locations
• DSO IT team completes data migration from legacy systems (patient demographics, provider profiles, payer relationships)
• Configure location-specific defaults: charge masters, payment posting logic, aging buckets
• Set up user access roles (biller, supervisor, manager, auditor, clinician)

Week 4: Payer and Credentialing Integration

• Import top 15 payers per location; validate fee schedules and contract terms
• Enroll unprivileged providers into Nierman's credentialing module
• Map claim submission destinations (direct, clearinghouse, portal)
• Configure automated explanation of benefit (EOB) ingestion

Week 5: Workflow Mapping and Testing

• Document current billing workflows (charge entry → claim generation → posting → collections)
• Redesign workflows to leverage Nierman automation: rules-based payment posting, auto-denial routing, predictive follow-up prioritization
• Execute 50 test claims end-to-end; verify posting accuracy to <0.1% variance
• Test system performance during peak submission hours

Training Approach

Role-Based Training (Live Virtual, 2–4 hours per role)

1. Billers (Primary Users)

   • Hands-on: Charge entry, claim status tracking, payment posting logic
   • Scenario practice: Handle common denials, patient responsibility estimation
   • Sandbox access for 1 week before go-live

2. Supervisors/Managers

   • Dashboard analytics, drill-down investigation, performance benchmarking
   • Report generation for payer profiling and trend analysis
   • User management and credential provisioning

3. Credentialing and Contracting

   • Payer portal navigation, application tracking, ongoing compliance monitoring
   • Contract term management and automated renewal workflows

4. Clinical Leadership

   • High-level overview; emphasis on data privacy and audit trails
   • Q&A focused on workflow impact to front-desk and clinical operations

Ongoing Support: Assign Nierman CSM + DSO super-user team (1 per location) for escalation and troubleshooting during pilot weeks 5–6.

Scaled Rollout (Weeks 7-16)

Wave Planning

Wave 1 (Weeks 7-10): 5 mid-size locations

• Replicate pilot playbook; reduce setup time to 10 days per location
• Stagger go-lives by 2–3 days to prevent simultaneous system strain
• Establish daily "war room" calls (10 am PT, 30 min) for rapid issue resolution

Wave 2 (Weeks 11-13): 10 smaller locations

• Accelerate deployment; use standardized configuration templates
• Reduce go-live support to 4 weeks (vs. pilot's 6 weeks)

Wave 3 (Weeks 14-16): Remaining locations + enterprise optimization

• Deploy to any remaining sites; activate DSO-wide analytics and benchmarking
• Begin contract renegotiation informed by Nierman payer performance data

Change Management

• Weekly DSO Town Halls: CEO + Nierman CSM addresses organizational concerns, celebrates milestones
• Location-Level Champions: Designate billing supervisor at each site as "Nierman Expert"; provide 5 hours/week release time
• Incentive Alignment: Tie 10% of quarterly bonuses for billing managers to DSO improvement (e.g., -2 DSO days, +2% clean claim rate)
• Documentation Repository: Maintain shared wiki with FAQs, workflow diagrams, and video tutorials

Support Infrastructure

• Tiered Escalation Path:

  • Level 1: On-site super-user (same-day response)
  • Level 2: DSO centralized support team (4-hour SLA, 8 am–6 pm PT weekdays)
  • Level 3: Nierman CS engineer (emergency only, 24-hour SLA)

• Knowledge Transfer: Record all training sessions and troubleshooting calls for asynchronous reference

ROI Tracking

Key Metrics to Measure

• DSO improvement: Current baseline vs. weeks