SIRS | Network and Computer Security Project
kandi X-RAY | SIRS Summary
kandi X-RAY | SIRS Summary
SIRS is a JavaScript library. SIRS has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
Health care institutions gather and store sensitive information from patients with the goal of providing the best care possible. The medical history of a patient is essential to allow correct diagnostic and help the clinical staff act in the shortest time possible. This information is highly sensitive and must be kept private for the responsible staff only. At the same time, the medical records should be accessible by any health care institution to ensure that a patient can be assisted anywhere. To guarantee data availability, health care institutions in the future might rely on data repositories accessible through the Internet. This poses a threat, since patient data can be accessed by unauthorized personnel. It is also extremely difficult to manage access to data using standard access control mechanisms due to the vast amounts of user, groups and patients and the constant adjustment in privileges that must be done to maintain patient’s confidentiality. In this topic we define a cloud-based system to store medical records. The records are available for a wide range of users, so the system provides a web interface to manage access privileges to the records. We use Atribute Based Access Control (ABAC) and the standard architecture XACML was implemented using AuthzForce. More information can be found in the report under /docs.
Health care institutions gather and store sensitive information from patients with the goal of providing the best care possible. The medical history of a patient is essential to allow correct diagnostic and help the clinical staff act in the shortest time possible. This information is highly sensitive and must be kept private for the responsible staff only. At the same time, the medical records should be accessible by any health care institution to ensure that a patient can be assisted anywhere. To guarantee data availability, health care institutions in the future might rely on data repositories accessible through the Internet. This poses a threat, since patient data can be accessed by unauthorized personnel. It is also extremely difficult to manage access to data using standard access control mechanisms due to the vast amounts of user, groups and patients and the constant adjustment in privileges that must be done to maintain patient’s confidentiality. In this topic we define a cloud-based system to store medical records. The records are available for a wide range of users, so the system provides a web interface to manage access privileges to the records. We use Atribute Based Access Control (ABAC) and the standard architecture XACML was implemented using AuthzForce. More information can be found in the report under /docs.
Support
Quality
Security
License
Reuse
Support
SIRS has a low active ecosystem.
It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 12 months.
There are 0 open issues and 20 have been closed. On average issues are closed in 14 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of SIRS is final_project
Quality
SIRS has no bugs reported.
Security
SIRS has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
SIRS is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
SIRS releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of SIRS
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of SIRS
SIRS Key Features
No Key Features are available at this moment for SIRS.
SIRS Examples and Code Snippets
No Code Snippets are available at this moment for SIRS.
Community Discussions
No Community Discussions are available at this moment for SIRS.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install SIRS
By default the port 8080 accepts HTTP requests and redirects them to port 8443 as HTTPS requests (This only work with GET). You can change the ports in /medical-records/server/src/main/resources/application.properties changing the. properties server.http.port and server.port respectively.
By default the port 8080 accepts HTTP requests and redirects them to port 8443 as HTTPS requests (This only work with GET)
You can change the ports in /medical-records/server/src/main/resources/application.properties changing the
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/src/main/resources/.key to mysql config folder (usually /etc/mysql/, where config file is located). Comment lines 2, 8, 9, 10, 11, 12 of medical-records/server/src/main/resources/dbconfig-linux, and check if the file paths for the keys are correct. Copy dbconfig-linux file contents to mysql config file (usually /etc/mysql/my.cnf).
Rename the file /medical-records/server/src/main/resources/database.properties.example to database.properties and fill it with your database credentials. According to your OS follow the next instructions to setup the encryption of MariaDB.
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/src/main/resources/.key to mysql config folder (usually /etc/mysql/, where config file is located)
Comment lines 2, 8, 9, 10, 11, 12 of medical-records/server/src/main/resources/dbconfig-linux, and check if the file paths for the keys are correct.
Copy dbconfig-linux file contents to mysql config file (usually /etc/mysql/my.cnf)
Restart mariadb service
Access mariadb and insert the following statement:
Uncomment the lines previously commented (2, 8, 9, 10, 11, 12)
Remove the .key file from the config folder and it's good to go
Everytime the mariadb service starts, the key must be in the the config folder
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/server/src/main/resources/.key to mysql config folder (usually /usr/local/var/mysql/, where config file is located)
Comment lines 2, 8, 9, 10, 11, 12 of medical-records/src/main/resources/dbconfig-macos, and check if the file paths for the keys are correct.
Copy dbconfig-macos file contents to mysql config file (usually /usr/local/etc/my.cnf)
Restart mariadb service
Access mariadb and insert the following statement:
Uncomment the lines previously commented (2, 8, 9, 10, 11, 12)
Remove the .key file from the config folder and it's good to go
Everytime the mariadb service starts, the key must be in the the config folder
Copy the files /medical-records/server/src/main/resources/keys.enc and medical-records/server/src/main/resources/.key to mysql config folder (usually C:\Program Files\MariaDB X.X\data\, where config file is located)
Copy dbconfig-windows file contents to mysql config file (usually C:\Program Files\MariaDB X.X\data\my.ini)
Restart mariadb service
Everytime the mariadb service starts, the key must be in the the config folder
By default the port 8080 accepts HTTP requests and redirects them to port 8443 as HTTPS requests (This only work with GET)
You can change the ports in /medical-records/server/src/main/resources/application.properties changing the
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/src/main/resources/.key to mysql config folder (usually /etc/mysql/, where config file is located). Comment lines 2, 8, 9, 10, 11, 12 of medical-records/server/src/main/resources/dbconfig-linux, and check if the file paths for the keys are correct. Copy dbconfig-linux file contents to mysql config file (usually /etc/mysql/my.cnf).
Rename the file /medical-records/server/src/main/resources/database.properties.example to database.properties and fill it with your database credentials. According to your OS follow the next instructions to setup the encryption of MariaDB.
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/src/main/resources/.key to mysql config folder (usually /etc/mysql/, where config file is located)
Comment lines 2, 8, 9, 10, 11, 12 of medical-records/server/src/main/resources/dbconfig-linux, and check if the file paths for the keys are correct.
Copy dbconfig-linux file contents to mysql config file (usually /etc/mysql/my.cnf)
Restart mariadb service
Access mariadb and insert the following statement:
Uncomment the lines previously commented (2, 8, 9, 10, 11, 12)
Remove the .key file from the config folder and it's good to go
Everytime the mariadb service starts, the key must be in the the config folder
Copy the files medical-records/server/src/main/resources/keys.enc and medical-records/server/src/main/resources/.key to mysql config folder (usually /usr/local/var/mysql/, where config file is located)
Comment lines 2, 8, 9, 10, 11, 12 of medical-records/src/main/resources/dbconfig-macos, and check if the file paths for the keys are correct.
Copy dbconfig-macos file contents to mysql config file (usually /usr/local/etc/my.cnf)
Restart mariadb service
Access mariadb and insert the following statement:
Uncomment the lines previously commented (2, 8, 9, 10, 11, 12)
Remove the .key file from the config folder and it's good to go
Everytime the mariadb service starts, the key must be in the the config folder
Copy the files /medical-records/server/src/main/resources/keys.enc and medical-records/server/src/main/resources/.key to mysql config folder (usually C:\Program Files\MariaDB X.X\data\, where config file is located)
Copy dbconfig-windows file contents to mysql config file (usually C:\Program Files\MariaDB X.X\data\my.ini)
Restart mariadb service
Everytime the mariadb service starts, the key must be in the the config folder
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page