Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/cdm53.html
Original file line number Diff line number Diff line change
Expand Up @@ -482,6 +482,7 @@ <h2 id="toc-title">On this page</h2>
<li><a href="#person" id="toc-person" class="nav-link" data-scroll-target="#person">PERSON</a></li>
<li><a href="#observation_period" id="toc-observation_period" class="nav-link" data-scroll-target="#observation_period">OBSERVATION_PERIOD</a></li>
<li><a href="#visit_occurrence" id="toc-visit_occurrence" class="nav-link" data-scroll-target="#visit_occurrence">VISIT_OCCURRENCE</a></li>
<li><a href="#visit_detail" id="toc-visit_detail" class="nav-link" data-scroll-target="#visit_detail">VISIT_DETAIL</a></li>
<li><a href="#condition_occurrence" id="toc-condition_occurrence" class="nav-link" data-scroll-target="#condition_occurrence">CONDITION_OCCURRENCE</a></li>
<li><a href="#drug_exposure" id="toc-drug_exposure" class="nav-link" data-scroll-target="#drug_exposure">DRUG_EXPOSURE</a></li>
<li><a href="#procedure_occurrence" id="toc-procedure_occurrence" class="nav-link" data-scroll-target="#procedure_occurrence">PROCEDURE_OCCURRENCE</a></li>
Expand Down Expand Up @@ -1814,8 +1815,10 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="visit_occurrence">VISIT
</tr>
</tbody>
</table>
<h3 id="visit_detail" class="tabset tabset-pills anchored">VISIT_DETAIL</h3>

</section>
<section id="visit_detail" class="level3 tabset tabset-pills">
<h3 class="tabset tabset-pills anchored" data-anchor-id="visit_detail">VISIT_DETAIL</h3>
<p><strong>Table Description</strong></p>
<p>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.</p>
<p><strong>User Guide</strong></p>
Expand Down Expand Up @@ -4654,7 +4657,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="measurement">MEASUREMEN
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;">
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>. The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
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>. The operator_concept_id explicitly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
</td>
<td style="text-align:left;">
integer
Expand Down
9 changes: 6 additions & 3 deletions docs/cdm54.html
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,7 @@ <h2 id="toc-title">On this page</h2>
<li><a href="#person" id="toc-person" class="nav-link" data-scroll-target="#person">PERSON</a></li>
<li><a href="#observation_period" id="toc-observation_period" class="nav-link" data-scroll-target="#observation_period">OBSERVATION_PERIOD</a></li>
<li><a href="#visit_occurrence" id="toc-visit_occurrence" class="nav-link" data-scroll-target="#visit_occurrence">VISIT_OCCURRENCE</a></li>
<li><a href="#visit_detail" id="toc-visit_detail" class="nav-link" data-scroll-target="#visit_detail">VISIT_DETAIL</a></li>
<li><a href="#condition_occurrence" id="toc-condition_occurrence" class="nav-link" data-scroll-target="#condition_occurrence">CONDITION_OCCURRENCE</a></li>
<li><a href="#drug_exposure" id="toc-drug_exposure" class="nav-link" data-scroll-target="#drug_exposure">DRUG_EXPOSURE</a></li>
<li><a href="#procedure_occurrence" id="toc-procedure_occurrence" class="nav-link" data-scroll-target="#procedure_occurrence">PROCEDURE_OCCURRENCE</a></li>
Expand Down Expand Up @@ -1882,8 +1883,10 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="visit_occurrence">VISIT
</tr>
</tbody>
</table>
<h3 id="visit_detail" class="tabset tabset-pills anchored">VISIT_DETAIL</h3>

