V1.0

get

/ec-dc-svc/rest/v1/studies/{studyId}/{mode}/subjectsettings/sdvsettings

Returns all the source data verification settings for a study.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SubjectSettingDto
Type: object
Subject setting data including start version, key/value, and auditing info.
Show Source
  • Key of the subject setting attribute. Possible values:
    • sequential_across_study_or_site
    • limit_screened_subjects
    • withdraw_subject_codebreak
    • limit_randomize_subjects
    • user_enters_screening_visit_date
    • user_edits_screening_visit_date
    • user_enters_randomization_visit_date
    • user_edits_randomization_visit_date
    • user_enters_dispensation_visit_date
    • user_edits_dispensation_visit_date
    • user_enters_non_dispensation_visit_date
    • user_edits_non_dispensation_visit_date
    • user_enters_optional_visit_date
    • user_edits_optional_visit_date
    • user_enters_withdraw_visit_date
    • user_edits_withdraw_visit_date
    • randomization_visit_date_additional_setting
    • dispensation_visit_date_additional_setting
    • can_dispensation_visit_be_skipped
    • can_non_dispensation_visit_be_skipped
    • separate_siteid_and_subjectid_hyphen
    • limit_study_status
    • limit_site_scr
    • limit_site_rand
    • limit_site_alerts
    • limit_site_status
    • limit_country_scr
    • limit_country_rand
    • limit_country_alerts
    • limit_country_status
    • padding_for_subject_id
    • max_randomize_subject
    • subject_alerts
    • max_screened_subject
    • subject_addition_allowed
    • subject_number_selection_allowed
    • subject_number_format
    • retry_partial_sdv_selection
    • notify_unsched_visit_failure_only
    • notify_screening_failure_only
    • notify_optional_visit_failure_only
    • notify_nondisp_visit_failure_only
    • notify_randomization_failure_only
    • notify_dispensation_failure_only
    • notify_subjcomplete_visit_failure_only
    • show_visit_window
    • notify_first_screened_in_study
    • notify_first_screened_at_site
    • notify_first_randomized_in_study
    • notify_first_randomized_at_site
    • allow_withdrawal_before_enrollment
    • allow_display_signature_elements
    • replace_subject_number_rand_number
    • code_data_for_new_and_screen_failed_subjects
    • blind_rand_number_enabled
    • replace_randomisation_enabled
    • replace_randomisation_prefix
    • replace_randomisation_max_limit
    • allow_rescreening
    • number_of_rescreen_allowed
    • lock_screen_data_on_failure
    • user_enters_rescreening_visit_date
    • user_edits_rescreening_visit_date
    • notify_rescreening_failure_only
    • replace_subject_number_enabled
    • assign_subject_number
    • allow_screen_fail_before_screened
    • limit_country_AF_status
    • limit_country_AF_scr
    • limit_country_AF_alerts
    • limit_country_AF_name
    • limit_country_AF_rand
    • limit_country_DZ_alerts
    • limit_country_DZ_rand
    • limit_country_DZ_status
    • limit_country_DZ_name
    • limit_country_DZ_scr
    • minimum_subject_number
    • allow_withdrawal_for_screen_failed
    • allow_completion_for_screen_failed
    • enable_assign_subject_number
    Example: assign_subject_number
  • Value of the subject setting attribute.
    Example: YES
  • Minimum Length: 0
    Maximum Length: 2048
    Comments or additional notes for this operation.
    Example: Enabled based on protocol
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) for the subject setting.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Object version number
    Example: 1
  • Minimum Length: 0
    Maximum Length: 255
    Reason for this operation or audit action.
    Example: Initial setup
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T00:00:00Z
Examples

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId
Back to Top