Trials

This is a dual-bound connection. The same junction links a site to a trial and a trial to a site. Both directions share the same underlying record.

Why it matters

• a study is executed at one or more sites with specific roles and named investigators
• reviewers need to understand which site activity belongs to which trial
• site readiness, capacity, and investigator assignment must stay connected to the right study
• the junction captures site code, role, and principal investigator for operational clarity

Dual-bound relationship

flowchart LR
  S[Site] -- "role · PI · version" --> T[Trial]
  T -- "site code · role · PI · version" --> S

In the product

The site record lists connected trials with role and principal investigator context directly on the tab.

Connecting from the site side captures the target trial, role, optional site code, and principal investigator.

Existing links can be updated in place when the site code, role, or principal investigator changes.

Junction fields

From the site page (site → trial)

Column	Description
Role	The site’s role in the trial — maps to trialSiteRole dictionary. Default when connecting: principal_site
PI	The name of the principal investigator assigned to this site for the trial
Version	Junction version counter

From the trial page (trial → site)

Column	Description
Site Code	The trial-specific code assigned to this site
Role	Same trialSiteRole value
PI	Same principal investigator name
Version	Junction version counter

Operations

Action	From site page	From trial page
Connect	Pick a trial (default role: principal_site)	Pick a site
Disconnect	Remove the trial link	Remove the site link
Reconnect	Update role / PI	Update site code / role / PI

From each side

• Use Sites for the site record.
• Use Trials for the governing study record.