</section>
<section id="visit_detail" class="level3 tabset tabset-pills">
<h3 class="tabset tabset-pills anchored" data-anchor-id="visit_detail">VISIT_DETAIL</h3>
<p><strong>Table Description</strong></p>
<p>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.</p>
<p><strong>User Guide</strong></p>
Expand Down Expand Up @@ -4893,7 +4896,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="measurement">MEASUREMEN
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;">
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>. The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
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>. The operator_concept_id explicitly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
</td>
<td style="text-align:left;">
integer
Expand Down Expand Up @@ -10552,7 +10555,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="episode">EPISODE</h3>
episode_start_date
</td>
<td style="text-align:left;">
The date when the Episode beings.
The date when the Episode begins.
</td>
<td style="text-align:left;">
Please see [article] for how to define an Episode start date.
Expand Down
2 changes: 1 addition & 1 deletion docs/cdm54ToolingSupport.html
Original file line number Diff line number Diff line change
Expand Up @@ -560,7 +560,7 @@ <h2 class="anchored" data-anchor-id="criteria">Criteria</h2>
</tr>
<tr class="even">
<td>Atlas Cohort</td>
<td>Used in te Atlas User Interface for cohort definition criteria (directly, or via ‘Add attribute’)</td>
<td>Used in the Atlas User Interface for cohort definition criteria (directly, or via ‘Add attribute’)</td>
<td>https://atlas-demo.ohdsi.org/</td>
</tr>
<tr class="odd">
Expand Down
9 changes: 6 additions & 3 deletions docs/cdm55.html
Original file line number Diff line number Diff line change
Expand Up @@ -483,6 +483,7 @@ <h2 id="toc-title">On this page</h2>
<li><a href="#person" id="toc-person" class="nav-link" data-scroll-target="#person">PERSON</a></li>
<li><a href="#observation_period" id="toc-observation_period" class="nav-link" data-scroll-target="#observation_period">OBSERVATION_PERIOD</a></li>
<li><a href="#visit_occurrence" id="toc-visit_occurrence" class="nav-link" data-scroll-target="#visit_occurrence">VISIT_OCCURRENCE</a></li>
<li><a href="#visit_detail" id="toc-visit_detail" class="nav-link" data-scroll-target="#visit_detail">VISIT_DETAIL</a></li>
<li><a href="#condition_occurrence" id="toc-condition_occurrence" class="nav-link" data-scroll-target="#condition_occurrence">CONDITION_OCCURRENCE</a></li>
<li><a href="#drug_exposure" id="toc-drug_exposure" class="nav-link" data-scroll-target="#drug_exposure">DRUG_EXPOSURE</a></li>
<li><a href="#procedure_occurrence" id="toc-procedure_occurrence" class="nav-link" data-scroll-target="#procedure_occurrence">PROCEDURE_OCCURRENCE</a></li>
Expand Down Expand Up @@ -1884,8 +1885,10 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="visit_occurrence">VISIT
</tr>
</tbody>
</table>
<h3 id="visit_detail" class="tabset tabset-pills anchored">VISIT_DETAIL</h3>

