CLIC — Clinical List Intent and Configuration
Microproduct UI for digitizing drug intent (Form F) creation and management within OptumRx PBM. Embedded in Benefit Central (external clients) and Ops Portal (internal users). Submissions flow downstream to DOSE for orchestration and delivery to RxClaim via CAT.
Phase 1 scope: Form F template builder, client setup, drug search via FSOT, drug intent capture, and submission to downstream (DOSE → CAT → RxClaim).
Topics
| What you'll learn | |
|---|---|
| What is CLIC | Problem statement, personas, end-to-end flow, and where CLIC fits in the pipeline |
| Form F Lifecycle | How a Form F request is created, progresses through draft/submitted states, and is delivered downstream |
| System Integrations | All upstream and downstream systems: AuthPass, FSOT, RxClient360, DOSE, CAT |
| Data Model | MongoDB collections — Client, Field, Template, FormFRequest, DrugIntent — plus the shared Java data-model library |
| Access & Roles | Personas, AuthPass secure groups, role-based access matrix, and how to request access |
Technical implementation (GitHub-sourced)
| What you'll learn | |
|---|---|
| UI / Surface | The Next.js application and shared component monorepos |
| Backend API | The core Clinical List Intent and Configuration API service |
| BFF Layer | The backend-for-frontend service between UI and core API |