> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Drug Testing / UDS Workflow — Integration

> Spec: CL-34-drug-testing-uds-workflow Status: ✅ Complete Last Updated: 2026-03-03

**Spec:** [CL-34-drug-testing-uds-workflow](../../../specs/cl/specs/CL-34-drug-testing-uds-workflow.md)\
**Status:** ✅ Complete\
**Last Updated:** 2026-03-03

***

## Overview

CL-34 (UDS Workflow) integrates with CL-09 (lab orders/results), CL-21 (OTP/MOUD), CL-04 (progress notes), CL-11 (Part 2 consent), CL-33 (court compliance), and PM-07 (billing). This document records integration contracts and platform layer usage.

***

## Integration Points (from Spec)

| Dependency          | Integration Type  | Purpose                                                                                                                                              |
| ------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| CL-09               | Data / pipeline   | UDS order extends or references lab order concept; result ingestion may use same lab result pipeline with UDS-specific mapping                       |
| CL-21 (OTP)         | Events / Platform | Overdue UDS escalation; publish overdue alerts via PF-10; align `cl_moud_monitoring_events.due_by` with UDS due dates; Phase 3: OTP 8/year reporting |
| CL-04               | Data              | Counseling note may be progress note linked to UDS interpretation                                                                                    |
| CL-11               | RLS / consent     | Part 2 consent gates display of UDS results                                                                                                          |
| CL-33               | Events / data     | Court-reportable results create or link to court compliance event                                                                                    |
| PM-07               | API / data        | Billing codes and encounter linkage for UDS charges                                                                                                  |
| PF-01, PF-02, PF-30 | Platform          | Organizations, RBAC, permissions                                                                                                                     |

***

## Event Contracts (Planned)

*To be added when events are defined (e.g. UDS result received, court-reportable result flagged, MOUD unexpected negative alert).*

***

## API Contracts (Planned)

*To be added for PM-07 charge/encounter linkage and any CL-21/CL-33 APIs consumed.*

***

## Platform Integration Layer

* **PF-10 (Notifications):** Overdue UDS alerts per CL-21 FR-4.
* **PF-30 (Permissions):** Permission keys for UDS orders/results (e.g. `cl.uds_orders.create`, `cl.uds_results.view`).
* **@/platform/scheduling:** Encounter context for `encounter_id` on orders and billing.
* **@/platform/types:** Shared encounter/billing types as applicable.

***

## Cross-Core Matrix

| From  | To    | Contract / Mechanism                                                                    |
| ----- | ----- | --------------------------------------------------------------------------------------- |
| CL-34 | PM-07 | Encounter-linked UDS charges (CPT/G-codes); document in API\_CONTRACTS when implemented |
| CL-34 | CL-21 | Overdue UDS events; MOUD unexpected negative alerts                                     |
| CL-34 | CL-33 | Court-reportable result → court compliance event                                        |

*Update [CROSS\_CORE\_INTEGRATIONS.md](CROSS_CORE_INTEGRATIONS.md) when CL-34 implementation adds concrete events/APIs.*

***

## References

* [CL-34 Spec](../../../specs/cl/specs/CL-34-drug-testing-uds-workflow.md)
* [PLATFORM\_INTEGRATION\_LAYERS.md](PLATFORM_INTEGRATION_LAYERS.md)
* [EVENT\_CONTRACTS.md](EVENT_CONTRACTS.md)
* [API\_CONTRACTS.md](API_CONTRACTS.md)
* [CROSS\_CORE\_INTEGRATIONS.md](CROSS_CORE_INTEGRATIONS.md)