Skip to content

Slot: Clinical Date Assignment Convention (clinical_date_assignment_convention)

The clinical-side mirror of day_boundary_convention (envar_temporal): which timezone / day-boundary rule collapsed the clinical timestamp to the date used in the join. A boundary mismatch between this and the exposure-side day_boundary_convention silently misattributes boundary-hour events to the wrong day, which is what makes the Core day_boundary_convention checkable at all. Metadata about the join — never the clinical timestamp itself; carries no PHI.

Tier: conditionally_core

Why this slot matters

If the clinical side collapsed timestamps to dates with a different day-boundary rule than the exposure side, events near midnight are silently joined to the wrong day's exposure; recording both rules is what makes that mismatch detectable at all.

In plain terms

A hospital visit at 11 pm can count as "today" or "tomorrow" depending on which clock and cutoff you use. This records the rule the clinical data used to turn a timestamp into a calendar date.

URI: envar:slot/clinical_date_assignment_convention

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 ClinicalDateAssignmentEnum
Domain Of LinkageMethod

Cardinality and Requirements

Property Value

Examples

Value
local_midnight
date_only_no_time

Identifier and Mapping Information

Annotations

property value
tier conditionally_core
justification If the clinical side collapsed timestamps to dates with a different day-boundary rule than the exposure side, events near midnight are silently joined to the wrong day's exposure; recording both rules is what makes that mismatch detectable at all.
explanation A hospital visit at 11 pm can count as "today" or "tomorrow" depending on which clock and cutoff you use. This records the rule the clinical data used to turn a timestamp into a calendar date.

Schema Source

Mappings

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

LinkML Source

name: clinical_date_assignment_convention
annotations:
  tier:
    tag: tier
    value: conditionally_core
  justification:
    tag: justification
    value: If the clinical side collapsed timestamps to dates with a different day-boundary
      rule than the exposure side, events near midnight are silently joined to the
      wrong day's exposure; recording both rules is what makes that mismatch detectable
      at all.
  explanation:
    tag: explanation
    value: A hospital visit at 11 pm can count as "today" or "tomorrow" depending
      on which clock and cutoff you use. This records the rule the clinical data used
      to turn a timestamp into a calendar date.
description: 'The clinical-side mirror of `day_boundary_convention` (envar_temporal):
  which timezone / day-boundary rule collapsed the clinical timestamp to the date
  used in the join. A boundary mismatch between this and the exposure-side `day_boundary_convention`
  silently misattributes boundary-hour events to the wrong day, which is what makes
  the Core `day_boundary_convention` checkable at all. Metadata *about the join* —
  never the clinical timestamp itself; carries no PHI.'
title: Clinical Date Assignment Convention
examples:
- value: local_midnight
  description: matches the exposure-side day_boundary_convention (Daymet tmax scenario)
- value: date_only_no_time
  description: clinical record carried only a date, so no boundary rule applies (ACAG
    PM2.5 scenario)
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- LinkageMethod
range: ClinicalDateAssignmentEnum