Business Analyst / Data Integration Consultant

Job Description:

CONTRACTOR QUALIFICATIONS AND EXPERIENCE

5.1. A minimum of three years’ experience defining business processes for information technology solutions and conducting stakeholder interviews across multiple agencies/entities. 5.2. A minimum of three years’ experience evaluating business processes associated with information technology solutions.

5.3. A minimum of three years’ experience in delivering data architecture solutions to support secure data sharing, including privacy and security governance.

5.4. A minimum of three years’ experience developing, communicating, and collaborating with executive-level management stakeholders to develop business cases and business requirements documentation.

5.5. A minimum of three years’ experience documenting case management and interoperability requirements; mapping data sources and terminologies.

5.6. Demonstrated proficiency with data message mapping standards and specs (e.g., HL7/FHIR) and other approaches to data integration and data sharing.

5.7. A minimum of three years’ experience in verbal and written communications to convey project progress and results.

5.8. A minimum of three years’ demonstrated experience working with public health organizations.

5.9. Familiarity with mortality data or the death certification process.

DELIVERABLES:

Monthly: Provision of a feasibility study in the time and manner specified in Tasks 6.1.1. through 6.1.12.

6.1. SERVICE TASKS: Contractor will perform the following tasks in the time and manner specified: 6.1.1. As directed by the Department, provide a business analyst(s) and/or consultant(s) within five business days from purchase order (PO) issuance to perform the following tasks.

6.1.2. Meet with the Department within 10 business days of PO issuance to conduct a Project Commencement and Visioning meeting. Create meeting minutes and submit them to the Department Project Manager within five business days following the conclusion of the meeting. Include the following in the meeting minutes: 6.1.2.1. The date and time of meeting;

6.1.2.2. A list of attendees;

6.1.2.3. A summary of information discussed during the meeting; and

6.1.2.4. A list of action items including responsible party.

6.1.3. Develop, submit, and modify a project work plan as follows: 6.1.3.1. Develop a project work plan which documents key activities, tasks, owners, dependencies, milestones, success criteria, and work products for tasks listed in the scope of work as well as outlining the project schedule. Ensure the project work plan does not conflict with the tasks below. In the event of a conflict between this SOW and the project work plan, the SOW will control. Ensure the project work plan includes, at a minimum: 6.1.3.1.1. A timeline for creating and submitting the Requirements Report;

6.1.3.1.2. A timeline for creating and submitting the Implementation Plan;

6.1.3.1.3. A timeline for creating and submitting the data and integration strategy;

6.1.3.1.4. A timeline for creating and submitting the Architecture Analysis Report.

6.1.3.2. Submit the project work plan within 30 calendar days from issuance of the PO to the Department Contract Manager for the Department to review and approve.

6.1.3.3. As directed by the Department, meet with the Department to discuss the project work plan.

6.1.3.4. As directed by the Department, modify and resubmit the project work plan to the Department Contract Manager for the Department to review and approve.

6.1.3.5. Modify the project work plan as needed and submit the modified project work plan within 5 business days of the modification to the Department Contract Manager for the Department to review and approve.

6.1.4. As directed by the Department, conduct requirements gathering sessions with Department programs, ME Districts, toxicology laboratories, and other external partners as required by the Department.

6.1.4.1. As directed by the Department, coordinate with ME Districts and toxicology laboratories to understand their diverse data environments (e.g. commercial or homegrown case management systems/laboratory information systems) and necessary accommodation for differing technical capacities.

6.1.4.2. As directed by the Department, coordinate with ME case management system vendors and laboratory information system vendors to understand requirements to facilitate automated data transfer between and integration with various systems used by ME Districts, toxicology laboratories, and a new Department data sharing platform.

6.1.5. Create, submit, and modify a Requirements Report as follows: 6.1.5.1. Create a Requirements Report for the data sharing platform and submit it to the Department Contract Manager in accordance with the approved project work plan. Ensure the Requirements Report includes, at a minimum, the following: 6.1.5.1.1. Identify and prioritize use cases for the data sharing platform.

