1 / 30

Building a Non-mandatory Enterprise System Key Factors for Success

Building a Non-mandatory Enterprise System Key Factors for Success. February 9, 2011 Elaine Ayres, MS, RD – Project Manager. Seven Factors for Success The Biomedical Translational Research Information System. Define a clear purpose for the system

hertz
Download Presentation

Building a Non-mandatory Enterprise System Key Factors for Success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Building a Non-mandatory Enterprise System Key Factors for Success February 9, 2011 Elaine Ayres, MS, RD – Project Manager

  2. Seven Factors for SuccessThe Biomedical Translational Research Information System • Define a clear purpose for the system • Create a system architecture that allows for optimum use of source data • Establish a data model that enables effective data storage and retrieval • Create an approach to terminology that allows utilization of data from disparate sources

  3. Continued 5) Develop a user interface that allows users to create their own queries 6) Establish clear policies and procedures for data use and data sharing that are accepted by institutional leadership 7) Ensure trans-institutional governance to ensure support and on-going funding for the system

  4. 1) Purpose of BTRIS • How does the system contribute to the IC and NIH mission? Create efficiencies in the research cycle.

  5. What is BTRIS?

  6. What is BTRIS?

  7. 2) Logical Architecture

  8. BTRIS Applications

  9. 3) Data Model • Hybrid model • Traditional tables and columns • Entity Attribute Value (EAV) for unique source specific data

  10. BTRIS Data Growth

  11. Data in BTRIS

  12. 4) Terminology • Research Entities Dictionary or “RED” • A controlled terminology • Allows for common and unique concepts • Each concept has a unique code • Codes are in hierarchies to allow for class-based queries or leaf-node queries

  13. Biomedical Translational Research Information System

  14. The Research Entities Dictionary

  15. 5) User Interface

  16. BTRIS Users

  17. Reports

  18. Report

  19. Radiaology and Imaging Report

  20. Radiology Test Report

  21. Radiology & Imaging Report

  22. Radiology & Imaging Report

  23. 33 years of Data

  24. Data Extracts • Data also available for extracts • Three methods: • Run queries in Cognos • Direct database connection (ODBC) • BTRIS Web Access (BWA) – an HL7 data service • NCI and NIAID using BWA • Other IC’s using ODBC

  25. 6) Establish Clear Policies and Procedures • BTRIS Policy Committee composed of investigators • Data sharing and use policies approved by Director, NIH • Modified over the past two years to include new types of users

  26. 7) Project Governance • CRIS Steering Committee governs project • Entirely funded by ITWG • Multiple sub-committees • Policy • Data Access • User Group • Clinical Trial Management Systems (new) • Hand Held Devices

  27. Accomplishments for 2010 • Images from the CC PACs now available in the BTRIS radiology report • NCI research data from two systems is available to NCI researchers • Created a web application for BTRIS data extracts to IC systems • Subject attribution improving based on input from investigators • User base increased from 120 to 297 over past year

  28. 2011 Development • Add NHGRI from LabMatrix system • Add NICHD data from CTDB system • Develop pilot of ClinicalTrials.gov report

  29. Performance Metrics • Enhanced user satisfaction compared to baseline • Ability to access data needed for analysis • Data available (numeric, reports, images, specimens) • User requests to add data for increased functionality • Utilization rates of targeted groups • Efficiency improvements to research cycle (throughput) • Impact on publications

  30. Challenges • Adding additional data • System performance • User workflow • Pressure to take on additional functionality

More Related