Lifecycle Actions

Manage consumer lifecycle transitions and benefit coverage updates. Lifecycle Actions provide a robust, discovery-driven framework for handling complex offboarding events and mid-year coverage changes. By combining impact analysis, synchronous execution, and asynchronous status tracking, these resources ensure that transitions—such as ending consumer benefit coverage—are accurate, transparent, and compliant with plan rules. Use these tools to automate the complexities of plan bundles, dependent coverage loss, and prorated financial adjustments while maintaining a clear audit trail of all lifecycle events.

Core Termination Services

Discovery: Get Termination Form Data

The Discovery endpoint acts as the prerequisite for any offboarding workflow by retrieving a “menu” of valid options tailored to a specific consumer.

• Menu Retrieval: Dynamically obtain available_plans, available_bundles, and reason_codes to populate administrative interfaces.

• Date Validation: Access the valid_termination_dates list to ensure the selected date adheres to business rules and plan configurations.

Execution & Impact Analysis (Requests)

The Termination Request engine is the central component for both simulating and committing coverage changes.

• Impact Analysis (Preview Mode): Use PREVIEW mode to perform a “dry-run” analysis, which identifies affected_dependents losing coverage and the financial_impact of prorated refunds or premium adjustments.

• Commitment (Execute Mode): Transition to EXECUTE mode to finalize the offboarding process and commit changes.

• Processing Strategies: Choose SYNCHRONOUS for immediate results or ASYNCHRONOUS to queue high-volume requests for background processing.

Tracking & Auditing

Maintain full visibility into the lifecycle process with dedicated status and history endpoints.

• Request Tracking: Poll for the status of asynchronous requests to monitor transitions through PENDING, PROCESSING, COMPLETED, or FAILED states.

• Lifecycle Auditing: Retrieve a paginated list of all historical termination activity for a specific consumer.

Integration Standards

Scopes & Permissions

Lifecycle operations require specific administrative authorizations:

Operational Guardrails

• Retry Safety: All POST requests require an Idempotency-Key (UUID) to ensure the termination is not processed twice if a timeout occurs.

• Organizational Context: Requests must include a Business-Entity-Id (Max 50 characters) that matches the consumer’s organizational context.

• Standardized Formats: Dates follow ISO 8601 (YYYY-MM-DD) , and processing timestamps utilize RFC 3339 in UTC.

• Request Identification: Generated Request IDs follow the specific pattern ^REQ-\d{4}-\d{6}$.

Global Error Reference