[Deprecated]: Get orders
get
/ec-ors-svc/rest/v3.0/studies/{studyId}/{mode}/orders
Deprecated: Retrieves a list of all orders in a study. If a kit list is disabled, the shipment will be excluded from the Orders API. Rights: OrsInventoryGet, OrsUnblinded.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.
-
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
Query Parameters
-
endDate(required): string
The ending date and time (optional). If you don't specify the time, the date range stops before midnight (23:59:59 UTC) for the specified date. The accepted date and time formats are: dd-MMM-yyyy HH:mm:ss.SSS, dd-MMM-yyyy HH:mm:ss, or dd-MMM-yyyy HH:mm.
-
includeDepotShipments(required): boolean
By Default this value is set to False, which the default API will exclude depot to depot shipments.Default Value:
false -
includeReconShipments(required): boolean
By Default this value is set to False, which the default API will exclude destruction shipments.Default Value:
false -
limit: integer(int32)
Minimum Value:
1 -
offset: integer(int32)
Minimum Value:
0 -
startDate(required): string
The starting date and time (optional). If you don't specify the time, the date range begins after midnight (UTC) for the specified date. The accepted date and time formats are: dd-MMM-yyyy HH:mm:ss.SSS, dd-MMM-yyyy HH:mm:ss, or dd-MMM-yyyy HH:mm.
-
status: string
Status of the order
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Successful operation
Root Schema : OrderInventoryPagedListResponse v4.0
Type:
objectTitle:
OrderInventoryPagedListResponse v4.0Contains order details for the inventory.
Show Source
-
count: integer
(int32)
Number of results in the current page.Example:
25 -
hasMore: boolean
Indicates if there are more results beyond the current page.Example:
true -
limit: integer
(int32)
Maximum number of records returned per page.Example:
25 -
offset: integer
(int32)
Index of the first record returned in the current page.Example:
0 -
resultData: array
resultData
Paginated result data for the current page. The concrete type depends on the API and typically is an array or list of DTOs.
-
shipments: array
shipments
-
totalResults: integer
(int32)
Total number of results across all pages.Example:
125
Nested Schema : resultData
Type:
arrayPaginated result data for the current page. The concrete type depends on the API and typically is an array or list of DTOs.
Show Source
-
Array of:
object OrderInventoryDTO v4.0
Title:
OrderInventoryDTO v4.0Contains inventory order details.
Nested Schema : shipments
Type:
Show Source
array-
Array of:
object OrderInventoryDTO v4.0
Title:
OrderInventoryDTO v4.0Contains inventory order details.
Nested Schema : OrderInventoryDTO v4.0
Type:
objectTitle:
OrderInventoryDTO v4.0Contains inventory order details.
Show Source
-
inventory: array
inventory
-
order: object
OrderDTO v3.0
Title:
OrderDTO v3.0Contains order related details. -
version: integer
(int32)
Version.Example:
1
Nested Schema : inventory
Type:
Show Source
array-
Array of:
object InventoryDTO v2.0
Title:
InventoryDTO v2.0Contains kit details.
Nested Schema : OrderDTO v3.0
Type:
objectTitle:
OrderDTO v3.0Contains order related details.
Show Source
-
comment: string
commentExample:
Updated with new values -
depotId: string
(uuid)
Depot Id.
-
depotVersionStart: string
(date-time)
Depot version start.
-
isDepotShipment: boolean
isDepotShipmentExample:
true -
isReconciliation: boolean
isReconciliationExample:
true -
jobInstanceId: string
(uuid)
Job instance Id.
-
objectVersionNumber: number
(double)
Software version NumberExample:
5 -
operationType: string
Allowed Values:
[ "CREATED", "MODIFIED", "REMOVED" ]Operation type.Example:CREATED -
orderDate: string
(date-time)
Date of order
-
orderId: string
(uuid)
Order Id.
-
orderStatusId: number
(double)
Order status Id.Example:
5 -
orderType: string
Allowed Values:
[ "INITIAL", "RESUPPLY", "MANUAL" ]Order type.Example:MANUAL -
orderTypeId: integer
(int64)
Order type Id.Example:
5 -
reason: string
reasonExample:
DATA ENTRY ERROR -
reportId: string
(uuid)
report Id.
-
shipDate: string
(date-time)
Date of shipping.
-
shipmentId: string
ID of the shipment.Example:
123 -
siteId: string
(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
-
siteVersionStart: string
(date-time)
Site version start.
-
studyId: string
(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
-
studyVersionStart: string
(date-time)
Study version start.
-
trackingNumber: string
Shipment tracking number.Example:
12345 -
trackingNumberUrl: string
Tracking number url.Example:
http://www.site.com -
userId: string
(uuid)
User Id.
-
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.
-
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.
Nested Schema : InventoryDTO v2.0
Type:
objectTitle:
InventoryDTO v2.0Contains kit details.
Show Source
-
Block number: string
Block number.Example:
245 -
blocknumber: string
-
doNotCount: number
(double)
Do Not Count (DNC) Days.Example:
5 -
doNotShip: number
(double)
Do Not Ship (DNS) Days.Example:
5 -
expirationDate: string
(date-time)
Expiration date
-
inventoryId: string
(uuid)
Inventory Id.
-
inventorySourceId: string
(uuid)
Id of the Inventory
-
inventorySourceVersionStart: string
(date-time)
Inventory version start
-
inventoryStatusId: number
(double)
Allowed Values:
[ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 ]Unique ID corresponding to each inventory status value (1 for Available, 2 for Damaged, 3 for Destroyed, 4 for Dispensed, 5 for Expired, 6 for Not in Use, 7 for Misallocated, 8 for Missing, 9 for In Transit, 10 for Quarantined, 11 for Pre-quarantined, 12 for Pending Destruction, 13 for Lost by Subject, 14 for Temporarily Unavailable, 15 for Damaged by Subject, 16 for New, 17 for Not Dispensed to Subject, 18 for Returned to Site, 19 for Conserved, 20 for Received for Destruction).Example:5 -
kitNumber: number
(double)
Kit number.Example:
5 -
kitNumberUTF: string
Kit number UTF8.Example:
24-1 -
kitTypeId: string
(uuid)
ID of the kit type.
-
kitTypeVersionStart: string
(date-time)
Kit type version start
-
labelGroupId: string
(uuid)
Label group Id.
-
labelGroupVersionStart: string
(date-time)
Label group version start
-
lotId: string
(uuid)
Lot Id.
-
lotVersionStart: string
(date-time)
Lot version start
-
sequenceNumber: number
(double)
Sequence nuumber.Example:
5 -
siteId: string
(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the clinical site.
-
siteVersionStart: string
(date-time)
Site version start
-
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.
-
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.
400 Response
Invalid order status value
Root Schema : ORSResponse
Type:
objectCommon response object.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result Object
-
status: string
Status of requestExample:
Success -
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:
objectResult Object
Nested 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: userId500 Response
Internal server error
Root Schema : DesignerResponse
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