Accessioning Lab Requests as Requisitions vs. Orders

Accessioning Lab Requests as Requisitions vs. Orders

When scheduling lab testing through the web portal, requests can be created as either Requisitions or Orders, depending on the lab’s workflow and configuration. Understanding the difference between these two options is important because each one affects how the request appears in the LIS and how pending results are managed by lab staff.

What Is a Requisition?

A Requisition is a preliminary lab request that is created before it becomes an active order in the LIS. This workflow is especially useful when a specimen has not yet been collected or when there is a chance that the collection may need to be canceled or rescheduled.

Requisitions help keep the pending results queue clean because they do not appear as pending results in the LIS. If the specimen is not collected, the requisition can be canceled or rescheduled without creating unnecessary pending items or confusion for the lab team.

Each requisition is assigned a unique requisition ID. Requisition IDs usually begin with the letter R. For example, the first requisition created on July 23, 2026, may look like this:

R072326000001

Once the requisition is converted into an order, the requisition status changes to Done, and a new order is created with its own unique Order ID.

What Is an Order?

An Order is an active lab request in the LIS. When a requisition is bypassed and an order is created directly, the order immediately enters the lab workflow.

Because an order is active in the LIS, its result will continue to appear as pending until the specimen arrives and testing is completed, or until the order is canceled. If the specimen is delayed, missed, or never collected, the order may remain in the pending results list and require additional follow-up from lab staff.

For this reason, creating orders directly is best suited for situations where the specimen has already been collected or where the lab is ready for the request to immediately become an active order.

Why Use Requisitions?

Using requisitions can help improve workflow and reduce confusion in the lab. Since requisitions do not appear as pending results, they are helpful for scheduled collections, future appointments, or cases where specimen collection is not guaranteed.

Benefits of using requisitions include:

  • Prevents uncollected specimens from appearing as pending results

  • Allows requests to be canceled or rescheduled before becoming active orders

  • Reduces unnecessary follow-up work for lab staff

  • Helps lab technicians focus on true pending results

  • Provides a clear workflow from scheduled request to active order

When to Create Orders Directly

Creating orders directly may be appropriate when the specimen is already available or when the lab wants the request to immediately enter the active LIS workflow.

However, it is important to understand that direct orders will remain pending in the LIS until they are resulted, completed, or canceled. If the specimen has not been collected yet, this can make the pending results list harder to manage.

Direct order creation should generally be used when:

  • The specimen has already been collected

  • The lab is ready to process the specimen immediately

  • The user is intentionally bypassing the requisition workflow

  • The lab has enabled direct order entry in the portal

Portal Configuration

The web portal supports both workflows: Requisitions and Orders. Labs can decide which workflow best fits their operational needs.

Please note that the option to create orders directly must be enabled by the lab. If direct order entry is not enabled, users will need to create a requisition first and convert it into an order when appropriate.

For most scheduled collections or situations where the specimen has not yet been collected, using a Requisition is the recommended workflow. This prevents unnecessary pending results from appearing in the LIS and helps keep the lab’s pending review process organized.

Creating an Order directly is recommended only when the specimen has already been collected or when the lab is prepared for the request to become active immediately.

Summary

Requisitions and orders both play an important role in lab accessioning, but they serve different purposes.

A Requisition is best used as a scheduled or preliminary request before specimen collection. It can be canceled or rescheduled without creating pending results in the LIS.

An Order is an active lab request that appears in the LIS and remains pending until it is completed or canceled.

Choosing the right workflow helps reduce confusion, improves pending result management, and supports a more efficient lab operation.

    • Related Articles

    • Multiple Orders

      Convert scheduled requisitions to orders Turn scheduled requisitions into active orders with a single click—individually or in batches—regardless of how they were created (entered in the LIS by lab staff, submitted via the client web portal, or ...
    • Converting Requisitions to Orders

      Convert requisitions to orders Turn scheduled or pre-collected work into active orders in just a few clicks, individually or in batch. This applies to requisitions created in the LIS, submitted via the client portal, or received through EMR/HL7 ...
    • Reference Lab Master File

      Reference Labs — Configuration and benefits OCL LIS lets you configure multiple reference laboratories and route specific tests to the most appropriate partner based on specialty, pricing, turnaround time, or contractual preferences. After ...
    • Mastering Lab Services Coding

      Mastering Lab Services Coding Purpose and Audience This knowledge base article equips revenue cycle teams, laboratory professionals, and coders with a practical, compliant approach to coding outpatient laboratory services. It synthesizes official ...
    • Requisitions Purpose and Workflow

      Requisitions in the LIS are used to: Schedule lab work to be performed in the future. Track specimens already collected but not yet received by the lab. Generate scheduled work from the Standing Orders module. Requisitions remain in the Requisitions ...