Overview
PM-51 provides browser-based RPA (Robotic Process Automation) for payer portal interactions: claim status checks, remittance/EOB downloads, and eligibility verification for payers without EDI support. It operates as an automation layer that extends PM-08, PM-02, and PM-09 with portal-sourced data.Platform Foundation Dependencies
Event Contracts
Published Events
1.pm.rpa.execution_completed
- Publisher: PM (RPA — durable worker job
rpa-execute-bot) - Subscribers: PM-08 (claim status refresh), PM-09 (staged documents available)
- Payload:
- Status: 📝 Planned
pm.rpa.consecutive_failures
- Publisher: PM (RPA —
rpa-failure-alerterEdge Function) - Subscribers: PF-10 (Notifications)
- Payload:
- Status: 📝 Planned
Same-Core Dependencies (PM Internal)
Edge Functions
Durable Worker Job:
rpa-execute-bot (FW-46) — Headless browser execution with PF-75 credential decryption, navigation engine, data extraction.
Security Considerations
- Portal credentials decrypted only at bot execution time via
pf_retrieve_credential()SECURITY DEFINER function - Execution logs contain claim/member identifiers only — no clinical PHI
- Error screenshots stored with RLS and auto-purged after 30 days
- Legal/compliance review required per payer before production deployment (ToS compliance)
Contract Validation
- Event payloads match schema (pm.rpa.execution_completed, pm.rpa.consecutive_failures)
- PF-75 credential vault FK and decryption pattern validated
- FW-46 durable worker job interface confirmed
- PF-10 notification delivery verified
- PM-08 claim status update with
source = 'rpa_portal'attribution