Skip to main content
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 (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)

​
Event Contract: referral_accepted

Full contract: 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

​
References

​
Enhancements

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

Spec: PM-06-EN-01 Adds court-ordered tracking, fax-to-digital intake, SLA monitoring, and packet checklist. No new cross-core event contracts. Dependencies are platform-layer only: The parent referral_accepted event is unchanged. EN-01 does not introduce entries to EVENT_CONTRACTS.md.