COG220 ACCESS DATA MODEL EXAM 2024 NEWEST
ACTUAL EXAM COMPLETE ACCURATE EXAM
QUESTIONS WITH DETAILED VERIFIED ANSWERS
(100% CORRECT ANSWERS) /ALREADY GRADED A+
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
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)
[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 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
A given coverage record represents the unique combination of which of the following? -
ANSWER Payer, Plan, Subscriber
Which of the following join conditions would connect each hospital account to its
guarantor's current information and exclude historical information? - 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? - ANSWER
0 or any number of encounters (different than one guarantor account to one HAR)
What does VERIFICATION.VERIF_STATUS_C represent? - 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? - ANSWER The
ACTUAL EXAM COMPLETE ACCURATE EXAM
QUESTIONS WITH DETAILED VERIFIED ANSWERS
(100% CORRECT ANSWERS) /ALREADY GRADED A+
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
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)
[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 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
A given coverage record represents the unique combination of which of the following? -
ANSWER Payer, Plan, Subscriber
Which of the following join conditions would connect each hospital account to its
guarantor's current information and exclude historical information? - 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? - ANSWER
0 or any number of encounters (different than one guarantor account to one HAR)
What does VERIFICATION.VERIF_STATUS_C represent? - 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? - ANSWER The
