OMOPDeviceExposure
type: StructureDefinition
node role: treeRoot
id:
  v: OMOPDeviceExposure
text:
  status:
    v: extensions
  div: Narratif généré : DéfinitionStructure OMOPDeviceExposure Nom Drapeaux Card. Type Description et contraintes<img src="[binary]" alt="doco" style="background-color: inherit"/> <a href="StructureDefinition-OMOPDeviceExposure-definitions.html#OMOPDeviceExposure" title="The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).">OMOPDeviceExposure 0..* Base Device Exposure OMOP Table Instances of this logical model can be the target of a Reference #xD; device_exposure_id 1..1 integer Device Exposure Identifier #xD; person_id 1..1 Reference(Person OMOP Table) Person #xD; device_concept_id 1..1 Reference(Concept OMOP Table) Device #xD; device_exposure_start_date 1..1 date Device Exposure Start Date #xD; device_exposure_start_datetime 0..1 dateTime Device Exposure Start Datetime #xD; device_exposure_end_date 0..1 date Device Exposure End Date #xD; device_exposure_end_datetime 0..1 dateTime Device Exposure End Datetime #xD; device_type_concept_id 1..1 integer Device Type Concept Identifier #xD; unique_device_id 0..1 string Unique Device Identifier #xD; production_id 0..1 integer Production Identifier #xD; quantity 0..1 integer Quantity #xD; provider_id 0..1 Reference(Provider OMOP Table) Provider #xD; visit_occurrence_id 0..1 Reference(Visit Occurrence OMOP Table) Visit Occurence Identifier #xD; visit_detail_id 0..1 Reference(Visit Detail OMOP Table) Visit Detail Identifier #xD; device_source_value 0..1 string Device Source Value #xD; <a href="StructureDefinition-OMOPDeviceExposure-definitions.html#OMOPDev…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-type-characteristics
  value: code
    v: can-be-target
url:
  v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPDeviceExposure
version:
  v: 0.1.0
name:
  v: OMOPDeviceExposure
title:
  v: Device Exposure OMOP Table
status:
  v: draft
date:
  v: 2025-10-23T20:49:03+00:00
publisher:
  v: AP-HP
contact:
  name:
    v: AP-HP
  telecom:
    system:
      v: url
    value:
      v: https://aphp.fr
description:
  v: The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
jurisdiction:
  coding:
    system:
      v: urn:iso:std:iso:3166
    code:
      v: FR
    display:
      v: France
fhir version:
  v: 4.0.1
kind:
  v: logical
abstract:
  v: false
type:
  v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPDeviceExposure
base definition:
  v: http://hl7.org/fhir/StructureDefinition/Base
  link: http://hl7.org/fhir/StructureDefinition/Base
derivation:
  v: specialization
snapshot:
  extension:
    url:
      v: http://hl7.org/fhir/tools/StructureDefinition/snapshot-base-version
    value: string
      v: 4.0.1
  element:
    id:
      v: OMOPDeviceExposure
    path:
      v: OMOPDeviceExposure
    short:
      v: Device Exposure OMOP Table
    definition:
      v: The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
    min:
      v: 0
    max:
      v: *
    base:
      path:
        v: Base
      min:
        v: 0
      max:
        v: *
    is modifier:
      v: false
  element:
    id:
      v: OMOPDeviceExposure.device-exposure-id
    path:
      v: OMOPDeviceExposure.device_exposure_id
    short:
      v: Device Exposure Identifier
    definition:
      v: Device Exposure Identifier
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: OMOPDeviceExposure.device_exposure_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: integer
  element:
    id:
      v: OMOPDeviceExposure.person-id
    path:
      v: OMOPDeviceExposure.person_id
    short:
      v: Person
    definition:
      v: The PERSON_ID of the PERSON for whom the condition is recorded.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: OMOPDeviceExposure.person_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: Reference
      target profile:
        v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPPerson
        link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPPerson
  element:
    id:
      v: OMOPDeviceExposure.device-concept-id
    path:
      v: OMOPDeviceExposure.device_concept_id
    short:
      v: Device
    definition:
      v: The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: OMOPDeviceExposure.device_concept_id
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: Reference
      target profile:
        v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
        link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
  element:
    id:
      v: OMOPDeviceExposure.device-exposure-start-date
    path:
      v: OMOPDeviceExposure.device_exposure_start_date
    short:
      v: Device Exposure Start Date
    definition:
      v: Use this date to determine the start date of the device record.
    min:
      v: 1
    max:
      v: 1
    base:
      path:
        v: OMOPDeviceExposure.device_exposure_start_date
      min:
        v: 1
      max:
        v: 1
    type:
      code:
        v: date
  element:
    id:
      v: OMOPDeviceExposure.device-exposure-start-datetime
    path:
      v: OMOPDeviceExposure.device_exposure_start_datetime
    short:
      v: Device Exposure Start Datetime
    definition:
      v: Device Exposure Start Datetime
    min:
      v: 0
    max:
      v: 1
    base:
      path:
        v: OMOPDeviceExposure.device_exposure_start_datetime
      min:
        v: 0
      max:
        v: 1

