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 of the study, accepts: test, active, or training.
    Example:
    test
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    CDBBCCDDEEFF11223344556677889900
  • 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 Top

Response

Supported Media Types

200 Response

List of dispensed visits by subject.
Body ()
Root Schema : schema
Type: array
Show Source
Nested Schema : DispensedVisit
Type: object
Represents a dispensed visit instance linked to a subject in a clinical study
Show Source
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) of the visit
    Example: ABCDEF1234567890ABCDEF1234567890
  • Name of the dispensed visit
    Example: Baseline
Examples

400 Response

Bad request.
Body ()
Root Schema : DcsResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • 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
Nested Schema : details
Type: object
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
Back to Top