Using Admin Configuration
Updated at February 18th, 2025
Table of Contents
Configuration is intended for PatientPay System Administrators to configure partners and their respective organizations. This gives our Services and Support teams tools to view and manage various settings related to branding, ingestion, payments, dunning, communication, and recon. A partner represents a grouping of medical providers. An organization represents a medical provider (often the legal entity). Admin provides configuration at the partner level, as well as the individual organization level. There is an inheritance model followed across all configuration:
- System-level configuration provides system defaults (set by PatientPay Product)
- Partner-level configuration overrides system defaults
- Organization-level configuration overrides partner-level configuration
This allows PatientPay to define configuration / behavior for a partner, and then override any unique behavior to a provider at the organization level. For example, there are no payment plans offer by default at the system level. A partner can configure payment plan options once, and offer this to all of their organizations. It streamlines onboarding for new practices, provides consistent policies across the group, and makes maintenance easy should the payment plan options need to be adjusted. If one organization in the group has special cases, you can configure different payment plan options at the organization level and they will override the partner's configuration.
Getting Started with Admin Configuration
- Configuring Partners
-
Configuring Organizations
- Configuring Organization Information Settings
- Configuring Organization Ingestion Settings
- Configuring Organization Dunning Settings
- Configuring Organization Payments Settings
- Configuring Organization Communication Settings
- Configuring Organization Recon Settings
- Configuring Organization Patient Experience Settings