COG220 Access Data Model Actual Exam Newest
2025/2026 Questions and Correct Answers
Already Graded A+
Which of the following join conditions would connect each hospital account to its
guarantor's current information and exclude historical information? - CORRECT
ANSWER-BillingAccountFact.GuarantorDurableKey = GuarantorDim.DurableKey
AND GuarantorDim.IsCurrent = 1 (IsCurrent allows to filter to current (1) or not
current (0))
How many patient encounters may be associated with a guarantor record? -
CORRECT ANSWER-0 or any number of encounters (different than one
guarantor account to one HAR)
What does VERIFICATION.VERIF_STATUS_C represent? - CORRECT ANSWER-
The current status of a verification record
A user changed the status of a VRX record about a guarantor. That was not the
final change to the VRX record's status. What would VERIFICATION store? -
,CORRECT ANSWER-The ID of the guarantor who was verified. (Note: if it is
looking for historical info, an HX table would suffice)
Registration - CORRECT ANSWER-Focuses on the patient, guarantor, and
coverage(s) used on an encounter
HAR - CORRECT ANSWER-Consolidates registration information active for an
encounter (patient, guarantor, coverage(s)).
Registration information for an encounter that is billed in Resolute HB -
CORRECT ANSWER-HSP_ACCOUNT
Registration information for an encounter that id billed in Resolute PB and uses
SBO - CORRECT ANSWER-HSP_ACCOUNT
Registration information for an encounter that is billed in Resolute PB and
organization does not use SBO - CORRECT ANSWER-ARPV_VISITS
BillingAccountFact - CORRECT ANSWER-One row per HAR, regardless of how it
is generated
,HSP_ACCOUNT - CORRECT ANSWER-One row per HAR, not including VFO
HARs
ARPV_VISITS - CORRECT ANSWER-One row per PB Visit HAR
EncounterFact - CORRECT ANSWER-One row per patient encounter
PAT_ENC - CORRECT ANSWER-One row per patient encounter
Linking registration data to guarantors and coverages - CORRECT ANSWER-
PAT_ENC only stores primary coverage, it is best use to identify the hospital
encounter for a patient encounter to find its registration data (one of the HSP
tables depending on how the encounter was billed).
BillingAccountEncounterMappingFact - CORRECT ANSWER-Links encounters
(EncounterFact) with HARs (BillingAccountFact)
[Clarity] Connect a HAR and its encounters - CORRECT ANSWER-Start from an
encounter and join to its HAR with PAT_ENC_4 or PAT_ENC_HSP. Also, you cab
use HSP_ACCT_PAT_CAN
, Internal IDs - CORRECT ANSWER-Guaranteed to be unique by Epic since
patients could have the same MRN (external IDs). ex: PAT_ID
Patient Identifiers - CORRECT ANSWER-Report consumers recognize MRN - but
to define a relationship in SQL we need to use/join with the internal IDs in Clarity
and durable keys in Caboodle. You can still display MRN, just do not join with
MRN.
Patient DVO - CORRECT ANSWER-PatientDim & Patient
Guarantor - CORRECT ANSWER-One patient can use different guarantor
accounts across encounters - a single HAR will only use one guarantor account
ACCT_GUAR_PAT_INFO - CORRECT ANSWER-Represented the general
relationships between guarantors and patients without indicating the specific
registration data for an encounter
ACCT_COVERAGE & PAT_ACCT_CVG - CORRECT ANSWER-Relationships
between guarantors, patients, and coverages at only a general level
2025/2026 Questions and Correct Answers
Already Graded A+
Which of the following join conditions would connect each hospital account to its
guarantor's current information and exclude historical information? - CORRECT
ANSWER-BillingAccountFact.GuarantorDurableKey = GuarantorDim.DurableKey
AND GuarantorDim.IsCurrent = 1 (IsCurrent allows to filter to current (1) or not
current (0))
How many patient encounters may be associated with a guarantor record? -
CORRECT ANSWER-0 or any number of encounters (different than one
guarantor account to one HAR)
What does VERIFICATION.VERIF_STATUS_C represent? - CORRECT ANSWER-
The current status of a verification record
A user changed the status of a VRX record about a guarantor. That was not the
final change to the VRX record's status. What would VERIFICATION store? -
,CORRECT ANSWER-The ID of the guarantor who was verified. (Note: if it is
looking for historical info, an HX table would suffice)
Registration - CORRECT ANSWER-Focuses on the patient, guarantor, and
coverage(s) used on an encounter
HAR - CORRECT ANSWER-Consolidates registration information active for an
encounter (patient, guarantor, coverage(s)).
Registration information for an encounter that is billed in Resolute HB -
CORRECT ANSWER-HSP_ACCOUNT
Registration information for an encounter that id billed in Resolute PB and uses
SBO - CORRECT ANSWER-HSP_ACCOUNT
Registration information for an encounter that is billed in Resolute PB and
organization does not use SBO - CORRECT ANSWER-ARPV_VISITS
BillingAccountFact - CORRECT ANSWER-One row per HAR, regardless of how it
is generated
,HSP_ACCOUNT - CORRECT ANSWER-One row per HAR, not including VFO
HARs
ARPV_VISITS - CORRECT ANSWER-One row per PB Visit HAR
EncounterFact - CORRECT ANSWER-One row per patient encounter
PAT_ENC - CORRECT ANSWER-One row per patient encounter
Linking registration data to guarantors and coverages - CORRECT ANSWER-
PAT_ENC only stores primary coverage, it is best use to identify the hospital
encounter for a patient encounter to find its registration data (one of the HSP
tables depending on how the encounter was billed).
BillingAccountEncounterMappingFact - CORRECT ANSWER-Links encounters
(EncounterFact) with HARs (BillingAccountFact)
[Clarity] Connect a HAR and its encounters - CORRECT ANSWER-Start from an
encounter and join to its HAR with PAT_ENC_4 or PAT_ENC_HSP. Also, you cab
use HSP_ACCT_PAT_CAN
, Internal IDs - CORRECT ANSWER-Guaranteed to be unique by Epic since
patients could have the same MRN (external IDs). ex: PAT_ID
Patient Identifiers - CORRECT ANSWER-Report consumers recognize MRN - but
to define a relationship in SQL we need to use/join with the internal IDs in Clarity
and durable keys in Caboodle. You can still display MRN, just do not join with
MRN.
Patient DVO - CORRECT ANSWER-PatientDim & Patient
Guarantor - CORRECT ANSWER-One patient can use different guarantor
accounts across encounters - a single HAR will only use one guarantor account
ACCT_GUAR_PAT_INFO - CORRECT ANSWER-Represented the general
relationships between guarantors and patients without indicating the specific
registration data for an encounter
ACCT_COVERAGE & PAT_ACCT_CVG - CORRECT ANSWER-Relationships
between guarantors, patients, and coverages at only a general level
