5. get

In a config modifier schema, use get to retrieve a value at a given path.

To retrieve a nested property value, use dot.notation; a prefix . isn’t required. Additionally, we support an array[index] notation (e.g., get: someArray[0].someProperty).

This value can either be simply returned or used as a starting point for other keywords at the same level or nested below.

This keyword executes at the following nesting level:

1. omit
2. constant
3. references
4. use
5. __get__
6. properties or if or concat or switch or pipe or merge
7. default
8. plugin

You could indicate which value in an array to return.

Let’s say you have an MDM message. The TXA.4.1 value—mapped from a FHIR® message and representing activity date/time—is missing and needs to be populated.

1
{
2
  ...,
3
  "TXA": {
4
    "1": 1,
5
    "19": "AV",
6
    "3": "TX",
7
    "6": {
8
      "1": "20250828173111"
9
    }
10
  }
11
}

TXA.6.1 is being mapped and represents origination date/time, and you want to use this value for TXA.4.1 as well.

There are different ways to solve this. But one approach is to get the value directly from TXA.6.1 (as opposed to the initial FHIR® message) to map to TXA.4.1.

To do this, first include use to get the HL7v2 output (the current processedPayload) and then use get to retrieve and map the value at TXA.6.1 to TXA.4.1.

1
$.TXA.4.1

1
use: processedPayload
2
get: TXA.6.1

Based on this example config modifier, TXA.4.1 is now populated.

1
{
2
  ...,
3
  "TXA": {
4
      "1": 1,
5
      "19": "AV",
6
      "3": "TX",
7
      "4": {
8
        "1": "20250828173111"
9
      },
10
      "6": {
11
        "1": "20250828173111"
12
      }
13
  }
14
}