Linked Libraries

Linked Libraries

If there is a Parent/Child Database linkage, Library records can be shared between the Parent and Child Databases.
  • A Parent Database can have multiple Child Databases, but a Child Database can only have one Parent Database.

The following Libraries support Parent/Child linkages:

  • Insurances, Insurance Addresses, Insurance Products
  • Referring Providers
  • Transaction Codes
  • Procedure Codes, NDC Codes, Procedure Base Units (if enrolled with AMA Procedure Codes)
  • Diagnosis Codes
  • Tags
  • Appointment Reminder, Recall, and Balance Notification Templates
  • Charge Management Rules/Actions
  • The Parent Database is the Source of Truth for linked records, but records can be added to the Child Database without being added to the Parent Database.
  • In a Child Database, the Linked Libraries will have a banner to show which Database is the Parent.

  • Records that are added to a Child Database can also be added to the Parent Database.
  • When adding a record to a Linked Library in a Child Database, select Yes in the Link to Parent dropdown.

  • The Parent Database will then send the new record to all other Linked Libraries from other Child Databases.

Create Independent Library Records from a Parent Database

Idea
Use this workflow when a Child Database needs to start with the same Library setup as the parent, but you want to manage records independently going forward.

To use Parent Library records in a Child Database without maintaining an ongoing link between the Databases:

  1. Link the Parent Library to the Child Database(s).

  2. Once the records have been populated, unlink the Child Database(s).

    • The records will remain in the Child Database, but they will not be updated if changes are made to the Parent records.

Existing Databases can also be linked to a Parent Library.

  • The existing records remain in the Child Database and will not populate the Parent Database.

  • If the same record already exists in the Parent Database, the Parent record will still be brought into the Child Database, but it will be appended with -P.

    • For example, if BCBS exists in the Parent and Child Database, the Parent record will show as BCBS-P in the Child Database.

    • The Insurance Addresses may differ but still be considered a duplicate record.

      • In this case, duplicate records need to be carefully managed to ensure the right Insurance is used.