Extending the View Benefits Microjourney
|Request to Publish|
|Description||Learn how to extend view benefits microjourney|
|Version as of||8.5|
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.
When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.
↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
View Benefits Microjourney
The View Benefits Microjourney™ answers questions about a member's coverage. Agents can quickly access critical, personalized information, and focus on the customer's needs. For example, it might be a simple eligibility check or a complex scenario that requires multiple types of coverage information, such as cost share responsibilities, claims, and limits.
Personas, channels, and use cases
The following table shows the personas and channels for each use case in this Microjourney.
|Member services representative||Agent-assisted||A member services representative assists health plan members in understanding and using their benefits, for example whether an authorization is required for a procedure, whether members are covered for a benefit, whether they have visits remaining in the benefit year, or a member’s cost-share responsibilities for an upcoming service.|
|Provider services representative||Agent-assisted||
|Health plan member||Agent-assisted||
Use the Data model page in App Studio to quickly view and understand the relationship between all data objects in the application. You can add, update, and delete data objects without exiting the visual data model. For information about the Data model page, see Data modeling. For information about connecting to external data entities, see Managing data and integrations with the Integration Designer.
The figure shows the entity relationship diagram (ERD) for this Microjourney. For each data object, the ERD shows only the properties that apply to this Microjourney
Extending the Microjourney
In App Studio, open the View Benefits Microjourney (Case types > View Benefits). Certain rules require switching to Dev Studio in order to update them. App Studio indicates when this is required.
Stage 1 - Verify
By default, Stage 1 - Verify is set to “skip stage”.
To extend this stage to meet your organization's business needs:
- Use the DetermineEligibilityToRun decision table to specify individuals who call on behalf of a member, for example, an office manager from the provider service, to launch a case.
- In App Studio, set the Allow user to bypass verification switch (Tools > Verification) and configure the steps in the stage to include an additional verification step.
Stage 2 - Intake
The Intake stage handles the member searches upon provider request. The D_Search_Member data page retrieves the member information and related plan information. To retrieve data from your own implementation-layer classes for member, subscriber, and plan tables, override the LoadMembersBasedOnSearchCriteria report definition, save the rule into your implementation-layer member class, and update the subscriber, policy, and plan data classes in the Data Access tab of the LoadMembersBasedOnSearchCriteria rule. For more information, see Learning about report definitions.
Note: By default, there is nothing in Stage 2 that applies to member services. This stage is related to provider services only.
Stage 3 – Process request
This stage includes steps to select a benefit to review, display coverage information, display related claims, and review the information with the customer. The steps in this stage can be re-run so that agents can discuss multiple benefits within one interaction.
The Benefit search step includes both a search and a list common benefits, which are bookmarked to save agents time. Operators with the role of CS:ExpressMgrTools can define these bookmarks in the Interaction portal by clicking Application Tools > View Benefits > Configure.
Both the Benefit search and the common benefits configuration tool use a type-ahead search that is populated by the D_BenefitNamesByPlanPurposeAndName data page. Update the data source to point to your plan benefits system of record.
The Benefit search step retrieves the benefits that are bookmarked in the configuration tool by using the read-only D_GetCommonBenefits data page.
Display of coverage information
This step displays rich coverage information to enable highly personalized interactions:
- Plan benefit coverage by network or tier: Information about the selected benefit, such as whether a deductible applies or copay amount, is retrieved by using the D_BenefitsByPlanAndPurpose datapage.
- Benefit usage: Usage accumulators, such as how many times a benefit has been used in a benefit year, are retrieved by the D_Getaccumulatorheader datapage.
- Plan level cost shares: Also displays the member’s plan-level cost shares and statuses, such as what types of deductibles are in a plan and how much has been accumulated to date.This information is retrieved by using the D_GetPlanAccumulators datapage, which in turn uses the GetPlanLevelAccumulators report definition. If you add other properties, then you must update this report definition and the MapAccumulatorsData data transform.
Claims are retrieved by using the D_FetchClaimsUsingSearchCriteria data page, which should point to an organization’s claims system of record.
If you maintain your history table for auditing the reviewed benefits, use the D_ReviewedBenefitsHistoryList data page to retrieve the benefit summary information that was captured in a given case or a specified time period.
Stage 4 - Resolve
This stage completes the inquiry and provides options to send information to the customer. Email is the default setting.
You can modify the IsDistributionMethodEmailcondition When rule in Dev Studio if your organization requires another communication channel. You can also use this stage to extend your workflow if your organization requires a post-inquiry follow-up.
a. Click the Is communication channel selected email step.
b. In the right pane, add a path, and then add the steps that are specific to your routing logic.