Skip to content

Slot: Target Health-Data Layer (health_layer_target)

The downstream health-data layer this sidecar links into. Names the target so health_layer_link_field is interpreted against the right model.

Tier: recommended

Why this slot matters

Without naming the target layer, health_layer_link_field is ambiguous — a consumer cannot know which data model the link field belongs to, so the exposure record cannot be reliably resolved from the health side. Naming the target in a slot (rather than baking it into slot names) is also what keeps the schema neutral across health data models.

In plain terms

Health records are stored in different standard formats — for example OMOP, a widely used common format for health records, so tools written for one hospital's data work on another's. This slot simply says which of those formats this exposure record is meant to plug into.

URI: envar:slot/health_layer_target

Applicable Classes

Name Description Modifies Slot
HealthLayerLinkage Hooks the sidecar uses to be findable from a downstream health-data layer (OM... no

Properties

Type and Range

Property Value
Range HealthLayerTargetEnum
Domain Of HealthLayerLinkage

Cardinality and Requirements

Property Value

Examples

Value
omop_external_exposure

See Also

Identifier and Mapping Information

Annotations

property value
tier recommended
justification Without naming the target layer, health_layer_link_field is ambiguous — a consumer cannot know which data model the link field belongs to, so the exposure record cannot be reliably resolved from the health side. Naming the target in a slot (rather than baking it into slot names) is also what keeps the schema neutral across health data models.
explanation Health records are stored in different standard formats — for example OMOP, a widely used common format for health records, so tools written for one hospital's data work on another's. This slot simply says which of those formats this exposure record is meant to plug into.
covered_by None

Schema Source

Mappings

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

LinkML Source

name: health_layer_target
annotations:
  tier:
    tag: tier
    value: recommended
  justification:
    tag: justification
    value: Without naming the target layer, `health_layer_link_field` is ambiguous
      — a consumer cannot know which data model the link field belongs to, so the
      exposure record cannot be reliably resolved from the health side. Naming the
      target in a slot (rather than baking it into slot names) is also what keeps
      the schema neutral across health data models.
  explanation:
    tag: explanation
    value: Health records are stored in different standard formats — for example OMOP,
      a widely used common format for health records, so tools written for one hospital's
      data work on another's. This slot simply says which of those formats this exposure
      record is meant to plug into.
  covered_by:
    tag: covered_by
    annotations:
      omop_gaia:
        tag: omop_gaia
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: external_exposure table (OMOP CDM GIS extension) — the target is
              OMOP but is implicit, not a named slot
          note:
            tag: note
            value: 'Gaia lands values into OMOP external_exposure, so the target layer
              is effectively OMOP, but it is baked into the pipeline rather than declared
              in a target field. Conservative: partial.'
      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 appends columns to the cohort CSV and names no downstream
              health-layer target.
      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 names no downstream health-layer target.
      cher:
        tag: cher
        annotations:
          extent:
            tag: extent
            value: partial
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: PostgreSQL schema=health (health-resource bucket)
          note:
            tag: note
            value: 'C-HER has a health schema for health resources, but does not name
              a downstream health-data model as an exposure-record target. Conservative:
              partial.'
      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: Health-layer target naming is instance/integration-layer; out of
              scope for CODATA.
description: The downstream health-data layer this sidecar links into. Names the target
  so `health_layer_link_field` is interpreted against the right model.
title: Target Health-Data Layer
examples:
- value: omop_external_exposure
  description: OMOP CDM via the OHDSI GIS `external_exposure` table extension
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://ohdsi.github.io/CommonDataModel/
rank: 1000
domain_of:
- HealthLayerLinkage
range: HealthLayerTargetEnum