V2.0

post

/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/subjects/migratesubject

Migrates a subject to current study context. Accepts a object, fully specifying subject number, site, state and timestamp. Returns the saved response with status and full migration metadata.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Core subject data for migration request
Show Source
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
    Example: AABBCCDDEEFF1234567890ABCDEF1234
  • Timestamp when the migration was triggered/sourced
    Example: 2025-12-01T09:50:00Z
  • Minimum Length: 0
    Maximum Length: 100
    States of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_Failed.
    Example: Active
  • Minimum Length: 0
    Maximum Length: 500
    External subject number identifier
    Example: SUBJ-0301
Examples

Back to Top

Response

Supported Media Types

200 Response

Migration successful, SubjectMigrationResponseDTO returned.
Body ()
Root Schema : SubjectMigrationResponseDTO
Type: object
Intermediate subject migration state, including subject audit/meta fields, event and version, and transfer 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