Question

configuring plan mapping & query chaining

#14 which of the following components need to be configured in order to set up plan mapping?

select all that apply (3 pts)

a. interface monitor
b. data pull
c. incoming settings record
d. the map_service_to profile variable in the incoming interface spec
e. general table

Explanation:

Identify the core configuration requirements for Epic RTE Plan Mapping

In Epic Real-Time Eligibility (RTE) configuration, setting up plan mapping (which maps incoming payer response codes to Epic benefit plans) requires specific components:

• Data pull: Used to extract the necessary values from the incoming response.
• Incoming settings record: Houses the mapping rules and links the data pull to the target plans.
• General table: Used to map external values to internal Epic values.

Evaluate the given options against Epic RTE specifications

• A. Interface Monitor: Used for monitoring and troubleshooting, not for configuring plan mapping rules.
• B. Data pull: Correct. A data pull extension is required to retrieve the plan identifier from the response.
• C. Incoming settings record: Correct. The incoming settings record (HFL) is where plan mapping is defined.
• D. The MAP_SERVICE_TO profile variable: This is used for service type mapping, not plan mapping.
• E. General table: Correct. General tables (HFT) are used within plan mapping to translate external codes to Epic plan IDs.

Answer:

• A. Interface Monitor
• B. Data pull (Correct answer)
• C. Incoming settings record (Correct answer)
• D. The MAP_SERVICE_TO profile variable in the Incoming Interface Spec
• E. General table (Correct answer)