top of page

Team 05 - 2026

Our team represents 5 countries, 6 time zones, and a wide range of levels of experience.

When we formed, we were a group of strangers - now we are a working team!

Designer_edited.jpg

Team Mentor & Product Owner

Marcela Rivas

New Zealand

​

Marcela is a results-driven professional with experience across IT, project management and operations. She enjoys bringing people together to solve complex problems, translating business needs into practical solutions, and helping teams deliver successful outcomes. Throughout her career, Marcela has partnered closely with stakeholders and technical teams, leveraging data, analysis, and process improvement to drive informed decision-making. Known for her collaborative approach and commitment to continuous learning, she is passionate about creating efficiencies, building strong relationships, and contributing to initiatives that support long-term business success.

 

Designer (1).png

Project Manager

Emmanuel Ukachukwu

Abuja Nigeria, Federal Capital Territory

 

Emmanuel is an early-career project management professional and Scrum Master with experience coordinating cross-functional initiatives, including timeline management and communication across international teams.

 

He holds a Project Business Professional (PBP) certification.

Untitled design - 2026-11-05T124027.119.png

Business Analyst

Moni Adeoye

Swindon, United Kingdom

​

Moni Adeoye is a Business Analyst with three years of experience in digital change, supported by nine years in banking. Alongside her BA work, she contributes to SDR initiatives, strengthening her skills in stakeholder engagement, discovery and commercial insight. She is passionate about translating business needs into practical, customer-focused solutions that deliver measurable value.

​

​

​

​

​

Zulfah Adeiza.jfif

Business Analyst

Zulfah Adeiza

Milton, Ontario, Canada

​

Zulfah Adeiza is a Certified Business Analysis Professional (CBAP) and Change Management Analyst with a background in clinical pharmacy.

 

She supports healthcare transformation through stakeholder engagement, requirements analysis, and change readiness. Passionate about connecting people, processes, and technology, she aims to improve healthcare services through business analysis, effective change management, and health informatics.

Mohammed Nour.png

Quality Assurance Analyst

Mohammed Nour

Toronto, Ontario, Canada

​

Mohammed is a Salesforce Certified Business Analyst with 5+ years of experience across government and private sector environments, specializing in requirements gathering, process improvement, and CRM solutions. 

 

He is equally comfortable configuring systems and training the people who use them, and enjoys making complex processes simpler for everyone involved.

Margo_Wald_headshot_SDLC_Experience_2026.jpg

User Interface & User Experience

Margo Wald

Boston, Massachusetts, USA

​

Margo has a background as both a business analyst and a product manager, across several different industries (enterprise software, mobile apps, utilities).

 

With a knack for asking insightful questions and a clear conceptual understanding of technology, Margo helps organizations build the right products to meet their users’ needs.

Donnie Roberts.jpg

Developer

Donnie Roberts

Lake Wales, Florida, USA

​

Donnie Roberts is an Embedded Systems Engineer with hands-on experience designing microcontroller-based systems, possessing strong knowledge in hardware/software integration, real-time control, networking, and sensor interfacing.

Designer (3).png

Quality Assurance Analyst

Sanjiv Kuchibhatla

Bradenton, Florida

​

Results-driven Lead Business/QA Analyst with strong experience in data analytics, turning complex data into actionable insights.
Proven ability to bridge business and technical teams, delivering high-quality, data-driven solutions.
Skilled in requirements gathering, testing, and continuous improvement with a focus on accuracy and efficiency.

Rural Hospital
Digital Intake Project

Business Need Summary

Screenshot 2026-11-01 163629.png

(document continues...)

Team Kanban Board

Screenshot 2026-11-06 161015.png
Screenshot 2026-11-06 161057.png

Project Deliverables - By the Project Manager

Project Plan
 

1. Project Overview 
1.1 Purpose of This Document 

This Project Plan is the Project Manager's core deliverable, produced at Session 1 by interpreting the business case — before any elicitation with the Product Owner takes place. It follows a standard PMBOK-aligned structure (scope, schedule, cost, quality, resources, risk, communications, and stakeholders) so it can serve as a template for any project the team runs, in the workshop or otherwise. 

 

