For my Masters of Science in Biomedical Informatics, we are required to create a Capstone Project. So I decided to write a Health Information Exchange infrastructure. The technical infrastructure uses MongoDB (a modern hierarchical database, similar to the MUMPS/Cache database what Epic uses), a full-stack isomorphic javascript framework called Meteor, and Facebook's user interface layer React. The HIE uses a wordpress business model, and is intended to be a distributed and federated peer-to-peer network. We use HL7 Fast Healthcare Interoperability Resources (FHIR) for data exchange and interoperability.
NOTE: We have recently refactored the codebase. We removed a ton of clutter, stale prototypes, dead code, and binary files that were tying Meteor on FHIR to Mac/Linux. Meteor on FHIR should now run on Azure, and is configured as a community build by default. You may notice some missing functionality, such as theming, geomapping, timelines, and other features. Please contact demos@symptomatic.io if you need access to those features.
Yes, the above is a live screenshot of the app, which supports a theming engine and an augmented reality interface.
# get the application
git clone http://github.com/clinical-meteor/meteor-on-fhir
# move into the webapp directory
cd meteor-on-fhir/webapp
# clone the example plugin
git clone http://github.com/clinical-meteor/example-plugin packages/example-plugin
# install the example plugin
meteor add clinical:example-plugin
# install the app
meteor npm install## general development
meteor --settings configs/settings.blank.canvas.json# install sample doctors and nurses
meteor add clinical:accounts-housemd
# run with initialization variables
INITIALIZE=true Patients=true Practitioners=true meteorEdit the settings.dev.json file, and update:
{
"public": {
"title": "Rainbow's End Nursing Home Health Exchange",
"theme": {
"backgroundImagePath": "/backgrounds/medical/Gradient.jpg",
"backgroundColor": "#34B6C2",
"palette": {
"colorA": "#34B6C2",
"colorB": "#177AB9",
"colorC": "#31323C",
"colorD": "#710A4A",
"colorE": "#FFFFFF"
}
},
"meshNetwork": {
"upstreamSync": "http://meteor-on-fhir.meteorapp.com/fhir-3.0.0",
"autosync": false
}
},
"private": {
"practitionerAccessCode": "practitionerAccessCode",
"sysadminAccessCode": "sysadminAccessCode"
},
"galaxy.meteor.com": {
"env": {
"MONGO_URL": "mongodb://username:password@mlab.com:25389/my-org-exchange-db",
"NODE_ENV": "produciton"
}
}
}
Run the script to remove restricted media assets:
scripts/remove_restricted_media_assets.sh
# don't include geodata
cd webapp
mv public/geodata ..
# development
# this can be tricky, because http://localhost:3000 may need to be a local IP address
# you may need to use `ifconfig` to find that address
# beware network isolation, and make sure your phone and workstation are on the same network
NODE_ENV=dev meteor run ios-device --mobile-server http://localhost:3000 --settings configs/settings.dev.json
# production
# we need to specify the production server
NODE_ENV=dev meteor run ios-device --mobile-server http://meteor-on-fhir.meteorapp.com --settings configs/settings.galaxy.json # build the executables and add them into the /public directory
meteor add-platform ios
meteor add omega:meteor-desktop-watcher@=0.11.1 omega:meteor-desktop-bundler@=0.11.1 omega:meteor-desktop-localstorage@=0.0.11
# install meteor-desktop / electron
meteor npm install --save meteor-desktop
# add the .desktop directory, which has files needed by omega:meteor-desktop
npm run desktop -- init
# run the app server locally, as if you were doing a mobile build
# (you may be able to just use the running mobile build server)
NODE_ENV=dev meteor --mobile-server http://localhost:3000 --settings configs/settings.galaxy.json
# then to run the desktop app locally...
npm run desktop
# or try the shortcut script
meteor npm run-script desktop
# If you want to build a production release, that connects to the main server, you'll need to specify a different URL
meteor --mobile-server http://www.symptomatic.io --settings configs/settings.galaxy.json
npm run desktop -- build-installer http://www.symptomatic.io# remove the desktop pipeline before building for Galaxy
meteor reset
meteor remove-platform ios
meteor remove omega:meteor-desktop-watcher omega:meteor-desktop-bundler omega:meteor-desktop-localstorage
meteor npm remove meteor-desktop
rm -rf node_modules
rm -rf .desktop-installer
meteor npm install
# upload to Galaxy
TIMEOUT_SCALE_FACTOR=10 DEPLOY_HOSTNAME=us-east-1.galaxy-deploy.meteor.com MONGO_URL=mongodb://<dbuser>:<dbpassword>@ds019638.mlab.com:19638/clinical-meteor meteor deploy --settings configs/settings.galaxy.json meteor-on-fhir.meteorapp.comaz webapp deployment user set --user-name admin --password password
az appservice list-locations
az group create --name appName --location 'Central US'
az appservice plan create --name appServicePlan --resource-group appName --sku S1
az webapp create --resource-group appResourceGroup --plan appServicePlan --name appname # prepare environment variables
export METEOR_SETTINGS="$(cat ../../webapp/packages/example-plugin/configs/settings.blank.json )"
export ROOT_URL=https://appname.azurewebsites.net
export MONGO_URL=mongodb://user:password@cosmodb.documents.azure.com:10255/?ssl=true
# Now that Azure is configured, go to application
cd webapp/packages
git clone https://github.com/clinical-meteor/example-plugin
cd webapp
# stringify the settings.json file; and add to Azure METEOR_SETTINGS
cat packages/example-plugin/configs/settings.json | tr -d ' ' | tr -d '\n'
# add required packages
meteor add clinical:example-plugin
# remove unnecessary packages
meteor remove-platform ios
# run local production build
npm install
node start
# meteor-azure
meteor-azure --settings packages/example-plugin/configs/settings.blank.json
# debugging
curl -u admin https://appname.scm.azurewebsites.net/api/logstream
curl -u admin https://appname.scm.azurewebsites.net/api/logstream
curl -u admin https://appname.scm.azurewebsites.net/api/logstream/application
curl -u admin https://appname.scm.azurewebsites.net/api/logstream/kudu/deploymentTo enable network synchronizing, you'll need to specify an upstream sync partner in your settings.json file. Afterwards, you can enable manual synchronization in the *Data Management page.
{
"public": {
"meshNetwork": {
"upstreamSync": "http://meteor-on-fhir.meteorapp.com/fhir-3.0.0",
"autosync": false
},
}
}HL7 v2 to FHIR Interface Mapping
Docker containers are pretty exciting, and we now support containerization and container composition of the Meteor on FHIR architecture.
# build the docker image
cd webapp
docker build -t symptomatic/meteor-on-fhir .
# run the docker image; you'll need to set environment variables
# beware that each container has it's own localhost address; so 127.0.0.1 won't point to the same container
# you'll need to link containers and/or enable host or bridge networking
docker run -d -e METEOR_SETTINGS="$(cat configs/settings.dev.json)" -e MONG_URL=mongodb://111.222.333.444:27017/meteor -p 80:3000 symptomatic/meteor-on-fhir
# push the container to your infrastructure
docker push symptomatic/meteor-on-fhir
# or run the orchestration and monitor logs
docker-compose up
docker-compose logs
# and general maintenance and devops
docker images
docker ps
docker inspectFor more details on running Dockerized Meteor apps in production, see: https://projectricochet.com/blog/production-meteor-and-node-using-docker-part-vi
Supporting Interoperability – Terminology, Subsets and Other Resources from Natl. Library of Medicine
Health IT Standards for Health Information Management Practices