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.

String

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

String

Identifies the system that originates the message. If you're using OAuth keys, this value is required; if you're using legacy API keys, this value is optional since legacy keys are specific to a given originating system.
UUID

String

Displays the name of the system that originates 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

Record in Redox that corresponds to the communication sent from the source system to Redox.
Included in requests from Redox.

Numeric

Identifies the numeric value of the message created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

String

Record in Redox that corresponds to the communication sent from Redox to the destination endpoint.
Included in messages from Redox.

Numeric

Identifies the numeric value of the transmission created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

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

Visit Number.
A 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.

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

String

Descriptive label for this document.

DateTime

This time represents when this media was created.
ISO 8601 Format

DateTime

This time represents a clinical service timestamp with which this media is related.
ISO 8601 Format

String

The sender's Direct address, if one or both sides are using Direct messaging.

String

The recipient's Direct address, if one or both sides are using Direct messaging.

String

ID type of the ID for the Provider responsible for the document

String

First name of the Provider responsible for the document

String

Last name of the Provider responsible for the document

Array of Strings

List of credentials for the Provider responsible for the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

The authenticated status of the document.
True or False. If True, it is recommended to have Media.Authenticator filled out

String

ID of the provider who authenticated the document.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who authenticated the document

String

First name of the provider who authenticated the document

String

Last name of the provider who authenticated the document

Array of Strings

List of credentials for the provider who authenticated the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

Array of Objects

List of providers that should be notified when this document posts to the patient's chart

String

ID of the provider who should be notified.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who should be notified

String

First name of the provider who should be notified

String

Last name of the provider who should be notified

Array of Strings

List of credentials for the provider who should be notified.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

ID of the order assigned by the placing system

String

Name of the order assigned by the placing system

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.

String

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

String

Identifies the system that originates the message. If you're using OAuth keys, this value is required; if you're using legacy API keys, this value is optional since legacy keys are specific to a given originating system.
UUID

String

Displays the name of the system that originates 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

Record in Redox that corresponds to the communication sent from the source system to Redox.
Included in requests from Redox.

Numeric

Identifies the numeric value of the message created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

String

Record in Redox that corresponds to the communication sent from Redox to the destination endpoint.
Included in messages from Redox.

Numeric

Identifies the numeric value of the transmission created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

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

Visit Number.
A 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.

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

String

Descriptive label for this document.

DateTime

This time represents when this media was created.
ISO 8601 Format

DateTime

This time represents a clinical service timestamp with which this media is related.
ISO 8601 Format

String

The sender's Direct address, if one or both sides are using Direct messaging.

String

The recipient's Direct address, if one or both sides are using Direct messaging.

String

ID type of the ID for the Provider responsible for the document

String

First name of the Provider responsible for the document

String

Last name of the Provider responsible for the document

Array of Strings

List of credentials for the Provider responsible for the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

The authenticated status of the document.
True or False. If True, it is recommended to have Media.Authenticator filled out

String

ID of the provider who authenticated the document.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who authenticated the document

String

First name of the provider who authenticated the document

String

Last name of the provider who authenticated the document

Array of Strings

List of credentials for the provider who authenticated the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

Array of Objects

List of providers that should be notified when this document posts to the patient's chart

String

ID of the provider who should be notified.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who should be notified

String

First name of the provider who should be notified

String

Last name of the provider who should be notified

Array of Strings

List of credentials for the provider who should be notified.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

ID of the order assigned by the placing system

String

Name of the order assigned by the placing system

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.

String

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

String

Identifies the system that originates the message. If you're using OAuth keys, this value is required; if you're using legacy API keys, this value is optional since legacy keys are specific to a given originating system.
UUID

String

Displays the name of the system that originates 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

Record in Redox that corresponds to the communication sent from the source system to Redox.
Included in requests from Redox.

Numeric

Identifies the numeric value of the message created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

String

Record in Redox that corresponds to the communication sent from Redox to the destination endpoint.
Included in messages from Redox.

Numeric