1.2 Project Summary 

This Project will deliver a tablet-based digital patient intake system that replaces the current paper-based registration process to reduce duplicate entry, improve the accuracy of patient information, and enhance efficiency. 

​

1.3 Business Objectives 
Key Business Outcomes 
  • Reduce duplicate patient data entry by eliminating repetitive manual processes and improving staff efficiency. 

  • Improve medication information accuracy to reduce clinical risks, documentation errors, and compliance concerns. 

  • Enhance the patient intake experience through a faster, simpler, and less frustrating registration process. 

  • Increase operational efficiency by reducing administrative workload and enabling staff to focus more on patient care. 

  • Improve data quality and compliance by ensuring patient information is complete, consistent, and reliable across systems. 

 

1.4 Success Criteria 
  • Duplicate Data Entry Reduction: Reduce duplicate data entry by 75% within 90 days of launch 

  • Medication List Accuracy: Reduce Medication list error by 50% within 6 months of launch 

  • Patient Intake Time: Reduce average patient Intake time by 20% within 3 months of launch. 

  • Tablet Adoption:  Achieve 90% tablet adoption within 6 months of Launch  

  • Patient Satisfaction: Achieve 85% Patient Satisfaction with the intake process within 6 months of launch 

 

  

2. Scope Statement 
2.1 In Scope 

Features/functions included:  

  • Digital Patient Registration 

  • Medication List Management 

  • Tablet-Based Intake Experience 

 

2.2 Out of Scope 

Excluded features/functions: 

  • Patient to remotely register 

  • Any intake capability beyond registration, insurance information and medication list management (e.g. scheduling, billing, etc.) 

​

(document continues...)

Project Manager: Emmanuel Ukachukwu

Project Deliverables - By the Product Owner

Business Objectives

Product Owner - Marcela Rivas
image.png

(document continues...)

Product Vision Statement

Product Owner - Marcela Rivas
For Patients, Nurses and Intake Staff, Healthcare Providers, Hospital Leadership, and Compliance Teams, who have duplication issues, long wait times, and medication errors; we will develop a Digital Intake Platform that is web-based on a tablet or PC which will decrease wait times, increase patient satisfaction, make clinical staff more effective, improve accuracy of patient details, and enforce compliance for medications. Unlike the current intake process, it will bring efficiencies with the new process, and decrease the number of errors and duplication, helping the organization achieve faster intake, fewer errors, less duplication, patient satisfaction, and accuracy in medication.

Project Deliverables - By the Business Analyst

RAO Log
Business Analyst: Moni Adeoye
Screenshot 2026-11-01 165548.png

Scope Statement

Business Analyst: Moni Adeoye
1. Project Overview

The Rural Hospital Digital Intake project will introduce a web-based digital intake platform for use on tablets and PCs to replace the current paper-based process. The solution will enable patients to enter and review their personal, insurance, and medication information electronically, while allowing nurses, intake staff, and healthcare providers to access the information without unnecessary re-entry. The project aims to reduce patient wait times, minimise duplicate data entry and medication-list errors, improve the accuracy of patient information, support compliance, increase staff efficiency, and improve the overall patient intake experience.

 

2. Project Objectives
  • Objective 1: Reduce duplicated data by 75% within 90 days.

  • Objective 2: Reduce medication errors by 50% within 6 months.

  • Objective 3: 85% patient satisfaction within 6 months.

 

3. In-Scope Boundaries

Features/functions included:

  • Digital Patient Registration

  • Medication List Management

  • Tablet-Based Intake Experience

 

Business units included:

  • Patients

  • Nurses and Intake Staff

 

Processes included:

  • Demographic Form

  • Visit Reason

  • Medication List Form

 

4. Out-of-Scope Boundaries Excluded features/functions

Patient to remotely register

Healthcare Providers functionality

Hospital Leadership and Compliance Teams functionality Excluded business units: N/A Future-phase considerations: Mobile Application Remote Registration

 

5. Assumptions
  • 1: Technology Assumptions Assumption

  • 2:  Patient Assumptions Assumption

  • 3: MVP Delivery Assumptions

 

