FHIR to OMOP FHIR IG
1.0.0-ballot - INFORMATIVE 1 - Ballot International flag

This page is part of the Vulcan FHIR to OMOP FHIR Implementation Guide (v1.0.0-ballot: INFORMATIVE 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Logical Model: FactRelationship - Detailed Descriptions

Page standards status: Informative Maturity Level: 1

Definitions for the FactRelationship logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. FactRelationship
Definition

The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: Person relationships (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen).


Base definition for all types defined in FHIR type system.

ShortFact Relationship OMOP TableBase for all types and resources
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. FactRelationship.domain-concept-id-1
Definition

Domain 1

ShortDomain 1
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. FactRelationship.fact-id-1
Definition

Fact Identifier 1

ShortFact Identifier 1
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. FactRelationship.domain-concept-id-2
Definition

Domain 2

ShortDomain 2
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. FactRelationship.fact-id-2
Definition

Fact Identifier 2

ShortFact Identifier 2
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. FactRelationship.relationship-concept-id
Definition

Relationship

ShortRelationship
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. FactRelationship
Definition

The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: Person relationships (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen).

ShortFact Relationship OMOP Table
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. FactRelationship.domain-concept-id-1
Definition

Domain 1

ShortDomain 1
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. FactRelationship.fact-id-1
Definition

Fact Identifier 1

ShortFact Identifier 1
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. FactRelationship.domain-concept-id-2
Definition

Domain 2

ShortDomain 2
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. FactRelationship.fact-id-2
Definition

Fact Identifier 2

ShortFact Identifier 2
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. FactRelationship.relationship-concept-id
Definition

Relationship

ShortRelationship
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. FactRelationship
Definition

The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: Person relationships (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen).

ShortFact Relationship OMOP Table
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. FactRelationship.domain-concept-id-1
Definition

Domain 1

ShortDomain 1
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. FactRelationship.fact-id-1
Definition

Fact Identifier 1

ShortFact Identifier 1
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. FactRelationship.domain-concept-id-2
Definition

Domain 2

ShortDomain 2
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. FactRelationship.fact-id-2
Definition

Fact Identifier 2

ShortFact Identifier 2
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. FactRelationship.relationship-concept-id
Definition

Relationship

ShortRelationship
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension