tools and methods that provide the ability to generate information (e.g. reports, data sets, alerts, notifications) based on configurable rules applied against Technical Architecture - queried data (e.g. notify User X if # Reporting and Analytics of encounters exceed N), on Tools and Methods demand or scheduled. IV.O.12 Operations Phase - Must enable policies, rules, Business Information and operational logic, and related Technical Architecture - decisions to be defined, tested, Rules Engine & Rules executed, and maintained Management separately from application code. IV.O.12 Operations - Business Information and Must perform rules addition, Technical Architecture - deletion, and modification per State Rules Engine & Rules direction and approval without Management modifying the application code. Must support rules management IV.O.12 Operations - (rules addition, deletion, Business Information and modification and validation) in Technical Architecture - natural language, English-like Rules Engine & Rules syntax without the need to learn a Management specialized coding language. IV.O.12 Operations Phase - Business Information and Must provide the ability to clone Technical Architecture - rules, modify them and then Rules Engine & Rules implement them as new separate Management rules. IV.O.12 Operations Phase - Business Information and Technical Architecture - Must test, validate and receive Rules Engine & Rules State approval for rule changes Management prior to implementation. IV.O.12 Operations - Must provide the capability for Business Information and users to receive push Technical Architecture - notifications/alerts based on Rules Engine & Rules parameters (rules Management and/or rules groups). IV.O.12 Operations Phase - Must provide the capability to track Business Information and and report rule usage, exception
Technical Architecture - Reporting and Analytics Tools and Methods tools and methods that provide the ability to generate information (e.g. reports, data sets, alerts, notifications) based on configurable rules applied against queried data (e.g. notify User X if # of encounters exceed N), on demand or scheduled. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must enable policies, rules, operational logic, and related decisions to be defined, tested, executed, and maintained separately from application code. IV.O.12 Operations - Business Information and Technical Architecture - Rules Engine & Rules Management Must perform rules addition, deletion, and modification per State direction and approval without modifying the application code. IV.O.12 Operations - Business Information and Technical Architecture - Rules Engine & Rules Management Must support rules management (rules addition, deletion, modification and validation) in natural language, English-like syntax without the need to learn a specialized coding language. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the ability to clone rules, modify them and then implement them as new separate rules. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must test, validate and receive State approval for rule changes prior to implementation. IV.O.12 Operations - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for users to receive push notifications/alerts based on parameters (rules and/or rules groups). IV.O.12 Operations Phase - Business Information and Must provide the capability to track and report rule usage, exception
Revised%20Attachment%20B%20-%20Business%20and%20Technical%20Requirements%20Matrix.docx