code:
  v: dateTime

id:
  v: OMOPDeviceExposure.device-exposure-end-date
path:
  v: OMOPDeviceExposure.device_exposure_end_date
short:
  v: Device Exposure End Date
definition:
  v: The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.device_exposure_end_date
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: date

id:
  v: OMOPDeviceExposure.device-exposure-end-datetime
path:
  v: OMOPDeviceExposure.device_exposure_end_datetime
short:
  v: Device Exposure End Datetime
definition:
  v: Device Exposure End Datetime
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.device_exposure_end_datetime
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: dateTime

id:
  v: OMOPDeviceExposure.device-type-concept-id
path:
  v: OMOPDeviceExposure.device_type_concept_id
short:
  v: Device Type Concept Identifier
definition:
  v: You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
min:
  v: 1
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.device_type_concept_id
  min:
    v: 1
  max:
    v: 1
type:
  code:
    v: integer

id:
  v: OMOPDeviceExposure.unique-device-id
path:
  v: OMOPDeviceExposure.unique_device_id
short:
  v: Unique Device Identifier
definition:
  v: This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.unique_device_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string

id:
  v: OMOPDeviceExposure.production-id
path:
  v: OMOPDeviceExposure.production_id
short:
  v: Production Identifier
definition:
  v: This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.production_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer

id:
  v: OMOPDeviceExposure.quantity
path:
  v: OMOPDeviceExposure.quantity
short:
  v: Quantity
definition:
  v: Quantity
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.quantity
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: integer

id:
  v: OMOPDeviceExposure.provider-id
path:
  v: OMOPDeviceExposure.provider_id
short:
  v: Provider
definition:
  v: The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.provider_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPProvider
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPProvider

id:
  v: OMOPDeviceExposure.visit-occurrence-id
path:
  v: OMOPDeviceExposure.visit_occurrence_id
short:
  v: Visit Occurence Identifier
definition:
  v: The Visit during which the device was prescribed or given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.visit_occurrence_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitOccurrence
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitOccurrence

id:
  v: OMOPDeviceExposure.visit-detail-id
path:
  v: OMOPDeviceExposure.visit_detail_id
short:
  v: Visit Detail Identifier
definition:
  v: The Visit Detail during which the device was prescribed or given.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.visit_detail_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitDetail
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitDetail

id:
  v: OMOPDeviceExposure.device-source-value
path:
  v: OMOPDeviceExposure.device_source_value
short:
  v: Device Source Value
definition:
  v: This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.device_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string

id:
  v: OMOPDeviceExposure.device-source-concept-id
path:
  v: OMOPDeviceExposure.device_source_concept_id
short:
  v: Device Source
definition:
  v: This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.device_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept

id:
  v: OMOPDeviceExposure.unit-concept-id
path:
  v: OMOPDeviceExposure.unit_concept_id
short:
  v: Unit
definition:
  v: UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.unit_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept

id:
  v: OMOPDeviceExposure.unit-source-value
path:
  v: OMOPDeviceExposure.unit_source_value
short:
  v: Unit Source Value
definition:
  v: This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.unit_source_value
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: string

id:
  v: OMOPDeviceExposure.unit-source-concept-id
path:
  v: OMOPDeviceExposure.unit_source_concept_id
short:
  v: Unit Source
definition:
  v: This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
base:
  path:
    v: OMOPDeviceExposure.unit_source_concept_id
  min:
    v: 0
  max:
    v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept

element:
  id:
    v: OMOPDeviceExposure
  path:
    v: OMOPDeviceExposure
  short:
    v: Device Exposure OMOP Table
  definition:
    v: The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).).
element:
  id:
    v: OMOPDeviceExposure.device-exposure-id
  path:
    v: OMOPDeviceExposure.device_exposure_id
  short:
    v: Device Exposure Identifier
  definition:
    v: Device Exposure Identifier
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: integer
element:
  id:
    v: OMOPDeviceExposure.person-id
  path:
    v: OMOPDeviceExposure.person_id
  short:
    v: Person
  definition:
    v: The PERSON_ID of the PERSON for whom the condition is recorded.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: Reference
    target profile:
      v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPPerson
      link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPPerson
