Why are you making this RSA-911 Edit Checker available?
Many vocational rehabilitation state agencies and VR industry partners have indicated that a tool like this would be very useful for cross-checking and validating data in RSA-911 reports. Based on that feedback, our group of industry collaborators is launching this project.
Who will the tool be available to? And how do agencies get it?
Any state agency can use this open-source tool free of charge. It will made available for download and the source code will also be made available on GitHub.com.
How much does it cost?
This is an open-source program with zero cost.
Is the RSA-911 Edit Checker Accessible?
Yes, with the v188.8.131.52 release, the RSA-911 Edit Checker is now fully accessible as validated with Accessibility Tools testing as well as passing Microsoft’s Accessibility Insights.
What rules and data validation items does the tool include?
The tool incorporates the current rules and data validation items, described in the Rehabilitation Services Administration (RSA) November 2017 document titled RSA-911 Edit Specification V5). It will also include optional rules sets developed by collaborators and VR state agencies.
What open-source language will you use? Will the source code be available?
The tool is an open-source .NET application, written in C#, that runs a series of rules. Rules will be written in T-SQL. The RSA-911 Edit Checker installs Microsoft SQL Express 2012 to run the T-SQL. The application is available for download and the source code is also available.
Will it be possible to contribute to the code/scripts, or customize it to fit our state agency needs?
Yes. Individuals will be able to add their own rules by adding rule files (written in T-SQL). Individuals can also contribute to the .NET application open-source project. We welcome your participation in this ongoing effort whether it’s raising issues, commenting in forums, suggesting code changes or rule additions.
The best way to participate is establish a GitHub.com account and then contact RSA-911 support with your GitHub user name. We will then send you an invite to join the community! Once you’re a part of the GitHub community you’ll be able to suggest changes and improvements to the code, call out issues, and participate in valuable discussions with other professionals across the industry.
Who decides what gets added and what is cut/changed? Who compiles if it is code that requires compiling to run?
This open-source project will have a moderator. The moderator will decide which proposed changes to accept. Learn how to suggest changes.
Do you plan to support this effort through your support desk or delegate it to a user group? If the latter, who is likely to head that group?
To start, there will be a community moderator. This is an open-source project, meaning support will need to come from the community.
How secure is the RSA-911 Edit Checker with respect to the data?
The RSA 911 Edit Checker tool runs locally on your machine and your data is never sent anywhere else. We have also incorporated the following security protections within the tool to help protect PII while on your desktop.
- RSA-911 Extract File – The RSA-911 Edit Checker does use the RSA-911 extract file to run the rules on. It will read the extract file into a SQL Express database, but uses a SQL temporary database table to do so. So, once the RSA-911 Edit Checker is closed, there is no RSA-911 extract information left in the database.
- When the RSA-911 Edit Checker does complete running its rule checks, there is an option to generate an error report. This error report is generated into an Excel file. If that Excel file is closed, without saving, there is no error report information left on the workstation. Only in the case of saving the error report is there any information saved on the workstation.
- For support, there is an option to export the RSA-911 extract file in the case it can be used to troubleshoot a rule check. When using this export option, the extract is exported without PII. Specifically, Element5, Element6 and Element8 are cleared. This cleansed, secured export file is opened in Excel and, if not saved, then there is no extract file information left on the workstation. Only in the case of saving the cleansed, secured export file is any information saved on the workstation but it is without PII.