CLIC — Clinical List Intent and Configuration
Purpose
CLIC is a Microproduct (with surface UI) within the OptumRx Pharmacy Benefits Management (PBM) transformation roadmap. It digitizes the existing manual process for drug intent creation and management — replacing paper-based Form F workflows with a structured, auditable, web-based experience.
One-sentence summary: A Clinical Consultant or Client logs into Benefit Central or Ops Portal → fills out a Form F (drug intent request) → CLIC captures, validates, and routes the payload downstream to DOSE → CAT → RxClaim.
Phase 1 scope: Form F template builder, client setup, drug search via FSOT, drug intent capture, draft/submit lifecycle, downstream push via DOSE.
The Problem It Solves
Drug intent requests (Form F) were previously handled manually — paper forms, email chains, and tribal knowledge spread across teams. This created:
- No auditability for who requested what, when, and why
- No structured validation before reaching RxClaim
- No self-service for external clients
CLIC replaces this with a guided digital workflow that enforces required fields, validates drug data via FSOT at entry, and produces a structured payload that DOSE can process automatically.
How it Works
Personas
CLIC is accessed via two surfaces, each with distinct personas:
Benefit Central (external clients — OHID login)
| Persona | Audience | What they can do |
|---|---|---|
| ClinicalConsultant | Internal | Search, view, create, update drug intent requests on behalf of clients |
| Client | External | View and create their own drug intent requests |
Ops Portal (internal users — MSID login)
| Persona | Audience | What they can do |
|---|---|---|
| ClinicalConsultant | Internal | Search, view, create, update drug intent requests |
| ClinicalCoder | Internal | Search, view, create, update drug intent requests; coding and validation |
| Admin | Internal | Administration setup — client search, field creation, template creation, client-to-template mapping, environment selection |
4 Core Capabilities
| # | Capability | What it delivers |
|---|---|---|
| 1 | Form F Template Builder | Admin-created configurable templates with reusable fields and sections; clients get a customized intake form |
| 2 | Drug Search & Intent Capture | GPI/NDC/name search via FSOT integration; drug-level intent fields captured per record |
| 3 | Submission & Audit | Form F moves through draft → submitted states with full audit trail on every change; immutable intent records on submission |
| 4 | AI Coding Workspace (Phase 2+) | Clinical coders review Form F data and use AI-assisted suggestions to map drug intent to RxClaim codes before final submission |
Release Timeline (2026)
| Release | Date | What shipped |
|---|---|---|
| Phase 1 foundation | Q1 2026 | Template builder, client setup, drug search, Form F creation |
| 8/01 Release | Aug 1, 2026 | FSOT integration, UAT-validated Form F end-to-end |
| 9/08 Release | Sep 8, 2026 | CT/ST protocol config, Test Bed, Admin Super User role, Ops Portal Web Component |
| 9/30 Release | Sep 30, 2026 | Role Level Security, Phase 2 enhancements, AI Coding Workspace (frontend + backend) |
| 10/28 Release | Oct 28, 2026 | CLIC–DOSE integration, Benefit Central OHID client flow, AI Assistant MVP |
| 11/30 | Nov 30, 2026 | Orchestration Layer DOSE with one automation use case |
AIDE Application ID
AIDE_009175 3 (Project Lead: Anurag Agarwal)
Repositories & Technical Stack
The CLIC microproduct is implemented across 6 GitHub repos spanning UI, backend API, and shared library layers. See UI / Surface, Backend API, BFF Layer, and Data Model for implementation-level detail.
| Repo | Role |
|---|---|
RxDrugIntent-Surface | Next.js UI application — the user-facing surface (login, plan/client forms, historical client views) |
Rx-DrugIntent-MP | Frontend micro-product monorepo (Lerna + Yarn workspaces) — packages and webcomponent surfaces |
PBRSharedComponent | Shared component library, built on the same micro-product template |
DrugIntentBFF | Backend-for-frontend service (Java) sitting between the UI and the core API |
RxDrugIntent-MP-Core | Core backend API service — the CLIC API services |
RxDrugIntentDataModelLib | Shared Java data-model library (DTOs, entities, enums) |
| Detail | Value |
|---|---|
| Frontend stack | Next.js, React, Yarn workspaces, Lerna, Storybook |
| Backend stack | Java, Spring (Boot/WebFlux), Maven |
| Data store | MongoDB Atlas (Reactive) |
| Environments | dev, test |