Run log inspector

post/v1/dry-run/logs/{logId}

Page View

Logs endpoints allow you to review log metadata, including relevant timestamps and statuses. Or, if you want to dig into a log for troubleshooting purposes, you can run log inspector.

Log payloads not returned

You can search log metadata or payloads via API, but you won't receive log payloads in the responses. You can only review log payload contents in the Redox dashboard (if you're assigned to an engineer or support role).

You can retrieve a list of log metadata, search for specific data within log payloads, retrieve one log with its metadata, or run log inspector.

Run log inspector

Run log inspector to review metadata and operation details for a given log.

This doesn't re-send the log; it's only a preview option for troubleshooting. Or, you can run log inspector as you make changes to operation settings (e.g., translations, filters, config modifiers) to preview the impact of your changes before applying to real-time traffic.

Learn more about log inspector.

Request parameters and payload

cURL request example

bash

1
curl 'https://api.redoxengine.com/platform/v1/dry-run/logs/{logId}' \
2
--request POST \
3
--header 'Authorization: Bearer $API_TOKEN' \
4
--header 'accept: application/json' \
5
--header 'content-type: application/json' \
6
--data '{
7
  "environment": {
8
    "id": "string"
9
  },
10
  "inspectorOverrides": {
11
    "source-request": {
12
      "configModifiers": [
13
        {
14
          "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
15
          "linkId": "009f739c-6620-43b0-978e-b245e723c57a",
16
          "flavor": "delete",
17
          "selector": "$.Patient.Identifiers[*].ID",
18
          "schema": {
19
            "plugin": {
20
              "name": "text",
21
              "action": "upper-case"
22
            }
23
          },
24
          "eventTypes": [
25
            "string"
26
          ]
27
        }
28
      ]
29
    },
30
    "destination-request": {
31
      "configModifiers": [
32
        {
33
          "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
34
          "linkId": "009f739c-6620-43b0-978e-b245e723c57a",
35
          "flavor": "delete",
36
          "selector": "$.Patient.Identifiers[*].ID",
37
          "schema": {
38
            "plugin": {
39
              "name": "text",
40
              "action": "upper-case"
41
            }
42
          },
43
          "eventTypes": [
44
            "string"
45
          ]
46
        }
47
      ]
48
    },
49
    "destination-response": {
50
      "configModifiers": [
51
        {
52
          "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
53
          "linkId": "009f739c-6620-43b0-978e-b245e723c57a",
54
          "flavor": "delete",
55
          "selector": "$.Patient.Identifiers[*].ID",
56
          "schema": {
57
            "plugin": {
58
              "name": "text",
59
              "action": "upper-case"
60
            }
61
          },
62
          "eventTypes": [
63
            "string"
64
          ]
65
        }
66
      ]
67
    },
68
    "source-response": {
69
      "configModifiers": [
70
        {
71
          "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
72
          "linkId": "009f739c-6620-43b0-978e-b245e723c57a",
73
          "flavor": "delete",
74
          "selector": "$.Patient.Identifiers[*].ID",
75
          "schema": {
76
            "plugin": {
77
              "name": "text",
78
              "action": "upper-case"
79
            }
80
          },
81
          "eventTypes": [
82
            "string"
83
          ]
84
        }
85
      ]
86
    }
87
  }
88
}'

Request Body Schema

environment
required, object
Describes the environment the log belongs to.
- id
  required, string
  Identifies the specific environment that the log belongs to.
inspectorOverrides
object
Describes unsaved changes to operations that will only apply during this run of log inspector. These changes won't apply to real-time logs until they're saved.
- source-request
  object
  Describes the changes to apply to a payload at the given processing location, whether on the source or destination side of the exchange.
  configModifiers
  Array of object
  flavor
  required, string
  Indicates the type, or flavor, of config modifier. A put flavor alters data (creates or replaces) in a payload, while a delete flavor removes data from a payload.
  Possible Values: delete, put
  selector
  required, string
  Indicates the location(s) within the payload that the config modifier will operate on.
  eventTypes
  required, Array of string
  Indicates which event type(s) of the subscription the config modifier will operate on. If not restricted to certain event types, you must explicitly set this field to null; this means the config modifier will operate on all event types.
  id
  string
  Contains the unique identifier of an existing config modifier. If an id isn't provided, the config modifier described here will be processed as if it were newly created and will be assigned a temporary unique id.
  Format: uuid
  linkId
  string
  Specifies the subscription that an existing config modifier is linked to.
  Format: uuid
  schema
  object
  Required for a put flavor config modifier. Indicates how to build the value at the location the selector specifies.
