RIDLY/Health corpora/Medication outcomes
Medication outcomes / Feasibility review

Medication Safety & Adherence

Cross-condition medication histories, reported doses, missed doses and symptom observations over time.

Request corpus feasibility Review the scope
Available for feasibility inquiries. Data access, cohort coverage and permitted uses require verification before a license is offered.

Define the corpus

Assess a cross-condition corpus for medication persistence, self-reported adherence and patient-reported experiences. Define exposures, observation windows and confounders before evaluating associations with symptoms or outcomes.

Fields to assess

  • Medication records and reported dose events
  • Reported missed doses and adherence patterns
  • Medication changes and concurrent treatments
  • Time-stamped symptoms and patient-reported outcomes

Field-level coverage, missingness and provenance are confirmed during feasibility review. Listed modalities are not a promise of availability.

Project applications

  • Adherence and persistence research
  • Polypharmacy and treatment pathways
  • Safety-signal feasibility
  • Medication-related model evaluation

Data interpretation

Reported medication use is not dispensing confirmation. Symptom timing alone does not establish a confirmed adverse drug reaction or a causal safety finding.

Cohort and delivery specification

Request the condition definition, unique participant count, geography, observation period, follow-up distribution, field coverage and update schedule. The specification distinguishes self-reported observations, device measurements and clinical-record-derived fields.

Clinical coding, measurement units, data dictionaries, missingness and de-identification are reviewed for the proposed delivery. Clinical images and reports are assessed separately from original DICOM studies; genetic test summaries are assessed separately from raw variants, sequencing and omics matrices.

Licensing and due diligence

Annual licenses, defined-project access and refreshes can be discussed after feasibility review. Research, AI evaluation, model training, derivative models, sublicensing and exclusivity require specific written permissions. Patient recontact is not included in an inquiry or implied by a data license.

Source provenance, the legal supplier or controller and its authority to license are disclosed during buyer due diligence. These profiles may draw on overlapping populations; counts are not added across products.

Tell us the cohort you need.

Include conditions, required fields, follow-up and intended use. No patient records are needed to make an inquiry.

Contact RIDLY