2. Input Layer
Here we document the Input Layer. The Input Layer is like the API for the Tuva Project. Once raw data sources (e.g. claims and medical records) are mapped to the Input Layer the rest of the Tuva Project runs automatically (i.e. core data model and all the data marts).
The Input Layer is designed to accomodate both claims and clinical data sources.
Click on any row in the data dictionaries below to expand the table and reveal additional context useful for mapping data to that column.
Claims Input
eligibility
The eligibility table includes information about a patient's health insurance coverage and demographics (note: we use the word patient as a synonym for member). Every claims dataset should include some sort of eligibility data, otherwise it's impossible to calculate member months, which are needed to calculate measures like PMPM. Each record in the table is intended to represent a unique eligibility (i.e. enrollment) span for a patient with a specific health plan.
Primary Key:
- person_id
- member_id
- enrollment_start_date
- enrollment_end_date
- payer
- plan
- data_source
| Column Name | Data Type | Description |
|---|---|---|
medical_claim
The medical_claim table contains information on healthcare services and supplies provided to patients, billed by providers, and paid for by health insurers. It includes information on the provider who rendered the service, the amount paid for the service by the health insurer, and the underlying reason for the service (i.e. diagnosis). Each record in the table is intended to represent a unique claim line.
Primary Key:
- claim_id
- claim_line_number
- data_source
Foreign Keys:
- person_id
- member_id
| Column Name | Data Type | Description |
|---|---|---|
pharmacy_claim
The pharmacy_claim table includes information about retail and specialty drug prescriptions that have been filled by a patient, billed by a pharmacy, and paid by an insurer. Each record in the table is intended to represent a unique claim line.
Primary Key:
- claim_id
- claim_line_number
- data_source
Foreign Keys:
- person_id
- member_id
| Column Name | Data Type | Description |
|---|---|---|
provider_attribution
To use the provider_attribution table, you must set the dbt variable provider_attribution_enabled to true.
The provider_attribution table assigns a provider to each patient-member_month of eligibility. The user may assign both a payer-attributed provider (as typically assigned by the payer in VBC contracts) as well as custom-attributed provider (typically determined by the user). Fields related to each attributed provider (practice, organization, line of business) are also present. Each record in the table is intended to represent a unique provider attribution for a patient in a specific month with a specific health plan.
Primary Key:
- person_id
- payer
- plan
- year_month
- data_source
Foreign Keys:
- person_id
- patient_id
| Column Name | Data Type | Description |
|---|
Clinical Input
appointment
| Column Name | Data Type | Description |
|---|
condition
| Column Name | Data Type | Description |
|---|
encounter
| Column Name | Data Type | Description |
|---|
lab_result
| Column Name | Data Type | Description |
|---|
immunization
| Column Name | Data Type | Description |
|---|
location
| Column Name | Data Type | Description |
|---|
medication
| Column Name | Data Type | Description |
|---|
observation
| Column Name | Data Type | Description |
|---|
patient
| Column Name | Data Type | Description |
|---|
practitioner
| Column Name | Data Type | Description |
|---|
procedure
| Column Name | Data Type | Description |
|---|