- destination-request
  object
  Describes the changes to apply to a payload at the given processing location, whether on the source or destination side of the exchange.
  configModifiers
  Array of object
  flavor
  required, string
  Indicates the type, or flavor, of config modifier. A put flavor alters data (creates or replaces) in a payload, while a delete flavor removes data from a payload.
  Possible Values: delete, put
  selector
  required, string
  Indicates the location(s) within the payload that the config modifier will operate on.
  eventTypes
  required, Array of string
  Indicates which event type(s) of the subscription the config modifier will operate on. If not restricted to certain event types, you must explicitly set this field to null; this means the config modifier will operate on all event types.
  id
  string
  Contains the unique identifier of an existing config modifier. If an id isn't provided, the config modifier described here will be processed as if it were newly created and will be assigned a temporary unique id.
  Format: uuid
  linkId
  string
  Specifies the subscription that an existing config modifier is linked to.
  Format: uuid
  schema
  object
  Required for a put flavor config modifier. Indicates how to build the value at the location the selector specifies.
- destination-response
  object
  Describes the changes to apply to a payload at the given processing location, whether on the source or destination side of the exchange.
  configModifiers
  Array of object
  flavor
  required, string
  Indicates the type, or flavor, of config modifier. A put flavor alters data (creates or replaces) in a payload, while a delete flavor removes data from a payload.
  Possible Values: delete, put
  selector
  required, string
  Indicates the location(s) within the payload that the config modifier will operate on.
  eventTypes
  required, Array of string
  Indicates which event type(s) of the subscription the config modifier will operate on. If not restricted to certain event types, you must explicitly set this field to null; this means the config modifier will operate on all event types.
  id
  string
  Contains the unique identifier of an existing config modifier. If an id isn't provided, the config modifier described here will be processed as if it were newly created and will be assigned a temporary unique id.
  Format: uuid
  linkId
  string
  Specifies the subscription that an existing config modifier is linked to.
  Format: uuid
  schema
  object
  Required for a put flavor config modifier. Indicates how to build the value at the location the selector specifies.
- source-response
  object
  Describes the changes to apply to a payload at the given processing location, whether on the source or destination side of the exchange.
  configModifiers
  Array of object
  flavor
  required, string
  Indicates the type, or flavor, of config modifier. A put flavor alters data (creates or replaces) in a payload, while a delete flavor removes data from a payload.
  Possible Values: delete, put
  selector
  required, string
  Indicates the location(s) within the payload that the config modifier will operate on.
  eventTypes
  required, Array of string
  Indicates which event type(s) of the subscription the config modifier will operate on. If not restricted to certain event types, you must explicitly set this field to null; this means the config modifier will operate on all event types.
  id
  string
  Contains the unique identifier of an existing config modifier. If an id isn't provided, the config modifier described here will be processed as if it were newly created and will be assigned a temporary unique id.
  Format: uuid
  linkId
  string
  Specifies the subscription that an existing config modifier is linked to.
  Format: uuid
  schema
  object
  Required for a put flavor config modifier. Indicates how to build the value at the location the selector specifies.

Response fields and example

Example payload generated from schema

