f39a4bfeca8e
Create an order
Create an Order. Returns HTTP_409_CONFLICT if order with the same ID already exists for the given customer ID.
Headers
Version of the Orders API to use with this call
Version of the Orders API to use with this call
Request body
The preferred formats the charts should be delivered in.
An enumeration.
An enumeration.
file naming template for charts to be delivered.
Whether to include a manifest with the delivery.
file naming template for delivery manifests.
file extension for delivery manifests.
delimiter for delivery manifests.
file naming template for zip file for when charts need to be zipped.
An enumeration.
A list of date times (in ISO format) for when deliveries should happen.
An enumeration.
Additional delivery locations for documents (besides API)
Email recipients for order delivery notifications.
User can specify a password that will be applied to the zip file encryption on delivery
User-provided identifier for the object.
- Must be between 4 and 32 characters
- Must contain only upper or lower-case alphanumeric characters, numbers, hyphens and/or underscores.
User-friendly name for the order.
ID for the project with which you want to associate the order.
An enumeration.
Date by which record delivery should be complete. Default is 90 days from order submission.
An enumeration.
An enumeration.
An enumeration.
Miscellaneous configuration related to order that may be used for scheduling, reporting, billing purposes. Also used to store information on whether to use experimental matches in Routing
DEPRECATED: use 'retrieval_sources'.
List of one or more Identified Switchboard sources to use when retrieving records.
Default retrieval sources are based on configuration.
Flag to indicate if manual QA is required
Flag to indicate if coding is required
Flag to route coding through the new SB->Archon workflow instead of the legacy ARCH DB export.
An enumeration.
Is provider information included?
This field is used to link forecasts to Orders. DemandID can be a dummy value (99999) and does not have to be unique.
This field is used to provide information to ChartFinder for traditional projects.Wave must be an integer between 1 and 9999.
This field is used to provide information to ChartFinder for traditional projects.Chart Review Year must be an integer between 2022 and 2025.
This field is used to provide information to ChartFinder for traditional projects.Target Yield must be a float between 0 and 1.
This field is used to provide information to ChartFinder for traditional projects.Must be an integer between 1 and 3.
Traditional Project flag.
An enumeration.
Response
Successful Response
The preferred formats the charts should be delivered in.
An enumeration.
An enumeration.
file naming template for charts to be delivered.
Whether to include a manifest with the delivery.
file naming template for delivery manifests.
file extension for delivery manifests.
delimiter for delivery manifests.
file naming template for zip file for when charts need to be zipped.
An enumeration.
A list of date times (in ISO format) for when deliveries should happen.
An enumeration.
Additional delivery locations for documents (besides API)
Email recipients for order delivery notifications.
User can specify a password that will be applied to the zip file encryption on delivery
Flag to indicate if merged charts per patient is required
Unique identifier for the object.
User-provided identifier for the object.
- Must be between 4 and 32 characters
- Must contain only upper or lower-case alphanumeric characters, numbers, hyphens and/or underscores.
User-friendly name for the order.
ID of the project associated with the order.
UUID of the project associated with the order.
Name of the project associated with the order.
An enumeration.
Date by which record delivery should be complete.
An enumeration.
An enumeration.
Miscellaneous configuration related to order that may be used for scheduling, reporting or billing purposes.
List of one or more Identified Switchboard sources to use when retrieving records.
Default retrieval sources are based on configuration.
Flag to indicate if manual QA is required
Flag to indicate if coding is required
Flag to route coding through the new SB->Archon workflow instead of the legacy ARCH DB export.
An enumeration.
Number of queries associated with the order.
OrderStatus is an enumeration representing the different stages in an order's lifecycle.
Definitions: draft: An initial state for orders that are created but not yet submitted for processing. - Used for orders created manually through the IDSB UI, requiring explicit action to proceed to dispatch.
accepted: A ready-for-processing state for newly received orders.
- Used for orders submitted via the CF orders API, indicating they are queued for dispatch without requiring further manual intervention.
intake_review_required: An action required state to complete steps prior to dispatching instructions.
- Used for orders that require action items to be completed as part of the import review process.
intake_review_completed: A state indicating that the import review process has been completed.
- Used for orders that have completed the import review process and are ready for dispatch.
rejected: A terminal state indicating the order was declined.
- Used for prematch when an order fails input file validation
processing: A temporary state while initial processing actions are performed on the order.
- Used after submission but before any external requests are dispatched, including internal steps like intake database updates, routing,
and merging charts (for semi-auto/ML sweep).
failed: A terminal state indicating the order failed to process.
- Used for prematch orders to indicate order failed to process.
dispatched: A state indicating that external chart or patient searches have been initiated.
- Set once the first external request related to the order is sent out.
canceled: A terminal state indicating the order was withdrawn and processing has ceased.
complete: A terminal state signifying that the order has been fully processed and closed.
- Currently set manually after all retrievals and chart deliveries are finalized.
pending_close: A terminal state indicating that further processing should halt.
- This state mirrors CF updates instructing IDSB to stop any remaining work on the order.
close_in_progress: A temporary state during which the order is being closed.
- Set when a close request is initiated. Closing actions are underway, and status will transition to 'complete' once finalized.
Order status lifecycle for IDSB fully automated projects:
- draft -> processing -> dispatched -> close_in_progress -> complete
Order status lifecycle for IDSB semi-automated projects:
- accepted -> dispatched -> complete
Order status lifecycle for IDSB traditional projects:
- draft -> accepted -> processing -> intake_review_required -> intake_review_completed -> dispatched -> complete
The ISO8601 formatted timestamp for when the object was created.
The ISO8601 formatted timestamp for when the object was last updated.
This field is used to link forecasts to Orders. DemandID can be a dummy value (99999) and does not have to be unique.
This field is used to provide information to ChartFinder for traditional projects.Wave must be an integer between 1 and 9999.
This field is used to provide information to ChartFinder for traditional projects.Chart Review Year must be an integer between 2022 and 2025.
This field is used to provide information to ChartFinder for traditional projects.Target Yield must be a float between 0 and 1.
This field is used to provide information to ChartFinder for traditional projects.Must be an integer between 1 and 3.
The type of project this order is.