Back to Topics

Secure Subject Tickets

A guide to maintaining strict research compliance by generating massive, anonymized ID batches and secure passwords for your clinical deployments.

What is the Ticket Generator capable of?

In clinical trials and academic research, protecting participant identity is paramount. The Ticket Generator allows you to instantly spin up hundreds of secure credentials, ensuring that your study remains strictly double-blind and IRB-compliant.

Total Anonymization

Participants log in using auto-generated alphanumeric passcodes. Your data is tied only to an ID (e.g., PAT001), ensuring researchers never see personally identifiable information.

Double-Blind Grouping

Split a batch into "Treatment" and "Control" groups, and let the system randomly assign participants. You distribute the tickets without knowing who is in which group.

Dynamic Clinical Secrets

Generate unique, random medical values (like lab numbers) attached to each ticket. These can be injected directly into your questions to give every student a different patient case.

Bulk CSV Control

Export your generated credentials to Excel with one click for easy distribution. Or, import your own custom CSV if you already have existing hospital IDs you want to use.


Part 1: Generating Basic Tickets

Creating a batch of simple credentials takes less than ten seconds.

1. Define Your Batch & Prefix

Give your batch an internal name (e.g., "Phase 1 Nursing Cohort"). Next, create a Subject ID Prefix (max 6 characters). The system will automatically append a three-digit sequence to this prefix.

Prefix: ONC Resulting IDs: ONC001, ONC002, ONC003...
2. Set Volume & Generate

Leave all other toggles off. Scroll down to Total Number of Subjects, enter how many tickets you need (up to 450 per batch), and click Build. The system will instantly generate the IDs along with highly secure, random 6-character passcodes for each.


Part 2: Advanced Batch Tools

Splitting into Groups (A/B Testing)

Toggle Split Batch into Groups if your trial requires cohort division.

  • Defining Cohorts: Click "Add Another Group" to create as many arms as you need (e.g., Control: 50, Placebo: 50, Treatment: 50).
  • Randomize Assignment: If checked, the system will shuffle the IDs so that ONC001 might be Treatment, and ONC002 might be Placebo. This is crucial for maintaining double-blind integrity when you hand out the login tickets.
Generating Unique Codes (Secrets)

The Secrets engine attaches random, hidden numbers to each specific ticket. You can generate these by typing an explicit range or by using the letter x as a wildcard placeholder.

Format TypedNumber Range GeneratedExample Output
1.00-3.001.00 to 3.00 (Precise boundaries)2.15
10-5010 to 50 (Precise whole numbers)42
xx10 to 99 (Wildcard)47
xxx100 to 999 (Wildcard)802
xx.x10.0 to 99.9 (Wildcard)36.4
How to use Secrets in your Questions

If you created a secret using either method (e.g., 10-50 or xx.x), you can type {{Secret 1}} directly into your Question Bank text. When Participant 1 logs in, their question will say: "The patient's temperature is 38.2 C." When Participant 2 logs in, their question will say: "The patient's temperature is 36.4 C."


Part 3: Managing Credentials

Exporting to CSV

Once your batch is built, it will appear in the Active Ticket Batches list. Click the green CSV button to download a master spreadsheet. This sheet contains the Subject ID, Passcode, Group Assignment, and any Secrets generated. You can use this sheet to perform a mail-merge or cut it into physical strips to hand to your participants.

Importing your own Custom CSV

If you already have a roster of Hospital IDs or Student IDs that you must use, you do not need to use our generator. You can click Import CSV to upload your own list.

CSV Format Rules:

  • Your CSV must have headers.
  • Column 1 must be exactly: Subject ID
  • Column 2 must be exactly: Passcode
  • Column 3 (Optional) can be: Assigned Group
  • Column 4 (Optional) can be: Status (Write "Used" or "Available")