hospitalrun/hospitalrun.io

HospitalRun website

HospitalRun website

With Jekyll 3 it was must necessary to switch from GitHub Pages to Netlify.

Development

hospitalrun.io is made with Jekyll a simple, blog-aware, static site generator. It takes a template directory containing raw text files in various formats, runs it through a converter (like Markdown) and our Liquid renderer, and spits out a complete, ready-to-publish static website suitable for serving on Netlify.

If you already have a full Ruby development environment with all headers and RubyGems installed, you can follow this simple step:

1. Run bundle install to install the dependencies
2. Run bundle exec jekyll build to build on local
3. Run bundle exec jekyll serve to start the Jekyll server

Directory structure

.
├── Gemfile
├── _config.yml
├── _data
│   ├── faq_page.yml
│   ├── future_roadmap.yml
│   ├── navigation.yml
│   ├── slider.yml
│   ├── sponsor.yml
│   ├── team_emeritus.yml
│   ├── team_members.yml
│   ├── testimonials.yml
│   └── trending_items.yml
├── _includes
│   ├── blog_and_items.html
│   ├── call_to_action.html
│   ├── cookie-consent.html
│   ├── enterprise.html
│   ├── features.html
│   ├── footer.html
│   ├── ga.js
│   ├── gtm.html
│   ├── gtm.js
│   ├── header.html
│   ├── help_area.html
│   ├── map.html
│   ├── page_header.html
│   ├── pagination.html
│   ├── post_loop.html
│   ├── sidebar.html
│   ├── slider.html
│   ├── social_share.html
│   ├── sponsor_area.html
│   ├── team_area.html
│   ├── team_area_emeritus.html
│   ├── testimonials.html
│   ├── text_area.html
│   ├── timeline_area.html
│   ├── tryit.html
│   └── why_area.html
├── _layouts
│   ├── blank.html
│   ├── default.html
│   ├── page.html
│   ├── post.html
│   └── tag_page.html
├── _posts
│   ├── 2014-08-25-coming-soon-hospitalrun-10.md
│   ├── 2014-08-25-hospitalrun-early-release-in-september-2014.md
│   ├── 2016-06-06-why-hospitalrun.md
│   ├── 2017-05-23-announcing-hospitalrun-1.0.0-beta.markdown
│   ├── 2018-02-26-roadmap-to-hospitalrun-1.0.markdown
│   ├── 2018-07-01-help-wanted-a-message-from-the-co-founders.markdown
│   └── 2019-08-07-a-new-beginning.md
├── assets
│   ├── css
│   ├── fonts
│   ├── images
│   ├── img #legacy folder
│   ├── js
│   └── scss #use this file to edit css
├── gulpfile.js
├── index.html
├── package.json
├── pages
│   ├── blog.html
│   ├── contacts.html
│   ├── contribute.html
│   ├── demo.html
│   ├── download.html
│   ├── faq.html
│   ├── features.html
│   ├── map.html
│   ├── privacy-policy.html
│   ├── roadmap.html
│   ├── standards.html
│   ├── team.html
│   └── tryit.html
├── robots.txt
└── search.json

hospitalrun.io's Issues

Fix the URL beta.hospitalrun.io

The page http://hospitalrun.io/demo/ asks to use the URL https://beta.hospitalrun.io/ to access the demo. But the URL is not working.

Reproduction steps

• Visit http://hospitalrun.io/demo/
• Click on https://beta.hospitalrun.io/
• The link is not working

Request the facility name, city/region and country of the deployment.

Demo page design cleanup

The current demo page is a quick and dirty implementation but needs some design love. The list could be laid out better, and there could be a screencap again on that page.

browser support for flexbox

Right now I'm vertically centering the page contents for the temp landing page with css flexbox. Browser support, however, is pretty limited right now, so I'm need to take some time to implement the vertical centering another way. Flexbox was just the fast way to get it done initially.

Another CHINESE EDITION

---

title: Contribute to HospitalRun
layout: default

对在HospitalRun项目中做贡献有兴趣吗？

在最近的一段时间内，这里只有不多的项目可以贡献。 随着项目扩大, 这里将会有更多的贡献. 我们希望你能看到我们所做的一切，并请以您擅长的方式参与进来。

成为一名代码贡献者

HospitalRun是由如下技术打造的Node， React, Fastify and CouchDB。如果您已经使用过这些技术，或者有软件开发经验，并且有兴趣学习这些技术，请考虑为HospitalRun做出贡献。 如果你对贡献有兴趣 加入我们的Slack（许多项目的主要贡献交流发生的地方）

对HospitalRun进行资金贡献

Contribute on our Open Collective page!感谢你为该项目的一些支出做贡献。
如果你想用一个特别的资金贡献来支持这个项目，发邮件给 mailto:[email protected] 来讨论你怎样实现。

