6. pipe

Last updated: Sep 10, 2025
DEVELOPER
IMPLEMENTATION
HEALTH TECH VENDOR

Definition

In a config modifier schema, use pipe to stack the outcome of a previous keyword as the input of the next. The keywords need to exist at the same nesting level for the keywords to be evaluated in order.

Think of this like a math equation with a parenthetical statement that must be resolved before calculating. For example, 2 + 4 x 6 would have a different outcome from 2 + (4 x 6). In this way, the pipe keyword allows you to bracket keywords for a particular order of operations within the overall schema.

Nesting level

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

Example

You can change VisitDateTime to ISO format.

Example: Pipe input from initial payload
json
1
"Visit": {
2
...
3
"VisitDateTime": "2025-06-11 00:00:00Z",
4
...
5
}
Example: Pipe selector
json
1
$.Visit.VisitDateTime
Example: Config modifier with pipe keyword
yaml
1
pipe:
2
- plugin:
3
name: text
4
action: split
5
parameters:
6
separator: Z
7
getIndex: 0
8
- plugin:
9
name: date-time
10
action: parse
11
parameters:
12
custom: yyyy-MM-dd HH:mm:ss
13
timeZone: America/New_York

Based on this example config modifier schema, VisitDateTime is updated to ISO format.

Example: Pipe output in processed payload
json
1
"Visit": {
2
...
3
"VisitDateTime": "2025-06-11T00:00:00.000-04:00",
4
...
5
}