TrialKit comes pre-enabled with integrations to specific external tools to support specific customer objectives, but can also be integrated with any other API-enabled systems.
Ready-made Integrations
Apple Health
Fitbit / Google Health
Nmible - for making payments to Participants
Quest Diagnositics - for central labs
IDEXX Labs - for central labs
Google Drive - for automated data exports
Google Cloud Storage - for automated data exports
Google Gemini - for AI services
EMR - Site Health Record Integrations
While TrialKit does generally support EMR integrations through the availability of robust web APIs, here are a few more important questions to address when it comes to EMR integrations
Is there access to the EMR policies to ensure data can be pulled from it?
Are there more than one EMR being used in the study?
Is there someone who will be writing the integration between the targeted EMR and the study?
CDS does not provide the services to write EMR-specific integrations, but the platform does support the technical capability to accomplish that objective.
To overcome the lack of scalability in integrating with hospital-specific health records systems, TrialKit has native capabilities to bring in data from Apple health.
For example, if a study site uses Oracle Health EHR enabled to share data with Apple Health, patients can open Apple Health on their personal device, lookup their clinic/hospital, login to their patient portal, and download all their data like lab results, medications, immunizations, and allergies directly from the Cerner system to the device. TrialKit can then pull that data into the study database. This direct patient interaction bypasses the obstacles that site policies most often impose.