V1.0

get

/ec-dc-svc/rest/v1.0/studies/{studyId}/{mode}/subjects/screeningnumber

Returns a list of subjects with their screening numbers and site details for the specified study.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful retrieval of subject screening numbers.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SubjectScreeningNumberResponseDto
Type: object
Subject screening number and related site details
Show Source
  • unique identifier (UUID, 32-character uppercase hexadecimal string) for a subject
    Example: 9876543210ABCDEF1234567890ABCDEF
  • Object version number
    Example: 3
  • Unique subject Number representing the patient/participant enrolled in the study.
    Example: SCR-00123
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: 40DB4EF4847849CCB24EFCCB71CDA436
  • Organization ID (UUID, 32-character uppercase hexadecimal string) for subject number at site
    Example: 40DB4EF4847849CCB24EFCCB71CDA436
Examples

400 Response

400
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