FHIR to OMOP FHIR IG
2.0.0-ballot - STU 1 Ballot International flag

FHIR to OMOP FHIR IG, published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-omop-ig/ and changes regularly. See the Directory of published versions

Logical Model: Note OMOP Table

Official URL: http://hl7.org/fhir/uv/omop/StructureDefinition/Note Version: 2.0.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: Note
Other Identifiers: OID:2.16.840.1.113883.4.642.40.77.42.15

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 Specification

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description Differentials, Snapshots, and other representations.

This structure is derived from Base

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

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

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(8 nested mandatory elements)

Maturity: 2

Differential View

This structure is derived from Base

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

doco Documentation for this format

Snapshot ViewView

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

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(8 nested mandatory elements)

Maturity: 2

 

Other representations of profile: CSV, Excel