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:20] – [Data Validation and Limits] 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 ====