V5.0

put

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

WithdrawalDate and StudyCompletionDate added. WithdrawalDate/StudyCompletionDate is stored as a part of this API for subject Withdraw/Complete actions respectively.WithdrawalDate/StudyCompletionDate is mandatory for changing a subject to Withdrawn/Complete state respectively

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:
    2FC29B36F5D64B1B95F4BDBBCEA481BE
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example:
    EDC29B36F5D64B1B95F4BDBBCEA481BE
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : SubjectDto13
Type: object
Subject properties indicating Screening Number
Show Source
Examples

Back to Top

Response

Supported Media Types

200 Response

Updated subject details returned if update successful.
Body ()
Root Schema : SubjectRespDto13
Type: object
Subject details including screening, randomization, completion status and withdrawal information
Show Source
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