anchor.diff:  NOTE,note_date,Yes,date,The date the note was recorded.,,No,No,,,,,
   NOTE,note_datetime,No,datetime,,If time is not given set the time to midnight.,No,No,,,,,
   NOTE,note_type_concept_id,Yes,integer,The provenance of the note. Most likely this will be EHR. ,"Put the source system of the note, as in EHR record. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&domain=Type+Concept&page=1&pageSize=15&query=).",No,Yes,CONCEPT,CONCEPT_ID,Type Concept,,
  -NOTE,note_class_concept_id,Yes,integer,"A Standard Concept Id representing the HL7 LOINC
  +NOTE,note_class_concept_id,Yes,integer,"A Standard Concept Id representing the HL7 LOINC
   Document Type Vocabulary classification of the note.",Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&conceptClass=Doc+Kind&conceptClass=Doc+Role&conceptClass=Doc+Setting&conceptClass=Doc+Subject+Matter&conceptClass=Doc+Type+of+Service&domain=Meas+Value&page=1&pageSize=15&query=). This Concept can alternatively be represented by concepts with the relationship 'Kind of (LOINC)' to [706391](https://athena.ohdsi.org/search-terms/terms/706391) (Note).,No,Yes,CONCEPT,CONCEPT_ID,,,
   NOTE,note_title,No,varchar(250),The title of the note.,,No,No,,,,,
   NOTE,note_text,Yes,varchar(MAX),The content of the note.,,No,No,,,,,
  
