1. REST API for Clinical One Cloud Service
  2. Tasks
  3. Designer
  4. Visit APIs
  5. Visits
  6. Get dispensation visits

[Deprecated]: V5.0
get

/ec-designer-svc/rest/v5.0/studies/{studyId}/versions/{version}/visits/{visitid}/dispensings

Deprecated: Use latest version instead. Retrieves dispensing assignments for a specific visit in the specified study version. The optional kitType query parameter filters the kit categories returned. The response includes dispensing rows with kit, visit, treatment arm, quantity, do-not-dispense days, titration details, and outside-window settings.

Request

Path Parameters
Query Parameters
  • Type of kits requested: standard, titration, or all. Optional.
    Default Value: ALL
    Example:
    ALL

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successful operation.
Body ()
Root Schema : schema
Type: array
Show Source
  • ArmKitVisitDto v4.0
    Title: ArmKitVisitDto v4.0
    Dispensing assignment that connects a treatment arm, kit or titration group, visit, and dosing design in a study version.
Nested Schema : ArmKitVisitDto v4.0
Type: object
Title: ArmKitVisitDto v4.0
Dispensing assignment that connects a treatment arm, kit or titration group, visit, and dosing design in a study version.
Show Source
  • Indicates whether titration is allowed for this dispensing assignment. Optional.
    Example: false
  • Treatment arm ID (UUID, 32-character uppercase hexadecimal string). Required when the visit uses treatment-arm specific dispensing; otherwise optional.
    Example: B1B8327AFAA6412287106192AB5984EF
  • Indicates whether the kit can be dispensed outside the visit schedule window. Required for create/update.
    Example: true
  • Number of days before kit expiration when the kit can no longer be dispensed. Required for create/update; valid range is 0 to 9999.
    Example: 5
  • Dosing ID associated with the dispensing assignment (UUID, 32-character uppercase hexadecimal string). Required only for kits that calculate doses; omit for titration groups.
    Example: F5F8327AFAA6412287106192AB5984EF
  • Dispensing assignment ID (UUID, 32-character uppercase hexadecimal string).
    Example: E4E8327AFAA6412287106192AB5984EF
  • Kit or titration group ID (UUID, 32-character uppercase hexadecimal string). Required.
    Example: C2C8327AFAA6412287106192AB5984EF
  • Number of kits or dose quantity to dispense at the visit. Required for standard kit create/update; use -1 to remove an existing assignment. Omit for titration group assignments.
    Example: 1
  • titrationKits
  • Visit ID (UUID, 32-character uppercase hexadecimal string). Required.
    Example: D3D8327AFAA6412287106192AB5984EF
Example:
{
    "kitid":"C2C8327AFAA6412287106192AB5984EF",
    "armid":"B1B8327AFAA6412287106192AB5984EF",
    "visitid":"D3D8327AFAA6412287106192AB5984EF",
    "dosingId":"F5F8327AFAA6412287106192AB5984EF",
    "quantity":1,
    "dnd":5,
    "dispenseoutsidewindow":true,
    "allowTitration":false,
    "id":"E4E8327AFAA6412287106192AB5984EF"
}
Nested Schema : titrationKits
Type: array
Show Source
Nested Schema : ArmKitVisitTitrationDto v4.0
Type: object
Title: ArmKitVisitTitrationDto v4.0
Kit included in a titration dispensing group.
Show Source
  • Kit ID (UUID, 32-character uppercase hexadecimal string). Required for each titration kit entry.
    Example: C2C8327AFAA6412287106192AB5984EF
  • Number of kits from this kit type to dispense. Required for each titration kit entry.
    Example: 1
  • Kit type identifier shown for the titration kit. Optional.
    Example: KIT_A_20MG
Example:
{
    "kitId":"C2C8327AFAA6412287106192AB5984EF",
    "kitTypeId":"KIT_A_20MG",
    "kitQuantity":1
}
Examples

500 Response

Returned when the request cannot be completed due to validation failure, authorization failure, or an unexpected server-side condition.
Body ()
Root Schema : ErrorResponseData
Type: object
Title: ErrorResponseData
Error Response Details Information
Show Source
  • Object
    Title: Object
    Object with error details information.
  • Error code which is stored in ErrorCode enum. Example : C1-003
    Example: C1-003
  • Error message which is stored in service property file. Example : Cannot modify object after a study version has been approved
    Example: Cannot modify object after a study version has been approved
Nested Schema : Object
Type: object
Title: Object
Object with error details information.
Example:
{
    "field":"studyId",
    "reason":"Invalid value"
}
Back to Top