Things to know about Validic-Abbott Integration
- Toni Connelly
This article pertains to: Inform (v2)
The Validic Inform API suports Abbott CGM data as cgm, or high-frequency data. But you already knew that.
What you may not know is that the implementation of the Abbott cgm data includes some things that are worth calling out to ensure that you are properly capturing all possible data for your patients.
Regional Servers
The Inform Abbott integration works with the Abbott US server only (for those Abbott users located in the United States).
Historical Data
Validic captures a maximum of 30 days of Abbott historical data. This would be the 30 days prior to the Abbott user first syncing to Validic. While Abbott may be able to have more than 30 days of historical data, Validic chose to only pull in 30 days due to the sheer volume of cgm data that would have to be captured, stored, and then made available in the Inform API.
Getting ongoing data from Abbott
As noted on this page, High-Frequency Data , Validic is getting the CGM data from Abbott in either 5 minute or 15 minute intervals via hourly data pulls, depending on whether the user has a Freestyle Libre 2 or Freestyle Libre 3 CGM. Each new hourly pull of data from Abbott retrieves all data for the last 3 UTC days (see “Data Retrieval Intervals“ below for more details).
Because of the 1 hour delay that Abbott has on the CGM data, this means that CGM records will include the readings from up to the previous hour. For example, at 10 am UTC the payload would include the readings from midnight UTC up to 9 am UTC.
A single cgm record in the Validic Inform API represents one UTC day.
Data Retrieval Intervals
We pull 3 UTC days of data for cgm records about once an hour
We pull 7 UTC days of data for cgm records about once per day
We pull up to 30 UTC days of historic data for Abbott cgm when the user initially connects to Abbott in the marketplace (dependent on the organization’s historical fetch settings).
Duplicate Data
If a patient fully disconnects Abbott 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 readings to check for possible duplicates.
Timezones
For more specifics on time handling for Abbott cgm, please see the article: https://help.validic.com/space/VCS/4383113217/Abbott+Time+Representations
Device Identifiers
The Abbott device identifier represents the identifier for the cgm transmitter. If the sensor is swapped but the transmitter remains the same, then the device identifier is not changed. In this case, the new_sensor boolean will be the only way for you to determine that a sensor swap has occurred. 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.