Multiple fixes

Fixed issue in CDM v5.3 field level csv, formatted rmd files, fixed documentation of the buildReleaseZip() function.
This commit is contained in:
Clair Blacketer 2021-09-23 10:42:24 -04:00
parent b89ce618c5
commit 5927b49a53
7 changed files with 8 additions and 12 deletions

View File

@ -11,7 +11,7 @@
<title>cdm53.utf8</title> <title>OMOP CDM v5.3</title>
<script src="site_libs/header-attrs-2.6/header-attrs.js"></script> <script src="site_libs/header-attrs-2.6/header-attrs.js"></script>
<script src="site_libs/jquery-1.11.3/jquery.min.js"></script> <script src="site_libs/jquery-1.11.3/jquery.min.js"></script>
@ -518,12 +518,11 @@ div.tocify {
<h1 class="title toc-ignore"><strong>OMOP CDM v5.3</strong></h1>
</div> </div>
<div id="omop-cdm-v5.3" class="section level1">
<h1><strong>OMOP CDM v5.3</strong></h1>
<p>Below is the specification document for the OMOP Common Data Model, v5.3 (previously v5.3.1). 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). Should you have questions please feel free to visit the <a href="https://forums.ohdsi.org/">forums</a> or the <a href="https://github.com/ohdsi/CommonDataModel/issues">github issue</a> page.</p> <p>Below is the specification document for the OMOP Common Data Model, v5.3 (previously v5.3.1). 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). Should you have questions please feel free to visit the <a href="https://forums.ohdsi.org/">forums</a> or the <a href="https://github.com/ohdsi/CommonDataModel/issues">github issue</a> page.</p>
<p><em><strong>Special Note</strong> This documentation previously referenced v5.3.1. During the OHDSI/CommonDataModel Hack-A-Thon that occurred on August 18, 2021 the decision was made to align documentation with the minor releases. Hot fixes and minor.minor release can be found through the searching of tags.</em></p> <p><em><strong>Special Note</strong> This documentation previously referenced v5.3.1. During the OHDSI/CommonDataModel Hack-A-Thon that occurred on August 18, 2021 the decision was made to align documentation with the minor releases. Hot fixes and minor.minor release can be found through the searching of tags.</em></p>
<p>after regeneration of DDLs link to csv of cdm link to pdf of cdm documentation link to forum on doc page</p> <p>after regeneration of DDLs link to csv of cdm link to pdf of cdm documentation link to forum on doc page</p>
@ -12228,7 +12227,7 @@ No
valid_start_date valid_start_date
</td> </td>
<td style="text-align:left;width: 3in; "> <td style="text-align:left;width: 3in; ">
The date when the Concept was first recorded. The default value is &lt;&lt;&lt;&lt;&lt;&lt;&lt; HEAD:inst/csv/OMOP_CDMv5.3_Field_Level.csv 1-Jan-1970. The date when the Concept was first recorded. The default value is 1-Jan-1970.
</td> </td>
<td style="text-align:left;width: 4in; "> <td style="text-align:left;width: 4in; ">
</td> </td>
@ -12695,7 +12694,6 @@ No
</table> </table>
</div> </div>
</div> </div>
</div>

View File

@ -498,7 +498,6 @@ DRUG_STRENGTH,denominator_unit_concept_id,No,integer,The Concept representing th
DRUG_STRENGTH,box_size,No,integer,The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.,,No,No,,,,, DRUG_STRENGTH,box_size,No,integer,The number of units of Clinical Branded Drug or Quantified Clinical or Branded Drug contained in a box as dispensed to the patient.,,No,No,,,,,
DRUG_STRENGTH,valid_start_date,Yes,date,"The date when the Concept was first DRUG_STRENGTH,valid_start_date,Yes,date,"The date when the Concept was first
recorded. The default value is recorded. The default value is
<<<<<<< HEAD:inst/csv/OMOP_CDMv5.3_Field_Level.csv
1-Jan-1970.",,No,No,,,,, 1-Jan-1970.",,No,No,,,,,
DRUG_STRENGTH,valid_end_date,Yes,date,The date when then Concept became invalid.,,No,No,,,,, DRUG_STRENGTH,valid_end_date,Yes,date,The date when then Concept became invalid.,,No,No,,,,,
DRUG_STRENGTH,invalid_reason,No,varchar(1),"Reason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.",,No,No,,,,, DRUG_STRENGTH,invalid_reason,No,varchar(1),"Reason the concept was invalidated. Possible values are D (deleted), U (replaced with an update) or NULL when valid_end_date has the default value.",,No,No,,,,,

1 cdmTableName cdmFieldName isRequired cdmDatatype userGuidance etlConventions isPrimaryKey isForeignKey fkTableName fkFieldName fkDomain fkClass unique DQ identifiers
498
499
500
501
502
503

View File

@ -7,7 +7,7 @@
buildReleaseZip( buildReleaseZip(
cdmVersion, cdmVersion,
targetDialect = listSupportedDialects(), targetDialect = listSupportedDialects(),
outputfolder = file.path(getwd(), "inst", "ddl") outputfolder = file.path(getwd(), "output")
) )
} }
\arguments{ \arguments{

View File

@ -1,5 +1,5 @@
% Generated by roxygen2: do not edit by hand % Generated by roxygen2: do not edit by hand
% Please edit documentation in R/writeDdl.R % Please edit documentation in R/writeDDL.R
\name{writeDdl} \name{writeDdl}
\alias{writeDdl} \alias{writeDdl}
\alias{writePrimaryKeys} \alias{writePrimaryKeys}

View File

@ -1,4 +1,5 @@
--- ---
title: '**OMOP CDM v5.3**'
output: output:
html_document: html_document:
toc: yes toc: yes
@ -18,8 +19,6 @@ library(stringr)
``` ```
# **OMOP CDM v5.3**
Below is the specification document for the OMOP Common Data Model, v5.3 (previously v5.3.1). 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). 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. Below is the specification document for the OMOP Common Data Model, v5.3 (previously v5.3.1). 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). 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.
*__Special Note__ This documentation previously referenced v5.3.1. During the OHDSI/CommonDataModel Hack-A-Thon that occurred on August 18, 2021 the decision was made to align documentation with the minor releases. Hot fixes and minor.minor release can be found through the searching of tags.* *__Special Note__ This documentation previously referenced v5.3.1. During the OHDSI/CommonDataModel Hack-A-Thon that occurred on August 18, 2021 the decision was made to align documentation with the minor releases. Hot fixes and minor.minor release can be found through the searching of tags.*

View File

@ -1,5 +1,5 @@
--- ---
title: "Preserving Privacy in an OMOP CDM Implementation" title: "**Preserving Privacy in an OMOP CDM Implementation**"
output: output:
html_document: html_document:
toc: TRUE toc: TRUE

View File

@ -1,5 +1,5 @@
--- ---
title: "Observation Period Considerations for EHR Data" title: "**Observation Period Considerations for EHR Data**"
output: html_document output: html_document
--- ---