Observational Health Data Sciences and Informatics

This is an old revision of the document!

NOTE_NLP table

The NOTE table encodes all output of NLP on clinical notes. Each row represents a single extracted term from a note. .

Field	Required	Type	Description
note_NLP_id	Yes	integer	A unique identifier for each note.
note_id	Yes	integer	A unique identifier for each note.
section_concept_id	Yes	integer	A unique identifier for each note.





nlp_date	Yes	date	The date the note was recorded.
term_exists	No	datetime	The date and time the note was recorded.
note_type_concept_id	Yes	integer	A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the type, origin or provenance of the Note.
value_as_concept_id	Yes	integer	A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the HL7 LOINC Document Type Vocabulary classification of the note.
value_as_number	No	varchar(250)	The title of the Note as it appears in the source.
value _as_string	Yes	RBDMS dependent text	The content of the Note.
unit_concept_id	Yes	integer	A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the note character encoding type.
term_temporal	Yes	integer	A foreign key to the predefined Concept in the Standardized Vocabularies reflecting the language of the note.
term_modifiers	No	integer	A foreign key to the Provider in the PROVIDER table who took the Note.

The NOTE table contains free text (in ASCII, or preferably in UTF8 format) taken by a healthcare Provider.
The Visit during which the note was written is recorded through a reference to the VISIT_OCCURRENCE table. This information is not always available.
The Provider making the note is recorded through a reference to the PROVIDER table. This information is not always available.
The type of note_text is CLOB or VARCHAR(MAX) depending on RDBMS