Skip to content
Clarrio.ai

Therapeutic area · Incl. long-term follow-up after gene therapy

Longitudinal data for rare-disease research

Rare disease populations are small, dispersed and followed for years. Clarrio.ai collects longitudinal data remotely and across centers so no observation is wasted. Align clinical, treatment and behavioral information on one shared longitudinal timeline, where available and appropriate to the program.

What Clarrio.ai captures

  • Disease-specific PROs
  • Caregiver-reported outcomes
  • Function and mobility tasks
  • Event diaries
  • Genetic and lab results
  • Records from multiple centers

The evidence gap

Small populations cannot afford incomplete records

In rare disease, a study may include tens of patients across many countries. Each missed visit or incomplete questionnaire is a meaningful loss of statistical power, and traveling to a specialist center is a real burden for patients and caregivers.

Natural history data is often scarce, and one-time or gene therapies may require long-term follow-up over many years. Sustaining that follow-up through site visits alone is costly and difficult for families.

Natural history

Disease progression data is limited and scattered across centers.

Gene therapy follow-up

Multi-year follow-up obligations strain sites and families.

Pediatric conditions

Caregivers report on behalf of children; their burden matters.

Functional decline

Mobility and function change slowly and need dense measurement.

The challenge

Few patients, long horizons, scarce data

Rare disease patients are few and geographically dispersed, so every data point matters and site visits are costly for families. Natural-history data is often thin, and one-time and gene therapies require years of long-term follow-up. Relying on periodic site visits produces sparse records and high participant burden, with function and caregiver experience between visits largely unrecorded.

Toggle the chart to compare what a visit-based record shows with what the continuous record shows for the same synthetic patient.

Functional score (0–100) over 120 days

Observations2

Events in periodNot visible

Events with no nearby visit3 of 3

Site visits capture two points. Remote measures and caregiver reports show the course in between, including a temporary decline the visits missed.

Illustrative · synthetic data

Dispersed

Travel burden

Families may travel long distances for each assessment, limiting how often data is collected.

Natural history

Thin baselines

Comparators depend on sparse, inconsistent historical data.

Follow-up

Years, not months

Long-term follow-up after gene therapy is hard to sustain through site visits alone.

How Clarrio.ai addresses the gap

Collection, integration and analytics, designed for this area

  1. 01

    Remote-first collection

    PROs, caregiver reports and function measures completed at home.

  2. 02

    Multicenter record

    One longitudinal record across referral centers and countries.

  3. 03

    Flexible schedules

    Protocols that adapt to disease course and family needs.

  4. 04

    Governed sharing

    Consent-driven access for sponsors, registries and investigators.

Data captured

Three layers of data, kept distinct

Select a layer. Exact sources depend on deployment configuration and data permissions.

Captured from patients or caregivers in the Patient App.

  • Disease-specific PROs
  • Caregiver-reported outcomes
  • Function and mobility tasks
  • Event diaries

Product workflow

How the record is built, step by step

Select a step to see what happens. Sources are captured through the Patient App and integrations, harmonized on the Platform and summarized by Intelligence.

Sources

  • Disease-specific PROs
  • Functional & mobility tests at home
  • Caregiver reports
  • Genomics & labs
  • Records from any center

Clarrio.ai workflow

Outputs

  • Natural-history dataset
  • LTFU record
  • Evidence package

Stakeholder outputs

Role-specific views of the longitudinal record

Each role receives a different view of the same longitudinal record. Values are synthetic.

Clinical development

Follow-up tracker

Status of every participant in long-term follow-up, with completeness by measure.

Clarrio.ai / Follow-up trackerSynthetic
  • Participants in LTFU86Across centers
  • Due this month12Remote functional test
  • Completeness91%Required measures, last 90 days

Caregiver

Weekly check-in

Caregivers report function and daily life in a few minutes, from home.

Clarrio.ai / Weekly check-inSynthetic
  • Mobility this weekReportGuided questions
  • Notable eventsOptionalIllness, falls, hospital visits
  • Next remote testFriReminder set

Medical affairs

Natural-history view

Aggregated trajectories by genotype or age band, from consented participants.

Clarrio.ai / Natural-history viewSynthetic
  • CohortsBy genotypeConsented, de-identified
  • MeasuresFunctional, PROsHarmonized
  • ExportReadyWith data dictionary

Worked examples

Two illustrative scenarios

Pediatric participant and caregiver

