Support for integration with a third-party enrollment system
Pega Sales Automation for Healthcare can send account enrollment details to a third-party enrollment system and receive real-time enrollment dates and status information from a third-party enrollment system. This article contains technical details for Lead System Architects who configure the integration.
Sending account and member details to the third-party enrollment system
After the Opportunity-Application stage is completed and the opportunity is won, Pega Sales Automation for Healthcare uses a REST API to send account enrollment details in XML format to the third-party enrollment system. The spmUpdateAccountEnrollment activity, which is part of the spmUpdateAccount flow, calls the D_EnrollAccountDetails data page. The D_EnrollAccountDetails data page calls the EnrollAccountDetails connector to send the account enrollment details in XML format.
Receiving enrollment data from the third-party enrollment system
After the third-party enrollment system completes the member enrollment, the enrollment system sends the enrollment details back to Pega Sales Automation for Healthcare. Pega Sales Automation for Healthcare uses the received enrollment information to track historical enrollment data for the Account, and also to renew an Account when it is about to expire.
Simulated third-party enrollment system
In order to model an integration with a third-party enrollment system, Pega Sales Automation for Healthcare has simulated a response coming from a third-party enrollment system. With the simulation, Pega Sales Automation for Healthcare receives enrollment period details such as enrollment start and end dates, and enrollment IDs. The enrollment ID is unique for each of the account’s plan types, and each plan type can have a different enrollment period.
Database table with simulated data
Pega Sales Automation for Healthcare provides a database table with simulated data as a reference point for your integration with a third-party enrollment system. The spm_data_accountenrollment database table is part of the PegaHCSPM-Data-AccountEnrollment class.
The simulated third-party enrollment system populates the following database table columns:
| Column | Type(length) | Purpose |
| accountid | Varchar(255) | Pega Sales Automation for Healthcare account case ID of the enrolled account |
| accountname | Varchar(255) | Enrolled account name |
| opportunityid | Varchar(255) | Pega Sales Automation for Healthcare Opportunity case ID |
| opportunityname | Varchar(255) | Opportunity name |
| plantype | Varchar(32) | Medical, Dental, or Vision type |
| enrollmentstartdate | Varchar(8) | Plan enrollment start date |
| enrollmentenddate | Varchar(8) | Plan enrollment end date |
| censusid | Varchar(255) | Pega Sales Automation for Healthcare census ID |
| partnerid | Varchar(255) | Pega Sales Automation for Healthcare partner ID |
| sellingmode | Varchar(32) | B2C or B2B |
| marketsegment | Varchar(32) | SmallGroup, Individual, LargeGroup, or Medicare |
| enrollmentid | Varchar(255) |
Third-party enrollment system extension points
The simulated third-party enrollment system has the following additional extension points:
- Data page: D_EnrollAccountDetails
- REST Connector: EnrollAccountDetails
- REST Service API: EnrollAccountDetails
- Service activity: EnrollAccountDetails
- Pre data transform: EnrollAccountDetailsPRE
- Post data transform: EnrollAccountDetailsPOST
Data exchange process for sending simulated data to Pega Sales Automation for Healthcare
A clipboard page of type Account is used for data exchange. In the pre-data transform of the D_EnrollAccountDetails data page, the simulated third-party system populates the account page with the necessary data and converts it to XML. The simulated third-party system uses a REST call to send the XML. The third-party enrollment system replies, the reply is re-mapped to a clipboard page, and then it is used to generate enrollment records with enrollment dates. Pega Sales Automation for Healthcare attaches the XML data to the account case type as an XML file.
Previous topic Reports Next topic Rating engine for healthcare plan rates