Q1M1A1-Formalize collaboration agreements
Goal/Objective: Formalize collaboration agreements with participating healthcare providers and UNICEF teams. Verification Criteria: 2 agreements signed; documentation archived.
Q1M1A2-Establish governance structure
Goal/Objective: Establish governance structure and project communication channels. Verification Criteria: Governance matrix created; communication tools in active use by team.
Q1M1A3-Define legal framework for data
Goal/Objective: Define data responsibility agreements and legal framework for data handling and consent. Verification Criteria: 1 data responsibility framework signed; consent forms approved.
Q1M2A1-Configure Google Cloud Healthcare env
Goal/Objective: Configure Google Cloud Healthcare environment with HL7v2 support. Verification Criteria: GCP console shows HL7v2 service active; test messages successfully ingested.
Q1M2A2 Establish secure API gateway and IAM
Goal/Objective: Establish secure API gateway and IAM settings. Verification Criteria: API access tested with 3 user roles; access logs confirm role restrictions.
Q1M2A3-Automated infrastructure monitoring
Goal/Objective: Implement automated infrastructure monitoring and traceability using IaC. Verification Criteria: Scripts run successfully in test environment; versioned in Git.
Q1M3A1-Conduct technical audits of SIPs
Goal/Objective: Conduct technical audits of provider information systems (SIPs). Verification Criteria: Checklist completed; SIP data fields mapped.
Q1M3A2-Design HL7v2 data mapping architecture
Goal/Objective: Design architecture of HL7v2 data mapping and exchange logic. Verification Criteria: Validated by tech lead and healthcare informatics advisor.
Q1M3A3-Develop HL7v2 connector prototype
Goal/Objective: Begin development of first HL7v2 connector prototype for a selected pilot provider. Verification Criteria: Test messages transmitted from SIP to cloud and acknowledged.
Q1M4A1-Select and procure hardware
Goal/Objective: Select and procure initial batch of NFC wristbands and/or QR-enabled cards. Verification Criteria: 100 NFC/QR identifiers received and tested. Accuracy: 95% of scans must correctly resolve to the intended unique identifier.
Q1M4A2-Develop secure identifier encoding module
Goal/Objective: Develop secure QR/NFC identifier encoding module. Verification Criteria: 10 test IDs generated and resolved via scanner.
Q1M4A3-Design identity workflows
Goal/Objective: Design workflows for identity assignment, activation, and scanning at healthcare points. Verification Criteria: SOPs validated through a table-top exercise at 1 site.
Q1M5A1-Draft informed consent protocols
Goal/Objective: Draft and validate protocols for informed consent, role-based access, and emergency scenarios. Verification Criteria: Protocols reviewed and signed by 1 provider and UNICEF legal team.
Q1M5A2-Conduct Privacy Impact Assessment (PIA)
Goal/Objective: Conduct privacy impact assessment aligned with Colombian data law. Verification Criteria: DPIA document submitted; internal feedback incorporated.
Q1M5A3-Design audit logging system
Goal/Objective: Design secure audit logging and real-time alerting module. Verification Criteria: Log system captures access by role and user ID in test cases.
Q1M6A1-Design communication materials
Goal/Objective: Design communication materials to target customers (nonprofits/multilateral organizations/national government). Verification Criteria: An approved pitch deck, a one-page fact sheet, and draft email templates for outreach are stored in the shared project folder.
Q1M6A2-Create waitlist form
Goal/Objective: Create a waitlist or form on your website or through your circulation materials to start mapping out entities that may be interested. Verification Criteria: A live URL for the waitlist form. A dashboard or spreadsheet showing the list of interested entities and th…
Q1M7A1-Attend technical product development sessio
Goal/Objective: Attend technical product development session. Verification Criteria: Session notes and key action items.
Q1M7A2-Revision of the work plan
Goal/Objective: Revision of the work plan at the end of the first quarter. Verification Criteria: The project work plan is 100% updated to reflect progress, challenges, and priorities for the next quarter.
Q1M7A3-Creation of Karma profile
Goal/Objective: Creation of company profile and project file on Grantee Accountability Protocol (Karma). Verification Criteria: A live URL or screenshot confirmation of the completed profile on the Karma platform.
Q1M8A1-Social media posts
Goal/Objective: 1 image + caption per month to be shared on your social media channels. Verification Criteria: Social media scheduler logs or live links to the published posts.
Q1M8A2-Blog post
Goal/Objective: 1 blog post at the beginning of the quarter. Verification Criteria: One 500-800 word blog post is drafted, approved by leadership, and published on the project website/blog. A live URL to the published blog post.
Q1M9A1-Apply OSI-approved license
Goal/Objective: Determine licensing strategy for Open Source intellectual property (i.e. permissive or copyleft). Apply an Open Source Initiative-approved license to a public source code repository. Verification Criteria: A signed memo or document stored in the project's internal…
Q1M9A2-Create project charter
Goal/Objective: Create a project charter. Project charters should include: vision statement, mission statement, community statement, licensing strategy, and identification of key trademarks. Verification Criteria: Project charter is approved.
Q1M9A3-Create READMEs
Goal/Objective: Create READMEs (in English) for all public repositories. READMEs should include: overview of specific repo, developer environment instructions, note about how repo connects into overall product, list of any Open Source software used. Verification Criteria: The REA…
Q1M9A4-Create public documentation site
Goal/Objective: Create a public Open Source documentation with a corresponding public source code repository. Use automation tools to set up automatic deployments of HTML documentation site from public source code repository. Verification Criteria: A live URL for the documentatio…
Q1M9A5-Establish QA process
Goal/Objective: Establish an Open Source quality assurance process. Explore unit testing frameworks for front-end/back-end software, if applicable. Document user stories and test cases. Verification Criteria: The QA process document and test case backlog are checked into the proj…
Q1M9A6-Publish Code of Conduct
Goal/Objective: Identify a Code of Conduct for any public Open Source repositories. Upload it to public source code repositories. Create internal documentation for how to respond to a Code of Conduct report. Verification Criteria: The CODE_OF_CONDUCT.md file is visible in the roo…
Q1M9A7-Follow Pull Request workflow
Goal/Objective: Follow the Pull Request Workflow when contributing code into your Open Source repositories. Verification Criteria: A PR template (PULL_REQUEST_TEMPLATE.md) is added to the repositories. PR history shows adherence to the workflow.
Q1M10A1-Attend privacy and security session
Goal/Objective: Attend data privacy and security information/awareness session. Verification Criteria: Attendance confirmed. Session notes.
Q1M10A2-Complete Privacy Impact Assessment
Goal/Objective: Complete the Privacy Impact Assessment (PIA), a standard template provided by UNICEF, for the specific product/service. PIA requires to outline data processing practices. Verification Criteria: DPIA document completed; internal feedback incorporated.
Q2M1A1-Finalize development of HL7v2 connector
Goal/Objective: Finalize development of the clinical interoperability connector for pilot-provider integration, implemented on FHIR R4 with Colombian RDA profiles. Verification Criteria: Connector service implemented and versioned in the public repository, with the RDA bundle bui…
Q2M1A2-Validate data flow to GCP
Goal/Objective: Test and Validate data flow from SIP to Google Cloud Healthcare. Verification Criteria: 20+ clinical bundles ingested without error and visible in the FHIR Explorer.
Q2M1A3-Document connector deployment and usage
Goal/Objective: Document connector deployment and usage for replication. Verification Criteria: Deployment and replication documentation published on the public documentation site and reviewed by the technical lead.
Q2M2A1-Implement ID assignment workflow
Goal/Objective: Implement ID assignment workflow at provider level Verification Criteria: Providers can register and assign unique identifiers to patients through the system: sync, scan and search endpoints resolving patients by device_uid.
Q2M2A2-Internal testing of NFC check-in and record
Goal/Objective: Conduct internal testing of patient check-in via QR/NFC and record access. Verification Criteria: Patient check-in (NFC/QR) and record-access flows verified through internal testing.
Q2M3A1-Develop mobile interface for patient lookup
Goal/Objective: Develop the mobile interface for patient lookup via NFC Verification Criteria: NFC lookup interface integrated in the app and validated with 10+ sample patients.
Q2M3A2-Connect mobile UI to cloud backend
Goal/Objective: Connect the mobile UI to the cloud backend for read-only access to clinical summaries. Verification Criteria: Data load time ≤ 30 seconds in ≥90% of cases.
Q2M3A3-UI/usability evaluation with health staff
Goal/Objective: Conduct UI/usability evaluation with health staff, updated with A/B testing. Verification Criteria: A/B evaluation protocol documented — UI variants, time-on-task and error-rate capture, task script and data-capture instrument — with the usability session coordina…
Q2M4A1-Simulate full data flow synthetic patients
Goal/Objective: Simulate the complete data pipeline using synthetic patient records. Verification Criteria: 10 synthetic patients processed through the full pipeline (LLM → DB → FHIR → GCP) with ≥90% of the intended workflow completing without failure; delta-sync verified.
Q2M4A2-Prepare technical documentation pilot
Goal/Objective: Prepare the technical documentation required to support first real use at a provider site. Verification Criteria: Pilot Readiness Checklist and technical guides (architecture, security, database, FHIR Store, AI integration) published on the public documentation si…
Q2M4A3- Conduct dry-run with test users
Goal/Objective: Conduct a dry-run of system operation with test users and collect structured feedback. Verification Criteria: Simulated sessions with users replicate the expected workflow: dry-run with at least 3 users completed and evaluated, evidenced by user test logs, partici…
Q2M5A1-Communication materials for customers
Goal/Objective: Design communication materials for target customers. Verification Criteria: Pitch deck, one-page fact sheet and outreach email templates stored in the shared project folder.
Q2M5A2-Create public waitlist / interest form
Goal/Objective: Deploy a public-facing mechanism to map entities interested in the solution. Verification Criteria: Live public waitlist form URL with an active response sheet.
Q2M5A3-Circulate materials with target customers
Goal/Objective: Circulate communication materials with at least 3 target customers, e.g. Onboarding blog or internal marketing materials. Verification Criteria: Materials sent to 3 target organizations.
Q2M6A1-Revise work plan at end of Q2 (v3.0)
Goal/Objective: Revise the project work plan at the end of Q2 to reflect progress and priorities for the remaining period. Verification Criteria: An approved v3.0 of the project plan is shared with all key personnel.
Q2M6A3-Complete mid-term narrative report
Goal/Objective: Complete and submit the mid-term narrative report on the official template. Verification Criteria: Report completed on the official UNICEF 6-month template and submitted.
Q2M7A1-OSI-approved license in public repositories
Goal/Objective: Distribute an OSI-approved license with all public source code repositories by end of Q2. Verification Criteria: LICENSE file with OSI-approved text visible in the root directory of both public repositories.
Q2M7A2-Contributing guidelines in all repositories
Goal/Objective: Create contributing guidelines for all Open Source repositories and link them from the documentation site. Verification Criteria: CONTRIBUTING.md merged into the main branch of both public repositories and referenced from the documentation sites.
Q2M7A3-Public tickets/issues for features and bugs
Goal/Objective: Create public tickets/issues corresponding to planned features and known bugs across the Open Source repositories. Verification Criteria: Populated public issue boards live and accessible in both repositories.
