Slack has a great experience for onboarding and getting help that involves the Slackbot.

HospitalRun could use something similar for help, with some basic responses to questions or help searches, and we could use Hubot to power it.

There are a number of ways we could use this repo, including:

• use issues basically as discussion threads with a permanent history
• create directories for different documents or initiatives like: event planning, project notes, etc
• store assets

For starters I'd suggest we use the issues (obv, and already doing), and create an events directory where we can document the Hack House details.

We are aiming for a very high bar of design and user experience in HospitalRun. In order to hit that bar and scale the project well as it gains continually more features and contributors, we need to provide contributors (both engineers and designers) with a documented framework for styles and design patterns.

Without such a clearly documented and visible (should live on the docs/marketing site) framework, we run the risk of a continuously degraded level of design and user experience as the project grows. Having such a framework will also help lower the barrier to entry to contributing to the project by making sure developers and designers don't have to solve problems that have already been solved.

What

• CSS styleguide/documentation
  • document the CSS practices we have established and are enforcing via the linter
• Pattern library
  • bring consistency to the app by defining patterns and using them consistently
  • surface all of the patterns in a pattern library format where contributors can copy markup

Where

For starters this could live in the repo in the contributing doc, but ideally it should live on the docs site where we can actually render elements from the pattern library in markup [similar to what we do with the GitHub styleguide.

cc @tangollama @jkleinsc per our 🍖 🎇 conversation this morning.

Notes from @jglovier and @tangollama's onboarding brainstorming session on 1/22

Transcribed notes

Onboarding from three perspectives

There are three ways we can look at the onboarding experience.

1. The experience for new contributors
2. The experience for sysadmins deploying a new instance
3. The experience for new end users

An example use case

Jean Francois Negrini, a surgeon in Niger, wants to find a better software system for his hospital.
Wants

• Features
  • Track patient records better
  • Reports
  • Share patient data
• To get past his current limitations (need for IT support, etc, etc)
• To be able to easily evaluate the system to see if it is the right solution for him

Ideas

• Make a demo mode in the software that can be flipped on, which is a type of sandbox for demoing the app
  • Contains a feature tour of the UI for new users to learn the app
  • Users can switch between roles to view the UI as different roles.
  • Comes with preloaded demo data set
  • From here, users can initiate a trial (new instance) of the software on their own machine
    

Note: demo.hospitalrun.io becomes a system that is always in demo mode.

• Make a trial mode that can be initiated from demo mode, which installs a new instance of the app on the users machine
  • Can ultimately be deployed to production/the cloud
  • Comes up as a blank instance to be populated with your own test data or live data
  • Lives only locally on users machine

Questions to explore

• How do we do email?
  • A: We get their email when they login to their instance/trial and use in-app analytics to track behavior
• How do we handle local/trial-mode setup WRT back end setup? (e.g. couch/pouch stuff, etc)
• How do we handle deploy to cloud?
  • UX of setting up (AWS, Heroku, etc)?

Onboarding flow diagram

Lets define a set of tasks that users will want to accomplish with the app, and then take time to run through the experience of accomplishing those tasks in HospitalRun, and accomplishing those tasks in other open source EMRs to compare the user experience. This will help us in a few ways:

• Help us develop a tangible set of tasks to measure our product requirements
• Help us gauge where we are failing or succeeding in comparison to other open source solutions
• Give us opportunity to learn from the mistakes or successes from other open source solutions

Grocery Stores

• Safeway - 1020 Johnson Ln, South Lake Tahoe, CA 96150
• Grocery Outlet Bargain Market - 2358 Lake Tahoe Blvd, South Lake Tahoe, CA 96150
• Raley's - 4000 Lake Tahoe Blvd, South Lake Tahoe, CA 96150
• Alpine Liquor - 3460 Lake Tahoe Blvd, South Lake Tahoe, CA 96150
• Dart Discount Liquors - 148 US-50, Stateline, NV 89449

Restaurants

• German
  • Himmel Haus - http://himmelhaustahoe.com/ (.3 miles from house)
• Sushi
  • http://www.thenakedfish.com/
• Mexican
  • Azul Latin Kitchen - http://azullatinkitchen.com/ (healthier version of Mexican food with locally grown and sourced ingredients
  • Chimayó Street Grill - http://www.chimayotahoe.com/
• Fine Dining
  • Nepheles - http://nepheles.com/ (eclectic California fare)
  • Cafe Fiore - http://www.cafefiore.com/index.html (Italien)

Take Out

• Blue Dog Pizza
  • http://bluedogpizzatahoe.com/
  • GF crusts available
• Vinny's
  • http://www.vinnyspizzatahoe.com/
  • New York style pizza

Cafe/Diner's

• Red Hut Cafe - http://www.redhutcafe.com/menus.html
• Driftwood Cafe - http://www.driftwoodtahoe.com/
• IHOP - 3730 Lake Tahoe Blvd, South Lake Tahoe, CA 96150

At our Tahoe meeting this week, @tangollama mentioned needing some design work for an upcoming event, including:

• Design for a booth backdrop opted not to do this
• Design for swag (hospital bracelet?)

I still need the existing design files for those.

App

Product design

• Flow for deployment
• Create overview screens for helpful info (charts, visualizations, etc)
• Dashboard concepts
  • Sketch out concepts
  • Make design mocks

Development

• Improve seed data

Cosmetic

• replace logo with new logo
• design new icons for UI
• replace octicons with SVG helpers

Login screen

• add HospitalRun logo
• add alert styling for forgotten passwords, wrong username, etc
• add forgot password link

App navigation

• fix settings nav
  • add appropriate links
  • make it so that clicking anywhere outside that nav will close it
• create minimized nav version for mobile
• add media queries for minimized nav to automatically work at smaller viewports (see GitLab for example)
• add media queries for smaller viewports for primary content panel nav, etc

Forms and views

• fix buttons on patient view
• improve seed data
• review feedback from user interviews

Front end tasks

• Clean up CSS to pass linter
• Merge jonrohan's PR

Marketing site

• improve demo page
• create community page
• create docs
• add blog
• implement responsive framework for site
  • Gridism?
  • Primer for marketing?

Per our 🍖 🎇 convo this morning with @tangollama and @jkleinsc, we really need to start defining what accessibility means for HospitalRun. We know how we can approach it from a technical standpoint, but we need someone who knows app accessibility better than any of us to take a look and give us an evaluation before we spend a bunch of time trying to solve for the wrong problems.

cc @tangollama @jkleinsc @amglovier