6. Constraints

Functional constraints (from the business case):

  • Must work on tablets Must reduce duplicate entry

  • Must support medication lists Must be accessible

  • Must be simple enough for patients to use without training.

 

Time constraints:

  • The project must be completed within the scheduled workshop timeline from August 22 to November 7, 2026, while keeping delivery focused on the agreed MVP

 

Technology constraints:

  • The solution must be web-based, tablet-compatible, accessible, easy for patients to use, and support digital registration and medication management. Resource constraints:

  • The project must be delivered within the available team and stakeholder capacity, with resources prioritised on the agreed MVP rather than future features such as remote registration or a mobile app.

​

(document continues...)

Business Analyst: Moni Adeoye
Current State Assessment
 
1. Current Process Overview 

 
The current patient intake process is triggered when a patient arrives at the hospital and checks in at the front desk. Front-desk or intake staff provide the patient with paper forms covering demographic information, reason for visit, and current medications.  

​

The patient completes the forms manually and returns them to the nurse or intake staff. 

​

The nurse or intake staff reviews the submitted forms to determine whether the information is complete and clear. Where information is missing, unclear, or inconsistent, the nurse verbally clarifies it with the patient. Medication information is reviewed in greater detail, including the medication name, dosage, frequency, missing medications, duplicate medications, and outdated information. The nurse also compares the patient-provided medication information with the medication list already recorded in the Electronic Health Record (EHR). 

​

Once the information has been reviewed and verified, the nurse or intake staff manually enters or updates the patient’s demographic, insurance, Visit Reason, and medication information in the EHR. The completed paper forms are then scanned into the EHR as supporting documents and transferred for storage in the hospital’s physical filing system. 

​

The stakeholders involved are the patient, front-desk or intake staff, nurses, records-management staff, and healthcare providers who rely on the information for patient care.  

​

The current outcome is an updated electronic patient record, a scanned copy of the completed forms, and a retained physical paper record. Achieving this outcome requires repeated data capture, verbal clarification, manual EHR entry, scanning, and physical filing. 

​

2. Pain Points & Inefficiencies 

​

Bottlenecks: 

  • Patients must manually complete multiple paper intake forms before staff can begin reviewing the information.  

  • Nurses or intake staff must review each form and verbally clarify missing, unclear, or inconsistent information with the patient.  

  • Medication information requires additional comparison and verification against the existing EHR medication list.  

  • Verified information must be manually entered or updated in the EHR before the intake process can proceed.  

  • Paper forms must still be scanned and physically filed after the information has been entered into the EHR.  

  • The sequential review, verification, data-entry, scanning, and filing activities increase the overall intake-processing time. 

 

Manual workarounds:  

  • Nurses or intake staff verbally verify information with patients when paper forms are incomplete, unclear, or inconsistent.  

  • Staff manually compare the patient’s handwritten medication information with the medication list stored in the EHR.  

  • Staff scan completed paper forms into the EHR to retain an electronic copy of the original documentation.  

  • Staff retain physical copies of completed forms in the paper filing system.  

  • Staff manually reconcile differences between the information provided by the patient and the existing EHR record. 

 

Delays and rework:  

  • Demographic, insurance, Visit Reason, and medication information may be re-entered even when some information already exists in the EHR.  

  • Missing or unclear information requires repeated clarification between patients and staff.  

  • Illegible handwriting may cause staff to misinterpret patient or medication information.  

  • Medication names, dosages, and frequencies may be entered incorrectly during manual transcription.  

  • Missing, duplicate, outdated, or inconsistent medication information requires additional verification and correction.  

  • Entering information into the EHR, scanning the same forms, and retaining physical copies creates duplicate documentation effort. 

 

User or stakeholder impact: 

  • Patients experience longer waiting times and may need to repeat information already held by the hospital.  

  • Nurses and intake staff spend additional time reviewing, clarifying, re-entering, scanning, and filing information.  

  • Healthcare providers may experience delays in receiving complete and accurate information needed for patient care.  

  • Inaccurate or outdated medication information increases patient-safety and medication-reconciliation risks.  

  • Hospital leadership and compliance teams face audit and compliance concerns arising from medication-list errors and inconsistent documentation.  

  • Repeated manual activities reduce operational efficiency and limit the number of patients staff can process efficiently. 

 

