Contratación de los Servicios de Desarrollo, Implantación, Soporte y Mantenimiento de la nueva aplicación para el programa de Detección Precoz de Cáncer de mama de Extremadura (SEYMA)

The contract has a total duration of 36 months. The estimated start date for the project is January 1, 2027.

The contract is structured into two distinct phases:

• Phase a) Development and Implementation: This phase has a maximum duration of twelve (12) months and includes activities such as analysis, design, development, integration, data migration, testing, training, and putting the application into production.
• Phase b) Support and Maintenance: This phase has a duration of twenty-four (24) months, commencing after the application goes live. It covers functional and technical support services, corrective, adaptive, and evolutionary maintenance, and actions to ensure the system's stability, operational continuity, and improvement in the production environment.

Key milestones with estimated timelines are as follows:

• Hito 1 (Functional analysis and solution definition): January 2027.
• Hito 2 (Functional and technical design): February 2027 - March 2027.
• Hito 3 (Solution development and implementation): April 2027 - July 2027.
• Hito 4 (Data migration, testing, and implementation): August 2027 - September 2027.
• Hito 5 (Go-live, training, and knowledge transfer): October 2027.
• Hito 6 (Initial stabilization of the system in production): November 2027 - December 2027.

The contract also allows for extensions. The end date is not explicitly stated as a calendar date in the provided documents, but it would be 36 months from the day indicated in the contract, with an estimated start date of January 1, 2027.

The core scope of work for this tender involves the comprehensive development, implementation, support, and maintenance of a new application called SEYMA, designed for the Early Detection Program for Breast Cancer in Extremadura.

The Statement of Work (SOW) outlines several key phases and deliverables:

Core Phases:

• Initial Planning: Includes the review and update of the initial work plan and the designation of interlocutors.
• Requirements Gathering and System Analysis: This phase focuses on reviewing and consolidating functional and non-functional requirements, identifying systems for interoperability, modeling and designing new processes, analyzing data, updating the project's scope, and identifying risks and dependencies. Mock-ups are presented to key users.
• Functional and Technical Solution Design: Involves the design of microservices, APIs, HL7/FHIR integrations, security, scalability, and detailed functional elements such as use cases, screens, validations, document management, reports, dashboards, alarms, and data models. This also includes the design of document templates for breast cancer screening, technical component design, and the data migration process. Navigable prototypes are presented to key users.
• System Development and Implementation: This phase covers the development of backend services (business logic, APIs, access control, auditing), frontend interfaces (screens, forms, navigation), integrations (HL7 channels, FHIR resources, adapters), task flow control, document management, statistical support, and the data migration process (scripts, ETLs). It also includes building automated and manual tests and configuring various environments (development, testing, pre-production, production) with CI/CD pipelines.
• Implementation and Production Rollout: This final phase includes presenting test plans, conducting functional and technical tests with real integrations, and presenting training and knowledge transfer plans.

Key Deliverables and Strategies:

• An executive summary of the project, detailing background, objectives, and the proposed technological solution.
• A preliminary project execution schedule, specifying phases, durations, milestones, and deliverables for each phase.
• A proposed work team, outlining responsibilities, dedication, and expected effort.
• A quality control plan.
• A specific data migration strategy.
• A testing strategy that defines test types and acceptance criteria.
• An implementation and production rollout strategy, including deployment procedures, pilot estimations, and a monitoring and stability plan.
• A support and maintenance plan, which includes the proposed model, Service Level Agreements (SLAs), and a knowledge transfer strategy.
• A proposed model for managing tasks outside of critical system operation hours.
• High-level functional design and a description of the proposed architectural model, standards, and frameworks.
• Regular reports to the SES on the service development and any encountered issues.
• Updated non-functional requirements at the project's commencement.
• A general list of tasks to be performed by the contractor.