Identifies the numeric value of the transmission created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

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

Visit Number.
A 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.

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

String

Descriptive label for this document.

DateTime

This time represents when this media was created.
ISO 8601 Format

DateTime

This time represents a clinical service timestamp with which this media is related.
ISO 8601 Format

String

The sender's Direct address, if one or both sides are using Direct messaging.

String

The recipient's Direct address, if one or both sides are using Direct messaging.

String

ID type of the ID for the Provider responsible for the document

String

First name of the Provider responsible for the document

String

Last name of the Provider responsible for the document

Array of Strings

List of credentials for the Provider responsible for the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

The authenticated status of the document.
True or False. If True, it is recommended to have Media.Authenticator filled out

String

ID of the provider who authenticated the document.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who authenticated the document

String

First name of the provider who authenticated the document

String

Last name of the provider who authenticated the document

Array of Strings

List of credentials for the provider who authenticated the document.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

Array of Objects

List of providers that should be notified when this document posts to the patient's chart

String

ID of the provider who should be notified.
This ID is often required for Inpatient Visits.

String

ID type of the ID for the provider who should be notified

String

First name of the provider who should be notified

String

Last name of the provider who should be notified

Array of Strings

List of credentials for the provider who should be notified.
e.g. MD, PhD

Object

Provider's address

String

Street address

String

City

String

State

String

ZIP

String

County

Array of Strings

Provider's email address(es)

String

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

Object

Provider's location

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

ID of the order assigned by the placing system

String

Name of the order assigned by the placing system

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.

String

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

String

Identifies the system that originates the message. If you're using OAuth keys, this value is required; if you're using legacy API keys, this value is optional since legacy keys are specific to a given originating system.
UUID

String

Displays the name of the system that originates 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

Record in Redox that corresponds to the communication sent from the source system to Redox.
Included in requests from Redox.

Numeric

Identifies the numeric value of the message created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

String

Record in Redox that corresponds to the communication sent from Redox to the destination endpoint.
Included in messages from Redox.

Numeric

Identifies the numeric value of the transmission created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

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

Array of patients to filter results on.
If multiple patients are provided, media associated with any of the patients will be returned.

Array of Objects

List of IDs and ID types that identify the patient.
If multiple identifiers are provided, only patients with all identifiers will be considered.

String

ID of the Patient

String

ID Type for the corresponding ID of this patient (ie. MRN, EHRID)

Array of Strings

Array of patient visits to query on.
If multiple visits are provided, media associated with any of the patient visits will be returned.

Array of Strings

Array of document types to query on.
The type of media to retrieve (E.g. Consent Form, Treatment Plan)

Array of Strings

Array of document identifiers to query on.

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.

String

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

String

Identifies the system that originates the message. If you're using OAuth keys, this value is required; if you're using legacy API keys, this value is optional since legacy keys are specific to a given originating system.
UUID

String

Displays the name of the system that originates 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

Record in Redox that corresponds to the communication sent from the source system to Redox.
Included in requests from Redox.

Numeric

Identifies the numeric value of the message created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

String

Record in Redox that corresponds to the communication sent from Redox to the destination endpoint.
Included in messages from Redox.

Numeric

Identifies the numeric value of the transmission created in Redox.
(Deprecated. Slated for removal on or after Apr. 30, 2023. Use Meta.Logs[].ID instead).

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

ID for the patient

String

Type of ID.
E.g. MRN, EPI

String

Visit Number.
A VisitNumber is highly recommended so that the document can be associated with a specific visit

String

File type of the document.
E.g. PDF, JPG

String

Name of the file

String (Base64)

Redox BLOB URI

String

Type of Document.
This is the document type the file will be associated with (E.g. Consent Form, Treatment Plan)

String

Unique identifier for this document.
This ID is required in order to update the document

String

Descriptive label for this document.

DateTime

This time represents when this media was created.
ISO 8601 Format

DateTime

This time represents a clinical service timestamp with which this media is related.
ISO 8601 Format