Get reusable kits from a list of kit types

post

/ec-ors-svc/rest/v4.0/studies/{studyId}/{mode}/subjects/{subjectId}/reuse-kits

Retrieves previously dispensed kits, form a list of kit types passed in the request body, that can be reused in the current visit for a given subject. Support for unblinded pharmacist kits which are put on dose hold. UTF8 format support for KitNumber.Rights: OrsSubjectVisitGet.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
Nested Schema : kitTypesForDoseHold
Type: array
Show Source
Nested Schema : DoseHoldRequestV1
Type: object
Contains details about kits which are to be hold or dispensed
Show Source
Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : ReusableKitsResponse v1.0
Type: object
Title: ReusableKitsResponse v1.0
Contains details of reusable kits.
Show Source
Nested Schema : kits
Type: array
Show Source
Nested Schema : ReusableKit
Type: object
Title: ReusableKit
Response containing reusable kit details
Show Source

400 Response

Invalid subject OR Scheduled visit with instance number OR Unscheduled visit with no instance number
Body ()
Root Schema : ORSResponse
Type: object
Common response 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
  • 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
  • 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
Result Object

500 Response

Internal server error
Body ()
Root Schema : ORSResponse
Type: object
Common response 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
  • 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
  • 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
Result Object
Back to Top