</section>
<section id="visit_detail" class="level3 tabset tabset-pills">
<h3 class="tabset tabset-pills anchored" data-anchor-id="visit_detail">VISIT_DETAIL</h3>
<p><strong>Table Description</strong></p>
<p>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.</p>
<p><strong>User Guide</strong></p>
Expand Down Expand Up @@ -4895,7 +4898,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="measurement">MEASUREMEN
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;">
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>. The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
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>. The operator_concept_id explicitly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
</td>
<td style="text-align:left;">
integer
Expand Down Expand Up @@ -10720,7 +10723,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="episode">EPISODE</h3>
episode_start_date
</td>
<td style="text-align:left;">
The date when the Episode beings.
The date when the Episode begins.
</td>
<td style="text-align:left;">
Please see [article] for how to define an Episode start date.
Expand Down
2 changes: 1 addition & 1 deletion docs/cdm60.html
Original file line number Diff line number Diff line change
Expand Up @@ -4691,7 +4691,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="measurement">MEASUREMEN
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;">
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>. The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
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>. The operator_concept_id explicitly refers to the value of the measurement. Leave it NULL if there’s an exact numeric value given (instead of putting ‘=’) or there’s no numeric value at all.
</td>
<td style="text-align:left;">
integer
Expand Down
2 changes: 1 addition & 1 deletion docs/oncology.html
Original file line number Diff line number Diff line change
Expand Up @@ -611,7 +611,7 @@ <h3 class="tabset tabset-pills anchored" data-anchor-id="episode">episode</h3>
episode_start_date
</td>
<td style="text-align:left;">
The date when the Episode beings.
The date when the Episode begins.
</td>
<td style="text-align:left;">
Please see [article] for how to define an Episode start date.
Expand Down
16 changes: 8 additions & 8 deletions docs/search.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion inst/csv/OMOP_CDMv5.3_Field_Level.csv
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ measurement,measurement_date,Yes,date,Use this date to determine the date of the
measurement,measurement_datetime,No,datetime,NA,This is not required. If a source does not specify datetime the convention is to set to NULL.,No,No,NA,NA,NA,NA
measurement,measurement_time,No,varchar(10),NA,This is present for backwards compatibility and will be deprecated in an upcoming version.,No,No,NA,NA,NA,NA
measurement,measurement_type_concept_id,Yes,integer,"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.","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. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Type+Concept&standardConcept=Standard&page=1&pageSize=15&query=). A more detailed explanation of each Type Concept can be found on the [vocabulary wiki](https://github.com/OHDSI/Vocabulary-v5.0/wiki/Vocab.-TYPE_CONCEPT).",No,Yes,CONCEPT,CONCEPT_ID,Type Concept,NA
measurement,operator_concept_id,No,integer,"The meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/4172703) 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 =.","Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&standardConcept=Standard&page=1&pageSize=15&query=). The operator_concept_id explictly refers to the value of the measurement. Leave it NULL if there's an exact numeric value given (instead of putting '=') or there's no numeric value at all.",No,Yes,CONCEPT,CONCEPT_ID,NA,NA
measurement,operator_concept_id,No,integer,"The meaning of Concept [4172703](https://athena.ohdsi.org/search-terms/terms/4172703) 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 =.","Operators are <, <=, =, >=, > and these concepts belong to the 'Meas Value Operator' domain. [Accepted Concepts](https://athena.ohdsi.org/search-terms/terms?domain=Meas+Value+Operator&standardConcept=Standard&page=1&pageSize=15&query=). The operator_concept_id explicitly refers to the value of the measurement. Leave it NULL if there's an exact numeric value given (instead of putting '=') or there's no numeric value at all.",No,Yes,CONCEPT,CONCEPT_ID,NA,NA
measurement,value_as_number,No,float,"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.",[Convention for negative values](https://ohdsi.github.io/Themis/negative_value_as_number.html),No,No,NA,NA,NA,NA
measurement,value_as_concept_id,No,integer,If the raw data gives a categorial result for measurements those values are captured and mapped to standard concepts. This can be done manually or using the \Maps to value\ relationship in the vocabulary.,"If there is no categorial result in the source data, set VALUE_AS_CONCEPT_ID to NULL, if there is a categorial result in a source data but without mapping, set VALUE_AS_CONCEPT_ID to 0, else map to a CONCEPT_ID. These are also mapped using the \Maps to value\ relationship in the vocabulary.",No,Yes,CONCEPT,CONCEPT_ID,NA,NA
measurement,unit_concept_id,No,integer,"At present, there isn't a prescribed unit for individual measurements, such as Hemoglobin A1C, meaning it's not obligatory to express these measurements as a percentage. UNIT_SOURCE_VALUES should be linked to a Standard Concept within the Unit domain that most accurately reflects the unit provided in the source data.","If the source data does not include units, set UNIT_CONCEPT_ID to NULL. If units are provided but not mapped, set UNIT_CONCEPT_ID to 0. Otherwise, map the units to a CONCEPT_ID. Remember that units are case-sensitive in vocabulary.",No,Yes,CONCEPT,CONCEPT_ID,Unit,NA
Expand Down
Loading
Loading