element:
  id:
    v: OMOPDeviceExposure.device-concept-id
  path:
    v: OMOPDeviceExposure.device_concept_id
  short:
    v: Device
  definition:
    v: The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: Reference
    target profile:
      v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
      link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
element:
  id:
    v: OMOPDeviceExposure.device-exposure-start-date
  path:
    v: OMOPDeviceExposure.device_exposure_start_date
  short:
    v: Device Exposure Start Date
  definition:
    v: Use this date to determine the start date of the device record.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: date
element:
  id:
    v: OMOPDeviceExposure.device-exposure-start-datetime
  path:
    v: OMOPDeviceExposure.device_exposure_start_datetime
  short:
    v: Device Exposure Start Datetime
  definition:
    v: Device Exposure Start Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
element:
  id:
    v: OMOPDeviceExposure.device-exposure-end-date
  path:
    v: OMOPDeviceExposure.device_exposure_end_date
  short:
    v: Device Exposure End Date
  definition:
    v: The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: date
element:
  id:
    v: OMOPDeviceExposure.device-exposure-end-datetime
  path:
    v: OMOPDeviceExposure.device_exposure_end_datetime
  short:
    v: Device Exposure End Datetime
  definition:
    v: Device Exposure End Datetime
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: dateTime
element:
  id:
    v: OMOPDeviceExposure.device-type-concept-id
  path:
    v: OMOPDeviceExposure.device_type_concept_id
  short:
    v: Device Type Concept Identifier
  definition:
    v: You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
  min:
    v: 1
  max:
    v: 1
  type:
    code:
      v: integer
element:
  id:
    v: OMOPDeviceExposure.unique-device-id
  path:
    v: OMOPDeviceExposure.unique_device_id
  short:
    v: Unique Device Identifier
  definition:
    v: This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: string
element:
  id:
    v: OMOPDeviceExposure.production-id
  path:
    v: OMOPDeviceExposure.production_id
  short:
    v: Production Identifier
  definition:
    v: This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: integer
element:
  id:
    v: OMOPDeviceExposure.quantity
  path:
    v: OMOPDeviceExposure.quantity
  short:
    v: Quantity
  definition:
    v: Quantity
  min:
    v: 0
  max:
    v: 1
  type:
    code:
      v: integer
element:
  id:
    v: OMOPDeviceExposure.provider-id
  path:
    v: OMOPDeviceExposure.provider_id
  short:
    v: Provider
  definition:
    v: The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
  min:
    v: 0

v: 1

code:
  v: Reference
target profile:
  v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPProvider
  link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPProvider

id:
  v: OMOPDeviceExposure.visit-occurrence-id
path:
  v: OMOPDeviceExposure.visit_occurrence_id
short:
  v: Visit Occurence Identifier
definition:
  v: The Visit during which the device was prescribed or given.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitOccurrence
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitOccurrence

id:
  v: OMOPDeviceExposure.visit-detail-id
path:
  v: OMOPDeviceExposure.visit_detail_id
short:
  v: Visit Detail Identifier
definition:
  v: The Visit Detail during which the device was prescribed or given.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitDetail
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPVisitDetail

id:
  v: OMOPDeviceExposure.device-source-value
path:
  v: OMOPDeviceExposure.device_source_value
short:
  v: Device Source Value
definition:
  v: This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string

id:
  v: OMOPDeviceExposure.device-source-concept-id
path:
  v: OMOPDeviceExposure.device_source_concept_id
short:
  v: Device Source
definition:
  v: This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept

id:
  v: OMOPDeviceExposure.unit-concept-id
path:
  v: OMOPDeviceExposure.unit_concept_id
short:
  v: Unit
definition:
  v: UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept

id:
  v: OMOPDeviceExposure.unit-source-value
path:
  v: OMOPDeviceExposure.unit_source_value
short:
  v: Unit Source Value
definition:
  v: This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: string

id:
  v: OMOPDeviceExposure.unit-source-concept-id
path:
  v: OMOPDeviceExposure.unit_source_concept_id
short:
  v: Unit Source
definition:
  v: This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
min:
  v: 0
max:
  v: 1
type:
  code:
    v: Reference
  target profile:
    v: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept
    link: https://interop.aphp.fr/ig/fhir/dm/StructureDefinition/OMOPConcept