clinical-meteor / meteor-on-fhir

Meteor using Fast Healthcare Interoperability Resources (FHIR)
http://meteor-on-fhir.meteorapp.com/
GNU Affero General Public License v3.0
55 stars 15 forks source link

Can't get it to launch #74

Open ramezrafla opened 4 years ago

ramezrafla commented 4 years ago

@awatson1978 I heard so much about clinical-meteor, but I can't get it to work.

The screenshot in the README is very nice, but we can't get the app to launch properly. I followed the instructions and I get a missing landing page error

Are there any instructions anywhere or should I use a different repo / branch?

Thanks

awatson1978 commented 4 years ago

Hi! May I please direct you to Node on FHIR, the successor project to Meteor on FHIR. :)

Node on FHIR still uses the meteor build pipeline, but relies on HTTP/OAuth2 instead of DDP, and uses all of the FHIR based libraries I could find on NPM. It's by far the better tech stack. Less bloat. Same design patterns. Newer documentation. Actively being worked on.

And hey, it's been picked up by the Linux Foundation for Community Bridge crowdfunding. Cool! https://funding.communitybridge.org/projects/node-on-fhir

ramezrafla commented 4 years ago

Thanks so much. Works better now. How easy is it to make a hospital management solution with it? Do you have setups we can start with? It seems to be built as a template for other projects to leverage

awatson1978 commented 4 years ago

"Meteor makes difficult things easy, and impossible things possible."

I would say Node on FHIR brings the difficult of building a hospital management solution down from 'near impossible' to 'difficult but doable'. It really depends on what you want out of your management system. The problem at hand is generally in terms of it being a broad domain. If you're just wanting to analyze encounters and create some reports, you can knock out an analytics dashboard in just a couple of months. If you want to import all the FHIR resources and create complex workflows that track a patient from registration through discharge.... doable, but will take upwards of a year.

The setup is all contained within the packages/example-plugin directory. Key things to remember are to use the --settings option and to use --extra-packages as needed. Take a look in the configs directories for different setup files. There are configs in both the main app, as well as the example plugin directory. We will try to create more examples going forward, but we need some sponsorship and runway first.

And yes, it was built with a WordPress architecture in mind. So it's meant to be a base template, that people build plugins for.