Appendix B7. Master Data Management Business and Technical Requirements Solicitation No.: YH Page 229

Transcription

1 aster Data anagement Business and Technical Requirements Solicitation No.: YH Page 229

2 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS B.7 ASTER DATA ANAGEENT The following sections identify the major requirements for key components of the master data management business areas. AZ HIX should support an efficient and robust master data management feature that will have the following key components: Consolidate and provide a single view of data across AZ HIX and all other solutions it will connect to Provide standardization and de duplication of data across the solutions Resolve data discrepancies across multiple solutions through the rules set by Arizona Allow easier search and identification of data records with probabilistic and partial match mechanisms anage the data through effective and efficient Data Collection Data Aggregation Data atching Data Transformation and Standardization Data Checking (QA) Data Storing Data Sharing NARRATIVE INSTRUCTIONS The aster Data anagement Requirements narrative must include the following: 1. How the solution meets all Federal guidance and requirements including the Seven Conditions and Standards and ACA Section Detailed description and diagrams, (if available) of the technical and database architecture for the solution 3. How the solution/service will integrate with AZ HIX based on the integration standards provided in the technical requirements. 4. A detailed description and diagrams, if available, of the technical and database architecture of the proposed solution, if appropriate for the Business Area 5. The State s engagement plan, including community and partner engagement. The State wants to understand how the Offeror team will be integrated with the AZ HIX project, what resource expectations and level of effort are expected and in what time frames. This State engagement plan should address proposed approach for project communication and administration. 6. The AZ HIX training plan which should address the types of materials and media to be provided, the specific training approach to be provided, engagement of users and time Page 230

3 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS required, ongoing support for training. The Offerors are expected to provide all training facilities and materials for their solution and will be responsible for communication and scheduling. 7. aintenance plan for this requirements area. Indicate whether upgrades are automatic or require additional programing for configurable or customized andatory requirements. This maintenance plan must be consistent with the technical requirements set forth for each business area included in this RFP. 8. Offeror insights and counsel to Arizona for this business area. aximum number of pages for aster Data anagement narrative section is three (3) pages. Page 231

4 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS B.7.1 ASTER DATA ANAGEENT BUSINESS AND TECHNICAL REQUIREENTS ATRIX INSTRUCTIONS Offerors must also complete the matrix below. Insert the primary Offeror Name in the heading and complete the columns for each requirement statement. Each of the Business and Technical Requirements are numbered and identified as andatory or. Instructions for responding to each requirement follow: a. For andatory Requirements (), the Proposal must always indicate explicitly whether or not the Offeror s proposed services meet the requirement. b. For requirements items, the Proposal must always indicate explicitly whether or not the Offeror's proposed services meet the requirement. The items must be priced separately from the mandatory items by Business Area in Appendix D, Pricing Template. Offerors may also provide additional functions and features in the table following the requirements table. These functions, features or services should only be included if they are provided by the Offeror at no cost to Arizona. [Reminder: Arizona is NOT seeking edicaid or other eligibility and enrollment functions, features or solutions. Arizona has an eligibility solution that will serve as the centerpiece of the Arizona HIX and that provides the Enterprise Service Bus that will facilitate integration of the solutions being requested in this proposal. Accordingly, proposals submitted that include eligibility and other operations not related to the solutions requested in this RFP may be eliminated as non compliant.] c. Arizona s strong preference is to have Offerors propose highly configurable solutions. Indications that a requirement is configurable will be rated higher than the non configurable items. Items that are client configurable will be given preference over Offeror configurable requirements. d. The Offeror shall provide a list of assumptions while responding to the functional, technical and operational requirements Complete the Business and Technical Requirements matrices below using the following instructions. andatory/ Offeror Response Pre filled Check the appropriate column using the following key. CC Client Configurable: Requirement is available and can be configured by the Client without Vendor support or involvement. VC Vendor Configurable: Requirement is available and can be configured by the Vendor. odifiable: Requirement is available and can be configured by the Vendor, but will require some level of modification. EE Expandable/Extensible: Software/Solution can be easily expanded or extended with a third party product to meet new requirements C Custom: Requirement is not available and would have to be customized for Arizona. NS Not Supported: Requirement is not supported and will not be modified or expanded to meet the requirement during this project. Enter. Each requirement must be in production and currently in use by a client. Offeror may include a brief statement as to whether it meets or exceeds each requirement; if the response is or C, indicate whether it will meet the required timeline. Include the cost of customization in the Financial Proposal/Pricing schedule. Page 232