3. System/Tool Inventory 
​
​

(document continues...)

Aligned Requirements
Business Analyst: Zulfah Adeiza
Requirements List
image.png

(document continues...)

User Stories
image.png

(document continues...)

Acceptance Criteria
image.png

(document continues...)

Product Backlog
Business Analyst: Mohammed Nour
Quality Assurance: Sanjiv Kuchibhatla
image.png

(document continues...)

Project Deliverables - By Quality Assurance Analyst

Test Strategy/Test Plan

 
1. Document Purpose  
 

The purpose of this Test Strategy and Test Plan document is to define the testing approach, scope, activities, responsibilities, and quality expectations for the Rural Hospital Digital Intake System Project. 

This document provides guidance to the QA team and project stakeholders on how testing will be planned and executed to ensure the delivered solution meets business requirements and quality standards. 
 

2. Project Overview 
 

Business Objective 

The team’s objective is to create a portal to reduce duplicate patient data entry, improve the accuracy of medication information, and improve patient satisfaction with the intake process.  

The enhanced portal will allow customers to: 

  • Reduce duplicate data entry 

  • Reduce medication-list errors  

  •  Achieve patient satisfaction 

 

3. Testing Objectives 

​

The objectives of testing are: 

  • Verify that business requirements are implemented correctly 

  • Identify defects before production release 

  • Validate application functionality and usability 

  • Ensure data accuracy 

  • Confirm the application works on the device 

  • Provide confidence before deployment 

 
4. Testing Scope 
In Scope 
Quality Assurance: Sanjiv Kuchibhatla,
Mohammed Nour

(document continues...)

Test Cases

Quality Assurance: Sanjiv Kuchibhatla,
Mohammed Nour
image.png

(document continues...)

Project Deliverables - By the UI/UX Designer

Persona 
Lucía 

55 years old 

Native Language is Spanish, knows some English 

Frequent visitor to the clinic, multiple health problems 

Wear reading glasses but often forget to take them when she goes out. 

 

Goal 

To get seen in the clinic as quickly as possible so that she can return to her work as soon as possible and not lose too much pay. 

 

Frustration 

Every time I go to the clinic I have to fill out a mountain of paperwork and then the next time I have to do it all over again. I wish they would keep track of my information from one appointment to the next. 

 

Device 

Lucía is comfortable making calls and sending texts with her Android phone, as well as watching videos on it. But she uses a computer only occasionally and has never owned or used a tablet 

 

Tech Comfort 

Low. Not adventurous with technology, struggles to learn new things on the phone or computer. Often gets frustrated that keyboards lack the accents/symbols that are used in Spanish, her native language. 

 

Quote 

“Stop asking me the same questions every time I check in for an appointment. Don’t you know me by now?” 

 

So, I must 
  • Provide language options including Spanish 

  • Provide option for large font size 

  • Save information from one appointment to the next 

  • Minimize the number of questions asked – only the essentials 

  • Provide options to skip questions if patient doesn’t know the answer 

​

User Stories 
  • New Patient checking in using tablet for the first time 

  • Returning Patient checking in for a subsequent appointment 

  • Nurse who needs to check medication list 

  • Provider who needs access to all patient data to provide the best care 

UI/UX Designer: Margo Wald

Test Cases

Quality Assurance: Sanjiv Kuchibhatla,
Mohammed Nour
image.png

(document continues...)

UAT Results

Quality Assurance: Sanjiv Kuchibhatla,
Mohammed Nour
image.png

UAT RESULTS.

-One Test case to create

-One test case in testing

-One defect

-23 completed done

Patient and Staff User Flow 
UI/UX Designer: Margo Wald
image.png
UI/UX Designer: Margo Wald

Project Deliverables - By the Developer

Developer: Donnie Roberts
Initial Technical Feasibility Assessment

 

Project / Case Study: Digital Patient Intake System

Team: SDLC Team 5 D

eveloper(s): Donnie Roberts