build a temporary landing page

Something simple that just has:

• logo
• short description
• links to GitHub repo and Twitter account
• email subscribe form (create separate issue and branch for this)

Site redesign

We need to make some major changes to the webite. Let's use this issue to track all the ideas that will come.
I'll put down some of them as a start:

• link to spectrum and slack community
• add GitHub banner that links to the GitHub's HospitalRun org
• team page
• "used by" section
• "supported by" section
• "powered by" section
• better blog experience
• use a new jekyll template
• documentation for tech people
• extensive wiki with the documentation for non tech people

Partners page

We need a standard design for managing a /partners page that includes the logo of a given company / NGO / government entity that is recognized as a formal partner. For starters, I'd like to get the following onboard (and therefore surfaced on the website).

• CURE International
• eHealthAfrica
• New Relic
• Microsoft's Bizspark
• Ember Sherpa

And hopefully soon (formally)

• GitHub (hopefully)
• SATMED (government of Luxembourg)
• Ember

Request the email/contact of the administrative contact for a deployment

"Try hospital run" Demo not working

Hi,

I am not sure to which repository of HospitalRun this issue belongs to. I figured this one to be the best fit.
I stumbled across this project and wanted to try the demo via the demo link on your website. This forwards me to the beta instance.

I do get a connection error when browsing beta.hostpialrun.io .

Cheers

Update to Jekyll 4

Update website to the new major release of Jekyll

add screenshots to landing page

