At this stage, some UCAM records are associated with incorrect device_id, as previously some device_ids were not present as an option to select in UCAM. Some study sites took the approach to 'temporarily' assign a incorrect ID, which (if taken as truth) results in wrong associations and data linking. Luckily, in these cases, all (as far as we understand) a note was added to indicate this. As such, we are currently excluding any records with content in the deviations field.
Once the UCAM API is live, the branch is integrated, and all study sites confirmed that all these cases have been corrected, we can remove the above linked restriction.
At this stage, some UCAM records are associated with incorrect
device_id, as previously somedevice_ids were not present as an option to select in UCAM. Some study sites took the approach to 'temporarily' assign a incorrect ID, which (if taken as truth) results in wrong associations and data linking. Luckily, in these cases, all (as far as we understand) a note was added to indicate this. As such, we are currently excluding any records with content in thedeviationsfield.Once the UCAM API is live, the branch is integrated, and all study sites confirmed that all these cases have been corrected, we can remove the above linked restriction.