HospitalRun Prerelease Beta Process

This document outlines the objectives, process, and expectations of the HospitalRun prerelease beta program.

Objectives

To validate the utility of the deployed functionality of HospitalRun with a select set of constituents under a varied set of implementation needs (small vs. larger, outpatient vs. inpatient, etc.)
To capture focused feedback on feature, process, or architectural changes that might be needed to move the product to a 1.0 release
To begin to build the implementation processes and tools to achieve our #1 requirement: usability
To ultimately serve the functional needs of the beta partner facilities

How will the Beta program work?

The following should be initiated on or about June 6, 2016

Beta application form is sent to key partners with an invitation to forward to others
Beta email list subscription is launched on hospitalrun.io/beta
All beta email list subscribers are sent the application form and invited to apply
HospitalRun Slack #general channel receives an form for community members to apply to participate in the beta process

The following should consist of a two-week process from the time a beta candidate submits an application.

Beta candidate applies to be a part of the beta
Within 2 days, a beta candidate's application is routed to a pair of HospitalRun community members to review the application
Within 5 days from applying, a beta candidate is contacted by a pair of authorized HospitalRun community members to conduct a validation interview
HospitalRun community members confirm the details of a candidate's application questions by a phone or video chat interview
HospitalRun community members either recommend or reject a beta candidate
Within 2 weeks from originally applying, a beta candidate is informed whether they will be a part of the beta