· web viewsolution vendor must provide solution administrator and user manuals in microsoft word...

77
Attachment A – Draft CMS Requirements This attachment contains draft functional and technical requirements for an Integrated Court Management System (CMS) desired by the Orleans Parish Criminal District Court and the Orleans Parish Clerk of Criminal District Court. Vendors are not required to comment on each requirement at this stage of the RFI process. However, CDC welcomes feedback and suggestions from vendors including but not limited to suggested revisions to make the requirements less restrictive without sacrificing the CDC’s ability to meet the objectives outlined in the RFI document. Req. # Description Comments 1 Solution provider’s court case management solution must be installed and in production use in at least five (5) other United States locations. Please list the three (3) largest clients with contact information in the Comments column. 2 Solution must run on the Microsoft Windows Server 2016 or later operating system. 3 Solution must use Microsoft SQL Server 2016 or later version. 4 Solution SQL Server database(s) must provide table views that Microsoft Power BI and SQL Server Reporting Services (SSRS) may access to produce reports and perform analytics. 5 Solution must provide a separate reporting services server. 6 Solution must provide a data dictionary that fully describes database table structures and attributes. Each database table and table column must have a clear understandable CDC CMS RFI Page 1 of 77 July 15, 2022

Upload: others

Post on 25-May-2021

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

This attachment contains draft functional and technical requirements for an Integrated Court Management System (CMS) desired by the Orleans Parish Criminal District Court and the Orleans Parish Clerk of Criminal District Court. Vendors are not required to comment on each requirement at this stage of the RFI process. However, CDC welcomes feedback and suggestions from vendors including but not limited to suggested revisions to make the requirements less restrictive without sacrificing the CDC’s ability to meet the objectives outlined in the RFI document.

Req. # Description Comments1 Solution provider’s court case management solution must be installed

and in production use in at least five (5) other United States locations. Please list the three (3) largest clients with contact information in the Comments column.

2 Solution must run on the Microsoft Windows Server 2016 or later operating system.

3 Solution must use Microsoft SQL Server 2016 or later version.4 Solution SQL Server database(s) must provide table views that

Microsoft Power BI and SQL Server Reporting Services (SSRS) may access to produce reports and perform analytics.

5 Solution must provide a separate reporting services server.6 Solution must provide a data dictionary that fully describes database

table structures and attributes. Each database table and table column must have a clear understandable definition.

7 Solution must provide a comprehensive, clear, and understandable database Entity Relationship Diagram (ERD).

8 Solution must have the ability to operate in a virtual server environment for high-availability, increased reliability, and redundancy.

9 Solution must provide the ability to support clustered servers for failover and load balancing.

10 Solution must provide the ability to be operational 24/7/365 except for planned outages.

11 Solution must provide no less than 99.99% of scheduled uptime in any calendar month.

12 Solution must provide the ability to provide backup and recovery operations to another site.

CDC CMS RFI Page 1 of 48 September 20, 2023

Page 2:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments13 Solution must provide response times not to exceed three (3) seconds

95% of the time for any transaction over a period of one (1) hour as determined by court. Solution provider must provide a response in the Comments column if unable to meet the specified response time requirement.

14 Solution must be capable of supporting 150+ concurrent users.15 Solution must have the ability to scale up, i.e., increase the number of

concurrent users, servers and data stores.16 Solution must be intuitive and user-friendly.17 Solution must provide easy to use screen display formats that are

consistent across the application.18 Solution must provide the ability for a user to toggle between

windows.19 Solution must provide the ability to view multiple windows at the

same time (e.g., side by side or cascade).20 Solution must provide the ability for a user to minimize or expand any

window.21 Solution must provide the ability to support touch-screen

functionality.22 Solution must provide the ability to accept input from:

3D barcode reader (e.g., driver's license, registration) Card swipe device Fingerprint reader Function keys (one touch keys) Point-and-click devices (i.e., mouse, trackball, touch pad)

23 Solution must be browser-based or be web accessible, preferably with a HTML5-based user interface (UI).

24 Solution must provide a consistent tabbed-based user interface (UI).25 Solution must provide a navigation bar to facilitate user navigation.26 Solution must be built fully on open standards.27 Solution must have the ability to ensure that technical aspects of

solution is service-oriented to the business need, e.g., n-tier, service-oriented architecture (SOA).

28 Solution must utilize W3C standards for data presentation and

CDC CMS RFI Page 2 of 48 September 20, 2023

Page 3:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsdocument rendering.

29 Solution must adhere to Open Web Application Security Project (OWASP) standards.

30 Solution must support user authentication and authorization, per NIST SP 800-63 suite (SP 800-63-3, SP 800-63A, SP 800-63B, SP 800-63C).

31 Solution must comply with FIPS 140-2 for encryption.32 Solution must be Americans with Disabilities Act (ADA) Section 508-

compliant.33 Solution must conform to GJXDM, NIEM, and NIST standards and

principles.34 Solution system interfaces must be NIEM compliant for data sharing

and integration with other systems.35 Solution must adhere to all local, state, and federal laws.36 Solution must provide the ability to comply with Criminal Justice

Information Services (CJIS) Security Policy security requirements37 Solution must have the ability to encrypt data stored in the database.38 Solution must comply with City of New Orleans IT and court technical

standards and operations, networking, and security policies.39 Solution must support Internet Explorer 11, Edge, Chrome, Firefox,

and Safari.40 Solution must provide system access via desktops, laptops and mobile

devices such as tablets and smartphones.41 Solution does not require the installation of client software on

desktops, laptops and mobile devices such as tablets and smartphones.

42 Solution has the ability to provide the technical components and platform to allow for application mobility, e.g., Windows, iOS or Android.

43 Solution must be a configurable commercial off-the-shelf court case management solution that allows authorized court staff to easily configure screens (user interface), workflow, business rules, and court processes without having to rely on or pay the solution vendor.

44 Solution must provide the ability for each user and/or user functional group (Magistrate, Clerk’s Office, court, and/or other administrator

CDC CMS RFI Page 3 of 48 September 20, 2023

Page 4:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsdefined) to have a unique view of the case management solution while still providing solution administrators a global view.

45 Solution must provide the ability for the court to define all screens, configure screen attributes, define required fields, and define validation warning and error messages.

46 Solution must provide the ability to rename and/or remove fields to meet local court requirements.

47 Solution must provide configurable screens based on workflows, roles and security permissions.

48 Solution must provide the ability for the system administrator to format screens based on roles and responsibilities for a user, a group of users, or enterprise-wide.

49 Solution must provide the ability to revert a custom formatted screen back to the original default settings.

50 Solution must provide the ability to format data fields by font size, color, position on the screen, descriptive text (label), and tab order.

51 Solution must provide the ability to make data fields invisible, un-editable, or required.

52 Solution must provide the ability to add an unlimited number of court-defined fields.

53 Solution must be easily configured after implementation to permit court staff to configure new local, state, and federal legislation and policy changes without solution provider assistance.

54 Solution must have the ability to maintain configurations and customizations during and after software version updates.

55 Solution must provide workflow engine and workflow management functionality.

56 Solution must be able to create workflows that mimic the court’s business process and automate the tasks that need to occur in each business process.

57 Solution must provide the ability for the court to customize workflows for specific job duties such as case initiation, minute entry, disposition entry, document generation, etc.

58 Solution must have the ability to process incoming electronically

CDC CMS RFI Page 4 of 48 September 20, 2023

Page 5:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentstransmitted data from external systems and initiate the proper workflow based on the data received.

59 Solution must provide the ability to allow letters, forms, and other documents to be incorporated into a workflow.

60 Solution must provide configurable common calendar date picker functionality. The component will be used for all date input fields, and should allow for both date selection and the ability to type in the date with date validation.

61 Solution must store dates in MM/DD/YYYY format.62 Solution must provide a default value for entering current date, e.g.,

“D” indicates default current date.63 Solution must provide the ability to automatically calculate the day of

week for any entered date.64 Solution must store times in military format including hours, minutes,

and seconds (HHMMSS).65 Solution must store timestamps in date, hour, minute, seconds, and

fractions of a second format (YYYY-MM-DD-HH-MM-SS-NNNNNN)66 Solution must have the ability to support multiple environments to

include Development, Testing, Staging, Training, and Production.67 Solution must provide keyboard shortcuts and drop-down menus to

enter/search all solution data categories.68 Solution’s use of function keys, shortcuts, and other functionalities

must be consistent throughout solution.69 Solution must provide the ability to complete all user tasks using only

a keyboard.70 Solution must permit the addition, modification, deletion, querying,

and printing of solution data categories based on user permissions.71 Solution must provide the ability to index data and documents for

quick and easy retrieval based on court-defined search criteria.72 Solution must provide search/query/print capabilities on any database

data field, narrative/note field, and scanned or attached documents.73 Solution must provide the ability to query/print any operational

database data field.74 Solution must provide the ability to search any field using a wildcard

CDC CMS RFI Page 5 of 48 September 20, 2023

Page 6:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentscharacter.

75 Solution must allow the ascending or descending ordering of entries in a query list by clicking on the header column.

76 Solution must provide query drill down capability on all search results, (e.g., hyperlink, icon).

77 Solution must provide the ability to search based on standard indexes and ad hoc values.

78 Solution must provide the ability to perform a search and then add or refine the list with additional search criteria.

79 Solution must provide the ability to retain search parameters to use with subsequent searches.

80 Solution must provide the ability to search case parties by a variety of criteria such as sound like searching (Soundex), partial name, exact spelling, synonyms, diminutive first names and other demographic information such as social security number, driver’s license number, date of birth, and State ID (SID) to eliminate duplicate results.

81 Solution must provide the ability to accommodate: Hyphenated names Names with apostrophes Multiple word names

82 Solution must provide the ability to search all data using the following criteria: Equal To (exact match) Partial Information Not Equal To Less Than Greater Than Between (date/time, day of week, date ranges, etc.)

83 Solution must provide the ability to narrow down searches (search within a search).

84 Solution must provide the ability to limit the number of records viewed at one time.

85 Solution must provide the ability to restrict searches that result in large volumes of data by:

CDC CMS RFI Page 6 of 48 September 20, 2023

Page 7:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Providing a warning of the number of records found Requesting the users to prompt the system to continue the

search Requesting the users to prompt the solution to cancel the search

86 Solution must provide the ability to enter data in non-case sensitive format.

87 Solution must provide the ability for search criteria to be non-case sensitive.

88 Solution must provide the ability to expand or refine a search with additional criteria without have to start the search over.

89 Solution must allow multiple users to search and view the same information at the same time without negatively affecting performance.

90 Solution must provide the ability to print search/query results on-demand.

91 Solution must provide the ability to export search/query results into multiple formats such as PDF, CSV, Word, Excel, XML, etc.

92 Solution must warn a user that they are about to perform an action (add, modify, delete) and ask if they want to proceed.

93 Solution must not allow the manual entry or modification of data until explicitly instructed to do so.

94 Solution must allow a user to cancel out of a transaction and/or exit any screen without saving changes.

95 Solution must provide the ability to set an auto-save interval in minutes.

96 Solution must provide a business rules engine that enables court staff to configure an unlimited number of business rules through a graphical interface.

97 Solution must provide the ability to create business rules to aid in the processing of information, providing alerts, and/or authorizing a task.

98 Solution must provide the ability to implement custom validation business rules for all data input types.

99 Solution must allow the court to create new business rules and change existing ones without solution vendor assistance.

CDC CMS RFI Page 7 of 48 September 20, 2023

Page 8:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments100 Solution must provide the ability to trigger business rules in multiple

ways, including based on the entry or update of screen and/or database values, specific day/time, document arrival, etc.

101 Solution must provide the ability to allow administrators to define structure, content, and frequency with which the system displays ticklers, alerts, and prompts, i.e., administrator privileges that can set, initiate, or notify staff of needed actions.)