Gene-therapy follow-up

  1. Year 0

    Treatment; enrolled in remote follow-up.

  2. Monthly

    Caregiver check-ins and home functional tests.

  3. Year 1

    Site visit uses the year of remote data as context.

  4. Years 2–5

    Follow-up continues with fewer trips.

Illustrative · synthetic data

Patient organization and sponsor

Building a natural history

  1. Month 0

    Families enroll across countries.

  2. Months 1–12

    Consistent PROs and functional measures.

  3. Month 12

    Harmonized dataset available for analysis.

Illustrative · synthetic data

FAQ

Rare diseases questions

Research & operational outputs

Research and operational deliverables

Patient journey map

Diagnosis, treatments and outcomes across centers on one line.

Longitudinal evidence map

Which variables exist for which patients, and when.

Natural history cohort view

Progression trends across a dispersed cohort.

Follow-up compliance report

Long-term follow-up status for every participant.

Value for each stakeholder

Pharmaceutical & biotech

Natural history and long-term follow-up data with less site burden.

Specialist centers

Continuity across referral pathways.

CROs & registries

Remote collection across countries with completeness tracking.

Patients & caregivers

Fewer trips and a supportive app that respects their time.

Program evaluation

Where Clarrio.ai can create measurable value

These are the KPIs we agree with customers before deployment, measured against their own baseline. Data coverage, patient experience and clinical outcomes answer different questions. Higher engagement alone does not demonstrate better health or lower utilization.

Explore benefits and evidence
LeverHow it is measured
Participant retentionParticipants remaining in follow-up relative to enrolled
Data completenessExpected timepoints with data
Visit burdenIn-person visits per participant per year
Cost per complete recordCollection cost relative to complete longitudinal records

Illustrative use case

Long-term follow-up after gene therapy

Clinical development, illustrative

Long-term follow-up after gene therapy

  1. Year 0

    Participants consent to remote follow-up at treatment.

  2. Years 1–2

    Quarterly PROs and function tasks at home; annual site visit.

  3. Ongoing

    Compliance report shows each participant's status.

  4. Year 5

    Longitudinal dataset supports regulatory reporting.

Illustrative · synthetic data

Neuromuscular disordersMetabolic and lysosomal disordersGene therapy follow-upPediatric rare disease

Clarrio.ai has joined Mayo Clinic Platform's Solutions Studio, supporting its mission to advance interoperable, data-driven healthcare innovation. This does not imply endorsement or clinical validation.

  • Consent and data governance
  • Privacy-by-design principles
  • Role-based access
  • Flexible deployment
  • Data residency options
  • FHIR-based interoperability
  • Research-use positioning, not diagnosis

Design Your Rare Disease Data Strategy

Design Your Rare Disease Data Strategy

Evidence interpretation

Long follow-up magnifies differences in observation coverage

Align records to meaningful study milestones and distinguish patient reports from caregiver assessments. Small, dispersed cohorts need explicit eligibility, instrument suitability and gap documentation. Natural-history observations are not automatically a valid comparison group.

Benefits in practice

From rare diseases observations to a useful review

Pharma & biotech

Start with the evidence question a decision-maker actually needs answered

Routine records can describe encounters and prescriptions while leaving daily function, symptom burden and experience under-observed. Adding remote data can fill selected gaps, but a large dataset is not automatically decision-ready. Population selection, questionnaire suitability, exposure timing and missing observations can all change the interpretation of a longitudinal analysis.

  1. 01

    Specify the evidence objective

    Define the population, observation window, outcome concept and intended decision before selecting sources.

  2. 02

    Collect and reconcile

    Combine appropriately scoped Patient App reports with available clinical and device data in the Platform; keep reported experience separate from recorded events.

  3. 03

    Review before analysis

    Use source-aware review to inspect context and quality. Agree variable definitions, analysis methods and limitations with the study team.

For the professional team

Clinical development, medical affairs and HEOR teams can work from a common record while asking different questions. Clinical operations needs coverage by site and timepoint; an evidence analyst needs definitions and provenance; medical affairs needs an account of the population and study limitations. Those outputs should not be treated as interchangeable.

For patients, members and caregivers

Participants have a structured way to contribute the experience that encounters may miss. Questions should be meaningful, proportionate and appropriate to the population. Explain the study purpose, who reviews submissions and whether reporting receives an individual response; a research diary is not an emergency service.

For payers and program funders

A payer-facing evidence package should connect patient experience to a defined decision question and relevant population. Include baseline characteristics, follow-up, missingness and the analysis method. Patient-reported experience can complement other evidence, but it does not alone establish comparative effectiveness, economic value or a coverage recommendation.

