Sunfire Integration Data Mapping
Audience: Admins, Developers, Automation Builders, Support & Operation teams, and Solution Architects
Purpose: Explains what data is sent between Kizen and Sunfire and when that data is exchanged during quoting and enrollment.
Overview
This page describes how data is exchanged between Kizen and Sunfire during a Sunfire session and completed enrollment. When Sunfire is launched from a Contact record, Kizen sends required demographic information to pre-fill the quote or enrollment experience.
Once the session and enrollment are complete, Sunfire returns enrollment and session details back to Kizen. This data exchange helps keep Contact records up to date, supports accurate record matching, and ensures enrollment information is captured consistently across both systems.
When Data is Sent vs Returned:
Data is sent from Kizen to Sunfire when a user launches Sunfire from a Contact record. This data is used to pre-fill the quoting or enrollment experience.
Data is returned from Sunfire to Kizen after a Sunfire session or enrollment is completed. Returned data includes enrollment details and selected session information, which are used to update the Contact record in Kizen.
Data Sent from Kizen to Sunfire
When you launch Sunfire from Kizen, the contact record must include the basic demographic fields listed below. All other fields are optional.
Basic demographics (Name, Date of birth, Address)
Contact record
Providers (optional)
Contact record
Pharmacy (optional, one only)
Contact record
Drugs (optional)
Contact record
Data Returned from Sunfire to Kizen
Kizen receives information from both the enrollment and session once the process is complete.
Enrollment data returned to Kizen:
First Name
Last Name
Email
Home Phone
Address (street, city, state, county, ZIP)
Gender
DOB: (mm/dd/yyyy)
FIPS (county code)
Medicare ID
Fields returned to Kizen from a session include:
Providers
Pharmacy
Drugs
What's Next
Next, continue to Sunfire Contact Matching Rules to understand how returned enrollment data is matched to existing Contacts in Kizen and how duplicate records are prevented.
Last updated
Was this helpful?