Slot: Address Period Alignment (address_period_alignment)
How the patient's location-over-time (the spatial axis of trajectory resolution) was modelled.
Tier: recommended
Why this slot matters
Assuming a single static address smears home-location exposure across days the patient was actually elsewhere; how location-over-time was modelled changes which days get which values and can bias exposure estimates.
In plain terms
People move house and travel, so "where the patient was" changes over time. This records whether the study used one fixed address, a full address history, or accounted for known trips away from home.
URI: envar:slot/address_period_alignment
Applicable Classes
| Name |
Description |
Modifies Slot |
| LinkageMethod |
How a gridded environmental value gets attached to a patient: the resolution ... |
no |
Properties
Type and Range
Cardinality and Requirements
Examples
| Value |
| address_history_from_emr |
Annotations
| property |
value |
| tier |
recommended |
| justification |
Assuming a single static address smears home-location exposure across days the patient was actually elsewhere; how location-over-time was modelled changes which days get which values and can bias exposure estimates. |
| explanation |
People move house and travel, so "where the patient was" changes over time. This records whether the study used one fixed address, a full address history, or accounted for known trips away from home. |
| covered_by |
None |
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
envar:address_period_alignment |
| native |
envar:address_period_alignment |
LinkML Source
name: address_period_alignment
annotations:
tier:
tag: tier
value: recommended
justification:
tag: justification
value: Assuming a single static address smears home-location exposure across days
the patient was actually elsewhere; how location-over-time was modelled changes
which days get which values and can bias exposure estimates.
explanation:
tag: explanation
value: People move house and travel, so "where the patient was" changes over time.
This records whether the study used one fixed address, a full address history,
or accounted for known trips away from home.
covered_by:
tag: covered_by
annotations:
omop_gaia:
tag: omop_gaia
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: GAIA/OMOP models a single static location per person and no address-history
/ location-over-time alignment.
degauss:
tag: degauss
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: DeGAUSS geocodes one address per row and models no location-over-
time period.
amadeus:
tag: amadeus
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: Amadeus takes fixed lat/lon and models no address period.
cher:
tag: cher
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: C-HER joins a participant point to a hex with no location-over-
time alignment.
codata:
tag: codata
annotations:
extent:
tag: extent
value: out_of_layer
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: How patient location-over-time is modelled is an instance-layer
linkage concern, outside CODATA's conceptual scope.
description: How the patient's location-over-time (the spatial axis of trajectory
resolution) was modelled.
title: Address Period Alignment
examples:
- value: address_history_from_emr
description: an EMR-sourced address history covers the observation period
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- LinkageMethod
range: AddressPeriodAlignmentEnum