6.1.5.1.2. Define and document the functional, technical, security and privacy, and operational requirements that would be needed to support transmission and management of raw structured and unstructured case data from diverse ME District case management systems and facilitate data sharing with authorized external partners.

6.1.5.1.3. Identify requirements to enhance case tracking efficiency, improve the timeliness of data sharing between ME Districts and the Department, support coordination on multi-jurisdiction cases, and standardize data collection and reporting practices.

6.1.5.1.4. Identify additional processes and practices to be streamlined or eliminated to create efficiencies in data sharing and reporting.

6.1.5.1.5. Identify requirements for dashboarding and report functionality to visualize data within the data-sharing platform.

6.1.5.2. As directed by the Department, meet with the Department to discuss the Requirements Report.

6.1.5.3. As directed by the Department, modify and resubmit the Requirements Report.

6.1.6. As directed by the Department, conduct an assessment to determine the feasibility of a secure, scalable cloud-based platform to store, process, and manage data from ME District reports, files, and case management systems, considering existing Department resources, outlined requirements, and the ME data sharing environment.

Florida Department of Health Public Health Statistics & Performance Management Formal Scope of Work Public Health Medicolegal Death Investigation Data Optimization Initiative: Feasibility Study of an External Cloud-Based Data Sharing PlatformSOW26-157

6.1.7.Using the results of the assessment, as specified in Task 6.1.8., create the following as directed by the Department:

6.1.7.1.A data integration strategy for platform development as stated in 6.1.8.Submit the data integration strategy to the Department upon request.

6.1.7.2.A report that analyzes analysis of architectural requirements for platform development as stated in 6.1.9. Submit a copy of the report to the Department upon request.

6.1.7.3.An implementation plan that includes strategies and roadmapsforplatform development as stated in 6.1.10. Submit a copy of the implementation plan to the Department upon request.

6.1.8.Develop, submit, and modify a data and integration strategy as follows:

6.1.8.1.Develop a data and integration strategy, outlining the conceptual data model and metadata standards for data sharing and integration.Include, at a minimum, the following data and integration strategy:

6.1.8.1.1.Outline data mapping standards (e.g. HL7/FHIR)and other integration and transfer options(e.g. APIs, secure file exchange)that facilitate data sharing.

6.1.8.1.2.Outline required functionality forPDFparsing or optical character recognition to process PDF ME autopsy, toxicology, and investigative reports.

6.1.8.1.3.Outlinedata models, requirements and considerations for datadomains, and strategies for master data management ,deduplication, and linkage.

6.1.8.1.4.Draft data sharing agreement templates(e.g. DUA,MOU)that support data sharing between ME Districts, the Department, and other external partners.

6.1.8.2.Submit the data and integration strategy in accordance with the approved project workplan to the Department Contract Manager for review and approval.

6.1.8.3.As directed by the Department, meet with the Department to review the data and integration strategy.

6.1.8.4.As directed by the Department, modify and resubmit the data and integration strategy.

6.1.9.Create, submit, and modify an Architecture Analysis Report as follows:

6.1.9.1.Create an Architecture Analysis Report that compares architectural options and proposed solutions for the data sharing platform. Ensure the Architecture Analysis Report includes, at a minimum, the following:

6.1.9.1.1.An assessment of the Department’s Enterprise Data Analysis Platform (EDAP)and other cloud platforms (e.g., Azure, AWS, GovCloud)as options for building the data sharing platform, with consideration future integration of the data sharing platform with EDAP.

6.1.9.1.2.Considerations for identity and access management options.

6.1.9.1.3.An assessment of security risks and necessary mitigation strategies.

6.1.9.1.4.Totalcost estimates for at least two development scenarios of the data sharing platform, an outlined procurement strategy, including licensing and managed services, and estimated sustainability costs for maintaining the system.

6.1.9.2. Submit the Architecture Analysis Report in accordance with the approved project work plan to the Department Contract Manager for the Department to review and approve.

6.1.9.3. As directed by the Department, meet with the Department to discuss the Architecture