Skip to main content

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.

Tracks integration doc stubs that need schemas filled when a dependency spec is implemented. Auto-populated by spec-reviewer; consumed by whats-next and generate-tasks. Schema (v2, 2026-04-17): Each row carries an explicit Owner, Unblock Condition, and Target Quarter so the IOU is closeable. npm run audit:integration-contracts treats every spec ID referenced in this file as “covered” until the row is resolved. Triage pass: 2026-04-10 — each row has an explicit next action; full schema closure remains tied to owning specs. Schema upgrade: 2026-04-17 — added Owner / Unblock Condition / Target Quarter columns.

​
Pending Stubs

Integration DocStub SectionBlocked OnWhat’s NeededOwnerUnblock ConditionTarget QuarterAdded ByResolved / Next step
PM-29-claims-denial-management-appeals-INTEGRATION.mdPF-29 task creation payload schemaPF-29 task API contractConfirm task entity-link format, required fields, and linked entity type for denial tasksPMPF-29 published task source_type union including pm_appealResolvedPM-29 spec-review 2026-03-02✅ 2026-03-02 — PF-29 is Complete; useTaskMutation().create() from @/platform/tasks; source_type: 'pm_appeal', source_id: appealSubmissionId; added 'pm_appeal' to TaskSourceType union. See integration doc.
PM-29-claims-denial-management-appeals-INTEGRATION.mdPM-18 Phase 2 denial-pattern feed schemaPM-18 Phase 2 implementationDenial history query design and suggestion-surface API contractPMPM-18 P2 denial-pattern store + API published2026 Q3PM-29 spec-review 2026-03-02🟡 Triage 2026-04-10: Blocked on PM-18 P2. Track under PM-18 tasks; stub stays open until denial-pattern store + API exists.
PM-33-capitation-pmpm-revenue-reconciliation-INTEGRATION.mdcapitation_payment_received event contractPM-33 implementationFormalize event payload in EVENT_CONTRACTS.md; FA team to confirm journal entry structure for ratable capitation revenue recognition (GAAP ASC 606)PM + FAPM-33 emits event AND FA-GL signs off ASC 606 fields2026 Q3PM-33 spec-review 2026-03-02🟡 Triage 2026-04-10: Add payload to EVENT_CONTRACTS.md when PM-33 emits event; FA-GL sign-off on ASC 606 fields.
PM-33-capitation-pmpm-revenue-reconciliation-INTEGRATION.mdPM-33 → PM-11 utilization queryPM-11 implementationDefine SQL query for encounter count vs. capitation amount widget; expose via pm_capitation_periods + pm_encounters joinPMPM-11 analytics view ships2026 Q3PM-33 spec-review 2026-03-02🟡 Triage 2026-04-10: Blocked on PM-11 analytics view; document SQL in PM-33 integration doc when widget ships.
GR-14-regulatory-incident-reporting-automation-INTEGRATION.mdregulatory_report_submitted event payload schemaGR-14 Phase 2 implementationFinalize payload schema; GR-03 and GR-08 teams to confirm compliance evidence record formatGRGR-14 P2 ships AND GR-03/GR-08 evidence record schema confirmed2026 Q3GR-14 spec-review 2026-03-07🟡 Triage 2026-04-10: Blocked GR-14 P2; align payload with GR evidence store before enabling consumers.
GR-14-regulatory-incident-reporting-automation-INTEGRATION.mdPF-11 source_type for regulatory report documentsPF-11 document APIConfirm source_type: gr_incident_regulatory_report is valid; add to PF-11 document generation source type union if neededGR + PFPF-11 document source_type union extended2026 Q3GR-14 spec-review 2026-03-07🟡 Triage 2026-04-10: Confirm union in PF-11 types + integration doc in same PR as GR-14 P2.
PF-91-compliance-automation-regulatory-dashboard-INTEGRATION.mdEdge Function request/response JSON Schema (compliance-run-checks, compliance-phi-scan, generate-compliance-evidence)PF-91 Phase 1–4 implementationAlign with CONTRACT_VALIDATION_CHECKLIST; document verify_jwt per function; no PHI in error bodiesPFPF-91 functions exit scaffold (Phase 1 complete)2026 Q2PF-91 spec workflow 2026-03-24🟡 Triage 2026-04-10: Blocked PF-91; publish schemas when functions leave scaffold.
HR-30-final-paycheck-termination-pay-compliance-INTEGRATION.mdHR-07 pay-run import / RPC hr_export_final_pay_for_run request-response schemaHR-07 pay run API designDefine JSON/CSV columns and idempotency key for approved hr_final_paycheck_requestsHRHR-07 export RPC design finalized2026 Q3HR-30 spec workflow 2026-03-25🟡 Triage 2026-04-10: Blocked HR-07 export RPC design; co-own with HR-PAY runbook.
PM-36-automated-charge-reconciliation-INTEGRATION.mdPF-29 createTask() payload — source_type: 'charge_reconciliation' union membershipPF-29 task platform APIConfirm 'charge_reconciliation' is (or can be added to) the TaskSourceType union in @/platform/tasks; verify source_id links to pm_charge_reconciliation_results.idPM + PFPF-29 source_type union extended in same PR as PM-36 task ship2026 Q2PM-36 spec-review 2026-03-27🟡 Triage 2026-04-10: Add union + integration note when PM-36 tasks ship; verify FK target id.
PM-36-automated-charge-reconciliation-INTEGRATION.mdReal-time reconciliation event contract (PM-07)PM-07 event contract designPM-36 Phase 2 deferred feature requires charge_capture_completed or equivalent event from PM-07; design event payload and add to EVENT_CONTRACTS.md when PM-07 Phase 2+ is implementedPMPM-07 P2 publishes charge_capture_completed (or equivalent)2026 Q4PM-36 spec-review 2026-03-27🟡 Triage 2026-04-10: Depends on PM-07 P2 event design; link charge → reconciliation in EVENT_CONTRACTS.md.
PM-35-cost-accounting-INTEGRATION.mdencounter_cost_calculated — FA-35 consumer confirmation of cost_breakdown shapeFA-35 spec update (C-9)Payload schema is documented in EVENT_CONTRACTS.md (encounter_cost_calculated). Outstanding: FA-35 team must confirm required cost_breakdown fields for cost-allocation entries and acknowledge the contract.PM + FAFA-35 written consumer confirmation2026 Q3PM-35 pre-verification 2026-05-11🟡 Narrowed 2026-05-11: schema published; only FA-35 sign-off remains.
PF-96-medicaid-state-compliance-configuration-INTEGRATION.mdCL consumer integration contract (Phases 3–4)CL-02, CL-04, CL-11, CL-40 Phase 2+Confirm which CL functions/hooks currently read AHCCCS constants so refactoring covers all call sites; validate that useClinicalRules() return shape matches CL consumer expectations including CL-11 consent-rule contract validation for Phase 3/4 readinessPF + CLPF-96 migration plan call-site inventory + CL jurisdiction rollout checklist complete2026 Q3PF-96 spec-review 2026-03-29🟡 Triage 2026-04-10: Inventory call sites in PF-96 migration plan; gate on CL jurisdiction rollout checklist.
PF-96-medicaid-state-compliance-configuration-INTEGRATION.mdPM consumer integration contract (Phases 3–4)PM-07, PM-08, PM-18, PM-41 Phase 2+Confirm PM timed-code, filing-deadline, and compliance-window call sites; validate that useBillingRules() return shape covers all PM consumer fieldsPF + PMPM call-site inventory per PF-96 migration plan complete2026 Q3PF-96 spec-review 2026-03-29🟡 Triage 2026-04-10: Same as CL row — complete PM call-site inventory per PF-96 migration plan.
CL-29-EN-65-hedis-fuh-fum-tracking-INTEGRATION.mdPM encounter type extension (inpatient_discharge, ed_visit)PM-03 migration to extend pm_encounters.encounter_type CHECK constraintEN-65 uses proxy mapping (residential_daily for FUH, crisis for FUM) until PM-03 adds true inpatient_discharge and ed_visit encounter type values; full NCQA FUH/FUM denominator compliance requires this extension. Deadline: before June 15, 2026 (NCQA HEDIS MY 2025 final reporting)CL + PMPM-03 migration extends pm_encounters.encounter_type AND CL-29 mapping update ships2026 Q2CL-29-EN-65 spec-review 2026-04-10🔴 Priority: June 15, 2026 — schedule PM-03 migration + CL-29 mapping update in same release train; until then document proxy mapping in CL integration doc only.
LO-INTEGRATION-OVERVIEW.mdRow + integration entries for LO-26 People Analyzer, LO-27 Core Process Documenter, LO-28 L10 Meeting Runtime; planned events people_analyzer_review_completed, seat_holder_flagged, core_process_published, core_process_revised, l10_meeting_concludedLO-26/27/28 spec validation (Phase F of lo-ecosystem-audit-summary-20260418)When LO-26/27/28 are validated and accepted, add a row each to LO-INTEGRATION-OVERVIEW.md and reserve event names in EVENT_CONTRACTS.md (📝 Planned). Until then the proposed lite specs are referenced via PENDING coverage.LOLO-26/27/28 specs validated and accepted (Phase F gated in lo-ecosystem-audit-summary-20260418 §F)2026 Q3LO ecosystem audit 2026-04-18🟡 Tracked in specs/lo/IMPLEMENTATION_LOG.md (LO-26/27/28 integration follow-ups). Proposed by specs/lo/lo-deep-review-20260320.md NS-LO-26/27/28.
PM-53-refund-recoupment-takeback-management-INTEGRATION.mdFA Edge Function consumer contract for payment_refund_issuedFA Cash Receipts / GL consumer Edge Function designFinalize whether to extend existing fa-consume-pm-payment-events or create new fa-consume-pm-refund-events; document GL account mapping per refund_method (cash out vs patient credit liability); finalize fa_journal_entry_id writeback pathPM + FAFA Edge Function design + GL account map signed off2026 Q3PM-53 spec-review 2026-04-19🟡 New IOU — Phase A blocker; resolve before PM-53 Phase A deploy.
PM-53-refund-recoupment-takeback-management-INTEGRATION.mdPM-37 ledger consumer contract (Phase C)PM-37 (proposed) Self-Pay AR Ledger specDefine pm_patient_liability_ledger row schema for refund_issued and recoupment_offset event consumption; idempotency keys; replay strategy for retroactive PM-37 GAPMPM-37 spec authored AND PM-37 Phase 1 ships2026 Q4PM-53 spec-review 2026-04-19🟡 Deferred — Phase C only; PM-53 Phase A/B/D ship without PM-37.
PM-53-refund-recoupment-takeback-management-INTEGRATION.mdPF-10 notification template pm.refund.approval_required payload schemaPF-10 template registration for FR-8Finalize template payload (refund ID, amount bucket, secure deep link) and PF-10 user-preference cadence; no PHI/PII (including patient initials) in cross-channel payloads — fetch patient context post-authenticationPM + PFPF-10 template registration ships2026 Q3PM-53 spec-review 2026-04-19🟡 Phase A blocker for FR-8; light effort.
PM-53-refund-recoupment-takeback-management-INTEGRATION.mdPF-96 jurisdiction profile addition: recoupmentDisputeWindowDaysPF-96 profile schema extensionAdd recoupmentDisputeWindowDays (or equivalent) to PF-96 jurisdiction profile; default Arizona/AHCCCS value; UI banner driven by FR-5.3PM + PFPF-96 profile schema extended AND seeded for Arizona2026 Q3PM-53 spec-review 2026-04-19🟡 Phase B blocker; coordinate with PF-96 owner.
PM-55-patient-access-api-INTEGRATION.md (to be created at PM-55 T002)Full integration doc + cl.part2_consent_granted / cl.part2_consent_revoked publisher contractsCL-11 publisher implementation + PM-55 T002(1) Author PM-55-patient-access-api-INTEGRATION.md covering CL-11/CL-16/PF-04/PF-30/PF-96 touchpoints. (2) CL-11 owner to publish cl.part2_consent_granted / cl.part2_consent_revoked events with PHI-free payload. (3) cl_part2_check(p_patient_id, p_app_registration_id, p_resource_type) SECURITY DEFINER helper in CL-11.PM + CLPM-55 T002 lands AND CL-11 publishes part2 consent events AND cl_part2_check helper deployed2026 Q3PM-55 pre-implementation review 2026-05-06🟡 New IOU — Phase 1 blocker for PM-55 (T027 Part 2 gating). Tracked in PM-55 TASKS.md T010a.

