> ## 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.

# Referral Management & Tracking — Integration

> Version: 1.0.0 Last Updated: 2026-02-17 Spec: PM-06 Referral Management & Tracking Constitution Reference: Section 1.2 (Core Independence), Section 1.3 (Integr…

**Version:** 1.0.0\
**Last Updated:** 2026-02-17\
**Spec:** [PM-06 Referral Management & Tracking](../../../specs/pm/specs/PM-06-referral-management-tracking.md)\
**Constitution Reference:** Section 1.2 (Core Independence), Section 1.3 (Integration Patterns)

***

## Overview

PM-06 owns the referral entity lifecycle (inbound/outbound), source attribution, conversion metrics, and document management. Integrations with PM-01, PM-10, CL-12, and CE support admission from referral, prior authorization linkage, clinical care coordination, and referral source relationship management.

***

## Integration Points (from spec)

| Dependency | Pattern                | Purpose                                                                                     |
| ---------- | ---------------------- | ------------------------------------------------------------------------------------------- |
| **PM-01**  | Data                   | Patient registration from referral admission; `pm_referrals.patient_id` → `pm_patients.id`  |
| **PM-10**  | Data                   | Prior authorization linkage; `pm_referrals.authorization_id` → `pm_prior_authorizations.id` |
| **CL-12**  | Event                  | Clinical care coordination; PM-06 publishes `referral_accepted` when status → admitted      |
| **CE**     | Platform Layer / Event | Referral source relationship management (CE core)                                           |

***

## Event Contract: referral\_accepted

**Full contract:** [CL-PM-REFERRALS.md](./CL-PM-REFERRALS.md)

* **Publisher:** PM-06
* **Subscribers:** CL-12
* **When:** Referral status set to admitted (inbound) or accepted (outbound); integration layer maps PM-06 status to event.
* **Payload:** `referral_id`, `patient_id`, `referral_direction`, facilities, level of care, reason, urgency, `organization_id`, `user_id`, `timestamp`.

***

## API / Data Contracts

* **PM-01:** Admission from referral creates/links `pm_patients` record; implementation may trigger from referral status workflow.
* **PM-10:** Referral form may link to existing `pm_prior_authorizations`; display auth status and units.
* **CE:** Referral source (e.g. community org) may be resolved via Platform Integration Layer or CE APIs; document exact contract when CE referral source feature is implemented.

***

## Integration Matrix

| From       | To    | Pattern              | Doc                                     |
| ---------- | ----- | -------------------- | --------------------------------------- |
| PM (PM-06) | CL-12 | Event                | [CL-PM-REFERRALS](./CL-PM-REFERRALS.md) |
| PM-06      | PM-01 | Data / workflow      | This doc                                |
| PM-06      | PM-10 | Data (FK)            | This doc                                |
| PM-06      | CE    | Platform Layer / TBD | TBD when CE spec finalized              |

***

## References

* [PM-06 Spec](../../../specs/pm/specs/PM-06-referral-management-tracking.md)
* [CL-PM-REFERRALS](./CL-PM-REFERRALS.md)
* [CROSS\_CORE\_INTEGRATIONS](./CROSS_CORE_INTEGRATIONS.md)

***

## Enhancements

### PM-06-EN-01 — Referral Management Enhancements

**Spec:** [PM-06-EN-01](../../../specs/pm/specs/PM-06-EN-01-referral-management-enhancements.md)

Adds court-ordered tracking, fax-to-digital intake, SLA monitoring, and packet checklist. **No new cross-core event contracts.** Dependencies are platform-layer only:

| Dependency | Pattern        | Purpose                                          |
| ---------- | -------------- | ------------------------------------------------ |
| PF-10      | Platform layer | In-app SLA breach + court deadline notifications |
| PF-11      | Platform layer | Fax artifact storage and access logging          |

The parent `referral_accepted` event is unchanged. EN-01 does not introduce entries to `EVENT_CONTRACTS.md`.