positive.code: CONCEPT,concept_id,Yes,integer,A unique identifier for each Concept across all domains.,,Yes,No,,,,,
  CONCEPT,concept_name,Yes,varchar(255),"An unambiguous, meaningful and descriptive name for the Concept.",,No,No,,,,,
  CONCEPT,domain_id,Yes,varchar(20),A foreign key to the [DOMAIN](https://ohdsi.github.io/CommonDataModel/cdm531.html#domain) table the Concept belongs to.,,No,Yes,DOMAIN,DOMAIN_ID,,,
  CONCEPT,vocabulary_id,Yes,varchar(20),"A foreign key to the [VOCABULARY](https://ohdsi.github.io/CommonDataModel/cdm531.html#vocabulary)
  table indicating from which source the
  Concept has been adapted.",,No,Yes,VOCABULARY,VOCABULARY_ID,,,
  CONCEPT,concept_class_id,Yes,varchar(20),"The attribute or concept class of the
  Concept. Examples are 'Clinical Drug',
  'Ingredient', 'Clinical Finding' etc.",,No,Yes,CONCEPT_CLASS,CONCEPT_CLASS_ID,,,
  CONCEPT,standard_concept,No,varchar(1),"This flag determines where a Concept is
  a Standard Concept, i.e. is used in the
  data, a Classification Concept, or a
  non-standard Source Concept. The
  allowable values are 'S' (Standard
  Concept) and 'C' (Classification
  Concept), otherwise the content is NULL.",,No,No,,,,,
  CONCEPT,concept_code,Yes,varchar(50),"The concept code represents the identifier
  of the Concept in the source vocabulary,
  such as SNOMED-CT concept IDs,
  RxNorm RXCUIs etc. Note that concept
  codes are not unique across vocabularies.",,No,No,,,,,
  CONCEPT,valid_start_date,Yes,date,"The date when the Concept was first
  recorded. The default value is
  1-Jan-1970, meaning, the Concept has no
  (known) date of inception.",,No,No,,,,,
  CONCEPT,valid_end_date,Yes,date,"The date when the Concept became
  invalid because it was deleted or
  superseded (updated) by a new concept.
  The default value is 31-Dec-2099,
  meaning, the Concept is valid until it
  becomes deprecated.",,No,No,,,,,
  CONCEPT,invalid_reason,No,varchar(1),"Reason the Concept was invalidated.
  Possible values are D (deleted), U
  (replaced with an update) or NULL when
  valid_end_date has the default value.",,No,No,,,,,
  VOCABULARY,vocabulary_id,Yes,varchar(20),"A unique identifier for each Vocabulary, such
  as ICD9CM, SNOMED, Visit.",,Yes,No,,,,,
  VOCABULARY,vocabulary_name,Yes,varchar(255),"The name describing the vocabulary, for
  example, International Classification of
  Diseases, Ninth Revision, Clinical
  Modification, Volume 1 and 2 (NCHS) etc.",,No,No,,,,,
  VOCABULARY,vocabulary_reference,Yes,varchar(255),"External reference to documentation or
  available download of the about the
  vocabulary.",,No,No,,,,,
  VOCABULARY,vocabulary_version,No,varchar(255),"Version of the Vocabulary as indicated in
  the source.",,No,No,,,,,
  VOCABULARY,vocabulary_concept_id,Yes,integer,A Concept that represents the Vocabulary the VOCABULARY record belongs to.,,No,Yes,CONCEPT,CONCEPT_ID,,,
  DOMAIN,domain_id,Yes,varchar(20),A unique key for each domain.,,Yes,No,,,,,
  DOMAIN,domain_name,Yes,varchar(255),"The name describing the Domain, e.g.
  Condition, Procedure, Measurement
  etc.",,No,No,,,,,
  DOMAIN,domain_concept_id,Yes,integer,A Concept representing the Domain Concept the DOMAIN record belongs to.,,No,Yes,CONCEPT,CONCEPT_ID,,,
  CONCEPT_CLASS,concept_class_id,Yes,varchar(20),A unique key for each class.,,Yes,No,,,,,
  CONCEPT_CLASS,concept_class_name,Yes,varchar(255),"The name describing the Concept Class, e.g.
  Clinical Finding, Ingredient, etc.",,No,No,,,,,
  CONCEPT_CLASS,concept_class_concept_id,Yes,integer,A Concept that represents the Concept Class.,,No,Yes,CONCEPT,CONCEPT_ID,,,
  CONCEPT_RELATIONSHIP,concept_id_1,Yes,integer,,,No,Yes,CONCEPT,CONCEPT_ID,,,
  
negative.code: VISIT_DETAIL,care_site_id,No,integer,This field provides information about the Care Site where the Visit Detail took place.,There should only be one Care Site associated with a Visit Detail.,No,Yes,CARE_SITE,CARE_SITE_ID,,,
  VISIT_DETAIL,visit_detail_source_value,No,varchar(50),"This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)","If there is information about the kind of visit detail in the source data that value should be stored here. If a visit is an amalgamation of visits from the source then use a hierarchy to choose the VISIT_DETAIL_SOURCE_VALUE, such as IP -> ER-> OP. This should line up with the logic chosen to determine how visits are created.",No,No,,,,,
  VISIT_DETAIL,visit_detail_source_concept_id,No,Integer,,If the VISIT_DETAIL_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.,No,Yes,CONCEPT,CONCEPT_ID,,,
  VISIT_DETAIL,admitted_from_value,No,Varchar(50),,"This information may be called something different in the source data but the field is meant to contain a value indicating where a person was admitted from. Typically this applies only to visits that have a length of stay, like inpatient visits or long-term care visits.",No,No,,,,,
  VISIT_DETAIL,admitted_from_concept_id,No,Integer,"Use this field to determine where the patient was admitted from. This concept is part of the visit domain and can indicate if a patient was admitted to the hospital from a long-term care facility, for example.","If available, map the admitted_from_source_value to a standard concept in the visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).",No,Yes,CONCEPT,CONCEPT_ID,Visit,,
  VISIT_DETAIL,discharge_to_source_value,No,Varchar(50),,"This information may be called something different in the source data but the field is meant to contain a value indicating where a person was discharged to after a visit, as in they went home or were moved to long-term care. Typically this applies only to visits that have a length of stay of a day or more.",No,No,,,,,
  VISIT_DETAIL,discharge_to_concept_id,No,integer,"Use this field to determine where the patient was discharged to after a visit detail record. This concept is part of the visit domain and can indicate if a patient was discharged to home or sent to a long-term care facility, for example.","If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Visit&standardConcept=Standard&page=1&pageSize=15&query=).",No,Yes,CONCEPT,CONCEPT_ID,Visit,,
  VISIT_DETAIL,preceding_visit_detail_id,No,integer,Use this field to find the visit detail that occurred for the person prior to the given visit detail record. There could be a few days or a few years in between.,"The PRECEDING_VISIT_DETAIL_ID can be used to link a visit immediately preceding the current Visit Detail. Note this is not symmetrical, and there is no such thing as a ""following_visit_id"".",No,Yes,VISIT_DETAIL,VISIT_DETAIL_ID,,,
  