​
Temporary Coverage Placeholders (2026-05-13)

These IDs are tracked here as governance coverage placeholders so audit:integration-contracts can pass while owners decide whether each item belongs in a dedicated *-INTEGRATION.md, a canonical cross-core table, or the intra-core allowlist. This section should be triaged down into authoritative destinations as part of upcoming spec maintenance.
  • CE owner: CE-30, CE-31, CE-32, CE-49, CE-51, CE-52, CE-53, CE-54, CE-55
  • CL owner: CL-58, CL-59, CL-60, CL-61, CL-62
  • FA owner: FA-42, FA-43, FA-44, FA-45, FA-46
  • FM owner: FM-23, FM-24, FM-25, FM-26, FM-27, FM-28
  • FW owner: FW-65, FW-66, FW-67, FW-68, FW-69
  • GR owner: GR-21, GR-22, GR-23, GR-24, GR-25
  • HR owner: HR-39, HR-40, HR-41, HR-42, HR-43
  • IT owner: IT-18, IT-19
  • LO owner: LO-29, LO-30, LO-31, LO-32
  • PF owner: PF-102, PF-103, PF-104, PF-105, PF-106
  • PM owner: PM-67, PM-68, PM-69, PM-70, PM-71
  • RH owner: RH-12, RH-13, RH-14, RH-15, RH-16