102 Solution must provide an unlimited number of configurable triggers for staff alerts including but not limited to: Multiple cases Active warrants Active detainers Other court-defined triggers

103 Solution must provide the ability to limit alerts by security profile.104 Solution must provide the ability for alerts and notifications to be

delivered by: At user logon E-mail Text message Screen message line

105 Solution must provide data validation on entry to ensure only valid data is entered.

106 Solution must eliminate/prevent duplicate data entry and/or prompt user when a possible duplication exists.

107 Solution must provide the ability to prevent redundant data entry.108 Solution must prevent duplicate system or reference numbers.109 Solution must allow court-defined system generated numbers, e.g.,

case number, case party number, bond number, document number, etc.

110 Solution must provide real-time user feedback for data validation errors and data integrity constraints violations.

111 Solution must provide the ability to use visual and audible clues definable by the system administrator.

112 Solution must provide data field edits, logical edits, relational edits,

CDC CMS RFI Page 8 of 48 September 20, 2023

Page 9:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsand acceptable field types (alphanumeric, numeric, date, time, code look-up, valid range, default values, required).

113 Solution must provide the ability to validate data to ensure that information is entered properly, e.g., nine digits for a SSN, valid dates, appropriate combination of letters and number for driver’s license, etc.

114 Solution must apply data entry formatting in applicable number fields, e.g., social security number xxx-xx-xxxx, phone number (xxx) xxx-xxxx, zip code xxxxx-xxxx, etc.

115 Solution must allow coded values to be hidden or visible, based on the dependency of other fields.

116 Solution must provide for the mandatory use of court specified codes in data entry fields.

117 Solution must allow for all coded values to be court defined and promote maximum use of court maintainable code tables.

118 Solution must provide the ability to designate code values as obsolete and unavailable for current use, preventing further entry of that value, yet retaining the value for inquires on historical data.

119 Solution must provide the ability to store the date a code table value becomes effective.

120 Solution must provide the ability to store the date a code table value becomes obsolete.

121 Solution must provide the ability to prevent display of obsolete code table values in picklists.

122 Solution must provide to the maximum extent possible picklists for field values.

123 Solution must provide configurable picklists and predictive auto-complete for field value selection at the field level.

124 Solution must provide the ability to limit available values in subsequent picklists or data fields based on previously entered data.

125 Solution must have the ability to mask fields (either entirely or portion) by user role including but not limited to: Password / Pin Social Security Number

CDC CMS RFI Page 9 of 48 September 20, 2023

Page 10:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Date of Birth Driver’s License Number Email Address Other court-defined fields

126 Solution must provide data encryption for Personally Identifiable Information (PII).

127 Solution must provide the ability to validate zip code and address.128 Solution must provide the ability to auto-populate city and state by

entering zip code.129 Solution must provide narrative fields with unlimited length.130 Solution must provide the ability to create templates for narrative

fields on any screen.131 Solution must provide standard word processing features and

functionality for input narrative/notes fields such as, but not limited to copy/cut/paste/delete, word-wrap, search/replace, alignment, bulleting, etc.

132 Solution must provide the ability to automatically spell check and grammar check free-form text entered into narrative/notes fields.

133 Solution must provide the ability to configure spell check to auto initiate and display possible errors without requiring the user to initiate the spell check function.

134 Solution must provide integration with Microsoft clipboard, with appropriate security permissions.

135 Solution must provide the ability to send email alerts, notifications, and requests directly from the solution.

136 Solution must provide the ability to share email and calendaring with MS Outlook accounts.

137 Solution must provide the ability to print documents/forms/reports on-demand.

138 Solution must provide the ability to generate barcode in multiple output formats.

139 Solution must provide barcode scanning capabilities.140 Solution reporting engine must be capable of producing graphs,

charts, and other forms of graphic presentation.

CDC CMS RFI Page 10 of 48 September 20, 2023

Page 11:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments141 Solution must share key data elements across all solution components

(no duplicate data entry).142 Solution must provide the ability to maintain historical information in

addition to the most current set of information.143 Solution must provide the ability to create an error log containing

error and user details.144 Solution must provide the ability to view and print the error log on-

demand.145 Solution must provide comprehensive auditing and logging giving a

granular view of wat data is being added, edited, deleted, and viewed,146 Solution must provide an audit block for each database table row that

at a minimum includes but is not limited to: Add user Add module/program Add timestamp Last update user Last update module/program Last update timestamp Other court-defined fields

147 Solution must provide court configurable auditing functionality that includes but is not limited to: Audit action Individual Record Module Information prior to and after change Errors Security violations Physical device location Workstation IP address Audit timestamp

148 Solution must provide the ability to review audit log activity performed by a specific user during a period of time.

149 Solution must provide the ability to print the audit log.

CDC CMS RFI Page 11 of 48 September 20, 2023

Page 12:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments150 Solution must provide the ability to secure the audit log from user

tampering.151 Solution must provide the ability to set audit log purge criteria.152 Solution must have the ability to merge, unmerge, and purge records

