Get a subject's events within a date range
get
/ec-dataintegration-svc/rest/v4.0/studies/{studyId}/{mode}/subjects/dateRange/{subjectId}
Retrieves the events for a specific subject within a specified date range. New properties are withdrawal or completion date and EHR link status. Used by Digital Gateway to retrieve events associated with a specific subject.
Rights: DataCaptureSubjectIntegrationGet and SubjectDataClassificationGet.
Rights: DataCaptureSubjectIntegrationGet and SubjectDataClassificationGet.
Request
Path Parameters
-
mode(required): string
Mode of the study. Accepts test, active, or training.Example:
test -
studyId(required): string
Study identifier in uppercase hex formatExample:
3F2504E04F8911D39A0C0305E82C3301 -
subjectId(required): string(uuid)
ID for the subject whose events you want to retrieve, as it appears in Clinical One.Example:
3F2504E04F8911D39A0C0305E82C3301
Query Parameters
-
endDate: string(date-time)
The ending date and time (optional) for which you want to get events. If you don't specify the time, the date range stops before midnight (23:59:59 UTC) for the specified date. The accepted date and time formats are: dd-MMM-yyyy HH:mm:ss.SSS, dd-MMM-yyyy HH:mm:ss, dd-MMM-yyyy HH:mm, or dd-MMM-yyyy.Example:
23-Oct-2025 14:35:47.123 -
startDate: string(date-time)
The starting date and time (optional) for which you want to get events. If you don't specify the time, the date range begins after midnight (UTC) for the specified date. The accepted date and time formats are: dd-MMM-yyyy HH:mm:ss.SSS, dd-MMM-yyyy HH:mm:ss, dd-MMM-yyyy HH:mm, or dd-MMM-yyyy.Example:
20-Oct-2025 14:35:47.123
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Subjects success.
Root Schema : schema
Type:
Show Source
array-
Array of:
object SubjectRespDto15
Subject response details including re-screening event instance number and all inherited subject properties
Nested Schema : SubjectRespDto15
Type:
objectSubject response details including re-screening event instance number and all inherited subject properties
Show Source
-
canBeCompleted: boolean
Indicates if the subject has met conditions to be completedExample:
true -
canBeReplaced: boolean
Indicates if the subject can be replacedExample:
true -
canBeUndoWithdrawn: boolean
Indicates if a withdrawn subject can be undoneExample:
true -
codeBreak: string
Code break note if applicableExample:
N -
comment: string
Minimum Length:
0Maximum Length:2048Comment for latest subject updateExample:Initial enrollment -
description: string
Minimum Length:
0Maximum Length:500Free text description for the subjectExample:Screened subject -
dob: string
(date-time)
Date of birth
-
ehrLinkStatus: number
EHR link status code for the subjectExample:
1 -
enrollmentFailure: string
Minimum Length:
0Maximum Length:255Reason for enrollment failure, if anyExample:Consent withdrawn -
enrollmentOverride: string
Minimum Length:
0Maximum Length:255Enrollment override note if appliedExample:Subject Enrollment Overridden -
eventType: string
Type of event associated with the subjectExample:
Screened -
freezedStatus: string
Freeze status of the subjectExample:
FROZEN -
fromStudyId: string
(uuid)
Origin study identifier from which the subject was transferred
-
gender: string
Minimum Length:
0Maximum Length:10Gender valueExample:[{"value":"1","label":"male"}] -
hasLockData: boolean
Indicates whether lock related data exists for the subjectExample:
false -
id: string
(uuid)
Unique identifier of the subject
-
incompleteVisits: integer
(int32)
Number of incomplete visits for the subjectExample:
1 -
informedConsentDate: string
(date-time)
Informed consent dateExample:
2025-09-25T09:00:00Z -
lastSigned: string
(date-time)
Timestamp when the subject was last signedExample:
2025-10-16T14:30:31.892Z -
lockedDateTime: string
(date-time)
Timestamp when the subject was lockedExample:
2025-10-16T14:30:31.892Z -
lockedInStudyVersion: string
Study version in which the subject is lockedExample:
3.0.0.4 -
lockedStatus: string
Lock status of the subjectExample:
UNLOCKED -
mhealthSubjectId: string
(uuid)
Identifier of the subject in mHealth system
-
objectVersionNumber: number
Object version number used for concurrency controlExample:
14 -
operationType: string
Operation type for the subject eventExample:
MODIFIED -
previousSubjectNumber: string
Previous subject number if renumbered or transferredExample:
SUBJECT-0001-OLD -
randomizationNumber: string
Randomization number for the subjectExample:
RND-001 -
reason: string
Minimum Length:
0Maximum Length:255Reason for latest subject updateExample:Protocol break happened -
replaceRand: string
Replacement randomization identifier if applicableExample:
Y -
reScreenEventInstanceNum: integer
(int32)
Event instance number for the re-screen event if presentExample:
2 -
screenFailureComment: string
Additional comment for screen failureExample:
Subject breached protocols -
screenFailureDate: string
(date-time)
Date when the subject was marked as screen failureExample:
2025-10-16T14:30:31.892Z -
screeningDate: string
(date-time)
Screening date if applicableExample:
2025-10-01T10:00:00Z -
screeningFailure: string
Minimum Length:
0Maximum Length:255Reason for screening failure, if anyExample:Inclusion criteria not met -
screeningNumber: string
Screening number assigned to the subjectExample:
SCR-0001 -
signedStatus: string
Signed status of the subjectExample:
SIGNED -
siteId: string
Site identifier in uppercase hex formatExample:
ABCDEF1234567890ABCDEF1234567890 -
softwareVersionNumber: number
Software version number associated with the eventExample:
14 -
sourceTimeStamp: string
(date-time)
Source system timestamp for the subject payloadExample:
2025-10-16T14:30:31.892Z -
state(required): string
Minimum Length:
0Maximum Length:100Lifecycle state of the subjectExample:ACTIVE -
stateDate: string
(date-time)
Timestamp when the subject transitioned to current stateExample:
2025-10-16T14:30:31.892Z -
studyCompletionDate: string
(date-time)
Date when the subject completed the studyExample:
2025-10-16T14:30:31.892Z -
studyId: string
Study identifier in uppercase hex formatExample:
ABCDEF1234567890ABCDEF1234567890 -
studyVersion(required): string
Study version stringExample:
3.0.0.1 -
subjectNumber(required): string
Minimum Length:
0Maximum Length:500Human readable subject numberExample:SUBJ-0001 -
subjectSiteSerialNumber: string
Site-level serial number assigned to the subjectExample:
SITE-0001-001 -
subjectStudySerialNumber: string
Study-level serial number assigned to the subjectExample:
STUDY-0001-001 -
subjectTransferId: string
(uuid)
Identifier of a subject transfer if applicable
-
subjNumSiteOrgId: string
Subject number site organization identifierExample:
SITE-ORG-0001 -
unResolvedQueries: integer
(int32)
Number of unresolved queries for the subjectExample:
2 -
userId: string
(uuid)
User identifier associated with the subject modification
-
verifiedStatus: string
Verified status of the subjectExample:
VERIFIED -
versionEnd: string
(date-time)
End timestamp of the subject version recordExample:
2025-10-16T14:30:31.892Z -
versionStart: string
(date-time)
Start timestamp of the subject versionExample:
2025-10-16T14:30:31.892Z -
withdrawalComment: string
Additional comment provided for withdrawalExample:
Subject breached protocols -
withdrawalDate: string
(date-time)
Date when the subject was withdrawnExample:
2025-10-16T14:30:31.892Z -
withdrawalReason: string
Reason provided when the subject is withdrawnExample:
Not applicable
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: string
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 -
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:
object