Enterprise configuration management overview

The Enterprise Configuration Management feature is a separately contracted add-on feature that allows you to automatically update configurations across linked CIDs. If you are interested in adding the Enterprise Configuration Management feature, please contact your account manager for more information.

Enterprise configuration management functionality

Enterprise configuration management provides the ability to update configurations in one place and have those changes automatically updated across all linked CIDs.

Managing configurations across enterprise CIDs is a powerful feature. When a user chooses to update across associated CIDs, the changes are applied automatically and take effect immediately. Analysis of your linked CIDs is needed to determine if this feature is appropriate for your facilities. Best practice usage would restrict this functionality to only those users who are responsible for maintaining site configurations.

When a user with the Enterprise Configuration Management group right updates any of the configuration items from the table below they are prompted to select if the changes made during this session to this configuration should be applied to linked CIDs. When the user selects yes, the linked CIDClosed Client ID (CID) is the assigned four-digit customer site ID. configurations are updated immediately. Some items update the configuration items and other items perform an overwrite of the configuration. The table below identifies each configuration feature that is currently available as well as the type of update that will be performed.

Prompt: Configuration category changes

When authorized users click OK after making a change to any of the configuration categories, they are presented with a confirmation prompt.

  • If a user clicks “Yes,” that change will be applied to all sites (CIDs) across the entire enterprise!
  • Use caution in making these changes, especially Bridge Routines, as these changes have implications all linked sites!

Configuration table

The configuration table describes each configuration category, the type of change that will occur when updating each category, and explanations, prompts, and warnings for relevant categories.

Configuration category Type Note
User Master N/A Shared user master for linked clients.
Group Master Change This action will update changed items on linked sites.
Bridge Routines Overwrite

Assurance checks across linked clients and client sets to confirm whether bridge routine files are checked out on another CID and whether site files are locked. When files are locked, users will see one of the following messages: 

  • CID: When a file is checked out on another CID, users will see this message:
    • "Bridge File (asc_hp.2nd) NOT copied (Client Locked)"
  • File: When a file is locked on a site, users will see this message: 
    • "Bridge File (asc_hp.2nd) NOT copied (File Locked)"

=========================

  • Use extreme caution when updating bridge routines with Enterprise Configuration Management as this update cannot be undone.
  • Assurance overwrites information at the individual file level.
  • Versioning will only be available on the CID where the update was made.
Error Severity Change This action will update changed items on linked sites.
Saved Filters Claims & Remits Overwrite This action will overwrite filters of the same name on linked sites.
Delete Claim or Remits Filters Remove This action will remove the filter with the same name from linked sites.
Payer Alias Change This action will update changed items on linked sites.
Hold Codes Change This action will update changed items on linked sites.
Remit Import Options Change This action will update changed items on linked sites.
Secondary Billing Options Change This action will update changed items on linked sites.
Site File Maintenance (Support/Power User feature) Overwrite
  • Use extreme caution when updating bridge routines with enterprise configuration management as this update cannot be undone.
  • Assurance overwrites information at the individual file level.
  • Versioning will only be available on the CID where the update was made.