diff --git a/docs/background.html b/docs/background.html
index dd2e97f..56faaba 100644
--- a/docs/background.html
+++ b/docs/background.html
@@ -13,7 +13,7 @@
 
 <title>background.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdm30.html b/docs/cdm30.html
index d065ea7..19da13e 100644
--- a/docs/cdm30.html
+++ b/docs/cdm30.html
@@ -13,7 +13,7 @@
 
 <title>CDM v3</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdm53.html b/docs/cdm53.html
index 6930c04..348eff6 100644
--- a/docs/cdm53.html
+++ b/docs/cdm53.html
@@ -13,7 +13,7 @@
 
 <title>OMOP CDM v5.3</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -501,28 +511,28 @@ div.tocify {
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -532,55 +542,55 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every person with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is meant to capture the biological sex at birth of the Person. This field should not be used to study gender identity issues.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the gender or sex value present in the data under the assumption that it is the biological sex at birth. If the source data captures gender identity it should be stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#observation">OBSERVATION</a> table. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted gender concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -588,133 +598,133 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Compute age using year_of_birth.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources with date of birth, the year should be extracted. For data sources where the year of birth is not available, the approximate year of birth could be derived based on age group categorization, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 month_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the month should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 day_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the day should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 birth_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. If birth_datetime is not provided in the source, use the following logic to infer the date: If day_of_birth is null and month_of_birth is not null then use the first of the month in that year. If month_of_birth is null or if day_of_birth AND month_of_birth are both null and the person has records during their year of birth then use the date of the earliest record, otherwise use the 15th of June of that year. If time of birth is not given use midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures race or ethnic background of the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Race&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Race Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Race
 </td>
 </tr>
@@ -722,28 +732,28 @@ Race
 <td style="text-align:left;font-weight: bold;">
 ethnicity_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between “Hispanic” and “Not Hispanic”. Races and ethnic backgrounds are not stored here.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted ethnicity concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Ethnicity
 </td>
 </tr>
@@ -751,275 +761,275 @@ Ethnicity
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location refers to the physical address of the person. This field should capture the last known location of the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the location_id from the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#location">LOCATION</a> table here that represents the most granular location information for the person. This could represent anything from postal code or parts thereof, state, or county for example. Since many databases contain deidentified data, it is common that the precision of the location is reduced to prevent re-identification. This field should capture the last known location.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider refers to the last known primary care provider (General Practitioner).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider_id from the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#provider">PROVIDER</a> table of the last known general practitioner of the person. If there are multiple providers, it is up to the ETL to decide which to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Care Site refers to where the Provider typically provides the primary care.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to persons in the source data. This field allows for the storing of the person value as it appears in the source. This field is not required but strongly recommended.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the biological sex of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes biological sex in a non-standard vocabulary, store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the race of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes race in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the person has an ethnicity other than the OMB standard of “Hispanic” or “Not Hispanic” store that value from the source data here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1039,28 +1049,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1070,136 +1080,136 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign a unique observation_period_id to each discrete Observation Period for a Person.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person ID of the PERSON record for which the Observation Period is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the Observation Period.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_start_date can be inferred as the earliest Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer. If a Person switches plans but stays with the same payer, and therefore capturing of data continues, that change would be captured in <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period">PAYER_PLAN_PERIOD</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 period_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation Period as in whether the period was determined from an insurance enrollment file, EHR healthcare encounters, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the observation_period_type_concept_id that best represents how the period was determined. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1234,28 +1244,28 @@ Type Concept
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1265,81 +1275,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1347,134 +1357,134 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 When populating VISIT_START_DATE, you should think about the patient experience to make decisions on how to define visits. In the case of an inpatient visit this should be the date the patient was admitted to the hospital or institution. In all other cases this should be the date of the patient-provider interaction.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits the end date is typically the discharge date.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them: - Outpatient Visit: visit_end_datetime = visit_start_datetime - Emergency Room Visit: visit_end_datetime = visit_start_datetime - Inpatient Visit: 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 Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 “Still patient” to identify the visit as incomplete. - All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit record, as in whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1482,138 +1492,138 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple providers associated with a visit, you will need to choose which one to put here. The additional providers can be stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#visit_detail">VISIT_DETAIL</a> table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the Care Site where the Visit took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one Care Site associated with a Visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is information about the kind of visit 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 source value, such as IP -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitting_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1621,54 +1631,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 admitting_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharge_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to determine where the patient was discharged to after a visit. 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the discharge_to_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1676,54 +1686,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 discharge_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field can be used to link a visit immediately preceding the current visit. Note this is not symmetrical, and there is no such thing as a “following_visit_id”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1743,28 +1753,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1774,81 +1784,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1856,134 +1866,134 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This the end date of the patient-provider interaction.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit detail record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1991,164 +2001,164 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per <strong>visit</strong> record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The additional providers associated to a Visit can be stored in this table where each VISIT_DETAIL record represents a different provider.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the Care Site where the Visit Detail took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one Care Site associated with a Visit Detail.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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 -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitting_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitting_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2156,54 +2166,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 discharge_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharge_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2211,84 +2221,84 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_parent_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple nested levels to how Visits are represented in the source, the VISIT_DETAIL_PARENT_ID can be used to record this relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the VISIT_OCCURRENCE_ID that subsumes the VISIT_DETAIL record here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2308,28 +2318,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2339,82 +2349,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the condition is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the CONDITION_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of “Condition” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -2422,134 +2432,134 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the CONDITION_TYPE_CONCEPT_ID that best represents the provenance of the record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -2557,28 +2567,28 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 condition_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the Concept in the Condition Status domain that best represents the point during the visit when the diagnosis was given. These can include admitting diagnosis, principal diagnosis, and secondary diagnosis. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition+Status&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition Status
 </td>
 </tr>
@@ -2586,193 +2596,193 @@ Condition Status
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the condition occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a CONDITION_START_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the CONDITION_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the CONDITION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition status.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a diagnosis was given to a patient. This source value is mapped to a standard concept which is stored in the CONDITION_STATUS_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2792,28 +2802,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2823,82 +2833,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the drug dispensing or administration is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a drug product or molecule otherwise introduced to the body. The drug concepts can have a varying degree of information about drug strength and dose. This information is relevant in the context of quantity and administration information in the subsequent fields plus strength information from the DRUG_STRENGTH table, provided as part of the standard vocabulary download.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DRUG_SOURCE_VALUE maps to. The concept id should be derived either from mapping from the source concept id or by picking the drug concept representing the most amount of detail you have. Records whose source values map to standard concepts with a domain of Drug should go in this table. When the Drug Source Value of the code cannot be translated into Standard Drug Concept IDs, a Drug exposure entry is stored with only the corresponding SOURCE_CONCEPT_ID and DRUG_SOURCE_VALUE and a DRUG_CONCEPT_ID of 0. The Drug Concept with the most detailed content of information is preferred during the mapping process. These are indicated in the CONCEPT_CLASS_ID field of the Concept and are recorded in the following order of precedence: ‘Branded Pack’, ‘Clinical Pack’, ‘Branded Drug’, ‘Clinical Drug’, ‘Branded Drug Component’, ‘Clinical Drug Component’, ‘Branded Drug Form’, ‘Clinical Drug Form’, and only if no other information is available ‘Ingredient’. Note: If only the drug class is known, the DRUG_CONCEPT_ID field should contain 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Drug&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -2906,161 +2916,161 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the drug record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration was recorded. It is a valid ETL choice to use the date the drug was ordered as the DRUG_EXPOSURE_START_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If this information is not explicitly available in the data, infer the end date using the following methods:<br><br> 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">Examples by dose form</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 verbatim_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the end date of the drug exposure as it appears in the source data, if it is given
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3068,159 +3078,159 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The reason a person stopped a medication as it is represented in the source. Reasons include regimen completed, changed, removed, etc. This field will be retired in v6.0.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 refills
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is only filled in when the record is coming from a prescription written this field is meant to represent intended refills at time of the prescription.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is ‘Has dose form’. If liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table. If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. For clinical drugs with fixed dose forms (tablets etc.) the quantity is the number of units/tablets/capsules prescribed or dispensed (can be partial, but then only 1/2 or 1/3, not 0.01). Clinical drugs with divisible dose forms (injections) the quantity is the amount of ingredient the patient got. For example, if the injection is 2mg/mL but the patient got 80mL then quantity is reported as 160. Quantified clinical drugs with divisible dose forms (prefilled syringes), the quantity is the amount of ingredient similar to clinical drugs. Please see <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">how to calculate drug dose</a> for more information.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 days_supply
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Days supply of the drug. This should be the verbatim days_supply as given on the prescription. If the drug is physician administered use duration end date if given or set to 1 as default if duration is not available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sig
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the verbatim instruction for the drug as written by the provider.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the written out instructions for the drug as it is verbatim in the source, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the ROUTE_SOURCE_VALUE maps to in the route domain.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Route
 </td>
 </tr>
@@ -3228,218 +3238,218 @@ Route
 <td style="text-align:left;font-weight: bold;">
 lot_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with drug record, e.g. the provider who wrote the prescription or the provider who administered the drug.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the ordering vs administering physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the drug was prescribed, administered or dispensed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field drug exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the drug exposure occurred. For example, if the person was in the ICU at the time of the drug administration the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Drug Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the drug source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Drug necessary for a given analytic use case. Consider using DRUG_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DRUG_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug route.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a drug was given to a patient. This source value is mapped to a standard concept which is stored in the ROUTE_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the dose unit of the drug given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating the unit of dosage of drug given to the patient. This is an older column and will be deprecated in an upcoming version.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -3452,35 +3462,35 @@ No
 <p><strong>User Guide</strong></p>
 <p>Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.</p>
 <p><strong>ETL Conventions</strong></p>
-<p>If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here.</p>
+<p>If a procedure lasts more than 24 hours, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here.</p>
 <table class="table table-condensed table-hover" style="font-size: 13px; margin-left: auto; margin-right: auto;">
 <thead>
 <tr>
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -3490,82 +3500,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 procedure_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the PROCEDURE_SOURCE_VALUE maps to. Only records whose source values map to standard concepts with a domain of “Procedure” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Procedure&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Procedure
 </td>
 </tr>
@@ -3573,81 +3583,81 @@ Procedure
 <td style="text-align:left;font-weight: bold;">
 procedure_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date the procedure occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the PROCEDURE_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. If a procedure is recorded as an EHR encounter, the PROCEDURE_TYPE_CONCEPT would be ‘EHR encounter record’. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3655,220 +3665,220 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 modifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is up to the ETL to choose how to map modifiers if they exist in source data. These concepts are typically distinguished by ‘Modifier’ concept classes (e.g., ‘CPT4 Modifier’ as part of the ‘CPT4’ vocabulary). If there is more than one modifier on a record, one should be chosen that pertains to the procedure rather than provider. <a href="https://athena.ohdsi.org/search-terms/terms?conceptClass=CPT4+Modifier&amp;conceptClass=HCPCS+Modifier&amp;vocabulary=CPT4&amp;vocabulary=HCPCS&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the quantity value is omitted, a single procedure is assumed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Procedure has a quantity of ‘0’ in the source, this should default to ‘1’ in the ETL. If there is a record in the source it can be assumed the exposure occurred at least once
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the procedure record, e.g. the provider who performed the Procedure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the procedure occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a PROCEDURE_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the PROCEDURE_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use this value to look up the source concept id and then map the source concept id to a standard concept id.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the PROCEDURE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 modifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The original modifier code from the source is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -3888,28 +3898,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -3919,81 +3929,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 device_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records a person’s exposure to a foreign physical object or instrument.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DEVICE_SOURCE_VALUE maps to.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Device
 </td>
 </tr>
@@ -4001,134 +4011,134 @@ Device
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the device record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a procedure to implant a device, the date of a prescription for a device, or the date of device administration.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4136,191 +4146,191 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 unique_device_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Unique Device Identification number for devices regulated by the FDA, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For medical devices that are regulated by the FDA, a Unique Device Identification (UDI) is provided if available in the data source and is recorded in the UNIQUE_DEVICE_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit detail record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DEVICE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4340,28 +4350,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -4371,82 +4381,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 measurement_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the MEASUREMENT_SOURCE_CONCEPT_ID maps to. Only records whose SOURCE_CONCEPT_IDs map to Standard Concepts with a domain of “Measurement” should go in this table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Measurement
 </td>
 </tr>
@@ -4454,107 +4464,107 @@ Measurement
 <td style="text-align:left;font-weight: bold;">
 measurement_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date of the measurement.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple dates in the source data associated with a record such as order_date, draw_date, and result_date, choose the one that is closest to the date the sample was drawn from the patient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_time
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is present for backwards compatibility and will be deprecated in an upcoming version.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4562,111 +4572,111 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 operator_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The meaning of Concept <a href="https://athena.ohdsi.org/search-terms/terms/4172703">4172703</a> for ‘=’ is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it’s important when devising analyses to not to forget testing for the content of this field for values different from =.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Operators are =, &gt; and these concepts belong to the ‘Meas Value Operator’ domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is a negative value coming from the source, set the VALUE_AS_NUMBER to NULL, with the exception of the following Measurements (listed as LOINC codes):<br>- <a href="https://athena.ohdsi.org/search-terms/terms/3003396">1925-7</a> Base excess in Arterial blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3002032">1927-3</a> Base excess in Venous blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3006277">8632-2</a> QRS-Axis - <a href="https://athena.ohdsi.org/search-terms/terms/3012501">11555-0</a> Base excess in Blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3003129">1926-5</a> Base excess in Capillary blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3004959">28638-5</a> Base excess in Arterial cord blood by calculation <a href="https://athena.ohdsi.org/search-terms/terms/3007435">28639-3</a> Base excess in Venous cord blood by calculation
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the ‘Meas Value’ domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the raw data provides categorial results as well as continuous results for measurements, it is a valid ETL choice to preserve both values. The continuous value should go in the VALUE_AS_NUMBER field and the categorical value should be mapped to a standard concept in the ‘Meas Value’ domain and put in the VALUE_AS_CONCEPT_ID field. This is also the destination for the ‘Maps to value’ relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual measurements, i.e. it is not mandatory to represent Hemoglobin a1C measurements as a percentage. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with MEASUREMENT_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -4674,247 +4684,247 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 range_low
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 range_high
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Measurement occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a MEASUREMENT_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the measurement record. If a measurement is related to a visit explicitly in the source data, it is possible that the result date of the Measurement falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Measurement that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Measurement Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the MEASUREMENT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim result value of the Measurement from the source data .
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If both a continuous and categorical result are given in the source data such that both VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are both included, store the verbatim value that was mapped to VALUE_AS_CONCEPT_ID here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4934,28 +4944,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -4965,163 +4975,163 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an observation present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The OBSERVATION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the OBSERVATION_SOURCE_CONCEPT_ID maps to. There is no specified domain that the Concepts in this table must adhere to. The only rule is that records with Concepts in the Condition, Procedure, Drug, Measurement, or Device domains MUST go to the corresponding table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the Observation. Depending on what the Observation represents this could be the date of a lab test, the date of a survey, or the date a patient’s family history was taken.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For some observations the ETL may need to make a choice as to which date to choose.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given set to midnight (00:00:00).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5129,136 +5139,136 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Observation, if applicable and available. It is not expected that all Observations will have numeric results, rather, this field is here to house values should they exist.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the categorical value of the Result of the Observation, if applicable and available.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(60)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is possible that some records destined for the Observation table have two clinical ideas represented in one source code. This is common with ICD10 codes that describe a family history of some Condition, for example. In OMOP the Vocabulary breaks these two clinical ideas into two codes; one becomes the OBSERVATION_CONCEPT_ID and the other becomes the VALUE_AS_CONCEPT_ID. It is important when using the Observation table to keep this possibility in mind and to examine the VALUE_AS_CONCEPT_ID field for relevant information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Note that the value of VALUE_AS_CONCEPT_ID may be provided through mapping from a source Concept which contains the content of the Observation. In those situations, the CONCEPT_RELATIONSHIP table in addition to the ‘Maps to’ record contains a second record with the relationship_id set to ‘Maps to value’. For example, ICD10 <a href="https://athena.ohdsi.org/search-terms/terms/45581076">Z82.4</a> ‘Family history of ischaemic heart disease and other diseases of the circulatory system’ has a ‘Maps to’ relationship to <a href="https://athena.ohdsi.org/search-terms/terms/4167217">4167217</a> ‘Family history of clinical finding’ as well as a ‘Maps to value’ record to <a href="https://athena.ohdsi.org/search-terms/terms/134057">134057</a> ‘Disorder of cardiovascular system’.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use your best judgement as to what Concepts to use here and if they are necessary to accurately represent the clinical record. There is no restriction on the domain of these Concepts, they just need to be Standard.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual observation concepts. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -5266,193 +5276,193 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the observation record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Observation occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If an OBSERVATION_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the observation record. If an observation is related to a visit explicitly in the source data, it is possible that the result date of the Observation falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Observation occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -5468,28 +5478,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5499,107 +5509,107 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the person was deceased.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the precise date include day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If not available set time to midnight (00:00:00)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the type concept that be reflects the source of the death record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5607,81 +5617,81 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 cause_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Standard Concept representing the Person’s cause of death, if available.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no specified domain for this concept, just choose the Standard Concept Id that best represents the person’s cause of death.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cause_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, put the source code representing the cause of death here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cause_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the cause of death was coded using a Vocabulary present in the OMOP Vocabularies put the CONCEPT_ID representing the cause of death here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -5707,28 +5717,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5738,132 +5748,132 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the note was recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If time is not given set the time to midnight.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provenance of the note. Most likely this will be EHR.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source system of the note, as in EHR record. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5871,244 +5881,244 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 note_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Standard Concept Id representing the HL7 LOINC Document Type Vocabulary classification of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;conceptClass=Doc+Kind&amp;conceptClass=Doc+Role&amp;conceptClass=Doc+Setting&amp;conceptClass=Doc+Subject+Matter&amp;conceptClass=Doc+Type+of+Service&amp;domain=Meas+Value&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. This Concept can alternatively be represented by concepts with the relationship ‘Kind of (LOINC)’ to <a href="https://athena.ohdsi.org/search-terms/terms/706391">706391</a> (Note).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_title
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The title of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_text
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The content of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 encoding_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Concept representing the character encoding type.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the Concept Id that represents the encoding character type here. Currently the only option is UTF-8 (<a href="https://athena.ohdsi.org/search-terms/terms/32678">32678</a>). It the note is encoded in any other type, like ASCII then put 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The language of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use Concepts that are descendants of the concept <a href="https://athena.ohdsi.org/search-terms/terms/4182347">4182347</a> (World Languages).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider who wrote the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a determination on which provider to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The source value mapped to the NOTE_CLASS_CONCEPT_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6124,28 +6134,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6155,365 +6165,365 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_nlp_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for the NLP record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the NOTE_ID for the NOTE record the NLP record is associated to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 section_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The SECTION_CONCEPT_ID should be used to represent the note section contained in the NOTE_NLP record. These concepts can be found as parts of document panels and are based on the type of note written, i.e. a discharge summary. These panels can be found as concepts with the relationship ‘Subsumes’ to CONCEPT_ID <a href="https://athena.ohdsi.org/search-terms/terms/45875957">45875957</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 snippet
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A small window of text surrounding the term
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 “offset”
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Character offset of the extracted term in the input note
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 lexical_variant
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Raw text extracted from the NLP tool.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_system
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Name and version of the NLP system that extracted the term. Useful for data provenance.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date and time of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_exists
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_exists is defined as a flag that indicates if the patient actually has or had the condition. Any of the following modifiers would make Term_exists false: Negation = true Subject = [anything other than the patient] Conditional = true/li&gt; Rule_out = true Uncertain = very low certainty or any lower certainties A complete lack of modifiers would make Term_exists true.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_temporal
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_temporal is to indicate if a condition is present or just in the past. The following would be past:<br><br> - History = true - Concept_date = anything before the time of the report
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_modifiers
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For the modifiers that are there, they would have to have these values:<br><br> - Negation = false - Subject = patient - Conditional = false - Rule_out = false - Uncertain = true or high or moderate or even low (could argue about low). Term_modifiers will concatenate all modifiers for different types of entities (conditions, drugs, labs etc) into one string. Lab values will be saved as one of the modifiers.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6531,28 +6541,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6562,107 +6572,107 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 specimen_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Unique identifier for each specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The person from whom the specimen is collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the SPECIMEN_SOURCE_VALUE maps to in the specimen domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Specimen&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source of the specimen record, as in an EHR system. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -6670,287 +6680,287 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 specimen_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the specimen was collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of specimen collected from the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unit for the quantity of the specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Unit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen is from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the ANATOMIC_SITE_SOURCE_VALUE to a Standard Concept in the Spec Anatomic Site domain. This should be coded at the lowest level of granularity <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Spec+Anatomic+Site&amp;conceptClass=Body+Structure&amp;page=4&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier for the specimen from the source system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This unit for the quantity of the specimen, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen was taken from, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6968,28 +6978,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6999,128 +7009,128 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7141,28 +7151,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7172,206 +7182,206 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a unique Location.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a Location in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the first line of the address.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the second line of the address
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 city
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 state
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 zip
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(9)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 county
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the verbatim value for the location here, as it shows up in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7389,28 +7399,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7420,159 +7430,159 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign an id to each unique combination of location_id and place_of_service_source_value
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the care_site as it appears in the source data
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=2&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location_id from the LOCATION table representing the physical location of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the place of service of the care_site as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7590,28 +7600,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7621,214 +7631,214 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not necessary as it is not necessary to have the actual identity of the Provider. Rather, the idea is to uniquely and anonymously identify providers of care across the database.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 npi
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dea
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field either represents the most common specialty that occurs in the data or the most specific concept that represents all specialties listed, should the provider have more than one. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Specialty, there are two options: 1. Choose a concept_id which is a common ancestor to the multiple specialties, or, 2. Choose the specialty that occurs most often for the provider. Concepts in this field should be Standard with a domain of Provider. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Provider&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the CARE_SITE_ID for the location that the provider primarily practices in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Care Site, the main or most often exerted CARE_SITE_ID should be recorded.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the recorded gender of the provider in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If given, put a concept from the gender domain representing the recorded gender of the provider. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -7836,137 +7846,137 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 provider_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider identifier as it appears in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the kind of provider or specialty as it appears in the source data. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the kind of provider as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store physician speciality.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is provider’s gender as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider’s gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store provider gender.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7987,28 +7997,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8018,458 +8028,457 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
-Yes
+<td style="text-align:left;">
+No
 </td>
-<td style="text-align:left;width: 1in; ">
-PERSON
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person covered by the Plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 A single Person can have multiple, overlapping, PAYER_PLAN_PERIOD records
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Start date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 End date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the organization who reimburses the provider which administers care to the Person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Payer directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same payer, though the name of the Payer is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Payer&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Payer as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Payer in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the specific health benefit Plan the Person is enrolled in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the health benefit Plan of the Person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Plan in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the sponsor of the Plan who finances the Plan. This includes self-insured, small group health plan and large group health plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the sponsor directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same sponsor though the name of the sponsor is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan sponsor as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the sponsor in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 family_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The common identifier for all people (often a family) that covered by the same policy.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Often these are the common digits of the enrollment id of the policy members.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the reason the Person left the Plan, if known.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the stop reason directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan stop reason as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the stop reason in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8490,28 +8499,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8521,557 +8530,557 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cost_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 DOMAIN
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 currency_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_charge
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_cost
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_paid
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_payer
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_patient
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_copay
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_coinsurance
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_deductible
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_primary
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_ingredient_cost
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_dispensing_fee
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_allowed
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(3)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9092,28 +9101,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9123,78 +9132,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -9202,103 +9211,103 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient, with at least 31 days since the previous exposure.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era End Date is the end date of the last Drug Exposure. The End Date of each Drug Exposure is either taken from the field drug_exposure_end_date or, as it is typically not available, inferred using the following rules: For pharmacy prescription data, the date when the drug was dispensed plus the number of days of supply are used to extrapolate the End Date for the Drug Exposure. Depending on the country-specific healthcare system, this supply information is either explicitly provided in the day_supply field or inferred from package size or similar information. For Procedure Drugs, usually the drug is administered on a single date (i.e., the administration date). A standard Persistence Window of 30 days (gap, slack) is permitted between two subsequent such extrapolated DRUG_EXPOSURE records to be considered to be merged into a single Drug Era.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gap_days
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Gap Days determine how many total drug-free days are observed between all Drug Exposure events that contribute to a DRUG_ERA record. It is assumed that the drugs are “not stockpiled” by the patient, i.e. that if a new drug prescription or refill is observed (a new DRUG_EXPOSURE record is written), the remaining supply from the previous events is abandoned. The difference between Persistence Window and Gap Days is that the former is the maximum drug-free time allowed between two subsequent DRUG_EXPOSURE records, while the latter is the sum of actual drug-free days for the given Drug Era under the above assumption of non-stockpiling.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9316,28 +9325,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9347,78 +9356,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 dose_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -9426,27 +9435,27 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the unit of the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -9454,78 +9463,78 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 dose_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value of the dosage of the drug_ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the Person started on the specific dosage, with at least 31 days since any prior exposure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The date the Person was no longer exposed to the dosage of the specific drug ingredient. An era is ended if there are 31 days or more between dosage records.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9547,28 +9556,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9578,78 +9587,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -9657,78 +9666,78 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of individual Condition Occurrences used to construct the condition era.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9747,28 +9756,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9778,178 +9787,178 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 metadata_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9965,28 +9974,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9996,257 +10005,257 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cdm_source_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_source_abbreviation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The abbreviation of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(25)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_holder
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The holder of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The description of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_documentation_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_etl_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the link to the CDM version used.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release date of the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release data of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10267,28 +10276,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10298,263 +10307,263 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Concept across all domains.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 An unambiguous, meaningful and descriptive name for the Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#domain">DOMAIN</a> table the Concept belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 DOMAIN
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#vocabulary">VOCABULARY</a> table indicating from which source the Concept has been adapted.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The attribute or concept class of the Concept. Examples are ‘Clinical Drug’, ‘Ingredient’, ‘Clinical Finding’ etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT_CLASS
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 standard_concept
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10570,28 +10579,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10601,131 +10610,131 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the vocabulary, for example, International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS) etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 External reference to documentation or available download of the about the vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Version of the Vocabulary as indicated in the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Vocabulary the VOCABULARY record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10741,28 +10750,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10772,79 +10781,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Domain, e.g. Condition, Procedure, Measurement etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept representing the Domain Concept the DOMAIN record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10860,28 +10869,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10891,79 +10900,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Concept Class, e.g. Clinical Finding, Ingredient, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Concept Class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10979,28 +10988,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11010,157 +11019,157 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The relationship between CONCEPT_ID_1 and CONCEPT_ID_2. Please see the <a href="https://ohdsi.github.io/CommonDataModel/dataModelConventions.html#concept_relationships">Vocabulary Conventions</a>. for more information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 RELATIONSHIP
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is invalidated.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Reason the relationship was invalidated. Possible values are ‘D’ (deleted), ‘U’ (updated) or NULL.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11176,28 +11185,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11207,156 +11216,156 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The type of relationship captured by the relationship record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 is_hierarchical
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 defines_ancestry
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 reverse_relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The identifier for the relationship used to define the reverse relationship between two concepts.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key that refers to an identifier in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#concept">CONCEPT</a> table for the unique relationship concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11372,28 +11381,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11403,77 +11412,77 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_synonym_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11490,28 +11499,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11521,106 +11530,106 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 ancestor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the higher-level concept that forms the ancestor in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 descendant_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the lower-level concept that forms the descendant in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 min_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 max_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11636,28 +11645,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11667,238 +11676,238 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 source_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source code being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the Source Concept that is being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_code_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The target Concept to which the source code is being mapped.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Vocabulary of the target Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the mapping instance was first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11914,28 +11923,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11945,318 +11954,318 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Branded Drug or Clinical Drug Product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ingredient_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Combination Drugs will have more than one record in this table, one for each active Ingredient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value or the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The concentration of the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the denominator unit for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 box_size
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when then Concept became invalid.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12272,28 +12281,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12303,184 +12312,184 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier given to the cohort, usually by the ATLAS application
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A short description of the cohort
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A complete description of the cohort.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 definition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Type defining what kind of Cohort Definition the record represents and how the syntax may be executed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_syntax
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Syntax or code to operationalize the Cohort Definition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 subject_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a Concept that represents the domain of the subjects that are members of the cohort (e.g., Person, Provider, Visit).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_initiation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A date to indicate when the Cohort was initiated in the COHORT table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12496,28 +12505,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12527,126 +12536,126 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 attribute_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 attribute_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 attribute_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 attribute_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 attribute_syntax
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
diff --git a/docs/cdm531.html b/docs/cdm531.html
index 626a74f..5f57236 100644
--- a/docs/cdm531.html
+++ b/docs/cdm531.html
@@ -13,7 +13,7 @@
 
 <title>OMOP CDM v5.3.1</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdm54.html b/docs/cdm54.html
