Build robust digital clinical trials with real-world data using no code
All your health information in one place
Simple and free daily symptom tracker
From ingestion and aggregation of raw data, to standardization and harmonization of disparate data types
Standardize & classify healthcare codes and concepts
Uplift & transform patient data to optimize your workflow
Compute hierarchical condition category (HCC) risk adjustment profiles
Privacy-preserving record linking across data sources and use cases
Securely match patient records in 2 simple steps
Reference guides, tutorials, and tools to develop your own participant experiences with the MyDataHelps APIs and SDKs
Reference guides, tutorials, and resources for using MyDataHelps Designer
Reference guides, tutorials, and tools for using the Orchestrate APIs
Manage your developer account and explore the Orchestrate APIs
Case studies, blogs, and white papers
Journal articles from partners leveraging CareEvolution’s platform
Webinars, conferences, and product educational resources
News articles and press releases
How we protect your data
Explore examples to get an idea of what’s possible with decentralized clinical trials and research
Collect high-quality data, fast—save your time and budget
Privacy-preserving record linkingacross data sources and use cases
Privacy-preserving record linking (PPRL) is a mechanism for securely matching patient data across sources.
Traditionally, healthcare data interoperability implementations have used master patient indexes with a centralized source of demographic information to perform record linking. Using privacy-preserving record linking (PPRL) instead improves upon traditional implementations.
Before storing a record, the PPRL performs an irreversible hash operation on the demographic data. All matching processes use the hashed values, thus “blinding” the data.
By one-way hashing plaintext strings to long sequences of semantically meaningless numbers and letters, patient data is more secure. This strategy ensures that patient demographic data stored in a centralized index is unrecoverable.
Learn more
Identity’s PPRL techniques perform the vast majority of linking hands-off, but allows for manual review where appropriate.
The Identity API has modern, cloud native architecture.
Demographic information is cleaned so comparing this information yields meaningful results.
Identity determines a final link status using multiple linking strategies, including deterministic and probabilistic record linking.
Identity is based on a mature, complex set of algorithms developed and refined by CareEvolution over the past 15+ years.
Identity performs this matching process for all demographic fields to determine which records belong to the same individual. It minimizes false positives by only linking records when there is high confidence of a match.
Before storing a record, Identity performs an irreversible hash operation on the demographic data. The service only stores and performs match operations with the hashed values, not the original values. This makes it “blinded.”
Read white paper
Learn more about how the Identity PPRL works.
CareEvolution’s Orchestrate technology and APIs liberate, aggregate, standardize, enrich, and transform data to power patient-centric use cases.