Date: 8/29/2026

 

1. Feasibility Conclusion

The proposed Digital Patient Intake System MVP is highly feasible because it addresses a clearly defined business problem using well-established technology and a limited, focused scope.

 

2. Proposed Solution at a High Level

The solution requires capabilities that are commonly available in healthcare applications today:

  • Tablet-based data entry

  • Electronic patient registration forms

  • Digital medication-list management

  • Staff access to submitted intake information

  • Integration or data transfer to existing EHR workflows

 

These features rely on mature technologies that are widely used in healthcare settings, reducing technical risk. The MVP does not require advanced technologies such as artificial intelligence or complex clinical decision support systems, making implementation achievable within a reasonable timeframe.

 

3. Technology Feasibility

​

 

​

​​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

 

 

4. Resource Feasibility

 

For the Digital Patient Intake System MVP, resource feasibility is concerned with whether the team can realistically build and demonstrate a working prototype that includes digital registration, medication management, and a tablet-based user experience.

 

Assess:

  • Available development skills: High feasibility. The solution does not require specialized expertise such as artificial intelligence, machine learning, or advanced healthcare analytics.

  • Available tools/platforms:

    • High feasibility.

    • Suitable development platforms are readily available and capable of supporting all MVP requirements.

  • Development time: High feasibility. The scope is small enough to be designed and prototyped within the available project timeframe.

  • Access to required APIs, services, or data: High feasibility. The MVP can be demonstrated without requiring access to production APIs or sensitive patient records.

  • Ability to create a prototype within the project timeline:

    • High feasibility. The team can realistically produce a functional prototype that demonstrates the core business value.

 

Assessment: the team has sufficient resources to successfully design and deliver the proposed MVP within the constraints of the simulation. 

image.png

(document continues...)

Technical Specification

 

1. System Architecture & Hosting


▶ The application will be deployed as a web application on Cloudflare Workers.
▶ The simulated EHR database will be an SQLite database managed by a central Cloudflare Durable Object (storage.sql).
▶ The user interface is optimized for tablet and desktop web browsers (any modern browser; no proprietary hospital hardware required).


2. Authentication & Access Control


▶ Patient Authentication: Patients authenticate using their Full Name (first and last) and Date of Birth (DOB). If an exact match is found, their existing record is retrieved; if no record exists, a new patient record is automatically initialized.
▶ Staff Authentication (Demo Mode): Formal authentication is bypassed for this prototype. The login screen displays a typical username and password field. However, the username field is actually a role dropdown (Nurse, Intake Staff, Healthcare Provider, Leadership / Compliance) and the password field accepts any input without validation.
▶ Role-Based Views: Selecting a role directs the user to role-specific capabilities (e.g., Intake Staff see the intake dashboard; Nurses and Providers see clinical reviews and verification; Leadership sees analytics reports).


3. Patient Intake Flow & Forms


1. Patient Registration: Collects mandatory personal and demographic details.
2. Reason for Visit: Mandatory selection from common clinical visit reasons with an optional free-text field for additional details.
3. Insurance Details: Allows adding, editing, and removing multiple insurance policies. An option for “Uninsured / Self-Pay” is provided to bypass mandatory insurance checks.

​​

​

​

Developer: Donnie Roberts

(document continues...)

Technical Stack

Developer: Donnie Roberts
AI-Assisted Engineering & Documentation

 

Google Antigravity

•Used to produce technical documentation and code for the project, facilitating rapid prototyping, requirement alignment, and high-quality deliverables.

•Powers agentic workflows for generating system designs, technical specifications, and production-ready application code while maintaining architectural consistency.

 

Frontend Presentation

Modern Vanilla HTML5, CSS3, ES Modules, & Web Notifications API

•Eliminates heavy framework dependencies, ensuring near-instantaneous page loads under standard response-time thresholds.

•Delivers seamless execution on any standard tablet web browser.

•Utilizes native browser WebSockets and Web Notifications for desktop alerts for patient intake tracking.

 

UI Design & Accessibility

CSS Custom Properties and Design Tokens, HTML5 Form Validation