index 7d1b8a4..41fde3b 100644
--- a/docs/cdm54.html
+++ b/docs/cdm54.html
@@ -13,7 +13,7 @@
 
 <title>OMOP CDM v5.4</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -572,28 +582,28 @@ div.tocify {
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -603,55 +613,55 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every person with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is meant to capture the biological sex at birth of the Person. This field should not be used to study gender identity issues.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the gender or sex value present in the data under the assumption that it is the biological sex at birth. If the source data captures gender identity it should be stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#observation">OBSERVATION</a> table. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted gender concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -659,133 +669,133 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Compute age using year_of_birth.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources with date of birth, the year should be extracted. For data sources where the year of birth is not available, the approximate year of birth could be derived based on age group categorization, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 month_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the month should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 day_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the day should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 birth_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. If birth_datetime is not provided in the source, use the following logic to infer the date: If day_of_birth is null and month_of_birth is not null then use the first of the month in that year. If month_of_birth is null or if day_of_birth AND month_of_birth are both null and the person has records during their year of birth then use the date of the earliest record, otherwise use the 15th of June of that year. If time of birth is not given use midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures race or ethnic background of the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Race&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Race Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Race
 </td>
 </tr>
@@ -793,28 +803,28 @@ Race
 <td style="text-align:left;font-weight: bold;">
 ethnicity_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between “Hispanic” and “Not Hispanic”. Races and ethnic backgrounds are not stored here.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted ethnicity concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Ethnicity
 </td>
 </tr>
@@ -822,275 +832,275 @@ Ethnicity
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location refers to the physical address of the person. This field should capture the last known location of the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the location_id from the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#location">LOCATION</a> table here that represents the most granular location information for the person. This could represent anything from postal code or parts thereof, state, or county for example. Since many databases contain deidentified data, it is common that the precision of the location is reduced to prevent re-identification. This field should capture the last known location.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider refers to the last known primary care provider (General Practitioner).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider_id from the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#provider">PROVIDER</a> table of the last known general practitioner of the person. If there are multiple providers, it is up to the ETL to decide which to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Care Site refers to where the Provider typically provides the primary care.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to persons in the source data. This field allows for the storing of the person value as it appears in the source. This field is not required but strongly recommended.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the biological sex of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes biological sex in a non-standard vocabulary, store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the race of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes race in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the person has an ethnicity other than the OMB standard of “Hispanic” or “Not Hispanic” store that value from the source data here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1110,28 +1120,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1141,136 +1151,136 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign a unique observation_period_id to each discrete Observation Period for a Person.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person ID of the PERSON record for which the Observation Period is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the Observation Period.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_start_date can be inferred as the earliest Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer. If a Person switches plans but stays with the same payer, and therefore capturing of data continues, that change would be captured in <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period">PAYER_PLAN_PERIOD</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 period_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation Period as in whether the period was determined from an insurance enrollment file, EHR healthcare encounters, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the observation_period_type_concept_id that best represents how the period was determined. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1305,28 +1315,28 @@ Type Concept
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1336,81 +1346,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1418,135 +1428,135 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 When populating VISIT_START_DATE, you should think about the patient experience to make decisions on how to define visits. In the case of an inpatient visit this should be the date the patient was admitted to the hospital or institution. In all other cases this should be the date of the patient-provider interaction.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits the end date is typically the discharge date. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them: - Outpatient Visit: visit_end_datetime = visit_start_datetime - Emergency Room Visit: visit_end_datetime = visit_start_datetime - Inpatient Visit: 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 Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 “Still patient” to identify the visit as incomplete. - All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit record, as in whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1554,138 +1564,138 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple providers associated with a visit, you will need to choose which one to put here. The additional providers can be stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#visit_detail">VISIT_DETAIL</a> table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the Care Site where the Visit took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one Care Site associated with a Visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is information about the kind of visit 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 source value, such as IP -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitted_from_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. If a person was admitted from home, set this to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1693,54 +1703,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 admitted_from_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharged_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for “home”. Use concept id = 0 when a person is discharged to home.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the discharged_to_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1748,54 +1758,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 discharged_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field can be used to link a visit immediately preceding the current visit. Note this is not symmetrical, and there is no such thing as a “following_visit_id”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1815,28 +1825,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1846,81 +1856,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1928,135 +1938,135 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This the end date of the patient-provider interaction. If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_date, then set the visit_end_date to the date of the data pull.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If a Person is still an inpatient in the hospital at the time of the data extract and does not have a visit_end_datetime, then set the visit_end_datetime to the datetime of the data pull.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit detail record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -2064,138 +2074,138 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per <strong>visit</strong> record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The additional providers associated to a Visit can be stored in this table where each VISIT_DETAIL record represents a different provider.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the Care Site where the Visit Detail took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one Care Site associated with a Visit Detail.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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 -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitted_from_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. If the person was admitted from home, set this to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2203,80 +2213,80 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 admitted_from_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharged_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharged_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to determine where the patient was discharged to after a visit. This concept is part of the visit domain and can indicate if a patient was transferred to another hospital or sent to a long-term care facility, for example. It is assumed that a person is discharged to home therefore there is not a standard concept id for “home”. Use concept id = 0 when a person is discharged to home.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2284,84 +2294,84 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 parent_visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple nested levels to how Visits are represented in the source, the VISIT_DETAIL_PARENT_ID can be used to record this relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the VISIT_OCCURRENCE_ID that subsumes the VISIT_DETAIL record here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2381,28 +2391,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2412,82 +2422,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the condition is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the CONDITION_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of “Condition” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -2495,134 +2505,134 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the CONDITION_TYPE_CONCEPT_ID that best represents the provenance of the record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -2630,28 +2640,28 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 condition_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the Concept in the Condition Status domain that best represents the point during the visit when the diagnosis was given. These can include admitting diagnosis, principal diagnosis, and secondary diagnosis. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition+Status&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition Status
 </td>
 </tr>
@@ -2659,193 +2669,193 @@ Condition Status
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the condition occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a CONDITION_START_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the CONDITION_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the CONDITION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition status.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a diagnosis was given to a patient. This source value is mapped to a standard concept which is stored in the CONDITION_STATUS_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2865,28 +2875,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2896,82 +2906,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the drug dispensing or administration is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a drug product or molecule otherwise introduced to the body. The drug concepts can have a varying degree of information about drug strength and dose. This information is relevant in the context of quantity and administration information in the subsequent fields plus strength information from the DRUG_STRENGTH table, provided as part of the standard vocabulary download.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DRUG_SOURCE_VALUE maps to. The concept id should be derived either from mapping from the source concept id or by picking the drug concept representing the most amount of detail you have. Records whose source values map to standard concepts with a domain of Drug should go in this table. When the Drug Source Value of the code cannot be translated into Standard Drug Concept IDs, a Drug exposure entry is stored with only the corresponding SOURCE_CONCEPT_ID and DRUG_SOURCE_VALUE and a DRUG_CONCEPT_ID of 0. The Drug Concept with the most detailed content of information is preferred during the mapping process. These are indicated in the CONCEPT_CLASS_ID field of the Concept and are recorded in the following order of precedence: ‘Branded Pack’, ‘Clinical Pack’, ‘Branded Drug’, ‘Clinical Drug’, ‘Branded Drug Component’, ‘Clinical Drug Component’, ‘Branded Drug Form’, ‘Clinical Drug Form’, and only if no other information is available ‘Ingredient’. Note: If only the drug class is known, the DRUG_CONCEPT_ID field should contain 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Drug&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -2979,161 +2989,161 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the drug record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration was recorded. It is a valid ETL choice to use the date the drug was ordered as the DRUG_EXPOSURE_START_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If this information is not explicitly available in the data, infer the end date using the following methods:<br><br> 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">Examples by dose form</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 verbatim_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the end date of the drug exposure as it appears in the source data, if it is given
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3141,159 +3151,159 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The reason a person stopped a medication as it is represented in the source. Reasons include regimen completed, changed, removed, etc. This field will be retired in v6.0.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 refills
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is only filled in when the record is coming from a prescription written this field is meant to represent intended refills at time of the prescription.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is ‘Has dose form’. If liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table. If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. For clinical drugs with fixed dose forms (tablets etc.) the quantity is the number of units/tablets/capsules prescribed or dispensed (can be partial, but then only 1/2 or 1/3, not 0.01). Clinical drugs with divisible dose forms (injections) the quantity is the amount of ingredient the patient got. For example, if the injection is 2mg/mL but the patient got 80mL then quantity is reported as 160. Quantified clinical drugs with divisible dose forms (prefilled syringes), the quantity is the amount of ingredient similar to clinical drugs. Please see <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">how to calculate drug dose</a> for more information.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 days_supply
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Days supply of the drug. This should be the verbatim days_supply as given on the prescription. If the drug is physician administered use duration end date if given or set to 1 as default if duration is not available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sig
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the verbatim instruction for the drug as written by the provider.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the written out instructions for the drug as it is verbatim in the source, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the ROUTE_SOURCE_VALUE maps to in the route domain.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Route
 </td>
 </tr>
@@ -3301,218 +3311,218 @@ Route
 <td style="text-align:left;font-weight: bold;">
 lot_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with drug record, e.g. the provider who wrote the prescription or the provider who administered the drug.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the ordering vs administering physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the drug was prescribed, administered or dispensed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field drug exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the drug exposure occurred. For example, if the person was in the ICU at the time of the drug administration the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Drug Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the drug source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Drug necessary for a given analytic use case. Consider using DRUG_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DRUG_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug route.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a drug was given to a patient. This source value is mapped to a standard concept which is stored in the ROUTE_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the dose unit of the drug given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating the unit of dosage of drug given to the patient. <strong>This is an older column and will be deprecated in an upcoming version.</strong>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -3525,35 +3535,35 @@ No
 <p><strong>User Guide</strong></p>
 <p>Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.</p>
 <p><strong>ETL Conventions</strong></p>
-<p>If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here.</p>
+<p>When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here.</p>
 <table class="table table-condensed table-hover" style="font-size: 13px; margin-left: auto; margin-right: auto;">
 <thead>
 <tr>
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -3563,82 +3573,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 procedure_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the PROCEDURE_SOURCE_VALUE maps to. Only records whose source values map to standard concepts with a domain of “Procedure” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Procedure&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Procedure
 </td>
 </tr>
@@ -3646,135 +3656,135 @@ Procedure
 <td style="text-align:left;font-weight: bold;">
 procedure_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date the procedure started.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is meant to be the <strong>start date</strong> of the procedure. It will be renamed in a future version to <strong>PROCEDURE_START_DATE</strong>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the procedure has a start time in the native date, use this field to house that information. This will be renamed in a future version to <strong>PROCEDURE_START_DATETIME</strong>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to house the date that the procedure ended.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is meant to be the end date of the procedure. It is not required and for most cases will be the same as the PROCEDURE_START_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to house the datetime that the procedure ended.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is meant to house the end datetime of the procedure and will most often be used in conjunction with the procedure_start_datetime to determine the length of the procedure.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the PROCEDURE_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. If a procedure is recorded as an EHR encounter, the PROCEDURE_TYPE_CONCEPT would be ‘EHR encounter record’. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3782,220 +3792,220 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 modifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is up to the ETL to choose how to map modifiers if they exist in source data. These concepts are typically distinguished by ‘Modifier’ concept classes (e.g., ‘CPT4 Modifier’ as part of the ‘CPT4’ vocabulary). If there is more than one modifier on a record, one should be chosen that pertains to the procedure rather than provider. <a href="https://athena.ohdsi.org/search-terms/terms?conceptClass=CPT4+Modifier&amp;conceptClass=HCPCS+Modifier&amp;vocabulary=CPT4&amp;vocabulary=HCPCS&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the quantity value is omitted, a single procedure is assumed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Procedure has a quantity of ‘0’ in the source, this should default to ‘1’ in the ETL. If there is a record in the source it can be assumed the exposure occurred at least once
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the procedure record, e.g. the provider who performed the Procedure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the procedure occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a PROCEDURE_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the PROCEDURE_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use this value to look up the source concept id and then map the source concept id to a standard concept id.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the PROCEDURE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 modifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The original modifier code from the source is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4015,28 +4025,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -4046,81 +4056,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 device_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records a person’s exposure to a foreign physical object or instrument.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DEVICE_SOURCE_VALUE maps to.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Device
 </td>
 </tr>
@@ -4128,134 +4138,134 @@ Device
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the device record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a procedure to implant a device, the date of a prescription for a device, or the date of device administration.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4263,245 +4273,245 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 unique_device_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Unique Device Identification (UDI-DI) number for devices regulated by the FDA, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For medical devices that are regulated by the FDA, a Unique Device Identification (UDI) is provided if available in the data source and is recorded in the UNIQUE_DEVICE_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 production_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Production Identifier (UDI-PI) portion of the Unique Device Identification.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit detail record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DEVICE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with DEVICE_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit. If there is no unit associated with a Device record, set to NULL.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -4509,55 +4519,55 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Device. For example, blood transfusions are considered devices and can be given in mL quantities.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference. Using the blood transfusion example, blood transfusion is represented by the DEVICE_CONCEPT_ID and the unit (mL) would be housed in the UNIT_SOURCE_VALUE and mapped to a standard concept in the unit domain.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Unit necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the UNIT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4577,28 +4587,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -4608,82 +4618,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 measurement_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the Person for whom the Measurement is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the MEASUREMENT_SOURCE_CONCEPT_ID maps to. Only records whose SOURCE_CONCEPT_IDs map to Standard Concepts with a domain of “Measurement” should go in this table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Measurement
 </td>
 </tr>
@@ -4691,107 +4701,107 @@ Measurement
 <td style="text-align:left;font-weight: bold;">
 measurement_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date of the measurement.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple dates in the source data associated with a record such as order_date, draw_date, and result_date, choose the one that is closest to the date the sample was drawn from the patient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_time
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is present for backwards compatibility and will be deprecated in an upcoming version.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4799,111 +4809,111 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 operator_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The meaning of Concept <a href="https://athena.ohdsi.org/search-terms/terms/4172703">4172703</a> for ‘=’ is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it’s important when devising analyses to not to forget testing for the content of this field for values different from =.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Operators are =, &gt; and these concepts belong to the ‘Meas Value Operator’ domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is a negative value coming from the source, set the VALUE_AS_NUMBER to NULL, with the exception of the following Measurements (listed as LOINC codes):<br>- <a href="https://athena.ohdsi.org/search-terms/terms/3003396">1925-7</a> Base excess in Arterial blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3002032">1927-3</a> Base excess in Venous blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3006277">8632-2</a> QRS-Axis - <a href="https://athena.ohdsi.org/search-terms/terms/3012501">11555-0</a> Base excess in Blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3003129">1926-5</a> Base excess in Capillary blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3004959">28638-5</a> Base excess in Arterial cord blood by calculation <a href="https://athena.ohdsi.org/search-terms/terms/3007435">28639-3</a> Base excess in Venous cord blood by calculation
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the ‘Meas Value’ domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the raw data provides categorial results as well as continuous results for measurements, it is a valid ETL choice to preserve both values. The continuous value should go in the VALUE_AS_NUMBER field and the categorical value should be mapped to a standard concept in the ‘Meas Value’ domain and put in the VALUE_AS_CONCEPT_ID field. This is also the destination for the ‘Maps to value’ relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual measurements, i.e. it is not mandatory to represent Hemoglobin a1C measurements as a percentage. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with MEASUREMENT_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -4911,330 +4921,330 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 range_low
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 range_high
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Measurement occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a MEASUREMENT_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the measurement record. If a measurement is related to a visit explicitly in the source data, it is possible that the result date of the Measurement falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Measurement that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Measurement Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the MEASUREMENT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 “This is the concept representing the UNIT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using UNIT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.”
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the UNIT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim result value of the Measurement from the source data .
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If both a continuous and categorical result are given in the source data such that both VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are both included, store the verbatim value that was mapped to VALUE_AS_CONCEPT_ID here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Measurement record is related to another record in the database, this field is the primary key of the linked record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record, if applicable, here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 meas_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Measurement record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the MEASUREMENT_EVENT_ID came from.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -5254,28 +5264,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5285,163 +5295,163 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an observation present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The OBSERVATION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the OBSERVATION_SOURCE_CONCEPT_ID maps to. There is no specified domain that the Concepts in this table must adhere to. The only rule is that records with Concepts in the Condition, Procedure, Drug, Measurement, or Device domains MUST go to the corresponding table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the Observation. Depending on what the Observation represents this could be the date of a lab test, the date of a survey, or the date a patient’s family history was taken.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For some observations the ETL may need to make a choice as to which date to choose.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given set to midnight (00:00:00).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5449,136 +5459,136 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Observation, if applicable and available. It is not expected that all Observations will have numeric results, rather, this field is here to house values should they exist.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the categorical value of the Result of the Observation, if applicable and available.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(60)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is possible that some records destined for the Observation table have two clinical ideas represented in one source code. This is common with ICD10 codes that describe a family history of some Condition, for example. In OMOP the Vocabulary breaks these two clinical ideas into two codes; one becomes the OBSERVATION_CONCEPT_ID and the other becomes the VALUE_AS_CONCEPT_ID. It is important when using the Observation table to keep this possibility in mind and to examine the VALUE_AS_CONCEPT_ID field for relevant information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Note that the value of VALUE_AS_CONCEPT_ID may be provided through mapping from a source Concept which contains the content of the Observation. In those situations, the CONCEPT_RELATIONSHIP table in addition to the ‘Maps to’ record contains a second record with the relationship_id set to ‘Maps to value’. For example, ICD10 <a href="https://athena.ohdsi.org/search-terms/terms/45581076">Z82.4</a> ‘Family history of ischaemic heart disease and other diseases of the circulatory system’ has a ‘Maps to’ relationship to <a href="https://athena.ohdsi.org/search-terms/terms/4167217">4167217</a> ‘Family history of clinical finding’ as well as a ‘Maps to value’ record to <a href="https://athena.ohdsi.org/search-terms/terms/134057">134057</a> ‘Disorder of cardiovascular system’.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use your best judgement as to what Concepts to use here and if they are necessary to accurately represent the clinical record. There is no restriction on the domain of these Concepts, they just need to be Standard.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual observation concepts. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -5586,275 +5596,275 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the observation record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Observation occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If an OBSERVATION_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the observation record. If an observation is related to a visit explicitly in the source data, it is possible that the result date of the Observation falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Observation occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim result value of the Observation from the source data. Do not get confused with the Observation_source_value which captures source value of the observation mapped to observation_concept_id. This field is the observation result value from the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the observation_source_value was a question, for example, or an observation that requires a result then this field is the answer/ result from the source data. Store the verbatim value that represents the result of the observation_source_value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Observation record is related to another record in the database, this field is the primary key of the linked record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record, if applicable, here. See the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#observation">ETL Conventions for the OBSERVATION</a> table for more details.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 obs_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Observation record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the OBSERVATION_EVENT_ID came from.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -5870,28 +5880,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5901,107 +5911,107 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the person was deceased.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the precise date include day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If not available set time to midnight (00:00:00)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the provenance of the death record, i.e., where it came from. It is possible that an administrative claims database would source death information from a government file so do not assume the Death Type is the same as the Visit Type, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the type concept that be reflects the source of the death record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -6009,81 +6019,81 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 cause_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Standard Concept representing the Person’s cause of death, if available.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no specified domain for this concept, just choose the Standard Concept Id that best represents the person’s cause of death.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cause_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, put the source code representing the cause of death here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cause_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the cause of death was coded using a Vocabulary present in the OMOP Vocabularies put the CONCEPT_ID representing the cause of death here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6109,28 +6119,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6140,132 +6150,132 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the note was recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If time is not given set the time to midnight.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provenance of the note. Most likely this will be EHR.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source system of the note, as in EHR record. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -6273,299 +6283,299 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 note_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Standard Concept Id representing the HL7 LOINC Document Type Vocabulary classification of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;conceptClass=Doc+Kind&amp;conceptClass=Doc+Role&amp;conceptClass=Doc+Setting&amp;conceptClass=Doc+Subject+Matter&amp;conceptClass=Doc+Type+of+Service&amp;domain=Meas+Value&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. This Concept can alternatively be represented by concepts with the relationship ‘Kind of (LOINC)’ to <a href="https://athena.ohdsi.org/search-terms/terms/706391">706391</a> (Note).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_title
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The title of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_text
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The content of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 encoding_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Concept representing the character encoding type.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the Concept Id that represents the encoding character type here. Currently the only option is UTF-8 (<a href="https://athena.ohdsi.org/search-terms/terms/32678">32678</a>). It the note is encoded in any other type, like ASCII then put 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The language of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use Concepts that are descendants of the concept <a href="https://athena.ohdsi.org/search-terms/terms/4182347">4182347</a> (World Languages).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider who wrote the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a determination on which provider to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The source value mapped to the NOTE_CLASS_CONCEPT_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Note record is related to another record in the database, this field is the primary key of the linked record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record, if applicable, here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Note record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the NOTE_EVENT_ID came from.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6581,28 +6591,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6612,365 +6622,365 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_nlp_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for the NLP record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the NOTE_ID for the NOTE record the NLP record is associated to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 section_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The SECTION_CONCEPT_ID should be used to represent the note section contained in the NOTE_NLP record. These concepts can be found as parts of document panels and are based on the type of note written, i.e. a discharge summary. These panels can be found as concepts with the relationship ‘Subsumes’ to CONCEPT_ID <a href="https://athena.ohdsi.org/search-terms/terms/45875957">45875957</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 snippet
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A small window of text surrounding the term
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 “offset”
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Character offset of the extracted term in the input note
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 lexical_variant
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Raw text extracted from the NLP tool.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_system
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Name and version of the NLP system that extracted the term. Useful for data provenance.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date and time of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_exists
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_exists is defined as a flag that indicates if the patient actually has or had the condition. Any of the following modifiers would make Term_exists false: Negation = true Subject = [anything other than the patient] Conditional = true/li&gt; Rule_out = true Uncertain = very low certainty or any lower certainties A complete lack of modifiers would make Term_exists true.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_temporal
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_temporal is to indicate if a condition is present or just in the past. The following would be past:<br><br> - History = true - Concept_date = anything before the time of the report
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_modifiers
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For the modifiers that are there, they would have to have these values:<br><br> - Negation = false - Subject = patient - Conditional = false - Rule_out = false - Uncertain = true or high or moderate or even low (could argue about low). Term_modifiers will concatenate all modifiers for different types of entities (conditions, drugs, labs etc) into one string. Lab values will be saved as one of the modifiers.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6988,28 +6998,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7019,107 +7029,107 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 specimen_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Unique identifier for each specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The person from whom the specimen is collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the SPECIMEN_SOURCE_VALUE maps to in the specimen domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Specimen&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source of the specimen record, as in an EHR system. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -7127,287 +7137,287 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 specimen_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the specimen was collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of specimen collected from the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unit for the quantity of the specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Unit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen is from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the ANATOMIC_SITE_SOURCE_VALUE to a Standard Concept in the Spec Anatomic Site domain. This should be coded at the lowest level of granularity <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Spec+Anatomic+Site&amp;conceptClass=Body+Structure&amp;page=4&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier for the specimen from the source system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This unit for the quantity of the specimen, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen was taken from, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7425,28 +7435,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7456,128 +7466,128 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7600,28 +7610,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7631,311 +7641,311 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a unique Location.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a Location in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the first line of the address.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the second line of the address
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 city
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 state
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 zip
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(9)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 county
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the verbatim value for the location here, as it shows up in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 country_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the country. Values should conform to the <a href="https://athena.ohdsi.org/search-terms/terms?domain=Geography&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=&amp;boosts">Geography</a> domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 country_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the country.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(80)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 latitude
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Must be between -90 and 90.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 longitude
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Must be between -180 and 180.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7953,28 +7963,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7984,159 +7994,159 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign an ID to each combination of a location and nature of the site - the latter could be the Place of Service, name or another characteristic in your source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the care_site as it appears in the source data
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=2&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location_id from the LOCATION table representing the physical location of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the place of service of the care_site as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8154,28 +8164,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8185,214 +8195,214 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not necessary as it is not necessary to have the actual identity of the Provider. Rather, the idea is to uniquely and anonymously identify providers of care across the database.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 npi
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dea
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field either represents the most common specialty that occurs in the data or the most specific concept that represents all specialties listed, should the provider have more than one. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Specialty, there are two options: 1. Choose a concept_id which is a common ancestor to the multiple specialties, or, 2. Choose the specialty that occurs most often for the provider. Concepts in this field should be Standard with a domain of Provider. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Provider&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the CARE_SITE_ID for the location that the provider primarily practices in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Care Site, the main or most often exerted CARE_SITE_ID should be recorded.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the recorded gender of the provider in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If given, put a concept from the gender domain representing the recorded gender of the provider. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -8400,137 +8410,137 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 provider_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider identifier as it appears in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the kind of provider or specialty as it appears in the source data. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the kind of provider as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store physician speciality.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is provider’s gender as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider’s gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store provider gender.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8551,28 +8561,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8582,458 +8592,457 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
-Yes
+<td style="text-align:left;">
+No
 </td>
-<td style="text-align:left;width: 1in; ">
-PERSON
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person covered by the Plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 A single Person can have multiple, overlapping, PAYER_PLAN_PERIOD records
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Start date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 End date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the organization who reimburses the provider which administers care to the Person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Payer directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same payer, though the name of the Payer is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Payer&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Payer as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Payer in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the specific health benefit Plan the Person is enrolled in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the health benefit Plan of the Person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Plan in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the sponsor of the Plan who finances the Plan. This includes self-insured, small group health plan and large group health plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the sponsor directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same sponsor though the name of the sponsor is not necessary. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan sponsor as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the sponsor in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 family_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The common identifier for all people (often a family) that covered by the same policy.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Often these are the common digits of the enrollment id of the policy members.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the reason the Person left the Plan, if known.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the stop reason directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan stop reason as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the stop reason in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9054,28 +9063,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9085,557 +9094,557 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cost_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 DOMAIN
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 currency_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_charge
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_cost
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 total_paid
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_payer
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_patient
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_copay
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_coinsurance
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_patient_deductible
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_by_primary
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_ingredient_cost
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_dispensing_fee
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_allowed
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Revenue codes are a method to charge for a class of procedures and conditions in the U.S. hospital system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Diagnosis Related Groups are US codes used to classify hospital cases into one of approximately 500 groups.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(3)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9656,28 +9665,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9687,78 +9696,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -9766,103 +9775,103 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient, with at least 31 days since the previous exposure.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era End Date is the end date of the last Drug Exposure. The End Date of each Drug Exposure is either taken from the field drug_exposure_end_date or, as it is typically not available, inferred using the following rules: For pharmacy prescription data, the date when the drug was dispensed plus the number of days of supply are used to extrapolate the End Date for the Drug Exposure. Depending on the country-specific healthcare system, this supply information is either explicitly provided in the day_supply field or inferred from package size or similar information. For Procedure Drugs, usually the drug is administered on a single date (i.e., the administration date). A standard Persistence Window of 30 days (gap, slack) is permitted between two subsequent such extrapolated DRUG_EXPOSURE records to be considered to be merged into a single Drug Era.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gap_days
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Gap Days determine how many total drug-free days are observed between all Drug Exposure events that contribute to a DRUG_ERA record. It is assumed that the drugs are “not stockpiled” by the patient, i.e. that if a new drug prescription or refill is observed (a new DRUG_EXPOSURE record is written), the remaining supply from the previous events is abandoned. The difference between Persistence Window and Gap Days is that the former is the maximum drug-free time allowed between two subsequent DRUG_EXPOSURE records, while the latter is the sum of actual drug-free days for the given Drug Era under the above assumption of non-stockpiling.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9880,28 +9889,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9911,78 +9920,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 dose_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -9990,27 +9999,27 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the unit of the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -10018,78 +10027,78 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 dose_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value of the dosage of the drug_ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the Person started on the specific dosage, with at least 31 days since any prior exposure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The date the Person was no longer exposed to the dosage of the specific drug ingredient. An era is ended if there are 31 days or more between dosage records.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10111,28 +10120,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10142,78 +10151,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -10221,78 +10230,78 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_era_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_era_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of individual Condition Occurrences used to construct the condition era.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10310,28 +10319,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10341,81 +10350,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 episode_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Episode.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the episode is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose a concept in the Episode domain that best represents the ongoing disease phase, outcome, or treatment. Please see [article] for cancers and [article] for non-cancers describing how these are defined. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Episode&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Episode
 </td>
 </tr>
@@ -10423,188 +10432,188 @@ Episode
 <td style="text-align:left;font-weight: bold;">
 episode_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Episode beings.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Please see [article] for how to define an Episode start date.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date and time when the Episode begins.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the instance of the Episode is considered to have ended.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Please see [article] for how to define an Episode end date.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the instance of the Episode is considered to have ended.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_parent_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the Episode that subsumes the given Episode record. This is used in the case that an Episode are nested into each other.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple nested levels to how Episodes are represented, the EPISODE_PARENT_ID can be used to record this relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Please see [article] for the details of how to count episodes.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_object_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Standard Concept representing the disease phase, outcome, or other abstraction of which the episode consists. For example, if the EPISODE_CONCEPT_ID is <a href="https://athena.ohdsi.org/search-terms/terms/32531">treatment regimen</a> then the EPISODE_OBJECT_CONCEPT_ID should contain the chemotherapy regimen concept, like <a href="https://athena.ohdsi.org/search-terms/terms/35804392">Afatinib monotherapy</a>.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Episode entries from the ‘Disease Episode’ concept class should have an episode_object_concept_id that comes from the Condition domain. Episode entries from the ‘Treatment Episode’ concept class should have an episode_object_concept_id that scome from the ‘Procedure’ domain or ‘Regimen’ concept class.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Procedure, Regimen
 </td>
 </tr>
@@ -10612,28 +10621,28 @@ Procedure, Regimen
 <td style="text-align:left;font-weight: bold;">
 episode_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Episode record, as in whether the episode was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the EPISODE_TYPE_CONCEPT_ID that best represents the provenance of the record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>. A more detailed explanation of each Type Concept can be found on the <a href="https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT">vocabulary wiki</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -10641,54 +10650,54 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 episode_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source code for the Episdoe as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to a Episode Concept that refers to the code used in the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Given that the Episodes are user-defined it is unlikely that there will be a Source Concept available. If that is the case then set this field to zero.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10708,28 +10717,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10739,83 +10748,83 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 episode_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link the EPISODE_EVENT record to its EPISODE.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the EPISODE_ID that subsumes the EPISODE_EVENT record here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 EPISODE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is the primary key of the linked record in the database. For example, if the Episode Event is a Condition Occurrence, then the CONDITION_OCCURRENCE_ID of the linked record goes in this field.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 episode_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the EVENT_ID came from. <a href="https://athena.ohdsi.org/search-terms/terms?vocabulary=CDM&amp;conceptClass=Field&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Metadata
 </td>
 </tr>
@@ -10835,28 +10844,28 @@ Metadata
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10866,231 +10875,231 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 metadata_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a Metadata record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Attribute value is auto-generated
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the result of the Metadata, if applicable and available. It is not expected that all Metadata will have numeric results, rather, this field is here to house values should they exist.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11106,28 +11115,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11137,286 +11146,286 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cdm_source_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_source_abbreviation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The abbreviation of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(25)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_holder
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The holder of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The description of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_documentation_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_etl_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the link to the CDM version used.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release date of the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release data of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_version_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the version of the CDM.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 You can find all concepts that represent the CDM versions using the query: SELECT * FROM CONCEPT WHERE VOCABULARY_ID = ‘CDM’ AND CONCEPT_CLASS = ‘CDM’
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 You can find the version of your Vocabulary using the query: SELECT vocabulary_version from vocabulary where vocabulary_id = ‘None’
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11437,28 +11446,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11468,263 +11477,263 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Concept across all domains.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 An unambiguous, meaningful and descriptive name for the Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#domain">DOMAIN</a> table the Concept belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 DOMAIN
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#vocabulary">VOCABULARY</a> table indicating from which source the Concept has been adapted.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The attribute or concept class of the Concept. Examples are ‘Clinical Drug’, ‘Ingredient’, ‘Clinical Finding’ etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT_CLASS
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 standard_concept
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11740,28 +11749,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11771,131 +11780,131 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the vocabulary, for example, International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS) etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 External reference to documentation or available download of the about the vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Version of the Vocabulary as indicated in the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Vocabulary the VOCABULARY record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11911,28 +11920,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11942,79 +11951,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Domain, e.g. Condition, Procedure, Measurement etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept representing the Domain Concept the DOMAIN record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12030,28 +12039,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12061,79 +12070,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Concept Class, e.g. Clinical Finding, Ingredient, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Concept Class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12149,28 +12158,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12180,157 +12189,157 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The relationship between CONCEPT_ID_1 and CONCEPT_ID_2. Please see the <a href="https://ohdsi.github.io/CommonDataModel/dataModelConventions.html#concept_relationships">Vocabulary Conventions</a>. for more information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 RELATIONSHIP
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is invalidated.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Reason the relationship was invalidated. Possible values are ‘D’ (deleted), ‘U’ (updated) or NULL.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12346,28 +12355,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12377,156 +12386,156 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The type of relationship captured by the relationship record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 is_hierarchical
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Defines whether a relationship defines concepts into classes or hierarchies. Values are 1 for hierarchical relationship or 0 if not.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 defines_ancestry
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Defines whether a hierarchical relationship contributes to the concept_ancestor table. These are subsets of the hierarchical relationships. Valid values are 1 or 0.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 reverse_relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The identifier for the relationship used to define the reverse relationship between two concepts.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key that refers to an identifier in the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#concept">CONCEPT</a> table for the unique relationship concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12542,28 +12551,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12573,77 +12582,77 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_synonym_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12660,28 +12669,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12691,106 +12700,106 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 ancestor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the higher-level concept that forms the ancestor in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 descendant_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the lower-level concept that forms the descendant in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 min_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 max_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12806,28 +12815,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12837,238 +12846,238 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 source_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source code being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the Source Concept that is being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_code_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The target Concept to which the source code is being mapped.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Vocabulary of the target Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the mapping instance was first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -13084,28 +13093,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -13115,318 +13124,318 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Branded Drug or Clinical Drug Product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ingredient_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Combination Drugs will have more than one record in this table, one for each active Ingredient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value or the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The concentration of the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the denominator unit for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 box_size
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when then Concept became invalid.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -13444,28 +13453,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -13475,100 +13484,100 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 subject_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -13584,28 +13593,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -13615,184 +13624,184 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier given to the cohort, usually by the ATLAS application
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A short description of the cohort
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A complete description of the cohort.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 definition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Type defining what kind of Cohort Definition the record represents and how the syntax may be executed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_syntax
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Syntax or code to operationalize the Cohort Definition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 subject_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a Concept that represents the domain of the subjects that are members of the cohort (e.g., Person, Provider, Visit).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_initiation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A date to indicate when the Cohort was initiated in the COHORT table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
diff --git a/docs/cdm54Changes.html b/docs/cdm54Changes.html
index 9c3e86a..33bcb80 100644
--- a/docs/cdm54Changes.html
+++ b/docs/cdm54Changes.html
@@ -13,7 +13,7 @@
 
 <title>Changes by Table</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdm60.html b/docs/cdm60.html
index d4ab48e..2246922 100644
--- a/docs/cdm60.html
+++ b/docs/cdm60.html
@@ -13,7 +13,7 @@
 
 <title>OMOP CDM v6.0</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -516,28 +526,28 @@ div.tocify {
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -547,55 +557,55 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every person with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Any person linkage that needs to occur to uniquely identify Persons ought to be done prior to writing this table. This identifier can be the original id from the source data provided if it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is meant to capture the biological sex at birth of the Person. This field should not be used to study gender identity issues.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the gender or sex value present in the data under the assumption that it is the biological sex at birth. If the source data captures gender identity it should be stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#observation">OBSERVATION</a> table. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted gender concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -603,158 +613,158 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Compute age using year_of_birth.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources with date of birth, the year should be extracted. For data sources where the year of birth is not available, the approximate year of birth could be derived based on age group categorization, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 month_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the month should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 day_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For data sources that provide the precise date of birth, the day should be extracted and stored in this field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 birth_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not required but highly encouraged. For data sources that provide the precise datetime of birth, that value should be stored in this field. If birth_datetime is not provided in the source, use the following logic to infer the date: If day_of_birth is null and month_of_birth is not null then use the first of the month in that year. If month_of_birth is null or if day_of_birth AND month_of_birth are both null and the person has records during their year of birth then use the date of the earliest record, otherwise use the 15th of June of that year. If time of birth is not given use midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 death_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is the death date to be used in analysis, as determined by the ETL logic. Any additional information about a Person’s death is stored in the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#observation">OBSERVATION</a> table with the concept_id <a href="https://athena.ohdsi.org/search-terms/terms/4306655">4306655</a> or in the CONDITION_OCCURRENCE .
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple dates of death given for a Person, choose the one that is deemed most reliable. This may be a discharge from the hospital where the Person is listed as deceased or it could be latest death date provided. If a patient has clinical activity more than 60 days after the death date given in the source, it is a viable option to drop the death record as it may have been falsely reported. Similarly, if the death record is from a reputable source (e.g. government provided information) it is also a viable option to remove event records that occur in the data &gt; 60 days after death.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures race or ethnic background of the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have information about race or ethnic background. The Vocabulary contains Concepts about the main races and ethnic backgrounds in a hierarchical system. Due to the imprecise nature of human races and ethnic backgrounds, this is not a perfect system. Mixed races are not supported. If a clear race or ethnic background cannot be established, use Concept_Id 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Race&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Race Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Race
 </td>
 </tr>
@@ -762,28 +772,28 @@ Race
 <td style="text-align:left;font-weight: bold;">
 ethnicity_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field captures Ethnicity as defined by the Office of Management and Budget (OMB) of the US Government: it distinguishes only between “Hispanic” and “Not Hispanic”. Races and ethnic backgrounds are not stored here.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Only use this field if you have US-based data and a source of this information. Do not attempt to infer Ethnicity from the race or ethnic background of the Person. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Ethnicity&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted ethnicity concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Ethnicity
 </td>
 </tr>
@@ -791,275 +801,275 @@ Ethnicity
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location refers to the physical address of the person. This field should capture the last known location of the person. Any prior locations are captured in the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#location_history">LOCATION_HISTORY</a> table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the location_id from the LOCATION table here that represents the most granular location information for the person. This could represent anything from postal code or parts thereof, state, or county for example. Since many databases contain deidentified data, it is common that the precision of the location is reduced to prevent re-identification. This field should capture the last known location. Any prior locations are captured in the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#location_history">LOCATION_HISTORY</a> table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider refers to the last known primary care provider (General Practitioner).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider_id from the PROVIDER table of the last known general practitioner of the person. If there are multiple providers, it is up to the ETL to decide which to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Care Site refers to where the Provider typically provides the primary care.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to persons in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to persons in the source data. This field allows for the storing of the person value as it appears in the source. This field is not required but strongly recommended.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the biological sex of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the biological sex of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes biological sex in a non-standard vocabulary, store the concept_id here, otherwise set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the race of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the race of the person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 race_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes race in an OMOP supported vocabulary store the concept_id here, otherwise set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field is used to store the ethnicity of the person from the source data. It is not intended for use in standard analytics but for reference only.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the person has an ethnicity other than the OMB standard of “Hispanic” or “Not Hispanic” store that value from the source data here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ethnicity_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Due to the small number of options, this tends to be zero.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes ethnicity in an OMOP supported vocabulary, store the concept_id here, otherwise set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1079,28 +1089,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1110,136 +1120,136 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Person can have multiple discrete Observation Periods which are identified by the Observation_Period_Id.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign a unique observation_period_id to each discrete Observation Period for a Person.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person ID of the PERSON record for which the Observation Period is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the Observation Period
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_start_date can be inferred as the earliest Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer. If a Person switches plans but stays with the same payer, and therefore capturing of data continues, that change would be captured in <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#payer_plan_period">PAYER_PLAN_PERIOD</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the period for which we can assume that all events for a Person are recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is often the case that the idea of Observation Periods does not exist in source data. In those cases, the observation_period_end_date can be inferred as the last Event date available for the Person. In insurance claim data, the Observation Period can be considered as the time period the Person is enrolled with a payer.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 period_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation Period as in whether the period was determined from an insurance enrollment file, EHR healthcare encounters, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the observation_period_type_concept_id that best represents how the period was determined. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1274,28 +1284,28 @@ Type Concept
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1305,81 +1315,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a concept id representing the kind of visit, like inpatient or outpatient. All concepts in this field should be standard and belong to the Visit domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1387,134 +1397,134 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits, the start date is typically the admission date. For outpatient visits the start date and end date will be the same.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 When populating visit_start_date, you should think about the patient experience to make decisions on how to define visits. In the case of an inpatient visit this should be the date the patient was admitted to the hospital or institution. In all other cases this should be the date of the patient-provider interaction.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 For inpatient visits the end date is typically the discharge date.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Visit end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them: Outpatient Visit: visit_end_datetime = visit_start_datetime Emergency Room Visit: visit_end_datetime = visit_start_datetime Inpatient Visit: 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 Visits: Particularly for claims data, if end dates are not provided assume the visit is for the duration of month that it occurs. For Inpatient Visits ongoing at the date of ETL, put date of processing the data into visit_end_datetime and visit_type_concept_id with 32220 “Still patient” to identify the visit as incomplete. All other Visits: visit_end_datetime = visit_start_datetime. If this is a one-day visit the end date should match the start date.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit record, as in whether it came from an EHR record or billing claim.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -1522,138 +1532,138 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per visit record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). If there are multiple providers associated with a visit in the source, this can be reflected in the event tables (CONDITION_OCCURRENCE, PROCEDURE_OCCURRENCE, etc.) or in the VISIT_DETAIL table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple providers associated with a visit, you will need to choose which one to put here. The additional providers can be stored in the visit_detail table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the care site where the visit took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one care site associated with a visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is information about the kind of visit 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 source value, such as IP -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the visit source value is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If not available set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitted_from_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. If not available set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1661,54 +1671,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 admitted_from_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharge_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to determine where the patient was discharged to after a visit. 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the discharge_to_source_value to a standard concept in the visit domain. If not available set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1716,54 +1726,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 discharge_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit that occurred for the person prior to the given visit. There could be a few days or a few years in between.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The preceding_visit_id can be used to link a visit immediately preceding the current visit. Note this is not symmetrical, and there is no such thing as a “following_visit_id”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -1783,28 +1793,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -1814,81 +1824,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this to identify unique interactions between a person and the health care system. This identifier links across the other CDM event tables to associate events with a visit detail.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This should be populated by creating a unique identifier for each unique interaction between a person and the healthcare system where the person receives a medical good or service over a span of time.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -1896,134 +1906,134 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 When populating visit_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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the start date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This the end date of the patient-provider interaction.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Visit Detail end dates are mandatory. If end dates are not provided in the source there are three ways in which to derive them:&lt;br&gt; - 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.&lt;br&gt; 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given for the end date of a visit, set it to midnight (00:00:0000).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to understand the provenance of the visit detail record, or where the record comes from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Populate this field based on the provenance of the visit detail record, as in whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -2031,164 +2041,164 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There will only be one provider per <strong>visit</strong> record and the ETL document should clearly state how they were chosen (attending, admitting, etc.). This is a typical reason for leveraging the VISIT_DETAIL table as even though each VISIT_DETAIL record can only have one provider, there is no limit to the number of VISIT_DETAIL records that can be associated to a VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The additional providers associated to a Visit can be stored in this table where each VISIT_DETAIL record represents a different provider.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field provides information about the Care Site where the Visit Detail took place.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There should only be one Care Site associated with a Visit Detail.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the kind of visit detail that took place (inpatient, outpatient, emergency, etc.)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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 -&gt; ER-&gt; OP. This should line up with the logic chosen to determine how visits are created.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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. If not available, map to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitted_from_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 admitted_from_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the admitted_from_source_value to a standard concept in the visit domain. If not available, map to 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2196,54 +2206,54 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 discharge_to_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 discharge_to_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, map the DISCHARGE_TO_SOURCE_VALUE to a Standard Concept in the Visit domain. If not available, set to 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Visit
 </td>
 </tr>
