1|Page
COG220 ACCESS DATA MODEL EXAM 2025 NEWEST
ACTUAL EXAM COMPLETE ACCURATE EXAM
QUESTIONS WITH DETAILED VERIFIED ANSWERS
(100% CORRECT ANSWERS) /ALREADY GRADED A+/
LATEST VERSION!!!
Registration - Answer-Focuses on the patient, guarantor,
and coverage(s) used on an encounter
HAR - Answer-Consolidates registration information active
for an encounter (patient, guarantor, coverage(s)).
Registration information for an encounter that is billed in
Resolute HB - Answer-HSP_ACCOUNT
Registration information for an encounter that id billed in
Resolute PB and uses SBO - Answer-HSP_ACCOUNT
Registration information for an encounter that is billed in
Resolute PB and organization does not use SBO -
Answer-ARPV_VISITS
,2|Page
BillingAccountFact - Answer-One row per HAR, regardless
of how it is generated
HSP_ACCOUNT - Answer-One row per HAR, not
including VFO HARs
ARPV_VISITS - Answer-One row per PB Visit HAR
EncounterFact - Answer-One row per patient encounter
PAT_ENC - Answer-One row per patient encounter
Linking registration data to guarantors and coverages -
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 - Answer-Links
encounters (EncounterFact) with HARs
(BillingAccountFact)
,3|Page
[Clarity] Connect a HAR and its encounters - 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 - Answer-Guaranteed to be unique by Epic
since patients could have the same MRN (external IDs).
ex: PAT_ID
Patient Identifiers - 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 - Answer-PatientDim & Patient
Guarantor - Answer-One patient can use different
guarantor accounts across encounters - a single HAR will
only use one guarantor account
ACCT_GUAR_PAT_INFO - Answer-Represented the
general relationships between guarantors and patients
, 4|Page
without indicating the specific registration data for an
encounter
ACCT_COVERAGE & PAT_ACCT_CVG - Answer-
Relationships between guarantors, patients, and
coverages at only a general level
Verification Database Objects - Answer-VERIFICATION -
One row per VRX record
(Record-level details)
VERIF_STATUS_HX - One row per change to a VRX
record's status
(Use this if you need to know the Verification status of a
record at some point)
RHX - Registration History Event - Answer-When
registration data was collected or changed, and who
completed those changes. Each change is documented as
a RHX
T or F: A patient's MRN is guaranteed to be unique across
all patients on the same instance of Epic - Answer-False
COG220 ACCESS DATA MODEL EXAM 2025 NEWEST
ACTUAL EXAM COMPLETE ACCURATE EXAM
QUESTIONS WITH DETAILED VERIFIED ANSWERS
(100% CORRECT ANSWERS) /ALREADY GRADED A+/
LATEST VERSION!!!
Registration - Answer-Focuses on the patient, guarantor,
and coverage(s) used on an encounter
HAR - Answer-Consolidates registration information active
for an encounter (patient, guarantor, coverage(s)).
Registration information for an encounter that is billed in
Resolute HB - Answer-HSP_ACCOUNT
Registration information for an encounter that id billed in
Resolute PB and uses SBO - Answer-HSP_ACCOUNT
Registration information for an encounter that is billed in
Resolute PB and organization does not use SBO -
Answer-ARPV_VISITS
,2|Page
BillingAccountFact - Answer-One row per HAR, regardless
of how it is generated
HSP_ACCOUNT - Answer-One row per HAR, not
including VFO HARs
ARPV_VISITS - Answer-One row per PB Visit HAR
EncounterFact - Answer-One row per patient encounter
PAT_ENC - Answer-One row per patient encounter
Linking registration data to guarantors and coverages -
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 - Answer-Links
encounters (EncounterFact) with HARs
(BillingAccountFact)
,3|Page
[Clarity] Connect a HAR and its encounters - 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 - Answer-Guaranteed to be unique by Epic
since patients could have the same MRN (external IDs).
ex: PAT_ID
Patient Identifiers - 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 - Answer-PatientDim & Patient
Guarantor - Answer-One patient can use different
guarantor accounts across encounters - a single HAR will
only use one guarantor account
ACCT_GUAR_PAT_INFO - Answer-Represented the
general relationships between guarantors and patients
, 4|Page
without indicating the specific registration data for an
encounter
ACCT_COVERAGE & PAT_ACCT_CVG - Answer-
Relationships between guarantors, patients, and
coverages at only a general level
Verification Database Objects - Answer-VERIFICATION -
One row per VRX record
(Record-level details)
VERIF_STATUS_HX - One row per change to a VRX
record's status
(Use this if you need to know the Verification status of a
record at some point)
RHX - Registration History Event - Answer-When
registration data was collected or changed, and who
completed those changes. Each change is documented as
a RHX
T or F: A patient's MRN is guaranteed to be unique across
all patients on the same instance of Epic - Answer-False
