V2.0
get
/ec-dc-svc/rest/v2.0/studies/{studyId}/{mode}/subjects/dispensedvisits/{subjectId}
Returns all dispensed visits associated with the given subject in the study. Use subjectId as path parameter (UUID, uppercase hex). Response contains an array of DispensedVisit objects, each with visitId and visitName.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
test -
studyId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
CDBBCCDDEEFF11223344556677889900 -
subjectId(required): string
Unique subject identifier (UUID, 32-character uppercase hexadecimal string) representing the patient/participant enrolled in the study.Example:
ABCDEF1234567890ABCDEF1234567890
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
List of dispensed visits by subject.
Root Schema : schema
Type:
Show Source
array-
Array of:
object DispensedVisit
Represents a dispensed visit instance linked to a subject in a clinical study
Nested Schema : DispensedVisit
Type:
objectRepresents a dispensed visit instance linked to a subject in a clinical study
Show Source
-
visitId: string
Unique identifier (UUID, 32-character uppercase hexadecimal string) of the visitExample:
ABCDEF1234567890ABCDEF1234567890 -
VisitName: string
Name of the dispensed visitExample:
Baseline
Examples
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