​
Closure workflow

When closing a row:
  1. Move the row to a ## Resolved Stubs section below (preserve historical record).
  2. Update the integration doc to remove the stub callout and finalize schemas/payloads.
  3. Re-run npm run audit:integration-contracts to confirm coverage holds.
  4. Reference the resolution in the owning spec’s IMPLEMENTATION_LOG.md.

​
Backlinking

Every open IOU above MUST be back-linked from the owning spec’s PLAN.md or TASKS.md so implementers see the contract dependency before they start work. Use the format:
Pending integration contract: see docs/architecture/integrations/PENDING_CONTRACTS.md row “{stub section name}”. From specs/{core}/plans/, use relative path ../../../docs/architecture/integrations/PENDING_CONTRACTS.md; from specs/{core}/tasks/, use ../../../../docs/architecture/integrations/PENDING_CONTRACTS.md.

​
Resolved Stubs

Integration DocStub SectionResolvedResolution
FA-18-revenue-recognition-advanced-INTEGRATION.mdRPC + event + HTTP alignment2026-04-26Contracts frozen in integration doc, EVENT_CONTRACTS.md § FA-18, and API_CONTRACTS.md § FA-18; primary transport fa_process_revenue_recognition; optional HTTP wrapper. Implementation of DB/RPC remains tracked on FA-18 tasks.