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
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
active -
studyId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
A1B2C3D4E5F647839ABCDEF012345678
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Nested Schema : SubjectNumberTransferDto
Type:
Show Source
object-
comment: string
Additional comment or note about the transfer.Example:
Automated renumber after transfer -
fromSiteId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred from.Example:
938D23FA6B7241CCA41BD627E5DB60DA -
id: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the subject number transfer record.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE -
newSubjectNumber: string
New subject number after transfer or renumbering.Example:
SUBJ-0001-NEW -
objectVersionNumber: number
Object version numberExample:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
MODIFIED -
randNumber: string
Randomization number assigned to the subject if applicable.Example:
R-000123 -
reason: string
Reason for the subject number transfer.Example:
Site change -
softwareVersionNumber: number
Software version number used when the record was generated.Example:
300 -
subjectId: string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
42CE52A1AF9A48EBABA25A361F6EC0FE -
subjectNumber: string
Unique subject Number representing the patient/participant enrolled in the study.Example:
SUBJ-0001 -
toSiteId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site the subject is transferred to.Example:
699EF3745FC545589F186D2198F3C65E -
userId: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the userExample:
225B79C982104415886DE02BC73C1E1E -
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.Example:
2023-01-01T10:00:00Z -
versionStart: string
(date-time)
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.
Root Schema : RestResponse
Type:
Show Source
object-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
-
status: string
-
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectNested Schema : details
Type:
objectDetailed 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