mz-health/OMOP
mz-health
/
OMOP
mirror of https://github.com/OHDSI/CommonDataModel.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DATALAD RUNCMD] Fix fieds typo 

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "git-sedi fieds fields",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^
This commit is contained in:
Yaroslav Halchenko 2024-03-28 15:31:21 -04:00
parent df61fe512c
commit 0c031eee12
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/cdm54ToolingSupport.html
View File

@ -499,7 +499,7 @@ Support</strong></h1>
make use of which OMOP CDM fields. The goal is to inform ETL developers, make use of which OMOP CDM fields. The goal is to inform ETL developers,
tooling developers and CDM extensions.</p> tooling developers and CDM extensions.</p>
<ul> <ul>
<li>For ETL developers it helps to have guidance on which fieds to <li>For ETL developers it helps to have guidance on which fields to
prioritise in the mapping. Most value will be gained from populating prioritise in the mapping. Most value will be gained from populating
fields support across the OHDSI tooling.</li> fields support across the OHDSI tooling.</li>
<li>For OHDSI tooling developers, this page provides insight in the gaps <li>For OHDSI tooling developers, this page provides insight in the gaps

2
rmd/cdm54ToolingSupport.RMD
View File

@ -10,7 +10,7 @@ output:
This tables below contain an overview of which standard OHDSI tools make use of which OMOP CDM fields. This tables below contain an overview of which standard OHDSI tools make use of which OMOP CDM fields.
The goal is to inform ETL developers, tooling developers and CDM extensions. The goal is to inform ETL developers, tooling developers and CDM extensions.
- For ETL developers it helps to have guidance on which fieds to prioritise in the mapping. Most value will be gained from populating fields support across the OHDSI tooling. - For ETL developers it helps to have guidance on which fields to prioritise in the mapping. Most value will be gained from populating fields support across the OHDSI tooling.
- For OHDSI tooling developers, this page provides insight in the gaps of support and can drive future development efforts. - For OHDSI tooling developers, this page provides insight in the gaps of support and can drive future development efforts.
- For CDM extenstions, it helps to known what it means for an OMOP CDM table/field to be part of the standard. In other words: what OHDSI tooling do we at least expect to support the new extensions? - For CDM extenstions, it helps to known what it means for an OMOP CDM table/field to be part of the standard. In other words: what OHDSI tooling do we at least expect to support the new extensions?