Documentation / Assets

Trials

Trials are the operational spine of TrialStack — they hold study identity, eligibility, scientific structure, and every connected record teams need to plan, execute, and govern a clinical study.

TrialStack dashboard overview showing usage, recent activity, and record navigation.

Run the study from one record

flowchart LR
    Scattered[Scattered study context] --> Trial[Trial record]
    Trial --> Design[Design and start-up decisions]
    Trial --> Context[Connected operational context]
    Trial --> Governance[Governed review and history]

Teams rarely fail because they have no study data. They fail because study context is scattered across documents, spreadsheets, and memory with no single governing anchor.

A trial record gives the team one durable place to answer questions such as:

  • what is this study, who is it for, and what does it measure
  • which organizations, sites, contacts, and interventions participate
  • what eligibility criteria, endpoints, and objectives define the scientific structure
  • whether changes to the study are traceable and reviewable

That matters because almost every other record in TrialStack — organizations, sites, contacts, interventions, personas, media, systems — becomes operationally meaningful only once it is connected back to the trial it supports.

Keep context connected

flowchart LR
    Trial[Trial] --> Orgs[Organizations]
    Trial --> Sites[Sites]
    Trial --> Contacts[Contacts]
    Trial --> Interventions[Interventions]
    Trial --> Personas[Personas]
    Trial --> Systems[Systems]
    Trial --> Media[Media]
    Trial --> Modules[Specialized modules]
    Modules --> Workflows[Design, review, and start-up workflows]

TrialStack treats the main trial record and the specialized trial workflow modules as related but different surfaces.

  • the main trial record holds the cross-study description, classification, criteria, objectives, outcomes, identifiers, and all entity relationships
  • the specialized modules hold deeper operational work such as design, approval, monitoring, recruitment, retention, safety, schedule, engagement, and statistical detail

That split matters because teams can keep one clear study anchor without forcing every trial-facing workflow into one overloaded form. The main record is the study-wide spine; the modules are where discipline-specific work deepens.

Teams usually get the most value from the trial record when they need to make cross-cutting study decisions, not when they are producing background documentation.

The page is especially useful when a team needs to:

  • establish the foundational study identity before connecting sites, contacts, and interventions
  • define the eligibility framework — indications, inclusion, and exclusion criteria
  • structure the scientific measurement model — endpoints, objectives, estimands, outcomes
  • frame the risk–benefit justification and treatment context
  • maintain governance across changes with full version history, compare, and restore

Trials also connect in both directions. A team can start from the trial and connect relevant entities, or start from an organization, site, or intervention and link back to the study it supports.

On the page

The trial page is section-based rather than flat. It is built around fifteen governed sections, with specialized modules and relationship tabs alongside.

SurfacePurposeWhat users do there
SummaryMaintain the study-wide description and structureCapture identity, classification, criteria, endpoints, objectives, estimands, outcomes, identifiers
Trial modulesHold deeper operational work by disciplineMove into design, approval, monitoring, recruitment, retention, safety, schedule, statistical, engagement
Relationship tabsKeep operational context visibleReview linked organizations, sites, contacts, interventions, personas, systems, media, documents, evidence packs

Most teams use the page in a rhythm like this:

  1. Create the trial record and establish the study identity.
  2. Define eligibility criteria, endpoints, and objectives.
  3. Connect organizations, sites, contacts, interventions, and personas.
  4. Move into specialized modules as planning and execution deepen.
  5. Review history, compare versions, or restore earlier states when the change path matters.
flowchart TD
    Page[Trial page] --> Summary[Summary sections]
    Page --> Modules[Trial modules]
    Page --> Relationships[Relationship tabs]
    Summary --> Core[Identity, criteria, objectives, outcomes]
    Modules --> Discipline[Design, approval, monitoring, recruitment, retention, safety, schedule, statistical, engagement]
    Relationships --> Context[Organizations, sites, contacts, interventions, personas, systems, media, documents, evidence packs]

A strong trial record is not just a protocol paraphrase. It gives the team a governed study anchor they can actually make cross-cutting decisions with.

Good trial records usually do six things well:

  • they establish a clear study identity with title, protocol number, phase, and design classification
  • they define eligibility criteria that are specific enough to be operationally useful
  • they structure the scientific measurement model so endpoints, objectives, and estimands remain explicit
  • they keep the risk–benefit justification visible and connected to treatment context
  • they connect every relevant entity — org, site, contact, intervention, persona, system — so operational context is never orphaned
  • they preserve a traceable change history because trial modifications have downstream impact

That is why only Title is required. The point is not to force completion of every section. The point is to capture the information that supports real downstream decisions.

Review, history, and other governed behavior are covered in the Workflows section and apply here in the same way they do across the rest of the governed record model. All fifteen sections support verification status tracking.

Overview

This section establishes the foundational study identity. It is the first thing reviewers see and the anchor for every downstream section.

LabelDescriptionType
TitleThe primary study title that identifies this trial across the systemText
Protocol NumberFormal protocol identifier used for regulatory submissions and cross-system referenceText
Responsible Party TypeWho holds responsibility for registration and reportingSelect
Study TypeWhether the study is interventional, observational, or another design categorySelect
PhaseClinical development phase that frames the study scopeSelect
Primary PurposeThe main scientific objective — treatment, prevention, diagnostic, or otherSelect
Interventional Study ModelDesign structure such as parallel, crossover, single group, or factorialSelect
Control TypeWhat the study compares against — placebo, active comparator, dose-comparison, or otherSelect
Enrollment CountTarget number of participants the study plans to enrollNumber
MaskingWhether the study uses single-blind, double-blind, open-label, or other masking approachesSelect
Masked RolesWhich roles are masked — participant, investigator, outcome assessor, care providerMulti-select
Therapeutic AreasDisease or therapy categories the study addressesMulti-select
SynopsisHigh-level study summary intended for quick orientationRich text
Background and RationaleScientific and operational rationale that justifies the studyRich text

