[Deprecated]: V5.0
post
/ec-dc-svc/rest/v5.0/studies/{studyId}/{mode}/subjects/visitschedule
Deprecated: This consolidated API retrieves locked status, subjects and their visit schedule,filter capabilities along with 'canBeCompleted' field for a subject.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
test -
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
1BC29B36F5D64B1B95F4BDBBCEA481BE
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest payload to retrieve visit schedules for subjects filtered by sites, pagination, ordering, review status and state filters
Show Source
-
containsSearchKeywords: array
containsSearchKeywords
Keywords for contains match in subject search which will be applied on subject number
-
exactSearchKeywords: array
exactSearchKeywords
Keywords for exact match in subject search which will be applied on subject number
-
limit: integer
(int32)
Maximum number of results to returnExample:
25 -
nextVisitOnly: boolean
When true, only the next scheduled visit is returned per subjectExample:
false -
notStarted: boolean
When true, include only subjects that have not startedExample:
false -
offset: integer
(int32)
Offset for paginationExample:
0 -
order: string
Sort order for resultsExample:
asc -
reviewStatus: string
Review status filter applied to subjects. Values can be noopenqueries, openqueries, verified, signed, locked, allvisitscomplete, readytosign, allvisitscomplete, readytoverify, all, signedandverified, frozenExample:
all -
sites: array
sites
List of site identifiers to scope the search
-
subjectStates: array
subjectStates
States of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_Failed
Nested Schema : containsSearchKeywords
Type:
arrayKeywords for contains match in subject search which will be applied on subject number
Show Source
-
Array of:
string
Keywords for contains match in subject search which will be applied on subject numberExample:
["100","SMI"]
Example:
[
"100",
"SMI"
]Nested Schema : exactSearchKeywords
Type:
arrayKeywords for exact match in subject search which will be applied on subject number
Show Source
-
Array of:
string
Keywords for exact match in subject search which will be applied on subject numberExample:
["1001","SMITH"]
Example:
[
"1001",
"SMITH"
]Nested Schema : sites
Type:
arrayList of site identifiers to scope the search
Show Source
-
Array of:
string(uuid)
List of site identifiers to scope the search
Example:
[
"D3C9A4B5E6F78123456789ABCDEF1234",
"E1F2A3B4C5D6E7F89012ABCDEF345678"
]Nested Schema : subjectStates
Type:
arrayStates of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_Failed
Show Source
-
Array of:
string
States of subjects to filter by Active, New, Screening_Initiated, Enrolled, Complete, Withdrawn, ehrLinked, ehrNotLinked, Screen_Failed, Auto_Screen_FailedExample:
["Auto_Screen_Failed"]
Example:
[
"Auto_Screen_Failed"
]Response
Supported Media Types
- application/json
200 Response
Subjects success.
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: userId400 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