Differences

This shows you the differences between two versions of the page.

--- decimal3d:instructions_for_use:instructions_for_use [2019/09/03 21:04] – [Product Features] kmobile
+++ decimal3d:instructions_for_use:instructions_for_use [2019/09/03 21:40] – [Release Notes] kmobile
@@ Line 43: / Line 43: @@
 ==== System Availability and Data Integrity ====
-As with any cloud based application there is always concern with system availability and uptime. Astroid makes use of caching at various system levels to improve performance and mitigate some of these concerns, however, this can never provide 100% assurance and reliability. Since customer has unique needs, specific business agreements will be entered into with each customer as appropriate to detail the reliability guarantees and assurances. Data integrity is generally a less variable concern, as Astroid's cloud storage providers strong guarantee the highest commercially available data redundancy and integrity limits (approaching 99.999999% per year). Data is transferred to and from the cloud services using secure transfer protocols, that guarantee error-free of transfer using common industry standard techniques (for more details please see the [[https://developers.thinknode.com/guides/ipc|Thinknode IPC article]]). While Astroid has been designed with security in mind, users should understand that it is still their responsibility to ensure the system is accessed and controlled properly. Following international standards for IT risk management, such as IEC 80001-1, is therefore highly recommended.
+FIXME - We need to discuss this
-Since data integrity is such a critical feature for application such as this, the Astroid Planning App automatically saves both the state of the application and the working record data on a timer (triggering every minute or less) as well as on exit of any create or edit event in the application. Additionally, each "save" event creates a new entry in the record's history log in Thinknode, which provides a log file for editing of all records and a ensures that patient records are saved securely on an independent medium so they are not lost in the event of a local system failure or crash.
 ==== Coordinates and Units of Measure ====
@@ Line 51: / Line 49: @@
 FIXME- should we delete this for the first go round?
-==== Data Validation and Limits ====
+==== Data Validation ====
-Users are responsible for inputting a lot of data into the Astroid Planning App to develop clinical treatment plans. In the course of entering such data, there are opportunities for users to enter incorrect information. Although users are responsible for checking for such errors before clinical treatment, Astroid does provide some assistance in ensuring data limitations are met by a plan. Machine energy (range) limits, gantry angles, patient support (couch) angles, snout extensions, as well as shifter and aperture sizes and availability are all explicitly limited to user configured levels within the Astroid Planning App controls. Additionally, certain incompatible settings, such as zero thickness rinds and overlapping structure min/max constraints are also explicitly prevented within the Astroid user interface. Despite these many data validation checks, some entries, such as min/max spot MU's are not validated within the Astroid user interface and users should include appropriate checks and warnings in their custom treatment plan reports to ensure such concerns are brought to the attention of all responsible parties before patient treatment begins. Such warnings should include a statement such as this (or similar): "CAUTION: SOME DATA ELEMENTS USED WERE OUTSIDE NORMAL RANGE".
+Users are responsible for confirming machine data input into decimal's p.d APP. This data will the machine data that is used in decimal3D. Users should complete a site survey found at [[https://dotdecimal.com/site-survey/]] if they do not have an account with .decimal. .decimal staff will aid users in setting up machines.
 ==== Data Displays and Interpretation ====
@@ Line 61: / Line 58: @@
 ==== Unauthorized Use ====
-The Astroid Planning Application will contain sensitive patient information that is protected under various governmental regulations, therefore users must ensure they adequately follow all appropriate and applicable rules regarding how, where, and when their staff may access the application and its data. In order to facilitate proper usage and protections, Astroid has a robust user permissioning scheme, as well as industry standard options for configuring password requirements, as explained at the [[https://developers.thinknode.com/services/ams/settings|Thinknode Account Management Settings page]]. Since all application and data access requires user login credentials, it is important that site administrators implement a strong password policy and that all users understand the importance of maintaining secrecy of their password (i.e. passwords should never be shared among more than one user). It is these user credentials that protect the system and its data from unauthorized access and replication.
+The decimal3D will contain sensitive patient information that is protected under various governmental regulations, therefore users must ensure they adequately follow all appropriate and applicable rules regarding how, where, and when their staff may access the application and its data. Since all application and data access requires user login credentials, it is important that site administrators implement a strong password policy and that all users understand the importance of maintaining secrecy of their password (i.e. passwords should never be shared among more than one user). It is these user credentials that protect the system and its data from unauthorized access and replication.
 ==== Access Control ====
-Astroid (Thinknode) administrators have the ability to manage user access, passwords, and "lock" data records to prevent unwanted and unintended modification. Several features have specific access rights that can be configured, including the ability to lock data records, unlock data records, and delete data. By configuring these options, administrators can lock critical data records, such as beam models, equipment information, and other machine/site level data, such that only expressly authorized users can edit these fields. All critical site records such as these should be kept "locked" at all times, and should be unlocked by only be authorized users when expliciting desiring to edit said records (and locking them again after modification is complete). In addition to the practice of locking site data records, users are expected to establish a review process whereby a minimum of two authorized individuals will review all proposed site data changes (including beam models and equipment data) prior to updating the records in Thinknode (please note that at this time, all such records are downloaded, reviewed, and updated through the Thinknode Desktop Client, which is available for download [[https://desktop.thinknode.com/|here]]).
+FIXME - this can be deleted?
-As Astroid is a cloud based application the site administrator will be responsible for the installation of Astroid on to the appropriate workstations. Each user should have an individual log in and password to access the planning app that prevents unauthorized access. Best practices should be followed.
+==== Known Limitations ====
-For further information on access management and permission settings please refer to [[https://developers.thinknode.com/services/iam|Thinknode IAM Services]]. The Thinknode services provide two important considerations regarding your clinical data, first, the permission schemes and access control, provide effective control against unintentional and malicious data manipulation and the inherent storage redundancy of the cloud resources provides exception protection against data loss.
+For a list of known system issues and limitations please refer to the following.
-==== Known Limitations ====
-For a list of known system issues and limitations please refer to the following articles for the Planning App and Dosimetry App, respectively.
-[[planning:userguide:userguide#known_application_limitations|Planning App Known Limitations]]
-[[dosimetry:userguide:userguide#known_application_limitations|Dosimetry App Known Limitations]]
@@ Line 83: / Line 75: @@
 === Release Notes ===
-For the release notes for each version of the Planning Application, please refer to the [[https://dotdecimal.freshdesk.com/support/discussions/forums/9000203024|.decimal Freshdesk Forum]].
+For the release notes for each version of the Planning Application, please refer to the FIXME we need to come up with where this is.