5 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 1. The aster Data anagement solution shall be able to consolidate data across multiple solutions that will include AZ HIX and other solutions it connects to and provide a single view of data records 2. The aster Data anagement solution shall be able to standardize and de duplicate data across multiple solutions regardless of the data types and formats in which they are stored in those solutions 3. The aster Data anagement solution shall be able to integrate with and leverage ADES Common Client Index 4. The aster Data anagement solution shall be able to provide simple search and identification of data records 5. The aster Data anagement solution shall identify data records through probabilistic and partial search mechanisms with a toolset of solution rules and data based rules set by Arizona 6. The aster Data anagement solution shall allow Arizona to set match thresholds by source and use 7. The aster Data anagement solution shall support role based and agency based security access to the data 8. The aster Data anagement solution shall be able to resolve data discrepancies in the data received across multiple solutions based on the rules set by Arizona 9. The aster Data anagement solution shall be able to manage the data through effective and efficient Data Collection Data Aggregation Data atching Data Transformation and Standardization Data Checking (QA) Data Storing Data Sharing andatory/ or D CC VC EE C NS Page 233

6 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 10. The aster Data anagement solution shall be able to integrate with AZ HIX, and other AZ HIX related systems, and AZ HIX and participating agencies Data Warehousing solutions 11. The aster Data anagement solution shall provide manual override for authorized users to resolve improper matches (and mismatches) and preserve the override for that data record for future use 12. The aster Data anagement solution shall provide mechanisms for bulk processing of issues similar to Requirement No 11 above 13. The aster Data anagement solution shall provide mechanisms to upload existing data from multiple solutions regardless of the technology platform on which they operate 14. The aster Data anagement solution shall support data standards such as: NIE, HIPAA, HL7, XL, TIPS and any possible federal standards that may be required. 15. The aster Data anagement solution shall sync with the changes that happens to any of the data records on any of the participating solutions through both batch and real time mechanisms 16. The aster Data anagement solution shall provide an audit log [who, what, where, when, why] of all manual updates to data. 17. The aster Data anagement solution shall have the auditing mechanism to log and record the source of each activity related to the data including the distinct records that were used to arrive at the aster Record 18. The aster Data anagement solution shall maintain a historical record of all derived aster Records and associated detailed record 19. The aster Data anagement solution shall be able to resolve to one single record through multiple unique identifiers from different solutions 20. The aster Data anagement solution shall be able to provide fraud detection mechanisms andatory/ or D CC VC EE C NS Page 234

7 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements aster Data anagement Technical Requirements 1. The aster Data anagement solution shall have a Service Oriented Architecture (SOA) that is consistent with ITA 2. The aster Data anagement solution shall support common bidirectional interface modalities including generic web services or APIs 3. The aster Data anagement solution shall provide data extracts in multiple formats such as Excel, XL, flat file, CSV, a CD or DVD to support audit and reporting requirements 4. The aster Data anagement solution shall support the current version of NIE, XL, HL7, TIPS and HIPAA related transactions such as 820, 834 and 270/ The aster Data anagement solution shall have modular and reusable services and components 6. The aster Data anagement solution shall have a flexible architecture that can easily incorporate changes and new features 7. The aster Data anagement solution shall meet the Service Level Agreement (SLA) and other performance standards set by Arizona 8. The aster Data anagement solution shall meet the HIPPA, NIST, HITECH, FIPS and FIPs standards as required by ACA andatory/ or D andatory/ or D CC VC EE C NS CC VC EE C NS Page 235

8 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 9. The aster Data anagement solution shall be easily and seamlessly integrate with AZ HIX, Plan anagement, Plan Selection, SHOP, Appeals anagement, Data Warehousing and other solutions that are a part of the HIX solution in Arizona. The integration shall be done through the AZ HIX ESB. The Offeror shall work on the integration of their solution with the AZ HIX ESB during the pre implementation phases of this project.. Because of the fact that all the Federal requirements have not been finalized and available yet, there may be some future requirements that could require AZ HIX to have other supporting solutions. Hence Arizona wants the Offeror s solution to have the capacity to integrate with those solutions if necessary. 10. The State will continuously analyze the total AZ HIX solution (which includes the solutions in this procurement) for scalability and performance. This testing will include the specific AZ HIX components, including but not limited to the ESB. The State will conduct load, concurrency and other performance testing before implementation and on a regular basis after implementation. The Offeror shall participate in and cooperate with the State s conduct of these tests. Further, the Offeror shall work with the State in analyzing the scalability and performance of the AZ HIX and shall make all necessary changes to their solutions to achieve the performance levels identified in the Service Level Agreement as well as industry standard performance expectations as agreed to with the State of Arizona. These integrated tests should be in addition to regular and ongoing performance and scalability tests that the Offeror should conduct for each individual solution it provides to the State. The State will require monthly updates of performance tests conducted, production performance and changes made to improve results. 11. The solution must meet the maintenance schedule followed by AZ HIX (note: this will be scheduled in a way to minimize downtime for users). andatory/ or D CC VC EE C NS Page 236

