We were inspired to create this simple tool that would make communication between patients more effective in terms of automating the discharge process. By allowing the physician to provide the patient with a detailed list of procedures we would be able to make the discharge process faster. Our main concern when building this product was to bridge the gap between any miscommunication that may occur between the patient and the physician.
What it does
he basic architecture of the app is as follows:
NFC Bootstrapper (phone-app) <--MQTT--> server --MQTT--> web-app
The basic idea is that the user (patient) uses NFC from his phone to quickly pull the required data from the server. NFC is only using for bootstrapping and connecting the web app to the server. Once the app is connected, the NFC has not used anymore.
The Web App, in its current state, shows the required steps that the patient needs to follow in order to complete the discharge process. However, updating the state of each step is not possible yet.
As outlined in the diagram above, MQTT was used for all communication between devices.
How we built it
All of our modules make use of a MQTT library in order to connect to the public sandbox MQTT broker iot.eclipse.org on port 1883.
The Phone App, which simulates the NFC bootstrapping between the web app and the server is written in Python and uses PAHO MQTT for connecting to the broker.
The server is the component of our app that takes care of information routing between the components. The server connects to a database where all the patient data is stored. Once a pairing request is received, it validates that the patient exists and sends the patient information back to the web app.
The server is written in Golang, and uses gobot for MQTT communication and gorm for database manipulations.
Challenges we ran into
One of the biggest challenges was to decide which programming languages and frameworks to use that would be able to effectively integrate with our database and each other. We also were able to integrate MQTT into our program even though no one in our group had prior knowledge communication protocol before let alone network programming. Also, we had to effectively send data to and from different programming languages and databases.
Accomplishments that we're proud of
Effectively creating a system design and its implementation that we were that was able to serve as a guide throughout the whole project. As a team that had formed the day of the hackathon, we were able to effectively collaborate with each other and learn from each other's skillsets.
What we learned
One of the biggest things our whole team had to learn was mqtt. Also, we were able to help each other out with programming concepts and git commands that we may not have known how to do.
What's next for CodeRED_2017
What we have today is a very simple prototype. For the next version, we hope to have a GUI to load and modify data. We would also want to use the actual device as a link between the app and the server.