• G2_484091
    了解作者
  • 155.1KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-05-27 01:36
    上传日期
CTSA指标 关于 这个Github存储库为CTSA程序的信息学通用指标提供了脚本,数据模型文档和相关文件。 基本原理 为了加快翻译速度,需要为研究人员提供访问广泛数据(电子健康记录,组学,影像学,遗传学,行为等)的权限。 这些数据可以来自不同的来源,例如临床数据库,研究数据集,传感器,移动技术,患者生成的数据以及可公开获得的数据集。 在CTSA计划中心内以及跨CTSA计划中心共享和共享数据时,要求以可以查询的格式表示数据,并遵守公认的标准。 CTSA计划的长期目标是协调数据和数据标准,以便可以对所有CTSA计划数据存储库不更改地运行任何站点编写的查询。 此通用指标的目的是提高整个财团的数据互操作性。 这一通用指标展示了每个枢纽的实力,为国家使命贡献了数据,并且每年继续提高整个财团的互操作性,以有效地利用数据进行科学研究。 具体来说,有关不同数据类型的度量标准将有助于本地集线器确定向其数
CTSA-Metrics-master.zip
  • CTSA-Metrics-master
  • Informatics Metric PCORnet MSSQL.sql
    35.1KB
  • Archive2020Scripts
  • CLICMetric-ACT-2019MSSql.sql
    4.9KB
  • Informatics Metric PCORnet MSSQL
    5.9KB
  • ric OMOP MySQL with Date Range ParameterInformatics Met
    7.7KB
  • Informatics Metric i2b2-ACT MSSQL.sql
    6.1KB
  • Informatics Metric i2b2-ACT Oracle.sql
    4KB
  • Informatics Metric OMOP Oracle with Date Range Parameter
    7.7KB
  • Informatics Metric PCORnet Oracle.sql
    5.9KB
  • Informatics Metric i2b2-ACT Oracle (UofR)
    7.5KB
  • CLICMetric-ACT-2019Oracle.sql
    4.4KB
  • Informatics Data Model Documentation.docx
    104.5KB
  • InformaticsMetricACTPostgres.sql
    25.1KB
  • Informatics Metric OMOP Oracle.sql
    23.7KB
  • Informatics Output for 2020 Data.xlsx
    9.8KB
  • Informatics Metric OMOP MSSQL.sql
    23.8KB
  • Informatics Metric PCORnet Oracle.sql
    38.8KB
  • Informatics Metric OMOP BigQuery.sql
    25.5KB
  • Informatics Metric OMOP PostgreSQL.sql
    33.9KB
  • InformaticsMetricACTSQLServer.sql
    25.1KB
  • README.md
    2.9KB
  • ProposedClicMetricTable.xlsx
    11KB
  • InformaticsMetricACTOracle.sql
    24.5KB
内容介绍
# CTSA Metrics ## About This Github repository provides scripts, data model documentation and associated files for the Informatics Common Metric for the CTSA Program. Rationale To accelerate translation, researchers need to be provided with access to a broad range of data (electronic health records, omics, imaging, genetics, behavioral, etc.). These data can come from different sources such as clinical databases, research datasets, sensors, mobile technology, patient generated data, and publicly available data sets. The sharing and pooling of data within and across CTSA Program hubs requires that data be represented in a format that can be queried and adheres to commonly accepted standards. A longer-term goal of the CTSA Program is to harmonize data and data standards so that a query written by any site can be run unaltered against all CTSA Program data repositories. The purpose of this common metric is to increase interoperability of data across the consortium. This common metric demonstrates the strength of each hub, contributes data to the national mission, and continues to increase interoperability across the consortium annually to efficiently use data to conduct scientific research. Specifically, the metrics on different data types will aid local hubs in prioritizing additions to their data repositories. Improving the CTSA Program’s clinical research data ecosystem can enhance the effectiveness of collaborative initiatives within and outside of the CTSA Program to provide tools to identify patient cohorts (i2b2/ACT, SHRINE, All of Us, PCORI). This metric will evolve over time to enhance the completeness of the research data warehouses across the CTSA Program consortium and incorporate additional types of data within warehouses as the CTSA Program, in collaboration with the iEC, finds useful and appropriate. ## Metric The data models approved for this metric by the Informatics Enterprise Committee (iEC) are: OMOP, PCORnet, i2b2/ACT (or other i2b2 data models), and TriNetX. Data is to be collected for both one- and five-year periods. The majority of the domains for this metric require information at both the patient and encounter level. Denominators for these calculations include: 1. Total number of unique patients in the data warehouse 2. Total number of unique encounters in the data warehouse 3. Total number of unique patients over age 12 in the data warehouse The Operational Guideline includes all of the metric details and can be accessed here. Standardized scripts for the OMOP, PCORnet and i2b2/ACT data models are available on this Github site. For hubs that choose to use i2b2 with their own hub-specific data model, that hub will be responsible for generating the script for their own purposes of reporting the required metric data Hubs using TriNetX must have a designated user from the site should send an email to CTSA@trinetx.com to request a CTSA Program Common Metric report. TriNetX will create the report and send it to the requesting site.
评论
    相关推荐
    • github上传
      这是您的模板存储库! 您将在changes分支中进行所有更改。 该存储库已获得 (c)2019 GitHub,Inc.的许可。
    • images:GitHub图像存储
      图片 GitHub图像存储 jsdelivr CDN
    • 测试github存储
      测试github存储
    • test:测试 GitHub 存储
      测试 测试 GitHub 存储
    • github测试
      github测试 我正在学习如何使用GitHub,这是我的第一个“真实”文件上传。 这组句子是从我的本地存储库创建的。 手指交叉,将其推送到远程仓库。
    • GitHubApp
      GitHubApp 创建具有两个屏幕的应用程序 -屏幕1:应具有您的Github个人资料。 使用响应中的至少4个字段来更新视图。... -屏幕2:使用从您的个人资料获得的存储库填充recyclerView。 每个项目视图中至少要使用3个字段。
    • github-traffic-stats:一个小的Python项目,使用GitHub API提取和存储GitHub项目的流量统计
      一个小型的Python项目,用于使用GitHub API提取和存储GitHub项目的流量统计信息。 目前,GitHub仅向仓库提供14天的流量数据。 该数据包括每天的观看次数和唯一身份访问者人数。 但是,如果您要存储和查看超过14天...
    • github-linkify
      浏览器扩展,显示指向GitHub配置文件和GitHub页面中存储库的链接 GitHub档案和回购链接有时位于最前面,但并非总是如此。 该扩展程序会在您访问GitHub Pages网站时进行检测,并在地址栏中添加指向相应配置文件或...
    • GitHits:永久存储GitHub的流量见解
      一个GitHub动作,用于*永久存储GitHub生成的流量信息,即视图和计数。 * GitHub仅提供14天之内的流量洞察。 此GitHub Action旨在克服该限制。 专为与使用而。 用法 创建/检索具有存储库级别访问权限的个人访问...