[Deprecated]: V1.0
get
/ec-dc-svc/rest/v1/studies/{studyId}/{mode}/visitstatus
Deprecated: Retrieves the list of visits status for a event ID. If the event ID is null, then it lists all the visit status records for a subject.
Request
Path Parameters
-
mode(required): string
Mode of the study. Accepts test, active, or training.Example:
test -
studyId(required): string(uuid)
ID of the study for which you want to get the list of subjects.Example:
E6C7BC17E0F041D5B79B21A165911AC3
Query Parameters
-
eventId: string
Visit ID from Designer for which you want to retrieve the visit details.
-
subjectId: string
Subject ID for which you want to retrieve the visits.
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 VisitsStatus
Details of the visit for screening.
Nested Schema : VisitsStatus
Type:
objectDetails of the visit for screening.
Show Source
-
associatedStudyVersion: string
Minimum Length:
0Maximum Length:100Associated study version, if visit is linked to another protocol version.Example:3.1.0.2 -
comment: string
Minimum Length:
0Maximum Length:2048Comment regarding the last change made to the entity.Example:Imported via migration tool. -
designStudyVersion: string
Design version for the study when visit was enerated.Example:
3.1.0.2 -
display: string
Display indicator flag (Y/N), whether this visit should display in UIs.Example:
Y -
doseHoldAction: string
Holds any dose hold action taken on this visit.Example:
ENABLE -
dynamicAllCycles: string
Indicates if visit is part of dynamic all cycles (Y/N).Example:
N -
eventId: string
Unique identifier(UUID, 32-character uppercase hexadecimal string) representing the clinical event like Screening, Visit 1 etc.Example:
D1AABBCCDDEEFF112233445566778899 -
eventInstanceNum: integer
(int32)
Numeric value representing the instance number of the event. Used for repeated or unscheduled visits. It is null for scheduled events.Example:
1 -
freezedStatus: string
Frozen status of the record can have values NOT_APPLICABLE, FROZEN.Example:
Freezed -
id: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) for visit status.Example:
AABBCCDDEEFF00112233445566778899 -
leadingDataelementId: string
Unique Identfier ( (UUID, 32-character uppercase hexadecimal string) of the leading data element for this visit, if any.Example:
EEDD00112233445566778899AABBCCDD -
lockedDateTime: string
(date-time)
Date/time when the visit was locked (if applicable).Example:
2025-10-02T12:00:00Z -
lockedStatus: string
Lock status specifically for the visit start date.Values can be LOCKED, UNLOCKED, NEVER_LOCKED, NOT_APPLICABLEExample:
UNLOCKED -
operationType: string
Minimum Length:
1Maximum Length:16Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:REMOVED -
reason: string
Minimum Length:
0Maximum Length:255Reason for the entity creation or latest modification.Example:Initial import. -
repeatingFormCount: number
Count of repeating forms related to visit.Example:
0 -
scheduledDate: string
(date-time)
holds visit schedule date which is calculated from an anchor visit start date.Example:
2025-10-02T09:00:00Z -
scheduledEndDate: string
(date-time)
holds visit schedule end date which is calculated from the visit scheduledDate.Example:
2025-10-03T23:59:59Z -
scheduledFromEventGUID: string
Event ID (UUID, 32-character uppercase hexadecimal string) from which the schedule for this visit was derived.Example:
EEDD00112233445566778899AABBCCDD -
scheduledStartDate: string
(date-time)
holds visit schedule start date which is calculated from the visit scheduledDate.Example:
2025-10-02T00:00:00Z -
scheduledWindowEndDate: string
(date-time)
Scheduled window end date for the visit (dynamic calculation).Example:
2025-10-05T23:59:59Z -
scheduledWindowStartDate: string
(date-time)
Scheduled window start date (dynamic calculation for visit scheduling).Example:
2025-09-30T00:00:00Z -
signedStatus: string
Signed status for workflow, the acceptable values are: NEVER_SIGNED, SIGNED, UNSIGNED, NEVER_SIGNED.Example:
SIGNED -
siteId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.Example:
BEEFAABBCCDDEEDDFF00112233445566 -
studyVersion(required): string
Minimum Length:
0Maximum Length:100String representing the version of the study configuration or protocol. Helps track changes in form or study design.Example:3.1.0.2 -
subjectId: string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
AABBCCDDEEFF00112233445566778899 -
verifiedStatus: string
Verified status for review workflow,the acceptable values are: NEVER_VEIFIED, VERIFIED, UNVERIFIED, NOT_APPLICABLE.Example:
VERIFIED -
visitAction: string
Action taken on the visit start date value. Acceptable values are SCREEN_ENABLE ,SCREEN_DISABLE ,RANDOMIZE_ENABLE ,RANDOMIZE_DISABLE, DISPENSE_ENABLE, DISPENSE_DISABLE, COMPLETE_STUDY_ENABLE, COMPLETE_STUDY_DISABLE.Example:
ENABLE -
visitStartDate: string
(date-time)
Date/time the visit was started.Example:
2025-10-02T08:45:00Z -
visitStartDateLockedDateTime: string
(date-time)
Datetime when visit start date was locked.Example:
2025-10-02T12:00:00Z -
visitStartDateLockedStatus: string
Action taken on the visit start date value. Acceptable values are LOCKED, UNLOCKED, NEVER_LOCKED.Example:
LOCKED -
visitStatus: string
Status of the visit. The Value of the status can be NEW, COMPLETE, COMPLETE_ERR, INPROGRESS, INCOMPLETE, INCOMPLETE_ERR, SKIPPED, UNDO_SKIP and NOT_STARTED.Example:
COMPLETED -
visitType: string
Type of visit as per the visit type enumeration. The acceptable values are: SCREENING, RANDOMIZATION, DISPENSATION, NON_DISPENSATION, OPTIONAL, OPTIONAL_DISPENSATION, WITHDRAW, SCREENDISP, SCREENRAND, SUBJECT_COMPLETE, UNSCHEDULED, UNSCHEDULED_DISPENSATION, ADVERSE_EVENT, SCREENFAILURE, RESCREENING and RESCREENDISP.Example:
SCREENING -
visitWindowWarning: string
Window warning details or messages for visit timing.Example:
Visit outside of permitted window.
400 Response
Bad request.
Root Schema : DcsResponse
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