COG220 ACCESS DATA MODEL EXM QUESTION BANK NEWEST
2025 ACTUAL EXAM WITH COMPLETE 500 QUESTIONS AND
CORRECT DETAILED ANSWERS (VERIFIED ANSWERS) ALREADY
GRADED A+ | GUARANTEED PASS
The moment when the patient first entered an inpatient bed with an inpatient
reporting base class
all you need is I ADT 84
Registration
Focuses on the patient, guarantor, and coverage(s) used on an encounter
HAR
Consolidates registration information active for an encounter (patient,
guarantor, coverage(s)).
Registration information for an encounter that is billed in Resolute HB
HSP_ACCOUNT
,Registration information for an encounter that id billed in Resolute PB and uses
SBO
HSP_ACCOUNT
Registration information for an encounter that is billed in Resolute PB and
organization does not use SBO
ARPV_VISITS
BillingAccountFact
One row per HAR, regardless of how it is generated
HSP_ACCOUNT
One row per HAR, not including VFO HARs
ARPV_VISITS
One row per PB Visit HAR
,EncounterFact
One row per patient encounter
PAT_ENC
One row per patient encounter
Linking registration data to guarantors and coverages
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
Links encounters (EncounterFact) with HARs (BillingAccountFact)
[Clarity] Connect a HAR and its encounters
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
Guaranteed to be unique by Epic since patients could have the same MRN
(external IDs). ex: PAT_ID
Patient Identifiers
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
PatientDim & Patient
Guarantor
One patient can use different guarantor accounts across encounters - a single
HAR will only use one guarantor account
ACCT_GUAR_PAT_INFO
Represented the general relationships between guarantors and patients without
indicating the specific registration data for an encounter
2025 ACTUAL EXAM WITH COMPLETE 500 QUESTIONS AND
CORRECT DETAILED ANSWERS (VERIFIED ANSWERS) ALREADY
GRADED A+ | GUARANTEED PASS
The moment when the patient first entered an inpatient bed with an inpatient
reporting base class
all you need is I ADT 84
Registration
Focuses on the patient, guarantor, and coverage(s) used on an encounter
HAR
Consolidates registration information active for an encounter (patient,
guarantor, coverage(s)).
Registration information for an encounter that is billed in Resolute HB
HSP_ACCOUNT
,Registration information for an encounter that id billed in Resolute PB and uses
SBO
HSP_ACCOUNT
Registration information for an encounter that is billed in Resolute PB and
organization does not use SBO
ARPV_VISITS
BillingAccountFact
One row per HAR, regardless of how it is generated
HSP_ACCOUNT
One row per HAR, not including VFO HARs
ARPV_VISITS
One row per PB Visit HAR
,EncounterFact
One row per patient encounter
PAT_ENC
One row per patient encounter
Linking registration data to guarantors and coverages
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
Links encounters (EncounterFact) with HARs (BillingAccountFact)
[Clarity] Connect a HAR and its encounters
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
Guaranteed to be unique by Epic since patients could have the same MRN
(external IDs). ex: PAT_ID
Patient Identifiers
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
PatientDim & Patient
Guarantor
One patient can use different guarantor accounts across encounters - a single
HAR will only use one guarantor account
ACCT_GUAR_PAT_INFO
Represented the general relationships between guarantors and patients without
indicating the specific registration data for an encounter
