Common use cases for config modifiers

Last updated: Apr 29, 2025
IMPLEMENTATION
DEVELOPER

Config modifiers are a set of custom instructions for processing incoming or outgoing data. Learn about changing data with config modifiers.

Config modifiers can help with many use cases. You’ll usually discover opportunities for config modifiers during implementation testing as you or your connection receive data you don’t expect or vice versa. Review some common ones below.

Hardcode a specific field

Different sites expect different things. You can hardcode fields and values so that your connection always gets the required data. For example, you expect a certain document ID type or sending facility code in every message.

Populate fields with values from different segments

Different sites configure their messages differently, so data might be found in unusual places. Redox base configs account for most of these variations. But if a value is missing from the segment you expect, you could write a config modifier to pull that value from another segment. For example, your connection sends time the visit starts in an unexpected segment.

Account for inconsistent messaging

Sometimes a site is inconsistent with their own message formatting. It's possible that a site populates a value in one field in some messages but leaves it blank or populate a different field for other messages. This can happen if your connection handles IDs and codes differently based on visit type or order type.

Other use cases

Review examples from our how-to docs to solve for common use cases:

Use cases
Examples
Check if a value exists in the initial payload. If so, set a constant value; if not, set a different constant value.
Change a code based on whether data in the initial payload equals or includes some other text.
Remove an observation from the Observations array in a Flowsheet when the code from that observation matches.