V1

post

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

This endpoint creates a new subject transfer record in the system. Provide all details for a subject transfer in the request body.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Subject transfer request payload. Contains the subjectTransfer object representing details of a transfer.
Show Source
Nested Schema : SubjectTransferDto
Type: object
Represents a subject transfer between sites used for API request/response bodies.
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Additional comment or note about the subject transfer.
    Example: Moved subject to new site
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred from.
    Example: 938D23FA6B7241CCA41BD627E5DB60DA
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the subject transfer record.
    Example: A1B2C3D4E5F64789AABBCCDDEEFF1122
  • Minimum Length: 0
    Maximum Length: 500
    New subject number after transfer or renumbering.
    Example: SUBJ-0001-NEW
  • Minimum Length: 0
    Maximum Length: 255
    Reason for the subject transfer.
    Example: Site change
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the subject being transferred.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Minimum Length: 0
    Maximum Length: 500
    Unique subject Number representing the patient/participant enrolled in the study.
    Example: SUBJ-0001
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred to.
    Example: 699EF3745FC545589F186D2198F3C65E
  • Timestamp representing the start of the version for this subject transfer record.
    Example: 2023-01-01T09:00:00Z
Examples

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : SubjectTransferDto
Type: object
Represents a subject transfer between sites used for API request/response bodies.
Show Source
  • Minimum Length: 0
    Maximum Length: 2048
    Additional comment or note about the subject transfer.
    Example: Moved subject to new site
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred from.
    Example: 938D23FA6B7241CCA41BD627E5DB60DA
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the subject transfer record.
    Example: A1B2C3D4E5F64789AABBCCDDEEFF1122
  • Minimum Length: 0
    Maximum Length: 500
    New subject number after transfer or renumbering.
    Example: SUBJ-0001-NEW
  • Minimum Length: 0
    Maximum Length: 255
    Reason for the subject transfer.
    Example: Site change
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the subject being transferred.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • Minimum Length: 0
    Maximum Length: 500
    Unique subject Number representing the patient/participant enrolled in the study.
    Example: SUBJ-0001
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred to.
    Example: 699EF3745FC545589F186D2198F3C65E
  • Timestamp representing the start of the version for this subject transfer record.
    Example: 2023-01-01T09: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