> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/changelog/2026/scheduled-orders-refactor-draft-upcoming.md).

# Scheduled Orders Refactor: draft → upcoming

*Released September 14, 2026 (UAT available September 18, 2026)*

> **Breaking change:** the order status previously called `draft` is renamed to `upcoming`. You must update your systems to use the new status name.

This is a breaking change to the Scheduled Orders workflow. The most important change: the order status previously called `draft` is renamed to `upcoming` — you must update your systems, API consumers, and workflow logic to use the new status name.

## \[Key Changes]

* `draft` → `upcoming` (breaking) — all partner systems, API consumers, and workflow logic must be updated
* Scheduled orders can now be edited by partners and clinicians before approval
* New approval fields: `approval_date`, `approval_by` — set when an order is approved/pre-approved, only if in Upcoming/Scheduled status; re-approving failed orders (resubmissions) does not update these fields
* Updated approval endpoints:
  * Approve — moves the order to Ready
  * Pre-approve — approves the order but keeps it Scheduled until `effective_date`
  * Delete approval — removes an existing approval
* Clinician App: approved Scheduled orders now show an approved label/checkmark in order details


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/changelog/2026/scheduled-orders-refactor-draft-upcoming.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.