based on user permissions.153 Solution must maintain an audit trail of all merge, unmerge, and

purge actions.154 Solution must provide the ability to purge data based on date

parameters or court-defined retention parameters.155 Solution must provide the ability to archive data based on date

parameters or court-defined parameters.156 Solution provider must be able to provide and manage customizations

to solution, as agreed to by the court and solution provider.157 Solution must provide the ability to limit access based on security

access rights and privileges.158 Solution must provide the ability to designate read, write, update, and

delete access via role-based security.159 Solution must provide the ability to create multiple security groups.160 Solution must provide the ability for court to define access

permissions for each security group.161 Solution must provide the following password and pin management

functionality: User self-service Complexity Expiration (30 days, 60 days, never, etc.) Ability to enforce strong passwords per CJIS requirements Ability to “lock out” user after court-defined number of

attempted logons. Number of failed login attempts History of prior passwords and pins

162 Solution must provide security at the following levels: Facility Department Role

CDC CMS RFI Page 12 of 48 September 20, 2023

Page 13:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments User ID Menu Screen Report

163 Solution must have the ability to store passwords and pins in encrypted format.

164 Solution must provide the ability to maintain multiple sessions at the same time while maintaining session and data integrity.

165 Solution must be able to restrict the number of sessions allowed for a single user.

166 Solution must provide functional security to control what processes can be performed by staff. Users only see/access functions they are authorized to perform.

167 Solution must provide the ability to approve/confirm/override solution actions via electronic approval/confirmation mechanisms, e.g., pin, password, etc.

168 Solution must allow system administrators to maintain user permissions for system access.

169 Solution must provide the ability to log users off the system after a court-defined period in inactivity, based on user roles.

170 Solution must provide the ability to lock or deactivate a user’s account.

171 Solution must provide standards-based security for external user authentication (NOPD, OPSO, District Attorney, Public Defender, Probation and Parole, public, etc.)

172 Solution must provide the ability to tie security profiles (users, groups, computers, etc.) with Active Directory: Solution must support federated single sign-on (SSO) using Active

Directory Federation Services (AD FS) 4.0 and above with Security Assertion Markup Language Integration (SAML) and/or WS-Federation.

Solution must provide the ability to integrate with Active Directory (e.g. ADFS) to maintain dynamic updates for employee, supervisor, role, and location information.

CDC CMS RFI Page 13 of 48 September 20, 2023

Page 14:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Solution must have the ability to set and restrict rights based on

Active Directory information.173 Solution must provide the ability to support two-factor

authentication.174 Solution must provide the ability to support alternate authentication

technologies, i.e., ID card, security token, biometrics, etc.175 Solution must have the ability to import and export data in industry-

standard digital, audio, or multi-media file formats including but not limited to: XML CSV XLSX PDF TIFF PNG TIF DOCX TXT WAV MPEG AVI Other court-defined file formats

176 Solution must have the ability to import data from and export data to external systems as needed.

177 Solution must provide the ability to exchange data in real-time between the court and other Orleans Parish justice agencies (Orleans Parish Sheriff Office, District Attorney CMS, Public Defender, Probation and Parole, New Orleans Police Department, etc.)

178 Solution must provide the ability to easily integrate with third-party products.

179 Solution must provide the ability for users to open any third party software, or web site from within the software (e.g., Westlaw, LexisNexis, etc.).

180 Solution must provide a Web services Application Programming

CDC CMS RFI Page 14 of 48 September 20, 2023

Page 15:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description CommentsInterface (API) for integrations (e.g., data exchanges and interfaces) to other applications or partner agencies.

181 Solution must provide the ability to create user and user group work queues to list and manage and work assignments.

182 Solution must provide easy to view court configurable dashboards to provide summary information, statistics, scheduled tasks, outstanding tasks, key reports and other key metrics of interest to court staff.

183 Solution must provide the ability for the court to configure dashboard functionality for each user and/or functional user group.

184 Solution must provide the ability for each user to identify what type of variables is part of their dashboard.

185 Solution must display user work assignments on the user’s dashboard.186 Solution must include a supervisor dashboard view that displays

management information about the status of each user’s tasks (e.g., due today, tomorrow, specific date, high priority, etc.) for work queues.

187 Solution must provide the ability for user dashboards to update in real-time.

188 Solution must allow users to configure and manage their own dashboards, without having to rely on or pay the solution vendor to perform configuration tasks.

189 Solution must provide status monitoring to monitor progression of workflow and manually assigned tasks, and alert on bottlenecks and/or overdue tasks.

190 Solution must allow for the creation of custom status monitoring displays allowing control over what information is displayed and in what format.

191 Solution status monitoring must automatically refresh and display real-time data.

192 Solution must allow court-defined status monitoring benchmarks and checkpoints to signal progress within process.

193 Solution must visually represent status monitoring benchmarks and checkpoints via a progress bar.

194 Solution status monitoring configuration and display must be

CDC CMS RFI Page 15 of 48 September 20, 2023

Page 16:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentscontrolled by security permissions.

195 Solution must provide error messages that appear in a consistent format across all system components.

196 Solution must provide error messages that are capable of being integrated with online help.

197 Solution must provide administrator-configurable error messages, e.g., a system administrator is able to modify an error message to reflect a custom message.

198 Solution must provide contextual online help, i.e., field descriptions that are displayed based on the location of the mouse or cursor).

199 Solution must provide court customizable online help.200 Solution must allow court created online help documents that detail

court policies and procedures.201 Solution must provide functional online help documentation for

system end users and technical online help documentation for system administrators.

202 Solution must allow users to search on-line help by topic or keyword.203 Solution must provide an on-line tutorial, user guide, and help text to

assist staff in learning to perform job tasks, mange workflows, and solution functionality.

204 Solution must provide the ability to provide administrative messaging functionality that allows messages to be sent to individual users, groups of users, and/or broadcast to the facility to alert users.

205 Solution must provide the ability to capture and securely store electronic signatures captured via a digital signature pads, tablets, and smartphones, as well as directly on desktops.

206 Solution must provide the ability to upload and store signatures in secure digital format.

207 Solution must provide the ability to view a digital signature.208 Solution must have the ability to apply digital signatures to

documents/forms/reports based on security permissions.209 Solution must have the ability to enable custom form and report

creation, that can be configured as desired by court, and saved in a form/report folder (or list) for later use.

CDC CMS RFI Page 16 of 48 September 20, 2023

Page 17:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments210 Solution must provide a document management, indexing, and

storage capabilities.211 Solution must provide the ability to attach or interface multiple

document scanning devices.212 Solution must provide the ability to import files from local hard drives,

accessible network drives, digital cameras (still and video), and document scanners.

213 Solution must NOT store scanned document and images in proprietary file formats.

214 Solution must provide the ability to create and index electronic case folders.

215 Solution must provide the ability to provide a database to store electronic media, including the following file types: Word Access Excel Text files HTML PDF Images Videos files Audio files

216 Solution must provide the ability for attached electronic media to be readily accessible from any screen via hyperlinks.

217 Solution must provide the ability to scan or import documents and images directly into solution and attach to the appropriate record.

218 Solution must provide auto-scanning of solution auto-generated documents/forms/reports, i.e., a solution generated document/form/report does not need to be printed and then scanned and attached/linked to the related case file for future reference.

219 Solution must provide the ability to record document metadata, e.g., document type, document name, document number, document date and time, confidentiality indicator, key words, etc.

220 Solution must provide the ability to index documents and images for

CDC CMS RFI Page 17 of 48 September 20, 2023

Page 18:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentseasy retrieval by document type, document name, document number, document date and time, confidentiality indicator, and key words.

221 Solution must provide ability to route scanned/imported documents for processing and/or review.

222 Solution must provide the ability to open, view, and delete documents and attachments.

223 Solution must provide document-based security based on user roles.224 Solution must provide the ability to restrict access to specific

document types.225 Solution must provide the ability to restrict access to confidential

documents.226 Solution must provide an audit trail of documents and images

accessed, printed, or exported from solution.227 Solution provider must provide the following service levels:

Severity Level 1 – System is down; attention required immediately, maximum 30 minute response time.

Severity Level 2 – system functionality is impacted or parts of the system are down, maximum one (1) hour response time.

Severity Level 3 – Non-mission critical processes are impacted, maximum eight (8) hour response time.

