ACTUAL EXAM QUESTIONS AND CORRECT ANSWERS
WITH RATIONALE ALREADY GRADED A+
This comprehensive document contains 400 multiple-choice questions and detailed
rationales covering the Epic Clarity and Caboodle Access Data Model, specifically
designed for the COG220 curriculum. The questions span the full spectrum of the
access data model including registration (HSP_ACCOUNT, ARPV_VISITS,
PAT_ENC), billing and financial data (BillingAccountFact, HAR, guarantor
relationships), insurance coverage structures, appointment scheduling (Cadence,
V_SCHED_APPT, ASN), and data warehousing concepts (star schema, fact and
dimension tables, SCD Type 2, bridge tables). Additional topics include relational
database design principles, normalization, primary and foreign key relationships,
SQL query writing, Access database objects and properties, healthcare analytics,
and key Epic-specific identifiers like PAT_ID, MRN, and encounter keys. Each
question provides four answer choices with the correct answer identified and a
comprehensive rationale explaining the underlying data model concept, table
structures, join logic, or Epic functionality. This resource thoroughly prepares
students for understanding Epic's access data model and healthcare data analytics.
1. What does the Registration data model primarily focus on?
A) Clinical documentation and procedures
B) The patient, guarantor, and coverage(s) used on an encounter
C) Facility bed management and transfers
D) Provider scheduling and availability
Correct Answer: B
Rationale: The Registration data model in Epic is specifically designed to
capture and manage patient demographic information, the responsible guarantor
(the person or entity financially responsible for the account), and the insurance
coverages that are applicable to a specific healthcare encounter. This data forms
the financial and administrative foundation for billing .
,2. What is the HAR (Hospital Account Record) in Epic?
A) A record containing a patient's clinical history
B) A record consolidating registration information active for an encounter
C) A schedule of provider appointments
D) A log of all user actions in the system
Correct Answer: B
Rationale: The HAR is a critical Epic record that consolidates all active
registration information for a specific patient encounter. This includes the patient's
identity, the responsible guarantor, and all insurance coverages in effect. It serves
as the billing and financial hub for an encounter .
3. In which Clarity table is registration information stored for an encounter that is
billed in Resolute Hospital Billing (HB)?
A) ARPV_VISITS
B) PAT_ENC
C) HSP_ACCOUNT
D) BillingAccountFact
Correct Answer: C
Rationale: For hospital billing (Resolute HB), encounter registration information
is stored in the HSP_ACCOUNT table. This table holds the financial and
registration data for hospital-based services .
4. In which table is registration information stored for an encounter billed in
Resolute Professional Billing (PB) when the organization uses Single Billing
Office (SBO)?
A) ARPV_VISITS
B) HSP_ACCOUNT
C) PAT_ENC
D) BillingAccountFact
Correct Answer: B
Rationale: Even when an encounter is billed through Resolute Professional
Billing, if the organization uses Single Billing Office (SBO) to consolidate billing,
the registration information is stored in the HSP_ACCOUNT table, similar to HB
encounters .
5. What is the name of the table that stores registration information for an
encounter billed in Resolute Professional Billing (PB) when the organization does
NOT use SBO?
A) HSP_ACCOUNT
B) BillingAccountFact
, C) ARPV_VISITS
D) PAT_ENC
Correct Answer: C
Rationale: When an organization does not use Single Billing Office, PB
encounters store their registration information in the ARPV_VISITS table. This
distinguishes them from HB encounters and PB encounters using SBO .
6. What is the grain of the BillingAccountFact table?
A) One row per patient
B) One row per provider
C) One row per HAR, regardless of how it is generated
D) One row per patient encounter
Correct Answer: C
Rationale: BillingAccountFact in the Caboodle data warehouse contains exactly
one row for every Hospital Account Record (HAR), irrespective of which Resolute
system (HB or PB) generated it. This provides a unified view of all financial
accounts .
7. What is the grain of the HSP_ACCOUNT table?
A) One row per patient
B) One row per HAR, not including VFO HARs
C) One row per patient encounter
D) One row per provider
Correct Answer: B
Rationale: The HSP_ACCOUNT table in Clarity stores one row for every
Hospital Account Record (HAR) that is used in Resolute billing systems,
excluding VFO (Virtual Fiscal Object) HARs. VFO HARs are typically used for
special financial scenarios .
8. What is the grain of the ARPV_VISITS table?
A) One row per patient
B) One row per HAR
C) One row per PB Visit HAR
D) One row per provider
Correct Answer: C
Rationale: ARPV_VISITS is the table used for professional billing registration
when an organization does not use SBO. It stores one row for every PB
(Professional Billing) Visit HAR .
9. What is the grain of the EncounterFact table?
, A) One row per HAR
B) One row per patient
C) One row per patient encounter
D) One row per provider
Correct Answer: C
Rationale: EncounterFact is a core fact table in the Caboodle data warehouse. It
contains one row for every patient encounter, making it the central table for
analyzing patient visits, clinical activity, and associated metrics .
10. What is the grain of the PAT_ENC table in Clarity?
A) One row per HAR
B) One row per patient
C) One row per patient encounter
D) One row per provider
Correct Answer: C
Rationale: PAT_ENC is the Clarity equivalent of the EncounterFact table and
serves as the primary source for encounter-level data. It contains one row for every
patient encounter, allowing for detailed reporting on visits .
11. A patient's MRN is guaranteed to be unique across all patients on the same
instance of Epic. Is this statement true or false?
A) True
B) False
Correct Answer: B
Rationale: MRNs are external identifiers that can be shared across different
organizational entities or systems. For example, a patient might have different
MRNs for different hospital systems. Epic uses internal IDs (like PAT_ID) which
are guaranteed unique within the system .
12. Which of the following correctly describes the difference between internal and
external identifiers?
A) Internal identifiers are recognizable by users; external identifiers are
guaranteed unique
B) Internal identifiers are guaranteed unique but not recognizable by users;
external identifiers are recognizable but not guaranteed unique
C) Both are guaranteed unique by Epic
D) Both are recognizable by users but not guaranteed unique
Correct Answer: B
Rationale: Internal identifiers (e.g., PAT_ID) are created by the system and are
unique, ensuring data integrity for joins. However, they are not user-friendly.