Dostawa i wdrożenie Systemu Pom-CMC oraz Infrastruktury Sprzętowej dla Systemu Pom-CMC w ramach projektu „Pomorskie Centrum Medycyny Cyfrowej”, wraz z przygotowaniem gotowości integracyjnej do przyszłej wymiany danych z zewnętrznym Systemem Biobanku dla Szpitali Pomorskich Sp. z o.o.

Question: What is the contract timeline?

Context: Contract start date, end date, total duration, and any key milestones or phases mentioned. Return null if not stated.

The contract comes into effect on the date of its signing.

The total duration for Task 1a (System Pom-CMC) is up to 18 months from the date the agreement is concluded.

The total duration for Task 1b (Hardware Infrastructure) is up to 240 days from the date the agreement is concluded.

Key milestones and phases are outlined as follows:

For Task 1a (System Pom-CMC):

• Etap 0: Backlog, test plan, security plan, with deliverables including the Acceptance Protocol Stage 0 and Implementation Plan, to be completed within 30 days.
• Etap 1: Pre-implementation analysis, technical design, integration design (API contracts, mappings). Deliverables include the Stage 1 Protocol, Data Quality Report, Integration Readiness Report, source data catalog, mapping matrix, and a list of integration risks and technical workarounds, to be completed within 60 days.
• Etap 2: Core implementation, environment launch (TEST/UAT/PROD), SSO/RBAC/audit, and on-premise mechanisms. Deliverables include the Stage 2 Protocol and a functional SAT Report, to be completed within 210 days.
• Etap 3: Integrations, data feeds, initial reports/feasibility, and integration tests. Deliverables include the Stage 3 Protocol, integration test report, end-to-end test report, and confirmation of mappings, validation rules, and data feeding mechanisms, to be completed within 360 days.
• Etap 4: User Acceptance Testing (UAT), training, Go-Live, post-implementation documentation, and IP/artifact transfer. Deliverables include the Go-Live Protocol, Training Protocols, and Documentation/runbook, to be completed within 540 days.

The maximum duration for Stages 1-4 is 18 months from the agreement date.

For Task 1b (Hardware Infrastructure):

• Etap A: Equipment delivery, BOM and serial number verification, and authorized channel. Deliverables include the Delivery Protocol, BOM/serials, and authorization statements, to be completed within 120 days.
• Etap B: Physical installation, basic configuration, integration with IT requirements, and network segmentation. Deliverables include the Installation Protocol, configurations, and basic documentation, to be completed within 180 days.
• Etap C: FAT/SAT tests, performance test, and backup/restore/DR smoke test. Deliverables include the FAT/SAT Report and Backup/restore test report, to be completed within 210 days.
• Etap D: Post-completion documentation, admin training, and handover for operation. Deliverables include the Final Acceptance Protocol, runbook, and training protocol, to be completed within 240 days.

• Structural methodology
• Object-oriented methodology
• Entity-Relationship Diagram (ERD)
• Data Flow Diagram (DFD)
• UML (Unified Modeling Language)
• API (Application Programming Interface)
• SDK (Software Development Kit)
• Python (for AI/ML, analytical models)
• R (for AI/ML, analytical models)
• Notebooks (for AI/ML, analytical models)
• FHIR (Fast Healthcare Interoperability Resources)
• CDA (Clinical Document Architecture)
• JSON (JavaScript Object Notation)
• XML (Extensible Markup Language)
• CSV (Comma Separated Values)
• ICD-10 (International Classification of Diseases, 10th Revision)
• ICD-9 (International Classification of Diseases, 9th Revision)
• ATC (Anatomical Therapeutic Chemical Classification System)
• EAN (European Article Numbering)
• LOINC (Logical Observation Identifiers Names and Codes)
• SNOMED CT (Systematized Nomenclature of Medicine - Clinical Terms)
• Data partitioning (for databases)
• B-tree indexes (for databases)
• Bitmap indexes (for databases)
• Enterprise-class ETL/ELT tool integration
• Unicode support (for databases)
• Polish code pages support (for databases)
• Contemporary 64-bit operating systems (Linux/Windows/Unix)
• ANSI/ISO SQL 2003 or newer
• High availability mechanisms (for databases)
• Replication mechanisms (for databases)
• Data encryption mechanisms (for databases)
• Backup encryption mechanisms (for databases)
• Data warehouse architecture (for databases)
• All-flash NVMe enterprise-class array (for storage)
• Scale-up storage architecture
• Scale-out storage architecture
• Distributed storage architecture
• Modular storage architecture
• ALUA (Asymmetric Logical Unit Access) multipathing support