The Ingestion tab of Organization Configuration is for editing ingestion-related settings for the selected organization. This includes whether the bill type is Lifetime or Episodic, the number of days to ignore statement files if there is a successful transaction, and the number of days till due (used to calculate a bill’s due date).

Ingestion Settings

Bill Type

The Bill Type determines how PatientPay should expect to handle bills for the provider's patients. Lifetime means that a patient/guarantor can have only one due bill at a given time.  Episodic means that a patient/guarantor can have multiple due bills at a given time.

Number of Days to Ignore After Transaction

The Number of Days to Ignore After Transaction setting defaults to 0 days which means to process all statement files. Organizations may adjust this to match their average days to post transactions from Recon so that they aren’t sending us statement files with stale bill balances.

Number of Days Until Due

The Number of Days Until Due setting defaults to 30 days which means a bill will be due 30 days after the effective date. If you set Number of Days Until Due to 0 days, it would reflect that the bill is due immediately. The Due Date is only re-evaluated if we change the EffectiveCreatedDate (via dunningStatus change).

Figure 193 - Organization Configuration Ingestion

Visit Locations

The Visit Locations section of Ingestion allows you to configure the mapping of visit location for the bill based on a location code. This is reserved for our partner HAP that cannot pass the locationName in the statement JSON and only have a code in their source system. The table maps a location code to its corresponding location name. If a code is found in this table, we use the location name as the visitLocation value in the statement JSON. If no code is found, we default to blank. This lookup table is represented in our DB schema customer_management.location_code_mapping.

Figure 194 - Organization Configuration Visit Locations

To add a single location, simply press the Add Location button to invoke the Add Location dialog and enter a unique location code and name. The location code would match what you expect the partner to send in the statement file for the locationName field. The location name is what you want displayed on the bill for the visit location when you receive this code.

Figure 195 - Add Location

To edit an existing location code or name, use the pencil icon to invoke the Add Location dialog.

Figure 196 - Edit Location

To quickly add several locations at once, use the Upload CSV button to select a CSV containing columns for location code and location name separated by a comma. Below is an example layout of the CSV. Once you’ve made all your changes, be sure to press Save to commit them.

NOTE: The file should not include a header record.

Figure 197 - Upload CSV

If the file contains any location codes that already exist in your list, they will be overwritten with the new location name. If the CSV contains invalid entries, you will get a warning “Unable to process some locations as they are not valid. Please add them manually”. Below are the reasons a location will fail to upload:

• Location code is not alphanumeric
• Location code length is greater than 45 characters
• Location name length is greater than 255 characters

To remove a location, use the trash can icon and confirm on the Confirm Deletion dialog.

Figure 198 - Delete Location