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: Fact Relationship OMOP Table

Official URL: http://hl7.org/fhir/uv/omop/StructureDefinition/FactRelationship Version: 1.0.0-ballot
Standards status: Informative Maturity Level: 1 Computable Name: FactRelationship

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).

Usages:

  • This Logical Model is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(5 nested mandatory elements)

Maturity: 1

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. FactRelationship 0..* Base Fact Relationship OMOP Table
Instances of this logical model can be the target of a Reference
... domain_concept_id_1 1..1 code Domain 1
... fact_id_1 1..1 string Fact Identifier 1
... domain_concept_id_2 1..1 code Domain 2
... relationship_concept_id 1..1 code Relationship

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(5 nested mandatory elements)

Maturity: 1

 

Other representations of profile: CSV, Excel