...
As noted on this page,https://helpdocs.validic.com/docs/high-frequency-data , Validic is getting the CGM data from Dexcom in 5 minute intervals via hourly data pulls. Each new hourly pull of data from Dexcom looks at the timestamp of the last record received and then adds 5 seconds to that time to look for new data. retrieves all data for the last 3 UTC days.
Because of the 1 hour delay that Dexcom has on the CGM data, this means that CGM records will include the readings from up to the previous hour. For example, at 10am 10 am UTC the payload would include the records up to 9amreadings from midnight UTC up to 9 am UTC. A single cgm record in the Validic Inform API represents one UTC day.
Duplicate Data
If a patient fully disconnects Dexcom from their Validic user and then reconnects that same user within 30 days, it is highly likely that the data pulled in upon reconnection will include duplicate data that you have already received. You can use the Validic "id" and "checksum" to check for data you may have already consumed. You would want to check the "time" and "value" pairs of the CGM records to check for possible duplicates.
...
For more specifics on time handling for Dexcom cgm, please see the article: https://help.validic.com/space/VCS/4272259073/Dexcom+Time+Representations
Device Identifiers
The Dexcom device identifier represents the combination of the cgm sensor and transmitter. If either changes, then the device identifier is changed. So, if the sensor is swapped but the transmitter remains the same, then the device identifier is changed. And if the transmitter is changed, then the device identifier is changed. The device identifier is included in the sources object of the cgm record in the Validic Inform API.
Scenarios that Dexcom data wouldn’t be available in their cloud
...