228 Solution must be thoroughly documented; both from a functional and technical perspective prior to implementation, and a process must be in place for future updates and maintenance of the documentation, e.g., functional manuals, user manuals, technical manuals, and configuration manuals prior to implementation to ensure the court is prepared for operational use of the system.

229 Solution provider has the ability to provide support levels as defined by the court

230 Solution provider provides support on a 24/7/365 basis.231 Solution provider provides a Web-based support.232 Solution provider provides a searchable database of common

problems and FAQs to assist with problem determination.233 Solution provider offers access to an online user group.234 Solution provider offers online training and recorded training sessions

CDC CMS RFI Page 18 of 48 September 20, 2023

Page 19:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsat no cost.

235 Solution vendor must include at least annual software releases or updates in their annual support and maintenance agreement for no additional cost.

236 Solution must provide the ability to initiate/accept a case filing via the electronic transfer of data from external agencies (e.g., data exchange / interface with Orleans Parish Sheriff Office JMS, Orleans Parish District Attorney CMS, or Orleans Parish Municipal Court CMS).

237 Solution must provide configurable workflows to support manual case creation for direct filings, change of venues, probation/parole violations, etc.

238 Solution must provide the ability to configure required case activities/events based on court-defined business rules.Solution business rule engine must be capable of: Initiating the scheduling of future tasks based on the occurrence

of prior tasks or events as defined by the court. Routing cases and work tasks based on court-defined rules and

notify users of the routed items. Triggering generation of events, documents, notifications, and

case status changes based on prior events. Preventing users from saving or exiting a case without saving

mandatory fields. Closing cases based on court-defined rules. Implementing other court-defined business rules.

239 Solution must provide the ability to automatically generate calendar/docket entries through the case initiation process.

240 Solution must provide the ability to link or insert defendant booking photos received from the Orleans Parish Sheriff Office.

241 Solution must provide the ability to define case number schemes per court rules to include year, case type, agency and/or division abbreviations, and sequential number.

242 Solution must be capable of creating a case to include case type (e.g., drug, murder, capital punishment, domestic violence, bond forfeiture, etc.), style, status, and initial filing information.

CDC CMS RFI Page 19 of 48 September 20, 2023

Page 20:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments243 Solution must allow Law Enforcement numbers (NOPD, OPSO, OPCD,

etc.) and court numbers (CDC, MC) to be linked to court cases and be searchable.

244 Solution must provide a dashboard to show overall tracking of required items required for initial case filing.

245 Solution must provide the ability to electronically route case and work tasks and notify users to the routed items.

246 Solution must provide the ability to carry forward data when manually entering repetitive items such as calendar events and charges (e.g., after entering the first charge and associated details such as bond, the first charge data will be carried forward if additional charges are being entering allowing the user to change only the data that needs to be changed.).

There are risks with this requirement in that data may not be changed by the user. Even though requested by George, I suggest giving some further thought to this requirement.

247 Solution must provide the ability to incorporate existing judge assignment algorithms/routines for random assignment of judges.

248 Solution must provide the ability to manually assign and reassign cases to judges.

249 Solution must provide the ability to monitor judge assignments to ensure equitable distribution of cases based on case type.

250 Solution must provide end-to-end administration over the life cycle of a criminal case from inception\creation through charge disposition and case closure.

251 Solution must provide checklist functionality that automatically adds predefined checklists to a case depending on case type or other court-defined criteria.

252 Solution must provide at a case level the ability to schedule, track and administer the outcome of all hearings including arraignments, motions, trials, probation violations, judicial reviews, report/status checks, etc.

253 Solution must provide the ability for court staff to designate cases with special scheduling needs/requirements.

254 Solution must provide the ability to maintain at a case level, trial details including trial type (e.g. jury, bench), jury sworn date, evidence submission/disposition and date, disposition, sentence, etc.

CDC CMS RFI Page 20 of 48 September 20, 2023

Page 21:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments255 Solution must provide court configurable workflow functionality to

ensure all steps and/or procedures are performed in an efficient and timely manner based on court-defined business rules.Solution must minimize the number of screens required to maintain (add, edit, delete, and query) a case and case related details.

256 Solution must provide workflow functionality that provides court defined queuing for individual or groups, with multi-step process flows, associated thresholds, due date monitoring, court configurable timeframes and escalation rules and notification of process completions.

257 Solution must provide the ability to configure workflows to trigger an electronic user notification, (e.g. system generated email).

258 Solution must provide the ability to configure workflows to execute interface tasks that are external to the court solution at any point within the workflow, (e.g., notify NOPD and OPSO of warrant recall, notify OPSO of bond modification, notify NOPD of charge dispositions, etc.).

259 Solution must provide the ability to create and maintain electronic case files allowing any file type to be linked to the case file including but not limited to documents, images, video, email correspondence, etc.

260 Solution must be able to track all correspondence by individual involvement to a specific case.

261 Solution must provide the ability to scan and/or import documents directly into the electronic case file.

262 Solution must allow the contents of an electronic case file to be searchable using indexing.

263 Solution must provide the ability to copy and/or move electronic case file contents from one electronic case file to another electronic case file (e.g., copy involved persons, charges, and documents to a co-defendant electronic case file).

264 Solution must provide the ability to generate unique software-generated barcode to identify case related documents, exhibits, evidence, etc.

CDC CMS RFI Page 21 of 48 September 20, 2023

Page 22:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments265 Solution must provide the ability to scan a barcode to retrieve case

information and/or determine the location of exhibits and evidence.266 Solution must provide for court-defined use of court-designated

required fields on solution screens.267 Solution must provide for the mandatory use of court-defined code

values in solution screens.268 Solution must provide for the creation of time based

ticklers/reminders with notifications.269 Solution must provide the ability for court-defined business rules for

required data fields based on the other field values.270 Solution must provide the ability to close a case automatically based

on court-defined business rules.271 Solution must provide the ability to restrict users from closing a case

unless other values are entered, based on court-defined business rules (e.g., a cases cannot be closed without a disposition).

272 Solution must provide the ability for a case closure to auto-generate court defined documents, notifications, and reports.

273 Solution must provide the ability to track staff actions and trigger/auto-generate court defined documents, notifications, and events based on the work actions.

274 Solution must allow for automatic notification via email or system prompts to court users and external court-defined case participants for changes in case and/or status.

275 Solution must allow for notification of case parties regarding changes in cases based on court-defined business rules.

276 Solution must provide the ability to manually assign and/or reassign cases to different attorneys and/or judges.

277 Solution must support multiple defendant cases (i.e., co-defendant cases).

278 Solution must provide the ability to sever defendants from a multi-defendant case to create separate cases.

279 Solution must provide the ability to combine/merge cases and/or defendants into a single case.

280 Solution must provide the ability to transfer cases for one defendant

CDC CMS RFI Page 22 of 48 September 20, 2023

Page 23:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsto another if incorrectly assigned.

281 Solution must alert the user when adding a new case party to a case if the individual is involved in another case.

282 Solution must alert the user when adding a new case party to a case if the individual has a pending court date.

283 Solution must provide the ability to link/relate cases to other cases.284 Solution must provide the ability to track substance abuse testing

(drug and alcohol) and test results.285 Solution must provide both a person and case centric mode (i.e.,

querying a person will display all cases and related case details for a person, querying a case will display all case party details for the case).

286 Solution must allow the user to drill-down to pertinent data in both person and case centric modes.

287 Solution must provide the ability to display the defendant’s name at the top of each screen in both person and case centric modes.

288 Solution must provide person and case centric dashboards that display key person and/or case details.

289 Solution must provide court performance measure statistics like those originally designed by the National Center for State Courts (NCSC) CourTools project to measure court performance and provide statistical reporting.

290 Solution must provide an unlimited length note/narrative field with for each individual case.Solution must provide the ability to share notes court-wide, share notes with designated users, or make notes private.

291 Solution must provide for confidential judge notes/comments viewable only by the judge and/or a judge authorized staff member (e.g., law clerk).

292 Solution must provide users with a notes/narrative library that permits users to have sentences and paragraphs of text that can be copied and pasted into a case note.

293 Solution must provide data fields for all data elements required for Louisiana Supreme Court reporting.

294 Solution must provide a court-customizable dashboard screen specific

CDC CMS RFI Page 23 of 48 September 20, 2023

Page 24:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsto each user and/or group job duties.

295 Solution provided dashboards must allow easy assessment of items requiring action (tasks) by court staff. Additionally, workflow milestones and changing statuses of defendants will need to be displayed.

