Import

Why it matters

flowchart LR
    External[External material] --> Import[Import]
    Import --> Workflow[Governed workflow]

Import explains how outside material enters TrialStack and becomes part of a governed workflow instead of remaining a disconnected upload event.

How it works

flowchart LR
    File[File or content] --> Request[Import request]
    Request --> Record[Relevant record model]

Imports bring external content or files into shared request flows that can be tracked, reviewed, and connected back to the relevant record model.

Trial imports

Trial import always creates a new governed Trial. JSON, PDF, and DOCX use the same import request and one visible workflow run, while the executor reflects the source format.

USDM JSON is mapped deterministically without AI or token use. The import retains the exact source, checksum, original USDM version, mapping provenance, unsupported content, and deterministic findings. Supported objects are written directly to their governed Trial owners.

PDF and DOCX retain the source as Media, extract structured content with source-block provenance, and pass that same content to the existing import operations for Trial Summary, Interventions, Trial Design, Schedule, Statistical, Safety, Randomization, Decisions, Participant Journeys, Retention, and Monitoring. Trial Summary owns imported protocol populations, cohorts, and planned enrollment; imports no longer create Recruitment versions. Those action runs are children of the import run and persist through their existing owners. Generated values remain drafts, and missing evidence produces empty values or findings rather than invented clinical data.

One failed action does not roll back successful actions. The parent run completes with findings so users can inspect or retry the affected action from the normal run and Trial surfaces.

The API flow is:

1. POST /api/imports with entityType: "trial", no targetEntityId, and a trial-import payload for usdm-json, pdf, or docx.
2. Poll GET /api/imports/{id} or open the returned WorkflowRun.
3. Use the returned trialId, findings, source evidence, and action-run identities to continue on the normal Trial and run surfaces.

When to use it

flowchart TD
    BringIn[Need to bring in material] --> Import[Import]
    AlreadyThere[Already governed] --> Skip[No import]

This concept matters when the team needs to bring source material, uploaded content, or reprocessed records into the workspace in a controlled way.

What to watch for

flowchart LR
    Import[Import] --> Owner[Owning workflow]
    Owner --> Review[Review path]

Import is not just file transfer. The important question is what workflow owns the result after the handoff. USDM persistence is deterministic; PDF and DOCX persistence is AI-generated draft content with visible findings. Neither path implies clinical approval.