Enrichment

Send data to a third party for processing.

This data model has event types that allow you to:

  • submit code entries for processing; or
  • receive processed code entries.

NormalizationQuery

Submit code entries (each in a given category) to a third party for normalization, or processing.

Beta
Dev preview

Request Body Schema

  • Meta
    required, object
    • DataModel
      required, string
      Reliable

      Enrichment

    • EventType
      required, string
      Reliable

      NormalizationQuery

    • EventDateTime
      string, null
      Reliable

      Displays the UTC date and time that an outgoing request is delivered or an incoming request is received.
      ISO 8601 Format

    • Test
      boolean, null
      Reliable

      Indicates whether the request is a test or not.

    • Source
      object

      Contains the information for the system initiating the message, including the source ID and name.
      Included in messages from Redox

      • ID
        string, null
        Reliable

        Identifies the system initiating the message. If you have multiple OAuth API keys per environment type, this value is required. If you have only one OAuth API key per environment type, or you're using legacy API keys, this value is optional.
        UUID

      • Name
        string, null
        Reliable

        Displays the name of the system initiating the message.

    • Destinations
      Array of object

      Contains the information for the endpoint(s) receiving the request. A request must contain at least one destination, but asynchronous requests can have more than one destination. Synchronous requests like queries can only support one destination.
      Required when sending data to Redox.

      • ID
        string, null
        Reliable

        Identifies the endpoint that the request is directed to.
        UUID

      • Name
        string, null
        Reliable

        Displays the name of the endpoint that the request is directed to.

    • Logs
      Array of object

      Contains the log identifier(s) for the request.

      • ID
        string, null
        Reliable

        Identifies the request log(s) that correspond to this request. You can use this value to locate the relevant log in the Redox dashboard for support and reference.
        UUID

      • AttemptID
        string, null
        Reliable

        Identifies the request log attempt value, which is useful when retries are possible.
        UUID

    • FacilityCode
      string, null
      Possible

      Code for the facility related to the message.
      Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.

  • Entries
    required, Array of object

    A list of entries to be normalized. The maximum number of entries that can be included is 100.

    • Category
      required, string
      Reliable

      The category of values in which to find this normalization entry.
      Categories currently supported: Problem.

    • EntryID
      string, null
      Possible

      The identifier of the specific entry to be normalized. If not provided, Redox generates an identifier to populate this field in the NormalizationQueryResponse so that you can match the normalized entry to the submitted entry.

    • Code
      string, null
      Probable

      Code for the value to be normalized by the third-party vendor.
      *You must include either code value or description, or you can provide both. *

    • Codeset
      string, null
      Probable
      Value Set

      Code set used to identify the value to be normalized by the third-party vendor.
      *For example: ICD-10-CM, ICD-9-CM, SNOMED CT. *

    • Description
      string, null
      Probable

      Description of the value to be normalized by the third-party vendor.
      *You must include either code value or description, or you can provide both. *

Example
json
1
{
2
"Meta": {
3
"DataModel": "Enrichment",
4
"EventType": "NormalizationQuery",
5
"EventDateTime": "2024-12-20T18:11:36.537Z",
6
"Test": true,
7
"Source": {
8
"ID": "7ce6f387-c33c-417d-8682-81e83628cbd9",
9
"Name": "Redox Dev Tools"
10
},
11
"Destinations": [
12
{
13
"ID": "af394f14-b34a-464f-8d24-895f370af4c9",
14
"Name": "Redox EMR"
15
}
16
],
17
"Logs": [
18
{
19
"ID": "d9f5d293-7110-461e-a875-3beb089e79f3",
20
"AttemptID": "925d1617-2fe0-468c-a14c-f8c04b572c54"
21
}
22
],
23
"FacilityCode": null
24
},
25
"Entries": [
26
{
27
"Category": "Problem",
28
"EntryID": "Diagnosis-0000000001-0",
29
"Code": "R07.0",
30
"Codeset": "ICD-10",
31
"Description": "Pain in throat"
32
}
33
]
34
}