docs update

docs/cdm54.html

@@ -13,7 +13,7 @@
 
 <title>OMOP CDM v5.4</title>
 
-<script src="site_libs/header-attrs-2.25/header-attrs.js"></script>
+<script src="site_libs/header-attrs-2.27/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" />
@@ -495,6 +495,7 @@ div.tocify {
 </div>
 
 
+<p><img src="images/Santa-George-A.png" /></p>
 <p>This is the specification document for the OMOP Common Data Model,
 v5.4. <strong>This is the latest version of the OMOP CDM.</strong> Each
 table is represented with a high-level description and ETL conventions

rmd/cdm54.Rmd

@@ -18,7 +18,8 @@ library(dplyr)
 library(stringr)
 
 ```
-
+![](images/Santa-George-A.png) 
+ 
 This is the specification document for the OMOP Common Data Model, v5.4. **This is the latest version of the OMOP CDM.**  Each table is represented with a high-level description and ETL conventions that should be followed. This is continued with a discussion of each field in each table, any conventions related to the field, and constraints that should be followed (like primary key, foreign key, etc). All tables should be instantiated in a CDM instance but do not need to be populated. Similarly, fields that are not required should exist in the CDM table but do not need to be populated. Should you have questions please feel free to visit the [forums](https://forums.ohdsi.org/) or the [github issue](https://github.com/ohdsi/CommonDataModel/issues) page.
 
 ### Current Support for CDM v5.4