Elation periodically syncs each lab vendor’s test compendium. When a vendor removes a test from its published compendium, Elation sets
deleted_date on the corresponding test record rather than removing the record. If the test is later reintroduced to the compendium, Elation creates a new test record with a new id instead of restoring the original one, so a stored test id isn’t guaranteed to stay valid indefinitely. A lab order that already references a test with deleted_date set can still be submitted successfully — the field doesn’t block order transmission.When building an integration against this endpoint, filter to tests where deleted_date is null when presenting available tests to users, avoid persisting a test id long-term, and look up the current record by code if a previously stored id becomes deleted.