9 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 12. The Offeror shall their solutions are provided on hardware that is current within three (3) years unless otherwise agreed to by the State. The Offeror s software should be current on all the patches and versions unless otherwise agreed to by the State. The Offeror will provide a monthly update of patches and other maintenance performed during the month. 13. The Offeror shall conduct testing to insure backward compatibility of its solutions and their integration with AZ HIX, It is expected that these tests will be conducted for any changes, upgrades to hardware or patches applied. 14. The Offeror shall follow the release schedules set forth in the SLA and otherwise established for the AZ HIX. 15. The Offeror shall work with AZ HIX team in advance of any release or change to allow AZ HIX team to adequately test, verify and train to support the smooth operation of AZ HIX and its supporting solutions. 16. The Offeror shall provide technical and help desk support for the aster Data anagement solution issues and questions based on the SLA set by Arizona 17. The Offeror shall provide access to their test and training environments for AZ HIX QA and Training team to ensure the correct implementation of changes before the changes are released to the production environment. 18. The Offeror shall provide version control management capability and integrate version control with the State s content management solution. All the changes to the solution shall reported and approved by the State, be maintained in the Offeror s version control management solution, which shall be available to the State for review and audit as needed. andatory/ or D CC VC EE C NS Page 237

10 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 19. The Offeror shall submit detailed documentation to the State on the following: Plan for maintaining the aster Data anagement solution Plan for keeping the aster Data anagement solution current on all the required patches and software versions and for working with AZ HIX team on following the same solution maintenance schedule as AZ HIX Plan for deploying changes to the aster Data anagement solution Testing requirements for changes in the aster Data anagement solution Plan for ensuring backward compatibility on changes Plan for working with AZ HIX team on integrating the changes into the aster Data anagement solution Plan for disaster recovery and business continuity Resource requirements from AZ HIX team Plan for the proposed integration with AZ HIX and its supporting solutions Detailed description of the technical and database architecture 20. The Offeror shall provide their current SSAE 16 certification for their solution and the hosting environment in which the solution will be hosted to the State of Arizona 21. The Offeror shall get their SSAE 16 certification for their solution and the hosting environment in which the solution will be hosted every year and provide that to the State of Arizona 22. The Offeror shall provide a solution that specifically addresses high availability, scalability, redundancy in order to meet the SLA set by Arizona andatory/ or D CC VC EE C NS Page 238

11 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS aster Data anagement Business Requirements 23. The Offeror shall have Disaster Recovery (DR) and Continuance of Operations Program (COOP) established for their solutions. The Offeror shall provide their DR and COOP plan and mechanisms to the State for each of their solutions as part of this submission. The DR and COOP mechanisms for the Offeror s solution shall meet the National Institute of Standards Technology (NIST) standards, 34 rev1/sp rev1_errata Nov pdf. 24. The Offeror shall host the solutions they are providing to the State unless alternative arrangements are made to host the Offeror s solutions on the AZ HIX cloud, in which case, the Offeror will be required to pay the proportionate share of the cloud set up and operating costs. The Offeror must inform the State in their response to this RFP which of the following options they are proposing to host their solutions: Offeror Hosted Offeror Cloud Hosting Participation in the AZ HIX Cloud If the solution is Offeror Hosted, the Offeror must meet the SSAE 16 audit requirements and submit the current SSAE with its proposal. If the Offeror chooses to host in a cloud environment of their own or participate in the AZ HIX cloud environment, the Offeror must meet the Federal security standards set for the cloud environments Cloud Computing Strategy.pdf. The Offeror shall include a detail hosting plan for each solution as well as evidence that they meet the SSAE 16 requirements and/or cloud computing requirements set forth above. andatory/ or D CC VC EE C NS Page 239

12 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS Additional Offeror Features Available to Arizona at NO cost a. b. c. d. In Production? How Long in Production? In Production for which Client? aster Data anagement Operational Services Requirements 1. The Offeror shall provide skilled resources to configure and implement the aster Data anagement solution for the AZ HIX 2. The Offeror shall provide skilled resources for ongoing maintenance of the aster Data anagement solution. The resources shall be onsite in Arizona and work on the data issues as well as other activities as directed by the State 3. Then Offeror shall have a regular process as directed by Arizona to monitor data errors and discrepancies and resolve them based on the rules defined by Arizona 4. The aster Data anagement solution shall provide regular ongoing reports on data errors and mismatches as directed by Arizona to support further analysis of the issues 5. The Offeror shall be responsible for making changes to the aster Data anagement process to accommodate new data elements that may be added to AZ HIX 6. The Offeror shall employ a mechanism to conduct regular data quality assessment as directed by Arizona 7. The Offeror shall have continuous monitoring and make ad hoc and on demand adjustments [to support the nature of issues associated with health care agencies] to staffing, equipment and other infrastructure that are required to handle unexpected changes of needs 8. The Offeror shall provide services in compliance with the HIPAA and HITECH requirements 9. The Offeror shall provide a complete turn key solution that will include hardware, software and services andatory/ or D D CC VC EE C NS Page 240

13 OFFEROR NAE: ASTER DATA ANAGEENT REQUIREENTS Page 241