This comprehensive test bank contains 450 multiple-choice questions with detailed
rationales covering the Epic Clarity and Caboodle Access Data Model. Topics include
registration (HSP_ACCOUNT, ARPV_VISITS, PAT_ENC), billing (BillingAccountFact, HAR,
guarantor relationships), insurance structures, appointment scheduling (Cadence,
V_SCHED_APPT), and data warehousing concepts (star schema, fact/dimension tables,
SCD Type 2, bridge tables). Additional topics include relational database design, SQL
query writing, healthcare analytics, regulatory compliance (HIPAA, MACRA), and 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, and Epic
functionality. This resource thoroughly prepares students for understanding Epic's access
data model and healthcare data analytics.
SECTION 1: REGISTRATION DATA MODEL FUNDAMENTALS (Questions 1-50)
1. What does the Registration data model primarily focus on?
A) Clinical documentation and procedures
B) The patient, guarantor, and coverages 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 and revenue cycle management. Unlike clinical documentation, bed
management, or scheduling, registration focuses exclusively on the administrative and
financial aspects of patient care, ensuring accurate patient identification, financial
responsibility assignment, and insurance verification for each encounter.
,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. The HAR serves as the billing
and financial hub for an encounter, linking together all the necessary administrative data
required for claims generation, payment posting, and revenue cycle tracking. It is
important to note that the HAR is encounter-specific, meaning each patient visit generates
its own unique HAR, even if the same patient returns for multiple visits.
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 such as inpatient stays, outpatient procedures, and emergency department
visits. The HSP_ACCOUNT table serves as the authoritative source for hospital billing
registration data in Clarity and contains critical fields such as account numbers, admission
dates, discharge dates, and financial class information that drive the hospital billing
process.
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. SBO is a
configuration that allows organizations to manage both hospital and professional billing
from a unified platform, creating a single HAR for each encounter regardless of the billing
,system used. This consolidation simplifies reporting and revenue cycle management by
providing a single source of truth for all registration data.
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. The ARPV_VISITS table is specifically designed
for professional billing environments where hospital and professional billing remain
separate, allowing organizations to maintain distinct registration records for professional
services that are billed independently from hospital services.
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. The grain being at the
HAR level means that each row represents a unique financial account, making it the ideal
table for analyzing billing-related metrics such as charges, payments, adjustments, and
outstanding balances across the entire organization regardless of the source system.
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 such as professional
billing components that are associated with hospital accounts. The exclusion of VFO HARs
is important for analysts to understand because these special accounts represent financial
, transactions rather than actual patient encounters and would otherwise skew reporting if
not properly filtered out.
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. This grain distinguishes it from HSP_ACCOUNT, which stores all HARs, and
emphasizes that ARPV_VISITS is specifically focused on professional billing encounters.
Understanding this grain is crucial when joining ARPV_VISITS with other tables, as each
row represents a unique professional billing account that may have multiple associated
procedures or services.
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. Unlike billing-focused tables that are at the
HAR grain, EncounterFact captures all encounters including those that may not generate a
bill, such as no-show appointments or encounters that are cancelled. This comprehensive
view makes EncounterFact essential for clinical and operational analytics that require a
complete picture of patient activity.
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. The PAT_ENC table captures both scheduled and
unscheduled visits, including emergency department visits, inpatient admissions, and
outpatient procedures. Understanding that PAT_ENC is at the encounter grain is
rationales covering the Epic Clarity and Caboodle Access Data Model. Topics include
registration (HSP_ACCOUNT, ARPV_VISITS, PAT_ENC), billing (BillingAccountFact, HAR,
guarantor relationships), insurance structures, appointment scheduling (Cadence,
V_SCHED_APPT), and data warehousing concepts (star schema, fact/dimension tables,
SCD Type 2, bridge tables). Additional topics include relational database design, SQL
query writing, healthcare analytics, regulatory compliance (HIPAA, MACRA), and 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, and Epic
functionality. This resource thoroughly prepares students for understanding Epic's access
data model and healthcare data analytics.
SECTION 1: REGISTRATION DATA MODEL FUNDAMENTALS (Questions 1-50)
1. What does the Registration data model primarily focus on?
A) Clinical documentation and procedures
B) The patient, guarantor, and coverages 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 and revenue cycle management. Unlike clinical documentation, bed
management, or scheduling, registration focuses exclusively on the administrative and
financial aspects of patient care, ensuring accurate patient identification, financial
responsibility assignment, and insurance verification for each encounter.
,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. The HAR serves as the billing
and financial hub for an encounter, linking together all the necessary administrative data
required for claims generation, payment posting, and revenue cycle tracking. It is
important to note that the HAR is encounter-specific, meaning each patient visit generates
its own unique HAR, even if the same patient returns for multiple visits.
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 such as inpatient stays, outpatient procedures, and emergency department
visits. The HSP_ACCOUNT table serves as the authoritative source for hospital billing
registration data in Clarity and contains critical fields such as account numbers, admission
dates, discharge dates, and financial class information that drive the hospital billing
process.
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. SBO is a
configuration that allows organizations to manage both hospital and professional billing
from a unified platform, creating a single HAR for each encounter regardless of the billing
,system used. This consolidation simplifies reporting and revenue cycle management by
providing a single source of truth for all registration data.
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. The ARPV_VISITS table is specifically designed
for professional billing environments where hospital and professional billing remain
separate, allowing organizations to maintain distinct registration records for professional
services that are billed independently from hospital services.
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. The grain being at the
HAR level means that each row represents a unique financial account, making it the ideal
table for analyzing billing-related metrics such as charges, payments, adjustments, and
outstanding balances across the entire organization regardless of the source system.
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 such as professional
billing components that are associated with hospital accounts. The exclusion of VFO HARs
is important for analysts to understand because these special accounts represent financial
, transactions rather than actual patient encounters and would otherwise skew reporting if
not properly filtered out.
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. This grain distinguishes it from HSP_ACCOUNT, which stores all HARs, and
emphasizes that ARPV_VISITS is specifically focused on professional billing encounters.
Understanding this grain is crucial when joining ARPV_VISITS with other tables, as each
row represents a unique professional billing account that may have multiple associated
procedures or services.
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. Unlike billing-focused tables that are at the
HAR grain, EncounterFact captures all encounters including those that may not generate a
bill, such as no-show appointments or encounters that are cancelled. This comprehensive
view makes EncounterFact essential for clinical and operational analytics that require a
complete picture of patient activity.
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. The PAT_ENC table captures both scheduled and
unscheduled visits, including emergency department visits, inpatient admissions, and
outpatient procedures. Understanding that PAT_ENC is at the encounter grain is
