...
The Inform Dexcom integration defaults to using the Dexcom US server since the majority of our clients and users are US-based. Any user without a country timezone in their Validic user profile will be assumed to be a US user.
A non-US user will receive a marketplace error if they attempt to authorize data sharing when a country code non-US timezone has not been specified in their Validic user profile.
To use the Dexcom EU server, a country non-US timezone must be specified in each user’s Validic user profile.
Specifying a non-US country timezone in the user profile will direct the user to the Dexcom EU server for authorization and data syncing.
Therefore, if you intend to use the Dexcom EU server, you must have Dexcom EU API credentials from Dexcom AND you must specify a non-US country code timezone when provisioning users in Inform. Any non-US users that are already provisioned in Inform must be updated to include the correct non-US country code timezone.
Historical Data
Validic captures a maximum of 7 days of Dexcom historical data. This would be the 7 days prior to the Dexcom user first syncing to Validic. While Dexcom may be able to have more than 7 days of historical data, Validic chose to only pull in 7 days due to the sheer volume of intraday data that would have to be captured, stored, and then made available in the Inform API.
...
Validic does not get timezone information from Dexcom. Therefore, the user is asked to provide their home timezone when connecting to Dexcom via the Validic Marketplace. If they had previously provided this timezone information, they will not be prompted for it again. The offset_origin for Dexcom will be "user_defined".
| Info |
|---|
If you have non-US users, please note that a non-US timezone must be set in the Validic user profile. See the “Regional Servers“ section above for more details. |
As a result, if a user is traveling across timezones, their Dexcom data will still show their timezone (utc_offset) as their base or home timezone. If this same user has other devices in use, like Fitbit or Apple Health, that do provide updated timezone information from the user's phone, you may see different utc_offsets depending on the data source.
...