FHIR to OMOP FHIR IG
1.0.0 - INFORMATIVE 1 International flag

This page is part of the Vulcan FHIR to OMOP FHIR Implementation Guide (v1.0.0: INFORMATIVE 1 - Informative) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Logical Model: Note OMOP Table

Official URL: http://hl7.org/fhir/uv/omop/StructureDefinition/Note Version: 1.0.0
Standards status: Informative Maturity Level: 2 Computable Name: Note

The NOTE table captures unstructured information that was recorded by a provider about a patient in free text (in ASCII, or preferably in UTF8 format) notes on a given date. The type of note_text is CLOB or varchar(MAX) depending on RDBMS.

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 Differentials, Snapshots, and other representations.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Note 0..* Base Note OMOP Table
Instances of this logical model can be the target of a Reference
... note_id 1..1 code Note Identifier
... person_id 1..1 integer Person
... note_date 1..1 date Note Date
... note_type_concept_id 1..1 code Note Type
... note_class_concept_id 1..1 code Note Class
... note_title 0..1 string Title
... note_text 1..1 string Text
... encoding_concept_id 1..1 code Encoding
... language_concept_id 1..1 code Language
... provider_id 0..1 integer Provider
... visit_occurrence_id 0..1 integer Visit Occurence
... visit_detail_id 0..1 integer Visit Detail
... note_source_value 0..1 string Note Source Value
... note_event_id 0..1 integer Note Event
... note_event_field_concept_id 0..1 code Note Event Field

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Note 0..* Base Note OMOP Table
Instances of this logical model can be the target of a Reference
... note_id 1..1 code Note Identifier
... person_id 1..1 integer Person
... note_date 1..1 date Note Date
... note_type_concept_id 1..1 code Note Type
... note_class_concept_id 1..1 code Note Class
... note_title 0..1 string Title
... note_text 1..1 string Text
... encoding_concept_id 1..1 code Encoding
... language_concept_id 1..1 code Language
... provider_id 0..1 integer Provider
... visit_occurrence_id 0..1 integer Visit Occurence
... visit_detail_id 0..1 integer Visit Detail
... note_source_value 0..1 string Note Source Value
... note_event_id 0..1 integer Note Event
... note_event_field_concept_id 0..1 code Note Event Field

doco Documentation for this format

Summary

Mandatory: 0 element(8 nested mandatory elements)

Maturity: 2

Differential View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Note 0..* Base Note OMOP Table
Instances of this logical model can be the target of a Reference
... note_id 1..1 code Note Identifier
... person_id 1..1 integer Person
... note_date 1..1 date Note Date
... note_type_concept_id 1..1 code Note Type
... note_class_concept_id 1..1 code Note Class
... note_title 0..1 string Title
... note_text 1..1 string Text
... encoding_concept_id 1..1 code Encoding
... language_concept_id 1..1 code Language
... provider_id 0..1 integer Provider
... visit_occurrence_id 0..1 integer Visit Occurence
... visit_detail_id 0..1 integer Visit Detail
... note_source_value 0..1 string Note Source Value
... note_event_id 0..1 integer Note Event
... note_event_field_concept_id 0..1 code Note Event Field

doco Documentation for this format

Snapshot ViewView

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Note 0..* Base Note OMOP Table
Instances of this logical model can be the target of a Reference
... note_id 1..1 code Note Identifier
... person_id 1..1 integer Person
... note_date 1..1 date Note Date
... note_type_concept_id 1..1 code Note Type
... note_class_concept_id 1..1 code Note Class
... note_title 0..1 string Title
... note_text 1..1 string Text
... encoding_concept_id 1..1 code Encoding
... language_concept_id 1..1 code Language
... provider_id 0..1 integer Provider
... visit_occurrence_id 0..1 integer Visit Occurence
... visit_detail_id 0..1 integer Visit Detail
... note_source_value 0..1 string Note Source Value
... note_event_id 0..1 integer Note Event
... note_event_field_concept_id 0..1 code Note Event Field

doco Documentation for this format

Summary

Mandatory: 0 element(8 nested mandatory elements)

Maturity: 2

 

Other representations of profile: CSV, Excel