Skip to content

Slot: Lag Alignment Applied (lag_alignment_applied)

Whether and how values were lag-aligned to a clinical event. Relocated from envar_temporal: lag alignment attaches a value to an event (a linkage concern), not an intrinsic temporal property. See lag_alignment_specifier for the concrete lag value(s).

Tier: recommended

Why this slot matters

If values were already shifted relative to the clinical event and this is not recorded, an analyst may apply the lag again — double-lagging is a silent analytic error that misdates every exposure.

In plain terms

Health effects can trail exposure by days — a heat wave today may send someone to hospital next week — so analyses sometimes pair a clinical event with earlier exposure values. This records whether such a shift was already built into the data.

URI: envar:slot/lag_alignment_applied

Applicable Classes

Name Description Modifies Slot
LinkageMethod How a gridded environmental value gets attached to a patient: the resolution ... no

Properties

Type and Range

Property Value
Range LagAlignmentEnum
Domain Of LinkageMethod

Cardinality and Requirements

Property Value

Examples

Value
none

See Also

Identifier and Mapping Information

Annotations

property value
tier recommended
justification If values were already shifted relative to the clinical event and this is not recorded, an analyst may apply the lag again — double-lagging is a silent analytic error that misdates every exposure.
explanation Health effects can trail exposure by days — a heat wave today may send someone to hospital next week — so analyses sometimes pair a clinical event with earlier exposure values. This records whether such a shift was already built into the data.
covered_by None

Schema Source

Mappings

Mapping Type Mapped Value
self envar:lag_alignment_applied
native envar:lag_alignment_applied

LinkML Source

name: lag_alignment_applied
annotations:
  tier:
    tag: tier
    value: recommended
  justification:
    tag: justification
    value: If values were already shifted relative to the clinical event and this
      is not recorded, an analyst may apply the lag again — double-lagging is a silent
      analytic error that misdates every exposure.
  explanation:
    tag: explanation
    value: Health effects can trail exposure by days — a heat wave today may send
      someone to hospital next week — so analyses sometimes pair a clinical event
      with earlier exposure values. This records whether such a shift was already
      built into the data.
  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 emits values at native dates with no lag-alignment record.
      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 emits per-day values at native dates with no lag-alignment
              record.
      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 emits per-day values at native dates with no lag-alignment
              record.
      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 is spatial-only and carries no lag-alignment record.
      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: Lag alignment to a clinical event is an instance-layer linkage
              concern, outside CODATA's conceptual scope.
description: 'Whether and how values were lag-aligned to a clinical event. Relocated
  from envar_temporal: lag alignment attaches a value to an event (a linkage concern),
  not an intrinsic temporal property. See `lag_alignment_specifier` for the concrete
  lag value(s).'
title: Lag Alignment Applied
examples:
- value: none
  description: values are at native dates; no lag alignment applied
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://cran.r-project.org/package=dlnm
rank: 1000
domain_of:
- LinkageMethod
range: LagAlignmentEnum