All members who are auto-renewed will be auto-effectuated during the auto-renewal process. Issuers are not required to send effectuation files for auto-renewals.
If a member is renewed into a different issuer’s plan, binder payment would be required and issuers would be required to send an effectuation for these enrollments.
Yes, the Exchange Assigned Member ID will be changed to new values similar to the process with FFM to SBE migrations. BeWell and GetInsured will provide a mapping file that has the consumer’s existing Exchange-Assigned Member ID and new Exchange-Assigned Member ID post-transition.
This ID change is only for Exchange-Assigned Member IDs; the Issuer-Assigned Member IDs do not need to change.
For Plan Year 2026 coverage and beyond, 820 files for APTC payments will only be sent to issuers from CMS following the standard monthly.
There will be two urls/portals until the full data migration date (est to be March 2026). Until that date, all PY2025 transactions will be handled in the current Optum platform. Following that date, the GetInsured platform would be the single system for prior year (2025) and current year (2026) transactions. All 2026 application and enrollment transactions will be in the GetInsured platform, beginning with renewals for PY2026 (October 2025).
There will be two urls/portals until the full data migration date (est to be March 2026). Until that date, all PY2025 transactions will handled in the current Optum platform. Following that date, the GetInsured platform would be the single system for prior year (2025) and current year (2026) transactions. All 2026 application and enrollment transactions will be in the GetInsured platform, beginning with renewals for PY2026 (October 2025).
