Importing an Order

Import externally-placed lab orders into Junction for centralized tracking and result delivery using the correct sample or requisition ID.

This feature is in closed beta.

Interested in this feature? Get in touch with your Customer Success Manager.

If you want to track orders with Junction that weren’t originally placed with Junction, you can import an order.

It’s crucial that imported orders are created with the correct sample ID. This is the requisition number or control number for Labcorp orders, or the lab reference ID for Quest orders. If in doubt, contact your Junction Customer Success Manager to confirm what you should supply for the sample ID.

The sample ID must also uniquely identify the order. If you supply an ID that clashes with an existing order, that will result in a validation error.

An imported order can be cancelled, receive results, and function similarly to orders originally placed with Junction, but with one important exception: a requisition will not be created. This means you cannot use the endpoint to retrieve the requisition for an imported order since Junction does not have access to it.

After an order is successfully imported, it will be in the requisition_bypassed state (for example, an imported testkit order would have a received.testkit.requisition_bypassed status). This status supports transitioning to the same states that requisition_created does.

Since import skips the regular order creation flow, no communications are sent to patients about the order being created, but communications are sent for subsequent events that might occur (order completion, for example).

Example

Python

from junction import Billing, Gender, Junction, LabTestCollectionMethod, OrderSetRequest, PatientAddress, PatientDetailsWithValidation, PhysicianCreateRequest
from junction.environment import JunctionEnvironment

client = Junction(
    api_key="YOUR_API_KEY",
    environment=JunctionEnvironment.SANDBOX,
)

data = client.lab_tests.import_order(
    user_id="<user_id>",
    billing_type=Billing.CLIENT_BILL,
    order_set=OrderSetRequest(lab_test_ids=["<lab_test_id>"]),
    collection_method=LabTestCollectionMethod.WALK_IN_TEST,
    physician=PhysicianCreateRequest(first_name="Jane", last_name="Doe", npi=""),
    patient_details=PatientDetailsWithValidation(
        first_name="John",
        last_name="Doe",
        dob="2020-01-01",
        gender=Gender.MALE,
        phone_number="[phone]",
        email="[e-mail]",
    ),
    patient_address=PatientAddress(
        receiver_name="John Doe",
        first_line="123 Main St.",
        second_line="Apt. 208",
        city="San Francisco",
        state="CA",
        zip="91189",
        country="US",
        phone_number="[phone]",
    ),
    sample_id="1234567890",
)

This example assumes you provide your own physician. The physician must be provided if your team configuration is set up as delegated. The billing type provided must also be appropriate to your team configuration. These aspects will be validated when making the request.

Since the request represents an existing order, we don’t perform strict address validation on the patient address, to make it easier to import orders exactly as they were placed in the original interface.

The response object schema is the same as creating an order.