1
{
2
  "meta": {
3
    "version": "1.0.0"
4
  },
5
  "payload": {
6
    "result": {
7
      "id": "6aaa12d1-99d5-4362-99c3-3ae4a3aa67f0",
8
      "timestamp": "2024-02-27T17:50:10.584Z",
9
      "status": "succeeded",
10
      "attempt": {
11
        "id": "b6016b49-9086-4ca3-a01f-36392bb7c829",
12
        "status": "succeeded",
13
        "timestamp": "2024-02-27T17:50:10.584Z",
14
        "stages": {
15
          "request": {
16
            "number": 1,
17
            "name": "Request",
18
            "communicationMethod": "Redox API",
19
            "status": "succeeded",
20
            "dataFormat": "HL7v2",
21
            "timestamp": "2024-06-04T09:21:58.960Z"
22
          },
23
          "process-request": {
24
            "number": 2,
25
            "name": "Process",
26
            "status": "succeeded",
27
            "dataFormat": "HL7v2",
28
            "timestamp": "2024-06-04T09:21:58.960Z"
29
          },
30
          "receive-request": {
31
            "number": 3,
32
            "name": "Receive",
33
            "communicationMethod": "Redox API",
34
            "status": "succeeded",
35
            "dataFormat": "HL7v2",
36
            "timestamp": "2024-06-04T09:21:58.960Z"
37
          },
38
          "respond": {
39
            "number": 4,
40
            "name": "Respond",
41
            "communicationMethod": "Redox API",
42
            "status": "succeeded",
43
            "dataFormat": "HL7v2",
44
            "timestamp": "2024-06-04T09:21:58.960Z"
45
          },
46
          "process-response": {
47
            "number": 5,
48
            "name": "Process",
49
            "status": "succeeded",
50
            "dataFormat": "HL7v2",
51
            "timestamp": "2024-06-04T09:21:58.960Z"
52
          },
53
          "receive-response": {
54
            "number": 6,
55
            "name": "Receive",
56
            "status": "succeeded",
57
            "dataFormat": "HL7v2",
58
            "timestamp": "2024-06-04T09:21:58.960Z"
59
          }
60
        },
61
        "operations": [
62
          {
63
            "type": "blobResolvers",
64
            "operationId": "3051932a-fdd2-48fa-b330-7e7d41535969",
65
            "version": 1,
66
            "order": 1,
67
            "attemptStage": "request",
68
            "startTime": "2024-06-04T00:00:00Z",
69
            "endTime": "2024-06-04T00:00:00Z",
70
            "error": {
71
              "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
72
              "code": "customer.translation.error",
73
              "meta": {},
74
              "title": "string",
75
              "detail": "string"
76
            },
77
            "inputSnapshotIds": [
78
              "string"
79
            ],
80
            "outputSnapshotIds": [
81
              "string"
82
            ],
83
            "typeCanModifyPayload": false,
84
            "managedBy": "redox",
85
            "managedByOrganization": {
86
              "id": 0,
87
              "name": "string"
88
            },
89
            "details": {
90
              "blobResolvers": [
91
                {
92
                  "id": 0,
93
                  "status": "found"
94
                }
95
              ]
96
            }
97
          }
98
        ],
99
        "snapshots": [
100
          {
101
            "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
102
            "name": "string",
103
            "data": null,
104
            "dataFormat": "JSON"
105
          }
106
        ]
107
      },
108
      "customProcessing": {
109
        "filters": [
110
          {
111
            "operationId": "string",
112
            "shouldFilter": true,
113
            "filters": [
114
              {
115
                "action": "send",
116
                "filterVersion": 1,
117
                "outcome": "disqualified",
118
                "rules": [
119
                  {
120
                    "path": "$.Admission.Diagnosis[*].AltCodes[*].Code",
121
                    "outcome": "disqualified"
122
                  }
123
                ]
124
              }
125
            ]
126
          }
127
        ],
128
        "translations": [
129
          {
130
            "operationId": "string",
131
            "translations": [
132
              {
133
                "translationSetLinkId": "878b1451-59de-4004-8a02-98539a419939",
134
                "translationSetId": "6531111b-777c-4c97-a077-8ddaea0830c4",
135
                "fields": [
136
                  {
137
                    "status": "translated",
138
                    "fieldPath": "string",
139
                    "matchedPath": "string"
140
                  }
141
                ]
142
              }
143
            ]
144
          }
145
        ]
146
      },
147
      "logType": "async",
148
      "transmissionUniqueIds": [
149
        "80a0b378-04b2-4419-b0ed-e560d8f4f152"
150
      ],
151
      "source": {
152
        "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
153
        "name": "string",
154
        "organization": {
155
          "id": 0,
156
          "name": "string"
157
        },
158
        "communicationMethod": "MLLP"
159
      },
160
      "destination": {
161
        "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
162
        "name": "string",
163
        "organization": {
164
          "id": 0,
165
          "name": "string"
166
        },
167
        "communicationMethod": "MLLP",
168
        "communicationMethodFlavor": "Wellstar-Azure"
169
      },
170
      "subscription": {
171
        "id": "string",
172
        "dataModel": "Patient Admin"
173
      }
174
    }
175
  }
176
}

meta
object
- version
  string
  Lists the major and minor version number for the format of the returned payload. The payload format or shape may change between minor versions, like including additional or extended fields in later versions. We include the version data in each response so that you have the option to handle the signaled differences.