Risks

This section captures the known potential risks that should remain visible as part of the risk–benefit justification.

LabelDescriptionType
CategoryRisk classification such as medical, procedural, or psychologicalSelect (badge)
TitleShort identifier for the riskText
DescriptionDetailed explanation of the risk and its contextRich text

Benefits

This section captures the known potential benefits that balance the risk profile.

LabelDescriptionType
CategoryBenefit classification such as therapeutic, diagnostic, or quality-of-lifeSelect (badge)
TitleShort identifier for the benefitText
DescriptionDetailed explanation of the benefit and expected impactRich text

Reference Therapies

Reference therapies frame the treatment context by identifying comparator treatments, standard-of-care references, or rescue medications.

LabelDescriptionType
Linked InterventionOptional link to an intervention record for cross-referencingCombobox
Therapy TypeWhether the therapy serves as comparator, rescue, standard-of-care, or otherSelect (badge)
Rationale for SelectionWhy this therapy was chosen as a comparator or referenceRich text
Dose RationaleJustification for the dosing regimenRich text
FrequencyHow often the reference therapy is administeredText
DurationLength of the reference therapy periodText
Supply SourceWhere the reference therapy is sourcedSelect
NotesAdditional context about the reference therapyRich text

Medication Restrictions

Medication restrictions define which medications participants must avoid and under what conditions.

LabelDescriptionType
NameMedication or therapy nameText
CategoryRestriction classification such as prohibited, conditional, or washout-requiredSelect (badge)
Washout PeriodRequired washout duration before study participationText
RationaleWhy this restriction exists and its scientific justificationRich text

Indications

Indications identify the medical conditions or disease areas the study targets.

LabelDescriptionType
NameIndication or condition nameText
Is PrimaryWhether this is the primary or secondary indicationToggle
DescriptionAdditional context about the indication and its relevanceRich text

Inclusion Criteria

Inclusion criteria define who is eligible to enter the study.

LabelDescriptionType
TextThe full inclusion criterion statementRich text

Exclusion Criteria

Exclusion criteria define who should not be enrolled in the study.

LabelDescriptionType
TextThe full exclusion criterion statementRich text

Endpoints

Endpoints define the specific measurements the study uses to evaluate outcomes.

LabelDescriptionType
TitleName of the endpointText
LevelWhether primary, secondary, or exploratory — filterable across the tableSelect (badge)
Data TypeNature of the measurement such as continuous, binary, time-to-event, or categoricalSelect (badge)
DescriptionDetailed specification of what the endpoint measures and howRich text

Objectives

Objectives state the scientific questions the study is designed to answer.

LabelDescriptionType
NameShort objective titleText
LevelWhether primary, secondary, or exploratory — filterable across the tableSelect (badge)
DescriptionFull objective statement with contextRich text

Estimands

Estimands define the treatment effect the study intends to estimate, following ICH E9(R1) guidance.

LabelDescriptionType
NameShort estimand titleText
LevelWhether primary, secondary, or exploratory — filterable across the tableSelect (badge)
DescriptionFull estimand definition including population, variable, intercurrent events, and summary measureRich text

Discontinuation Criteria

Discontinuation criteria define the conditions under which a participant or the study itself may be stopped.

LabelDescriptionType
TitleShort name for the discontinuation criterionText
ScopeWhether the criterion applies at participant or study levelSelect (badge)
CategoryClassification such as safety, futility, efficacy, or administrativeSelect (badge)
Estimand StrategyHow this intercurrent event is handled in the estimand frameworkSelect
Is MandatoryWhether discontinuation is required or discretionary when the criterion is metToggle
DescriptionFull explanation of the criterion and its operational implicationsRich text

Subject Replacement Rules

Replacement rules define how and when participants who discontinue can be replaced to maintain study power.

LabelDescriptionType
TitleShort name for the replacement ruleText
Trigger CriterionWhich discontinuation criteria activate this replacement rule — cross-references the Discontinuation Criteria sectionMulti-select
Replacement Window ValueHow long the replacement window stays openNumber
Replacement Window UnitTime unit for the replacement windowSelect
Max ReplacementsUpper limit on how many replacements are allowed under this ruleNumber
DescriptionFull explanation of the replacement logic and any constraintsRich text

Outcome Measures

Outcome measures define registry-facing measurements used for reporting and compliance.

LabelDescriptionType
TitleName of the outcome measureText
TypeWhether primary, secondary, or otherSelect (badge)
Time Frame ValueMeasurement window durationNumber
Time Frame UnitTime unit for the measurement windowSelect
DescriptionFull specification of what is measured and howRich text

Secondary Identifiers

Secondary identifiers capture external reference numbers used for cross-system tracking and regulatory submissions.

LabelDescriptionType
IdentifierThe external identifier valueText
TypeKind of identifier such as registry, regulatory, or internalSelect (badge)
DomainWhich system or domain the identifier belongs toSelect (badge)