Free EPIC EDI101 Practice Exam with Questions & Answers | Set: 2

In Epic’s Identity framework, an ID Type is explicitly linked to a single Chronicles master file (e.g., EPT for patients, SER for providers). This one-to-one relationship ensures that the system knows exactly which master file to search when an ID of that type is received in a message. You cannot use a single ID Type definition to identify both a patient and a provider.

Workqueue rules in Bridges are generally not retroactive by default. Once you update a rule, only future occurrences of the error will be caught by the new logic (Option A). Any errors that were already in the workqueue from previous rules will remain there (Option C). To get past occurrences of the new error into the workqueue, you would need to run the Maintenance utility described in Question 26.

In Epic, Identity is the required framework for mapping record-level identifiers, especially for patients. Translation Tables are intended for mapping " Category Lists " (like Gender, Race, or Marital Status) where there are a limited number of static values. Because patient IDs are unique to every record and number in the millions, they cannot be managed via a simple translation table.

The Error Resolution Planner is a tool for triaging and planning , not for final configuration. Selecting " Suppress " within the planner indicates an intention or a decision that the error should be suppressed, but the actual administrative suppression must still be configured in the Error Code or Interface records to take effect.

The Specification Audit Report is designed to track configuration changes—the " build " of the interface. It records modifications to critical connectivity settings like the Port and IP Address (Option C) and functional logic changes in Profile Variables (Option D). Operational data like Message Volume (Option A) or active Interface Alerts (Option B) are monitored in real-time activities and are not part of the static specification audit.