So remember when we said that HospitalRun 1.0 would be out in April?
We obviously missed that date by several weeks.
For the record, there were some very good and immovable reasons why that happened (for instance, JK and I were transitioning away from CURE International in the last few months), and we learned some valuable lessons about projecting release dates in open source projects.
But there’s good news. I’m pleased to announce…
HospitalRun 1.0.0 Beta is available!
If you want a complete list of all the changes, you can of course read the Change log, but I’ll try to offer a rundown of the numerous features.
The stuff you need to get work done.
- Patients, including history, diagnosis, orders, and procedures
- Outpatient Workflow
- Operative Planning and Reporting
- Appointment scheduling
- Operative theatre / resource scheduling
- Inpatient and outpatient Visit tracking
- Consumable Inventory, including stock on hand predictive reports
- Labs Queue (not yet integrated with a LIS)
- Imaging Queue (not yet integrated with a PACS)
- Medication ordering that is tied to the consumable inventory system
- Basic billing, including handling discount profiles for charitable and discounted work
- Incident Management, tracing quality issues within a facility
- Partially-configurable Roles and permissions
- User Management
The stuff that’s arguably the most special, important things about the project.
- Offline-first support (thanks to PouchDB and service workers)
- The capability to deploy to a local server AND the cloud with synchronization for free (thanks to CouchDB)
- Desktop deployment for Mac and Windows (thanks to Electron)
- Scripted server deployment (thanks to Docker)
- Near-complete internationalization (ember-i18n)
- Repo-enforced code standards (thanks to eslint)
- Automated integration testing (thanks to Travis CI)
- Over 1,000 acceptance tests
- A donated Demo environment (thanks to Microsoft Bizspark)
- Incredible traceability on the project repository for issues, projects, and code (thanks to GitHub)
Key Time-saving Features
The stuff we’re arguably most proud of.
- Custom forms with current support for Patients, Social Work, Visits, Outpatient Reports, Labs, Incidents, Operative Plans and Reports, and Discharge Reports
- Shortcode support, allowing common text to be “short-handed” into all text fields
- Operative plans that become one-click operative reports
- “Grow with you” Lookup lists: start with empty metadata, lock down your system (per meta data field) as you are ready to formalize your taxonomies
- Google Apps authentication
- A relatively intuitive user interface
- Inventory-aware consumption of Medication and Supplies, helping resource-constrained environments plan to deliver only what they have available
In total this release involved nearly 100 code contributors and over 3,000 commits. Thank you to everyone involved in producing this first, important step for the project. We believe that HospitalRun can and will do a lot of good in the world because of you.
We also need to thank the following groups.
The stuff that helps makes the project sustainable.
- Over 2,800 stars/recommendations as one of - if not the - most popular open source health project on GitHub
- Over 500 members in our project Slack
- Marketing and video support from companies like GitHub, New Relic, and CURE International
- Amazing support from other open source movements like Ember, Electron, PouchDB, CouchDB, and the Offline First communities… with a tip of the hat to projects like Ember Electron and Hoodie that have been a big help. Thank you all!
That’s really up to all of us. As people start to download and use the system, rest assured there will be an active stream of change requests, and we need your help to keep up with the demand. If you’re looking for a game-changing feature to work on, how about auto-provisioning a cloud instance from the Electron Desktop download? There’s a feature ticket for it right here. You could also finish auto-generating a research instance of the data.
If you’ve been think about contributing, this Summer (or Winter for my southern hemisphere friends and colleagues) would be a great time to start.