Personas

Trials provide the governing trial record. Personas provide structured participant context that helps teams reason about that trial.

Why it matters

• a team needs role-based or perspective-based context around a trial
• persona work should stay grounded in the trial it informs
• reviewers need to understand which trial a persona view belongs to
• the team wants to generate personas from the trial itself
• engagement questionnaires need persona-based answers or feedback

From each side

• Use Trials for the operational trial record, including generating or linking personas that matter for that trial.
• Use Personas for the maintained participant profiles behind those trial connections.

On the trial side, personas are not only reference material. They can also be used to:

• track eligibility and enrollment priority for a specific persona-trial relationship
• generate personas from trial context
• drive participant engagement questionnaire review from a persona perspective

Generating several personas

Each requested persona has its own generation run, progress, and result. Requesting four personas queues four runs, which can generate concurrently when your organization’s AI capacity allows. Each completed run saves its persona independently, so a failed run does not discard the other results.

The API returns a batch identifier, requested and queued counts, independently tracked workflows with candidate ordinals, and any candidate ordinals that could not be queued. No special request header is required. Partial acceptance keeps the accepted runs active; review their results before requesting more personas.

Independent candidates use their batch ordinal to distribute recruitment segments and narrative focuses while respecting trial evidence and existing-persona exclusions. They do not see concurrent sibling outputs, so this planning does not guarantee uniqueness.