mdpnp / bigwalldisplay_1 Goto Github PK

Concept demo for the layout of a nurse workstation-like UI and assessment of the involved technologies.

License: MIT License

CSS 2.95% HTML 37.44% JavaScript 59.61%

bigwalldisplay_1's Introduction

BIG WALL DISPLAY

This project is a concept demo for the layout of a user interface (Big Wall Screen) displaying vital signs and other information for a group of patients.

Basically, the Big Wall Screen is the UI of a "nurse station", but should be responsice in smaller devices/screen too. This project is meant to help visualizing the final result of such UI and thus help brainstorming and refining the UI itself and a technology stack meant to be used to gather patient data through OpenICE and display such information in a meaningful way. Click here for more information about the OpenICE platform.

Technology Stack

These technologies have been selected to help rapidly prototyping the UI and may have nothing to do with other technologies (databases, middleware, etc.) involved in other MD PnP projects trying to implement this idea.

Mongo 3.0.X as DB
Meteor A reactive full-stack JavaScript platform. This app uses Blaze as template language / view layer.

To run

Running with just $meteor will create/use a local database. Use the MONGO_URL environment variable to connect to a database. for example (to connect to a Mongo server running localy):

$ MONGO_URL=mongodb://localhost:27017/warfighter meteor

Syntax is MONGO_URL=mongodb://user:pass@host:port/dbname. Host and port may change accorging to environment.

bigwalldisplay_1's People

Contributors

Stargazers

Watchers

Forkers

aslanr

bigwalldisplay_1's Issues

change "assessment" label

Having assessment twice on the tile (once for the clinical decision support's assessment and again for a clinician input) leads to confusion.

Change the "assessed" label to last examined or similar.

Change the button to "Patient Checked" or similar.

layout with 10 patients

Add a different layout.

Layout 1. Current layout with 3 rows of 4 tiles (12 patients)

Layout 2. 2 rows with 5 tiles each

This issue/enhancement is a direct consequence of the requirement of needing to have 10 patients on screen.

Show trends

Show next to each metric an arrow pointing up or down to let the users understand better if a value has been going up or down over time.

Exception while polling query {"collectionName":"patient_demographic","selector":{}

Investigate this exception that sometimes I get in my local env

Exception while polling query {"collectionName":"patient_demographic","selector":{},"options":{"transform":null}}: Error: failed to connect to

connect to PostgreSQL DB?

We may need this project to connect to to a different DB than MongoDB. PostgreSQL could be one.

Check this article and research into others about how to connect with meteor to something different than MongoDB.

bad message / diagnostic

Those conditions are not hypertension. Maybe the message is not refreshing well after updating the DB.

change color of timestamp label

Change the color of the label for the timestamp from green to yellow when there is no information of the info is too old. Rationale, is that we don't want to show something "green" which means OK when the patient is not checked or has been checked a long time ago.

App sometimes crashes, unable to establish a connection w/ DB

the latest log
/Users/diego/.meteor/packages/meteor-tool/.1.3.1.1tiubdb++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:300
throw(ex);
^
Error: failed to connect to [localhost:27017]
at Object.Future.wait (/Users/diego/.meteor/packages/meteor-tool/.1.3.1.1tiubdb++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:420:15)
at new MongoConnection (packages/mongo/mongo_driver.js:213:27)
at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
at Object. (packages/mongo/remote_collection_driver.js:38:10)
at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
at new Mongo.Collection (packages/mongo/collection.js:102:40)
at meteorInstall.imports.api.patients.js (imports/api/patients.js:4:25)
at fileEvaluate (packages/modules-runtime.js:158:9)
at require (packages/modules-runtime.js:92:16)
at meteorInstall.server.main.js (server/main.js:3:1)
- - - - -
at [object Object]. (/Users/diego/.meteor/packages/npm-mongo/.1.4.42.1ybqvxj++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:556:74)
at [object Object].emit (events.js:106:17)
at [object Object]. (/Users/diego/.meteor/packages/npm-mongo/.1.4.42.1ybqvxj++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:156:15)
at [object Object].emit (events.js:98:17)
at Socket. (/Users/diego/.meteor/packages/npm-mongo/.1.4.42.1ybqvxj++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection.js:534:10)
at Socket.emit (events.js:95:17)
at net.js:834:16
at process._tickCallback (node.js:458:13)
Exited with code: 8
Your application is crashing. Waiting for file change.

data visualization

Visualization of data in separate patient pages (upon clicking on a tile)

found dygraphs here: https://econsultancy.com/blog/66131-17-visualisation-tools-to-make-your-data-beautiful/ and it seems that there is a wrapper for meteor: https://github.com/crazyrohila/meteor-dygraphs

Add inputs to patient tiles

Add input fields to the patient tiles, such as:

1- A button for "patient assessed". Upon clicking the button (to indicate that the patient's status was just assessed) another field will display the timestamp of when the patient was assessed for the last time.

2- A check box (or dropdown?) for "mental status" (values normal or abnormal). This input would be used to asses CNS (central neurological system) functions.

Choose between list and grid to display "patient cards"

The layout options could offer to choose between a "list" or "grid" layout for the patient's info.

Maybe depending on this choice the patient template could change (on a list layout we may have enough room for a waveform for certain metrics, while on a grid layout we won't, but we'll have smaller charts that would maximize the amount of patients/info that we can display in the screen).

This choice would be tightly coupled with the number of patients to show. The advantage of a grid is that charts are smaller, not needing that much room, so we would be able to have the info of more patients on the screen.