Understand impact of subject number assignments on study data
Learn how the timing of subject number assignment - whether during subject addition or after submitting screening forms - affects study data, data propagation in downstream applications, and overall system behavior.
Note:
When a subject number is assigned after the screening forms are submitted, there is common downstream impact regardless of whether the screening is successful or fails:- Subject data is available for all applicable integrations, reports, CRF Submit archives, Oracle Clinical One Analytics datasets, and Oracle Central Coding.
If your study integrates with Oracle Central Coding and the Code data for new and screen failed subjects setting on the Study Settings tab is disabled, Oracle Central Coding data will not be sent until the subject is enrolled or randomized.
- Custom JavaScript rules and Source Data Verification (SDV) workflows are triggered.
- Manual queries can be raised on subject data, while automated queries are triggered by custom JavaScript rules and validation rules.
- EHR linking occurs later by selecting the appropriate option on the Manage drop-down.
When a subject number is assigned depends on the study configuration and user actions. The following table shows the differences across use cases and their impact on study data.
| Subject number assignment type and use case | Study data impact |
|---|---|
| Subject numbers are assigned upon addition - site user adds and screens a subject (whether successfully or not) |
|
| Subject numbers are assigned upon addition - site user cancels or leaves the screening forms |
|
| Subject numbers are assigned upon screening - site user screens a candidate (whether successfully or not) |
|
| Subject numbers are assigned upon screening - site user collects data but cancels or leaves forms without submitting data |
|
Parent topic: Specify study, enrollment, and visits settings