- notify the FDA for any bugs that affect a patient - document every software decision, who made it, and when it was made, in the DMR - etc
-
-
Replying to @EmilyGorcenski
Now, here is the complete regulatory process for a voting machine:
2 replies 147 retweets 178 likes -
Replying to @EmilyGorcenski
That's it. Nothing. No mandatory code reviews. No cybersecurity analysis. No versioning reqs. Absolutely nothing.
8 replies 104 retweets 235 likes -
Replying to @EmilyGorcenski
not criticizing, but https://www.eac.gov/testing_and_certification/ … is something that voting system companies go through. It's expensive and
2 replies 8 retweets 13 likes -
Replying to @Slestac @EmilyGorcenski
requires adherence to VVSG standards, which include code history, reviews, style guides, etc
1 reply 4 retweets 9 likes -
Replying to @Slestac @EmilyGorcenski
and that's just at the federal level. Some states have additional certification requirements that manufacturers must meet.
2 replies 3 retweets 10 likes -
-
Replying to @EmilyGorcenski
I'm wrapping up a job at ES&S, and we submit all systems through this process. Don't know if statutorily required
2 replies 1 retweet 10 likes -
Replying to @Slestac
Digging into the stuff, it appears that it is voluntary. It's good that it exists as a starting point. Needs to be codified.
1 reply 3 retweets 20 likes -
Replying to @EmilyGorcenski
I agree with you on that. I'm really not the expert you need though.
1 reply 1 retweet 4 likes
I am incredibly grateful you brought this to my attention, as my searches gave me nothing. <3
-
-
Replying to @EmilyGorcenski
glad to help. I love reading your tweet storms and I'm glad I can contribute.
0 replies 0 retweets 12 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.