Mapping Guide

This page describes the actions and data required to implement to Ideon's ICHRA solution.

The following information supports Ideon sending enrollments for Individual Coverage Health Reimbursement Arrangements.

What changes are needed to send ICHRA enrollments with Ideon?

• Notify Ideon that a given coverage_period is for ICHRA management

• Optionally: Notify Ideon that a given coverage_period is using the ICHRA payment solution

  • This allows us to begin the process of generating secure payments for a given group

• Create and provide a plan , with associated plan_identifier (hios id)

• optionally, provide the expected policy_premium_amount , which we can reconcile with existing data to ensure accuracy at time of enrollment

Each endpoint in the traditional workflow is used during this implementation, with limited information required at each step:

• a Group shell is created

• a Coverage Period is created to show the carrier_name and time period

• under a Coverage Period, each Plan option is created

• Subscribers and dependents are created

• Plans are associated with Subscribers by creating Qualifying Life Event objects

Required Changes

Endpoint	Ideon Field	Usage & Mapping
POST subscriber/[id]/qualifying_life_event	plan_id policy_premium_amount (optional)	plan_id is necessary if an Ideon Quote Plan Id is not provided. Providing the expected policy_premium_amount , which we can reconcile with existing data to ensure accuracy at time of enrollment
POST subscriber/[id]/qualifying_life_event	plan_quote_id	Future Enhancment. Discuss with Ideon whether you can provide this data, based on previous quotes made via IdeonQuote's API

Additional Documentation

For a full API specification, see https://app.swaggerhub.com/apis/VericredEnrollments/Enrollments/0.3.3#