DateTime

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

Boolean

Indicates whether the request is a test or not.

String

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

String

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

String

Displays the name of the system initiating the message.

Array of Objects

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.

String

Identifies the endpoint that the request is directed to.
UUID

String

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

Array of Objects

Contains the log identifier(s) for the request.

String

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

String

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

String

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.

Array of Objects

List of IDs and ID types that identify the patient

String

Patient's first name

String

Patient's middle name or middle initial. For patients with multiple middle names, all their middle names are included in this field.

String

Patient's last name

String

Patient's date of birth.
In ISO 8601 format

String

Patient's social security number

Boolean

Indicates if the patient is deceased

DateTime

Date and Time the patient was proclaimed deceased.
ISO 8601 Format

String

Patient's home phone number.
In E. 164 Format. (e.g. +16085551234)

String

Patient's office phone number.
In E. 164 Format. (e.g. +16085551234)

String

Patient's mobile phone number.
In E. 164 Format. (e.g. +16085551234)

Array of Strings

Patient's email address(es)

Object

Patient's home address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of strings

Patient-level notes

String

First name of the contact

String

Middle name of the contact

String

Last name of the contact

Object

Address of the contact

String

Street address

String

City

String

State

String

ZIP

String

County

String

Home phone number.
In E. 164 Format. (e.g. +16085551234)

String

Office phone number.
In E. 164 Format. (e.g. +16085551234)

String

Mobile phone number.
In E. 164 Format. (e.g. +16085551234)

Array of string

Email address(es) of the contact person

Array of strings

Role of this contact for the patient.
e.x. Employer, Emergency Contact

String

Number for the visit that contains the flowsheet.
VisitNumber is highly recommended so that the document can be associated with a specific visit

String

Account Number.
An ID that can span several visits often related to the same issue - pregnancy, surgeries, research study, etc.

String

DateTime of visit or appointment.
ISO 8601 Format

Object

Location of the patient. This may be used for validation or to identify your application/device.

String

Type of location.
Examples: Clinic, Department, Home, Nursing Unit, Provider's Office, Phone

String

Facility.
Example: Community Hospital

Array of Objects

List of IDs specific to this facility

String

An ID specific to this facility

String

The source or system to which this ID pertains.
Could be an OID or a human-readable name

String

Department

Array of Objects

List of IDs specific to this department

String

An ID specific to this department

String

The source or system to which this ID pertains.
Could be an OID or a human-readable name

String

Room.
Example: 136

String

Bed.
Example: B

Array of objects

List of values to be added to the flowsheet

String

Units of the value.
If the Code is "Heart Rate", this may be "BPM"

String

Codeset used to identify the code

String

Description of the flowsheet row

Array of Strings

Notes about the observation

String

Optional code indicating who made the observation.
Typically represents an actual person, but may also be linked to device in some EHRs

String

ID type of the ID for the Observer

String

Optional code indicating who made the observation

String

Optional code indicating who made the observation

Object

Reference range for the observation.
Numeric observation values will use the low and high properties. Non-numeric observation values will put the normal value in the text property.

Numeric

Lower bound for a normal observation

Numeric

Upper bound for a normal observation

String

The normal value for non-numeric observations