V1.0

get

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

Returns detailed subject information including screening, randomization, completion and re-screen event data as well as study/site context. Supports re-screening enabled events. Includes all current and previous subject properties as per the latest API model.

Request

Path Parameters
  • Mode of the study, accepts: test, active, or training.
    Example:
    test
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    3F2504E04F8911D39A0C0305E82C3301
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    1BC29B36F5D64B1B95F4BDBBCEA481BE

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Subject information with screenfail dates retrieved successfully. The response includes all relevant current and historical subject and screening event fields.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SubjectRespDto15
Type: object
Subject response details including re-screening event instance number and all inherited subject properties
Show Source
Examples

400 Response

Bad request - invalid subject ID or parameters.
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