296 Solution must provide the ability for administrators/supervisors to monitor subordinates workloads.

297 Solution must provide the ability for administrators/supervisors to reassign/redistribute workload amongst users.

298 Solution must provide the ability for previously closed cases to be reopened, retaining all history on the case.

299 Solution must provide the ability to seal cases from both staff and/or public view based on security privileges.

300 Solution must provide the ability to share information (import/export) with external agencies (e.g., New Orleans Police Department RMS, Orleans Parish Sheriff Office JMS, Orleans Parish District Attorney CMS, Orleans Parish Municipal Court CMS, Probation and Parole, Louisiana Department of Correction, and Louisiana Supreme Court etc.)

301 Solution must provide the ability to generate a summary of the case to include defendant names and addresses, associated case parties, attorneys, charges, dispositions, sentences, bond details, and other court-defined information.

302 Solution must provide the ability to record and maintain case activities/events using activity/event codes along with free form comments pertaining to the activity/event.

303 Solution must provide the ability to add, edit and delete case activities from an activity view based on security privileges.

304 Solution must provide the ability to automatically generate minute entries, future events, documents and notifications based on completion of a case activity/event.

305 Solution must provide the ability to scan and record all documents filed in a case.

306 Solution must allow the viewing of documents from the activity view

CDC CMS RFI Page 24 of 48 September 20, 2023

Page 25:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsby clicking on a document icon and/or hyperlink.

307 Solution must provide a document history view of all court documents created for defendant in the case ordered by the date created, document name, and viewing status.

308 Solution must provide the ability to print, reprint, or delete documents from the document history view.

309 Solution must provide the ability to view/print a chronological (ascending or descending) history of all case activities and documents filed in a case.

310 Solution must provide a history of all court documents and notifications sent to external agencies by date, type, issued by (e.g., clerk, magistrate, judge, etc.), and return due date.

311 Solution must provide the ability record and track miscellaneous activities for a case.

312 Solution must provide an activity list that lists all activities associated with a defendant in a case.

313 Solution must provide a searchable and updateable collection of person records that uniquely identifies each person record and allows records to be associated with one or many cases.

314 Solution must allow an unlimited number of case parties per case.315 Solution must allow an unlimited number of subject types (e.g.,

defendants, victims, witnesses, etc.) per case.316 Solution must provide the ability to add, edit, delete, and query all

parties in a case. 317 Solution must capture and store demographic, address and personal

identifiers data required for a full featured Master Name Index (MNI) to include but not limited to: Subject Type (defendant, co-defendant, complainant, victim,

witness, attorney, expert witness, etc.) Prefix (title) Last Name First Name Middle Name

CDC CMS RFI Page 25 of 48 September 20, 2023

Page 26:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Suffix Business/Organization Name Date of Birth Addresses broken into component fields Apt # City State Country Zip and Plus 4 Code Residence Phone (multiples) Business Phone (multiples) Mobile Phone (multiples) E-mail addresses (multiples) Gender Race Ethnicity Citizenship Height Weight Eye Color Hair Color Social Security Number Driver License Number Driver License State Driver License Type CAD Item Number Arrest Number Offender Booking Number Magistrate Number Photos / Mugshots Aliases and Nicknames (multiples) Other court-defined criteria

318 Solution must provide the ability to store an unlimited number of addresses, phone numbers, and e-mail address for any case party.

CDC CMS RFI Page 26 of 48 September 20, 2023

Page 27:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments319 Solution must provide the ability to track dates associated with

address, phone number, and email address changes.320 Solution must provide the ability to maintain and track different

addresses for each individual case and bond.321 Solution must provide the ability to store an unlimited number of

aliases.322 Solution must provide the ability to capture one or more person

identifiers (e.g. driver’s license, SID, SSN, bar number, badge number, etc.) for each defendant, attorney, and other participant in a case, and use this identifier to link the individual with case and other case information.

323 Solution must provide the ability to track an unlimited number of relationships between individuals (e.g., spouse, ex-spouse, child, brother, sister, in-laws, friend, co-defendant, etc.).

324 Solution must provide discrete name fields for first name, last name, middle name, suffix (e.g., Sr., Jr., III), and title; accommodate hyphenated names, foreign names, aliases (AKAs), doing business as (DBAs), and corporate names.

325 Solution must provide the ability to indicate a case party requires a translator as well as the language requirement.

326 Solution must provide the ability to capture multiple sets of data for the same person, business or organization.

327 Solution must provide the ability to prompt users when person identity information may already exist for an individual being entered, including most likely candidate identities to avoid duplicate data and unnecessary entry; e.g., support phonetic (Soundex) and other complex (multi-field) algorithms for matching identities to avoid creation of duplicate records for individuals.

328 Solution must provide the ability to add, edit, and delete case party’s data in a case no matter the data’s origin (data exchange, interface, direct entry, etc.)

329 Solution must provide the ability to maintain confidential witness details.

330 Solution must provide the ability to change the order of defendants in

CDC CMS RFI Page 27 of 48 September 20, 2023

Page 28:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsa case.

331 Solution must provide the ability to maintain a system table of attorneys registered to practice in the court.

332 Solution must provide the ability to maintain a system table of attorney firms.

333 Solution must provide the ability to link/associate attorneys with an attorney firm.

334 Solution must provide the ability add and edit attorney records, flag as active, and flag as inactive.

335 Solution must provide the ability to link/associate an attorney with one or more defendants.

336 Solution must provide the ability to inactivate an attorney/defendant link/association.

337 Solution must provide the ability to maintain a system table of judges, magistrates, and commissioners details.

338 Solution must provide the ability to maintain a system table of police officer details

339 Solution must provide an unlimited length note/narrative field with for each case party.

340 Solution must provide the ability to query/identify case parties by: Subject Type (defendant, co-defendant, complainant, victim,

witness, attorney, expert witness, etc.) Name (last, first, middle, business/organization) Aliases Date of Birth Gender Social Security Number State ID Number Case Number Case Filed Date Range Court Dates Judge Prosecutor Defendant’s Attorney / Public Defender

CDC CMS RFI Page 28 of 48 September 20, 2023

Page 29:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Warrant Number Warrant Issue Date Protection Order Number A combination of the above search elements (e.g., last name +

gender + DOB) Other court-defined criteria

341 Solution must allow users to view all involvements of a case party on one (1) screen (e.g. all aliases, cases, relationship to each case, etc.).

342 Solution must allow users to view all cases linked to a name, and from the view allow users to go directly to a specific case.

343 Solution must provide the ability to add, edit and delete charges from a charges view based on security privileges.

344 Solution must allow an unlimited number of charges per case and/or defendant.

345 Solution must provide the sequential numbering of charges as they are entered.

346 Solution must provide the ability to record all charge level data elements required by the Louisiana Supreme Court.

347 Solution must provide the ability for users to repeat similar charge details automatically for cases/defendants with multiple charges.

348 Solution must provide the ability to link charges to all persons (defendants, victims, witnesses, police officers, attorneys, etc.) involved in the case and case events.

349 Solution must provide the ability to record the NOPD CAD Item Number, OPSO Booking and Arrest Numbers, Clerk’s Number, DA’s Number, State SID, and any other court identified number per charge.

350 Solution must provide the ability to record incident information, offense date and time, arrest, booking and custody information, probable cause, Rule to Show Cause, and bond at the charge level.

351 Solution must provide the ability to amend filed charges.352 Solution must provide the ability to record a charge reduction while

maintaining the original charge.353 Solution must provide the ability to track arresting charge,

prosecution charge, and final charge for reporting/statistical

CDC CMS RFI Page 29 of 48 September 20, 2023

Page 30:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentspurposes.

354 Solution must provide the ability to enter and track statute enhancers and modifiers.

355 Solution must provide a note/narrative field for each charge with unlimited text length.

356 Solution must provide the ability to re-order charge counts (e.g., count one (1) is changed to count three (3), and count three (3) becomes count one (1) or some other count).

357 Solution must provide the ability to import the Louisiana Supreme Court statute/charge code table into the solution charge code table.

358 Solution must be able to import and/or manually enter municipal/city charges into the solution charge code table.

359 Solution must allow the court to update all charges (statutes), associated fees, etc. whenever legislative changes occur without having to rely on the solution vendor.

360 Solution must provide a query that presents a RAP sheet styled view of charges, dispositions and sentence details together. Additionally the ability to print the RAP sheet must be provided.

