ferviddigital / healthrecord Goto Github PK

When first creating a new record, pages like Vitals and Measurements only show the page title and description when there is no data.

• Create informative notice on Vitals page
• Offer one-click creation of simple vital suggestions like body weight and heart rate
• Create informative notice on Measurements page
• Create informative notice on individual Person page

Use bootstrap style notices.

Allow a user to set a password for their signal server configuration to enable use of public signaling servers. y-webrtc has this functionality already built in. Create UI and logic to enter and store.

Presently, HealthRecord has an exclusive private copyright license. In order to make this software an attractive open source project, contributors will need to know their contributions are respected and protected.

I would like to use a copyleft license so that should companies in the healthcare industry or other industries decide to use and redistribute this software, they will not be able to make proprietary others' contributions to the software and deny others from receiving the benefit of additional contributions.

I am inclined to use the GNU AGPLv3 license because people who interact with a changed version of this software over a network are allowed access to a copy of the software.

I would like to open this discussion to others.

More reading:

• Why the GNU Affero GPL | GNU Project
• GNU Affero General Public License v3.0 | Choose a License
• No License | Choose a License

Right now, HealthRecord supports y-webrtc and y-indexeddb Yjs connection and database providers for syncing data. Syncing works with the local IndexedDB fine, but only works between browser tabs right now through WebRTC due to an empty list of public signaling servers in the initialization of the WebrtcProvider. The public signaling server set as default in y-webrtc is not functional (yjs/y-webrtc#43) and to save browser resources attempting to connect to an unavailable WebSocket server for signaling, an empty list was set in this project.

I have created a new repo (y-webrtc-signaler) that includes a signaling server built for y-webrtc signaling that is easily deployable to cloud hosting providers including Heroku, Render, and Google Cloud.

A user should be able to choose which signaling server they would like to connect to and have their preference saved in their record's configuration settings when they download their record. A toggle in Settings could be created to enable WebRTC syncing with a text box that is revealed to allow a custom signaling server URL to be set. Optionally, if this project can sustain its own signaling server, provide another toggle that will enable the use of the project maintained signaling server.