While the UI has a long way to go, and will likely undergo plenty of changes, it would be good to add some screenshots (probably with multiple devices, showcasing that it's responsive and accessible) to the landing page.

Add blog

Per @tangollama's comments in Slack, we need a blog.

Wikipedia page

Dear Maintainers,

My name is Matthew Vita, a programmer in the healthcare industry. I am trying to help build up the high impact "List of open-source health software" Wikipedia page (https://en.wikipedia.org/wiki/List_of_open-source_health_software) and would love to add your software to the list. However, it appears that your project does not have a page on Wikipedia so I ask you to consider the following:

1. Adding a nice article for your project (see the GNU Health article (https://en.wikipedia.org/wiki/GNU_Health) for a really good example and Ginkgo CADx (https://en.wikipedia.org/wiki/Ginkgo_CADx) for a lightweight, but acceptable example).
2. Adding said article to "List of open-source health software" Wikipedia page (https://en.wikipedia.org/wiki/List_of_open-source_health_software).

(If you’re already on Wikipedia, my search-fu wasn’t working when I looked you up so please consider doing only step 2 above)

Thanks,
Matthew

Surfacing docs on the project site

We should really have a better documentation experience, directly from the project site. Right now we're linking to the project Wiki, but we can do much better. For some great examples, see the following docs sites:

• Bootstrap
• Ember
• Ratchet
• jQuery
• Jekyll
• etc

I'll do some design comps and work on a framework for this part of the site. The part I can't do is writing the actual docs, so would someone like to work on rewriting the docs in a more digestible, narrative format?

add Gemfile

for kramdown

Events Page Out of Date

Hi Team!

I know that this isn't necessarily a place where you're looking for assistance, but I did notice that the Events page is out of date.

I'm not sure if you have more events looming and would like to update this yourself, but if not I'm happy to make a quick switch with push access. 😄

Transfer domain to another domain provider

OpenJS has some agreements that motivate the use of Godaddy for domain hosting.

You should transfer the domain.

Demo landing page

Links to https://beta.hospitalrun.io

Account information
[email protected] - HR_Business Office
[email protected] - HR_ Doctor
[email protected] - HR_Imaging Tech
[email protected] - HR_Inventory Manager
[email protected] - HR_Lab Tech
[email protected] - HR_Nurse Manager
[email protected] - HR_ Nurse
[email protected] - HR_Patient Admin
[email protected] - HR_ Pharmacist
[email protected] - HR_Social Worker
[email protected] - HR_System Admin

'Proceedures' spelling mistake on front page image

On hospitalrun.github.io/img/screenshot-mock-sm.jpg I can see 'Proceedures' being used twice. Believe the correct spelling is 'Procedures'.

GH Pages build failure due to upgrade to Jekyll 3.0

GH Pages recently updated to Jekyll 3.0, and we need to update some of the dependencies accordingly.

The page build completed successfully, but returned the following warning:

You are attempting to use the 'pygments' highlighter, which is currently unsupported on GitHub Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the 'highlighter' value to 'rouge' in your '_config.yml' and ensure the 'pygments' key is unset. For more information, see https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors.

GitHub Pages was recently upgraded to Jekyll 3.0. It may help to confirm you're using the correct dependencies:

  https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

For information on troubleshooting Jekyll see:

  https://help.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can contact us by replying to this email.

Evaluate if ubersicht suits our needs

🚀 Feature Proposal

Check if https://github.com/espy/ubersicht can help in showing all of our issues in only one place.

Motivation

We need only one place, possibly linked on our website, to show to the community all of the issues that needs attention.

Setup custom domain `hospitalrun.io`

Now that the temp landing page is stubbed out, we need to setup the custom domain hospitalrun.io now. Jekyll/GH Pages makes this really easy for us. I'll add a CNAME file to the root, then someone with DNS access just needs to follow the instructions here under the Apex Domains section (you'll probably have to go the A record route, unless your DNS provider supports domain aliases.

Append the word "free" to the front of the front page description

Multiple times a week, I get an email from people asking how much they need to pay for HospitalRun. I respond politely to them all, but it occurred to @jglovier and I to change the website to include the word "free" before "open source" to try to address this.

Map the data feedback forms into /usage screen on hospitalrun.io using the Google Maps API to demonstrate where the project is being used.

Hospital Stories

As a prospective Hospital Run user, I want to learn about how other practices/hospitals are using Hospital Run and how it works for them so that I can determine whether Hospital Run is a viable solution for me.

Need:

• Refactor Hospital Stories landing page
• Determine content priority/wireframe for a case study/Hospital Story detail page

Information on the Team behind the HospitalRun and their roles

It would help us to understand better if some information on the Team behind HospitalRun and their roles are provided on the website hospitalrun.io

A proper Sketch file for designer contributors to contribute to the marketing website

Expected behavior:

As a designer who wants to contribute to an open source project such as Hospital Run for the first time, I want to be able to immediately start on building a new mockup from a Sketch file with components I can re-use.

Actual behavior:

Right now, after downloading the design source files, it seems there is only a Sketch file for the App UI. As a result, I will either have to recreate the elements I see on the site itself on Sketch, or make screenshots and chop up what I can use.

@jglovier Unless there's a file that just hasn't been uploaded? :/

Steps to reproduce:

Screenshots (if applicable):

OS and Browser:

Mobile fixes

In #10 I rushed to get a redesign out the door, but it still needs some minor fixes for mobile. Mostly layout spacing and such.

HEY,I bring a Chinese edition of readme.md!

HospitalRun 网站

这个项目包含着最近的HospitalRun网站. 由 GitHub Pages 和 Jekyll.支持

---

运行 / 开发

如果你想在本地网络开发环境中管理这个网站，你将使用Ruby.

0.安装 Jekyll 和 bundler gems gem install jekyll bundler 1. 克隆数据库 git clone [email protected]:HospitalRun/hospitalrun.github.io.git 2. 换到你的新目录中 cd hospitalrun.github.io 3. Install missing gems bundle install 4. Build the site and make it available on a local server bundle exec jekyll serve

你应该看到像这样的提示:

Configuration file: /HospitalRun/hospitalrun.github.io/_config.ym Source: /HospitalRun/hospitalrun.github.io Destination: /HospitalRun/hospitalrun.github.io/_site Incremental build: disabled. Enable with --incremental Generating... done in 1.795 seconds. Auto-regeneration: enabled for '/HospitalRun/hospitalrun.github.io' Server address: http://127.0.0.1:4000 Server running... press ctrl-c to stop.

1. 切换到 http://localhost:4000

折叠的结构

sh hospitalrun.github.io/ ├── _assets # Mockup ├── _includes # HTML structure ├── _layouts ├── _posts # Blog posts in Markdown ├── _sass ├── _site # Generated pages from source ├── beta ├── blog ├── contribute ├── css ├── demo ├── events ├── hack-week ├── img ├── lisbon ├── partners ├── team └── tryit

许可协议

根据 MIT license.发布

Add a community standards page

As HospitalRun contribution involvement grows, we should have a clearly defined set of community standards for how to interact with each other to help define how we want our community to treat each other. It's our job to help make being a contributor to open source a positive, welcoming, and inclusive experience. Having a clearly defined set of standards for interaction and communication is important to that end.

Here is some great prior art:

• http://julialang.org/community/standards/
• https://nodejs.org/en/get-involved/
  • (:point_up_2: links to: https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-of-conduct)
• http://emberjs.com/guidelines/
• http://bundler.io/conduct.html

Demo webpage not working

http://demo.hospitalrun.io/ not opening and giving timeout error even in the high speed internet

Consume the submitted information for a feedback form in a central service under the hospitalrun.io domain

Fix broken links and error 4xx

Follow this Excel file as a reference

Text revision

@fox1t @StefanoMiC @irvelervel can you take care of it?

This site can’t be reached - beta.hospitalrun.io

This issue was pointed out and fixed before, however, the problem is back again: #49

URL https://beta.hospitalrun.io/ is not working.

Reproduction steps

• Visit http://hospitalrun.io/demo/
• Click on https://beta.hospitalrun.io/
• The link is not working

Build page for Why HospitalRun

Right now, the Why HospitalRun link just points to a Google Doc. Let's make a page for a better user experience than just reading all the content in a Google Doc.

The biggest question is how to structure the content, if differently from the Google Doc? For starters, we could certainly just use the outline in the doc, but having an actual landing page does give us a way to express the content in a more creative format. Thoughts on what you might do differently given that format?

In the meantime I'll work on comping up a basic version from the existing page content/layout.

Discourse page is broken

Blog post announcing help wanted is broken: https://hospitalrun.io/blog/wanted-discourse-manager/

Prioritization

@danielgolden and I just chatted about the things that need work on the site, and I decided it would be really helpful to have a place to document the priorities. In rough order from my perspective, here's the prioritized list:

• Blog work (see #9)
• Demo page cleanup (see #12)
• Why HospitalRun page (see #15)
• Features page (see #6)
• Contributors page
• Partners page (see #30)
  • happening in #53
• Documentation (see #14)

cc @tangollama and @tracicakes who may have also input on the prioritization.

features page

Here's the current list.

Offline-first architecture to allow access anywhere, regardless of variable connectivity
Dual deployment architecture, allow local and cloud installation to work seamlessly
Inventory management (including audit tracking and cost accounting)
Patient management
Procedures (including ICD-10 coding for diagnosis and procedures)
Appointments & Visits (inpatient, outpatient, pharmacy, vitals)
Imaging queueing
Lab queueing
Pharmacy/medication queueing (tying into the inventory system
Predefined security rights & roles

The follow modules/task are still outstanding:
Billing/Invoicing/Receipting
Automated and adhoc operational reporting
Exporting billing formats for insurance processing
Integrating PAX (imaging) and CT solutions into the imaging queue
Defining a strategy for Lab system integration
User-defined role and security management
Bed management and patient workflows
Alertings
Optimizing the development environment
Production deployment optimization
Cloud-based packaging, partnership, and deployment

Blog paginator issue

Help styling the tryit page

In preparation for a release of a 1.0 beta, we have a new page on the website. I did the messaging, but it looks like garbage. I'm logging an issue as a basis to request for help bringing this thing to completion. https://github.com/HospitalRun/hospitalrun.github.io/tree/try-it

Updating administrative contacts when a new release is delivered via newsletter

Send the contact information from a feedback form (as provided) into the HospitalRun Releases list in the project Mailchimp account for the purposes of updating administrative contacts when a new release is delivered.

How do people contribute to the project?

Love the premise of this project and was looking into how to contribute but couldn't find anything that outlined:

• If external contributions are accepted
• What type of contributions or help you're in need of
• In terms of coding, a central place that outlines all the libs, frameworks, technologies and skills that form the project so that an individual can see if they have something to contribute

The jQuery project has a great Contribute page that goes into a lot of detail about how to engage with the project. It'd be great to see something like that.

Thoughts?

Add documentations

The inspiring story link is broken, or it says page not found

🐛 Bug Report

In this page , Great for New Contributors, the inspiring story is
a broken link, because when i tried to visit this page, it says Page Not Found

To Reproduce

Steps to reproduce the behavior:

[the inspiring story](https://hospitalrun.io/blog/2016/06/why-hospitalrun)

Expected behavior

I suggest that it may be this link that you're trying to direct viewers to.

[the inspiring story](https://hospitalrun.io/stories)

Your Environment

• os: Windows
• Browser: Google Chrome

What's happening with HospitalRun.io?

I wanted to reach out to ask what was happening with HospitalRun.io. I was looking at your website, but it seems that the demo is offline, there are several GitHub repositories that have been archived, and the Twitter page seems to be full of automated updates.

I'm looking for a Hospital Information System for a hospital that desperately needs one, and HospitalRun seems like it could be the perfect solution. Has this project been given up on or am I missing something? If if is available, how could I go about setting up the web application?

Redesign home page

The landing page sucks. It just does. Once the new UI lands, we should add a screencap, and start to think about making the landing page actually present a pitch with features and benefits, etc.

Here's an initial mock. We can tweak content accordingly, but this is the general direction I'd like to take for the next iteration. Note this only addresses the home page for now, but we'll also need to think about other parts of the site that exist and need attention (demo site landing page, blog), or don't exist at all (docs, features page, about page, etc.)

cc @tangollama @jkleinsc

❤️ 🎨 💄

testing gitmagic with issues