361 Solution must provide the ability to add, edit and delete a charge disposition from a charges view based on security privileges.

362 Solution must allow users to enter and track a charge plea and/or disposition (i.e., guilty, not guilty, dismissed, etc.).

363 Solution must provide the ability to add, edit and delete charge sentence details from a charges view based on security privileges.

364 Solution must allow users to enter and track each charge’s sentence including the sentence type (e.g., jail, suspended, fine, restitution, probation, or type combinations) sentence start date and duration, sentence credit time suspended time, consecutive/concurrent sentence indicator, sentence location, probation, community service, work program, etc.

365 Solution must allow users to enter and track court ordered conditions placed on a case (e.g., non-monetary provisions such as work programs, community service, service restitution, educational programs, etc.).

CDC CMS RFI Page 30 of 48 September 20, 2023

Page 31:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments366 Solution must provide the ability to track progress, compliance, and

completion on referrals for services and programs (e.g., counseling, treatment, education, etc.).

367 Solution must allow users to enter and track probation/parole requirements if ordered.

368 Solution must provide the ability to create and maintain sentencing templates for each judge.

369 Solution must provide the ability to record bonding details for each defendant in a case.

370 Solution must provide the ability to add, edit and delete bonds from a bond view based on security privileges.

371 Solution must provide a code table to identify and maintain details for bonding and surety companies.

372 Solution must provide the ability to record bondsman name, address, and bond amount for cash and property types.

373 Solution must provide the ability to record one or more bond types (e.g., cash, property, surety and commercial) per charge.

374 Solution must provide the ability to record both numeric and non-numeric bond amounts (e.g., No Bond, ROR, 1000.00, 10,000.00, etc.) per charge.

375 Solution must provide the ability to enter any combination of cash, property, surety, or commercial bonds to make up the total bond amount.

376 Solution must provide the ability to view a history of defendant bond information by charge to include bond type, bond amount, bond date, bondsman name, surety name, etc.

377 Solution must provide for event scheduling and rescheduling.378 Solution must maintain a code table of court events (e.g., first

appearance, arraignment, motion hearing, status conference, trial, sentencing, etc.).

379 Solution must allow court-defined calendar/docket limits (e.g., date, time, case type, event type, event length, etc.).

380 Solution must allow court clerks to calendar future court dates while remaining within court-defined docket limits.

CDC CMS RFI Page 31 of 48 September 20, 2023

Page 32:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments381 Solution must provide the ability to schedule all court events (e.g.,

First Appearance hearings, Arraignments, Pre-Trial hearings, Motions, Trials, Sentencings, Miscellaneous hearings, etc.).

382 Solution must allow user and user groups calendars to be displayed on an a user’s main dashboard.

383 Solution must allow user to manually and automatically link an involved case party’s events to a case.

384 Solution must provide a viewable/printable calendar (Docket Master) for upcoming events.

385 Solution must provide the ability to specify the view/print order of calendars (e.g., case number, case type, event, defendant, etc.).

386 Solution must provide the ability to produce event schedules for individuals and groups.

387 Solution must be able to display individual, office, and division calendars.

388 Solution must provide the ability to print and export calendars to PDF, Excel, RTF, Word, and Microsoft Outlook.

389 Solution must provide the ability to display case and non-case events in a format similar to Microsoft Outlook.

390 Solution must provide the ability to export calendars to Microsoft Outlook.

What about Gmail?

391 Solution must provide the ability to publish and display calendar/docket information via a publicly accessible Web site.

392 Solution judge calendars must show docket counts for each date and provide the ability to open the docket and view case details from the calendar/docket view.

393 Solution must provide a business rule engine that employs court defined business rules to systematically create minute entries based on the checking/selecting predefined minute data elements and entry of case related variable data elements such as calendar entries, bond amount, charge disposition, charge sentence fields, etc.

394 Solution must provide integration between the court calendar and the minute generation process.

395 Solution must allow a minute clerk to click on quick links to add items

CDC CMS RFI Page 32 of 48 September 20, 2023

Page 33:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsto minutes, or to type court-defined minute codes into a minute command prompt to quickly add items to minutes.

396 Solution must provide the ability for the minute entries to be customizable by minute clerks.

397 Solution must provide the flexibility to build minute entries for differing requirements by judge, minute clerk, etc.

398 Solution must provide a stream-lined user interface to allow for the speedy entry of court minute information in the courtroom.

399 Solution must provide the ability for minute clerks to create minute entries by freeform typing.

400 Solution must provide full word processing capabilities with spell-check for clerk entered/edited minute text.

401 h402 Solution must provide minute entries with unlimited length.403 Solution must provide the ability for minute clerks to edit system

generated minutes.404 Solution must provide the ability to designate which system

generated minute entries may be edited by the minute clerks.405 Solution must provide a means to finalize or lock one or more minute

entries at a time.406 Solution must restrict editing of minutes once finalized (i.e., finalized

minutes are read/view only).407 Solution must provide the ability to amend minutes while maintaining

the original minutes (i.e., supplemental minutes are entered).408 Solution must provide the ability for an authorized user to copy

minute text from one defendant’s case to the Windows clipboard for editing and pasting to another defendant case.

409 Solution must control the editing of minutes based on user security.410 Solution must provide the ability to view/print case minutes in either

ascending or descending order by minute date.411 Solution must provide the ability to view/print minutes by case, court

date, section/department, judge, event and other court-defined criteria.

412 Solution must provide a minute history view that lists all court

CDC CMS RFI Page 33 of 48 September 20, 2023

Page 34:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsminutes recorded in a case by case number, date, and minute text.

413 Solution must provide the ability to create both a detailed (full content) and partial (reduced content) minute summary containing the finalized minutes of each case processed for a calendar/docket (Docket Master).Solution must provide the ability to view the partial (reduced content) minute summary of each case processed for a calendar/docket (Docket Master) via the court Web portal.

414 Solution must include an integrated financial system.415 Solution must adhere to Generally Accepted Accounting Principles

(GAAP).416 Solution must provide the ability to establish an unlimited number of

court-defined fine, fee, cost, and bank accounts.417 Solution must provide the ability to establish an unlimited number of

general ledger accounts that support master accounts and sub-accounts that rollup into the master account.

418 Solution must have a general ledger that permits court-defined periods and are stored for an unlimited time period.

419 Solution must provide for tracking of fines, fees, costs, with integrated assessment, payment processing, payment application, collection, and agency distribution of court fines, fees and costs.

420 Solution must provide the ability to assess, track, and distribute restitution.

421 Solution must provide the ability to produce reports showing restitution received and money disbursed (by victim) for each case or defendant.

422 Solution must provide the ability to track debits/credits for defendants and agencies.

423 Solution must provide the ability to set up and monitor payment plans for defendants.

424 Solution must provide the ability to quickly identify delinquent payments, generate alerts and automatically generate delinquent payment notices.

425 Solution must provide debt collection capabilities to manage efforts to

CDC CMS RFI Page 34 of 48 September 20, 2023

Page 35:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsrecover court-related debts on all overdue and past-due court payments.

426 Solution must maintain a system table of standard fines, fees and costs at the charge level.

427 Solution must provide the ability to compute fines, fees and costs using a configurable table and not business rules or program code to determine the fines, fees and costs. The configurable aspects of the fines, fees, and costs must provide effective to and from dates to allow the court to update and make effective the fine, fee, and cost assessments.

428 Solution must permit a judge to increase or decrease a calculated fine, fee, and/or cost amount with a judge imposed amount.Solution must provide the ability to account for all bond assets, forfeitures, cancellations, and refunds.

429 Solution must maintain a table of agencies and agency details (e.g., address, phone number, contact, etc.) receiving court disbursed fines, fees, and/or costs.

430 Solution must be able to process cash, check and credit card payments.

431 Solution must allow for full, partial and installment payments by various methods.

432 Solution must allow multiple types of payments in a single transaction (e.g., cash, check, credit card and fee waiver).

433 Solution must allow single payment for multiple cases with the ability to process separately for each case.

434 Solution must compute totals, list transactions and balance each case drawer.

435 Solution must produce a summary for each cashier including totals for each type of payment (e.g., cash, check, credit card, fee waiver).

436 Solution must be able to print checks.437 Solution must be capable of generating a sequentially numbered

check or batch of checks.438 Solution must provide the ability to view and print an itemized receipt

for all payments received.

CDC CMS RFI Page 35 of 48 September 20, 2023

