Subsequent versions of RadarOpus are released following a strict procedure, installed to offer all RadarOpus users a smooth and easy transition to the next stable version. This description will offer you some insight in the careful steps we take to achieve this.
The alpha- and beta-testing is done by the programmers, our internal support and our own internal Test Team until we have a stable version including all desired features
The final beta test version is sent as a Field Test to all dealers, to Zeus Soft's worldwide Support Team and to selected users worldwide. You too are welcome to join the Zeus Soft Test Team and install the so called Link Release (install the test version by clicking a link on our website). The Field Test allows us test the next version in a multitude of combinations of Operating Systems, languages, firewalls, etc.
The next version is released, first as an intermittent Live Update. RadarOpus users who are connected to the internet when they start RadarOpus, will be invited to install the update. At first, the Live Update will be activated for a short period only. This allows our support team to collect additional feedback from the first hundreds of users and to immediately assist them in case that would be needed
When the Live Update is running smoothly and support is not needed any more, that version is released as a Live Update 24/7: anyone connected to the internet when starting RadarOpus will be invited to install the update, any time
As a last step, the update is released on DVD, USB, as an ISO Image and as a download from our website. All options may not apply to each update
Zeus Soft is looking for some more users to test RadarOpus at various stages.
If you are an enthusiastic, active RadarOpus user, you can be part of our Test Team.
You will not get a test version where nothing is functional, as we do the alpha and beta testing internally. You will get the so called final beta version or the Field test, which should allow you to continue working with the new RadarOpus as usual.
These are some requirements to be part of the Test Team:
Actively use the last official version of RadarOpus
Be able to report in either English, French or German
Send us a weekly report by Monday morning at the latest
Advantages of being part of the Test Team:
You will be able to use the future developments before all other users
Your feedback will be considered while finalizing the next version, we consider you part of our development team
You will get free support up to the third level in case that would be needed (1 = dealer; 2 = support team; 3 = programmers)
Whenever you want to resume working with your previous version, we will help you for free (in case that would be needed)
How to be(come) a Test Team member
If you want to become a Test Team member: Contact your dealer so he is aware of your intentions and can be your first contact in case of any problems
Make sure that all your personal data are backed up before installing a test version
A few requests about the reports you will send:
Be precise in your reporting, possibly include print screens
Mention your Operating System (e.g.: macOS Sierra, Windows 7 Pro-32 bit)
Tests should focus on the new and resolved issues of the version (not be a wish list for the future). The relevant issues can be found in the What's New information
Do not only mention (even minor) problems but also major things that work, so we know what you have tested
Mail your report to which will automatically forward it to René Otter (NL) and Carlo Rezzani (IT), our Test Coordinators
The Zeus Soft Team and our thousands of RadarOpus users thank you most sincerely for your efforts!
GDPR and HIPAA modules implemented in RadarOpus from version 2.2
GDPR/HIPAA compliant data structure
Patient data is stored in a database and not in single text files
Data is more secure when stored in a database (in binary code)
Patient data but also the analysis (repertory symptoms) are encrypted
Any analysis, even a single analysis in XML-format is encrypted
Personal administrative data is separate from clinical data
Data identifying the patient is stored in a separate database table
Encryption of all media files (PDF, video, images, sounds, etc.)
All media saved in RadarOpus are encrypted to protect privacy of the patient. They can only be retrieved after opening RadarOpus.
GDPR/HIPAA compliant traceability
Every time the homeopath creates data in RadarOpus, the time and date is automatically recorded in the database.
GDPR/HIPAA compliant discriminatory data
Saving discriminatory data is not allowed
RadarOpus does not allow to save discriminatory data (e.g.: race and religion)
GDPR/HIPAA compliant password policy
Password protected access to all data
All patient data entered with RadarOpus can only be accessed after logging in with your password
New password each 3 months
New password can be set by the user 24/7.
Strong password is compulsory
Password must be at least 8 characters, alphanumeric and contain special characters
Password is required after 1 hour of software inactivity
Automatic setting in RadarOpus
GDPR/HIPAA data handling requests
Print the patient file
At the request of the patient, RadarOpus allows to print all patient data (administrative data, consultation texts, prescriptions, evaluations, medical tests, etc). This print function does not include personal notes of the homeopath, which can be printed separately.
Delete a patient file
The option to delete all information of a patient is available in countries where this is required.
GDPR/HIPAA compliant backup
Backup suggets to use an external hard drive.
Backup is always automatically encrypted.
Useful additional information for professionals storing sensitive health data (applicable to RadarOpus and other programs)
Use a password to protect your PC/Mac and change it every 3 months.
The PC/Mac must be protected by Antivirus and Antimalware.
Encrypt your data whenever possible (e.g. save back-ups and then encrypt the file or password protect it).
Never keep all back-ups in the same place. Have a copy of your back-up in a separate safe place in case of fire, theft or natural calamities (a password protected hard drive in a locked cabinet) or use a GDPR/HIPAA compliant cloud.
Run through a report of how to handle data that is lost or stolen and keep a written record of it.
Ensure you know how to successfully delete data of a patient if required (but check whether the request of the patient complies with national laws regarding the time during which you need to keep patient records).
Ensure you have written consent from each patient to record and keep their personal data.
If you use patient data for research purposes, ensure your patient has given you written permission to use it.
If data is lost or violated in any way, immediately contact local authorities.