Timezones
Data provided over our API should be assumed to be in UTC.Datetime format
Our API accepts most ISO 8601 formats.Examples:
Example:
Common Datetimes
There are some datetimes that are common across a lot of Elation’s API resources. It can be useful to understand what each describes. Some specific resources will includedocument_date- The datetime this document “happened” in the world. Sometimes changeable in-app to help provider’s better represent a patient’s longitudinal history. Often the same as
chart_datebelow. - e.g. A CCDA import includes data about a visit that happened sometime in the past will have a document date that represents when that visit occurred.
- The datetime this document “happened” in the world. Sometimes changeable in-app to help provider’s better represent a patient’s longitudinal history. Often the same as
chart_date- The datetime this document appeared in the patient’s chart.
- Often the same as
document_dateabove but can be different if the document represents historical data.
signed_date- The datetime a document was signed by a provider.
created_date- The datetime when a resource was created in Elation’s platform. Will often be the same as the
chart_dateanddocument_dateabove.
- The datetime when a resource was created in Elation’s platform. Will often be the same as the
deleted_date- Most resources in Elation’s platform are “soft” deleted to ensure we can recover data and provide more accurate reporting.
- The datetime this resource was marked as deleted.
last_modified_date- The datetime when this resource was last updated.