anchor.diff:  CONCEPT_RELATIONSHIP,valid_start_date,Yes,date,The date when the relationship is first recorded.,,No,No,,,,,
   CONCEPT_RELATIONSHIP,valid_end_date,Yes,date,The date when the relationship is invalidated.,,No,No,,,,,
   CONCEPT_RELATIONSHIP,invalid_reason,No,varchar(1),"Reason the relationship was invalidated. Possible values are 'D' (deleted), 'U' (updated) or NULL. ",,No,No,,,,,
  -RELATIONSHIP,relationship_id,Yes,varchar(20),"The type of relationship captured by the
  +RELATIONSHIP,relationship_id,Yes,varchar(20),"The type of relationship captured by the
   relationship record.",,Yes,No,,,,,
   RELATIONSHIP,relationship_name,Yes,varchar(255),,,No,No,,,,,
  -RELATIONSHIP,is_hierarchical,Yes,varchar(1),"Defines whether a relationship defines
  -concepts into classes or hierarchies. Values
  +RELATIONSHIP,is_hierarchical,Yes,varchar(1),"Defines whether a relationship defines
  +concepts into classes or hierarchies. Values
   are 1 for hierarchical relationship or 0 if not.",,No,No,,,,,
  -RELATIONSHIP,defines_ancestry,Yes,varchar(1),"Defines whether a hierarchical relationship
  -contributes to the concept_ancestor table.
  -These are subsets of the hierarchical
  +RELATIONSHIP,defines_ancestry,Yes,varchar(1),"Defines whether a hierarchical relationship
  +contributes to the concept_ancestor table.
  +These are subsets of the hierarchical
   relationships. Valid values are 1 or 0.",,No,No,,,,,
  -RELATIONSHIP,reverse_relationship_id,Yes,varchar(20),"The identifier for the relationship used to
  -define the reverse relationship between two
  +RELATIONSHIP,reverse_relationship_id,Yes,varchar(20),"The identifier for the relationship used to
  +define the reverse relationship between two
   concepts.",,No,No,,,,,
  -RELATIONSHIP,relationship_concept_id,Yes,integer,"A foreign key that refers to an identifier in
  -the [CONCEPT](https://ohdsi.github.io/CommonDataModel/cdm531.html#concept) table for the unique
  +RELATIONSHIP,relationship_concept_id,Yes,integer,"A foreign key that refers to an identifier in
  +the [CONCEPT](https://ohdsi.github.io/CommonDataModel/cdm531.html#concept) table for the unique
   relationship concept.",,No,Yes,CONCEPT,CONCEPT_ID,,,
   CONCEPT_SYNONYM,concept_id,Yes,integer,,,No,Yes,CONCEPT,CONCEPT_ID,,,
   CONCEPT_SYNONYM,concept_synonym_name,Yes,varchar(1000),,,No,No,,,,,
   CONCEPT_SYNONYM,language_concept_id,Yes,integer,,,No,Yes,CONCEPT,CONCEPT_ID,,,
  -CONCEPT_ANCESTOR,ancestor_concept_id,Yes,integer,"The Concept Id for the higher-level concept
  +CONCEPT_ANCESTOR,ancestor_concept_id,Yes,integer,"The Concept Id for the higher-level concept
   that forms the ancestor in the relationship.",,No,Yes,CONCEPT,CONCEPT_ID,,,
  -CONCEPT_ANCESTOR,descendant_concept_id,Yes,integer,"The Concept Id for the lower-level concept
  -that forms the descendant in the
  +CONCEPT_ANCESTOR,descendant_concept_id,Yes,integer,"The Concept Id for the lower-level concept
  +that forms the descendant in the
   relationship.",,No,Yes,CONCEPT,CONCEPT_ID,,,
  -CONCEPT_ANCESTOR,min_levels_of_separation,Yes,integer,"The minimum separation in number of
  -levels of hierarchy between ancestor and
  -descendant concepts. This is an attribute
  +CONCEPT_ANCESTOR,min_levels_of_separation,Yes,integer,"The minimum separation in number of
  +levels of hierarchy between ancestor and
  +descendant concepts. This is an attribute
   that is used to simplify hierarchic analysis.",,No,No,,,,,
  -CONCEPT_ANCESTOR,max_levels_of_separation,Yes,integer,"The maximum separation in number of
  -levels of hierarchy between ancestor and
  -descendant concepts. This is an attribute
  +CONCEPT_ANCESTOR,max_levels_of_separation,Yes,integer,"The maximum separation in number of
  +levels of hierarchy between ancestor and
  +descendant concepts. This is an attribute
   that is used to simplify hierarchic analysis.",,No,No,,,,,
  -SOURCE_TO_CONCEPT_MAP,source_code,Yes,varchar(50),"The source code being translated
  +SOURCE_TO_CONCEPT_MAP,source_code,Yes,varchar(50),"The source code being translated
   into a Standard Concept.",,No,No,,,,,
  -SOURCE_TO_CONCEPT_MAP,source_concept_id,Yes,integer,"A foreign key to the Source
  -Concept that is being translated
  +SOURCE_TO_CONCEPT_MAP,source_concept_id,Yes,integer,"A foreign key to the Source
  +Concept that is being translated
   into a Standard Concept.","This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings. ",No,Yes,CONCEPT,CONCEPT_ID,,,
  -SOURCE_TO_CONCEPT_MAP,source_vocabulary_id,Yes,varchar(20),"A foreign key to the
  -VOCABULARY table defining the
  -vocabulary of the source code that
  -is being translated to a Standard
  +SOURCE_TO_CONCEPT_MAP,source_vocabulary_id,Yes,varchar(20),"A foreign key to the
  +VOCABULARY table defining the
  +vocabulary of the source code that
  +is being translated to a Standard
   Concept.",,No,No,,,,,
  -SOURCE_TO_CONCEPT_MAP,source_code_description,No,varchar(255),"An optional description for the
  -source code. This is included as a
  -convenience to compare the
  -description of the source code to
  +SOURCE_TO_CONCEPT_MAP,source_code_description,No,varchar(255),"An optional description for the
  +source code. This is included as a
  +convenience to compare the
  +description of the source code to
   the name of the concept.",,No,No,,,,,
  -SOURCE_TO_CONCEPT_MAP,target_concept_id,Yes,integer,"The target Concept
  -to which the source code is being
  +SOURCE_TO_CONCEPT_MAP,target_concept_id,Yes,integer,"The target Concept
  +to which the source code is being
   mapped.",,No,Yes,CONCEPT,CONCEPT_ID,,,
   SOURCE_TO_CONCEPT_MAP,target_vocabulary_id,Yes,varchar(20),The Vocabulary of the target Concept.,,No,Yes,VOCABULARY,VOCABULARY_ID,,,
  -SOURCE_TO_CONCEPT_MAP,valid_start_date,Yes,date,"The date when the mapping
  +SOURCE_TO_CONCEPT_MAP,valid_start_date,Yes,date,"The date when the mapping
   instance was first recorded.",,No,No,,,,,
  -SOURCE_TO_CONCEPT_MAP,valid_end_date,Yes,date,"The date when the mapping
  -instance became invalid because it
  -was deleted or superseded
  -(updated) by a new relationship.
  +SOURCE_TO_CONCEPT_MAP,valid_end_date,Yes,date,"The date when the mapping
  +instance became invalid because it
  +was deleted or superseded
  +(updated) by a new relationship.
   Default value is 31-Dec-2099.",,No,No,,,,,
   SOURCE_TO_CONCEPT_MAP,invalid_reason,No,varchar(1),"Reason the mapping instance was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.",,No,No,,,,,
   DRUG_STRENGTH,drug_concept_id,Yes,integer,The Concept representing the Branded Drug or Clinical Drug Product.,,No,Yes,CONCEPT,CONCEPT_ID,,,
  
positive.code: VISIT_DETAIL,visit_detail_concept_id,Yes,integer,"This field contains a concept id representing the kind of visit detail, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.","Populate this field based on the kind of visit that took place for the person. For example this could be ""Inpatient Visit"", ""Outpatient Visit"", ""Ambulatory Visit"", etc. This table will contain standard concepts in the Visit domain. These concepts are arranged in a hierarchical structure to facilitate cohort definitions by rolling up to generally familiar Visits adopted in most healthcare systems worldwide. [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,visit_detail_start_date,Yes,date,This is the date of the start of the encounter. This may or may not be equal to the date of the Visit the Visit Detail is associated with.,"When populating VISIT_DETAIL_START_DATE, you should think about the patient experience to make decisions on how to define visits. Most likely this should be the date of the patient-provider interaction.",No,No,,,,,
  VISIT_DETAIL,visit_detail_start_datetime,No,datetime,,"If no time is given for the start date of a visit, set it to midnight (00:00:0000).",No,No,,,,,
  VISIT_DETAIL,visit_detail_end_date,Yes,date,This the end date of the patient-provider interaction.,"Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:<br>
  - Outpatient Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
  - Emergency Room Visit Detail: visit_detail_end_datetime = visit_detail_start_datetime
  - Inpatient Visit Detail: Usually there is information about discharge. If not, you should be able to derive the end date from the sudden decline of activity or from the absence of inpatient procedures/drugs.
  - Non-hospital institution Visit Details: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs.<br>
  For Inpatient Visit Details ongoing at the date of ETL, put date of processing the data into visit_detai_end_datetime and visit_detail_type_concept_id with 32220 ""Still patient"" to identify the visit as incomplete.
  All other Visits Details: visit_detail_end_datetime = visit_detail_start_datetime. ",No,No,,,,,
  VISIT_DETAIL,visit_detail_end_datetime,No,datetime,,"If no time is given for the end date of a visit, set it to midnight (00:00:0000).",No,No,,,,,
  VISIT_DETAIL,visit_detail_type_concept_id,Yes,integer,"Use this field to understand the provenance of the visit detail record, or where the record comes from.","Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=).",No,Yes,CONCEPT,CONCEPT_ID,Type Concept,,
  
negative.code: 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
  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,,,,,
  