An abstract base data type for all device events.
An array of annotations.
An array of associations for the resource.
Clock drift offset, expressed as milliseconds.
Conversion offset, expressed as milliseconds.
String representation of a Tidepool User ID. Old style IDs are 10-digit strings consisting of only hexadeximcal digits. New style IDs are 36-digit UUID v4
String representation of a Tidepool User ID. Old style IDs are 10-digit strings consisting of only hexadeximcal digits. New style IDs are 36-digit UUID v4
Globally unique to device and repeatable with each upload, e.g. device make and model with serial number
Revision history of the event
Location information associated with the resource. One or both of name
and gps
must be specified.
String representation of a Tidepool User ID. Old style IDs are 10-digit strings consisting of only hexadeximcal digits. New style IDs are 36-digit UUID v4
An array of 1 to 100 notes.
External origin information for the source of the resource.
Grab bag field for data that isn't yet part of the data model. The maximum size is 4K bytes.
An array of tags.
A string timezone name from the IANA timezone database
Time zone offset, expressed as positive or negative number of minutes from UTC.
Data type
An upload identifier; this field should be the uploadId of the corresponding upload record
A string timezone name from the IANA timezone database
A string ID. Added to each event during data processing in the Tidepool Uploader or upon ingestion by the platform data ingestion service.
A time change event represents an instance when a diabetes device user changed the display date & time settings on the device. An accurate history of time change events is crucial as Platform uses the most recent set of time change events, raw log from a device's records and user's selection of timezone to translate relative (local time) timestamps of device records into UTC timestamps. This is to align all diabetes device timelines. For further information, please see "Bootstrapping" to UTC.
All the relevant data from the time change event is stored in various fields on an embedded change object.
Contains the following properties:
- From
- To
- Method
When a device's date & time is updated, the to, from and method fields should be included within the change embedded object on a time change event. The from field details the date & time the device is being changed from (the old date & time). The to field details the date & time the device is being changed to (the new date & time). Both the from and to properties are formatted as ISO 8601 timestamps without any offset from UTC specified; this is the exact same "relative" timestamp format used for device time.
The method field on the change object details whether the time change was manual (user-initiated) or automatic (initiated by the device).
{
"type": "deviceEvent",
"subType": "timeChange",
"change": {
"from": "2018-05-14T08:17:08",
"to": "2018-05-14T07:20:33",
"agent": "manual"
},
"clockDriftOffset": 0,
"conversionOffset": 0,
"deviceId": "DevId0987654321",
"deviceTime": "2018-05-14T18:17:08",
"guid": "7a91b3bc-2808-4c92-8769-3526db11ce41",
"id": "0ccaad06f9104c098595cf6e871edc09",
"time": "2018-05-14T08:17:08.814Z",
"timezoneOffset": 600,
"uploadId": "SampleUploadId"
}
{
"type": "deviceEvent",
"subType": "timeChange",
"change": {
"from": "2018-05-14T08:17:08",
"to": "2018-05-14T07:20:33",
"agent": "manual"
},
"clockDriftOffset": 0,
"conversionOffset": 0,
"deviceId": "DevId0987654321",
"deviceTime": "2018-05-14T18:17:08",
"time": "2018-05-14T08:17:08.815Z",
"timezoneOffset": 600,
"uploadId": "SampleUploadId"
}
{
"type": "deviceEvent",
"subType": "timeChange",
"change": {
"from": "2018-05-14T08:17:08",
"to": "2018-05-14T07:20:33",
"agent": "manual"
},
"_active": true,
"_groupId": "abcdef",
"_schemaVersion": 0,
"_version": 0,
"clockDriftOffset": 0,
"conversionOffset": 0,
"createdTime": "2018-05-14T08:17:13.815Z",
"deviceId": "DevId0987654321",
"deviceTime": "2018-05-14T18:17:08",
"guid": "2f17e38d-a39a-4116-a11c-5f014ea9ddd4",
"id": "8f3abbd0fe4f49879f1bd8b2356c1942",
"time": "2018-05-14T08:17:08.815Z",
"timezoneOffset": 600,
"uploadId": "SampleUploadId"
}