payload
object
- result
  object
  Contains the results after running log inspector on the specified log. You can use the results for troubleshooting or comparison purposes.
  id
  required, string
  Contains the unique identifier of the log inspector processing attempt. This is different from the original log id.
  Format: uuid
  timestamp
  required, string
  Displays the date and time that log inspector ran in ISO 8601 format.
  status
  required, string
  Indicates the log status after running log inspector.
  Possible Values: failed, filtered, pending, succeeded
  attempt
  required, object
  Describes an attempt at processing a log.
  id
  required, string
  Contains the unique identifier of the specific log attempt.
  Format: uuid
  status
  required, string
  Indicates the current status of the attempt.
  Possible Values: failed, filtered, pending, succeeded
  timestamp
  required, string
  Displays the date and time in ISO 8601 format indicating when the attempt was made.
  stages
  required, object
  Describes a phase of log processing, which includes at least one operation or a collection of operations.
  One of:
  request
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  communicationMethod
  string
  Indicates the communication method used during this processing stage.
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  process-request
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  receive-request
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  communicationMethod
  string
  Indicates the communication method used during this processing stage.
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  respond
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  communicationMethod
  string
  Indicates the communication method used during this processing stage.
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  process-response
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  receive-response
  object
  number
  required, integer
  Indicates the sequential order in log processing where this stage occurs.
  name
  required, string
  Displays the human-readable name of this processing stage.
  status
  nullable, required, string
  Indicates the overall status of a stage. Will be null if processing didn't reach this stage.
  Possible Values: failed, filtered, pending, succeeded
  dataFormat
  string
  Describes the format the data was in when exchanged during this processing stage.
  timestamp
  nullable, string
  Indicates the date and time of the outcome of this processing stage in ISO 8601 format.
  operations
  required, Array of BLOB resolvers, Cleansers, Conductors, Config modifiers
  Describes any operations (e.g., filters, translations) that were performed during log processing.
  Any of:
  type
  required, string
  Indicates the type of operation performed. The type determines what data is included in the Details property.
  Possible Values: blobResolvers, cleansers, conductors, configModifiers, deliveries, filters, jsonConverters, preParsers, redoxConfigurations, redoxFilters, taggers, translations
  operationId
  required, string
  Contains the unique identifier of the given operation.
  Format: uuid
  version
  required, number
  Displays the Redox version of the given operation.
  order
  required, number
  Indicates the sequential order in log processing where the operation occurs. The first operation will have an order number of 1.
  attemptStage
  required, string
  Describes the processing stage where the given operation occurred.
  Possible Values: send, process, receive, request, process-request, receive-request, respond, process-response, receive-response
  startTime
  required, string
  Displays the date and time that the operation began processing in ISO 8601 format.
  endTime
  required, string
  Displays the date and time that the operation finished processing in ISO 8601 format.
  typeCanModifyPayload
  required, boolean
  Indicates whether the operation can alter any payload content.
  managedBy
  required, string
  Indicates whether you (i.e., customer) can create and manage this operation type, or if only a Redoxer (i.e., redox) can.
  Possible Values: redox, customer
  details
  required, object
  blobResolvers
  required, Array of object
  id
  required, number
  Contains the unique identifier of the BLOB resolver.
  status
  required, string
  Indicates whether the BLOB file location referenced in the payload could be found and resolved to its file contents.
  Possible Values: found, not-found
  error
  object
  Describes any errors related to the operation that occurred during log processing.
  id
  string
  Contains the unique identifier of the error.
  Format: uuid
  code
  string
  Displays a code that indicates the type of error that occurred.
  meta
  object
  Contains metadata about the error that occurred. This can vary depending on the specific error.
  title
  string
  Contains a human-readable description of the error.
  detail
  string
  Explains the error in more detail.
  inputSnapshotIds
  Array of string
  Lists the unique identifiers that correlate to each input snapshot, respectively, for a given log, which represent the full payload input to the given operation.
  outputSnapshotIds
  Array of string
  Lists the unique identifiers that correlate to each output snapshot, respectively, for a given log, which represent the full payload output from the given operation.
  managedByOrganization
  object
  Describes the Redox organization that owns and manages a given operation.
  id
  nullable, number
  Contains the unique identifier of the organization.
  name
  string
  Displays the human-readable name for the organization.
  snapshots
  required, Array of object
  Describes how the log payload looks at a specific moment during log processing. Snapshots show how and when data changed during log processing for troubleshooting or comparison purposes.
  id
  string
  Contains the unique identifier of the snapshot.
  Format: uuid
  name
  string
  Displays the human-readable name of the stage where the snapshot occurred.
  data
  nullable,
  Contains the log payload content at the time of the snapshot. This data could be an object, string, null, or undefined.
  dataFormat
  string
  Describes the language and format of the snapshot.
  customProcessing
  required, object
  Describes metadata and outcomes of operations you manage (e.g., filters, translations).
  filters
  Array of object
  Describes any customer-managed filters applied during log processing.
  operationId
  string
  Displays the unique identifier of this customer-managed operation.
  shouldFilter
  boolean
  Indicates whether the log should be sent (i.e., not filtered) or not sent (i.e., filtered).
  filters
  Array of object
  action
  required, string
  Describes the type of filter that will apply to the log. A block-all value indicates that any logs that meet the criteria will be blocked. A send value indicates that a log meeting the filter criteria will be allowed through.
  Possible Values: send, block-all
  filterVersion
  required, number
  Displays the version of the filter that was applied to the log. A filter's version number is incremented every time the filter is updated.
  outcome
  required, string
  Summarizes the outcomes of all the defined rules for this filter operation. If evaluated, all filter rules were evaluated; this doesn't mean all criteria was satisfied but that each rule was evaluated without encountering errors. If skipped, another filter ran before this one and blocked this log; in other words, this filter didn't need to be evaluated. If disqualified, the filter is invalid due to its configuration settings (e.g., invalid path syntax in one of the filters rules), so the filter failed to run.
  Possible Values: disqualified, evaluated, skipped
  rules
  required, Array of object
  path
  required, string
  Displays the JSON path of the fields which are compared against the filter criteria defined in the rule.
  outcome
  required, string
  Describes the result of an individual send-if filter rule. If satisfied, the filter rule's criteria was met, and the next filter rule in the sequence was evaluated. If unsatisfied, the filter rule's criteria wasn't met, so the log wasn't sent per the defined send-if filter. If skipped, the previous filter rule was unsatisfied, so this rule wasn't evaluated. If disqualified, the filter rule is invalid due to its configuration settings (e.g., invalid field path syntax).
  Possible Values: disqualified, satisfied, skipped, unsatisfied
  translations
  Array of object
  Describes any customer-managed translations applied during log processing.
  operationId
  string
  Displays the unique identifier of this customer-managed operation.
  translations
  Array of object
  translationSetLinkId
  string
  Contains the unique identifier of the translation set link, which applies the translation to the appropriate subscription and event type(s).
  Format: uuid
  translationSetId
  string
  Contains the unique identifier of the translation set, which defines the translation logic and is referenced in the translation set link.
  Format: uuid
  fields
  Array of object
  status
  string
  Describes the outcome of a given field's translation. If translated, the field was translated as expected. If field-not-found, the field wasn't found in the payload, so no translation occurred. If value-not-found, the value in the specified field didn't match the mapped value in the linked translation set, so no translation occurred.
  Possible Values: translated, field-not-found, value-not-found
  fieldPath
  string
  Contains the JSON path of the field to translate, as specified in the translation set.
  matchedPath
  string
  Contains the actual JSON for the matching translation value. For example, if the fieldPath is $.SomeArray[*].SomeProperty and the translation value was matched at the first item in the array, then the matchedPath would be SomeArray[0].SomeProperty.
  logType
  required, string
  Specifies the directionality of the traffic, whether asynchronous (i.e, uni-directional) or synchronous (i.e., bi-directional).
  Possible Values: sync, async
  source
  required, object
  Describes the system that initiated the log.
  id
  string
  Contains the unique identifier of the source.
  Format: uuid
  name
  string
  Displays the human-readable name of the source.
  organization
  object
  Identifies the Redox organization associated with this source.
  id
  integer
  Displays the unique identifier of the Redox organization.
  name
  string
  Displays the human-readable name of the Redox organization.
  communicationMethod
  string
  Describes the source's type of communication method to send and/or receive data.
  transmissionUniqueIds
  Array of string
  Contains the unique identifier(s) of the transmissions that the destination normally would've received; however, no data is sent to destinations when running log inspector.
  Format: uuid
  destination
  object
  Describes the intended endpoint of the log.
  id
  string
  Contains the unique identifier of the destination.
  Format: uuid
  name
  string
  Displays the human-readable name of the destination.
  organization
  object
  Describes the Redox organization associated with this destination.
  id
  integer
  Displays the unique identifier of the Redox organization.
  name
  string
  Displays the human-readable name of the Redox organization.
  communicationMethod
  string
  Describes the destination's type of communication method to receive and/or send data.
  communicationMethodFlavor
  string
  Describes a subset of communication method the destination uses, if applicable.
  subscription
  object
  Describes the connection between the log's source and destination.
  id
  string
  Displays the unique identifier of the subscription.
  dataModel
  string
  Identifies the Redox data model used to exchange data for a given subscription.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.