Page 36:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments439 Solution must provide the ability to view and print multiple receipts

from one financial transaction covering payment for multiple cases.440 Solution must provide the ability to reconcile payments received to

cases and/or charges.441 Solution must provide the ability to produce, view and print a deposit

listing for a specified date range.442 Solution must provide the ability to produce, view and print a check

register for a specified date range.443 Solution must provide the ability to produce, view and print daily cash

receipts journal.444 Solution must provide the ability to produce, view and print a general

ledger for a specified date range.445 Solution must provide the ability to produce, view and print court

disbursements of fines, fees and costs for a specified date range.446 Solution must provide the ability to produce, view and print summary

lists of financial transactions (e.g., court fee assessment, court cost assessment, waivers, voided transactions, etc.) for specific cases and defendants over specified periods (e.g., daily, monthly, life of case).

447 Solution must provide robust financial auditing features.448 Solution must provide bar-coding capability to help users easily record

and track the location of case exhibits and evidence.449 Solution must provide the ability to record and track case related

forfeitures (e.g. driver’s license, passport, cash, and weapons).450 Solution must provide the ability to create, track, and process

warrants/capiases issued for parties in a case.451 Solution must provide the ability to create all court-defined

warrant/capias types.452 Solution must be able to digitally sign generated warrants/capiases.453 Solution must provide the ability to print/view warrants to include but

not limited to: Warrant type Warrant issue date Warrant signed date Signing judge

CDC CMS RFI Page 36 of 48 September 20, 2023

Page 37:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Defendant identification information Bond amount Warrant text

454 Solution must provide the ability to quash/recall a warrant recording date quashed/recalled, judge who ordered warrant quashed/recalled, reason why quash/recall was ordered.

455 Solution must provide a notice of warrant quash/recall to designated Law Enforcement agencies (NOPD, OPSO, etc.)

456 Solution must allow batch production of warrants.457 Solution must provide the ability for warrants to be signed digitally.458 Solution must provide the ability to track warrant service/execution.459 Solution must provide a system alert to indicate an outstanding

warrant for a case party.460 Solution must provide the ability to print warrants.461 Solution must prevent the printing of a recalled warrant.462 Solution must be able to maintain a library of notice templates.463 Solution must provide the ability to generate all notices produced by

the court on-demand and in batch mode (e.g., generate all court notices for a court session at day’s end).

464 Solution must be able to digitally sign generated notices.465 Solution must provide the ability to create and track subpoenas issued

for parties in a case to include regular subpoenas and subpoenas duces tecum.

466 Solution must be able to digitally sign generated subpoenas.467 Solution must provide the ability to generate witness lists along with

court ordered subpoenas.468 Solution must provide the ability to include case party service of

process information on witness lists.469 Solution must provide the ability to import and export data with the