•Direct implementation of accessibility toggles: dynamic root font-scaling for “Large Text” mode and scoped color themes for “High Contrast” mode (minimum contrast ratio >= 4.5:1 text, 7:1 high-contrast).

•Touch-first ergonomics with minimum 48x48px hit targets, clear focus rings, and screen-reader ARIA semantics.

 

Client Storage & Offline Resilience

Browser Storage API (localStorage & IndexedDB) + Service Worker

•Delivers seamless offline continuity: caches active form sections locally when network connectivity drops.

•Enables precise privacy enforcement: allows immediate, programmatic purging of locally cached sensitive health data upon logout or final submission.

 

Hosting & Infrastructure

Cloudflare Workers Assets & Global Edge Network

•Serverless architecture; delivers SSL/TLS encryption, automatic DDoS mitigation, and edge caching out of the box.

•Simplifies deployment to a single wrangler deploy pipeline without external database connection pools or complex VPC setups.Backend Compute & API GatewayCloudflare Workers (V8 Serverless Runtime)

•Edge compute platform with sub-millisecond cold starts deployed across global points of presence, satisfying responsiveness goals.

•Natively hosts static frontend assets, routes REST API endpoints, manages staff authentication, and transparently upgrades and proxies authenticated WebSocket connections directly to Durable Objects while validating unexpired tokens.

 

State Coordination & Consistency

Cloudflare Durable Objects & WebSocket Hibernation API

•Provides a distributed, strongly consistent actor model coordinating concurrent patient and staff access.

•Acts as the authoritative single point of coordination for the simulated EHR and real-time push hub, validating active staff tokens before accepting WebSockets, and using the Cloudflare Durable Object WebSocket Hibernation API for efficient, zero-idle-cost client event fanout.

 

Database & Persistence

Cloudflare Durable Object Embedded SQLite (storage.sql)

•Co-locates relational SQLite storage directly inside the Durable Object memory boundary with zero network latency between compute and SQL engine.

•Full ACID transactions for relational intake data: handles tabular relational schemas (patients, insurances, medications, audit_logs) and complex aggregate reporting queries.

 

Development & Verification

Miniflare (Local Workers / DO Simulator)

•Miniflare provides 100% faithful local simulation of Cloudflare Workers, Durable Objects, and embedded SQLite for rapid development and automated testing.

Solution Design
​

​

Developer: Donnie Roberts
image.png

(document continues...)

image.png

(document continues...)

Tampa Bay Health Center - Live Application
https://team5-intake.dr0b3rts.workers.dev/

Developer: Donny Roberts
To Test:

As a New Patient - enter a name and Date of Birth

Or - Under Quick Demo Shortcuts:

Existing draft with medications - Jane Doe

Self-Pay / Uninsured Patient - David Chen

New patient check-in - Maria Rodriguez

Impact of the SDLC Experience Workshop

Zulfah Adeiza.jfif

Business Analyst

Zulfah Adeiza

The SDLC Experience Workshop strengthened my confidence as a Business Analyst through hands-on work in current-state analysis, requirements refinement, and cross-functional collaboration.

Moni Adeoye Updated.png

Business Analyst

Moni Adeoye

The SDLC experience has enhanced my ability to apply structured business analysis practices across the project lifecycle, particularly in requirements management, stakeholder alignment and solution validation.

 

It has also strengthened my appreciation of how early BA involvement and continuous collaboration contribute to effective delivery.

Mohammed Nour.png

Quality Assurance Analyst

Mohammed Nour

Through the project I gained real, end-to-end experience with the full SDLC using Agile. I’d worked on parts of projects before, but this was my first time taking one from discovery all the way through testing.

 

Working as a QA Tester and supporting other roles, alongside a team spread across four continents, showed me how each role and deliverable connects to the next, and how much depends on clear communication when you can’t all be in the same room.

Awards and Recognition 

Do YOU have a story? Post it in BA Force Multiplier - I'm IN! 👉

  • LinkedIn

Need Assistance or Coaching? Contact Thea Soehren          👉

  • Website
  • create an icon for a calendar
  • LinkedIn

© 2024 by BA Force Multiplier. Web design by WebMox LLC

bottom of page