COG220 ACCESS DATA MODEL EXAM 2024 WITH 100%
CORRECT ANSWERS
With regard to the Access Data Model, What is a patient? - Answer- A person who receives the services
an organization provides.
What is "Welcome" as it pertains to Epic applications? - Answer- Allows patients to check themselves in
for an appointment. It is an application that focuses on self service kiosks or tablets a patient can use to
check in.
With regard to the Access Data Model, What is a payor - Answer- The insurance company to whom an
insurance claim will be sent.
Subscriber - Answer- The person under whose name the insurance is issued. Each insurance coverage has
only one.
Plan - Answer- The set of benefits that the insurance company offers.
Member - Answer- The person who is covered by insurance. Patients who will use the coverage. i.e.
children on the health insurance policy.
True of False: Most organizations are more concerned with the member effective dates on a coverage than
the coverage effective dates. - Answer- True: Most organizations are more concerned with the member
effective dates
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
CORRECT ANSWERS
With regard to the Access Data Model, What is a patient? - Answer- A person who receives the services
an organization provides.
What is "Welcome" as it pertains to Epic applications? - Answer- Allows patients to check themselves in
for an appointment. It is an application that focuses on self service kiosks or tablets a patient can use to
check in.
With regard to the Access Data Model, What is a payor - Answer- The insurance company to whom an
insurance claim will be sent.
Subscriber - Answer- The person under whose name the insurance is issued. Each insurance coverage has
only one.
Plan - Answer- The set of benefits that the insurance company offers.
Member - Answer- The person who is covered by insurance. Patients who will use the coverage. i.e.
children on the health insurance policy.
True of False: Most organizations are more concerned with the member effective dates on a coverage than
the coverage effective dates. - Answer- True: Most organizations are more concerned with the member
effective dates
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