@@ -2251,84 +2261,84 @@ Visit
 <td style="text-align:left;font-weight: bold;">
 preceding_visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 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”.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_parent_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to find the visit detail that subsumes the given visit detail record. This is used in the case that a visit detail record needs to be nested beyond the VISIT_OCCURRENCE/VISIT_DETAIL relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple nested levels to how Visits are represented in the source, the VISIT_DETAIL_PARENT_ID can be used to record this relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link the VISIT_DETAIL record to its VISIT_OCCURRENCE.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the VISIT_OCCURRENCE_ID that subsumes the VISIT_DETAIL record here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2348,28 +2358,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2379,82 +2389,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a condition record for a person. Refer to the ETL for how duplicate conditions during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a condition present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same condition within the same visit. It is valid to keep these duplicates and assign them individual, unique, CONDITION_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the condition is recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The CONDITION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the CONDITION_SOURCE_VALUE maps to. Only records whose source values map to concepts with a domain of “Condition” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -2462,134 +2472,134 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the end date of the condition
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Most often data sources do not have the idea of a start date for a condition. Rather, if a source only has one date associated with a condition record it is acceptable to use that date for both the CONDITION_START_DATE and the CONDITION_END_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Condition record, as in whether the condition was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the condition_type_concept_id that best represents the provenance of the record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -2597,221 +2607,221 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 condition_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This concept represents the point during the visit the diagnosis was given (admitting diagnosis, final diagnosis), whether the diagnosis was determined due to laboratory findings, if the diagnosis was exclusionary, or if it was a preliminary diagnosis, among others.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the Concept in the Condition Status domain that best represents the point during the visit when the diagnosis was given. These can include admitting diagnosis, principal diagnosis, and secondary diagnosis. If not available, set to 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Condition+Status&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Stop Reason indicates why a Condition is no longer valid with respect to the purpose within the source data. Note that a Stop Reason does not necessarily imply that the condition is no longer occurring.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with condition record, e.g. the provider who made the diagnosis or the provider who recorded the symptom.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the condition occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a CONDITION_START_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the CONDITION_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the condition occurred. For example, if the person was in the ICU at the time of the diagnosis the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the condition source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Condition necessary for a given analytic use case. Consider using CONDITION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the CONDITION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the condition status.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a diagnosis was given to a patient. This source value is mapped to a standard concept which is stored in the CONDITION_STATUS_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -2831,28 +2841,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -2862,82 +2872,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records of drug dispensings or administrations for a person. Refer to the ETL for how duplicate drugs during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a drug dispensing or administration present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same drug within the same visit. It is valid to keep these duplicates and assign them individual, unique, DRUG_EXPOSURE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the drug dispensing or administration is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a drug product or molecule otherwise introduced to the body. The drug concepts can have a varying degree of information about drug strength and dose. This information is relevant in the context of quantity and administration information in the subsequent fields plus strength information from the DRUG_STRENGTH table, provided as part of the standard vocabulary download.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DRUG_SOURCE_VALUE maps to. The concept id should be derived either from mapping from the source concept id or by picking the drug concept representing the most amount of detail you have. Records whose source values map to standard concepts with a domain of Drug should go in this table. When the Drug Source Value of the code cannot be translated into Standard Drug Concept IDs, a Drug exposure entry is stored with only the corresponding SOURCE_CONCEPT_ID and DRUG_SOURCE_VALUE and a DRUG_CONCEPT_ID of 0. The Drug Concept with the most detailed content of information is preferred during the mapping process. These are indicated in the CONCEPT_CLASS_ID field of the Concept and are recorded in the following order of precedence: ‘Branded Pack’, ‘Clinical Pack’, ‘Branded Drug’, ‘Clinical Drug’, ‘Branded Drug Component’, ‘Clinical Drug Component’, ‘Branded Drug Form’, ‘Clinical Drug Form’, and only if no other information is available ‘Ingredient’. Note: If only the drug class is known, the DRUG_CONCEPT_ID field should contain 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Drug&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -2945,161 +2955,161 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the drug record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a prescription, the date a prescription was filled, or the date on which a Drug administration was recorded. It is a valid ETL choice to use the date the drug was ordered as the DRUG_EXPOSURE_START_DATE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DRUG_EXPOSURE_END_DATE denotes the day the drug exposure ended for the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If this information is not explicitly available in the data, infer the end date using the following methods:/n/n 1. Start first with duration or days supply using the calculation drug start date + days supply -1 day. 2. Use quantity divided by daily dose that you may obtain from the sig or a source field (or assumed daily dose of 1) for solid, indivisibile, drug products. If quantity represents ingredient amount, quantity divided by daily dose * concentration (from drug_strength) drug concept id tells you the dose form. 3. If it is an administration record, set drug end date equal to drug start date. If the record is a written prescription then set end date to start date + 29. If the record is a mail-order prescription set end date to start date + 89. The end date must be equal to or greater than the start date. Ibuprofen 20mg/mL oral solution concept tells us this is oral solution. Calculate duration as quantity (200 example) * daily dose (5mL) /concentration (20mg/mL) 200*5/20 = 50 days. <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">Examples by dose form</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 verbatim_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the end date of the drug exposure as it appears in the source data, if it is given
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to delineate between prescriptions written vs. prescriptions dispensed vs. medication history vs. patient-reported exposure, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3107,159 +3117,159 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 stop_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The reason a person stopped a medication as it is represented in the source. Reasons include regimen completed, changed, removed, etc. This field will be retired in v6.0.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information is often not populated in source data and it is a valid etl choice to leave it blank if the information does not exist.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 refills
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is only filled in when the record is coming from a prescription written this field is meant to represent intended refills at time of the prescription.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To find the dose form of a drug the RELATIONSHIP table can be used where the relationship_id is ‘Has dose form’. If liquid, quantity stands for the total amount dispensed or ordered of ingredient in the units given by the drug_strength table. If the unit from the source data does not align with the unit in the DRUG_STRENGTH table the quantity should be converted to the correct unit given in DRUG_STRENGTH. For clinical drugs with fixed dose forms (tablets etc.) the quantity is the number of units/tablets/capsules prescribed or dispensed (can be partial, but then only 1/2 or 1/3, not 0.01). Clinical drugs with divisible dose forms (injections) the quantity is the amount of ingredient the patient got. For example, if the injection is 2mg/mL but the patient got 80mL then quantity is reported as 160. Quantified clinical drugs with divisible dose forms (prefilled syringes), the quantity is the amount of ingredient similar to clinical drugs. Please see <a href="https://ohdsi.github.io/CommonDataModel/drug_dose.html">how to calculate drug dose</a> for more information.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 days_supply
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Days supply of the drug. This should be the verbatim days_supply as given on the prescription. If the drug is physician administered use duration end date if given or set to 1 as default if duration is not available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sig
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the verbatim instruction for the drug as written by the provider.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the written out instructions for the drug as it is verbatim in the source, if available.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the ROUTE_SOURCE_VALUE maps to in the route domain.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Route
 </td>
 </tr>
@@ -3267,218 +3277,218 @@ Route
 <td style="text-align:left;font-weight: bold;">
 lot_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with drug record, e.g. the provider who wrote the prescription or the provider who administered the drug.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the ordering vs administering physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the drug was prescribed, administered or dispensed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field drug exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the drug exposure occurred. For example, if the person was in the ICU at the time of the drug administration the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Drug Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the drug source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Drug necessary for a given analytic use case. Consider using DRUG_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DRUG_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If unavailable, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 route_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the drug route.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating when and how a drug was given to a patient. This source value is mapped to a standard concept which is stored in the ROUTE_CONCEPT_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the dose unit of the drug given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This information may be called something different in the source data but the field is meant to contain a value indicating the unit of dosage of drug given to the patient. This is an older column and will be deprecated in an upcoming version.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -3498,28 +3508,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -3529,82 +3539,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 procedure_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a procedure record for a person. Refer to the ETL for how duplicate procedures during the same visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a procedure occurrence in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same procedure within the same visit. It is valid to keep these duplicates and assign them individual, unique, PROCEDURE_OCCURRENCE_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the procedure is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PROCEDURE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source value which represents a procedure
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the PROCEDURE_SOURCE_VALUE maps to. Only records whose source values map to standard concepts with a domain of “Procedure” should go in this table. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Procedure&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Procedure
 </td>
 </tr>
@@ -3612,81 +3622,81 @@ Procedure
 <td style="text-align:left;font-weight: bold;">
 procedure_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date the procedure occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Procedure record, as in whether the procedure was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the PROCEDURE_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. If a procedure is recorded as an EHR encounter, the PROCEDURE_TYPE_CONCEPT would be ‘EHR encounter record’. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -3694,220 +3704,220 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 modifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The modifiers are intended to give additional information about the procedure but as of now the vocabulary is under review.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 It is up to the ETL to choose how to map modifiers if they exist in source data. These concepts are typically distinguished by ‘Modifier’ concept classes (e.g., ‘CPT4 Modifier’ as part of the ‘CPT4’ vocabulary). If there is more than one modifier on a record, one should be chosen that pertains to the procedure rather than provider. If not available, set to 0. <a href="https://athena.ohdsi.org/search-terms/terms?conceptClass=CPT4+Modifier&amp;conceptClass=HCPCS+Modifier&amp;vocabulary=CPT4&amp;vocabulary=HCPCS&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the quantity value is omitted, a single procedure is assumed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Procedure has a quantity of ‘0’ in the source, this should default to ‘1’ in the ETL. If there is a record in the source it can be assumed the exposure occurred at least once
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the procedure record, e.g. the provider who performed the Procedure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record, for example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the procedure occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a PROCEDURE_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the Visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the PROCEDURE_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Procedure occurred. For example, if the Person was in the ICU at the time of the Procedure the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the procedure that occurred. For example, this could be an CPT4 or OPCS4 code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use this value to look up the source concept id and then map the source concept id to a standard concept id.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 procedure_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the procedure source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Procedure necessary for a given analytic use case. Consider using PROCEDURE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the PROCEDURE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 modifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The original modifier code from the source is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -3927,28 +3937,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -3958,81 +3968,81 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 device_exposure_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to records a person’s exposure to a foreign physical object or instrument.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an exposure to a foreign object or device present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies. This is the standard concept mapped from the source concept id which represents a foreign object or instrument the person was exposed to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the DEVICE_SOURCE_VALUE maps to.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Device
 </td>
 </tr>
@@ -4040,134 +4050,134 @@ Device
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the start date of the device record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Valid entries include a start date of a procedure to implant a device, the date of a prescription for a device, or the date of device administration.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The DEVICE_EXPOSURE_END_DATE denotes the day the device exposure ended for the patient, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the end date or discontinuation date as it appears from the source data or leave blank if unavailable.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_exposure_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 You can use the TYPE_CONCEPT_ID to denote the provenance of the record, as in whether the record is from administrative claims or EHR. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the drug_type_concept_id that best represents the provenance of the record, for example whether it came from a record of a prescription written or physician administered drug.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4175,191 +4185,191 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 unique_device_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Unique Device Identification number for devices regulated by the FDA, if given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For medical devices that are regulated by the FDA, a Unique Device Identification (UDI) is provided if available in the data source and is recorded in the UNIQUE_DEVICE_ID field.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider associated with device record, e.g. the provider who wrote the prescription or the provider who implanted the device.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the device was prescribed or given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 To populate this field device exposures must be explicitly initiated in the visit detail record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the device exposure that occurred. For example, this could be an NDC or Gemscript code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Device Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 device_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the device source value and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Device necessary for a given analytic use case. Consider using DEVICE_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the DEVICE_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If unavailable, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4379,28 +4389,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -4410,82 +4420,82 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 measurement_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a Measurement record for a Person. Refer to the ETL for how duplicate Measurements during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a measurement present in the source data should be assigned this unique key. In some cases, a person can have multiple records of the same measurement within the same visit. It is valid to keep these duplicates and assign them individual, unique, MEASUREMENT_IDs, though it is up to the ETL how they should be handled.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the PERSON for whom the measurement is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The MEASUREMENT_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the MEASUREMENT_SOURCE_CONCEPT_ID maps to. Only records whose SOURCE_CONCEPT_IDs map to Standard Concepts with a domain of “Measurement” should go in this table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Measurement
 </td>
 </tr>
@@ -4493,107 +4503,107 @@ Measurement
 <td style="text-align:left;font-weight: bold;">
 measurement_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this date to determine the date of the measurement.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there are multiple dates in the source data associated with a record such as order_date, draw_date, and result_date, choose the one that is closest to the date the sample was drawn from the patient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is not required, though it is in v6. If a source does not specify datetime the convention is to set the time to midnight (00:00:0000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_time
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is present for backwards compatibility and will be deprecated in an upcoming version.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Measurement record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the MEASUREMENT_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -4601,111 +4611,111 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 operator_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The meaning of Concept <a href="https://athena.ohdsi.org/search-terms/terms/4172703">4172703</a> for ‘=’ is identical to omission of a OPERATOR_CONCEPT_ID value. Since the use of this field is rare, it’s important when devising analyses to not to forget testing for the content of this field for values different from =.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Operators are &lt;, &lt;=, =, &gt;=, &gt; and these concepts belong to the ‘Meas Value Operator’ domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Measurement, if available. Note that measurements such as blood pressures will be split into their component parts i.e. one record for systolic, one record for diastolic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If there is a negative value coming from the source, set the VALUE_AS_NUMBER to NULL, with the exception of the following Measurements (listed as LOINC codes):&lt;br&gt;- <a href="https://athena.ohdsi.org/search-terms/terms/3003396">1925-7</a> Base excess in Arterial blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3002032">1927-3</a> Base excess in Venous blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3006277">8632-2</a> QRS-Axis - <a href="https://athena.ohdsi.org/search-terms/terms/3012501">11555-0</a> Base excess in Blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3003129">1926-5</a> Base excess in Capillary blood by calculation - <a href="https://athena.ohdsi.org/search-terms/terms/3004959">28638-5</a> Base excess in Arterial cord blood by calculation <a href="https://athena.ohdsi.org/search-terms/terms/3007435">28639-3</a> Base excess in Venous cord blood by calculation
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts in the ‘Meas Value’ domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the raw data provides categorial results as well as continuous results for measurements, it is a valid ETL choice to preserve both values. The continuous value should go in the VALUE_AS_NUMBER field and the categorical value should be mapped to a standard concept in the ‘Meas Value’ domain and put in the VALUE_AS_CONCEPT_ID field. This is also the destination for the ‘Maps to value’ relationship.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual measurements, i.e. it is not mandatory to represent Hemoglobin a1C measurements as a percentage. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with MEASUREMENT_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -4713,247 +4723,247 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 range_low
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 range_high
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Ranges have the same unit as the VALUE_AS_NUMBER. These ranges are provided by the source and should remain NULL if not given.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If reference ranges for upper and lower limit of normal as provided (typically by a laboratory) these are stored in the RANGE_HIGH and RANGE_LOW fields. This should be set to NULL if not provided.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with measurement record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Measurement occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If a MEASUREMENT_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the measurement record. If a measurement is related to a visit explicitly in the source data, it is possible that the result date of the Measurement falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Measurement occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Measurement that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Measurement Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 measurement_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the MEASUREMENT_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Measurement necessary for a given analytic use case. Consider using MEASUREMENT_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the MEASUREMENT_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Measurement that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim result value of the Measurement from the source data .
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If both a continuous and categorical result are given in the source data such that both VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are both included, store the verbatim value that was mapped to VALUE_AS_CONCEPT_ID here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -4973,28 +4983,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5004,163 +5014,163 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 observation_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to an Observation record for a Person. Refer to the ETL for how duplicate Observations during the same Visit were handled.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of an observation present in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The PERSON_ID of the Person for whom the Observation is recorded. This may be a system generated code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The OBSERVATION_CONCEPT_ID field is recommended for primary use in analyses, and must be used for network studies.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The CONCEPT_ID that the OBSERVATION_SOURCE_CONCEPT_ID maps to. There is no specified domain that the Concepts in this table must adhere to. The only rule is that records with Concepts in the Condition, Procedure, Drug, Measurement, or Device domains MUST go to the corresponding table.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the Observation. Depending on what the Observation represents this could be the date of a lab test, the date of a survey, or the date a patient’s family history was taken.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For some observations the ETL may need to make a choice as to which date to choose.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time is given set to midnight (00:00:00).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field can be used to determine the provenance of the Observation record, as in whether the measurement was from an EHR system, insurance claim, registry, or other sources.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the OBSERVATION_TYPE_CONCEPT_ID that best represents the provenance of the record, for example whether it came from an EHR record or billing claim. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5168,136 +5178,136 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 value_as_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the numerical value of the Result of the Observation, if applicable and available. It is not expected that all Observations will have numeric results, rather, this field is here to house values should they exist.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the categorical value of the Result of the Observation, if applicable and available.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(60)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is possible that some records destined for the Observation table have two clinical ideas represented in one source code. This is common with ICD10 codes that describe a family history of some Condition, for example. In OMOP the Vocabulary breaks these two clinical ideas into two codes; one becomes the OBSERVATION_CONCEPT_ID and the other becomes the VALUE_AS_CONCEPT_ID. It is important when using the Observation table to keep this possibility in mind and to examine the VALUE_AS_CONCEPT_ID field for relevant information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Note that the value of VALUE_AS_CONCEPT_ID may be provided through mapping from a source Concept which contains the content of the Observation. In those situations, the CONCEPT_RELATIONSHIP table in addition to the ‘Maps to’ record contains a second record with the relationship_id set to ‘Maps to value’. For example, ICD10 <a href="https://athena.ohdsi.org/search-terms/terms/45581076">Z82.4</a> ‘Family history of ischaemic heart disease and other diseases of the circulatory system’ has a ‘Maps to’ relationship to <a href="https://athena.ohdsi.org/search-terms/terms/4167217">4167217</a> ‘Family history of clinical finding’ as well as a ‘Maps to value’ record to <a href="https://athena.ohdsi.org/search-terms/terms/134057">134057</a> ‘Disorder of cardiovascular system’.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains all attributes specifying the clinical fact further, such as as degrees, severities, drug-drug interaction alerts etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use your best judgement as to what Concepts to use here and if they are necessary to accurately represent the clinical record. There is no restriction on the domain of these Concepts, they just need to be Standard.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 There is currently no recommended unit for individual observation concepts. UNIT_SOURCE_VALUES should be mapped to a Standard Concept in the Unit domain that best represents the unit as given in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no standardization requirement for units associated with OBSERVATION_CONCEPT_IDs, however, it is the responsibility of the ETL to choose the most plausible unit.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -5305,274 +5315,274 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provider associated with the observation record, e.g. the provider who ordered the test or the provider who recorded the result.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which PROVIDER_ID to put here. Based on what is available this may or may not be different than the provider associated with the overall VISIT_OCCURRENCE record. For example the admitting vs attending physician on an EHR record.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The visit during which the Observation occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Depending on the structure of the source data, this may have to be determined based on dates. If an OBSERVATION_DATE occurs within the start and end date of a Visit it is a valid ETL choice to choose the VISIT_OCCURRENCE_ID from the visit that subsumes it, even if not explicitly stated in the data. While not required, an attempt should be made to locate the VISIT_OCCURRENCE_ID of the observation record. If an observation is related to a visit explicitly in the source data, it is possible that the result date of the Observation falls outside of the bounds of the Visit dates.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The VISIT_DETAIL record during which the Observation occurred. For example, if the Person was in the ICU at the time the VISIT_OCCURRENCE record would reflect the overall hospital stay and the VISIT_DETAIL record would reflect the ICU stay during the hospital visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Same rules apply as for the VISIT_OCCURRENCE_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the Observation that occurred. For example, this could be an ICD10 or Read code.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the concept representing the OBSERVATION_SOURCE_VALUE and may not necessarily be standard. This field is discouraged from use in analysis because it is not required to contain Standard Concepts that are used across the OHDSI community, and should only be used when Standard Concepts do not adequately represent the source detail for the Observation necessary for a given analytic use case. Consider using OBSERVATION_CONCEPT_ID instead to enable standardized analytics that can be consistent across the network.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the OBSERVATION_SOURCE_VALUE is coded in the source data using an OMOP supported vocabulary put the concept id representing the source value here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the unit of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 qualifier_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field houses the verbatim value from the source data representing the qualifier of the Observation that occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 observation_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Observation record is related to another record in the database, this field is the primary key of the linked record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record, if applicable, here. See the <a href="https://ohdsi.github.io/CommonDataModel/cdm60.html#observation">ETL Conventions for the OBSERVATION</a> table for more details.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 obs_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Observation record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the OBSERVATION_EVENT_ID came from.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is possible that some Observation records might store a result as a date value.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -5598,28 +5608,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -5629,183 +5639,183 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the note was recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If time is not given set the time to midnight.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The provenance of the note. Most likely this will be EHR.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source system of the note, as in EHR record. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -5813,244 +5823,244 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 note_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Standard Concept Id representing the HL7 LOINC Document Type Vocabulary classification of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the note classification to a Standard Concept. For more information see the ETL Conventions in the description of the NOTE table. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;conceptClass=Doc+Kind&amp;conceptClass=Doc+Role&amp;conceptClass=Doc+Setting&amp;conceptClass=Doc+Subject+Matter&amp;conceptClass=Doc+Type+of+Service&amp;domain=Meas+Value&amp;page=1&amp;pageSize=15&amp;query=">AcceptedConcepts</a>. This Concept can alternatively be represented by concepts with the relationship ‘Kind of (LOINC)’ to <a href="https://athena.ohdsi.org/search-terms/terms/706391">706391</a> (Note).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_title
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The title of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_text
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The content of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 encoding_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Concept representing the character encoding type.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the Concept Id that represents the encoding character type here. Currently the only option is UTF-8 (<a href="https://athena.ohdsi.org/search-terms/terms/32678">32678</a>). It the note is encoded in any other type, like ASCII then put 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The language of the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use Concepts that are descendants of the concept <a href="https://athena.ohdsi.org/search-terms/terms/4182347">4182347</a> (World Languages).
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Provider who wrote the note.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a determination on which provider to put here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_detail_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit Detail during which the note was written.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_DETAIL
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The source value mapped to the NOTE_CLASS_CONCEPT_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6066,28 +6076,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6097,365 +6107,365 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 note_nlp_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for the NLP record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the NOTE_ID for the NOTE record the NLP record is associated to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 section_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The SECTION_CONCEPT_ID should be used to represent the note section contained in the NOTE_NLP record. These concepts can be found as parts of document panels and are based on the type of note written, i.e. a discharge summary. These panels can be found as concepts with the relationship ‘Subsumes’ to CONCEPT_ID <a href="https://athena.ohdsi.org/search-terms/terms/45875957">45875957</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 snippet
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A small window of text surrounding the term
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 "offset"
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Character offset of the extracted term in the input note
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 lexical_variant
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Raw text extracted from the NLP tool.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 note_nlp_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_system
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Name and version of the NLP system that extracted the term. Useful for data provenance.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 nlp_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date and time of the note processing.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_exists
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_exists is defined as a flag that indicates if the patient actually has or had the condition. Any of the following modifiers would make Term_exists false: Negation = true Subject = [anything other than the patient] Conditional = true/li&gt; Rule_out = true Uncertain = very low certainty or any lower certainties A complete lack of modifiers would make Term_exists true.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_temporal
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Term_temporal is to indicate if a condition is present or just in the past. The following would be past:&lt;br&gt;&lt;br&gt; - History = true - Concept_date = anything before the time of the report
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 term_modifiers
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For the modifiers that are there, they would have to have these values:&lt;br&gt;&lt;br&gt; - Negation = false - Subject = patient - Conditional = false - Rule_out = false - Uncertain = true or high or moderate or even low (could argue about low). Term_modifiers will concatenate all modifiers for different types of entities (conditions, drugs, labs etc) into one string. Lab values will be saved as one of the modifiers.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6473,28 +6483,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6504,107 +6514,107 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 specimen_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Unique identifier for each specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The person from whom the specimen is collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The standard CONCEPT_ID that the SPECIMEN_SOURCE_VALUE maps to in the specimen domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Specimen&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the source of the specimen record, as in an EHR system. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Type+Concept&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -6612,287 +6622,287 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 specimen_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the specimen was collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 quantity
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of specimen collected from the person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unit for the quantity of the specimen.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the UNIT_SOURCE_VALUE to a Standard Concept in the Unit domain. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Unit&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen is from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the ANATOMIC_SITE_SOURCE_VALUE to a Standard Concept in the Spec Anatomic Site domain. This should be coded at the lowest level of granularity <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Spec+Anatomic+Site&amp;conceptClass=Body+Structure&amp;page=4&amp;pageSize=15&amp;query=">Accepted Concepts</a>
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier for the specimen from the source system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specimen_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 unit_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This unit for the quantity of the specimen, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 anatomic_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is the site on the body where the specimen was taken from, as represented in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 disease_status_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -6910,28 +6920,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -6941,128 +6951,128 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 fact_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7082,28 +7092,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7113,641 +7123,641 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 survey_conduct_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Unique identifier for each completed survey.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 For each instance of a survey completion create a unique identifier.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Concept that represents the survey that was completed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies the survey that the Person completed. There is no specified domain for this table but the concept class ‘staging/scales’ contains many common surveys. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;conceptClass=Staging+%2F+Scales&amp;page=5&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Date on which the survey was started.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time given, set to midnight.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Date on which the survey was completed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If no time given, set to midnight.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Provider associated with the survey completion.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The ETL may need to make a choice as to which Provider to put here. This could either be the provider that ordered the survey or the provider who observed the completion of the survey.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PROVIDER
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 assisted_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a Concept that represents whether the survey was completed with assistance or independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no specific domain or class for this field, just choose the one that best represents the value given in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 respondent_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a Concept that represents who actually recorded the answers to the survey. For example, this could be the patient or a research associate.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no specific domain or class for this field, just choose the one that best represents the value given in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 timing_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a Concept that represents the timing of the survey. For example this could be the 3-month follow-up appointment.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 There is no specific domain or class for this field, just choose the one that best represents the value given in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 collection_method_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This Concept represents how the responses were collected.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Use the concepts that have the relationship ‘Has Answer’ with the CONCEPT_ID <a href="https://athena.ohdsi.org/search-terms/terms/42529316">42529316</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 assisted_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Source value representing whether patient required assistance to complete the survey. Example: ‘Completed without assistance’, ‘Completed with assistance’.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 respondent_type_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Source code representing role of person who completed the survey.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(100)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 timing_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Text string representing the timing of the survey. Example: Baseline, 6-month follow-up.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(100)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 collection_method_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The collection method as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(100)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The survey name as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(100)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If unavailable, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_source_identifier
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Unique identifier for each completed survey in source system.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(100)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 validated_survey_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If unavailable, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 validated_survey_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Source value representing the validation status of the survey.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 survey_version_number
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Version number of the questionnaire or survey used.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which the Survey occurred.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 response_visit_occurrence_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Visit during which any treatment related to the Survey was carried out.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VISIT_OCCURRENCE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -7768,28 +7778,28 @@ VISIT_OCCURRENCE
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -7799,258 +7809,258 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The unique key given to a unique Location.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Each instance of a Location in the source data should be assigned this unique key.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the first line of the address.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 address_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the second line of the address
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 city
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 state
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(2)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 zip
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Zip codes are handled as strings of up to 9 characters length. For US addresses, these represent either a 3-digit abbreviated Zip code as provided by many sources for patient protection reasons, the full 5-digit Zip or the 9-digit (ZIP + 4) codes. Unless for specific reasons analytical methods should expect and utilize only the first 3 digits. For international addresses, different rules apply.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(9)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 county
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the verbatim value for the location here, as it shows up in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 latitude
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The geocoded latitude.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 longitude
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The geocoded longitude.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8066,28 +8076,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8097,159 +8107,159 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the LOCATION_ID for the LOCATION_HISTORY record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the relationship between the location and the entity (PERSON, PROVIDER, or CARE_SITE)
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Concepts in this field must be in the Location class. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;conceptClass=Location&amp;page=1&amp;pageSize=15&amp;query=&amp;boosts">Accepted Concepts</a>. If the DOMAIN_ID is CARE_SITE this should be 0 and when the domain is PROVIDER the value is <a href="https://athena.ohdsi.org/search-terms/terms/4121722">Office</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The domain of the entity that is related to the location. Either PERSON, PROVIDER, or CARE_SITE.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 entity_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The unique identifier for the entity. References either person_id, provider_id, or care_site_id, depending on domain_id.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the relationship started
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the relationship ended
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8267,28 +8277,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8298,159 +8308,159 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Assign an id to each unique combination of location_id and place_of_service_source_value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the care_site as it appears in the source data
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is a high-level way of characterizing a Care Site. Typically, however, Care Sites can provide care in multiple settings (inpatient, outpatient, etc.) and this granularity should be reflected in the visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Choose the concept in the visit domain that best represents the setting in which healthcare is provided in the Care Site. If most visits in a Care Site are Inpatient, then the place_of_service_concept_id should represent Inpatient. If information is present about a unique Care Site (e.g. Pharmacy) then a Care Site record should be created. If this information is not available then set to 0. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Visit&amp;standardConcept=Standard&amp;page=2&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 location_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The location_id from the LOCATION table representing the physical location of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 LOCATION
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The identifier of the care_site as it appears in the source data. This could be an identifier separate from the name of the care_site.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 place_of_service_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the place of service of the care_site as it appears in the source data.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8468,28 +8478,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8499,214 +8509,214 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 provider_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 It is assumed that every provider with a different unique identifier is in fact a different person and should be treated independently.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This identifier can be the original id from the source data provided it is an integer, otherwise it can be an autogenerated number.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 provider_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This field is not necessary as it is not necessary to have the actual identity of the Provider. Rather, the idea is to uniquely and anonymously identify providers of care across the database.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 npi
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the National Provider Number issued to health care providers in the US by the Centers for Medicare and Medicaid Services (CMS).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dea
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier issued by the DEA, a US federal agency, that allows a provider to write prescriptions for controlled substances.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field either represents the most common specialty that occurs in the data or the most specific concept that represents all specialties listed, should the provider have more than one. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Specialty, there are two options: 1. Choose a concept_id which is a common ancestor to the multiple specialties, or, 2. Choose the specialty that occurs most often for the provider. Concepts in this field should be Standard with a domain of Provider. If not available, set to 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Provider&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 care_site_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the CARE_SITE_ID for the location that the provider primarily practices in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If a Provider has more than one Care Site, the main or most often exerted CARE_SITE_ID should be recorded.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CARE_SITE
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 year_of_birth
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the recorded gender of the provider in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If given, put a concept from the gender domain representing the recorded gender of the provider. If not available, set to 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Gender&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Gender
 </td>
 </tr>
@@ -8714,137 +8724,137 @@ Gender
 <td style="text-align:left;font-weight: bold;">
 provider_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Use this field to link back to providers in the source data. This is typically used for error checking of ETL logic.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Some use cases require the ability to link back to providers in the source data. This field allows for the storing of the provider identifier as it appears in the source.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the kind of provider or specialty as it appears in the source data. This includes physician specialties such as internal medicine, emergency medicine, etc. and allied health professionals such as nurses, midwives, and pharmacists.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the kind of provider as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 specialty_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store physician speciality.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider specialty in an OMOP supported vocabulary store the concept_id here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is provider’s gender as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the provider’s gender as it appears in the source data. This field is up to the discretion of the ETL-er as to whether this should be the coded value from the source or the text description of the lookup value.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gender_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is often zero as many sites use proprietary codes to store provider gender.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes provider gender in an OMOP supported vocabulary store the concept_id here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -8865,28 +8875,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -8896,565 +8906,565 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each unique combination of a Person, Payer, Plan, and Period of time.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person covered by the Plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 A single Person can have multiple, overlapping, PAYER_PLAN_PERIOD records
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 contract_person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Person who is the primary subscriber/contract owner for Plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This may or may not be the same as the PERSON_ID. For example, if a mother has her son on her plan and the PAYER_PLAN_PERIOD record is the for son, the sons’s PERSON_ID would go in PAYER_PLAN_PERIOD.PERSON_ID and the mother’s PERSON_ID would go in PAYER_PLAN_PERIOD.CONTRACT_PERSON_ID.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Start date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 End date of Plan coverage.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the organization who reimburses the provider which administers care to the Person.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Payer directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same payer, though the name of the Payer is not necessary. If not available, set to 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Payer&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the Payer as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Payer in an OMOP supported vocabulary store the concept_id here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the specific health benefit Plan the Person is enrolled in.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the Plan directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same health benefit Plan though the name of the Plan is not necessary. If not available, set to 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the health benefit Plan of the Person as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 plan_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the Plan in an OMOP supported vocabulary store the concept_id here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 contract_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the relationship between the PERSON_ID and CONTRACT_PERSON_ID. It should be read as PERSON_ID is the <em>CONTRACT_CONCEPT_ID</em> of the CONTRACT_PERSON_ID. So if CONTRACT_CONCEPT_ID represents the relationship ‘Stepdaughter’ then the Person for whom PAYER_PLAN_PERIOD record was recorded is the stepdaughter of the CONTRACT_PERSON_ID.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If available, use this field to represent the relationship between the PERSON_ID and the CONTRACT_PERSON_ID. If the Person for whom the PAYER_PLAN_PERIOD record was recorded is the stepdaughter of the CONTRACT_PERSON_ID then CONTRACT_CONCEPT_ID would be <a href="https://athena.ohdsi.org/search-terms/terms/4330864">4330864</a>. If not available, set to 0. <a href="https://athena.ohdsi.org/search-terms/terms?standardConcept=Standard&amp;domain=Relationship&amp;page=12&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 contract_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the relationship of the PERSON_ID to CONTRACT_PERSON_ID as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 contract_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the relationship between the PERSON_ID and CONTRACT_PERSON_ID in an OMOP supported vocabulary store the concept_id here. If not available, set to 0.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the sponsor of the Plan who finances the Plan. This includes self-insured, small group health plan and large group health plan.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the sponsor directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. The point is to stratify on this information and identify if Persons have the same sponsor though the name of the sponsor is not necessary. If not available, set to 0. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Sponsor&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan sponsor as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 sponsor_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the sponsor in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 family_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The common identifier for all people (often a family) that covered by the same policy.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Often these are the common digits of the enrollment id of the policy members.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field represents the reason the Person left the Plan, if known.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Map the stop reason directly to a standard CONCEPT_ID. If one does not exists please contact the vocabulary team. There is no global controlled vocabulary available for this information. <a href="http://athena.ohdsi.org/search-terms/terms?domain=Plan+Stop+Reason&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Plan stop reason as it appears in the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 stop_reason_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 If the source data codes the stop reason in an OMOP supported vocabulary store the concept_id here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9475,28 +9485,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -9506,160 +9516,160 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cost_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each COST record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_event_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Cost record is related to another record in the database, this field is the primary key of the linked record.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the primary key of the linked record, if applicable, here.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_event_field_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 If the Cost record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the CONCEPT_ID that identifies which table and field the COST_EVENT_ID came from.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key that refers to a Standard Cost Concept identifier in the Standardized Vocabularies belonging to the ‘Cost’ vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key identifier to a concept in the CONCEPT table for the provenance or the source of the COST data and belonging to the ‘Type Concept’ vocabulary
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Type Concept
 </td>
 </tr>
@@ -9667,316 +9677,316 @@ Type Concept
 <td style="text-align:left;font-weight: bold;">
 cost_source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to a Cost Concept that refers to the code used in the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source value for the cost as it appears in the source data
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 currency_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key identifier to the concept representing the 3-letter code used to delineate international currencies, such as USD for US Dollar. These belong to the ‘Currency’ vocabulary
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cost
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The actual financial cost amount
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 incurred_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The first date of service of the clinical event corresponding to the cost as in table capturing the information (e.g. date of visit, date of procedure, date of condition, date of drug etc).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 billed_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date a bill was generated for a service or encounter
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 paid_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date payment was received for a service or encounter
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for Revenue codes belonging to the ‘Revenue Code’ vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key referring to a Standard Concept ID in the Standardized Vocabularies for DRG codes belonging to the ‘DRG’ vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 revenue_code_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source value for the Revenue code as it appears in the source data, stored here for reference.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drg_source_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source value for the 3-digit DRG source code as it appears in the source data, stored here for reference.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 payer_plan_period_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the PAYER_PLAN_PERIOD table, where the details of the Payer, Plan and Family are stored. Record the payer_plan_id that relates to the payer who contributed to the paid_by_payer field.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -9997,28 +10007,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10028,78 +10038,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -10107,103 +10117,103 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 drug_era_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era Start Date is the start date of the first Drug Exposure for a given ingredient, with at least 31 days since the previous exposure.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_era_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Drug Era End Date is the end date of the last Drug Exposure. The End Date of each Drug Exposure is either taken from the field drug_exposure_end_date or, as it is typically not available, inferred using the following rules: For pharmacy prescription data, the date when the drug was dispensed plus the number of days of supply are used to extrapolate the End Date for the Drug Exposure. Depending on the country-specific healthcare system, this supply information is either explicitly provided in the day_supply field or inferred from package size or similar information. For Procedure Drugs, usually the drug is administered on a single date (i.e., the administration date). A standard Persistence Window of 30 days (gap, slack) is permitted between two subsequent such extrapolated DRUG_EXPOSURE records to be considered to be merged into a single Drug Era.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_exposure_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 gap_days
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The Gap Days determine how many total drug-free days are observed between all Drug Exposure events that contribute to a DRUG_ERA record. It is assumed that the drugs are “not stockpiled” by the patient, i.e. that if a new drug prescription or refill is observed (a new DRUG_EXPOSURE record is written), the remaining supply from the previous events is abandoned. The difference between Persistence Window and Gap Days is that the former is the maximum drug-free time allowed between two subsequent DRUG_EXPOSURE records, while the latter is the sum of actual drug-free days for the given Drug Era under the above assumption of non-stockpiling.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10221,28 +10231,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10252,78 +10262,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 dose_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Drug
 </td>
 </tr>
@@ -10331,27 +10341,27 @@ Drug
 <td style="text-align:left;font-weight: bold;">
 unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the unit of the specific drug ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Unit
 </td>
 </tr>
@@ -10359,78 +10369,78 @@ Unit
 <td style="text-align:left;font-weight: bold;">
 dose_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value of the dosage of the drug_ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date the Person started on the specific dosage, with at least 31 days since any prior exposure.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 dose_era_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 The date the Person was no longer exposed to the dosage of the specific drug ingredient. An era is ended if there are 31 days or more between dosage records.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10452,28 +10462,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10483,78 +10493,78 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 condition_era_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 person_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 bigint
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 PERSON
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id representing the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Condition
 </td>
 </tr>
@@ -10562,78 +10572,78 @@ Condition
 <td style="text-align:left;font-weight: bold;">
 condition_era_start_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The start date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the start date of the very first chronologically recorded instance of the condition with at least 31 days since any prior record of the same Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_era_end_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The end date for the Condition Era constructed from the individual instances of Condition Occurrences. It is the end date of the final continuously recorded instance of the Condition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 condition_occurrence_count
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of individual Condition Occurrences used to construct the condition era.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10652,28 +10662,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10683,178 +10693,178 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 metadata_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_string
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(250)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 value_as_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 metadata_datetime
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 datetime
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -10870,28 +10880,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -10901,257 +10911,257 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cdm_source_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_source_abbreviation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The abbreviation of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(25)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_holder
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The holder of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The description of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_documentation_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_etl_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Put the link to the CDM version used.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release date of the source data.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_release_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The release data of the CDM instance.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cdm_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(10)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11172,28 +11182,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11203,263 +11213,263 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Concept across all domains.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 An unambiguous, meaningful and descriptive name for the Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#domain">DOMAIN</a> table the Concept belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 DOMAIN
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the <a href="https://ohdsi.github.io/CommonDataModel/cdm531.html#vocabulary">VOCABULARY</a> table indicating from which source the Concept has been adapted.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The attribute or concept class of the Concept. Examples are ‘Clinical Drug’, ‘Ingredient’, ‘Clinical Finding’ etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT_CLASS
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 standard_concept
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970, meaning, the Concept has no (known) date of inception.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11475,28 +11485,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11506,131 +11516,131 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique identifier for each Vocabulary, such as ICD9CM, SNOMED, Visit.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the vocabulary, for example International Classification of Diseases, Ninth Revision, Clinical Modification, Volume 1 and 2 (NCHS) etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_reference
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 External reference to documentation or available download of the about the vocabulary.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_version
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Version of the Vocabulary as indicated in the source.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 vocabulary_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Vocabulary the VOCABULARY record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11646,28 +11656,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11677,79 +11687,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 domain_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each domain.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Domain, e.g. Condition, Procedure, Measurement etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 domain_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept representing the Domain Concept the DOMAIN record belongs to.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11765,28 +11775,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11796,79 +11806,79 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_class_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A unique key for each class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The name describing the Concept Class, e.g. Clinical Finding, Ingredient, etc.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_class_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A Concept that represents the Concept Class.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -11884,28 +11894,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -11915,157 +11925,157 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id_1
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_id_2
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The relationship between CONCEPT_ID_1 and CONCEPT_ID_2. Please see the <a href="https://ohdsi.github.io/CommonDataModel/dataModelConventions.html#concept_relationships">Vocabulary Conventions</a>. for more information.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 RELATIONSHIP
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the relationship is invalidated.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Reason the relationship was invalidated. Possible values are ‘D’ (deleted), ‘U’ (updated) or NULL.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12081,28 +12091,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12112,151 +12122,151 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 is_hierarchical
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 defines_ancestry
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 reverse_relationship_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 relationship_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12272,28 +12282,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12303,77 +12313,77 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 concept_synonym_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1000)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 language_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12390,28 +12400,28 @@ CONCEPT
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12421,106 +12431,106 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 ancestor_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the higher-level concept that forms the ancestor in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 descendant_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept Id for the lower-level concept that forms the descendant in the relationship.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 min_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 max_levels_of_separation
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12536,28 +12546,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12567,238 +12577,238 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 source_code
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The source code being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(50)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the Source Concept that is being translated into a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 This is either 0 or should be a number above 2 billion, which are the Concepts reserved for site-specific codes and mappings.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A foreign key to the VOCABULARY table defining the vocabulary of the source code that is being translated to a Standard Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 source_code_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The target Concept to which the source code is being mapped.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 target_vocabulary_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Vocabulary of the target Concept.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(20)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 VOCABULARY
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the mapping instance was first recorded.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -12814,28 +12824,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -12845,318 +12855,318 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 drug_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Branded Drug or Clinical Drug Product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 ingredient_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 Combination Drugs will have more than one record in this table, one for each active Ingredient.
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The numeric value or the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 amount_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the amount of active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The concentration of the active ingredient contained within the drug product.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 numerator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the Unit of measure for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_value
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The amount of total liquid (or other divisible product, such as ointment, gel, spray, etc.).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 float
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 denominator_unit_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The Concept representing the denominator unit for the concentration of active ingredient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 box_size
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when the Concept was first recorded. The default value is 1-Jan-1970.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 valid_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 The date when then Concept became invalid.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 invalid_reason
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 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.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(1)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -13174,28 +13184,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -13205,100 +13215,100 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 subject_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_start_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_end_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
@@ -13314,28 +13324,28 @@ No
 <th style="text-align:left;">
 CDM Field
 </th>
