Giter Site home page Giter Site logo

data2health / maturity-model Goto Github PK

View Code? Open in Web Editor NEW
4.0 19.0 1.0 5.04 MB

Research Informatics and open science maturity model

License: BSD 3-Clause "New" or "Revised" License

Python 10.29% HTML 0.51% TypeScript 74.10% CSS 15.09%
data2health cd2hpm

maturity-model's Introduction

maturity-model

Research Informatics Maturity Model Tool

Problem statement

CTSAs are the core sources of clinical and translational research, but often struggle with helping their organizations understand the strategic importance of improving their informatics capabilities and IT deployment. All institutions are trying to understand what they should invest in to remain innovative and competitive, not only in research but in translating knowledge into practice and exploring the data they have to improve health.

Significant interest in the Maturity Model has already been elicited without a wide call. We want to democratize this kind of survey so that stakeholders at all levels can self-assess and work to improve their current functions and plan for innovation.

Project description

Organizations that engage in research, especially those with Clinical and Translational Science groups, may want to self-assess their maturity of key research IT capabilities and learn to improve these capabilities. This project intends to develop an approach to help organizations through that process. It builds on other assessments by Embi, Knosp, Barnett, and Anderson by narrowing the focus to key areas related to collaborative and open science, and provides more clarity and context for the possibilities for improvement. It also intends to facilitate the process of improvement through guided vignettes and tools.

The purpose of this survey is to elicit key indicators related to research and translational IT that may drive the ability for institutions to engage in innovative and collaborative open science. Our definition of research and translational IT are the capabilities that enable data, information, and knowledge to be discovered, processed, and shared. It focuses on three key areas:

  • Governance and Leadership
  • Data sharing and licensing
  • Deployment of capabilities related to data (architecture, content, tools, and sharing)

The survey has three steps:

  1. Data collection for “artifacts” related to our focus areas and open science/collaboration more broadly. This includes documenting the evidence of tools, policies, governance structures, leadership positions, and resources at a site.

  2. Open-ended questions related to governance and leadership, and policies influencing data sharing and licensing.

  3. A guided identification of ‘bright spots’ related to the deployment of key infrastructure capabilities.

Contact person

Point person (github handle) Site Core Director
Liz Zampino (@ezampino) UW / WUSTL Adam Wilcox (@abwilcox)

Leads

Lead(s) (github handle) Site
Adam Wilcox (@abwilcox) Washington University St. Louis
Robin Champieux (@rchampieux) OHSU

maturity-model's People

Contributors

abwilcox avatar cgcook avatar davedorr9 avatar eichmann avatar ezampino avatar jmcmurry avatar mh2727 avatar ndobb avatar ramussa avatar rchampieux avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

lrasmus

maturity-model's Issues

Deploy version 1 of survey app on production server

The Maturity Model Survey app uses a pretty straightforward 3-tier deployment with

  1. A React web client application
  2. A Python-Flask REST API on the server
  3. A REDCap project as a database

We need to deploy 1 & 2 on an RIT server. At a high level this should include:

  1. Reserving a subdomain (perhaps https://maturitymodel.rit.uw.edu? let's discuss)
  2. Setting up Apache to serve the React client on /
  3. Setting up Apache to have the Python API listen on /api/

Note that we don't need to do anything setting up REDCap, and the React client has its own login page to prevent unauthorized web traffic from getting in. As users from many sites will be using the tool, it should not be protected by UW NetID.

Create UI flow for adding new models to app

Should:

  • Handling survey structure and user answer mapping.
  • Typecheck survey name fields to ensure they match REDCap and Python API
  • Allow for custom display of a given model if necessary.

Add Results view

Required:

  • Scoring and aggregation should happen only on server.
  • Visualizations should done in React with Recharts

Create feedback mechanism

Form/survey or other means to collect information from individuals that attended the 9.24.2019 chat. We requested that they identify areas of interest (either current models or expansion).

Handle data syncing between web app and REDCap

Should:

  • Allow for data to be submitted upon completing each maturity model survey.
  • Use the Python Flask API as a gatekeeper for REDCap, ensuring user has access and is not able to modify fields they should not have access to, etc.
  • Use diff'ing to ensure only fields that have changed are sent to update REDCap.

Development Team Meeting

Team is meeting 10.02.2019 to discuss implementation of this tool. Team to include: Nic Dobbins, Mehadi Hassan, and Liz Zampino.

Create initial landing and model selection page

Should:

  • Greet users by name and let them know purpose of survey app.
  • Show a list of selectable maturity models to answer questions for
  • Include header/sidebar links for Home, Results, and quick links for each model

Create linked survey forms-sheets for initial models

  • Quintegra Maturity Model for electronic Healthcare (eHMM)
  • IDC Healthcare IT (HIT) Maturity Model
  • HIMSS Maturity Model for Electronic Medical Record (EMRAM)
  • HIMSS Continuity of Care Maturity Model
  • Maturity Model for Electronic Patient Record (EPRMM)
  • Patient Records/Content Management Maturity Model
  • Interoperability Maturity Model

RIOSM Report back

Report RIOSM data back to Columbia; compared data collected and self assessment.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.