Illustrative review brief
Population definition
Eligibility, enrollment dates and relevant baseline characteristics
Longitudinal variables
Source, units, assessment window and missing-data conventions
Evidence limitations
Selection, confounding and generalisability to the decision population

Workflow illustration · not a customer result or live record

What to evaluate before making a claim

Assess suitability against the research question: provenance, completeness, accuracy and relevance. Predefine the analysis rather than choosing a favorable pattern after viewing the results. Publication and payer use require appropriate scientific review.

Explore evidence and evaluation

Payers & health economics

Distinguish richer patient context from evidence of value

Claims and encounter datasets can describe recorded utilization without fully capturing function, experience or the practical burden of a program. Patient reports add a different perspective, but they can be incomplete or drawn from a population unlike the members covered by a payer. The task is to establish whether those observations are suitable for a specific appraisal question, not to turn engagement into a savings claim.

  1. 01

    Define the appraisal question

    Specify the relevant covered population, decision, comparator where needed and evaluation horizon.

  2. 02

    Assess data suitability

    Review provenance, participation, measurement windows and missingness before examining results.

  3. 03

    Build the evidence account

    Combine appropriately governed patient experience with relevant clinical or utilization evidence; document assumptions and limits for expert appraisal.

For the professional team

HEOR and population-health teams can examine how reported experience varies across the observation period and which groups are represented. A useful output explains the denominator behind a measure and the observations excluded from analysis. Governance must also define the permitted purpose of any linkage to payer-held data.

For patients, members and caregivers

The member perspective should remain visible in a program evaluation: burden, everyday function, access and what participants consider meaningful. Reporting should not become an unexplained condition of receiving services. Explain the collection purpose and permitted uses in a way members can understand.

For payers and program funders

Decision support means an inspectable evidence package, not an automatic reimbursement verdict. Include the target population, relevant baseline differences, data sources, follow-up and limitations. Cost and utilization conclusions need appropriate data and analysis; neither can be inferred from app activity or observation coverage.

Illustrative review brief
Decision context
Population, appraisal question and evaluation horizon
Suitability account
Provenance, completeness, accuracy and relevance
Interpretation boundary
What the analysis can support and what remains uncertain

Workflow illustration · not a customer result or live record

What to evaluate before making a claim

Separate program participation, patient-reported experience, clinical outcomes and economic endpoints. Define each before collection, use an appropriate comparison where the question requires one and examine whether findings transfer to the covered population.

Explore evidence and evaluation

Patients, members & caregivers

Give the person contributing data a meaningful place in the workflow

A person can complete many questions without understanding why they are being asked or who will read the answers. Device observations may look precise while missing personal context. A useful longitudinal journey starts with the person's priorities and makes the reporting purpose, burden and review arrangements understandable.

  1. 01

    Explain the purpose

    Agree what the care or research program needs to learn and what participation involves.

  2. 02

    Capture lived experience

    Use appropriate reports alongside available observations; distinguish the patient's own answers from caregiver observations.

  3. 03

    Bring context to review

    Discuss a dated interval with the responsible professional, including what is missing and what matters to the person.

For the professional team

Teams gain context for a more specific conversation, but should not assume that a missed report means a person disengaged. Accessibility, fatigue, language and connectivity may affect reporting. Define support and review arrangements before introducing new questions.

For patients, members and caregivers

Patients and members can keep a dated account of experiences they might otherwise forget. Caregivers can contribute observations when appropriately scoped, without replacing the person's own perspective. Personal patterns invite discussion; they are not instructions or proof that a particular routine produced an outcome.

For payers and program funders

A program's apparent reach can hide who could not participate. Payers and commissioners should examine access, reporting burden and representativeness alongside outcome evidence. Patient experience is an important perspective in appraisal, not a shortcut to an economic conclusion.

Illustrative review brief
Personal context
The person's own priorities and dated reports
Reporting perspective
Patient answer or appropriately identified caregiver observation
Review arrangement
Who reviews reports, when and through which contact pathway

Workflow illustration · not a customer result or live record

What to evaluate before making a claim

Ask whether reporting is understandable, manageable and meaningful. Examine completion alongside accessibility and support needs. A high completion rate alone does not show that people feel heard or that a program has improved their health.

Explore evidence and evaluation

Request a demo

Explore disease, treatment and behavior together

Explore how clinical, treatment and behavioral information align around your program and the research or review questions your team needs to answer.

Book a demo

Opens the Calendly booking page in a new tab.

Prefer to write first? Send an inquiry and the team will reply.