-<th style="text-align:left;width: 3in; ">
+<th style="text-align:left;">
 User Guide
 </th>
-<th style="text-align:left;width: 4in; ">
+<th style="text-align:left;">
 ETL Conventions
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Datatype
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Required
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Primary Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 Foreign Key
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Table
 </th>
-<th style="text-align:left;width: 1in; ">
+<th style="text-align:left;">
 FK Domain
 </th>
 </tr>
@@ -13345,185 +13355,185 @@ FK Domain
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This is the identifier given to the cohort, usually by the ATLAS application
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 COHORT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_name
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A short description of the cohort
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(255)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_description
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A complete description of the cohort.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 definition_type_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Type defining what kind of Cohort Definition the record represents and how the syntax may be executed.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_definition_syntax
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 Syntax or code to operationalize the Cohort Definition.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 varchar(MAX)
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 subject_concept_id
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 This field contains a Concept that represents the domain of the subjects that are members of the cohort (e.g., Person, Provider, Visit).
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 integer
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 Yes
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 CONCEPT
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 <tr>
 <td style="text-align:left;font-weight: bold;">
 cohort_initiation_date
 </td>
-<td style="text-align:left;width: 3in; ">
+<td style="text-align:left;">
 A date to indicate when the Cohort was initiated in the COHORT table.
 </td>
-<td style="text-align:left;width: 4in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 date
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 No
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
-<td style="text-align:left;width: 1in; ">
+<td style="text-align:left;">
 </td>
 </tr>
 </tbody>
diff --git a/docs/cdmDecisionTree.html b/docs/cdmDecisionTree.html
new file mode 100644
index 0000000..9ca3f2e
--- /dev/null
+++ b/docs/cdmDecisionTree.html
@@ -0,0 +1,472 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>cdmDecisionTree.knit</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore"><div>
+<img src="ohdsi40x40.png"></img> CDM Request Decision Tree
+</div></h1>
+
+</div>
+
+
+<p>If you have arrived to this page then you must be thinking <strong>HELP! I have some data that doesn’t fit in the CDM!</strong> Never fear as this handy guide will point you in the right direction and all you have to do is answer a few questions.</p>
+<p><strong>First things first, do you think you will need to change the OMOP Common Data Model itself or are you solely looking for vocabulary support?</strong></p>
+<p><a href="networkUseCase.html">I think I need to change the OMOP CDM</a></p>
+<p><a href="vocabN.html">I need vocabulary support</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/cdmPrivacy.html b/docs/cdmPrivacy.html
index 971df68..9c05342 100644
--- a/docs/cdmPrivacy.html
+++ b/docs/cdmPrivacy.html
@@ -13,7 +13,7 @@
 
 <title>Preserving Privacy in an OMOP CDM Implementation</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdmRPackage.html b/docs/cdmRPackage.html
index e233fe7..5a6e930 100644
--- a/docs/cdmRPackage.html
+++ b/docs/cdmRPackage.html
@@ -13,7 +13,7 @@
 
 <title>CDM R Package Demo</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -60,6 +60,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -85,6 +86,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -236,7 +240,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -252,7 +256,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -272,7 +276,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -292,7 +296,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -310,7 +314,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -323,19 +327,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -345,7 +352,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -365,7 +372,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -373,6 +380,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/cdmRefreshProcess.html b/docs/cdmRefreshProcess.html
