Successfully Track Sexual Assault Kits Within The System

Successfully Track Sexual Assault Kits Within The System • • • Unique Identifier Developed to Allow Tracking of Kits in the System Survivor Login Mechanism in Place Survivor Able to Track Their Kit [Validated in Pilot] Final Standardization of Sexual Assault Kit Meet Business and Technical Requirements • Administered Washington Administrative Code Process for Standardization of WSAK (public hearing pending) [Anticipated date of adoption - May 29, 2018] • Communication with SAK Vendor in Place for Short Term and Long Term Solutions [Tri-Tech agreement in place] • Vetted Business Requirements with Stakeholders and Advisory Committee [Completed] • Concluded System Development [February 2018] • Completed User Acceptance Testing [February 2018] User Communication Mechanism Established Assess Performance and Processes • Feedback Mechanisms Within System in Place [Validated in Pilot] • Created SAK Tracking System Support Email [Completed] • Newsletters and Project Website in Place [Completed] • Logistics Communication Approach Established [Validated in Pilot] • Successfully Completed Pilot [March 2018] • Analyzed MS Azure Government Cloud Metrics [STACSDNA] • Verified Reporting Metrics within System [STACS DNA and SAK Team] • Conducted Performance Testing To Validate and Verify Quality and Reliability of Processes [STACS DNA and SAK Tracking Team] Sustainable Training Curriculum and Approach in Place Validate Data and Data Flow • Statewide Implementation and Training Schedule [Completed] • Identified Training Approach – Web-based, Videos, User Manuals, In-person [Validated in Pilot] • Curriculum Developed for all Portal Types [Validated in Pilot] • Tested Entire System Through Pilot [February – March 2018] • Validated Workflow Within System [Completed within Pilot] • Conducted Use Cases Throughout The System [Validated in Pilot] SAK Tracking Business Process are Operational Functionality and Security of Deployment in Place • Utilized Advisory Committee to Ensure System Processes Meet Business Need [Validated in Pilot] • Verified Business Process are Met Through Pilot and User Acceptance Testing [Validated in Pilot] • Simplistic System Design Allowing Easy Integration Within Current Processes [Validated in Pilot] • Administered Office of Cyber Security Review [Completed April 10, 2018] • System Implemented in MS Azure Government Cloud [Implemented – STACS DNA] • Office of Chief Information Office Security Requirements Met [Completed April 10, 2018] Vendor Feedback Loop Process to Identify and Resolve System Defects in Place • Continuous Regression Testing in Place [SAK Tracking Team] • Feedback Mechanisms Within System [Validated in Pilot] • WSP Support [in place] • STACS DNA Support [in place and validated in Pilot] • Issues Addressed with Vendor Support Mechanisms [Ongoing - Validated in Pilot] • Approach Established – Identify, Verify, Test, Implement to Production [Validated in Pilot] DRAFT

Outstanding Items Washington Administrative Code • Currently pending hearing – April 24, 2018 • If no objections, submit CR-103 which must be filed for 31 days before rule becomes effective • Anticipated Date of Adoption – May 29, 2018 • If revision is necessary, the process would entail the following: • Revised CR-102 must be filed for 20 days prior to hearing date • Hold hearing, if no objections, file CR-103 • CR-103 must be filed for 31 days before rule becomes effective Standardized Sexual Assault Kit • Communication with SAK vendor in-place for short term and long term solutions • Agreement for: • Short term – Medical Facility staff receive envelope with survivor login credentials card and adhesive barcode label (Current) • Long term – Barcode affixed to box and survivor login credentials card inside kit during manufacturing, once majority of users are trained to use the system (Beginning September/October 2018) DRAFT