CourtNotify Subpoena Management software product (vendor: Orion Communications Inc., Web Site: https://www.orioncom.com).

470 Solution must include a Document Management System seamlessly integrated with the overall case management system.

471 Solution must include hard copy imaging/scanning functionality to

CDC CMS RFI Page 37 of 48 September 20, 2023

Page 38:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsfacilitate digital capture of paper based documents and systematically store scanned documents within a case’s electronic case file.

472 Solution must include a document scanning feature that allows users to scan documents and images directly into the electronic case file from a desktop attached scanner.

473 Solution must provide duplex scanning and de-skew, de-speckle, and blank page detection features.

474 Solution must provide automatic sensing of document orientation during scanning.

475 Solution must provide the ability to insert, delete and reorder document pages.

476 Solution must provide the ability to have scanned documents populate predefined work queues for validation and follow-up processing.

477 Solution must provide the ability to display each work queue’s items waiting for processing.

478 Solution must store scanned in and system generated documents as searchable PDF’s.

479 Solution must allow image files such photographs to be imported directly into the electronic case file.

480 Solution must provide the ability to watermark scanned in documents with case number, date and time filed, and/or other court-defined metadata.

481 Solution must provide the ability to annotation scanned in or system generated documents.

482 Solution must provide the ability to add virtual “sticky notes” to a document within the electronic case file to alert staff of important details regarding the case.

483 Solution must allow documents to be indexed by multiple key fields including case number, document number, document type, filing/generation date, and other court-defined metadata.

484 Solution must support designating documents as “confidential” within an electronic case file (e.g. drug test results). Access to such documents would be restricted to users with the appropriate level of

CDC CMS RFI Page 38 of 48 September 20, 2023

Page 39:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentssecurity.

485 Solution must provide the ability for authorized users to delete or seal electronic case file documents.

486 Solution must provide the ability to digitally sign system generated documents auto-scanned into the case’s electronic case file.

487 Solution must provide the ability to redact sensitive, privileged, and/or confidential information from documents, highlight information in documents, and add notations to documents.

488 Solution must provide the ability to retain the original document as well as a redacted version of the document.

489 Solution must provide the ability to move, transfer or copy scanned in or system generated documents from one electronic case file to another.

490 Solution must provide the ability to electronically route documents generated/approved in court to all necessary parties via multiple methods including but not limited to email, web service, or other automated means.

491 Solution must provide search capabilities across case documents stored within the electronic case file to users with the appropriate level of security. Search must include all documents whether scanned in or system generated.

492 Solution must provide the ability to search through the electronic case file by document type, document filed date, key words, etc.

493 Solution must provide a search feature permitting single word, partial, and multiple word searches of the electronic case file documents.

494 Solution must provide the ability to expunge defendant charges based on security privileges.

495 Solution must provide the ability to expunge charges by flagging the charge as expunged without physically deleting the charge.

496 Solution must retain expunged charges for statistical purposes.497 Solution must provide the ability to prevent the viewing of

defendant’s expunged charges by court staff without proper security privileges or by the public.

498 Solution must provide the ability to electronically notify local Law

CDC CMS RFI Page 39 of 48 September 20, 2023

Page 40:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description CommentsEnforcement agencies of expunged charges.

499 Solution must provide the ability to seal a case and particular documents based on security privileges.

500 Solution must provide an audit trail of expunged and sealed records to document when the action was ordered and by whom.

501 Solution must provide integrated appeals processing.502 Solution must provide the ability to file a “Motion to Appeal” into the

defendant’s case file.503 Solution must provide the ability to track the appeals process.504 Solution must provide the ability to package data, documents,

transcripts and exhibits to be included in the appeals package.505 Solution must provide the ability to preview the appeals package and

include marker pages and page ranges for items to be included (not printed from system) in the appeals package.

506 Solution must be able to page number each printed page of the appeals package.

507 Solution must be able to number each appeals package item and generate an appeals package “Table of Contents” (numerical and alphabetical) including page numbers.

508 Solution must provide the ability to view and inspect the appeals package before printing.

509 Solution must comply with all Louisiana Supreme Court reporting requirements.

Nathaniel to provide Supreme Court Compliance requirements.

510 Solution must provide users the ability to search by specifying criteria, or combinations of criteria, for fast, efficient, and accurate search results for viewing and printing. Users must be able to search using the following search criteria: Case Number Magistrate Number Folder Number (OPSO Booking Number) Arrest Number NOPD Item Number

CDC CMS RFI Page 40 of 48 September 20, 2023

Page 41:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Case Type Case Party Names to include defendants, victims, witnesses, etc. Case Party Alias Names Social Security Number Driver’s License Number Gender Date of Birth Attorney Names Attorney Bar Number Judge Name Court Section/Department Prosecutor Name Public Defender Name Bondsman/Surety Bonding Agency Case Filed Date Court/Event Dates Charge Codes Disposition Codes Minute Codes Activity/Event Codes Dates and Date Ranges Combination of any search criteria identified above Other court-defined criteria

511 Solution must provide the ability to search names by a variety of criteria such as sound like searching (Soundex), partial name, exact spelling, synonyms, and diminutive first names together with other demographic information such as social security number, driver’s license number, and date of birth to eliminate duplicate results.

512 Solution must allow the entry of a specific date or date range for all searches.

513 Solution must allow the ascending or descending ordering of entries in a query results list by clicking on the header column.

514 Solution must provide query drill down capability on all search results

CDC CMS RFI Page 41 of 48 September 20, 2023

Page 42:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsto view additional case or defendant details.

515 Solution must allow the printing of query results based on user security privileges.

516 Solution must allow the copying of query results to the Windows clipboard based on user security privileges.

517 Solution must allow the retrieval, viewing and printing of case and/or defendant related documents by: Document Number Case Number Document Type Document Filed/Created Date Other court-defined criteria

518 Solution must provide integrated reporting, documents and forms generation capabilities.

519 Solution must provide the ability for automatic document and form generation using all data available in the solution database.

520 Solution provided forms/document generator must provide design tools to facilitate form/document layout, data inclusion, and calculation capabilities (e.g., calculate total due, calculate sentence less time served, etc.)

521 Solution must provide the ability to format forms/documents and reports to accommodate multiple paper sizes, different fonts, colored text, special symbols such as checkbox, check mark, dollar sign, etc..

522 Solution must allow general users to design and run reports without having a technical background or reporting writing knowledge.

523 Solution must generate file folder labels for manual case files.524 Solution must auto-scan generated documents and forms to the

associated electronic case file for future reference and reprinting if needed.

525 Solution must allow reports to be placed in user-defined locations for eased execution of reports (e.g., calendar reports run from calendar screens).

526 Solution must allow for report execution to be automated with report output emailed to staff and external stakeholders based on a

CDC CMS RFI Page 42 of 48 September 20, 2023

Page 43:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsscheduled delivery schedule.

527 Solution must allow reports to be printed and/or exported in PDF, CSV, Word, Excel, and XML formats without the need for additional third-party software.

528 Solution provided form/document generator must permit the court to create custom forms/documents for single or repeated use.

529 Solution must provide the ability to create documents with Microsoft Word from within the solution.

530 Solution must provide the ability to create all required forms/documents and reports based on court-defined criteria.

531 Solution must generate State of Louisiana and federal reports that are required.

532 Solution must provide the ability to maintain a library of form, and document templates (e.g., letters, receipts, subpoenas, warrants, etc.).

533 Solution must provide the ability to include any solution object (e.g., data element, document, photo, etc.) to complete a custom form/document or report.

534 Solution must provide the ability to attach multiple documents and/or objects retrieved from both within the solution and from external systems to a completed custom form/document/report.

535 Solution must allow editing of a system generated documents and forms when necessary.

536 Solution must include an inventory of currently available solution reports that can be adapted for court use. An example of each existing solution report must be provided as a proposal attachment referencing this requirement.

537 Solution must allow the court to build new reports from or alter existing solution provided reports without solution vendor assistance.

538 Solution vendor must ensure the data elements required to generate and deliver (e.g., print, email, file transfer) the following commonly generated court forms/documents are captured and maintained by the proposed solution. Additionally, the proposed solution’s forms/document generation product must be capable of producing

Mike Geerken and Seann Halligan to provide the most commonly 10 to 20 forms/documents to be produced by the solution.

Seann provided 10 court forms and documents. Need

CDC CMS RFI Page 43 of 48 September 20, 2023

Page 44:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentsthe forms/documents in the same format as the examples provided in Attachment A-2.

1. Bail Order2. Domestic Stay Away3. Firearm Transfer to Sheriff4. Personal Surety Bond5. Plea Felony6. Plea Misdemeanor7. Plea Multiple Offender8. Release of Property9. State of Louisiana Uniform Commitment Order10. Transfer Order Form

Magistrate and Clerk forms.

Need example of each form/document.

539 Solution must provide the ability to analyze and report on court events using the following analysis options, including but not limited to: Trend analysis Frequency analysis (e.g., analysis with only one variable) Spatial analysis (e.g., analysis by user-defined geographical area) Time analysis (e.g., by time, date, date range, etc.) Link analysis (e.g., relationship between non-key related fields) Comparative analysis (e.g., changes over time) Simple relational analysis (e.g., relationships between two data

fields) Complex relational analysis (e.g., relationships among three or

more data fields).540 Solution must provide the ability to present data and statistics in

graphical formats, including but not limited to: Pin maps Density maps Bar graphs Line graphs Pie charts

CDC CMS RFI Page 44 of 48 September 20, 2023

Page 45:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments Link charts Relational maps

541 Solution must provide the ability to display photos in link charts.542 Solution must provide the ability to save and/or print the output of an

analysis.543 Solution must provide the ability to aggregate data by:

Date range Time of day Day of week Case type Charge type Event type Judge Other court-defined

544 Solution must provide the ability to aggregate data to create summary reports showing: Totals Averages Frequencies Percentages

545 Solution must provide the ability to generate reports comparing aggregate information over multiple years/time ranges.

546 Solution must provide secure, view-only access to court records via the internet for staff, external case participants, and the general public.

547 Solution Web search types (e.g., defendant name, case number, etc.) and search results must be configurable by the court.

548 Solution must provide user friendly searches using wildcard characters,

549 Solution must provide self-help for public users.550 Solution must support 100+ concurrent users via the Web Portal.551 Solution must allow the court to create an unlimited number of

integrations to other applications or partner agencies.

CDC CMS RFI Page 45 of 48 September 20, 2023

Page 46:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments552 Solution must implement the real-time exchange of data with external

Orleans Parish and Louisiana state justice agencies using either the Crossflo Data Integration Software product currently implemented in the City or a new ESB solution being evaluated by City IT. Solution provider will be required to work hand-in-hand with City IT and the Orleans Parish Criminal District Court to implement all needed CDC data exchanges. Required data exchanges are identified below.

Mike to provide data exchange / interface specifications. Listed below are the data exchanges / interfaces discussed.

553 Orleans Parish Sheriff Office Jail Management System (inbound/outbound)

554 Municipal Court DigiCourt System (inbound/outbound)555 Orleans Parish District Attorney Office (inbound/outbound)556 Orleans Parish Public Defender Office (inbound/outbound)557 CourtNotify Subpoena Management (outbound)

vendor: Orion Communications Inc., https://www.orioncom.com558 Louisiana Supreme Court (outbound)559 Louisiana Department of Corrections CAJUN System (outbound)560 CASTNet Interface (outbound)

Note: CASTNet is a SOAP-enabled Request-Reply Web Service that updates and returns criminal history information. A SOAPUI project will be provided to the successful solution provider.

561 CloudGavel eWarrant Solution (inbound)https://cloudgavel.com

Note: CloudGavel API specifications will be provided to the successful solution provider.

562 New Orleans Police & Justice Foundation (NOPJF) Data Exchange Server (outbound)

Note: The current exchange of information is achieved by replicating tables from the AS400 CMS. Solution provider will be required to work with NOPJF to implement a new interface and assist NOPJF to map the data to current jobs.

563 Solution provider must provide hourly rates in the Cost Proposal that

CDC CMS RFI Page 46 of 48 September 20, 2023

Page 47:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Commentswill be used for additional data exchange implementations that may be identified during the CMS implementation.

564 Solution provider must provide data migration services for all existing court case management data to new solution. Current database is DB2 for I Series hosted on an IBM I Series Machine (Type 8202 Model E4C).

As of 12/1/2019 there are ?? GB of CMS data.

Mike to provide CDC CMS database size.

565 Solution provider must provide costs and timeframes associated with data and document migration. Solution provider must agree to complete all data and document migration before the go-live date for the new solution.

566 Solution vendor must provide sufficient detailed training to allow court project team to participate in the solution configuration process, thus reducing overall project costs to the court. In particular, solution vendor must provide instruction on configuring screens, configuring workflow processes, building and validating business rules, creating and managing form/document/notification templates, creating custom and ad-hoc reports, and administrating the solution.

567 Solution vendor must provide on-site training for 100 users to be designated by the court and Clerk’s Office.

568 Solution vendor must provide detailed training plans.569 Solution vendor must provide a detailed training schedule prior to

solution implementation.570 Solution vendor must provide solution Administrator and User

Manuals in Microsoft Word format to guide users in the operation and of the solution.

571 Solution vendor must provide solution training videos to be used for refresher training and the training of new employees.

572 Solution User Manuals and training videos must be accessible from within the solution to facilitate ease of use and solution problem resolution.

573 Solution must provide a training/practice database, independent of the actual solution database, for training purposes.

CDC CMS RFI Page 47 of 48 September 20, 2023

Page 48:  · Web viewSolution vendor must provide solution Administrator and User Manuals in Microsoft Word format to guide users in the operation and of the solution. Solution vendor must

Attachment A – Draft CMS Requirements

Req. # Description Comments574 Solution vendor must provide regular training opportunities through

webinars, user conferences, newsletters, etc. after Go-live.

CDC CMS RFI Page 48 of 48 September 20, 2023