Design, Development, Testing, Implementation, and Maintenance of the Digital Health Information Warehouse for Secondary Data Use for the Ministry of Health and Mass Media, Sri Lanka
UNOPS
Design, Development, Testing, Implementation, and Maintenance of the Digital Health Information Warehouse for Secondary Data Use for the Ministry of Health and Mass Media, Sri Lanka
Request for proposal
Reference:
RFP/2026/61959
Beneficiary countries or territories:
Sri Lanka
Registration level:
Basic
Published on:
25-Mar-2026
Deadline on:
20-Apr-2026 11:30 0.00
Description
Design, Development, Testing, Implementation, and Maintenance of the Digital Health Information Warehouse for Secondary Data Use for the Ministry of Health and Mass Media, Sri Lanka
The United Nations Office for Project Services (UNOPS) is an operational arm of the United Nations that provides project management, procurement, and infrastructure support. Through its project services — including infrastructure, procurement, project management, human resources, and financial management services — UNOPS supports governments, the United Nations, and other partners in achieving Member States’ Global Goals, and local objectives for people and countries.
The Health Information and Quality Improvement Project (HIQIP) is a major initiative implemented by the Ministry of Health as the Principal Recipient of a grant from the Federal Government of Germany and managed by the Global Fund to Fight AIDS, Tuberculosis and Malaria (GFATM). The project focuses on strengthening health systems through integration and interoperability of health data systems, enhancing TB screening facilities, and building institutional capacity to improve the quality of healthcare services.
In 2022, the Ministry of Health of Sri Lanka, through the World Health Organization and Global Fund Support, commissioned the development of a National Digital Health Blueprint, Interoperability Plan, Capacity Development Plan and Procurement Plan. These plans were subsequently developed, along with a Roadmap for the execution of the National Digital Health Blueprint.
Considering the extensive nature of the National Digital Health Blueprint, a prioritization exercise has been undertaken to identify a ‘thin-slice' of it to be implemented during the HiQi / D2H project.
The purpose of this assignment is to hire a service provider for the Design, Development, Testing, Implementation, and Maintenance of the Digital Health Information Warehouse for Secondary Data Use for the Ministry of Health and Mass Media, Sri Lanka to ensure the successful and timely implementation of the Digital Health Platform (DHP) under the HiQi / D2H project.
-----
IMPORTANT NOTE: Interested vendors must respond to this tender using the UNOPS eSourcing system, via the UNGM portal. In order to access the full UNOPS tender details, request clarifications on the tender, and submit a vendor response to a tender using the system, vendors need to be registered as a UNOPS vendor at the UNGM portal and be logged into UNGM. For guidance on how to register on UNGM and submit responses to UNOPS tenders in the UNOPS eSourcing system, please refer to the user guide and other resources available at: https://esourcing.unops.org/#/Help/Guides
Interested in improving your knowledge of what UNOPS procures, how we procure and how to become a vendor to supply to our organization? Learn more about our free online course on “Doing business with UNOPS” here
The United Nations Office for Project Services (UNOPS) is an operational arm of the United Nations that provides project management, procurement, and infrastructure support. Through its project services — including infrastructure, procurement, project management, human resources, and financial management services — UNOPS supports governments, the United Nations, and other partners in achieving Member States’ Global Goals, and local objectives for people and countries.
The Health Information and Quality Improvement Project (HIQIP) is a major initiative implemented by the Ministry of Health as the Principal Recipient of a grant from the Federal Government of Germany and managed by the Global Fund to Fight AIDS, Tuberculosis and Malaria (GFATM). The project focuses on strengthening health systems through integration and interoperability of health data systems, enhancing TB screening facilities, and building institutional capacity to improve the quality of healthcare services.
In 2022, the Ministry of Health of Sri Lanka, through the World Health Organization and Global Fund Support, commissioned the development of a National Digital Health Blueprint, Interoperability Plan, Capacity Development Plan and Procurement Plan. These plans were subsequently developed, along with a Roadmap for the execution of the National Digital Health Blueprint.
Considering the extensive nature of the National Digital Health Blueprint, a prioritization exercise has been undertaken to identify a ‘thin-slice' of it to be implemented during the HiQi / D2H project.
The purpose of this assignment is to hire a service provider for the Design, Development, Testing, Implementation, and Maintenance of the Digital Health Information Warehouse for Secondary Data Use for the Ministry of Health and Mass Media, Sri Lanka to ensure the successful and timely implementation of the Digital Health Platform (DHP) under the HiQi / D2H project.
-----
IMPORTANT NOTE: Interested vendors must respond to this tender using the UNOPS eSourcing system, via the UNGM portal. In order to access the full UNOPS tender details, request clarifications on the tender, and submit a vendor response to a tender using the system, vendors need to be registered as a UNOPS vendor at the UNGM portal and be logged into UNGM. For guidance on how to register on UNGM and submit responses to UNOPS tenders in the UNOPS eSourcing system, please refer to the user guide and other resources available at: https://esourcing.unops.org/#/Help/Guides
Interested in improving your knowledge of what UNOPS procures, how we procure and how to become a vendor to supply to our organization? Learn more about our free online course on “Doing business with UNOPS” here
This tender has been posted through the UNOPS eSourcing system. / Cet avis a été publié au moyen du système eSourcing de l'UNOPS. / Esta licitación ha sido publicada usando el sistema eSourcing de UNOPS. Vendor Guide / Guide pour Fournisseurs / Guíra para Proveedores: https://esourcing.unops.org/#/Help/Guides
First name:
N/A
Surname:
N/A
This procurement opportunity integrates considerations for at least one sustainability indicator. However, it does not meet the requirements to be considered sustainable.
Gender issues
Social
The tender contains sustainability considerations addressing gender equality and women's empowerment.
Examples:
Gender mainstreaming, targeted employment of women, promotion of women-owned businesses.
| Link | Description | |
|---|---|---|
| https://esourcing.unops.org/#/Help/Guides | UNOPS eSourcing – Vendor guide and other system resources / Guide pour fournisseurs et autres ressources sur le système / Guía para proveedores y otros recursos sobre el sistema |
81111501
-
Mainframe software applications design
New clarification added: Clarification No: 07Question:Q1: From the TOR the business analyst needs a Bachelor’s degree in business administration, IT, engineering, computer science or a related discipline. Is any engineering degree valid as long as the candidate has relative experience as a business analyst in the ICT sector?Q2: For integration Engineer, a Bachelor’s degree in Computer Science, Software Engineering or a related discipline is required, what disciples are considered related? If a candidate doesn't have a related bachelor degree but has a master in information systems and relevant experience, can they still be applied for the Integration role?Q3: What is the expected start date of this project?Q4: Is computer engineering or electrical and electronics engineering valid for a data scientist Response: Q1/Q2/Q4 The educational qualification requirements identified as minimum for key personnel in the Schedule of Requirements are considered minimum requirements.The determination of whether a degree in a particular discipline is considered “related” will be made on a case‑by‑case basis. This assessment will include (but is not limited to) reviewing the curriculum of the degree program and its relevance to the requirements outlined in the Schedule of Requirements. Offerors may be required to submit additional documentation to justify the relevance of the discipline.Q3: As set out in tender particulars sections, the Expected contract award date is 2026-05-29
Edited on:
13-Apr-2026 16:09
Edited by:
webservice@unops.org
New clarification added: Clarification 06QuestionsOur understanding: Multiple systems (HHIMS, EMRs, registries) exist. Can you confirm total number of systems?Our understanding: Mixed standards. What % are FHIR/HL7 compliant vs proprietary?Our understanding: Near real-time (<15 min). Should ingestion be streaming, batch, or hybrid?Are event-based integrations available or should polling be assumed?Our understanding: TRE required. Will external researchers be allowed access?What are data export controls in TRE?Our understanding: Consent required. Is there centralized consent management?How should consent revocation propagate across systems?Our understanding: CI/CD required. Who owns DevOps pipelines?Our understanding: DHIS2 used. Integrate existing or deploy new?What is total population size and expected TPS/RPS?What is annual data growth and retention period?What infra will be provided (on-prem/cloud/hybrid)?Is Kubernetes available or required to provision?Who manages cross-bundle integration and SLAs?Who owns raw, curated, and analytical data?Is there a defined data stewardship model?What is data quality and standardization level?What are uptime, response time SLAs?How is consent managed across systems?Expected number of dashboards and users?What is rollout strategy (pilot vs national)?Is HSM/key management required?Are there DR/backup RPO/RTO requirements?Are API gateways standardized nationally?Are master patient identifiers standardized?Are audits/reporting mandatory to regulators?Are KPI catalogs predefined or to be created?Is internet access allowed for research environments?What support model and SLA post go-live?Response:Q01. Multiple systems (HHIMS, EMRs, registries, surveillance systems) exist; exact count is not fixed and evolving, and architecture must support integration with a heterogeneous and expanding system landscape.Q02. A mixed standards environment exists, with increasing adoption of FHIR/HL7, but limited number of legacy systems could remain proprietary; interoperability layer must handle both.Q03. A hybrid ingestion model is required: event-driven (near real-time) plus batch ingestion for legacy systems.Q04. Event-based integration (via NHDX/FHIR) is expected where available; polling or batch extraction should be supported.Q05. Yes. External researchers may access data within governed TRE environments, subject to approval, agreements, and de-identification, with explicit MoH authorisation.Q06. TRE must enforce strict export controls, including approval workflows, output checking, and prevention of raw data extraction. Q07. Centralized consent management is planned but not fully implemented; systems must support integration with future consent services.Q08. Consent revocation must propagate via central governance mechanisms and APIs, ensuring downstream systems restrict further use.Q09. Contractor maintains the CI/CD pipelines for components developed under this bundle; must integrate with and leverage Platform Support Services bundle (DevOps, monitoring, etc.); all artefacts in MoH-designated repo.Q10. Existing DHIS2 deployments should be integrated where applicable; new deployments only if justified.Q11. Must be designed for national scale (~20–25 million population) with scalable TPS/RPS, though exact figures may not be predefined.Q12. System must support high annual data growth and long-term retention, aligned with national policy and legal requirements.Q13. Infrastructure will be primarily Ministry of Health Data Centre with potential hybrid integration.Q14. Kubernetes may not be pre-provisioned; vendor should be prepared to deploy or adapt to available orchestration environments. Huawei DCS virtualization platform powers the MoH DC.Q15. Integration and SLA alignment are managed via programme-level governance and architecture oversight.Q16. Data ownership resides with Ministry of Health, across all layers (raw, curated, analytical).Q17. A data stewardship model is required, with defined roles for ownership, quality, and governance.Q18. Variable; requires significant standardization and validation pipelines using FHIR and national standards.Q19. SLAs will define high availability, response times, and performance thresholds, aligned with national ICT standards.Q20. Consent must be managed via centralised or federated mechanisms, integrated across systems via APIs.Q21. Not fixed; system should support multiple dashboards and diverse user groups (national, provincial, facility-level). Identified use cases would define this, and the system must scale to accommodate dashboards created by MoH staff.Q22. Likely phased rollout (pilot → scale to national).Q23. Yes. Secure key management (HSM or equivalent) is required for data protection.Q24. Offsite DR is available with replication of identified VMs at defined intervals. RTO/RPO within 1 hour could be acceptable for secondary use cases.Q25. Yes. NHDX/NDX acts as the national API gateway layer.Q26. Yes. MPI (Master Patient Index) provides standardized patient identification.Q27. Yes. Audit logging and reporting are mandatory, including regulatory oversight. Integration with the audit repository (under Platform Support Services bundle) for key events is required.Q28. KPI catalog may be partially defined but must be expanded and governed during implementation.Q29. Likely restricted or controlled, with whitelist/proxy mechanisms in TRE environments.Q30. Post go-live support must include defined SLAs, maintenance, monitoring, and incident management processes.
Edited on:
12-Apr-2026 09:13
Edited by:
webservice@unops.org
New clarification added: Clarification No: 05 (B)Questions: 29. Support : Kindly confirm detailed SLA expectations beyond critical issue resolution timelines.30. Evaluation : Please clarify the evaluation methodology and weightage of technical versus financial proposals.31.Dependencies : Kindly confirm how delays or dependencies related to other vendors will be managed.32.Eligibility / Local Presence : Kindly clarify whether it is acceptable for the bidder to establish a local office in Sri Lanka after contract award, in compliance with regulatory requirements, instead of having a pre-existing local registration at the time of bid submission.33.FHIR Standards : Kindly clarify whether national HL7 FHIR profiles, value sets, and implementation guides are already defined and available.34.Data Volume : Kindly provide indicative data volumes (daily ingestion, number of facilities, records).35.Data Quality : Are there predefined data quality rules or validation frameworks to be followed?36.Historical Data : Kindly clarify whether migration of historical data is in scope and expected data volume.37.Terminology Services : Please confirm if a centralized terminology service exists or is expected to be implemented.38.MDM Responsibility : Kindly clarify whether Master Data Management (e.g., patient matching) is handled by registries or within this scope.39.Data Lake : Is implementation of a data lake mandatory, or can the architecture be optimized based on use cases?40.Identity Management : Kindly confirm availability of centralized IAM/SSO for integration.41.Data Privacy : Are there specific PDPA implementation guidelines or anonymization standards to be followed?42.KPI Governance : Kindly clarify ownership and change management process for KPIs post-implementation.43.Data Access Workflow : Please clarify approval workflow and governance model for researcher access in TRE.44.Infrastructure : Kindly confirm infrastructure provisioning (compute, storage, network) by MoH.45.DR Requirements : Please confirm Recovery Time Objective (RTO) and Recovery Point Objective (RPO).46.Dependency Risk : Kindly clarify how delays from other DHP vendors will be managed in project timelines.47.Consortium vs Lead Bidder : Kindly clarify whether eligibility criteria (financial, technical, and experience) must be fully met by the lead bidder alone, or can be collectively satisfied through a consortium/joint venture arrangement48.Upstream Systems : Please confirm the availability timeline and readiness of NEHR, NHDX, and registries for integration.Response: Q29. SLAs will include response/resolution times, availability targets, and support coverage.Q30. As set out in the tender particulars - Weightage of technical and financial proposals : 70% (Technical) : 30% (Financial), Minimum points for technical compliance: 70%. Please also refer Evaluation method details under tender particularsQ31. Programme-level governance will manage cross-vendor dependencies and escalation.Q32. As set out in the eligibility criteria the Offeror should be legally registered and operate in Sri Lanka or authorized to operate within its jurisdiction for software development related activities. Proof of registration is required.Q33. FHIR standards will be aligned nationally but may evolve, requiring vendor flexibility.Q34. Systems must support large-scale national data volumes, though exact figures may not be predefined.Q35. Data quality rules must be implemented using national standards and validation pipelines, though exact framework may not be predefined.Q36. Historical data migration may be required selectively, depending on use cases and availability.Q37. A centralized terminology service is procured under NEHR bundle, aligned with standards (ex: SNOMED-GPS, ICD).Q38. Master Data Management (e.g., patient identity) is handled by registries (MPI), not DHIW.Q39. Data lake implementation is not mandatory; architecture may be optimized based on use cases.Q40. Centralized IAM/SSO is expected as part of DHP architecture under the Platform Support Services bundle.Q41. Must comply with PDPA, including anonymization, pseudonymization, and consent frameworks.Q42. KPI ownership and change management will be governed by MoH-led processes.Q43. Access will follow formal approval workflows with governance oversight and auditing.Q44. Infrastructure will be provisioned via the Ministry of Health Data Centre co-located in a National Tier III data centre.Q45. Offsite DR is available with replication of identified VMs in given intervals. RTO/RPO with in 1 hour could be acceptable for secondary use cases.Q46. Risks will be managed through programme governance and escalation mechanisms.Q47. Please also refer Evaluation method details under tender particularsWhen a joint venture, consortium or association submits an offer:The proposal documents must be submitted in the name of the leading partner. The duly filled Form A: Joint Venture Partner Information Form , copies of business registration for each of the partners, copies of the audited financial statements for the last three (3) years prior to the deadline for proposal submission for each of the partners, duly filled returnable Form F: Performance Statement Form for each of the partners, must be submitted as part of the proposal.The following evaluation method shall be applied:Each joint venture/consortium/association member must meet formal & eligibility criteria #1 & 5 and qualification criteria #1Lead partner of joint venture/consortium/association must meet formal & eligibility criteria # 3All joint venture/consortium/association members combined must meet all other criteriasQ48. NEHR, NHDX, and Registries are part of parallel DHP bundles and are expected to be developed concurrently, with phased availability; full dependency alignment is required during implementation.
Edited on:
12-Apr-2026 08:54
Edited by:
webservice@unops.org
New clarification added: Clarification No: 05 (A)Questions:1. Digital Health Platform : Kindly clarify the current implementation status and availability timelines of other DHP components such as NEHR, Registries, and NHDX.2. DHP Components : It would be helpful to understand whether all upstream systems will be available during the implementation phase or developed in parallel.3. Purpose of Assignment : Kindly confirm if any prioritized list of secondary data use cases or KPIs is available for initial implementation.4. Data Ingestion : Could the Authority provide indicative data volumes and number of source systems expected to be integrated?5. Technology Stack : Please clarify whether DHIS2 is mandated for DHIW or if equivalent FOSS-based alternatives can be proposed.6. Standards : Kindly confirm if national HL7 FHIR profiles or implementation guides are already defined and available.7. Compliance : It would be helpful to understand if specific PDPA implementation guidelines or templates are available.8. KPIs & Reporting : Kindly provide clarification on expected KPI definitions and reporting frequency for initial dashboards.9. Scope of Work : Please clarify the expected level of customization versus configuration for proposed FOSS components.10.Stakeholder Engagement : Kindly confirm the level of support from MoH in coordinating stakeholder workshops and consultations.11.Advocacy Conference : It would be helpful to understand the extent of logistical or administrative support, if any, to be provided by MoH for the conference.12.Integration : Kindly confirm the availability of APIs for NEHR, NHDX, and registries for integration and testing.13.Sandbox : Please clarify whether a centralized sandbox environment will be provided or is expected to be established by the vendor.14.Data Sources : It would be helpful if sample datasets or schemas for key source systems could be shared.15.Testing : Kindly confirm if there are predefined national testing standards or certification requirements (e.g., SLCERT).16.Deployment : Please clarify the infrastructure (compute, storage, network) that will be provisioned by MoH.17. DevOps : Kindly confirm if there is any preferred DevOps or CI/CD toolchain within the existing ecosystem.18.TRE : It would be helpful to understand if there are specific accreditation or compliance requirements for the TRE.19.Intellectual Property : Kindly clarify whether reusable generic components developed during the project can be used in future implementations.20.Open Source : Please confirm if there are any restrictions or preferred licenses for FOSS components.21.Inputs from MoH : Kindly confirm the availability of dedicated MoH technical and functional resources for coordination and approvals.22.Data Access : Please clarify the process and expected timelines for obtaining access to required data sources and systems.23.Eligibility : Kindly confirm whether consortium or joint venture submissions are permitted.24.Experience : Please clarify if multiple projects can be combined to meet experience requirements.25.Team Deployment : Kindly confirm whether key personnel are required to be fully on-site or if a hybrid deployment model is acceptable.26.Timeline : Please confirm if there is any flexibility in the 30-week timeline considering dependencies on other DHP components.27.Deliverables : Kindly clarify the acceptance criteria and approval process for deliverables and milestones.28.Payment : It would be helpful to understand the indicative milestone-based payment structure.Response: Q01/48. NEHR, NHDX, and Registries are part of parallel DHP bundles and are expected to be developed concurrently, with phased availability; full dependency alignment is required during implementation.Q02. Upstream systems will be developed in parallel, requiring the DHIW to support incremental integration and evolving interfaces.Q03. A predefined list may not be final; vendor must support use case prioritization and KPI definition through stakeholder engagement.Q04. Exact figures may not be fixed; architecture must support high-volume ingestion across multiple systems (NEHR, registries, HHIMS, eIMMR) with scalable design.Q05. DHIS2 is not strictly mandated; equivalent FOSS-based architectures may be proposed, provided they meet interoperability and standards compliance.Q06. National FHIR profiles may be under development or partially defined; vendors must support profile alignment and extension as needed.Q07. Some guidance may exist, but vendor is expected to develop detailed compliance artefacts (policies, templates, agreements) aligned with PDPA.Q08. KPIs will be defined collaboratively; reporting may include near real-time dashboards and periodic reporting (daily/monthly).Q09. Preference is for configuration-first using FOSS, with minimal custom development only where essential.Q10. MoH is expected to facilitate introductions and coordination, but vendor must lead execution of workshops and consultations.Q11. MoH likely provides strategic support and participation, while vendor manages logistics and execution.Q12. APIs (FHIR-based via NHDX) are expected, but may evolve during implementation, requiring flexible integration design.Q13. A central sandbox may be provided, but vendor should be prepared to establish local testing environments if required.Q14. Sample schemas or datasets may be partially available, but vendor should design based on standard models (FHIR, MCDS).Q15. Testing must align with national ICT and security standards, though specific certification processes may be defined later.Q16. Infrastructure will be provisioned via Ministry of Health DC virtualized environment , including compute, storage, and network resources.Q17. No strict mandate; vendor should implement modern CI/CD practices, compatible with infrastructure.Q18. TRE must comply with data privacy, security, and governance standards (ex., PDPA, NDHGS); formal accreditation may evolve.Q19. Reusable generic components are typically allowed for reuse, subject to government ownership/licensing terms as defined in the ToR.Q20. Preference for permissive FOSS licenses (e.g., Apache, MIT); restrictive licenses should be avoided.Q21. MoH will provide functional and technical counterparts based on availability, but vendor must drive delivery.Q22. Access will follow formal approval workflows, including governance checks and agreements; timelines may vary.Q23. As set out under tender particulars, If an offeror does not have all the expertise required for the provision of the Services described in the RFP, the offeror may submit a proposal in association with other entities, particularly with an entity in the country where the Services are to be provided.Q24. Yes, however as set out in the schedule of requirements and evaluation criteria & scoring document -overlapping or concurrent project periods will not be double-counted. For example, if two projects were executed simultaneously from January 2024 to June 2024, this will be considered as six (6) months of experience in total, rather than one (1) year.Q25. The proposed key personnel shall be deployed in Sri Lanka as required and specified in the schedule of requirements.Q26. Baseline expectation remains 30 weeks due to funding constraints.Q27. Deliverables will be accepted based on defined milestones, quality criteria, and MoH approvals.Q28. Please refer to the schedule of payments set out in the schedule of requirements.
Edited on:
12-Apr-2026 08:35
Edited by:
webservice@unops.org
New clarification added: Clarification 4(B)Questions: 21. Will MoH issue formal letters of introduction to all 60+ stakeholder organisations required for D2 consultation prior to contract commencement? Without these introductions, completing meaningful consultations within 8 weeks is extremely difficult.22. Is there a published national FHIR Implementation Guide (IG) for Sri Lanka? If yes, where is it published, what is its current version and publication status, and which profiles within it are mandatory for DHIW integrations with NEHR and NHDX?23. Regarding de-identification of free-text clinical content in health records: is full intelligent de-identification of all free-text fields a mandatory go-live requirement for D5, or is a phased approach acceptable? For example: Phase 1 applies complete suppression of free-text fields at go-live; Phase 2 implements intelligent de-identification during the warranty period once MoH-approved reference data is available. Or does MoH require free-text to be queryable (in de-identified form) at go-live?24. What are the expected data volumes at go-live — approximate number of FHIR resources currently in NEHR, estimated daily NHDX event volume, and approximate eIMMR record volume per month? This is required to size LGC infrastructure correctly in D1 and cannot be estimated without at least an order-of-magnitude figure from MoH.25. Can MoH share the eIMMR technical documentation — data model, indicator definitions, morbidity/mortality code set used, and any existing API or data export capabilities? This is essential for designing the Pattern C integration in D1.26. What is the current eIMMR data submission workflow from hospital to national level? Is data entered directly into eIMMR by hospital staff, or does it pass through an intermediate aggregation step? This determines the integration design.27. Is there a test or staging eIMMR environment available for the vendor to develop and validate the Pattern C integration against, without affecting live reporting workflows?Responses:Q21. MoH will provide official letters when requiredQ22. Current IGs are available through https://ig.hiu.lk/Q23. Policy-driven and consultation-based; Phased approach likely acceptable but not confirmed.Q24. No estimates availableQ25. Specific documentation not available.Q26. Currently majority of eIMMR data entry is through it’s own user interface with limited integration with selected HHIMS systems.Q27. Currently not available.
Edited on:
12-Apr-2026 06:45
Edited by:
webservice@unops.org
New clarification added: Clarification No: 04 (A)Questions: 1. Does LGC provide GPU-capable virtualisation nodes that support GPU passthrough to VMs? If yes, what GPU models are available (A10, V100, T4, or equivalent), and how many vGPUs can be allocated to a single project namespace?2. What storage provisioning model does LGC provide — dedicated physical storage nodes with direct-attached disks, or only shared virtual disk allocations from a central SAN/NVMe pool? What is the maximum storage capacity and IOPS available per project namespace?3. What is the virtualisation hypervisor used on LGC — Huawei FusionSphere/FusionCompute (Huawei DCS) or Proxmox VE? Which version is currently in production?4. What is the maximum VM specification available per project? Specifically: maximum vCPU count, RAM ceiling, storage quota (per VM and total project), and network throughput limits.5. Is there a Tier III DR site on LGC/LGN? What is the network connectivity and latency between the primary and DR zones? Can vendors configure async replication between them for PostgreSQL and object storage?6. Is Ubuntu 22.04 LTS an approved guest OS on LGC VMs? Is there a list of approved operating systems the vendor must select from?7.What is the outbound internet access policy for project VMs on LGC? Is there a whitelist/proxy mechanism, or are project namespaces fully isolated from the public internet?8. What NTP servers are available on LGC/LGN for time synchronisation? Is there a designated central time service provided through Bundle #3 (Platform Support Services)?9. What is the expected contract award and first delivery timeline for Bundle #2 (NEHR/NHDX/IdP)? Will Bundle #2 have a sandbox HAPI FHIR server operational for other bundle vendors to develop against before Bundle #2 reaches production?10.Will NHDX expose FHIR Subscription endpoints for Pattern A near-real-time streaming? Which FHIR R4 Subscription channel types will be supported — rest-hook, websocket, or both? Who owns and operates the NHDX FHIR Subscription infrastructure — GovTech or the Bundle #2 vendor?11. Will HAPI FHIR NEHR support FHIR Bulk Export ($export operation) from day one of production? What FHIR R4 resource types will be available for bulk export at go-live?12. Can Bundle #4 vendor establish a direct technical working relationship with the Bundle #2 vendor from contract start to agree FHIR API contracts in writing? Is there a programme-level mechanism for this?13. What is the expected contract award date for Bundle #1 (Client/Provider/Facility Registries)? Is OpenCR Client Registry already operational, or is it part of Bundle #1 scope?14. Is there a programme-level integration manager or technical architect overseeing inter-bundle API design? If two bundle vendors have conflicting API requirements, what is the escalation path?15. What is the current operational status of the eIMMR system? Who is the technical owner within MoH? Can Bundle #4 vendor access eIMMR technical documentation, data model, and a test environment from contract start?16. The DHIW requires integration with HHIMS for clinical inpatient and outpatient data extraction. Which procurement or contract is responsible for providing FHIR-compatible data access to HHIMS data? Is this within the scope of RFP/2026/61684, a separate mechanism, or is HHIMS FHIR integration the responsibility of the DHIW vendor? What is the expected timeline for HHIMS FHIR data access to be available?17. Will MoH designate a PSErB Working Group or interim committee within the first month of contract commencement? D2 governance framework deliverables require a constituted governing body — without this, D2 cannot be finalised.18. Has MoH engaged the Personal Data Protection Authority (PDPA Authority) regarding the DHIW project? Has the PDPA Authority provided any preliminary guidance on what constitutes adequate pseudonymisation and valid public health or research exceptions under PDPA 2022 for this specific use case?19. Has the AG Department been briefed on the DHIW project? Is there an existing data sharing agreement template or framework that covers DHIW secondary data use, or does the vendor need to draft these instruments from scratch?20. For the 200-participant advocacy conference (mandatory D2 deliverable): will MoH provide the invite list and chair the event, or is the vendor expected to manage the full stakeholder convening process independently? What is MoH's role in agenda setting?Responses: Q1. DHP will not be hosted in the LGC and it will be in co-located servers in a tier III data centre. NO GPUs are currently availableQ2. Storage is shared SAN. With 100TB for all the DHP componentsQ3. Huawei FusionSphere (Huawei DCS) FusionCompute v8.8.0Q4. Will be allocated based on the requirements of each DHP component on shared basisQ5. DC will be in a Tier III datacentre. DR is setup in a Ministry of Health owned location with replication over ILI link Q6. You may deploy an appropriate guest OS on the provided VM with approval of the MoH.Q7. Secure environments are expected to have no default outbound internet with policy-based exceptions.Q8. NTP-based synchronisation expected; Bundle #3 (Platform Support Services) includes timekeeping service. Q9. Timeline not specified. Programme runs to Dec 2026. Sandbox environments are expected early but not guaranteed.Q10. Not specified. FHIR R4 APIs required but Subscription support (rest-hook/websocket) not confirmed. Will be provided as the project progress.Q11. Not specified. FHIR R4 required, bulk export will be controlled.Q12. Yes, collaboration required across bundles. The Specialist Support Services entity is to facilitate the activities between vendors.Q13. All registries are to be established under the common registry tender. No current implementation.Q14. Programme oversight exists (Specialist Support Services , Ministry of Health and UNOPSQ15. eIMMR is operational is owned by the Ministry of Health. Information will be shared to the selected vendorQ16. Any EMR Integrations (such as HHIMS integration) will be through the NHDX and will be done by a different vendor.Q17. Not plannedQ18. Vendor must engage PDPA Authority.Q19. Vendor required to develop agreements; No template available.Q20. Vendor must fully organise and fund the conference; MoH concurrence required. Invite list/agenda ownership not finalized.
Edited on:
12-Apr-2026 06:42
Edited by:
webservice@unops.org
New amendment added #1: Amendment 01Pre-proposal meeting minutes have been uploaded in the documents section
Edited on:
10-Apr-2026 18:04
Edited by:
webservice@unops.org
New clarification added: Clarification No: 03 Question 01: Kindly grant an extension due to complexity of this project.Question 02: To ensure we provide a comprehensive and highly competitive submission that fully addresses the technical requirements of this project, we would like to formally request two weeks extension of the submission deadline.Response:We will not be able to provide an extension to the bid submission deadline as there is a hard deadline for the grant that is funding this project.
Edited on:
07-Apr-2026 14:24
Edited by:
webservice@unops.org
New clarification added: Clarification No 02:Question:Is 18% VAT applicable for these? And you expect the BID with or without VAT?Response:As set out under tender particulars, All proposals shall be submitted net of any direct taxes such as customs duties and indirect taxes, such as sales taxes, VAT, taxes on commodities such as fuel.
Edited on:
01-Apr-2026 06:55
Edited by:
webservice@unops.org
New clarification added: Clarification No: 01Questions:Considering the New Year holiday week from 13th April to 17th April, we kindly request a one-week extension for the submission.We appreciate your understanding and look forward to your favorable response.Response:We will not be able to provide an extension to the bid submission deadline as there is a hard deadline for the grant that is funding this project.
Edited on:
27-Mar-2026 10:49
Edited by:
webservice@unops.org