Giter VIP home page Giter VIP logo

research's Introduction

HospitalRun logo

Last commit GitHub CI Documentation Status Commitizen friendly License Slack License OpenUK


All HospitalRun code lives in a single repository, an architecture generally called a monorepo. This repository holds all of HospitalRun's open source projects that lived in their own separate Github repos: frontend, server and components. Built with React, Node, PouchDB/CouchDB and using offline first design, we're working to deliver an HIS system that makes usability the #1 requirement, is built specifically for developing world requirements, and seeks to give back time to patient care.

‼️ Version 1.0.0-beta is no longer supported. Version 2 is currently under development ‼️

FAQs

Question Answer
"I want to help" Find out how
"I have a question" Join our Slack Workspace
"I found a bug" Open an issue
"How can I deploy 1.0.0-beta?" Follow this guide

Table of Contents

Staging Area

You can follow developments by visiting the dedicated staging environment. Use username / password as credentials to access.

Contributing

Interested in contributing to HospitalRun? There are many ways that you can get involved:

Community

Join HospitalRun's community for discussion and ask questions: HospitalRun's Slack Workspace

Channels :

  • #general - For general purpose
  • #contributors - For people who contribute to HospitalRun by developing features
  • #troubleshooting - For software related issues

Project Structure

Submodules Version Progress status Build status Coverage status Code quality
Frontend GitHub tag (latest SemVer pre-release) Status GitHub CI Coverage Status Language grade: JavaScript
Server GitHub tag (latest SemVer pre-release) Status GitHub CI Coverage Status Language grade: JavaScript
Components GitHub tag (latest SemVer pre-release) Status GitHub CI Coverage Status Language grade: JavaScript
Core GitHub tag (latest SemVer pre-release) Status GitHub CI Language grade: JavaScript
CLI GitHub tag (latest SemVer pre-release) Status GitHub CI Coverage Status Language grade: JavaScript

Last Update: 2 July 2020

Application Infrastructure

A visual representation of the functionality of all HospitalRun modules and their interactions.

miro

Behind HospitalRun

Hosted by

Sponsors

Sponsors

Backers

Backers

Big Thanks

Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs

Lead Maintainer


Maksim Sinik


Jack Meyer

Matteo Vivona

Stefano Casasola

Kumiko Kashii

Grace Lau

Stefano Miceli

Blessed Tabvirwa

Dr. MaryEtta Morris

Medical Supervisor


M.D. Daniele Piccolo

Past Contributors


Michael Daly

Contributors

Contributors

Founders


John Kleinschmidtr

Joel Worrall

Joel Glovier

License

Released under the MIT license.

research's People

Contributors

lauggh avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

research's Issues

HospitalRun initial UX research

What's this issue all about? (Background and context)

HospitalRun started in 2016 and it's been at least that long ago since research has been conducted to assess the user and tech needs for hospital information systems and EHRs for the developing world. Meanwhile, research and design documentation is needed for contributors to understand user stories and solutions. This initial research will be necessary for the team to get on the same page.

What research questions are you trying to answer?

  • Understand the tech and user needs for EMRs and HIS systems for facilities in developing areas.
  • Understand the team dynamics for people in those facilities
  • Understand the information that can/would be configured for an HIS system to be used in that facility/system

How should we prioritize development of features for HospitalRun 2.0?

Not sure. At the moment, thinking about qual research using the HospitalRun mailing list

What persona, persona segment, or customer type experiences the problem most acutely?

What business decisions will be made based on this information?

We will use this information to determine how to design an onboarding process when setting HospitalRun for the first time. We will also use this information to design a team workflow, if applicable.

What, if any, relevant prior research already exists?

Wiki: https://github.com/HospitalRun/hospitalrun-frontend/wiki/Personas

What timescales do you have in mind for the research?

Who will be leading the research?

@lauggh @HospitalRun/design

Relevant links (opportunity canvas, discussion guide, notes, etc.)

TBD

Feature Request: Version History

I believe that having a version history feature (such as Google Docs or Microsoft Word) would be useful because of this quote I found as I was sitting in on a health information exchange webinar: "When I discover an updated document, sometimes I need to know how it relates to prior versions, ideally without having to retrieve the documents."

Understand the mental models of users

I don't have a mental model of what healthcare workers want out of their EHR's, which makes it pretty much impossible to offer good design recommendations, conduct competitive analysis, etc. I plan to read this popular press article with the hope that it will guide me toward understanding healthcare workers' mental models. It's a very long article, so the more people who are looking at it to see if it's a good fit for our group, the better! Because these publications can be behind a paywall, I copy-and-pasted everything onto a Word document that has been attached to this comment. Here is the actual link to the article: https://www.newyorker.com/magazine/2018/11/12/why-doctors-hate-their-computers

Why Doctors Hate Their Computers New Yorker.docx

Feature Request: Mobile App

Providers will need to carry around a HospitalRun-enabled device with them as they are meeting different patients. We should expect that in under-resourced environments, HospitalRun will be downloaded on whatever consumer-facing devices they can get their hands on. So a mobile app will allow providers to download HospitalRun onto their existing mobile phones and tablets.

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.