v1.0

get

/ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/subjecttransfers

The API endpoint is designed to fetch all subject transfers for a given study, as indicated by the studyId path parameter.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : SubjectNumberTransferDto
Type: object
Show Source
  • Additional comment or note about the transfer.
    Example: Automated renumber after transfer
  • 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 number transfer record.
    Example: 1BC29B36F5D64B1B95F4BDBBCEA481BE
  • New subject number after transfer or renumbering.
    Example: SUBJ-0001-NEW
  • Object version number
    Example: 1
  • Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: MODIFIED
  • Randomization number assigned to the subject if applicable.
    Example: R-000123
  • Reason for the subject number transfer.
    Example: Site change
  • Software version number used when the record was generated.
    Example: 300
  • Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.
    Example: 42CE52A1AF9A48EBABA25A361F6EC0FE
  • 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
  • Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the user
    Example: 225B79C982104415886DE02BC73C1E1E
  • The end date until which the data is applicable or valid.
    Example: 2023-01-01T10:00:00Z
  • The timestamp marking the beginning of the validity period for this record version within the system.
    Example: 2023-01-01T09:00:00Z
Examples

400 Response

Bad request.
Body ()
Root Schema : RestResponse
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