index cdf8a99..b437a9b 100644
--- a/docs/cdmRefreshProcess.html
+++ b/docs/cdmRefreshProcess.html
@@ -13,7 +13,7 @@
 
 <title>cdmRefreshProcess.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -485,21 +495,22 @@ div.tocify {
 
 
 <p>The OMOP Common Data Model is managed by the OHDSI CDM Working Group. The formal remit of the CDM Working Group (WG) is to hear proposals for change, ratifying only those with valid use cases and data to support them. Then, once ratified, these proposals are incorporated into the next version of the CDM. In the past, this was done by the WG alone. The group would invite others from around the community to present use cases for change and suggestions for improvement. The WG would then vote on the proposals and a new CDM version would be released after a certain period of time or if enough proposals were voted in. This approach worked when the community was smaller but as it is growing rapidly the CDM WG needed to adapt the refresh cycle such that everyone has an opportunity to weigh in on the proposed changes.</p>
+<p>Looking to make a change or addition to the OMOP CDM? Please answer the questions in the <a href="cdmDecisionTree.html">decision tree</a> to point you in the right direction.</p>
 <div id="cdm-refresh-cycle" class="section level2">
 <h2>CDM Refresh Cycle</h2>
 <p><img src="images/CDM_refresh_cycle.png" /></p>
-<div id="define-new-version-completed-for-v5.4" class="section level3">
-<h3>1. Define New Version [Completed for v5.4]</h3>
-<p>The image above describes the new CDM refresh cycle. It begins with <strong>defining a new version</strong>. This has been completed for the current cycle. Issues and proposals on the github were considered during a 4-hour workshop where it was decided the next CDM version will be CDM v5.4, building off of CDM v5.3. The group then participated in a rapid-fire voting activity to identify which changes should be incorporated into CDM v5.4. Any items that were not unanimously agreed upon were then discussed in small groups to hone the proposal and suggestions were presented back to the group. The final roadmap for CDM v5.4 can be found <a href="https://github.com/OHDSI/CommonDataModel/projects/3">here</a>.</p>
-<p>Looking to open a proposal to change or augment the CDM? Please open an <a href="https://github.com/OHDSI/CommonDataModel/issues">issue</a> and use the <strong>proposal template</strong>.</p>
+<div id="define-new-version" class="section level3">
+<h3>1. Define New Version</h3>
+<p>The image above describes the new CDM refresh cycle. It begins with <strong>defining a new version</strong>. Proposals are heard over the course of a year according to the <a href="cdmRequestProcess.html">CDM Request Process</a> and the ratified changes are added to the roadmap until such time that there are enough updates to warrant a new version of the model.</p>
+<p>Looking to open a proposal to change or augment the CDM? Please follow the questions in the <a href="cdmDecisionTree.html">decision tree</a> to help you determine what you will need.</p>
 </div>
-<div id="sign-off-from-work-groups-completed-for-v5.4" class="section level3">
-<h3>2. Sign off from Work Groups [Completed for v5.4]</h3>
+<div id="sign-off-from-work-groups" class="section level3">
+<h3>2. Sign off from Work Groups</h3>
 <p>Each member of the CDM WG is a liaison for another workgroup in the community. They are responsible for presenting the proposed changes to the CDM and collecting the feedback. This has resulted in very helpful suggestions from the EHR, Data Quality, Device, HADES, and ACHILLES groups. This outreach has proven to be very effective and should result in a very stable version.</p>
 </div>
 <div id="release-ddls" class="section level3">
 <h3>3. Release DDLs</h3>
-<p>After all changes and suggestions are agreed upon by the community and work groups the next step is to generate the DDLs. The CDM WG hosted a hackathon on August 18-19, 2021. During this time the group created an R package to automatically generate the DDLs and the code to instantiate an empty CDM instance. Changes were made to v5.3 to generate v5.4 and the repository was refactored.</p>
+<p>After all changes and suggestions are agreed upon by the community and work groups the next step is to generate the DDLs. For example, the CDM WG hosted a hackathon on August 18-19, 2021. During this time the group created an R package to automatically generate the DDLs and the code to instantiate an empty CDM instance. Changes were made to v5.3 to generate v5.4 and the repository was refactored.</p>
 </div>
 <div id="software-update" class="section level3">
 <h3>4. Software Update</h3>
@@ -513,7 +524,7 @@ div.tocify {
 <div id="cdm-wg-meeting-information" class="section level1">
 <h1>CDM WG Meeting Information</h1>
 <p>The CDM working group meets the first and third Tuesday of the month. See below for links to the meetings.</p>
-<p><strong>Every first Tuesday of the month at 1pm est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d">Teams Meeting</a></p>
+<p><strong>Every first Tuesday of the month at 10am est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d">Teams Meeting</a></p>
 <p><strong>Every third Tuesday of the month at 1pm est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1611000164347?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%223c193b7f-c2ab-4bcf-b88c-f89a6b1fba38%22%7d">Teams Meeting</a></p>
 <p><strong>Note</strong> These were recently changed from a Skype meeting to a Microsoft Teams meeting. If you do you have access to the OHDSI Teams Tenet, please contact Clair Blacketer at <a href="mailto:mblacke@its.jnj.com" class="email">mblacke@its.jnj.com</a>.</p>
 <div id="cdm-wg-important-links" class="section level3">
diff --git a/docs/cdmRequestProcess.html b/docs/cdmRequestProcess.html
new file mode 100644
index 0000000..e4d69a0
--- /dev/null
+++ b/docs/cdmRequestProcess.html
@@ -0,0 +1,665 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>cdmRequestProcess.knit</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/jqueryui-1.11.4/jquery-ui.min.js"></script>
+<link href="site_libs/tocify-1.9.1/jquery.tocify.css" rel="stylesheet" />
+<script src="site_libs/tocify-1.9.1/jquery.tocify.js"></script>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+<style type="text/css">
+
+#TOC {
+  margin: 25px 0px 20px 0px;
+}
+@media (max-width: 768px) {
+#TOC {
+  position: relative;
+  width: 100%;
+}
+}
+
+@media print {
+.toc-content {
+  /* see https://github.com/w3c/csswg-drafts/issues/4434 */
+  float: right;
+}
+}
+
+.toc-content {
+  padding-left: 30px;
+  padding-right: 40px;
+}
+
+div.main-container {
+  max-width: 1200px;
+}
+
+div.tocify {
+  width: 20%;
+  max-width: 260px;
+  max-height: 85%;
+}
+
+@media (min-width: 768px) and (max-width: 991px) {
+  div.tocify {
+    width: 25%;
+  }
+}
+
+@media (max-width: 767px) {
+  div.tocify {
+    width: 100%;
+    max-width: none;
+  }
+}
+
+.tocify ul, .tocify li {
+  line-height: 20px;
+}
+
+.tocify-subheader .tocify-item {
+  font-size: 0.90em;
+}
+
+.tocify .list-group-item {
+  border-radius: 0px;
+}
+
+
+</style>
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+<!-- setup 3col/9col grid for toc_float and main content  -->
+<div class="row">
+<div class="col-xs-12 col-sm-4 col-md-3">
+<div id="TOC" class="tocify">
+</div>
+</div>
+
+<div class="toc-content col-xs-12 col-sm-8 col-md-9">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore"><div>
+<img src="ohdsi40x40.png"></img> How to Request Changes to the CDM
+</div></h1>
+
+</div>
+
+
+<p>Are you in the right place? Please answer the questions in the <a href="cdmDecisionTree.html">decision tree</a> prior to beginning a CDM Request to make sure you aren’t missing something.</p>
+<p>As OHDSI is an open-source community working towards developing a Common Data Model that fulfills the needs of its users, it is often the case that changes need to be made to the model as the community and its research continues to mature. However, the number of people, institutions, and initiatives that rely on the OMOP CDM to advance the science of observational health has grown dramatically since its inception in 2015. Therefore, care must be taken when considering any update to the model, big or small. This document outlines the process that should be taken to ratify a change to the CDM.</p>
+<p><strong>If you would like guidance prior to starting this process, consider contacting us on our <a href="https://github.com/OHDSI/CommonDataModel">GitHub</a> or <a href="https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&amp;tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5">Teams Channel</a>.</strong></p>
+<div id="scope" class="section level3">
+<h3>Scope</h3>
+<ul>
+<li>What kind of changes?
+<ul>
+<li>Minor, e.g. new field in existing table</li>
+<li>Major, e.g. breaking changes, additional tables</li>
+</ul></li>
+<li>Who can propose changes?
+<ul>
+<li>Individuals, OHDSI working groups, organizations</li>
+</ul></li>
+</ul>
+</div>
+<div id="step-1-proposal" class="section level2">
+<h2>Step 1: Proposal</h2>
+<p>Once a group or organization has decided on the update they would like made to the model, they must produce a document including the following:</p>
+<ol style="list-style-type: decimal">
+<li>A clear description of the change or addition including the User Guide and ETL Conventions in the same structure as what is present on the website for every table and field currently in the CDM.</li>
+<li>A clearly defined use case noting why the latest version of the OMOP CDM fails to adequately address said use case. This should include describing what you have already tried with the latest version of the OMOP CDM and why it does not meet your needs.</li>
+<li>An example of how the requested change or addition will be used in practice. This can be in the form of sample data, SQL code, a diagram, or text. The proposal can optionally include suggestions as to how other OHDSI tools (Achilles, DataQualityDashboard, Atlas, etc.) should work with your change or addition.</li>
+</ol>
+<p>Once the document is ready to submit, please email <a href="mailto:a58abde7.ohdsi.org@amer.teams.ms">CDM Proposals - Workgroup - Common Data Model</a>. This will go directly to a separate channel in the OHDSI Teams environment that is available to all members of the CDM Working Group. After submitting your document with your proposal to email listed above, someone in the OMOP CDM Working Group will respond to you within 2 weeks. The potential outcomes are as follows:</p>
+<ul>
+<li>Proposal merits further review (move on to next steps)</li>
+<li>Proposal is not ready for workgroup review due to one or more factors
+<ul>
+<li>Incomplete</li>
+<li>Insufficiently aligned with the OMOP framework</li>
+<li>Poorly described use case</li>
+</ul></li>
+</ul>
+</div>
+<div id="step-2-initial-presentation" class="section level2">
+<h2>Step 2: Initial Presentation</h2>
+<p>Should your proposals merit further review, the OMOP CDM Working Group will reach out to you to schedule a time for you to present your case at an upcoming meeting. You will be given 15-30 minutes to present your document and you can include anything you feel will help illustrate the need and your potential solution. The group will then discuss, ask questions, and potentially offer other solutions. Depending on the nature of the request, this may go over multiple sessions and you may be asked to make changes to your initial design. At the end of this process your proposal will then be put to consensus in the CDM WG. If the group decides no, they will give feedback describing why they did not feel your proposal should be accepted at this time. If the group decides yes, you move on to step 3.</p>
+<p><strong>Potential Decision Criteria:</strong></p>
+<ul>
+<li>If the change is foundational to OHDSI tools, then the proposal will be put to the larger community open to public comment</li>
+<li>How generalizable is your change? Can it be readily applied to other use cases?</li>
+<li>Are the proposed changes/additions well designed from a modeling perspective? Do they follow the existing OMOP CDM conventions?</li>
+<li>What are the consequences of the change? Are they potentially breaking changes or are they just changes to existing conventions? Will they require the remapping of existing OMOP datasources?</li>
+<li>How complicated is your change? Is it an addition of a field or multiple tables?</li>
+</ul>
+</div>
+<div id="step-3-preliminary-decision" class="section level2">
+<h2>Step 3: Preliminary Decision</h2>
+<p>If the proposal is accepted in the preliminary decision, then a branch will be created in the CommonDataModel repository, based on the latest version of the OMOP CDM in use (currently v5.4). It will then be your responsibility to apply the change programmatically in this branch. This should include:</p>
+<ul>
+<li>Updating the CSV file with the CDM specification, including the User Guide and ETL Conventions documentation</li>
+<li>Generating the DDL files with the change</li>
+<li>Testing the new DDL files in at least one supported environment</li>
+</ul>
+<p>Once the DDLs with the proposed change are created and tested, you should then ETL some data (either real or synthetic) into the new table/fields. Then, an example cohort should be created that utilizes the change or addition and clearly displays how it can be used in a real study. It is expected that during this stage the proposal will change as you work through your idea in a tangible environment.</p>
+<p><strong>Potential Decision Criteria:</strong></p>
+<ul>
+<li>How would you evaluate the quality of this new field/table?</li>
+<li>What characterizations would you perform?</li>
+<li>How would you perform a study using this new feature?</li>
+</ul>
+<p><strong>Potential Outcomes:</strong></p>
+<ul>
+<li>Proposal demonstrates merit for further consideration as:
+<ul>
+<li>a core data model change (move on to next steps)</li>
+<li>an extension (how do we deal with these/do we have ownership of them?)</li>
+</ul></li>
+<li>Proposal does not demonstrate merit for further consideration at this time, and:
+<ul>
+<li>recommend as a LOCAL extension</li>
+<li>recommend a different course</li>
+</ul></li>
+</ul>
+</div>
+<div id="step-4-final-presentation" class="section level2">
+<h2>Step 4: Final Presentation</h2>
+<p>After generating, testing, and implementing your proposal in a real-world environment the CDM working group will invite you again to present your findings in another 15-30 minute presentation. This should include learnings from the exercise and any updates made to the initial proposal.</p>
+</div>
+<div id="step-5-final-decision" class="section level2">
+<h2>Step 5: Final Decision</h2>
+<p>At this point, the working group liaisons will also take the proposal to other groups to elicit feedback. Then the CDM working group will vote and give a final decision on the proposed change. If ratified, the branch in the repository will be merged into the develop branch to be included in a next version of the OMOP Common Data Model.</p>
+<p>The change should initiate requests for features in tools. The end of this process should be a trigger for using the new feature as per the use case. The group should also produce at least one query for the query library on how to work with the new addition/change.</p>
+<div id="resources" class="section level3">
+<h3>Resources</h3>
+<p>“Implementing &amp; adopting a customized OMOP Common Data Model” (Melany Philofsky, OHDSI Symposium 2021) <a href="https://www.ohdsi.org/2021-global-symposium-showcase-18/" class="uri">https://www.ohdsi.org/2021-global-symposium-showcase-18/</a></p>
+</div>
+</div>
+
+
+
+</div>
+</div>
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+<script>
+$(document).ready(function ()  {
+
+    // temporarily add toc-ignore selector to headers for the consistency with Pandoc
+    $('.unlisted.unnumbered').addClass('toc-ignore')
+
+    // move toc-ignore selectors from section div to header
+    $('div.section.toc-ignore')
+        .removeClass('toc-ignore')
+        .children('h1,h2,h3,h4,h5').addClass('toc-ignore');
+
+    // establish options
+    var options = {
+      selectors: "h1,h2,h3",
+      theme: "bootstrap3",
+      context: '.toc-content',
+      hashGenerator: function (text) {
+        return text.replace(/[.\\/?&!#<>]/g, '').replace(/\s/g, '_');
+      },
+      ignoreSelector: ".toc-ignore",
+      scrollTo: 0
+    };
+    options.showAndHide = true;
+    options.smoothScroll = true;
+
+    // tocify
+    var toc = $("#TOC").tocify(options).data("toc-tocify");
+});
+</script>
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/contactVocab.html b/docs/contactVocab.html
new file mode 100644
index 0000000..5aa5c7a
--- /dev/null
+++ b/docs/contactVocab.html
@@ -0,0 +1,469 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Contact the Vocab Team</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Contact the Vocab Team</h1>
+
+</div>
+
+
+<p>Okay so you have something you would like to add to the CDM but there is not an existing OMOP vocabulary nor an open-source vocabulary we can bring in to support it. <strong>In this case, please contact the vocabulary team on next steps</strong> as data elements in the CDM must have a vocabulary in place before they can be implemented.</p>
+<p><a href="https://teams.microsoft.com/l/channel/19%3a31208179438d45749ff484124e7b1e5e%40thread.tacv2/Vocabulary%2520Subgroup?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&amp;tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5">Vocabulary Teams Channel</a></p>
+<p>Once you come to consensus with the vocabulary team regarding your needs, please follow the <a href="cdmRequestProcess.html">CDM Request Process</a> to begin the steps soliciting a change or addition to the model itself. Need more guidance? Consider contacting the CDM Working Group on our <a href="https://github.com/OHDSI/CommonDataModel">GitHub</a> or <a href="https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&amp;tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5">Teams Channel</a>.</p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/contribute.html b/docs/contribute.html
index 3d39bec..f79030a 100644
--- a/docs/contribute.html
+++ b/docs/contribute.html
@@ -13,7 +13,7 @@
 
 <title>Ask A Question</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/dataModelConventions.html b/docs/dataModelConventions.html
index 21aefa9..9ca459d 100644
--- a/docs/dataModelConventions.html
+++ b/docs/dataModelConventions.html
@@ -13,7 +13,7 @@
 
 <title>dataModelConventions.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/download.html b/docs/download.html
index 4bd54f2..5d9c5c7 100644
--- a/docs/download.html
+++ b/docs/download.html
@@ -13,7 +13,7 @@
 
 <title>Download</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/drug_dose.html b/docs/drug_dose.html
index b65c59c..cb458f6 100644
--- a/docs/drug_dose.html
+++ b/docs/drug_dose.html
@@ -15,7 +15,7 @@
 
 <title>drug_dose.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -62,6 +62,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -87,6 +88,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -238,7 +242,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -254,7 +258,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -274,7 +278,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -294,7 +298,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -312,7 +316,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -325,19 +329,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -347,7 +354,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -367,7 +374,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -375,6 +382,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/ehrObsPeriods.html b/docs/ehrObsPeriods.html
index a050d77..eecb081 100644
--- a/docs/ehrObsPeriods.html
+++ b/docs/ehrObsPeriods.html
@@ -13,7 +13,7 @@
 
 <title>Observation Period Considerations for EHR Data</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -60,6 +60,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -85,6 +86,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -236,7 +240,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -252,7 +256,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -272,7 +276,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -292,7 +296,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -310,7 +314,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -323,19 +327,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -345,7 +352,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -365,7 +372,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -373,6 +380,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/faq.html b/docs/faq.html
index 5541100..843d41d 100644
--- a/docs/faq.html
+++ b/docs/faq.html
@@ -13,7 +13,7 @@
 
 <title>OMOP CDM Frequently Asked Questions</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -29,6 +29,9 @@
        h6 {font-size: 12px;}
        code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
        pre:not([class]) { background-color: white }</style>
+<script src="site_libs/jqueryui-1.11.4/jquery-ui.min.js"></script>
+<link href="site_libs/tocify-1.9.1/jquery.tocify.css" rel="stylesheet" />
+<script src="site_libs/tocify-1.9.1/jquery.tocify.js"></script>
 <script src="site_libs/navigation-1.1/tabsets.js"></script>
 <link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
 <script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
@@ -60,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -85,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -222,6 +229,69 @@ $(document).ready(function () {
 
 
 
+<style type="text/css">
+
+#TOC {
+  margin: 25px 0px 20px 0px;
+}
+@media (max-width: 768px) {
+#TOC {
+  position: relative;
+  width: 100%;
+}
+}
+
+@media print {
+.toc-content {
+  /* see https://github.com/w3c/csswg-drafts/issues/4434 */
+  float: right;
+}
+}
+
+.toc-content {
+  padding-left: 30px;
+  padding-right: 40px;
+}
+
+div.main-container {
+  max-width: 1200px;
+}
+
+div.tocify {
+  width: 20%;
+  max-width: 260px;
+  max-height: 85%;
+}
+
+@media (min-width: 768px) and (max-width: 991px) {
+  div.tocify {
+    width: 25%;
+  }
+}
+
+@media (max-width: 767px) {
+  div.tocify {
+    width: 100%;
+    max-width: none;
+  }
+}
+
+.tocify ul, .tocify li {
+  line-height: 20px;
+}
+
+.tocify-subheader .tocify-item {
+  font-size: 0.90em;
+}
+
+.tocify .list-group-item {
+  border-radius: 0px;
+}
+
+
+</style>
+
+
 
 </head>
 
@@ -231,12 +301,22 @@ $(document).ready(function () {
 <div class="container-fluid main-container">
 
 
+<!-- setup 3col/9col grid for toc_float and main content  -->
+<div class="row">
+<div class="col-xs-12 col-sm-4 col-md-3">
+<div id="TOC" class="tocify">
+</div>
+</div>
+
+<div class="toc-content col-xs-12 col-sm-8 col-md-9">
+
+
 
 
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -252,7 +332,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -272,7 +352,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -292,7 +372,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -310,7 +390,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -323,19 +403,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -345,7 +428,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -365,7 +448,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -373,6 +456,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -504,9 +590,36 @@ $(document).ready(function () {
 <p>OHDSI runs as a distributed data network. All analyses are publicly available and can be downloaded to run at each site. The packages can be run locally and, at the data partner’s discretion, aggregate results can be shared with the study coordinator.</p>
 <p>Data partners can also make use of one of OHDSI’s open-source tools called <a href="https://github.com/OHDSI/arachne">ARACHNE</a>, a tool to facilitate distributed network analytics against the OMOP CDM.</p>
 </div>
+<div id="recommended-system-requirements" class="section level2">
+<h2>Recommended System Requirements</h2>
+<p>It is difficult to recommend what technical capabilities a site needs to set up an ETL because it is heavily dependent on the amount of data they have and how they plan to use it. Here are some examples of options that have worked well for small to medium organizations and large organizations:</p>
+<p><strong>Small-to-Medium Organization</strong></p>
+<ul>
+<li>CDM size is 100MB to several GBs</li>
+<li>Vocab ~20GB</li>
+<li>Results &lt; 500 MB</li>
+<li>Recommend
+<ul>
+<li>Server class machine disk &gt;= 250GB (SSD preferred), &gt;= 4 cores, &gt;= 32GB RAM</li>
+</ul></li>
+</ul>
+<p><strong>Large Organization</strong></p>
+<ul>
+<li>CDM size is 12GB to several TBs</li>
+<li>Vocab ~20GB</li>
+<li>Results &lt; 500 MB</li>
+<li>Recommend
+<ul>
+<li>Cloud-based infrastructure like multiple AWS Redshift clusters, for example:</li>
+<li><img src="images/AWS_clusters.png" /></li>
+</ul></li>
+</ul>
+</div>
 
 
 
+</div>
+</div>
 
 </div>
 
@@ -539,6 +652,35 @@ $(document).ready(function () {
 
 <!-- code folding -->
 
+<script>
+$(document).ready(function ()  {
+
+    // temporarily add toc-ignore selector to headers for the consistency with Pandoc
+    $('.unlisted.unnumbered').addClass('toc-ignore')
+
+    // move toc-ignore selectors from section div to header
+    $('div.section.toc-ignore')
+        .removeClass('toc-ignore')
+        .children('h1,h2,h3,h4,h5').addClass('toc-ignore');
+
+    // establish options
+    var options = {
+      selectors: "h1,h2,h3,h4,h5",
+      theme: "bootstrap3",
+      context: '.toc-content',
+      hashGenerator: function (text) {
+        return text.replace(/[.\\/?&!#<>]/g, '').replace(/\s/g, '_');
+      },
+      ignoreSelector: ".toc-ignore",
+      scrollTo: 0
+    };
+    options.showAndHide = true;
+    options.smoothScroll = true;
+
+    // tocify
+    var toc = $("#TOC").tocify(options).data("toc-tocify");
+});
+</script>
 
 <!-- dynamically load mathjax for compatibility with self-contained -->
 <script>
diff --git a/docs/images/AWS_clusters.png b/docs/images/AWS_clusters.png
new file mode 100644
index 0000000..17add03
Binary files /dev/null and b/docs/images/AWS_clusters.png differ
diff --git a/docs/index.html b/docs/index.html
index 09ea47e..8d6288a 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -13,7 +13,7 @@
 
 <title>index.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -60,6 +60,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -85,6 +86,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -236,7 +240,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -252,7 +256,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -272,7 +276,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -292,7 +296,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -310,7 +314,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -323,19 +327,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -345,7 +352,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -365,7 +372,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -373,6 +380,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -497,9 +507,9 @@ $(document).ready(function () {
 <div id="meeting-information" class="section level3">
 <h3>Meeting Information</h3>
 <p>The CDM working group meets the first and third Tuesday of the month. See below for links to the meetings.</p>
-<p><strong>Every first Tuesday of the month at 1pm est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d">Teams Meeting</a></p>
+<p><strong>Every first Tuesday of the month at 10am est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d">Teams Meeting</a></p>
 <p><strong>Every third Tuesday of the month at 1pm est</strong> <a href="https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1611000164347?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%223c193b7f-c2ab-4bcf-b88c-f89a6b1fba38%22%7d">Teams Meeting</a></p>
-<p><strong>Note</strong> If you do you have access to the OHDSI Teams Tenet, either contact Clair Blacketer at <a href="mailto:mblacke@its.jnj.com" class="email">mblacke@its.jnj.com</a> or fill out [this form] (<a href="https://forms.office.com/Pages/ResponsePage.aspx?id=lAAPoyCRq0q6TOVQkCOy1ZyG6Ud_r2tKuS0HcGnqiQZUOVJFUzBFWE1aSVlLN0ozR01MUVQ4T0RGNyQlQCN0PWcu" class="uri">https://forms.office.com/Pages/ResponsePage.aspx?id=lAAPoyCRq0q6TOVQkCOy1ZyG6Ud_r2tKuS0HcGnqiQZUOVJFUzBFWE1aSVlLN0ozR01MUVQ4T0RGNyQlQCN0PWcu</a>) and check “Common Data Model”</p>
+<p><strong>Note</strong> If you do you have access to the OHDSI Teams Tenet, either contact Clair Blacketer at <a href="mailto:mblacke@its.jnj.com" class="email">mblacke@its.jnj.com</a> or fill out <a href="https://forms.office.com/Pages/ResponsePage.aspx?id=lAAPoyCRq0q6TOVQkCOy1ZyG6Ud_r2tKuS0HcGnqiQZUOVJFUzBFWE1aSVlLN0ozR01MUVQ4T0RGNyQlQCN0PWcu">this form</a> and check “Common Data Model”</p>
 </div>
 <div id="cdm-wg-important-links" class="section level3">
 <h3>CDM WG Important Links</h3>
diff --git a/docs/indices-primary-foreign.html b/docs/indices-primary-foreign.html
index fe2dddc..9c50a1d 100644
--- a/docs/indices-primary-foreign.html
+++ b/docs/indices-primary-foreign.html
@@ -13,7 +13,7 @@
 
 <title>Indices, Primary Keys and Foreign Key Constraints</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/leaveAsIs.html b/docs/leaveAsIs.html
new file mode 100644
index 0000000..1feb8db
--- /dev/null
+++ b/docs/leaveAsIs.html
@@ -0,0 +1,467 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Leave As Is</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Leave As Is</h1>
+
+</div>
+
+
+<p>Okay, so you do not have a network use case but multiple collaborators have access to the element you are interested in adding to the CDM. <strong>In this circumstance, the CDM Working Group suggests leaving the model as-is.</strong> Without a network use case there is no need to augment the data model. If this is something you need for your work, consider a <a href="localChange.html">local change</a> or a model extension.</p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/localChange.html b/docs/localChange.html
new file mode 100644
index 0000000..247f9e8
--- /dev/null
+++ b/docs/localChange.html
@@ -0,0 +1,467 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Local Change</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Local Change</h1>
+
+</div>
+
+
+<p>Since you do not have a network use case and this element is specific to your data source, <strong>feel free to create a local change to your instance of the OMOP Common Data Model.</strong> Augmenting the model at your institution for administrative purposes or other in-house needs is totally acceptable with the understanding that any local changes cannot and should not be relied upon in network studies or supported by the open-source tools.</p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/networkUseCase.html b/docs/networkUseCase.html
new file mode 100644
index 0000000..ced85b9
--- /dev/null
+++ b/docs/networkUseCase.html
@@ -0,0 +1,469 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Network Use Case</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Network Use Case</h1>
+
+</div>
+
+
+<p>Alright, so you think you might need to change the OMOP Common Data Model. <strong>Do you have a documented network use case for this data need? This could take the form of an upcoming study or a convention for how to store information.</strong> In this scenario, at least two or more collaborators with data to contribute constitute a network need.</p>
+<p><a href="useCaseY.html">Yes, I have a network use case</a></p>
+<p><a href="useCaseN.html">No, I do not have a network use case</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/oncology.html b/docs/oncology.html
index 414af3b..ca4e87c 100644
--- a/docs/oncology.html
+++ b/docs/oncology.html
@@ -13,7 +13,7 @@
 
 <title>Oncology Extension</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -486,429 +496,14 @@ div.tocify {
 <h2>OMOP Common Data Model Oncology Extension Documentation</h2>
 <p>This documentation details the ratified proposal of adding an oncology extension to the OMOP CDM. These tables and fields will become part of the next release (v6.1) of the Common Data Model. Below are their descriptions; showing <em>additions</em> to the model only. For example, two fields were added to the MEASUREMENT table as part of this extension so only those two fields are listed below for MEASUREMENT instead of the entire table. For more information, please see the <a href="https://github.com/OHDSI/OncologyWG/wiki">OMOP Oncology wiki site</a>.</p>
 <p>The DDLs for these tables are located on the Oncology github, as detailed in the <a href="https://github.com/OHDSI/OncologyWG/wiki/Oncology-CDM-Extension-Installation">installation instructions</a>.</p>
-<pre><code>## Warning in read.table(file = file, header = header, sep = sep, quote = quote, : incomplete final line found by readTableHeader on &#39;../inst/csv/
-## OMOP_CDM_Oncology_Ex_Table_Level.csv&#39;</code></pre>
+<pre><code>## Warning in read.table(file = file, header = header, sep = sep, quote = quote, : incomplete final line found
+## by readTableHeader on &#39;../inst/csv/OMOP_CDM_Oncology_Ex_Table_Level.csv&#39;</code></pre>
 <div id="episode" class="section level3 tabset tabset-pills">
 <h3 class="tabset tabset-pills">EPISODE</h3>
 <p><strong>Table Description</strong></p>
 <p>The EPISODE table aggregates lower-level clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) into a higher-level abstraction representing clinically and analytically relevant disease phases,outcomes and treatments. The EPISODE_EVENT table connects qualifying clinical events (VISIT_OCCURRENCE, DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, DEVICE_EXPOSURE) to the appropriate EPISODE entry. For example cancers including their development over time, their treatment, and final resolution.</p>
 <p><strong>User Guide</strong></p>
 <p>Valid Episode Concepts belong to the ‘Episode’ domain. For cancer episodes please see [article], for non-cancer episodes please see [article]. If your source data does not have all episodes that are relevant to the therapeutic area, write only those you can easily derive from the data. It is understood that that table is not currently expected to be comprehensive.</p>
-<table class="table table-condensed table-hover" style="font-size: 13px; margin-left: auto; margin-right: auto;">
-<thead>
-<tr>
-<th style="text-align:left;">
-CDM Field
-</th>
-<th style="text-align:left;width: 3in; ">
-User Guide
-</th>
-<th style="text-align:left;width: 4in; ">
-ETL Conventions
-</th>
-<th style="text-align:left;width: 1in; ">
-Datatype
-</th>
-<th style="text-align:left;width: 1in; ">
-Required
-</th>
-<th style="text-align:left;width: 1in; ">
-Primary Key
-</th>
-<th style="text-align:left;width: 1in; ">
-Foreign Key
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Table
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Domain
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Class
-</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_id
-</td>
-<td style="text-align:left;width: 3in; ">
-A unique identifier for each Episode.
-</td>
-<td style="text-align:left;width: 4in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-person_id
-</td>
-<td style="text-align:left;width: 3in; ">
-The PERSON_ID of the PERSON for whom the episode is recorded.
-</td>
-<td style="text-align:left;width: 4in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-PERSON
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-The EPISODE_CONCEPT_ID represents the kind abstraction related to the disease phase, outcome or treatment.
-</td>
-<td style="text-align:left;width: 4in; ">
-Choose a concept in the Episode domain that best represents the ongoing disease phase, outcome, or treatment. Please see [article] for cancers and [article] for non-cancers describing how these are defined. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Episode&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-Episode
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_start_date
-</td>
-<td style="text-align:left;width: 3in; ">
-The date when the Episode beings.
-</td>
-<td style="text-align:left;width: 4in; ">
-Please see [article] for how to define an Episode start date.
-</td>
-<td style="text-align:left;width: 1in; ">
-date
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_start_datetime
-</td>
-<td style="text-align:left;width: 3in; ">
-The date and time when the Episode begins.
-</td>
-<td style="text-align:left;width: 4in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-datetime
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_end_date
-</td>
-<td style="text-align:left;width: 3in; ">
-The date when the instance of the Episode is considered to have ended.
-</td>
-<td style="text-align:left;width: 4in; ">
-Please see [article] for how to define an Episode end date.
-</td>
-<td style="text-align:left;width: 1in; ">
-date
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_end_datetime
-</td>
-<td style="text-align:left;width: 3in; ">
-The date when the instance of the Episode is considered to have ended.
-</td>
-<td style="text-align:left;width: 4in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-datetime
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_parent_id
-</td>
-<td style="text-align:left;width: 3in; ">
-Use this field to find the Episode that subsumes the given Episode record. This is used in the case that an Episode are nested into each other.
-</td>
-<td style="text-align:left;width: 4in; ">
-If there are multiple nested levels to how Episodes are represented, the EPISODE_PARENT_ID can be used to record this relationship.
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_number
-</td>
-<td style="text-align:left;width: 3in; ">
-For sequences of episodes, this is used to indicate the order the episodes occurred. For example, lines of treatment could be indicated here.
-</td>
-<td style="text-align:left;width: 4in; ">
-Please see [article] for the details of how to count episodes.
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_object_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-A Standard Concept representing the disease phase, outcome, or other abstraction of which the episode consists. For example, if the EPISODE_CONCEPT_ID is <a href="https://athena.ohdsi.org/search-terms/terms/32531">treatment regimen</a> then the EPISODE_OBJECT_CONCEPT_ID should contain the chemotherapy regimen concept, like <a href="https://athena.ohdsi.org/search-terms/terms/35804392">Afatinib monotherapy</a>.
-</td>
-<td style="text-align:left;width: 4in; ">
-Episode entries from the ‘Disease Episode’ concept class should have an episode_object_concept_id that comes from the Condition domain. Episode entries from the ‘Treatment Episode’ concept class should have an episode_object_concept_id that scome from the ‘Procedure’ domain or ‘Regimen’ concept class.
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-CONCEPT
-</td>
-<td style="text-align:left;width: 1in; ">
-Procedure, Regimen
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_type_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-This field can be used to determine the provenance of the Episode record, as in whether the episode was from an EHR system, insurance claim, registry, or other sources.
-</td>
-<td style="text-align:left;width: 4in; ">
-Choose the EPISODE_TYPE_CONCEPT_ID that best represents the provenance of the record. <a href="https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&amp;standardConcept=Standard&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>.
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-CONCEPT
-</td>
-<td style="text-align:left;width: 1in; ">
-Type Concept
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_source_value
-</td>
-<td style="text-align:left;width: 3in; ">
-The source code for the Episdoe as it appears in the source data. This code is mapped to a Standard Condition Concept in the Standardized Vocabularies and the original code is stored here for reference.
-</td>
-<td style="text-align:left;width: 4in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-varchar(50)
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_source_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-A foreign key to a Episode Concept that refers to the code used in the source.
-</td>
-<td style="text-align:left;width: 4in; ">
-Given that the Episodes are user-defined it is unlikely that there will be a Source Concept available. If that is the case then set this field to zero.
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-CONCEPT
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-</tbody>
-</table>
 </div>
 <div id="episode_event" class="section level3 tabset tabset-pills">
 <h3 class="tabset tabset-pills">EPISODE_EVENT</h3>
@@ -918,134 +513,6 @@ CONCEPT
 <p>This connecting table is used instead of the FACT_RELATIONSHIP table for linking low-level events to abstracted Episodes.</p>
 <p><strong>ETL Conventions</strong></p>
 <p>Some episodes may not have links to any underlying clinical events. For such episodes, the EPISODE_EVENT table is not populated.</p>
-<table class="table table-condensed table-hover" style="font-size: 13px; margin-left: auto; margin-right: auto;">
-<thead>
-<tr>
-<th style="text-align:left;">
-CDM Field
-</th>
-<th style="text-align:left;width: 3in; ">
-User Guide
-</th>
-<th style="text-align:left;width: 4in; ">
-ETL Conventions
-</th>
-<th style="text-align:left;width: 1in; ">
-Datatype
-</th>
-<th style="text-align:left;width: 1in; ">
-Required
-</th>
-<th style="text-align:left;width: 1in; ">
-Primary Key
-</th>
-<th style="text-align:left;width: 1in; ">
-Foreign Key
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Table
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Domain
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Class
-</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_id
-</td>
-<td style="text-align:left;width: 3in; ">
-Use this field to link the EPISODE_EVENT record to its EPISODE.
-</td>
-<td style="text-align:left;width: 4in; ">
-Put the EPISODE_ID that subsumes the EPISODE_EVENT record here.
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-EPISODE
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-event_id
-</td>
-<td style="text-align:left;width: 3in; ">
-This field is the primary key of the linked record in the database. For example, if the Episode Event is a Condition Occurrence, then the CONDITION_OCCURRENCE_ID of the linked record goes in this field.
-</td>
-<td style="text-align:left;width: 4in; ">
-Put the primary key of the linked record here.
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-episode_event_field_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-This field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
-</td>
-<td style="text-align:left;width: 4in; ">
-Put the CONCEPT_ID that identifies which table and field the EVENT_ID came from. <a href="https://athena.ohdsi.org/search-terms/terms?vocabulary=CDM&amp;conceptClass=Field&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-CONCEPT
-</td>
-<td style="text-align:left;width: 1in; ">
-Metadata
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-</tbody>
-</table>
 </div>
 <div id="measurement" class="section level3 tabset tabset-pills">
 <h3 class="tabset tabset-pills">MEASUREMENT</h3>
@@ -1053,104 +520,6 @@ Metadata
 <p>The MEASUREMENT table contains records of Measurement, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person’s sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID).</p>
 <p><strong>User Guide</strong></p>
 <p>Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result.</p>
-<table class="table table-condensed table-hover" style="font-size: 13px; margin-left: auto; margin-right: auto;">
-<thead>
-<tr>
-<th style="text-align:left;">
-CDM Field
-</th>
-<th style="text-align:left;width: 3in; ">
-User Guide
-</th>
-<th style="text-align:left;width: 4in; ">
-ETL Conventions
-</th>
-<th style="text-align:left;width: 1in; ">
-Datatype
-</th>
-<th style="text-align:left;width: 1in; ">
-Required
-</th>
-<th style="text-align:left;width: 1in; ">
-Primary Key
-</th>
-<th style="text-align:left;width: 1in; ">
-Foreign Key
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Table
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Domain
-</th>
-<th style="text-align:left;width: 1in; ">
-FK Class
-</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-modifier_of_event_id
-</td>
-<td style="text-align:left;width: 3in; ">
-If the Measurement record is related to another record in the database, this field is the primary key of the linked record.
-</td>
-<td style="text-align:left;width: 4in; ">
-Put the primary key of the linked record, if applicable, here.
-</td>
-<td style="text-align:left;width: 1in; ">
-bigint
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-<tr>
-<td style="text-align:left;font-weight: bold;">
-modifier_of_field_concept_id
-</td>
-<td style="text-align:left;width: 3in; ">
-If the Measurement record is related to another record in the database, this field is the CONCEPT_ID that identifies which table the primary key of the linked record came from.
-</td>
-<td style="text-align:left;width: 4in; ">
-Put the CONCEPT_ID that identifies which table and field the MODIFIER_OF_EVENT_ID came from. <a href="https://athena.ohdsi.org/search-terms/terms?vocabulary=CDM&amp;conceptClass=Field&amp;page=1&amp;pageSize=15&amp;query=">Accepted Concepts</a>
-</td>
-<td style="text-align:left;width: 1in; ">
-integer
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-No
-</td>
-<td style="text-align:left;width: 1in; ">
-Yes
-</td>
-<td style="text-align:left;width: 1in; ">
-CONCEPT
-</td>
-<td style="text-align:left;width: 1in; ">
-Metadata
-</td>
-<td style="text-align:left;width: 1in; ">
-</td>
-</tr>
-</tbody>
-</table>
 </div>
 </div>
 
diff --git a/docs/queries.html b/docs/queries.html
index bb73e06..72e1953 100644
--- a/docs/queries.html
+++ b/docs/queries.html
@@ -15,7 +15,7 @@
 
 <title>Example_Queries</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -62,6 +62,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -87,6 +88,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -238,7 +242,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -254,7 +258,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -274,7 +278,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -294,7 +298,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -312,7 +316,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -325,19 +329,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -347,7 +354,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -367,7 +374,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -375,6 +382,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/reviewProposals.html b/docs/reviewProposals.html
index 6f61248..06f079a 100644
--- a/docs/reviewProposals.html
+++ b/docs/reviewProposals.html
@@ -13,7 +13,7 @@
 
 <title>CDM Proposals Under Review</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -60,6 +60,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -85,6 +86,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -236,7 +240,7 @@ $(document).ready(function () {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -252,7 +256,7 @@ $(document).ready(function () {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -272,7 +276,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -292,7 +296,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -310,7 +314,7 @@ $(document).ready(function () {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -323,19 +327,22 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -345,7 +352,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -365,7 +372,7 @@ $(document).ready(function () {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -373,6 +380,9 @@ $(document).ready(function () {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/docs/site_libs/header-attrs-2.11/header-attrs.js b/docs/site_libs/header-attrs-2.13/header-attrs.js
similarity index 100%
rename from docs/site_libs/header-attrs-2.11/header-attrs.js
rename to docs/site_libs/header-attrs-2.13/header-attrs.js
diff --git a/docs/site_libs/navigation-1.1/codefolding.js b/docs/site_libs/navigation-1.1/codefolding.js
index 8a0d36f..981faea 100644
--- a/docs/site_libs/navigation-1.1/codefolding.js
+++ b/docs/site_libs/navigation-1.1/codefolding.js
@@ -34,7 +34,9 @@ window.initializeCodeFolding = function(show) {
     showCodeButton.append(showCodeText);
     showCodeButton
         .attr('data-toggle', 'collapse')
+        .attr('data-bs-toggle', 'collapse') // BS5
         .attr('data-target', '#' + id)
+        .attr('data-bs-target', '#' + id)   // BS5
         .attr('aria-expanded', showThis)
         .attr('aria-controls', id);
 
diff --git a/docs/sqlScripts.html b/docs/sqlScripts.html
index 86e7398..6fb3a26 100644
--- a/docs/sqlScripts.html
+++ b/docs/sqlScripts.html
@@ -13,7 +13,7 @@
 
 <title>sqlScripts.knit</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
@@ -698,176 +708,170 @@ GROUP BY person_id
 </div>
 <div id="drug-eras" class="section level3">
 <h3>Drug Eras</h3>
-<p>If the DRUG_EXPOSURE table is populated this script will string together periods of time that a person is exposed to an active drug ingredient, allowing for 30 gaps in between. It will then insert the resulting era records into the DRUG_ERA table. <strong>NOTE</strong> This query only works with 5.3 and below.</p>
+<p>If the DRUG_EXPOSURE table is populated this script will string together periods of time that a person is exposed to an active drug ingredient, allowing for 30 gaps in between. It will then insert the resulting era records into the DRUG_ERA table. <strong>NOTE</strong> This query only works with the <strong>version 5</strong> series and below.</p>
 <pre class="sql"><code>
-/****************************************************
-OHDSI-SQL File Instructions
------------------------------
- 1. Set parameter name of schema that contains CDMv4 instance
-    (@SOURCE_CDMV4, @SOURCE_CDMV4_SCHEMA)
- 2. Set parameter name of schema that contains CDMv5 instance
-    (@TARGET_CDMV5, @TARGET_CDMV5_SCHEMA)
- 3. Run this script through SqlRender to produce a script that will work in your
-    source dialect. SqlRender can be found here: https://github.com/OHDSI/SqlRender
- 4. Run the script produced by SQL Render on your target RDBDMS.
-&lt;RDBMS&gt; File Instructions
--------------------------
- 1. This script will hold a number of placeholders for your CDM V4 and CDMV5
-    database/schema. In order to make this file work in your environment, you
-    should plan to do a global &quot;FIND AND REPLACE&quot; on this file to fill in the
-    file with values that pertain to your environment. The following are the
-    tokens you should use when doing your &quot;FIND AND REPLACE&quot; operation:
-    
-     [CDM]
-     [CDM].[CDMSCHEMA]
-    
-*********************************************************************************/
-/* SCRIPT PARAMETERS */
-
-    
-    {DEFAULT @TARGET_CDMV5 = &#39;[CDM]&#39; } -- The target CDMv5 database name
-    {DEFAULT @TARGET_CDMV5_SCHEMA = &#39;[CDM].[CDMSCHEMA]&#39; } -- the target CDMv5 database plus schema
-
-USE @TARGET_CDMV5;
+-- Code taken from:
+-- https://github.com/OHDSI/ETL-CMS/blob/master/SQL/create_CDMv5_drug_era_non_stockpile.sql
 
 
+if object_id(&#39;tempdb..#tmp_de&#39;, &#39;U&#39;) is not null drop table #tmp_de;
 
-/****
-DRUG ERA
-Note: Eras derived from DRUG_EXPOSURE table, using 30d gap
- ****/
-IF OBJECT_ID(&#39;tempdb..#cteDrugTarget&#39;, &#39;U&#39;) IS NOT NULL
-    DROP TABLE #cteDrugTarget;
+WITH
+ctePreDrugTarget(drug_exposure_id, person_id, ingredient_concept_id, drug_exposure_start_date, days_supply, drug_exposure_end_date) AS
+(-- Normalize DRUG_EXPOSURE_END_DATE to either the existing drug exposure end date, or add days supply, or add 1 day to the start date
+    SELECT
+        d.drug_exposure_id
+        , d.person_id
+        , c.concept_id AS ingredient_concept_id
+        , d.drug_exposure_start_date AS drug_exposure_start_date
+        , d.days_supply AS days_supply
+        , COALESCE(
+            ---NULLIF returns NULL if both values are the same, otherwise it returns the first parameter
+            NULLIF(drug_exposure_end_date, NULL),
+            ---If drug_exposure_end_date != NULL, return drug_exposure_end_date, otherwise go to next case
+            NULLIF(dateadd(day,days_supply,drug_exposure_start_date), drug_exposure_start_date),
+            ---If days_supply != NULL or 0, return drug_exposure_start_date + days_supply, otherwise go to next case
+            dateadd(day,1,drug_exposure_start_date)
+            ---Add 1 day to the drug_exposure_start_date since there is no end_date or INTERVAL for the days_supply
+        ) AS drug_exposure_end_date
+    FROM @cdm_schema.drug_exposure d
+        JOIN @cdm_schema.concept_ancestor ca ON ca.descendant_concept_id = d.drug_concept_id
+        JOIN @cdm_schema.concept c ON ca.ancestor_concept_id = c.concept_id
+        WHERE c.vocabulary_id = &#39;RxNorm&#39; ---8 selects RxNorm from the vocabulary_id
+        AND c.concept_class_id = &#39;Ingredient&#39;
+        AND d.drug_concept_id != 0 ---Our unmapped drug_concept_id&#39;s are set to 0, so we don&#39;t want different drugs wrapped up in the same era
+        AND coalesce(d.days_supply,0) &gt;= 0 ---We have cases where days_supply is negative, and this can set the end_date before the start_date, which we don&#39;t want. So we&#39;re just looking over those rows. This is a data-quality issue.
+)
 
-/* / */
-
--- Normalize DRUG_EXPOSURE_END_DATE to either the existing drug exposure end date, or add days supply, or add 1 day to the start date
-SELECT d.DRUG_EXPOSURE_ID
-    ,d.PERSON_ID
-    ,c.CONCEPT_ID
-    ,d.DRUG_TYPE_CONCEPT_ID
-    ,DRUG_EXPOSURE_START_DATE
-    ,COALESCE(DRUG_EXPOSURE_END_DATE, DATEADD(day, DAYS_SUPPLY, DRUG_EXPOSURE_START_DATE), DATEADD(day, 1, DRUG_EXPOSURE_START_DATE)) AS DRUG_EXPOSURE_END_DATE
-    ,c.CONCEPT_ID AS INGREDIENT_CONCEPT_ID
-INTO #cteDrugTarget
-FROM @TARGET_CDMV5_SCHEMA.DRUG_EXPOSURE d
-INNER JOIN @TARGET_CDMV5_SCHEMA.CONCEPT_ANCESTOR ca ON ca.DESCENDANT_CONCEPT_ID = d.DRUG_CONCEPT_ID
-INNER JOIN @TARGET_CDMV5_SCHEMA.CONCEPT c ON ca.ANCESTOR_CONCEPT_ID = c.CONCEPT_ID
-WHERE c.DOMAIN_ID = &#39;Drug&#39;
-    AND c.CONCEPT_CLASS_ID = &#39;Ingredient&#39;
-    AND c.STANDARD_CONCEPT = &#39;S&#39;;
-
-/* / */
-
-IF OBJECT_ID(&#39;tempdb..#cteEndDates&#39;, &#39;U&#39;) IS NOT NULL
-    DROP TABLE #cteEndDates;
-
-/* / */
-
-SELECT PERSON_ID
-    ,INGREDIENT_CONCEPT_ID
-    ,DATEADD(day, - 30, EVENT_DATE) AS END_DATE -- unpad the end date
-INTO #cteEndDates
-FROM (
-    SELECT E1.PERSON_ID
-        ,E1.INGREDIENT_CONCEPT_ID
-        ,E1.EVENT_DATE
-        ,COALESCE(E1.START_ORDINAL, MAX(E2.START_ORDINAL)) START_ORDINAL
-        ,E1.OVERALL_ORD
-    FROM (
-        SELECT PERSON_ID
-            ,INGREDIENT_CONCEPT_ID
-            ,EVENT_DATE
-            ,EVENT_TYPE
-            ,START_ORDINAL
-            ,ROW_NUMBER() OVER (
-                PARTITION BY PERSON_ID
-                ,INGREDIENT_CONCEPT_ID ORDER BY EVENT_DATE
-                    ,EVENT_TYPE
-                ) AS OVERALL_ORD -- this re-numbers the inner UNION so all rows are numbered ordered by the event date
+, cteSubExposureEndDates (person_id, ingredient_concept_id, end_date) AS --- A preliminary sorting that groups all of the overlapping exposures into one exposure so that we don&#39;t double-count non-gap-days
+(
+    SELECT person_id, ingredient_concept_id, event_date AS end_date
+    FROM
+    (
+        SELECT person_id, ingredient_concept_id, event_date, event_type,
+        MAX(start_ordinal) OVER (PARTITION BY person_id, ingredient_concept_id
+            ORDER BY event_date, event_type ROWS unbounded preceding) AS start_ordinal,
+        -- this pulls the current START down from the prior rows so that the NULLs
+        -- from the END DATES will contain a value we can compare with
+            ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+                ORDER BY event_date, event_type) AS overall_ord
+            -- this re-numbers the inner UNION so all rows are numbered ordered by the event date
         FROM (
             -- select the start dates, assigning a row number to each
-            SELECT PERSON_ID
-                ,INGREDIENT_CONCEPT_ID
-                ,DRUG_EXPOSURE_START_DATE AS EVENT_DATE
-                ,0 AS EVENT_TYPE
-                ,ROW_NUMBER() OVER (
-                    PARTITION BY PERSON_ID
-                    ,INGREDIENT_CONCEPT_ID ORDER BY DRUG_EXPOSURE_START_DATE
-                    ) AS START_ORDINAL
-            FROM #cteDrugTarget
+            SELECT person_id, ingredient_concept_id, drug_exposure_start_date AS event_date,
+            -1 AS event_type,
+            ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+                ORDER BY drug_exposure_start_date) AS start_ordinal
+            FROM ctePreDrugTarget
 
             UNION ALL
 
-            -- add the end dates with NULL as the row number, padding the end dates by 30 to allow a grace period for overlapping ranges.
-            SELECT PERSON_ID
-                ,INGREDIENT_CONCEPT_ID
-                ,DATEADD(day, 30, DRUG_EXPOSURE_END_DATE)
-                ,1 AS EVENT_TYPE
-                ,NULL
-            FROM #cteDrugTarget
-            ) RAWDATA
-        ) E1
-    INNER JOIN (
-        SELECT PERSON_ID
-            ,INGREDIENT_CONCEPT_ID
-            ,DRUG_EXPOSURE_START_DATE AS EVENT_DATE
-            ,ROW_NUMBER() OVER (
-                PARTITION BY PERSON_ID
-                ,INGREDIENT_CONCEPT_ID ORDER BY DRUG_EXPOSURE_START_DATE
-                ) AS START_ORDINAL
-        FROM #cteDrugTarget
-        ) E2 ON E1.PERSON_ID = E2.PERSON_ID
-        AND E1.INGREDIENT_CONCEPT_ID = E2.INGREDIENT_CONCEPT_ID
-        AND E2.EVENT_DATE &lt;= E1.EVENT_DATE
-    GROUP BY E1.PERSON_ID
-        ,E1.INGREDIENT_CONCEPT_ID
-        ,E1.EVENT_DATE
-        ,E1.START_ORDINAL
-        ,E1.OVERALL_ORD
-    ) E
-WHERE 2 * E.START_ORDINAL - E.OVERALL_ORD = 0;
+            SELECT person_id, ingredient_concept_id, drug_exposure_end_date, 1 AS event_type, NULL
+            FROM ctePreDrugTarget
+        ) RAWDATA
+    ) e
+    WHERE (2 * e.start_ordinal) - e.overall_ord = 0
+)
 
-/* / */
+, cteDrugExposureEnds (person_id, drug_concept_id, drug_exposure_start_date, drug_sub_exposure_end_date) AS
+(
+SELECT
+    dt.person_id
+    , dt.ingredient_concept_id
+    , dt.drug_exposure_start_date
+    , MIN(e.end_date) AS drug_sub_exposure_end_date
+FROM ctePreDrugTarget dt
+JOIN cteSubExposureEndDates e ON dt.person_id = e.person_id AND dt.ingredient_concept_id = e.ingredient_concept_id AND e.end_date &gt;= dt.drug_exposure_start_date
+GROUP BY
+        dt.drug_exposure_id
+        , dt.person_id
+    , dt.ingredient_concept_id
+    , dt.drug_exposure_start_date
+)
+--------------------------------------------------------------------------------------------------------------
+, cteSubExposures(row_number, person_id, drug_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count) AS
+(
+    SELECT ROW_NUMBER() OVER (PARTITION BY person_id, drug_concept_id, drug_sub_exposure_end_date ORDER BY person_id)
+        , person_id, drug_concept_id, MIN(drug_exposure_start_date) AS drug_sub_exposure_start_date, drug_sub_exposure_end_date, COUNT(*) AS drug_exposure_count
+    FROM cteDrugExposureEnds
+    GROUP BY person_id, drug_concept_id, drug_sub_exposure_end_date
+    --ORDER BY person_id, drug_concept_id
+)
+--------------------------------------------------------------------------------------------------------------
+/*Everything above grouped exposures into sub_exposures if there was overlap between exposures.
+ *So there was no persistence window. Now we can add the persistence window to calculate eras.
+ */
+--------------------------------------------------------------------------------------------------------------
+, cteFinalTarget(row_number, person_id, ingredient_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count, days_exposed) AS
+(
+    SELECT row_number, person_id, drug_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count
+        , datediff(day,drug_sub_exposure_start_date,drug_sub_exposure_end_date) AS days_exposed
+    FROM cteSubExposures
+)
+--------------------------------------------------------------------------------------------------------------
+, cteEndDates (person_id, ingredient_concept_id, end_date) AS -- the magic
+(
+    SELECT person_id, ingredient_concept_id, dateadd(day,-30,event_date) AS end_date -- unpad the end date
+    FROM
+    (
+        SELECT person_id, ingredient_concept_id, event_date, event_type,
+        MAX(start_ordinal) OVER (PARTITION BY person_id, ingredient_concept_id
+            ORDER BY event_date, event_type ROWS UNBOUNDED PRECEDING) AS start_ordinal,
+        -- this pulls the current START down from the prior rows so that the NULLs
+        -- from the END DATES will contain a value we can compare with
+            ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+                ORDER BY event_date, event_type) AS overall_ord
+            -- this re-numbers the inner UNION so all rows are numbered ordered by the event date
+        FROM (
+            -- select the start dates, assigning a row number to each
+            SELECT person_id, ingredient_concept_id, drug_sub_exposure_start_date AS event_date,
+            -1 AS event_type,
+            ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+                ORDER BY drug_sub_exposure_start_date) AS start_ordinal
+            FROM cteFinalTarget
 
-IF OBJECT_ID(&#39;tempdb..#cteDrugExpEnds&#39;, &#39;U&#39;) IS NOT NULL
-    DROP TABLE #cteDrugExpEnds;
+            UNION ALL
 
-/* / */
+            -- pad the end dates by 30 to allow a grace period for overlapping ranges.
+            SELECT person_id, ingredient_concept_id, dateadd(day,30,drug_sub_exposure_end_date), 1 AS event_type, NULL
+            FROM cteFinalTarget
+        ) RAWDATA
+    ) e
+    WHERE (2 * e.start_ordinal) - e.overall_ord = 0
 
-SELECT d.PERSON_ID
-    ,d.INGREDIENT_CONCEPT_ID
-    ,d.DRUG_TYPE_CONCEPT_ID
-    ,d.DRUG_EXPOSURE_START_DATE
-    ,MIN(e.END_DATE) AS ERA_END_DATE
-INTO #cteDrugExpEnds
-FROM #cteDrugTarget d
-INNER JOIN #cteEndDates e ON d.PERSON_ID = e.PERSON_ID
-    AND d.INGREDIENT_CONCEPT_ID = e.INGREDIENT_CONCEPT_ID
-    AND e.END_DATE &gt;= d.DRUG_EXPOSURE_START_DATE
-GROUP BY d.PERSON_ID
-    ,d.INGREDIENT_CONCEPT_ID
-    ,d.DRUG_TYPE_CONCEPT_ID
-    ,d.DRUG_EXPOSURE_START_DATE;
+)
+, cteDrugEraEnds (person_id, drug_concept_id, drug_sub_exposure_start_date, drug_era_end_date, drug_exposure_count, days_exposed) AS
+(
+SELECT
+    ft.person_id
+    , ft.ingredient_concept_id
+    , ft.drug_sub_exposure_start_date
+    , MIN(e.end_date) AS era_end_date
+    , drug_exposure_count
+    , days_exposed
+FROM cteFinalTarget ft
+JOIN cteEndDates e ON ft.person_id = e.person_id AND ft.ingredient_concept_id = e.ingredient_concept_id AND e.end_date &gt;= ft.drug_sub_exposure_start_date
+GROUP BY
+        ft.person_id
+    , ft.ingredient_concept_id
+    , ft.drug_sub_exposure_start_date
+    , drug_exposure_count
+    , days_exposed
+)
+SELECT
+    row_number()over(order by person_id) drug_era_id
+    , person_id
+    , drug_concept_id
+    , MIN(drug_sub_exposure_start_date) AS drug_era_start_date
+    , drug_era_end_date
+    , SUM(drug_exposure_count) AS drug_exposure_count
+    , datediff(day,MIN(drug_sub_exposure_start_date),drug_era_end_date)-SUM(days_exposed) as gap_days
+INTO #tmp_de
+FROM cteDrugEraEnds dee
+GROUP BY person_id, drug_concept_id, drug_era_end_date;
 
-/* / */
-
-INSERT INTO @TARGET_CDMV5_SCHEMA.drug_era
-SELECT row_number() OVER (
-        ORDER BY person_id
-        ) AS drug_era_id
-    ,person_id
-    ,INGREDIENT_CONCEPT_ID
-    ,min(DRUG_EXPOSURE_START_DATE) AS drug_era_start_date
-    ,ERA_END_DATE
-    ,COUNT(*) AS DRUG_EXPOSURE_COUNT
-    ,30 AS gap_days
-FROM #cteDrugExpEnds
-GROUP BY person_id
-    ,INGREDIENT_CONCEPT_ID
-    ,drug_type_concept_id
-    ,ERA_END_DATE;
-</code></pre>
+INSERT INTO @cdm_schema.drug_era(drug_era_id,person_id, drug_concept_id, drug_era_start_date, drug_era_end_date, drug_exposure_count, gap_days)
+SELECT * FROM #tmp_de;</code></pre>
 </div>
 </div>
 <div id="example-etl-script" class="section level2">
diff --git a/docs/useCaseN.html b/docs/useCaseN.html
new file mode 100644
index 0000000..2d0af16
--- /dev/null
+++ b/docs/useCaseN.html
@@ -0,0 +1,469 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Local Data</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Local Data</h1>
+
+</div>
+
+
+<p>Okay, so you don’t have a network use case. <strong>Is this data element specific to your data source, or are there others in the community who might also have this data but don’t yet need it for a study or data model convention?</strong></p>
+<p><a href="localChange.html">Yes, this element is specific to my data source</a></p>
+<p><a href="leaveAsIs.html">No, there are others in the community who also have this data</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/useCaseY.html b/docs/useCaseY.html
new file mode 100644
index 0000000..f0f2c78
--- /dev/null
+++ b/docs/useCaseY.html
@@ -0,0 +1,470 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>OMOP Vocabulary</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">OMOP Vocabulary</h1>
+
+</div>
+
+
+<p>Great, you have a network use case!</p>
+<p>Next question: <strong>Is there an existing OMOP vocabulary to support this new element? If you are unsure, feel free to check <a href="https://athena.ohdsi.org/search-terms/terms?query">Athena</a>.</strong></p>
+<p><a href="vocabY.html">Yes, I have all the required vocabulary I need</a></p>
+<p><a href="vocabN.html">No, I there is not an existing OMOP vocabulary to support my request</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/vocabN.html b/docs/vocabN.html
new file mode 100644
index 0000000..f832692
--- /dev/null
+++ b/docs/vocabN.html
@@ -0,0 +1,469 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Open Source Vocabulary</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Open Source Vocabulary</h1>
+
+</div>
+
+
+<p>Okay, so you have a use case but you don’t have an OMOP vocabulary to support your need. <strong>Is there an existing open-source (not proprietary or custom) vocabulary that has not yet been incorporated into the OMOP vocabulary?</strong></p>
+<p><a href="vocabRequest.html">Yes, the vocabulary exists, it just needs to be brought in</a></p>
+<p><a href="contactVocab.html">No, there is no open-source vocabulary for this data element</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/vocabRequest.html b/docs/vocabRequest.html
new file mode 100644
index 0000000..ede123f
--- /dev/null
+++ b/docs/vocabRequest.html
@@ -0,0 +1,469 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Vocabulary Request</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Vocabulary Request</h1>
+
+</div>
+
+
+<p>Okay so you have something you would like to add to the CDM and there is an existing OMOP vocabulary we can bring in to support it. <strong>In this case, please open an issue on the vocabulary github with the details of what you need added</strong> as data elements in the CDM must have a vocabulary in place before they can be implemented. The team will follow up with you should they need additional information.</p>
+<p><a href="https://github.com/OHDSI/Vocabulary-v5.0/issues">Vocabulary GitHub Issue Tracker</a></p>
+<p>Once that request is made, please follow the <a href="cdmRequestProcess.html">CDM Request Process</a> to begin the steps soliciting a change or addition to the model itself. Need more guidance? Consider contacting the CDM Working Group on our <a href="https://github.com/OHDSI/CommonDataModel">GitHub</a> or <a href="https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&amp;tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5">Teams Channel</a>.</p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/vocabY.html b/docs/vocabY.html
new file mode 100644
index 0000000..f32dedb
--- /dev/null
+++ b/docs/vocabY.html
@@ -0,0 +1,468 @@
+<!DOCTYPE html>
+
+<html>
+
+<head>
+
+<meta charset="utf-8" />
+<meta name="generator" content="pandoc" />
+<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
+
+
+
+
+<title>Request Process</title>
+
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
+<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
+<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
+<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
+<style>h1 {font-size: 34px;}
+       h1.title {font-size: 38px;}
+       h2 {font-size: 30px;}
+       h3 {font-size: 24px;}
+       h4 {font-size: 18px;}
+       h5 {font-size: 16px;}
+       h6 {font-size: 12px;}
+       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
+       pre:not([class]) { background-color: white }</style>
+<script src="site_libs/navigation-1.1/tabsets.js"></script>
+<link href="site_libs/highlightjs-9.12.0/default.css" rel="stylesheet" />
+<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
+<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
+<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
+<link rel='shortcut icon' type='image/x-icon' href='favicon.ico' />
+
+<style type="text/css">
+  code{white-space: pre-wrap;}
+  span.smallcaps{font-variant: small-caps;}
+  span.underline{text-decoration: underline;}
+  div.column{display: inline-block; vertical-align: top; width: 50%;}
+  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+  ul.task-list{list-style: none;}
+    </style>
+
+<style type="text/css">code{white-space: pre;}</style>
+<script type="text/javascript">
+if (window.hljs) {
+  hljs.configure({languages: []});
+  hljs.initHighlightingOnLoad();
+  if (document.readyState && document.readyState === "complete") {
+    window.setTimeout(function() { hljs.initHighlighting(); }, 0);
+  }
+}
+</script>
+
+
+
+
+
+
+<link rel="stylesheet" href="style.css" type="text/css" />
+
+
+
+<style type = "text/css">
+.main-container {
+  max-width: 940px;
+  margin-left: auto;
+  margin-right: auto;
+}
+img {
+  max-width:100%;
+}
+.tabbed-pane {
+  padding-top: 12px;
+}
+.html-widget {
+  margin-bottom: 20px;
+}
+button.code-folding-btn:focus {
+  outline: none;
+}
+summary {
+  display: list-item;
+}
+details > summary > p:only-child {
+  display: inline;
+}
+pre code {
+  padding: 0;
+}
+</style>
+
+
+<style type="text/css">
+.dropdown-submenu {
+  position: relative;
+}
+.dropdown-submenu>.dropdown-menu {
+  top: 0;
+  left: 100%;
+  margin-top: -6px;
+  margin-left: -1px;
+  border-radius: 0 6px 6px 6px;
+}
+.dropdown-submenu:hover>.dropdown-menu {
+  display: block;
+}
+.dropdown-submenu>a:after {
+  display: block;
+  content: " ";
+  float: right;
+  width: 0;
+  height: 0;
+  border-color: transparent;
+  border-style: solid;
+  border-width: 5px 0 5px 5px;
+  border-left-color: #cccccc;
+  margin-top: 5px;
+  margin-right: -10px;
+}
+.dropdown-submenu:hover>a:after {
+  border-left-color: #adb5bd;
+}
+.dropdown-submenu.pull-left {
+  float: none;
+}
+.dropdown-submenu.pull-left>.dropdown-menu {
+  left: -100%;
+  margin-left: 10px;
+  border-radius: 6px 0 6px 6px;
+}
+</style>
+
+<script type="text/javascript">
+// manage active state of menu based on current page
+$(document).ready(function () {
+  // active menu anchor
+  href = window.location.pathname
+  href = href.substr(href.lastIndexOf('/') + 1)
+  if (href === "")
+    href = "index.html";
+  var menuAnchor = $('a[href="' + href + '"]');
+
+  // mark it active
+  menuAnchor.tab('show');
+
+  // if it's got a parent navbar menu mark it active as well
+  menuAnchor.closest('li.dropdown').addClass('active');
+
+  // Navbar adjustments
+  var navHeight = $(".navbar").first().height() + 15;
+  var style = document.createElement('style');
+  var pt = "padding-top: " + navHeight + "px; ";
+  var mt = "margin-top: -" + navHeight + "px; ";
+  var css = "";
+  // offset scroll position for anchor links (for fixed navbar)
+  for (var i = 1; i <= 6; i++) {
+    css += ".section h" + i + "{ " + pt + mt + "}\n";
+  }
+  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
+  document.head.appendChild(style);
+});
+</script>
+
+<!-- tabsets -->
+
+<style type="text/css">
+.tabset-dropdown > .nav-tabs {
+  display: inline-table;
+  max-height: 500px;
+  min-height: 44px;
+  overflow-y: auto;
+  border: 1px solid #ddd;
+  border-radius: 4px;
+}
+
+.tabset-dropdown > .nav-tabs > li.active:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
+  content: "&#xe258;";
+  border: none;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
+  content: "";
+  font-family: 'Glyphicons Halflings';
+  display: inline-block;
+  padding: 10px;
+  border-right: 1px solid #ddd;
+}
+
+.tabset-dropdown > .nav-tabs > li.active {
+  display: block;
+}
+
+.tabset-dropdown > .nav-tabs > li > a,
+.tabset-dropdown > .nav-tabs > li > a:focus,
+.tabset-dropdown > .nav-tabs > li > a:hover {
+  border: none;
+  display: inline-block;
+  border-radius: 4px;
+  background-color: transparent;
+}
+
+.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
+  display: block;
+  float: none;
+}
+
+.tabset-dropdown > .nav-tabs > li {
+  display: none;
+}
+</style>
+
+<!-- code folding -->
+
+
+
+
+</head>
+
+<body>
+
+
+<div class="container-fluid main-container">
+
+
+
+
+<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
+  <div class="container">
+    <div class="navbar-header">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+        <span class="icon-bar"></span>
+      </button>
+      <a class="navbar-brand" href="index.html"><div><img src="ohdsi16x16.png"></img> OMOP Common Data Model </div></a>
+    </div>
+    <div id="navbar" class="navbar-collapse collapse">
+      <ul class="nav navbar-nav">
+        <li>
+  <a href="index.html">
+    <span class="fa fa-home"></span>
+     
+  </a>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-landmark"></span>
+     
+    Background
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="background.html">Model Background</a>
+    </li>
+    <li>
+      <a href="cdmRefreshProcess.html">CDM Refresh Process</a>
+    </li>
+    <li>
+      <a href="vocabulary.html">How the Vocabulary is Built</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-list-alt"></span>
+     
+    Conventions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="dataModelConventions.html">General Conventions</a>
+    </li>
+    <li>
+      <a href="ehrObsPeriods.html">Observation Periods for EHR Data</a>
+    </li>
+    <li>
+      <a href="cdmPrivacy.html">Patient Privacy and OMOP</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-history"></span>
+     
+    CDM Versions
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdm30.html">CDM v3.0</a>
+    </li>
+    <li>
+      <a href="cdm60.html">CDM v6.0</a>
+    </li>
+    <li>
+      <a href="cdm53.html">CDM v5.3</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="cdm54.html">CDM v5.4</a>
+        </li>
+        <li>
+          <a href="cdm54Changes.html">Changes from CDM v5.3</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-plus-square"></span>
+     
+    CDM Proposals
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
+    <li>
+      <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
+    </li>
+    <li class="dropdown-submenu">
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
+      <ul class="dropdown-menu" role="menu">
+        <li>
+          <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
+        </li>
+      </ul>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-question"></span>
+     
+    How to
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="download.html">Download the DDL</a>
+    </li>
+    <li>
+      <a href="cdmRPackage.html">Use the CDM R Package</a>
+    </li>
+    <li>
+      <a href="drug_dose.html">Calculate Drug Dose</a>
+    </li>
+  </ul>
+</li>
+<li class="dropdown">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
+    <span class="fa fa-life-ring"></span>
+     
+    Support
+     
+    <span class="caret"></span>
+  </a>
+  <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
+    <li>
+      <a href="faq.html">FAQ</a>
+    </li>
+    <li>
+      <a href="sqlScripts.html">SQL Scripts</a>
+    </li>
+    <li>
+      <a href="contribute.html">Ask a Question</a>
+    </li>
+  </ul>
+</li>
+      </ul>
+      <ul class="nav navbar-nav navbar-right">
+        <li>
+  <a href="https://github.com/OHDSI/CommonDataModel">
+    <span class="fa fa-github"></span>
+     
+  </a>
+</li>
+      </ul>
+    </div><!--/.nav-collapse -->
+  </div><!--/.container -->
+</div><!--/.navbar -->
+
+<div id="header">
+
+
+
+<h1 class="title toc-ignore">Request Process</h1>
+
+</div>
+
+
+<p>Great, so you have a network use case and an existing OMOP Vocabulary! <strong>From here, please follow the steps to formally request a change to the OMOP Common Data Model.</strong></p>
+<p><a href="cdmRequestProcess.html">CDM Request Process</a></p>
+
+
+
+
+</div>
+
+<script>
+
+// add bootstrap table styles to pandoc tables
+function bootstrapStylePandocTables() {
+  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
+}
+$(document).ready(function () {
+  bootstrapStylePandocTables();
+});
+
+
+</script>
+
+<!-- tabsets -->
+
+<script>
+$(document).ready(function () {
+  window.buildTabsets("TOC");
+});
+
+$(document).ready(function () {
+  $('.tabset-dropdown > .nav-tabs > li').click(function () {
+    $(this).parent().toggleClass('nav-tabs-open');
+  });
+});
+</script>
+
+<!-- code folding -->
+
+
+<!-- dynamically load mathjax for compatibility with self-contained -->
+<script>
+  (function () {
+    var script = document.createElement("script");
+    script.type = "text/javascript";
+    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
+    document.getElementsByTagName("head")[0].appendChild(script);
+  })();
+</script>
+
+</body>
+</html>
diff --git a/docs/vocabulary.html b/docs/vocabulary.html
index abc5195..c3a7195 100644
--- a/docs/vocabulary.html
+++ b/docs/vocabulary.html
@@ -13,7 +13,7 @@
 
 <title>How the Vocabulary is Built</title>
 
-<script src="site_libs/header-attrs-2.11/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.13/header-attrs.js"></script>
 <script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link href="site_libs/bootstrap-3.3.5/css/cosmo.min.css" rel="stylesheet" />
@@ -63,6 +63,7 @@ if (window.hljs) {
 
 
 
+
 <link rel="stylesheet" href="style.css" type="text/css" />
 
 
@@ -88,6 +89,9 @@ button.code-folding-btn:focus {
 summary {
   display: list-item;
 }
+details > summary > p:only-child {
+  display: inline;
+}
 pre code {
   padding: 0;
 }
@@ -312,7 +316,7 @@ div.tocify {
 <div class="navbar navbar-default  navbar-fixed-top" role="navigation">
   <div class="container">
     <div class="navbar-header">
-      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
+      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
         <span class="icon-bar"></span>
@@ -328,7 +332,7 @@ div.tocify {
   </a>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-landmark"></span>
      
     Background
@@ -348,7 +352,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-list-alt"></span>
      
     Conventions
@@ -368,7 +372,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-history"></span>
      
     CDM Versions
@@ -386,7 +390,7 @@ div.tocify {
       <a href="cdm53.html">CDM v5.3</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">NEW CDM v5.4</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">NEW CDM v5.4</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="cdm54.html">CDM v5.4</a>
@@ -399,19 +403,22 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-plus-square"></span>
      
-    Proposals
+    CDM Proposals
      
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmRequestProcess.html">How to Propose Changes to the CDM</a>
+    </li>
     <li>
       <a href="https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal">Under Review</a>
     </li>
     <li class="dropdown-submenu">
-      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">Accepted</a>
+      <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Accepted</a>
       <ul class="dropdown-menu" role="menu">
         <li>
           <a href="https://github.com/OHDSI/CommonDataModel/issues/252">Region_concept_id</a>
@@ -421,7 +428,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-question"></span>
      
     How to
@@ -441,7 +448,7 @@ div.tocify {
   </ul>
 </li>
 <li class="dropdown">
-  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
+  <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
     <span class="fa fa-life-ring"></span>
      
     Support
@@ -449,6 +456,9 @@ div.tocify {
     <span class="caret"></span>
   </a>
   <ul class="dropdown-menu" role="menu">
+    <li>
+      <a href="cdmDecisionTree.html">Help! My Data Doesn't Fit!</a>
+    </li>
     <li>
       <a href="faq.html">FAQ</a>
     </li>
diff --git a/inst/csv/OMOP_CDMv5.3_Table_Level.csv b/inst/csv/OMOP_CDMv5.3_Table_Level.csv
index 79400b9..cb1ed0f 100644
--- a/inst/csv/OMOP_CDMv5.3_Table_Level.csv
+++ b/inst/csv/OMOP_CDMv5.3_Table_Level.csv
@@ -1,6 +1,6 @@
-cdmTableName,schema,isRequired,conceptPrefix,measurePersonCompleteness,measurePersonCompletenessThreshold,validation,tableDescription,userGuidance,etlConventions
-PERSON,CDM,Yes,,No,,,"This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information. ",All records in this table are independent Persons.,"All Persons in a database needs one record in this table, unless they fail data quality requirements specified in the ETL. Persons with no Events should have a record nonetheless. If more than one data source contributes Events to the database, Persons must be reconciled, if possible, across the sources to create one single record per Person. The content of the BIRTH_DATETIME must be equivalent to the content of BIRTH_DAY, BIRTH_MONTH and BIRTH_YEAR. "
-OBSERVATION_PERIOD,CDM,Yes,,Yes,0,,"This table contains records which define spans of time during which two conditions are expected to hold: (i) Clinical Events that happened to the Person are recorded in the Event tables, and (ii) absense of records indicate such Events did not occur during this span of time.","For each Person, one or more OBSERVATION_PERIOD records may be present, but they will not overlap or be back to back to each other. Events may exist outside all of the time spans of the OBSERVATION_PERIOD records for a patient, however, absence of an Event outside these time spans cannot be construed as evidence of absence of an Event. Incidence or prevalence rates should only be calculated for the time of active OBSERVATION_PERIOD records. When constructing cohorts, outside Events can be used for inclusion criteria definition, but without any guarantee for the performance of these criteria. Also, OBSERVATION_PERIOD records can be as short as a single day, greatly disturbing the denominator of any rate calculation as part of cohort characterizations. To avoid that, apply minimal observation time as a requirement for any cohort definition.","Each Person needs to have at least one OBSERVATION_PERIOD record, which should represent time intervals with a high capture rate of Clinical Events. Some source data have very similar concepts, such as enrollment periods in insurance claims data. In other source data such as most EHR systems these time spans need to be inferred under a set of assumptions. It is the discretion of the ETL developer to define these assumptions. In many ETL solutions the start date of the first occurrence or the first high quality occurrence of a Clinical Event (Condition, Drug, Procedure, Device, Measurement, Visit) is defined as the start of the OBSERVATION_PERIOD record, and the end date of the last occurrence of last high quality occurrence of a Clinical Event, or the end of the database period becomes the end of the OBSERVATOIN_PERIOD for each Person. If a Person only has a single Clinical Event the OBSERVATION_PERIOD record can be as short as one day. Depending on these definitions it is possible that Clinical Events fall outside the time spans defined by OBSERVATION_PERIOD records. Family history or history of Clinical Events generally are not used to generate OBSERVATION_PERIOD records around the time they are referring to. Any two overlapping or adjacent OBSERVATION_PERIOD records have to be merged into one."
+cdmTableName,schema,isRequired,conceptPrefix,measurePersonCompleteness,measurePersonCompletenessThreshold,validation,tableDescription,userGuidance,etlConventions
+PERSON,CDM,Yes,,No,,,"This table serves as the central identity management for all Persons in the database. It contains records that uniquely identify each person or patient, and some demographic information. ",All records in this table are independent Persons.,"All Persons in a database needs one record in this table, unless they fail data quality requirements specified in the ETL. Persons with no Events should have a record nonetheless. If more than one data source contributes Events to the database, Persons must be reconciled, if possible, across the sources to create one single record per Person. The content of the BIRTH_DATETIME must be equivalent to the content of BIRTH_DAY, BIRTH_MONTH and BIRTH_YEAR. "
+OBSERVATION_PERIOD,CDM,Yes,,Yes,0,,"This table contains records which define spans of time during which two conditions are expected to hold: (i) Clinical Events that happened to the Person are recorded in the Event tables, and (ii) absense of records indicate such Events did not occur during this span of time.","For each Person, one or more OBSERVATION_PERIOD records may be present, but they will not overlap or be back to back to each other. Events may exist outside all of the time spans of the OBSERVATION_PERIOD records for a patient, however, absence of an Event outside these time spans cannot be construed as evidence of absence of an Event. Incidence or prevalence rates should only be calculated for the time of active OBSERVATION_PERIOD records. When constructing cohorts, outside Events can be used for inclusion criteria definition, but without any guarantee for the performance of these criteria. Also, OBSERVATION_PERIOD records can be as short as a single day, greatly disturbing the denominator of any rate calculation as part of cohort characterizations. To avoid that, apply minimal observation time as a requirement for any cohort definition.","Each Person needs to have at least one OBSERVATION_PERIOD record, which should represent time intervals with a high capture rate of Clinical Events. Some source data have very similar concepts, such as enrollment periods in insurance claims data. In other source data such as most EHR systems these time spans need to be inferred under a set of assumptions. It is the discretion of the ETL developer to define these assumptions. In many ETL solutions the start date of the first occurrence or the first high quality occurrence of a Clinical Event (Condition, Drug, Procedure, Device, Measurement, Visit) is defined as the start of the OBSERVATION_PERIOD record, and the end date of the last occurrence of last high quality occurrence of a Clinical Event, or the end of the database period becomes the end of the OBSERVATOIN_PERIOD for each Person. If a Person only has a single Clinical Event the OBSERVATION_PERIOD record can be as short as one day. Depending on these definitions it is possible that Clinical Events fall outside the time spans defined by OBSERVATION_PERIOD records. Family history or history of Clinical Events generally are not used to generate OBSERVATION_PERIOD records around the time they are referring to. Any two overlapping or adjacent OBSERVATION_PERIOD records have to be merged into one."
 VISIT_OCCURRENCE,CDM,No,VISIT_,Yes,0,,"This table contains Events where Persons engage with the healthcare system for a duration of time. They are often also called ""Encounters"". Visits are defined by a configuration of circumstances under which they occur, such as (i) whether the patient comes to a healthcare institution, the other way around, or the interaction is remote, (ii) whether and what kind of trained medical staff is delivering the service during the Visit, and (iii) whether the Visit is transient or for a longer period involving a stay in bed. ","The configuration defining the Visit are described by Concepts in the Visit Domain, which form a hierarchical structure, but rolling up to generally familiar Visits adopted in most healthcare systems worldwide:
 
 - [Inpatient Visit](https://athena.ohdsi.org/search-terms/terms/9201): Person visiting hospital, at a Care Site, in bed, for duration of more than one day, with physicians and other Providers permanently available to deliver service around the clock 
@@ -15,15 +15,15 @@ VISIT_OCCURRENCE,CDM,No,VISIT_,Yes,0,,"This table contains Events where Persons
 - [Ambulance Visit](https://athena.ohdsi.org/search-terms/terms/581478): Person using transportation service for the purpose of initiating one of the other Visits, without a Care Site, within one day, potentially with Providers accompanying the Visit and delivering service
 - [Case Management Visit](https://athena.ohdsi.org/search-terms/terms/38004193): Person interacting with healthcare system, without a Care Site, within a day, with no Providers involved, for administrative purposes
 
-The Visit duration, or 'length of stay', is defined as VISIT_END_DATE - VISIT_START_DATE. For all Visits this is <1 day, except Inpatient Visits and Non-hospital institution Visits. The CDM also contains the VISIT_DETAIL table where additional information about the Visit is stored, for example, transfers between units during an inpatient Visit.","Visits can be derived easily if the source data contain coding systems for Place of Service or Procedures, like CPT codes for well visits. In those cases, the codes can be looked up and mapped to a Standard Visit Concept. Otherwise, Visit Concepts have to be identified in the ETL process. This table will contain 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. Visits can be adjacent to each other, i.e. the end date of one can be identical with the start date of the other. As a consequence, more than one-day Visits or their descendants can be recorded for the same day. Multi-day visits must not overlap, i.e. share days other than start and end days. It is often the case that some logic should be written for how to define visits and how to assign Visit_Concept_Id. For example, in US claims outpatient visits that appear to occur within the time period of an inpatient visit can be rolled into one with the same Visit_Occurrence_Id. In EHR data inpatient visits that are within one day of each other may be strung together to create one visit. It will all depend on the source data and how encounter records should be translated to visit occurrences. Providers can be associated with a Visit through the PROVIDER_ID field, or indirectly through PROCEDURE_OCCURRENCE records linked both to the VISIT and PROVIDER tables."
-VISIT_DETAIL,CDM,No,VISIT_DETAIL_,Yes,0,,The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.,"The configuration defining the Visit Detail is described by Concepts in the Visit Domain, which form a hierarchical structure. The Visit Detail record will have an associated to the Visit Occurrence record in two ways: <br> 1. The Visit Detail record will have the VISIT_OCCURRENCE_ID it is associated to 2. The VISIT_DETAIL_CONCEPT_ID  will be a descendant of the VISIT_CONCEPT_ID for the Visit.","It is not mandatory that the VISIT_DETAIL table be filled in, but if you find that the logic to create VISIT_OCCURRENCE records includes the roll-up of multiple smaller records to create one picture of a Visit then it is a good idea to use VISIT_DETAIL. In EHR data, for example, a Person may be in the hospital but instead of one over-arching Visit their encounters are recorded as times they interacted with a health care provider. A Person in the hospital interacts with multiple providers multiple times a day so the encounters must be strung together using some heuristic (defined by the ETL) to identify the entire Visit. In this case the encounters would be considered Visit Details and the entire Visit would be the Visit Occurrence. In this example it is also possible to use the Vocabulary to distinguish Visit Details from a Visit Occurrence by setting the VISIT_CONCEPT_ID to [9201](https://athena.ohdsi.org/search-terms/terms/9201) and the VISIT_DETAIL_CONCEPT_IDs either to 9201 or its children to indicate where the patient was in the hospital at the time of care."
-CONDITION_OCCURRENCE,CDM,No,CONDITION_,Yes,0,,"This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient. ","Conditions are defined by Concepts from the Condition domain, which form a complex hierarchy. As a result, the same Person with the same disease may have multiple Condition records, which belong to the same hierarchical family. Most Condition records are mapped from diagnostic codes, but recorded signs, symptoms and summary descriptions also contribute to this table. Rule out diagnoses should not be recorded in this table, but in reality their negating nature is not always captured in the source data, and other precautions must be taken when when identifying Persons who should suffer from the recorded Condition. Record all conditions as they exist in the source data. Any decisions about diagnosis/phenotype definitions would be done through cohort specifications. These cohorts can be housed in the [COHORT](https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period) table. Conditions span a time interval from start to end, but are typically recorded as single snapshot records with no end date. The reason is twofold: (i) At the time of the recording the duration is not known and later not recorded, and (ii) the Persons typically cease interacting with the healthcare system when they feel better, which leads to incomplete capture of resolved Conditions. The [CONDITION_ERA](https://ohdsi.github.io/CommonDataModel/cdm531.html#condition_era) table addresses this issue. Family history and past diagnoses ('history of') are not recorded in this table. Instead, they are listed in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table. Codes written in the process of establishing the diagnosis, such as 'question of' of and 'rule out', should not represented here. Instead, they should be recorded in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table, if they are used for analyses. However, this information is not always available.",Source codes and source text fields mapped to Standard Concepts of the Condition Domain have to be recorded here. 
-DRUG_EXPOSURE,CDM,No,DRUG_,Yes,0,,"This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs.","The purpose of records in this table is to indicate an exposure to a certain drug as best as possible. In this context a drug is defined as an active ingredient. Drug Exposures are defined by Concepts from the Drug domain, which form a complex hierarchy. As a result, one DRUG_SOURCE_CONCEPT_ID may map to multiple standard concept ids if it is a combination product. Records in this table represent prescriptions written, prescriptions dispensed, and drugs administered by a provider to name a few. The DRUG_TYPE_CONCEPT_ID can be used to find and filter on these types. This table includes additional information about the drug products, the quantity given, and route of administration.",Information about quantity and dose is provided in a variety of different ways and it is important for the ETL to provide as much information as possible from the data. Depending on the provenance of the data fields may be captured differently i.e. quantity for drugs administered may have a separate meaning from quantity for prescriptions dispensed. If a patient has multiple records on the same day for the same drug or procedures the ETL should not de-dupe them unless there is probable reason to believe the item is a true data duplicate. Take note on how to handle refills for prescriptions written.
-PROCEDURE_OCCURRENCE,CDM,No,PROCEDURE_,Yes,0,,"This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.","Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.","If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here."
-DEVICE_EXPOSURE,CDM,No,DEVICE_,Yes,0,,"The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).","The distinction between Devices or supplies and Procedures are sometimes blurry, but the former are physical objects while the latter are actions, often to apply a Device or supply.",Source codes and source text fields mapped to Standard Concepts of the Device Domain have to be recorded here. 
-MEASUREMENT,CDM,No,MEASUREMENT_,Yes,0,,"The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.","Measurements are predominately lab tests with a few exceptions, like blood pressure or function tests. Results are given in the form of a value and unit combination. When investigating measurements, look for operator_concept_ids (<, >, etc.).","Only records where the source value maps to a Concept in the measurement domain should be included in this table. Even though each Measurement always has a result, the fields VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are not mandatory as often the result is not given in the source data. When the result is not known, the Measurement record represents just the fact that the corresponding Measurement was carried out, which in itself is already useful information for some use cases. For some Measurement Concepts, the result is included in the test. For example, ICD10 CONCEPT_ID [45548980](https://athena.ohdsi.org/search-terms/terms/45548980) 'Abnormal level of unspecified serum enzyme' indicates a Measurement and the result (abnormal). In those situations, the CONCEPT_RELATIONSHIP table in addition to the 'Maps to' record contains a second record with the relationship_id set to 'Maps to value'. In this example, the 'Maps to' relationship directs to [4046263](https://athena.ohdsi.org/search-terms/terms/4046263) 'Enzyme measurement' as well as a 'Maps to value' record to [4135493](https://athena.ohdsi.org/search-terms/terms/4135493) 'Abnormal'."
-OBSERVATION,CDM,No,OBSERVATION_,Yes,0,,"The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.","Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leads to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. Valid Observation Concepts are not enforced to be from any domain though they still should be Standard Concepts.","Records whose Source Values map to any domain besides Condition, Procedure, Drug, Measurement or Device should be stored in the Observation table. Observations can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in VALUE_AS_CONCEPT), a numerical value (VALUE_AS_NUMBER), a verbatim string (VALUE_AS_STRING), or a datetime (VALUE_AS_DATETIME). Even though Observations do not have an explicit result, the clinical fact can be stated separately from the type of Observation in the VALUE_AS_* fields. It is recommended for Observations that are suggestive statements of positive assertion should have a value of 'Yes' (concept_id=4188539), recorded, even though the null value is the equivalent. "
-DEATH,CDM,No,,No,,,"The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data.",,
+The Visit duration, or 'length of stay', is defined as VISIT_END_DATE - VISIT_START_DATE. For all Visits this is <1 day, except Inpatient Visits and Non-hospital institution Visits. The CDM also contains the VISIT_DETAIL table where additional information about the Visit is stored, for example, transfers between units during an inpatient Visit.","Visits can be derived easily if the source data contain coding systems for Place of Service or Procedures, like CPT codes for well visits. In those cases, the codes can be looked up and mapped to a Standard Visit Concept. Otherwise, Visit Concepts have to be identified in the ETL process. This table will contain 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. Visits can be adjacent to each other, i.e. the end date of one can be identical with the start date of the other. As a consequence, more than one-day Visits or their descendants can be recorded for the same day. Multi-day visits must not overlap, i.e. share days other than start and end days. It is often the case that some logic should be written for how to define visits and how to assign Visit_Concept_Id. For example, in US claims outpatient visits that appear to occur within the time period of an inpatient visit can be rolled into one with the same Visit_Occurrence_Id. In EHR data inpatient visits that are within one day of each other may be strung together to create one visit. It will all depend on the source data and how encounter records should be translated to visit occurrences. Providers can be associated with a Visit through the PROVIDER_ID field, or indirectly through PROCEDURE_OCCURRENCE records linked both to the VISIT and PROVIDER tables."
+VISIT_DETAIL,CDM,No,VISIT_DETAIL_,Yes,0,,The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.,"The configuration defining the Visit Detail is described by Concepts in the Visit Domain, which form a hierarchical structure. The Visit Detail record will have an associated to the Visit Occurrence record in two ways: <br> 1. The Visit Detail record will have the VISIT_OCCURRENCE_ID it is associated to 2. The VISIT_DETAIL_CONCEPT_ID  will be a descendant of the VISIT_CONCEPT_ID for the Visit.","It is not mandatory that the VISIT_DETAIL table be filled in, but if you find that the logic to create VISIT_OCCURRENCE records includes the roll-up of multiple smaller records to create one picture of a Visit then it is a good idea to use VISIT_DETAIL. In EHR data, for example, a Person may be in the hospital but instead of one over-arching Visit their encounters are recorded as times they interacted with a health care provider. A Person in the hospital interacts with multiple providers multiple times a day so the encounters must be strung together using some heuristic (defined by the ETL) to identify the entire Visit. In this case the encounters would be considered Visit Details and the entire Visit would be the Visit Occurrence. In this example it is also possible to use the Vocabulary to distinguish Visit Details from a Visit Occurrence by setting the VISIT_CONCEPT_ID to [9201](https://athena.ohdsi.org/search-terms/terms/9201) and the VISIT_DETAIL_CONCEPT_IDs either to 9201 or its children to indicate where the patient was in the hospital at the time of care."
+CONDITION_OCCURRENCE,CDM,No,CONDITION_,Yes,0,,"This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient. ","Conditions are defined by Concepts from the Condition domain, which form a complex hierarchy. As a result, the same Person with the same disease may have multiple Condition records, which belong to the same hierarchical family. Most Condition records are mapped from diagnostic codes, but recorded signs, symptoms and summary descriptions also contribute to this table. Rule out diagnoses should not be recorded in this table, but in reality their negating nature is not always captured in the source data, and other precautions must be taken when when identifying Persons who should suffer from the recorded Condition. Record all conditions as they exist in the source data. Any decisions about diagnosis/phenotype definitions would be done through cohort specifications. These cohorts can be housed in the [COHORT](https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period) table. Conditions span a time interval from start to end, but are typically recorded as single snapshot records with no end date. The reason is twofold: (i) At the time of the recording the duration is not known and later not recorded, and (ii) the Persons typically cease interacting with the healthcare system when they feel better, which leads to incomplete capture of resolved Conditions. The [CONDITION_ERA](https://ohdsi.github.io/CommonDataModel/cdm531.html#condition_era) table addresses this issue. Family history and past diagnoses ('history of') are not recorded in this table. Instead, they are listed in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table. Codes written in the process of establishing the diagnosis, such as 'question of' of and 'rule out', should not represented here. Instead, they should be recorded in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table, if they are used for analyses. However, this information is not always available.",Source codes and source text fields mapped to Standard Concepts of the Condition Domain have to be recorded here. 
+DRUG_EXPOSURE,CDM,No,DRUG_,Yes,0,,"This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs.","The purpose of records in this table is to indicate an exposure to a certain drug as best as possible. In this context a drug is defined as an active ingredient. Drug Exposures are defined by Concepts from the Drug domain, which form a complex hierarchy. As a result, one DRUG_SOURCE_CONCEPT_ID may map to multiple standard concept ids if it is a combination product. Records in this table represent prescriptions written, prescriptions dispensed, and drugs administered by a provider to name a few. The DRUG_TYPE_CONCEPT_ID can be used to find and filter on these types. This table includes additional information about the drug products, the quantity given, and route of administration.",Information about quantity and dose is provided in a variety of different ways and it is important for the ETL to provide as much information as possible from the data. Depending on the provenance of the data fields may be captured differently i.e. quantity for drugs administered may have a separate meaning from quantity for prescriptions dispensed. If a patient has multiple records on the same day for the same drug or procedures the ETL should not de-dupe them unless there is probable reason to believe the item is a true data duplicate. Take note on how to handle refills for prescriptions written.
+PROCEDURE_OCCURRENCE,CDM,No,PROCEDURE_,Yes,0,,"This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.","Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.","If a procedure lasts more than 24 hours, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here."
+DEVICE_EXPOSURE,CDM,No,DEVICE_,Yes,0,,"The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).","The distinction between Devices or supplies and Procedures are sometimes blurry, but the former are physical objects while the latter are actions, often to apply a Device or supply.",Source codes and source text fields mapped to Standard Concepts of the Device Domain have to be recorded here. 
+MEASUREMENT,CDM,No,MEASUREMENT_,Yes,0,,"The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.","Measurements are predominately lab tests with a few exceptions, like blood pressure or function tests. Results are given in the form of a value and unit combination. When investigating measurements, look for operator_concept_ids (<, >, etc.).","Only records where the source value maps to a Concept in the measurement domain should be included in this table. Even though each Measurement always has a result, the fields VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are not mandatory as often the result is not given in the source data. When the result is not known, the Measurement record represents just the fact that the corresponding Measurement was carried out, which in itself is already useful information for some use cases. For some Measurement Concepts, the result is included in the test. For example, ICD10 CONCEPT_ID [45548980](https://athena.ohdsi.org/search-terms/terms/45548980) 'Abnormal level of unspecified serum enzyme' indicates a Measurement and the result (abnormal). In those situations, the CONCEPT_RELATIONSHIP table in addition to the 'Maps to' record contains a second record with the relationship_id set to 'Maps to value'. In this example, the 'Maps to' relationship directs to [4046263](https://athena.ohdsi.org/search-terms/terms/4046263) 'Enzyme measurement' as well as a 'Maps to value' record to [4135493](https://athena.ohdsi.org/search-terms/terms/4135493) 'Abnormal'."
+OBSERVATION,CDM,No,OBSERVATION_,Yes,0,,"The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.","Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leads to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. Valid Observation Concepts are not enforced to be from any domain though they still should be Standard Concepts.","Records whose Source Values map to any domain besides Condition, Procedure, Drug, Measurement or Device should be stored in the Observation table. Observations can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in VALUE_AS_CONCEPT), a numerical value (VALUE_AS_NUMBER), a verbatim string (VALUE_AS_STRING), or a datetime (VALUE_AS_DATETIME). Even though Observations do not have an explicit result, the clinical fact can be stated separately from the type of Observation in the VALUE_AS_* fields. It is recommended for Observations that are suggestive statements of positive assertion should have a value of 'Yes' (concept_id=4188539), recorded, even though the null value is the equivalent. "
+DEATH,CDM,No,,No,,,"The death domain contains the clinical event for how and when a Person dies. A person can have up to one record if the source system contains evidence about the Death, such as: Condition in an administrative claim, status of enrollment into a health plan, or explicit record in EHR data.",,
 NOTE,CDM,No,,Yes,0,,"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. ",,"HL7/LOINC CDO is a standard for consistent naming of documents to support a range of use cases: retrieval, organization, display, and exchange. It guides the creation of LOINC codes for clinical notes. CDO annotates each document with 5 dimensions:
 
 - **Kind of Document**: Characterizes the general structure of the document at a macro level (e.g. Anesthesia Consent)
@@ -34,21 +34,21 @@ NOTE,CDM,No,,Yes,0,,"The NOTE table captures unstructured information that was r
 Each combination of these 5 dimensions rolls up to a unique LOINC code.
 
 According to CDO requirements, only 2 of the 5 dimensions are required to properly annotate a document; Kind of Document and any one of the other 4 dimensions.
-However, not all the permutations of the CDO dimensions will necessarily yield an existing LOINC code. Each of these dimensions are contained in the OMOP Vocabulary under the domain of 'Meas Value' with each dimension represented as a Concept Class. "
-NOTE_NLP,CDM,No,,No,,,The NOTE_NLP table encodes all output of NLP on clinical notes. Each row represents a single extracted term from a note.,,
-SPECIMEN,CDM,No,SPECIMEN_,Yes,0,,The specimen domain contains the records identifying biological samples from a person.,,"Anatomic site is coded at the most specific level of granularity possible, such that higher level classifications can be derived using the Standardized Vocabularies."
+However, not all the permutations of the CDO dimensions will necessarily yield an existing LOINC code. Each of these dimensions are contained in the OMOP Vocabulary under the domain of 'Meas Value' with each dimension represented as a Concept Class. "
+NOTE_NLP,CDM,No,,No,,,The NOTE_NLP table encodes all output of NLP on clinical notes. Each row represents a single extracted term from a note.,,
+SPECIMEN,CDM,No,SPECIMEN_,Yes,0,,The specimen domain contains the records identifying biological samples from a person.,,"Anatomic site is coded at the most specific level of granularity possible, such that higher level classifications can be derived using the Standardized Vocabularies."
 FACT_RELATIONSHIP,CDM,No,,No,,,"The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains. Examples of Fact Relationships include: [Person relationships](https://athena.ohdsi.org/search-terms/terms?domain=Relationship&standardConcept=Standard&page=2&pageSize=15&query=) (parent-child), care site relationships (hierarchical organizational structure of facilities within a health system), indication relationship (between drug exposures and associated conditions), usage relationships (of devices during the course of an associated procedure), or facts derived from one another (measurements derived from an associated specimen).",,"All relationships are directional, and each relationship is represented twice symmetrically within the FACT_RELATIONSHIP table. For example, two persons if person_id = 1 is the mother of person_id = 2 two records are in the FACT_RELATIONSHIP table (all strings in fact concept_id records in the Concept table:
 - Person, 1, Person, 2, parent of
-- Person, 2, Person, 1, child of"
-LOCATION,CDM,No,,No,,,The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites.,,"Each address or Location is unique and is present only once in the table. Locations do not contain names, such as the name of a hospital. In order to construct a full address that can be used in the postal service, the address information from the Location needs to be combined with information from the Care Site."
-CARE_SITE,CDM,No,,No,,,"The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.).",,"Care site is a unique combination of location_id and place_of_service_source_value. Care site does not take into account the provider (human) information such a specialty. Many source data do not make a distinction between individual and institutional providers. The CARE_SITE table contains the institutional providers. If the source, instead of uniquely identifying individual Care Sites, only provides limited information such as Place of Service, generic or ""pooled"" Care Site records are listed in the CARE_SITE table. There can be hierarchical and business relationships between Care Sites. For example, wards can belong to clinics or departments, which can in turn belong to hospitals, which in turn can belong to hospital systems, which in turn can belong to HMOs.The relationships between Care Sites are defined in the FACT_RELATIONSHIP table."
-PROVIDER,CDM,No,,No,,,"The PROVIDER table contains a list of uniquely identified healthcare providers. These are individuals providing hands-on healthcare to patients, such as physicians, nurses, midwives, physical therapists etc.","Many sources do not make a distinction between individual and institutional providers. The PROVIDER table contains the individual providers. If the source, instead of uniquely identifying individual providers, only provides limited information such as specialty, generic or 'pooled' Provider records are listed in the PROVIDER table.",
-PAYER_PLAN_PERIOD,CDM,No,,Yes,0,,"The PAYER_PLAN_PERIOD table captures details of the period of time that a Person is continuously enrolled under a specific health Plan benefit structure from a given Payer. Each Person receiving healthcare is typically covered by a health benefit plan, which pays for (fully or partially), or directly provides, the care. These benefit plans are provided by payers, such as health insurances or state or government agencies. In each plan the details of the health benefits are defined for the Person or her family, and the health benefit Plan might change over time typically with increasing utilization (reaching certain cost thresholds such as deductibles), plan availability and purchasing choices of the Person. The unique combinations of Payer organizations, health benefit Plans and time periods in which they are valid for a Person are recorded in this table.","A Person can have multiple, overlapping, Payer_Plan_Periods in this table. For example, medical and drug coverage in the US can be represented by two Payer_Plan_Periods. The details of the benefit structure of the Plan is rarely known, the idea is just to identify that the Plans are different.",
+- Person, 2, Person, 1, child of"
+LOCATION,CDM,No,,No,,,The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites.,,"Each address or Location is unique and is present only once in the table. Locations do not contain names, such as the name of a hospital. In order to construct a full address that can be used in the postal service, the address information from the Location needs to be combined with information from the Care Site."
+CARE_SITE,CDM,No,,No,,,"The CARE_SITE table contains a list of uniquely identified institutional (physical or organizational) units where healthcare delivery is practiced (offices, wards, hospitals, clinics, etc.).",,"Care site is a unique combination of location_id and place_of_service_source_value. Care site does not take into account the provider (human) information such a specialty. Many source data do not make a distinction between individual and institutional providers. The CARE_SITE table contains the institutional providers. If the source, instead of uniquely identifying individual Care Sites, only provides limited information such as Place of Service, generic or ""pooled"" Care Site records are listed in the CARE_SITE table. There can be hierarchical and business relationships between Care Sites. For example, wards can belong to clinics or departments, which can in turn belong to hospitals, which in turn can belong to hospital systems, which in turn can belong to HMOs.The relationships between Care Sites are defined in the FACT_RELATIONSHIP table."
+PROVIDER,CDM,No,,No,,,"The PROVIDER table contains a list of uniquely identified healthcare providers. These are individuals providing hands-on healthcare to patients, such as physicians, nurses, midwives, physical therapists etc.","Many sources do not make a distinction between individual and institutional providers. The PROVIDER table contains the individual providers. If the source, instead of uniquely identifying individual providers, only provides limited information such as specialty, generic or 'pooled' Provider records are listed in the PROVIDER table.",
+PAYER_PLAN_PERIOD,CDM,No,,Yes,0,,"The PAYER_PLAN_PERIOD table captures details of the period of time that a Person is continuously enrolled under a specific health Plan benefit structure from a given Payer. Each Person receiving healthcare is typically covered by a health benefit plan, which pays for (fully or partially), or directly provides, the care. These benefit plans are provided by payers, such as health insurances or state or government agencies. In each plan the details of the health benefits are defined for the Person or her family, and the health benefit Plan might change over time typically with increasing utilization (reaching certain cost thresholds such as deductibles), plan availability and purchasing choices of the Person. The unique combinations of Payer organizations, health benefit Plans and time periods in which they are valid for a Person are recorded in this table.","A Person can have multiple, overlapping, Payer_Plan_Periods in this table. For example, medical and drug coverage in the US can be represented by two Payer_Plan_Periods. The details of the benefit structure of the Plan is rarely known, the idea is just to identify that the Plans are different.",
 COST,CDM,No,,No,,,"The COST table captures records containing the cost of any medical event recorded in one of the OMOP clinical event tables such as DRUG_EXPOSURE, PROCEDURE_OCCURRENCE, VISIT_OCCURRENCE, VISIT_DETAIL, DEVICE_OCCURRENCE, OBSERVATION or MEASUREMENT.
 
-Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event.","When dealing with summary costs, the cost of the goods or services the provider provides is often not known directly, but derived from the hospital charges multiplied by an average cost-to-charge ratio.","One cost record is generated for each response by a payer. In a claims databases, the payment and payment terms reported by the payer for the goods or services billed will generate one cost record. If the source data has payment information for more than one payer (i.e. primary insurance and secondary insurance payment for one entity), then a cost record is created for each reporting payer. Therefore, it is possible for one procedure to have multiple cost records for each payer, but typically it contains one or no record per entity. Payer reimbursement cost records will be identified by using the PAYER_PLAN_ID field. Drug costs are composed of ingredient cost (the amount charged by the wholesale distributor or manufacturer), the dispensing fee (the amount charged by the pharmacy and the sales tax)."
-DRUG_ERA,CDM,No,,Yes,0,,"A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras.",,The SQL script for generating DRUG_ERA records can be found [here](https://ohdsi.github.io/CommonDataModel/sqlScripts.html#drug_eras).
-DOSE_ERA,CDM,No,,Yes,0,,A Dose Era is defined as a span of time when the Person is assumed to be exposed to a constant dose of a specific active ingredient.,,"Dose Eras will be derived from records in the DRUG_EXPOSURE table and the Dose information from the DRUG_STRENGTH table using a standardized algorithm. Dose Form information is not taken into account. So, if the patient changes between different formulations, or different manufacturers with the same formulation, the Dose Era is still spanning the entire time of exposure to the Ingredient. "
+Each record in the cost table account for the amount of money transacted for the clinical event. So, the COST table may be used to represent both receivables (charges) and payments (paid), each transaction type represented by its COST_CONCEPT_ID. The COST_TYPE_CONCEPT_ID field will use concepts in the Standardized Vocabularies to designate the source (provenance) of the cost data. A reference to the health plan information in the PAYER_PLAN_PERIOD table is stored in the record for information used for the adjudication system to determine the persons benefit for the clinical event.","When dealing with summary costs, the cost of the goods or services the provider provides is often not known directly, but derived from the hospital charges multiplied by an average cost-to-charge ratio.","One cost record is generated for each response by a payer. In a claims databases, the payment and payment terms reported by the payer for the goods or services billed will generate one cost record. If the source data has payment information for more than one payer (i.e. primary insurance and secondary insurance payment for one entity), then a cost record is created for each reporting payer. Therefore, it is possible for one procedure to have multiple cost records for each payer, but typically it contains one or no record per entity. Payer reimbursement cost records will be identified by using the PAYER_PLAN_ID field. Drug costs are composed of ingredient cost (the amount charged by the wholesale distributor or manufacturer), the dispensing fee (the amount charged by the pharmacy and the sales tax)."
+DRUG_ERA,CDM,No,,Yes,0,,"A Drug Era is defined as a span of time when the Person is assumed to be exposed to a particular active ingredient. A Drug Era is not the same as a Drug Exposure: Exposures are individual records corresponding to the source when Drug was delivered to the Person, while successive periods of Drug Exposures are combined under certain rules to produce continuous Drug Eras.",,The SQL script for generating DRUG_ERA records can be found [here](https://ohdsi.github.io/CommonDataModel/sqlScripts.html#drug_eras).
+DOSE_ERA,CDM,No,,Yes,0,,A Dose Era is defined as a span of time when the Person is assumed to be exposed to a constant dose of a specific active ingredient.,,"Dose Eras will be derived from records in the DRUG_EXPOSURE table and the Dose information from the DRUG_STRENGTH table using a standardized algorithm. Dose Form information is not taken into account. So, if the patient changes between different formulations, or different manufacturers with the same formulation, the Dose Era is still spanning the entire time of exposure to the Ingredient. "
 CONDITION_ERA,CDM,No,,Yes,0,,"A Condition Era is defined as a span of time when the Person is assumed to have a given condition. Similar to Drug Eras, Condition Eras are chronological periods of Condition Occurrence. Combining individual Condition Occurrences into a single Condition Era serves two purposes:
 
 - It allows aggregation of chronic conditions that require frequent ongoing care, instead of treating each Condition Occurrence as an independent event.
@@ -56,26 +56,26 @@ CONDITION_ERA,CDM,No,,Yes,0,,"A Condition Era is defined as a span of time when
 For example, consider a Person who visits her Primary Care Physician (PCP) and who is referred to a specialist. At a later time, the Person visits the specialist, who confirms the PCP's original diagnosis and provides the appropriate treatment to resolve the condition. These two independent doctor visits should be aggregated into one Condition Era.",,"Each Condition Era corresponds to one or many Condition Occurrence records that form a continuous interval.
 The condition_concept_id field contains Concepts that are identical to those of the CONDITION_OCCURRENCE table records that make up the Condition Era. In contrast to Drug Eras, Condition Eras are not aggregated to contain Conditions of different hierarchical layers. The SQl Script for generating CONDITION_ERA records can be found [here](https://ohdsi.github.io/CommonDataModel/sqlScripts.html#condition_eras)
 The Condition Era Start Date is the start date of the first Condition Occurrence.
-The Condition Era End Date is the end date of the last Condition Occurrence. Condition Eras are built with a Persistence Window of 30 days, meaning, if no occurrence of the same condition_concept_id happens within 30 days of any one occurrence, it will be considered the condition_era_end_date."
-METADATA,CDM,No,,No,,,The METADATA table contains metadata information about a dataset that has been transformed to the OMOP Common Data Model.,,
-CDM_SOURCE,CDM,No,,No,,,The CDM_SOURCE table contains detail about the source database and the process used to transform the data into the OMOP Common Data Model.,,
+The Condition Era End Date is the end date of the last Condition Occurrence. Condition Eras are built with a Persistence Window of 30 days, meaning, if no occurrence of the same condition_concept_id happens within 30 days of any one occurrence, it will be considered the condition_era_end_date."
+METADATA,CDM,No,,No,,,The METADATA table contains metadata information about a dataset that has been transformed to the OMOP Common Data Model.,,
+CDM_SOURCE,CDM,No,,No,,,The CDM_SOURCE table contains detail about the source database and the process used to transform the data into the OMOP Common Data Model.,,
 CONCEPT,VOCAB,No,,No,,,"The Standardized Vocabularies contains records, or Concepts, that uniquely identify each fundamental unit of meaning used to express clinical information in all domain tables of the CDM. Concepts are derived from vocabularies, which represent clinical information across a domain (e.g. conditions, drugs, procedures) through the use of codes and associated descriptions. Some Concepts are designated Standard Concepts, meaning these Concepts can be used as normative expressions of a clinical entity within the OMOP Common Data Model and within standardized analytics. Each Standard Concept belongs to one domain, which defines the location where the Concept would be expected to occur within data tables of the CDM.
 
 Concepts can represent broad categories (like 'Cardiovascular disease'), detailed clinical elements ('Myocardial infarction of the anterolateral wall') or modifying characteristics and attributes that define Concepts at various levels of detail (severity of a disease, associated morphology, etc.).
 
-Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis. ",,
-VOCABULARY,VOCAB,No,,No,,,The VOCABULARY table includes a list of the Vocabularies collected from various sources or created de novo by the OMOP community. This reference table is populated with a single record for each Vocabulary source and includes a descriptive name and other associated attributes for the Vocabulary.,,
-DOMAIN,VOCAB,No,,No,,,"The DOMAIN table includes a list of OMOP-defined Domains the Concepts of the Standardized Vocabularies can belong to. A Domain defines the set of allowable Concepts for the standardized fields in the CDM tables. For example, the ""Condition"" Domain contains Concepts that describe a condition of a patient, and these Concepts can only be stored in the condition_concept_id field of the CONDITION_OCCURRENCE and CONDITION_ERA tables. This reference table is populated with a single record for each Domain and includes a descriptive name for the Domain.",,
-CONCEPT_CLASS,VOCAB,No,,No,,,"The CONCEPT_CLASS table is a reference table, which includes a list of the classifications used to differentiate Concepts within a given Vocabulary. This reference table is populated with a single record for each Concept Class.",,
-CONCEPT_RELATIONSHIP,VOCAB,No,,No,,,The CONCEPT_RELATIONSHIP table contains records that define direct relationships between any two Concepts and the nature or type of the relationship. Each type of a relationship is defined in the RELATIONSHIP table.,,
-RELATIONSHIP,VOCAB,No,,No,,,The RELATIONSHIP table provides a reference list of all types of relationships that can be used to associate any two concepts in the CONCEPT_RELATIONSHP table.,,
-CONCEPT_SYNONYM,VOCAB,No,,No,,,The CONCEPT_SYNONYM table is used to store alternate names and descriptions for Concepts.,,
+Records in the Standardized Vocabularies tables are derived from national or international vocabularies such as SNOMED-CT, RxNorm, and LOINC, or custom Concepts defined to cover various aspects of observational data analysis. ",,
+VOCABULARY,VOCAB,No,,No,,,The VOCABULARY table includes a list of the Vocabularies collected from various sources or created de novo by the OMOP community. This reference table is populated with a single record for each Vocabulary source and includes a descriptive name and other associated attributes for the Vocabulary.,,
+DOMAIN,VOCAB,No,,No,,,"The DOMAIN table includes a list of OMOP-defined Domains the Concepts of the Standardized Vocabularies can belong to. A Domain defines the set of allowable Concepts for the standardized fields in the CDM tables. For example, the ""Condition"" Domain contains Concepts that describe a condition of a patient, and these Concepts can only be stored in the condition_concept_id field of the CONDITION_OCCURRENCE and CONDITION_ERA tables. This reference table is populated with a single record for each Domain and includes a descriptive name for the Domain.",,
+CONCEPT_CLASS,VOCAB,No,,No,,,"The CONCEPT_CLASS table is a reference table, which includes a list of the classifications used to differentiate Concepts within a given Vocabulary. This reference table is populated with a single record for each Concept Class.",,
+CONCEPT_RELATIONSHIP,VOCAB,No,,No,,,The CONCEPT_RELATIONSHIP table contains records that define direct relationships between any two Concepts and the nature or type of the relationship. Each type of a relationship is defined in the RELATIONSHIP table.,,
+RELATIONSHIP,VOCAB,No,,No,,,The RELATIONSHIP table provides a reference list of all types of relationships that can be used to associate any two concepts in the CONCEPT_RELATIONSHP table.,,
+CONCEPT_SYNONYM,VOCAB,No,,No,,,The CONCEPT_SYNONYM table is used to store alternate names and descriptions for Concepts.,,
 CONCEPT_ANCESTOR,VOCAB,No,,No,,,"The CONCEPT_ANCESTOR table is designed to simplify observational analysis by providing the complete hierarchical relationships between Concepts. Only direct parent-child relationships between Concepts are stored in the CONCEPT_RELATIONSHIP table. To determine higher level ancestry connections, all individual direct relationships would have to be navigated at analysis time. The CONCEPT_ANCESTOR table includes records for all parent-child relationships, as well as grandparent-grandchild relationships and those of any other level of lineage. Using the CONCEPT_ANCESTOR table allows for querying for all descendants of a hierarchical concept. For example, drug ingredients and drug products are all descendants of a drug class ancestor.
 
-This table is entirely derived from the CONCEPT, CONCEPT_RELATIONSHIP and RELATIONSHIP tables.",,
-SOURCE_TO_CONCEPT_MAP,VOCAB,No,,No,,,"The source to concept map table is a legacy data structure within the OMOP Common Data Model, recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a Standard Concept as target_concept_ids that can be used to populate the Common Data Model tables. The SOURCE_TO_CONCEPT_MAP table is no longer populated with content within the Standardized Vocabularies published to the OMOP community.",,
-DRUG_STRENGTH,VOCAB,No,,No,,,The DRUG_STRENGTH table contains structured content about the amount or concentration and associated units of a specific ingredient contained within a particular drug product. This table is supplemental information to support standardized analysis of drug utilization.,,
-COHORT_DEFINITION,VOCAB,No,,No,,,"The COHORT_DEFINITION table contains records defining a Cohort derived from the data through the associated description and syntax and upon instantiation (execution of the algorithm) placed into the COHORT table. Cohorts are a set of subjects that satisfy a given combination of inclusion criteria for a duration of time. The COHORT_DEFINITION table provides a standardized structure for maintaining the rules governing the inclusion of a subject into a cohort, and can store operational programming code to instantiate the cohort within the OMOP Common Data Model.",,
+This table is entirely derived from the CONCEPT, CONCEPT_RELATIONSHIP and RELATIONSHIP tables.",,
+SOURCE_TO_CONCEPT_MAP,VOCAB,No,,No,,,"The source to concept map table is a legacy data structure within the OMOP Common Data Model, recommended for use in ETL processes to maintain local source codes which are not available as Concepts in the Standardized Vocabularies, and to establish mappings for each source code into a Standard Concept as target_concept_ids that can be used to populate the Common Data Model tables. The SOURCE_TO_CONCEPT_MAP table is no longer populated with content within the Standardized Vocabularies published to the OMOP community.",,
+DRUG_STRENGTH,VOCAB,No,,No,,,The DRUG_STRENGTH table contains structured content about the amount or concentration and associated units of a specific ingredient contained within a particular drug product. This table is supplemental information to support standardized analysis of drug utilization.,,
+COHORT_DEFINITION,VOCAB,No,,No,,,"The COHORT_DEFINITION table contains records defining a Cohort derived from the data through the associated description and syntax and upon instantiation (execution of the algorithm) placed into the COHORT table. Cohorts are a set of subjects that satisfy a given combination of inclusion criteria for a duration of time. The COHORT_DEFINITION table provides a standardized structure for maintaining the rules governing the inclusion of a subject into a cohort, and can store operational programming code to instantiate the cohort within the OMOP Common Data Model.",,
 ATTRIBUTE_DEFINITION,VOCAB,No,,No,,,"The ATTRIBUTE_DEFINITION table contains records to define each attribute
 through an associated description and syntax. Attributes are derived elements
 that can be selected or calculated for a subject within a cohort. The
diff --git a/inst/csv/OMOP_CDMv5.4_Table_Level.csv b/inst/csv/OMOP_CDMv5.4_Table_Level.csv
index 3265736..c5bc664 100644
--- a/inst/csv/OMOP_CDMv5.4_Table_Level.csv
+++ b/inst/csv/OMOP_CDMv5.4_Table_Level.csv
@@ -19,7 +19,7 @@ The Visit duration, or 'length of stay', is defined as VISIT_END_DATE - VISIT_ST
 VISIT_DETAIL,CDM,No,VISIT_DETAIL_,Yes,0,,The VISIT_DETAIL table is an optional table used to represents details of each record in the parent VISIT_OCCURRENCE table. A good example of this would be the movement between units in a hospital during an inpatient stay or claim lines associated with a one insurance claim. For every record in the VISIT_OCCURRENCE table there may be 0 or more records in the VISIT_DETAIL table with a 1:n relationship where n may be 0. The VISIT_DETAIL table is structurally very similar to VISIT_OCCURRENCE table and belongs to the visit domain.,"The configuration defining the Visit Detail is described by Concepts in the Visit Domain, which form a hierarchical structure. The Visit Detail record will have an associated to the Visit Occurrence record in two ways: <br> 1. The Visit Detail record will have the VISIT_OCCURRENCE_ID it is associated to 2. The VISIT_DETAIL_CONCEPT_ID  will be a descendant of the VISIT_CONCEPT_ID for the Visit.","It is not mandatory that the VISIT_DETAIL table be filled in, but if you find that the logic to create VISIT_OCCURRENCE records includes the roll-up of multiple smaller records to create one picture of a Visit then it is a good idea to use VISIT_DETAIL. In EHR data, for example, a Person may be in the hospital but instead of one over-arching Visit their encounters are recorded as times they interacted with a health care provider. A Person in the hospital interacts with multiple providers multiple times a day so the encounters must be strung together using some heuristic (defined by the ETL) to identify the entire Visit. In this case the encounters would be considered Visit Details and the entire Visit would be the Visit Occurrence. In this example it is also possible to use the Vocabulary to distinguish Visit Details from a Visit Occurrence by setting the VISIT_CONCEPT_ID to [9201](https://athena.ohdsi.org/search-terms/terms/9201) and the VISIT_DETAIL_CONCEPT_IDs either to 9201 or its children to indicate where the patient was in the hospital at the time of care."
 CONDITION_OCCURRENCE,CDM,No,CONDITION_,Yes,0,,"This table contains records of Events of a Person suggesting the presence of a disease or medical condition stated as a diagnosis, a sign, or a symptom, which is either observed by a Provider or reported by the patient. ","Conditions are defined by Concepts from the Condition domain, which form a complex hierarchy. As a result, the same Person with the same disease may have multiple Condition records, which belong to the same hierarchical family. Most Condition records are mapped from diagnostic codes, but recorded signs, symptoms and summary descriptions also contribute to this table. Rule out diagnoses should not be recorded in this table, but in reality their negating nature is not always captured in the source data, and other precautions must be taken when when identifying Persons who should suffer from the recorded Condition. Record all conditions as they exist in the source data. Any decisions about diagnosis/phenotype definitions would be done through cohort specifications. These cohorts can be housed in the [COHORT](https://ohdsi.github.io/CommonDataModel/cdm531.html#payer_plan_period) table. Conditions span a time interval from start to end, but are typically recorded as single snapshot records with no end date. The reason is twofold: (i) At the time of the recording the duration is not known and later not recorded, and (ii) the Persons typically cease interacting with the healthcare system when they feel better, which leads to incomplete capture of resolved Conditions. The [CONDITION_ERA](https://ohdsi.github.io/CommonDataModel/cdm531.html#condition_era) table addresses this issue. Family history and past diagnoses ('history of') are not recorded in this table. Instead, they are listed in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table. Codes written in the process of establishing the diagnosis, such as 'question of' of and 'rule out', should not represented here. Instead, they should be recorded in the [OBSERVATION](https://ohdsi.github.io/CommonDataModel/cdm531.html#observation) table, if they are used for analyses. However, this information is not always available.",Source codes and source text fields mapped to Standard Concepts of the Condition Domain have to be recorded here. 
 DRUG_EXPOSURE,CDM,No,DRUG_,Yes,0,,"This table captures records about the exposure to a Drug ingested or otherwise introduced into the body. A Drug is a biochemical substance formulated in such a way that when administered to a Person it will exert a certain biochemical effect on the metabolism. Drugs include prescription and over-the-counter medicines, vaccines, and large-molecule biologic therapies. Radiological devices ingested or applied locally do not count as Drugs.","The purpose of records in this table is to indicate an exposure to a certain drug as best as possible. In this context a drug is defined as an active ingredient. Drug Exposures are defined by Concepts from the Drug domain, which form a complex hierarchy. As a result, one DRUG_SOURCE_CONCEPT_ID may map to multiple standard concept ids if it is a combination product. Records in this table represent prescriptions written, prescriptions dispensed, and drugs administered by a provider to name a few. The DRUG_TYPE_CONCEPT_ID can be used to find and filter on these types. This table includes additional information about the drug products, the quantity given, and route of administration.",Information about quantity and dose is provided in a variety of different ways and it is important for the ETL to provide as much information as possible from the data. Depending on the provenance of the data fields may be captured differently i.e. quantity for drugs administered may have a separate meaning from quantity for prescriptions dispensed. If a patient has multiple records on the same day for the same drug or procedures the ETL should not de-dupe them unless there is probable reason to believe the item is a true data duplicate. Take note on how to handle refills for prescriptions written.
-PROCEDURE_OCCURRENCE,CDM,No,PROCEDURE_,Yes,0,,"This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.","Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.","If a procedure lasts more than a day, then it should be recorded as a separate record for each day the procedure occurred, this logic is in lieu of the PROCEDURE_END_DATE, which will be added in a future version of the CDM. When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here."
+PROCEDURE_OCCURRENCE,CDM,No,PROCEDURE_,Yes,0,,"This table contains records of activities or processes ordered by, or carried out by, a healthcare provider on the patient with a diagnostic or therapeutic purpose.","Lab tests are not a procedure, if something is observed with an expected resulting amount and unit then it should be a measurement. Phlebotomy is a procedure but so trivial that it tends to be rarely captured. It can be assumed that there is a phlebotomy procedure associated with many lab tests, therefore it is unnecessary to add them as separate procedures. If the user finds the same procedure over concurrent days, it is assumed those records are part of a procedure lasting more than a day. This logic is in lieu of the procedure_end_date, which will be added in a future version of the CDM.","When dealing with duplicate records, the ETL must determine whether to sum them up into one record or keep them separate. Things to consider are: - Same Procedure - Same PROCEDURE_DATETIME - Same Visit Occurrence or Visit Detail - Same Provider - Same Modifier for Procedures. Source codes and source text fields mapped to Standard Concepts of the Procedure Domain have to be recorded here."
 DEVICE_EXPOSURE,CDM,No,DEVICE_,Yes,0,,"The Device domain captures information about a person's exposure to a foreign physical object or instrument which is used for diagnostic or therapeutic purposes through a mechanism beyond chemical action. Devices include implantable objects (e.g. pacemakers, stents, artificial joints), medical equipment and supplies (e.g. bandages, crutches, syringes), other instruments used in medical procedures (e.g. sutures, defibrillators) and material used in clinical care (e.g. adhesives, body material, dental material, surgical material).","The distinction between Devices or supplies and Procedures are sometimes blurry, but the former are physical objects while the latter are actions, often to apply a Device or supply.",Source codes and source text fields mapped to Standard Concepts of the Device Domain have to be recorded here. 
 MEASUREMENT,CDM,No,MEASUREMENT_,Yes,0,,"The MEASUREMENT table contains records of Measurements, i.e. structured values (numerical or categorical) obtained through systematic and standardized examination or testing of a Person or Person's sample. The MEASUREMENT table contains both orders and results of such Measurements as laboratory tests, vital signs, quantitative findings from pathology reports, etc. Measurements are stored as attribute value pairs, with the attribute as the Measurement Concept and the value representing the result. The value can be a Concept (stored in VALUE_AS_CONCEPT), or a numerical value (VALUE_AS_NUMBER) with a Unit (UNIT_CONCEPT_ID). The Procedure for obtaining the sample is housed in the PROCEDURE_OCCURRENCE table, though it is unnecessary to create a PROCEDURE_OCCURRENCE record for each measurement if one does not exist in the source data. Measurements differ from Observations in that they require a standardized test or some other activity to generate a quantitative or qualitative result. If there is no result, it is assumed that the lab test was conducted but the result was not captured.","Measurements are predominately lab tests with a few exceptions, like blood pressure or function tests. Results are given in the form of a value and unit combination. When investigating measurements, look for operator_concept_ids (<, >, etc.).","Only records where the source value maps to a Concept in the measurement domain should be included in this table. Even though each Measurement always has a result, the fields VALUE_AS_NUMBER and VALUE_AS_CONCEPT_ID are not mandatory as often the result is not given in the source data. When the result is not known, the Measurement record represents just the fact that the corresponding Measurement was carried out, which in itself is already useful information for some use cases. For some Measurement Concepts, the result is included in the test. For example, ICD10 CONCEPT_ID [45548980](https://athena.ohdsi.org/search-terms/terms/45548980) 'Abnormal level of unspecified serum enzyme' indicates a Measurement and the result (abnormal). In those situations, the CONCEPT_RELATIONSHIP table in addition to the 'Maps to' record contains a second record with the relationship_id set to 'Maps to value'. In this example, the 'Maps to' relationship directs to [4046263](https://athena.ohdsi.org/search-terms/terms/4046263) 'Enzyme measurement' as well as a 'Maps to value' record to [4135493](https://athena.ohdsi.org/search-terms/terms/4135493) 'Abnormal'."
 OBSERVATION,CDM,No,OBSERVATION_,Yes,0,,"The OBSERVATION table captures clinical facts about a Person obtained in the context of examination, questioning or a procedure. Any data that cannot be represented by any other domains, such as social and lifestyle facts, medical history, family history, etc. are recorded here.","Observations differ from Measurements in that they do not require a standardized test or some other activity to generate clinical fact. Typical observations are medical history, family history, the stated need for certain treatment, social circumstances, lifestyle choices, healthcare utilization patterns, etc. If the generation clinical facts requires a standardized testing such as lab testing or imaging and leads to a standardized result, the data item is recorded in the MEASUREMENT table. If the clinical fact observed determines a sign, symptom, diagnosis of a disease or other medical condition, it is recorded in the CONDITION_OCCURRENCE table. Valid Observation Concepts are not enforced to be from any domain though they still should be Standard Concepts.","Records whose Source Values map to any domain besides Condition, Procedure, Drug, Measurement or Device should be stored in the Observation table. Observations can be stored as attribute value pairs, with the attribute as the Observation Concept and the value representing the clinical fact. This fact can be a Concept (stored in VALUE_AS_CONCEPT), a numerical value (VALUE_AS_NUMBER), a verbatim string (VALUE_AS_STRING), or a datetime (VALUE_AS_DATETIME). Even though Observations do not have an explicit result, the clinical fact can be stated separately from the type of Observation in the VALUE_AS_* fields. It is recommended for Observations that are suggestive statements of positive assertion should have a value of 'Yes' (concept_id=4188539), recorded, even though the null value is the equivalent. "
diff --git a/rmd/.Rapp.history b/rmd/.Rapp.history
index 9052497..85b7cd5 100644
--- a/rmd/.Rapp.history
+++ b/rmd/.Rapp.history
@@ -1,2 +1,4 @@
 setwd("/Users/clairblacketer/Documents/Github/CommonDataModel/rmd")#
 rmarkdown::render_site()
+setwd("/Users/clairblacketer/Documents/Github/CommonDataModel/rmd")#
+rmarkdown::render_site()
diff --git a/rmd/_site.yml b/rmd/_site.yml
index 27f67cb..680ecfd 100644
--- a/rmd/_site.yml
+++ b/rmd/_site.yml
@@ -48,9 +48,11 @@ navbar:
               href: cdm54.html
             - text: "Changes from CDM v5.3"
               href: cdm54Changes.html
-    - text: "Proposals"
+    - text: "CDM Proposals"
       icon: fa-plus-square
       menu:
+        - text: "How to Propose Changes to the CDM"
+          href: cdmRequestProcess.html
         - text: "Under Review"
           href: https://github.com/OHDSI/CommonDataModel/issues?q=is%3Aopen+is%3Aissue+label%3AProposal
         - text: "Accepted"
@@ -69,6 +71,8 @@ navbar:
     - text: "Support"
       icon: fa-life-ring
       menu:
+        - text: "Help! My Data Doesn't Fit!"
+          href: cdmDecisionTree.html
         - text: "FAQ"
           href: faq.html
         - text: "SQL Scripts"
diff --git a/rmd/cdm53.Rmd b/rmd/cdm53.Rmd
index 8daccee..737d50d 100644
--- a/rmd/cdm53.Rmd
+++ b/rmd/cdm53.Rmd
@@ -92,9 +92,9 @@ for(tb in tables) {
  
   print(kable(x = loopTable, align = "l", row.names = FALSE, format = "html", escape = FALSE) %>%
            column_spec(1, bold = T) %>%
-           column_spec(2, width = "3in", include_thead = T) %>%
-           column_spec(3, width = "4in", include_thead = T) %>%
-           column_spec(4:9, width = "1in", include_thead = T) %>%
+           # column_spec(2, width = "3in", include_thead = T) %>%
+           # column_spec(3, width = "4in", include_thead = T) %>%
+           # column_spec(4:9, width = "1in", include_thead = T) %>%
            kable_styling(c("condensed","hover"), position = "center", full_width = T, font_size = 13))
          
   
diff --git a/rmd/cdm54.Rmd b/rmd/cdm54.Rmd
index 5b9cc0f..b61f3cf 100644
--- a/rmd/cdm54.Rmd
+++ b/rmd/cdm54.Rmd
@@ -108,9 +108,9 @@ for(tb in tables) {
  
   print(kable(x = loopTable, align = "l", row.names = FALSE, format = "html", escape = FALSE) %>%
            column_spec(1, bold = T) %>%
-           column_spec(2, width = "3in", include_thead = T) %>%
-           column_spec(3, width = "4in", include_thead = T) %>%
-           column_spec(4:9, width = "1in", include_thead = T) %>%
+           # column_spec(2, width = "3in", include_thead = T) %>%
+           # column_spec(3, width = "4in", include_thead = T) %>%
+           # column_spec(4:9, width = "1in", include_thead = T) %>%
            kable_styling(c("condensed","hover"), position = "center", full_width = T, font_size = 13))
          
   
diff --git a/rmd/cdm60.Rmd b/rmd/cdm60.Rmd
index 7e8bebe..5bffe5c 100644
--- a/rmd/cdm60.Rmd
+++ b/rmd/cdm60.Rmd
@@ -104,9 +104,9 @@ for(tb in tables) {
  
   print(kable(x = loopTable, align = "l", row.names = FALSE, format = "html") %>% 
            column_spec(1, bold = T) %>%
-           column_spec(2, width = "3in", include_thead = T) %>%
-           column_spec(3, width = "4in", include_thead = T) %>%
-           column_spec(4:9, width = "1in", include_thead = T) %>%
+           # column_spec(2, width = "3in", include_thead = T) %>%
+           # column_spec(3, width = "4in", include_thead = T) %>%
+           # column_spec(4:9, width = "1in", include_thead = T) %>%
            kable_styling(c("condensed","hover"), position = "center", full_width = T, font_size = 13)) 
          
   
diff --git a/rmd/cdmDecisionTree.Rmd b/rmd/cdmDecisionTree.Rmd
new file mode 100644
index 0000000..662c035
--- /dev/null
+++ b/rmd/cdmDecisionTree.Rmd
@@ -0,0 +1,13 @@
+---
+title: '<div><img src="ohdsi40x40.png"></img> CDM Request Decision Tree </div>'
+output: 
+  html_document
+---
+
+If you have arrived to this page then you must be thinking **HELP! I have some data that doesn't fit in the CDM!** Never fear as this handy guide will point you in the right direction and all you have to do is answer a few questions. 
+
+**First things first, do you think you will need to change the OMOP Common Data Model itself or are you solely looking for vocabulary support?** 
+
+[I think I need to change the OMOP CDM](networkUseCase.html)
+
+[I need vocabulary support](vocabN.html)
diff --git a/rmd/cdmRefreshProcess.Rmd b/rmd/cdmRefreshProcess.Rmd
index 261d88a..f12f178 100644
--- a/rmd/cdmRefreshProcess.Rmd
+++ b/rmd/cdmRefreshProcess.Rmd
@@ -8,29 +8,31 @@ output:
 
 The OMOP Common Data Model is managed by the OHDSI CDM Working Group. The formal remit of the CDM Working Group (WG) is to hear proposals for change, ratifying only those with valid use cases and data to support them. Then, once ratified, these proposals are incorporated into the next version of the CDM. In the past, this was done by the WG alone. The group would invite others from around the community to present use cases for change and suggestions for improvement. The WG would then vote on the proposals and a new CDM version would be released after a certain period of time or if enough proposals were voted in. This approach worked when the community was smaller but as it is growing rapidly the CDM WG needed to adapt the refresh cycle such that everyone has an opportunity to weigh in on the proposed changes. 
 
+Looking to make a change or addition to the OMOP CDM? Please answer the questions in the [decision tree](cdmDecisionTree.html) to point you in the right direction.
+
 ## CDM Refresh Cycle
 
 ![](images/CDM_refresh_cycle.png)
 
-### 1. Define New Version [Completed for v5.4]
+### 1. Define New Version 
 
-The image above describes the new CDM refresh cycle. It begins with **defining a new version**. This has been completed for the current cycle. Issues and proposals on the github were considered during a 4-hour workshop where it was decided the next CDM version will be CDM v5.4, building off of CDM v5.3. The group then participated in a rapid-fire voting activity to identify which changes should be incorporated into CDM v5.4. Any items that were not unanimously agreed upon were then discussed in small groups to hone the proposal and suggestions were presented back to the group. The final roadmap for CDM v5.4 can be found [here](https://github.com/OHDSI/CommonDataModel/projects/3).
+The image above describes the new CDM refresh cycle. It begins with **defining a new version**. Proposals are heard over the course of a year according to the [CDM Request Process](cdmRequestProcess.html) and the ratified changes are added to the roadmap until such time that there are enough updates to warrant a new version of the model. 
 
-Looking to open a proposal to change or augment the CDM? Please open an [issue](https://github.com/OHDSI/CommonDataModel/issues) and use the **proposal template**. 
+Looking to open a proposal to change or augment the CDM? Please follow the questions in the [decision tree](cdmDecisionTree.html) to help you determine what you will need. 
 
-### 2. Sign off from Work Groups [Completed for v5.4]
+### 2. Sign off from Work Groups 
 
 Each member of the CDM WG is a liaison for another workgroup in the community. They are responsible for presenting the proposed changes to the CDM and collecting the feedback. This has resulted in very helpful suggestions from the EHR, Data Quality, Device, HADES, and ACHILLES groups. This outreach has proven to be very effective and should result in a very stable version.
 
-### 3. Release DDLs
+### 3. Release DDLs 
 
-After all changes and suggestions are agreed upon by the community and work groups the next step is to generate the DDLs. The CDM WG hosted a hackathon on August 18-19, 2021. During this time the group created an R package to automatically generate the DDLs and the code to instantiate an empty CDM instance. Changes were made to v5.3 to generate v5.4 and the repository was refactored. 
+After all changes and suggestions are agreed upon by the community and work groups the next step is to generate the DDLs. For example, the CDM WG hosted a hackathon on August 18-19, 2021. During this time the group created an R package to automatically generate the DDLs and the code to instantiate an empty CDM instance. Changes were made to v5.3 to generate v5.4 and the repository was refactored. 
 
-### 4. Software Update
+### 4. Software Update 
 
 There will be period of time once the DDLs are ready to allow the software and methods developers to prepare for the official release of the CDM. This is meant to serve as a buffer so that once the community starts adopting the new model, the tools and methods will be ready to support it. 
 
-### 5. Community Support
+### 5. Community Support 
 
 This is the final stage of the CDM refresh cycle. Once the DDLs are ready and the software and tools supports the new version, the CDM WG will work to help the community convert their data to the new model. 
 
@@ -39,7 +41,7 @@ This is the final stage of the CDM refresh cycle. Once the DDLs are ready and th
 
 The CDM working group meets the first and third Tuesday of the month. See below for links to the meetings. 
 
-**Every first Tuesday of the month at 1pm est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d)   
+**Every first Tuesday of the month at 10am est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d)   
 
 **Every third Tuesday of the month at 1pm est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1611000164347?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%223c193b7f-c2ab-4bcf-b88c-f89a6b1fba38%22%7d)
 
diff --git a/rmd/cdmRequestProcess.Rmd b/rmd/cdmRequestProcess.Rmd
new file mode 100644
index 0000000..9bf3582
--- /dev/null
+++ b/rmd/cdmRequestProcess.Rmd
@@ -0,0 +1,91 @@
+---
+title: '<div><img src="ohdsi40x40.png"></img> How to Request Changes to the CDM </div>'
+output: 
+  html_document:
+        toc: TRUE
+        toc_float: TRUE
+---
+
+Are you in the right place? Please answer the questions in the [decision tree](cdmDecisionTree.html) prior to beginning a CDM Request to make sure you aren't missing something. 
+
+As OHDSI is an open-source community working towards developing a Common Data Model that fulfills the needs of its users, it is often the case that changes need to be made to the model as the community and its research continues to mature. However, the number of people, institutions, and initiatives that rely on the OMOP CDM to advance the science of observational health has grown dramatically since its inception in 2015. Therefore, care must be taken when considering any update to the model, big or small. This document outlines the process that should be taken to ratify a change to the CDM. 
+
+**If you would like guidance prior to starting this process, consider contacting us on our [GitHub](https://github.com/OHDSI/CommonDataModel) or [Teams Channel](https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5).**
+
+
+### Scope
+
+- What kind of changes? 
+  - Minor, e.g. new field in existing table
+  - Major, e.g. breaking changes, additional tables
+- Who can propose changes?
+  - Individuals, OHDSI working groups, organizations
+
+## Step 1: Proposal
+
+Once a group or organization has decided on the update they would like made to the model, they must produce a document including the following:
+
+1. A clear description of the change or addition including the User Guide and ETL Conventions in the same structure as what is present on the website for every table and field currently in the CDM.
+2. A clearly defined use case noting why the latest version of the OMOP CDM fails to adequately address said use case. This should include describing what you have already tried with the latest version of the OMOP CDM and why it does not meet your needs.
+3. An example of how the requested change or addition will be used in practice. This can be in the form of sample data, SQL code, a diagram, or text. The proposal can optionally include suggestions as to how other OHDSI tools (Achilles, DataQualityDashboard, Atlas, etc.) should work with your change or addition. 
+
+Once the document is ready to submit, please email [CDM Proposals - Workgroup - Common Data Model](mailto:a58abde7.ohdsi.org@amer.teams.ms). This will go directly to a separate channel in the OHDSI Teams environment that is available to all members of the CDM Working Group.
+After submitting your document with your proposal to email listed above, someone in the OMOP CDM Working Group will respond to you within 2 weeks. The potential outcomes are as follows: 
+
+- Proposal merits further review (move on to next steps)
+- Proposal is not ready for workgroup review due to one or more factors
+  - Incomplete
+  - Insufficiently aligned with the OMOP framework
+  - Poorly described use case
+
+## Step 2: Initial Presentation
+
+Should your proposals merit further review, the OMOP CDM Working Group will reach out to you to schedule a time for you to present your case at an upcoming meeting. You will be given 15-30 minutes to present your document and you can include anything you feel will help illustrate the need and your potential solution. The group will then discuss, ask questions, and potentially offer other solutions. Depending on the nature of the request, this may go over multiple sessions and you may be asked to make changes to your initial design. At the end of this process your proposal will then be put to consensus in the CDM WG. If the group decides no, they will give feedback describing why they did not feel your proposal should be accepted at this time. If the group decides yes, you move on to step 3. 
+
+**Potential Decision Criteria:**
+
+- If the change is foundational to OHDSI tools, then the proposal will be put to the larger community open to public comment
+- How generalizable is your change? Can it be readily applied to other use cases?
+- Are the proposed changes/additions well designed from a modeling perspective? Do they follow the existing OMOP CDM conventions?
+- What are the consequences of the change? Are they potentially breaking changes or are they just changes to existing conventions? Will they require the remapping of existing OMOP datasources?
+- How complicated is your change? Is it an addition of a field or multiple tables?
+
+## Step 3: Preliminary Decision
+
+If the proposal is accepted in the preliminary decision, then a branch will be created in the CommonDataModel repository, based on the latest version of the OMOP CDM in use (currently v5.4). It will then be your responsibility to apply the change programmatically in this branch.  This should include:
+
+- Updating the CSV file with the CDM specification, including the User Guide and ETL Conventions documentation
+- Generating the DDL files with the change
+- Testing the new DDL files in at least one supported environment
+
+Once the DDLs with the proposed change are created and tested, you should then ETL some data (either real or synthetic) into the new table/fields. Then, an example cohort should be created that utilizes the change or addition and clearly displays how it can be used in a real study. It is expected that during this stage the proposal will change as you work through your idea in a tangible environment.   
+
+**Potential Decision Criteria:**
+
+- How would you evaluate the quality of this new field/table?
+- What characterizations would you perform?
+- How would you perform a study using this new feature?
+
+**Potential Outcomes:**
+
+- Proposal demonstrates merit for further consideration as:
+  - a core data model change (move on to next steps)
+  - an extension (how do we deal with these/do we have ownership of them?)
+- Proposal does not demonstrate merit for further consideration at this time, and:
+  - recommend as a LOCAL extension
+  - recommend a different course
+
+## Step 4: Final Presentation
+
+After generating, testing, and implementing your proposal in a real-world environment the CDM working group will invite you again to present your findings in another 15-30 minute presentation. This should include learnings from the exercise and any updates made to the initial proposal. 
+
+## Step 5: Final Decision
+
+At this point, the working group liaisons will also take the proposal to other groups to elicit feedback. Then the CDM working group will vote and give a final decision on the proposed change. If ratified, the branch in the repository will be merged into the develop branch to be included in a next version of the OMOP Common Data Model.   
+
+The change should initiate requests for features in tools. The end of this process should be a trigger for using the new feature as per the use case. The group should also produce at least one query for the query library on how to work with the new addition/change. 
+
+### Resources
+
+“Implementing & adopting a customized OMOP Common Data Model” (Melany Philofsky, OHDSI Symposium 2021) https://www.ohdsi.org/2021-global-symposium-showcase-18/
+
diff --git a/rmd/contactVocab.Rmd b/rmd/contactVocab.Rmd
new file mode 100644
index 0000000..d69af85
--- /dev/null
+++ b/rmd/contactVocab.Rmd
@@ -0,0 +1,10 @@
+---
+title: "Contact the Vocab Team"
+output: html_document
+---
+
+Okay so you have something you would like to add to the CDM but there is not an existing OMOP vocabulary nor an open-source vocabulary we can bring in to support it. **In this case, please contact the vocabulary team on next steps** as data elements in the CDM must have a vocabulary in place before they can be implemented. 
+
+[Vocabulary Teams Channel](https://teams.microsoft.com/l/channel/19%3a31208179438d45749ff484124e7b1e5e%40thread.tacv2/Vocabulary%2520Subgroup?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5)
+
+Once you come to consensus with the vocabulary team regarding your needs, please follow the [CDM Request Process](cdmRequestProcess.html) to begin the steps soliciting a change or addition to the model itself. Need more guidance? Consider contacting the CDM Working Group on our [GitHub](https://github.com/OHDSI/CommonDataModel) or [Teams Channel](https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5).
diff --git a/rmd/faq.Rmd b/rmd/faq.Rmd
index fcddd8d..49f96c7 100644
--- a/rmd/faq.Rmd
+++ b/rmd/faq.Rmd
@@ -1,11 +1,12 @@
 ---
 title: "OMOP CDM Frequently Asked Questions"
 output: 
-    html_document
-        
+  html_document:
+    toc: yes
+    toc_depth: 5
+    toc_float: yes
 ---
 
-
 **1. I understand that the common data model (CDM) is a way of organizing disparate data sources into the same relational database design, but how can it be effective since many databases use different coding schemes?**
 
 During the extract, transform, load (ETL) process of converting a data source into the OMOP common data model, we standardize the structure (e.g. tables, fields, data types), conventions (e.g. rules that govern how source data should be represented), and content (e.g. what common vocabularies are used to speak the same language across clinical domains).  The common data model preserves all source data, including the original source vocabulary codes, but adds the standardized vocabularies to allow for network research across the entire OHDSI research community.
@@ -171,3 +172,24 @@ Queries are written in R and SQL. The [SqlRender](https://github.com/OHDSI/sqlre
 OHDSI runs as a distributed data network.  All analyses are publicly available and can be downloaded to run at each site. The packages can be run locally and, at the data partner’s discretion, aggregate results can be shared with the study coordinator.
 
 Data partners can also make use of one of OHDSI's open-source tools called [ARACHNE](https://github.com/OHDSI/arachne), a tool to facilitate distributed network analytics against the OMOP CDM.
+
+## Recommended System Requirements
+
+It is difficult to recommend what technical capabilities a site needs to set up an ETL because it is heavily dependent on the amount of data they have and how they plan to use it. Here are some examples of options that have worked well for small to medium organizations and large organizations:
+
+**Small-to-Medium Organization**
+
+- CDM size is 100MB to several GBs
+- Vocab ~20GB
+- Results < 500 MB
+- Recommend 
+  - Server class machine disk >= 250GB (SSD preferred), >= 4 cores, >= 32GB RAM
+  
+**Large Organization**
+
+- CDM size is 12GB to several TBs
+- Vocab ~20GB
+- Results < 500 MB
+- Recommend 
+  - Cloud-based infrastructure like multiple AWS Redshift clusters, for example:
+  - ![](images/AWS_clusters.png)
diff --git a/rmd/images/AWS_clusters.png b/rmd/images/AWS_clusters.png
new file mode 100644
index 0000000..17add03
Binary files /dev/null and b/rmd/images/AWS_clusters.png differ
diff --git a/rmd/index.Rmd b/rmd/index.Rmd
index c2d1059..1e26260 100644
--- a/rmd/index.Rmd
+++ b/rmd/index.Rmd
@@ -46,13 +46,12 @@ The CDM is managed by the OHDSI CDM Working Group. If you would like to join our
 
 The CDM working group meets the first and third Tuesday of the month. See below for links to the meetings. 
 
-**Every first Tuesday of the month at 1pm est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d)   
+**Every first Tuesday of the month at 10am est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1601910741972?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%2281c21b6d-448d-4634-abbc-6b0962d1138a%22%7d)   
 
 **Every third Tuesday of the month at 1pm est** [Teams Meeting](https://teams.microsoft.com/l/meetup-join/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/1611000164347?context=%7b%22Tid%22%3a%22a30f0094-9120-4aab-ba4c-e5509023b2d5%22%2c%22Oid%22%3a%223c193b7f-c2ab-4bcf-b88c-f89a6b1fba38%22%7d)
 
 
-**Note** If you do you have access to the OHDSI Teams Tenet, either contact Clair Blacketer at mblacke@its.jnj.com or fill out [this form]
-(https://forms.office.com/Pages/ResponsePage.aspx?id=lAAPoyCRq0q6TOVQkCOy1ZyG6Ud_r2tKuS0HcGnqiQZUOVJFUzBFWE1aSVlLN0ozR01MUVQ4T0RGNyQlQCN0PWcu) and check "Common Data Model"
+**Note** If you do you have access to the OHDSI Teams Tenet, either contact Clair Blacketer at mblacke@its.jnj.com or fill out [this form](https://forms.office.com/Pages/ResponsePage.aspx?id=lAAPoyCRq0q6TOVQkCOy1ZyG6Ud_r2tKuS0HcGnqiQZUOVJFUzBFWE1aSVlLN0ozR01MUVQ4T0RGNyQlQCN0PWcu) and check "Common Data Model"
 
 ### CDM WG Important Links
 
diff --git a/rmd/leaveAsIs.Rmd b/rmd/leaveAsIs.Rmd
new file mode 100644
index 0000000..e4de014
--- /dev/null
+++ b/rmd/leaveAsIs.Rmd
@@ -0,0 +1,6 @@
+---
+title: "Leave As Is"
+output: html_document
+---
+
+Okay, so you do not have a network use case but multiple collaborators have access to the element you are interested in adding to the CDM. **In this circumstance, the CDM Working Group suggests leaving the model as-is.** Without a network use case there is no need to augment the data model. If this is something you need for your work, consider a [local change](localChange.html) or a model extension. 
diff --git a/rmd/localChange.Rmd b/rmd/localChange.Rmd
new file mode 100644
index 0000000..b28d20f
--- /dev/null
+++ b/rmd/localChange.Rmd
@@ -0,0 +1,6 @@
+---
+title: "Local Change"
+output: html_document
+---
+
+Since you do not have a network use case and this element is specific to your data source, **feel free to create a local change to your instance of the OMOP Common Data Model.** Augmenting the model at your institution for administrative purposes or other in-house needs is totally acceptable with the understanding that any local changes cannot and should not be relied upon in network studies or supported by the open-source tools.  
diff --git a/rmd/networkUseCase.Rmd b/rmd/networkUseCase.Rmd
new file mode 100644
index 0000000..690b7dd
--- /dev/null
+++ b/rmd/networkUseCase.Rmd
@@ -0,0 +1,10 @@
+---
+title: "Network Use Case"
+output: html_document
+---
+
+Alright, so you think you might need to change the OMOP Common Data Model. **Do you have a documented network use case for this data need? This could take the form of an upcoming study or a convention for how to store information.** In this scenario, at least two or more collaborators with data to contribute constitute a network need. 
+
+[Yes, I have a network use case](useCaseY.html)
+
+[No, I do not have a network use case](useCaseN.html)
diff --git a/rmd/oncology.Rmd b/rmd/oncology.Rmd
index 0d554bb..5eaa96e 100644
--- a/rmd/oncology.Rmd
+++ b/rmd/oncology.Rmd
@@ -66,13 +66,13 @@ for(tb in tables) {
   loopTable <- subset(cdmSpecsClean, `CDM Table` == tb)
   loopTable <- subset(loopTable, select = -c(1))
  
-  print(kable(x = loopTable, align = "l", row.names = FALSE, format = "html") %>% 
+   print(kable(x = loopTable, align = "l", row.names = FALSE, format = "html", escape = FALSE) %>%
            column_spec(1, bold = T) %>%
-           column_spec(2, width = "3in", include_thead = T) %>%
-           column_spec(3, width = "4in", include_thead = T) %>%
-           column_spec(4:10, width = "1in", include_thead = T) %>%
-           kable_styling(c("condensed","hover"), position = "center", full_width = T, font_size = 13)) 
-         
+           # column_spec(2, width = "3in", include_thead = T) %>%
+           # column_spec(3, width = "4in", include_thead = T) %>%
+           # column_spec(4:9, width = "1in", include_thead = T) %>%
+           kable_styling(c("condensed","hover"), position = "center", full_width = T, font_size = 13))
+        
   
   }
 
diff --git a/rmd/sqlScripts.Rmd b/rmd/sqlScripts.Rmd
index 929c86c..1b6a3c7 100644
--- a/rmd/sqlScripts.Rmd
+++ b/rmd/sqlScripts.Rmd
@@ -232,178 +232,172 @@ GROUP BY person_id
 
 ### Drug Eras
 
-If the DRUG_EXPOSURE table is populated this script will string together periods of time that a person is exposed to an active drug ingredient, allowing for 30 gaps in between. It will then insert the resulting era records into the DRUG_ERA table. **NOTE** This query only works with 5.3 and below.
+If the DRUG_EXPOSURE table is populated this script will string together periods of time that a person is exposed to an active drug ingredient, allowing for 30 gaps in between. It will then insert the resulting era records into the DRUG_ERA table. **NOTE** This query only works with the **version 5** series and below.
 
 ```{sql eval = FALSE, echo = TRUE}
 
-/****************************************************
-OHDSI-SQL File Instructions
------------------------------
- 1. Set parameter name of schema that contains CDMv4 instance
-    (@SOURCE_CDMV4, @SOURCE_CDMV4_SCHEMA)
- 2. Set parameter name of schema that contains CDMv5 instance
-    (@TARGET_CDMV5, @TARGET_CDMV5_SCHEMA)
- 3. Run this script through SqlRender to produce a script that will work in your
-    source dialect. SqlRender can be found here: https://github.com/OHDSI/SqlRender
- 4. Run the script produced by SQL Render on your target RDBDMS.
-<RDBMS> File Instructions
--------------------------
- 1. This script will hold a number of placeholders for your CDM V4 and CDMV5
-    database/schema. In order to make this file work in your environment, you
-	should plan to do a global "FIND AND REPLACE" on this file to fill in the
-	file with values that pertain to your environment. The following are the
-	tokens you should use when doing your "FIND AND REPLACE" operation:
-	
-     [CDM]
-	 [CDM].[CDMSCHEMA]
-	
-*********************************************************************************/
-/* SCRIPT PARAMETERS */
-
-	
-	{DEFAULT @TARGET_CDMV5 = '[CDM]' } -- The target CDMv5 database name
-	{DEFAULT @TARGET_CDMV5_SCHEMA = '[CDM].[CDMSCHEMA]' } -- the target CDMv5 database plus schema
-
-USE @TARGET_CDMV5;
+-- Code taken from:
+-- https://github.com/OHDSI/ETL-CMS/blob/master/SQL/create_CDMv5_drug_era_non_stockpile.sql
 
 
+if object_id('tempdb..#tmp_de', 'U') is not null drop table #tmp_de;
 
-/****
-DRUG ERA
-Note: Eras derived from DRUG_EXPOSURE table, using 30d gap
- ****/
-IF OBJECT_ID('tempdb..#cteDrugTarget', 'U') IS NOT NULL
-	DROP TABLE #cteDrugTarget;
+WITH
+ctePreDrugTarget(drug_exposure_id, person_id, ingredient_concept_id, drug_exposure_start_date, days_supply, drug_exposure_end_date) AS
+(-- Normalize DRUG_EXPOSURE_END_DATE to either the existing drug exposure end date, or add days supply, or add 1 day to the start date
+	SELECT
+		d.drug_exposure_id
+		, d.person_id
+		, c.concept_id AS ingredient_concept_id
+		, d.drug_exposure_start_date AS drug_exposure_start_date
+		, d.days_supply AS days_supply
+		, COALESCE(
+			---NULLIF returns NULL if both values are the same, otherwise it returns the first parameter
+			NULLIF(drug_exposure_end_date, NULL),
+			---If drug_exposure_end_date != NULL, return drug_exposure_end_date, otherwise go to next case
+			NULLIF(dateadd(day,days_supply,drug_exposure_start_date), drug_exposure_start_date),
+			---If days_supply != NULL or 0, return drug_exposure_start_date + days_supply, otherwise go to next case
+			dateadd(day,1,drug_exposure_start_date)
+			---Add 1 day to the drug_exposure_start_date since there is no end_date or INTERVAL for the days_supply
+		) AS drug_exposure_end_date
+	FROM @cdm_schema.drug_exposure d
+		JOIN @cdm_schema.concept_ancestor ca ON ca.descendant_concept_id = d.drug_concept_id
+		JOIN @cdm_schema.concept c ON ca.ancestor_concept_id = c.concept_id
+		WHERE c.vocabulary_id = 'RxNorm' ---8 selects RxNorm from the vocabulary_id
+		AND c.concept_class_id = 'Ingredient'
+		AND d.drug_concept_id != 0 ---Our unmapped drug_concept_id's are set to 0, so we don't want different drugs wrapped up in the same era
+		AND coalesce(d.days_supply,0) >= 0 ---We have cases where days_supply is negative, and this can set the end_date before the start_date, which we don't want. So we're just looking over those rows. This is a data-quality issue.
+)
 
-/* / */
-
--- Normalize DRUG_EXPOSURE_END_DATE to either the existing drug exposure end date, or add days supply, or add 1 day to the start date
-SELECT d.DRUG_EXPOSURE_ID
-	,d.PERSON_ID
-	,c.CONCEPT_ID
-	,d.DRUG_TYPE_CONCEPT_ID
-	,DRUG_EXPOSURE_START_DATE
-	,COALESCE(DRUG_EXPOSURE_END_DATE, DATEADD(day, DAYS_SUPPLY, DRUG_EXPOSURE_START_DATE), DATEADD(day, 1, DRUG_EXPOSURE_START_DATE)) AS DRUG_EXPOSURE_END_DATE
-	,c.CONCEPT_ID AS INGREDIENT_CONCEPT_ID
-INTO #cteDrugTarget
-FROM @TARGET_CDMV5_SCHEMA.DRUG_EXPOSURE d
-INNER JOIN @TARGET_CDMV5_SCHEMA.CONCEPT_ANCESTOR ca ON ca.DESCENDANT_CONCEPT_ID = d.DRUG_CONCEPT_ID
-INNER JOIN @TARGET_CDMV5_SCHEMA.CONCEPT c ON ca.ANCESTOR_CONCEPT_ID = c.CONCEPT_ID
-WHERE c.DOMAIN_ID = 'Drug'
-	AND c.CONCEPT_CLASS_ID = 'Ingredient'
-	AND c.STANDARD_CONCEPT = 'S';
-
-/* / */
-
-IF OBJECT_ID('tempdb..#cteEndDates', 'U') IS NOT NULL
-	DROP TABLE #cteEndDates;
-
-/* / */
-
-SELECT PERSON_ID
-	,INGREDIENT_CONCEPT_ID
-	,DATEADD(day, - 30, EVENT_DATE) AS END_DATE -- unpad the end date
-INTO #cteEndDates
-FROM (
-	SELECT E1.PERSON_ID
-		,E1.INGREDIENT_CONCEPT_ID
-		,E1.EVENT_DATE
-		,COALESCE(E1.START_ORDINAL, MAX(E2.START_ORDINAL)) START_ORDINAL
-		,E1.OVERALL_ORD
-	FROM (
-		SELECT PERSON_ID
-			,INGREDIENT_CONCEPT_ID
-			,EVENT_DATE
-			,EVENT_TYPE
-			,START_ORDINAL
-			,ROW_NUMBER() OVER (
-				PARTITION BY PERSON_ID
-				,INGREDIENT_CONCEPT_ID ORDER BY EVENT_DATE
-					,EVENT_TYPE
-				) AS OVERALL_ORD -- this re-numbers the inner UNION so all rows are numbered ordered by the event date
+, cteSubExposureEndDates (person_id, ingredient_concept_id, end_date) AS --- A preliminary sorting that groups all of the overlapping exposures into one exposure so that we don't double-count non-gap-days
+(
+	SELECT person_id, ingredient_concept_id, event_date AS end_date
+	FROM
+	(
+		SELECT person_id, ingredient_concept_id, event_date, event_type,
+		MAX(start_ordinal) OVER (PARTITION BY person_id, ingredient_concept_id
+			ORDER BY event_date, event_type ROWS unbounded preceding) AS start_ordinal,
+		-- this pulls the current START down from the prior rows so that the NULLs
+		-- from the END DATES will contain a value we can compare with
+			ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+				ORDER BY event_date, event_type) AS overall_ord
+			-- this re-numbers the inner UNION so all rows are numbered ordered by the event date
 		FROM (
 			-- select the start dates, assigning a row number to each
-			SELECT PERSON_ID
-				,INGREDIENT_CONCEPT_ID
-				,DRUG_EXPOSURE_START_DATE AS EVENT_DATE
-				,0 AS EVENT_TYPE
-				,ROW_NUMBER() OVER (
-					PARTITION BY PERSON_ID
-					,INGREDIENT_CONCEPT_ID ORDER BY DRUG_EXPOSURE_START_DATE
-					) AS START_ORDINAL
-			FROM #cteDrugTarget
+			SELECT person_id, ingredient_concept_id, drug_exposure_start_date AS event_date,
+			-1 AS event_type,
+			ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+				ORDER BY drug_exposure_start_date) AS start_ordinal
+			FROM ctePreDrugTarget
 
 			UNION ALL
 
-			-- add the end dates with NULL as the row number, padding the end dates by 30 to allow a grace period for overlapping ranges.
-			SELECT PERSON_ID
-				,INGREDIENT_CONCEPT_ID
-				,DATEADD(day, 30, DRUG_EXPOSURE_END_DATE)
-				,1 AS EVENT_TYPE
-				,NULL
-			FROM #cteDrugTarget
-			) RAWDATA
-		) E1
-	INNER JOIN (
-		SELECT PERSON_ID
-			,INGREDIENT_CONCEPT_ID
-			,DRUG_EXPOSURE_START_DATE AS EVENT_DATE
-			,ROW_NUMBER() OVER (
-				PARTITION BY PERSON_ID
-				,INGREDIENT_CONCEPT_ID ORDER BY DRUG_EXPOSURE_START_DATE
-				) AS START_ORDINAL
-		FROM #cteDrugTarget
-		) E2 ON E1.PERSON_ID = E2.PERSON_ID
-		AND E1.INGREDIENT_CONCEPT_ID = E2.INGREDIENT_CONCEPT_ID
-		AND E2.EVENT_DATE <= E1.EVENT_DATE
-	GROUP BY E1.PERSON_ID
-		,E1.INGREDIENT_CONCEPT_ID
-		,E1.EVENT_DATE
-		,E1.START_ORDINAL
-		,E1.OVERALL_ORD
-	) E
-WHERE 2 * E.START_ORDINAL - E.OVERALL_ORD = 0;
+			SELECT person_id, ingredient_concept_id, drug_exposure_end_date, 1 AS event_type, NULL
+			FROM ctePreDrugTarget
+		) RAWDATA
+	) e
+	WHERE (2 * e.start_ordinal) - e.overall_ord = 0
+)
 
-/* / */
+, cteDrugExposureEnds (person_id, drug_concept_id, drug_exposure_start_date, drug_sub_exposure_end_date) AS
+(
+SELECT
+	dt.person_id
+	, dt.ingredient_concept_id
+	, dt.drug_exposure_start_date
+	, MIN(e.end_date) AS drug_sub_exposure_end_date
+FROM ctePreDrugTarget dt
+JOIN cteSubExposureEndDates e ON dt.person_id = e.person_id AND dt.ingredient_concept_id = e.ingredient_concept_id AND e.end_date >= dt.drug_exposure_start_date
+GROUP BY
+      	dt.drug_exposure_id
+      	, dt.person_id
+	, dt.ingredient_concept_id
+	, dt.drug_exposure_start_date
+)
+--------------------------------------------------------------------------------------------------------------
+, cteSubExposures(row_number, person_id, drug_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count) AS
+(
+	SELECT ROW_NUMBER() OVER (PARTITION BY person_id, drug_concept_id, drug_sub_exposure_end_date ORDER BY person_id)
+		, person_id, drug_concept_id, MIN(drug_exposure_start_date) AS drug_sub_exposure_start_date, drug_sub_exposure_end_date, COUNT(*) AS drug_exposure_count
+	FROM cteDrugExposureEnds
+	GROUP BY person_id, drug_concept_id, drug_sub_exposure_end_date
+	--ORDER BY person_id, drug_concept_id
+)
+--------------------------------------------------------------------------------------------------------------
+/*Everything above grouped exposures into sub_exposures if there was overlap between exposures.
+ *So there was no persistence window. Now we can add the persistence window to calculate eras.
+ */
+--------------------------------------------------------------------------------------------------------------
+, cteFinalTarget(row_number, person_id, ingredient_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count, days_exposed) AS
+(
+	SELECT row_number, person_id, drug_concept_id, drug_sub_exposure_start_date, drug_sub_exposure_end_date, drug_exposure_count
+		, datediff(day,drug_sub_exposure_start_date,drug_sub_exposure_end_date) AS days_exposed
+	FROM cteSubExposures
+)
+--------------------------------------------------------------------------------------------------------------
+, cteEndDates (person_id, ingredient_concept_id, end_date) AS -- the magic
+(
+	SELECT person_id, ingredient_concept_id, dateadd(day,-30,event_date) AS end_date -- unpad the end date
+	FROM
+	(
+		SELECT person_id, ingredient_concept_id, event_date, event_type,
+		MAX(start_ordinal) OVER (PARTITION BY person_id, ingredient_concept_id
+			ORDER BY event_date, event_type ROWS UNBOUNDED PRECEDING) AS start_ordinal,
+		-- this pulls the current START down from the prior rows so that the NULLs
+		-- from the END DATES will contain a value we can compare with
+			ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+				ORDER BY event_date, event_type) AS overall_ord
+			-- this re-numbers the inner UNION so all rows are numbered ordered by the event date
+		FROM (
+			-- select the start dates, assigning a row number to each
+			SELECT person_id, ingredient_concept_id, drug_sub_exposure_start_date AS event_date,
+			-1 AS event_type,
+			ROW_NUMBER() OVER (PARTITION BY person_id, ingredient_concept_id
+				ORDER BY drug_sub_exposure_start_date) AS start_ordinal
+			FROM cteFinalTarget
 
-IF OBJECT_ID('tempdb..#cteDrugExpEnds', 'U') IS NOT NULL
-	DROP TABLE #cteDrugExpEnds;
+			UNION ALL
 
-/* / */
+			-- pad the end dates by 30 to allow a grace period for overlapping ranges.
+			SELECT person_id, ingredient_concept_id, dateadd(day,30,drug_sub_exposure_end_date), 1 AS event_type, NULL
+			FROM cteFinalTarget
+		) RAWDATA
+	) e
+	WHERE (2 * e.start_ordinal) - e.overall_ord = 0
 
-SELECT d.PERSON_ID
-	,d.INGREDIENT_CONCEPT_ID
-	,d.DRUG_TYPE_CONCEPT_ID
-	,d.DRUG_EXPOSURE_START_DATE
-	,MIN(e.END_DATE) AS ERA_END_DATE
-INTO #cteDrugExpEnds
-FROM #cteDrugTarget d
-INNER JOIN #cteEndDates e ON d.PERSON_ID = e.PERSON_ID
-	AND d.INGREDIENT_CONCEPT_ID = e.INGREDIENT_CONCEPT_ID
-	AND e.END_DATE >= d.DRUG_EXPOSURE_START_DATE
-GROUP BY d.PERSON_ID
-	,d.INGREDIENT_CONCEPT_ID
-	,d.DRUG_TYPE_CONCEPT_ID
-	,d.DRUG_EXPOSURE_START_DATE;
-
-/* / */
-
-INSERT INTO @TARGET_CDMV5_SCHEMA.drug_era
-SELECT row_number() OVER (
-		ORDER BY person_id
-		) AS drug_era_id
-	,person_id
-	,INGREDIENT_CONCEPT_ID
-	,min(DRUG_EXPOSURE_START_DATE) AS drug_era_start_date
-	,ERA_END_DATE
-	,COUNT(*) AS DRUG_EXPOSURE_COUNT
-	,30 AS gap_days
-FROM #cteDrugExpEnds
-GROUP BY person_id
-	,INGREDIENT_CONCEPT_ID
-	,drug_type_concept_id
-	,ERA_END_DATE;
+)
+, cteDrugEraEnds (person_id, drug_concept_id, drug_sub_exposure_start_date, drug_era_end_date, drug_exposure_count, days_exposed) AS
+(
+SELECT
+	ft.person_id
+	, ft.ingredient_concept_id
+	, ft.drug_sub_exposure_start_date
+	, MIN(e.end_date) AS era_end_date
+	, drug_exposure_count
+	, days_exposed
+FROM cteFinalTarget ft
+JOIN cteEndDates e ON ft.person_id = e.person_id AND ft.ingredient_concept_id = e.ingredient_concept_id AND e.end_date >= ft.drug_sub_exposure_start_date
+GROUP BY
+      	ft.person_id
+	, ft.ingredient_concept_id
+	, ft.drug_sub_exposure_start_date
+	, drug_exposure_count
+	, days_exposed
+)
+SELECT
+    row_number()over(order by person_id) drug_era_id
+	, person_id
+	, drug_concept_id
+	, MIN(drug_sub_exposure_start_date) AS drug_era_start_date
+	, drug_era_end_date
+	, SUM(drug_exposure_count) AS drug_exposure_count
+	, datediff(day,MIN(drug_sub_exposure_start_date),drug_era_end_date)-SUM(days_exposed) as gap_days
+INTO #tmp_de
+FROM cteDrugEraEnds dee
+GROUP BY person_id, drug_concept_id, drug_era_end_date;
 
+INSERT INTO @cdm_schema.drug_era(drug_era_id,person_id, drug_concept_id, drug_era_start_date, drug_era_end_date, drug_exposure_count, gap_days)
+SELECT * FROM #tmp_de;
 ```
 
 ## **Example ETL Script**
diff --git a/rmd/useCaseN.Rmd b/rmd/useCaseN.Rmd
new file mode 100644
index 0000000..32f7de7
--- /dev/null
+++ b/rmd/useCaseN.Rmd
@@ -0,0 +1,10 @@
+---
+title: "Local Data"
+output: html_document
+---
+
+Okay, so you don't have a network use case. **Is this data element specific to your data source, or are there others in the community who might also have this data but don't yet need it for a study or data model convention?**
+
+[Yes, this element is specific to my data source](localChange.html)
+
+[No, there are others in the community who also have this data](leaveAsIs.html)
diff --git a/rmd/useCaseY.Rmd b/rmd/useCaseY.Rmd
new file mode 100644
index 0000000..f308231
--- /dev/null
+++ b/rmd/useCaseY.Rmd
@@ -0,0 +1,13 @@
+---
+title: "OMOP Vocabulary"
+output: html_document
+---
+
+Great, you have a network use case! 
+
+Next question: **Is there an existing OMOP vocabulary to support this new element? If you are unsure, feel free to check [Athena](https://athena.ohdsi.org/search-terms/terms?query).**
+
+[Yes, I have all the required vocabulary I need](vocabY.html)
+
+[No, I there is not an existing OMOP vocabulary to support my request](vocabN.html)
+
diff --git a/rmd/vocabN.Rmd b/rmd/vocabN.Rmd
new file mode 100644
index 0000000..0eccca8
--- /dev/null
+++ b/rmd/vocabN.Rmd
@@ -0,0 +1,10 @@
+---
+title: "Open Source Vocabulary"
+output: html_document
+---
+
+Okay, so you have a use case but you don't have an OMOP vocabulary to support your need. **Is there an existing open-source (not proprietary or custom) vocabulary that has not yet been incorporated into the OMOP vocabulary?**
+
+[Yes, the vocabulary exists, it just needs to be brought in](vocabRequest.html)
+
+[No, there is no open-source vocabulary for this data element](contactVocab.html)
diff --git a/rmd/vocabRequest.Rmd b/rmd/vocabRequest.Rmd
new file mode 100644
index 0000000..b80fd2e
--- /dev/null
+++ b/rmd/vocabRequest.Rmd
@@ -0,0 +1,10 @@
+---
+title: "Vocabulary Request"
+output: html_document
+---
+
+Okay so you have something you would like to add to the CDM and there is an existing OMOP vocabulary we can bring in to support it. **In this case, please open an issue on the vocabulary github with the details of what you need added** as data elements in the CDM must have a vocabulary in place before they can be implemented. The team will follow up with you should they need additional information.
+
+[Vocabulary GitHub Issue Tracker](https://github.com/OHDSI/Vocabulary-v5.0/issues)
+
+Once that request is made, please follow the [CDM Request Process](cdmRequestProcess.html) to begin the steps soliciting a change or addition to the model itself. Need more guidance? Consider contacting the CDM Working Group on our [GitHub](https://github.com/OHDSI/CommonDataModel) or [Teams Channel](https://teams.microsoft.com/l/team/19%3a133f2b94b86a41a884d4a4d160610148%40thread.tacv2/conversations?groupId=a6f2c516-e568-4974-8f1e-a7bdc2f997c5&tenantId=a30f0094-9120-4aab-ba4c-e5509023b2d5).
diff --git a/rmd/vocabY.Rmd b/rmd/vocabY.Rmd
new file mode 100644
index 0000000..7211460
--- /dev/null
+++ b/rmd/vocabY.Rmd
@@ -0,0 +1,8 @@
+---
+title: "Request Process"
+output: html_document
+---
+
+Great, so you have a network use case and an existing OMOP Vocabulary! **From here, please follow the steps to formally request a change to the OMOP Common Data Model.** 
+
+[CDM Request Process](cdmRequestProcess.html)