Biomedical Product Design

1. Chapter Overview

Biomedical product design is the disciplined translation of clinical unmet needs into safe, effective, manufacturable medical devices. On the MoE exit blueprint, this theme carries 18% of exam weight across 9 blueprint items—This theme carries significant weight on the national exit examination.

The course spans two tightly linked frameworks:

1. Ulrich & Eppinger concept development process — mission statement → customer needs → target specifications → concept generation → concept selection → final specifications → prototyping → testing → downstream planning.
2. Regulated medical device development — ISO 13485 quality management system (QMS) with design controls, and ISO 14971 risk management threaded through every phase.

Exit exams test whether you can place activities in the correct phase, distinguish requirements from specifications, select the right decision tool (Pugh vs concept scoring vs AHP), and apply engineering judgment in scenario questions about ethics, low-resource settings, usability, and simulation limits.

This chapter walks the full design workflow using a low-cost pulse oximeter for low-resource settings (the Q400 pattern: cost-effectiveness, ruggedness, maintainability trump premium features). All practice questions include full solutions.

Primary sources: materials/extracted/telegram/chapter-two-product-planning.txt, chapter-four-product-specifications.txt, chapter-five-concept-generation.txt, chapter-six-consept-selection.txt, and biomedical-product-design-exit_exam-q-a2024.txt.

2. Learning Outcomes

After completing this chapter, you should be able to:

1. Describe the six-phase design process used in this curriculum: product planning → concept generation → design selection → procurement and specifications → prototype → test (V&V).
2. Write a mission statement and screen opportunities using the Real-Win-Worth-it (RWW) framework.
3. Conduct customer needs analysis with hierarchical need statements, importance ratings, and translation to measurable target specifications.
4. Apply the four-step target specification process and five-step final specification process, including competitive benchmarking and trade-off analysis.
5. Execute concept generation using problem decomposition, function diagrams, external/internal search, classification trees, and combination tables.
6. Perform concept screening (Pugh matrix, +/0/−) and concept scoring (weighted criteria) and know when to use AHP or pairwise comparison.
7. Explain the difference between user needs, design requirements, design inputs, design outputs, and specification documents in procurement.
8. Build and test alpha/beta/physical working prototypes using appropriate tools (CAD, Proteus, Arduino, LabVIEW).
9. Distinguish design verification (did we build it right?) from design validation (did we build the right thing?).
10. Map development activities to ISO 13485 design controls and ISO 14971 risk management lifecycle requirements.

3. Core Concepts

3.1 The Concept Development Process (Master Flow)

The canonical flow from lecture materials:

Mission Statement
       ↓
Identify Customer Needs ──→ Establish Target Specifications
       ↓                              ↓
Generate Product Concepts ──→ Select Product Concept(s)
       ↓                              ↓
Set Final Specifications ←── Test Product Concept(s)
       ↓
Plan Downstream Development
       ↓
Build and Test Models/Prototypes → Perform Economic Analysis
       ↓
Benchmark Competitive Products (continuous)

Key insight: This is iterative, not linear. Failed prototype tests force revisiting specifications or concepts. Regulatory risk reviews may reopen design inputs. Product planning sets which projects enter this funnel; concept development executes how a chosen project proceeds.

Five dimensions of successful product development (lecture): Product quality, product cost, development time, development cost, and development capability (organizational learning for future projects).

Interdisciplinary team (lecture): Marketing (customer interface), Design (physical form), Manufacturing (production system), plus clinical, regulatory, and quality roles. Core team is small; extended team adds specialists as needed. Typical development duration: 3–5 years for many medical devices; cost scales with team size, duration, and tooling.

3.2 Phase A — Product Planning

Product planning occurs before a development project is formally approved. It answers: Which products should we build, when, and with what resources?

Opportunity identification

An opportunity is an embryonic product idea:

• A rough match between a need and a possible solution
• Often less than one page: title, narrative, sketch
• Categorized by familiarity with technology and market

Opportunity tournament (six steps)

1. Establish a grant — innovation charter / mission scope (e.g., "wearable glucose monitor launchable within one year through existing channels")
2. Generate and sense many opportunities (internal + external sources equally important)
3. Screen opportunities — holistic group judgment; eliminate non-viable ideas
4. Develop promising opportunities — customer interviews, test existing products, concept generation, quick prototypes, market size estimates (days to weeks each)
5. Select exceptional opportunities — RWW or capital/time/passion criteria
6. Reflect on process quality

RWW framework

Product planning steps

1. Identifying opportunities
2. Evaluate and prioritize projects (competitive strategy, market segmentation, technology trajectories, platform planning)
3. Allocate resources and plan timing (pipeline management: technology readiness, market readiness, competition)
4. Complete pre-project planning — rewrite opportunity as product mission statement with cross-functional core team
5. Reflect

Competitive strategy perspectives: technology leadership, cost leadership, customer focus, imitative strategy.

Exam trap: Quality assurance monitors execution; it is least relevant to upfront product planning strategy (exit-0321, exit-0684).

3.3 Phase B — Concept Generation

A product concept is a technical description of how the product will satisfy customer needs:

• Approximate technology, working principles, and form
• Expressed with sketch/3D model plus brief text
• Not the same as a vague "idea" — concepts are evaluable

Five-step concept generation process

1. Clarify the problem — mission statement, customer needs, specifications; decompose via function diagrams
2. Search externally — lead users, experts, patents, literature, benchmarking
3. Search internally — individual and group methods; suspend judgment; welcome infeasible ideas
4. Explore systematically — classification tree; combination table
5. Reflect — was solution space fully explored?

Common dysfunctions (memorize for exams)

• Considering only one or two alternatives
• Ignoring competitors' concepts
• Involving only one or two people
• Failing to integrate partial solutions
• Failing to consider entire categories of solutions

Internal search hints

Suspend judgment, generate many ideas, use analogies, wish-and-wonder, set quantitative goals, gallery method, trade ideas in groups.

Exam trap: Exploring supply chain options is not part of concept generation (exit-0307) — logistics comes later.

Exam note: The curriculum's "first stage of the design process" in some bank items is listed as Concept Generation (exit-0305) when referring to the six-phase engineering cycle starting after planning. Always read the stem: if options include "Planning," customer needs belong to concept development phase (exit-0422).

3.4 Phase C — Design Selection (Concept Selection)

Concept selection is a decision process to choose one or few concepts for further development.

Goal: Not merely "pick the best concept" but develop the best concept by combining strengths and eliminating weaknesses.

Two stages

Concept selection approaches

• External decision (customers/clients)
• Product champion & intuition
• Multi-voting
• Pros and cons
• Prototype and test
• Decision metrics (Pugh, scoring, AHP)

Pugh concept screening — six steps

1. Prepare matrix (criteria, reference concept, optional weightings)
2. Rate concepts (+ better, 0 same, − worse vs reference)
3. Rank by sum of + and −
4. Combine and improve — merge good features; eliminate bad
5. Select one or more concepts (beware "average" concepts)
6. Reflect

Concept scoring formula

Where $w_i$ = weight of criterion $i$, $r_{ij}$ = raw rating of concept $j$ on criterion $i$.

Tool selection guide (high-yield)

Requirements during design selection define constraints and functional requirements used as selection criteria (exit-0308).

3.5 Phase D — Procurement and Specifications

Requirements vs specifications (critical distinction)

A specification consists of a metric and its value with appropriate units. Product specifications are a set of individual specifications.

Specification document types:

• Design specification — what the device is made of, geometry, materials
• Performance specification — what it must do (accuracy, flow rate)
• Management specification — QMS processes (ISO 13485) (exit-0642)
• Prescriptive specification — exact manufacturing instructions (less common)

Exam trap: Specification documents in procurement specify requirements of purchased items (exit-0309), not executive vision or prototype usability alone.

When to establish specifications

• Target specifications: early, after customer needs, before concept generation — preliminary ranges
• Final specifications: after concept selected — refined, precise; require trade-offs
• Technology-intensive products: specifications revisited at least twice

Four steps — establishing target specifications

1. Prepare list of metrics (complete, dependent variables, practical; one metric may serve multiple needs)
2. Collect competitive benchmarking information
3. Set ideal and marginally acceptable target values
4. Reflect on results and process

Ways to express metric values:

• At least X — lower bound (higher is better)
• At most X — upper bound (lower is better)
• Between X and Y — bounded range
• Exactly X — avoid when possible (over-constrains)
• Set of discrete values — categorical choices

Five steps — setting final specifications

1. Develop technical model of product
2. Develop cost model
3. Refine specifications; make trade-offs
4. Flow down specifications to subsystems
5. Reflect

Quality Function Deployment (QFD) links customer needs to engineering characteristics via the House of Quality — heavily tested indirectly through needs-to-metrics translation.

Target specification = desired measurable product characteristics, not final dimensions only, not marketing strategy (exit-0421, exit-0615).

3.6 Phase E — Prototype

A prototype is an early version of a design — not the final design, not merely a presentation (exit-0310, exit-0570).

Prototype types

Design specification contains basic elements when creating a prototype (exit-0311).

Prototyping methods

Common: 3D printing, soft tooling, VR simulation, breadboarding.

NOT typical early rapid prototyping default: precision CNC machining (slow, expensive for first iterations) — exit-0572 marks CNC as least aligned with "common rapid prototyping" framing; injection molding is mass production, not early prototype method.

Primary purpose of prototyping: determine feasibility and validate with end-users (exit-0322, exit-0577) — not mass production (reject answer key typo "C" on Q9 of 2024 PDF; correct answer is testing with end-users).

Design tools (exam favorites)

Proteus simulation modes: IDE simulation, real-time, mixed-mode — not "virtual simulation mode" as a named Proteus mode (exit-0331).

Proteus advantage: simulate circuits before physical prototyping; rapid iteration — does not eliminate physical prototypes or ensure regulatory compliance (exit-0573, exit-0576).

Integration pattern: Proteus for circuit design; Arduino for real-world sensor/actuator iteration; Proteus cannot model complex biology (exit-0567 insulin loop — biological limitation, not just calibration).

3.7 Phase F — Test (Verification and Validation)

Prototype testing occurs in Prototyping and Testing stage (exit-0312).

Feasibility analysis (early): assess technical and economic viability — gate before detailed design (exit-0575).

Risk Management Plan (ISO 14971): identify vulnerabilities/hazards and implement preventative measures (exit-0318).

Iterating = repeating stages until design meets requirements (exit-0313) — not starting from zero each time.

Flowcharts = graphical representation of a process (exit-0323).

Detailed design stage designs systems, components, parts to meet functional requirements (exit-0319).

Procurement and specifications stage identifies and obtains equipment, tools, materials (exit-0315).

4. Technical Deep Dive

4.1 ISO 13485 Design Controls

ISO 13485 defines the Quality Management System (QMS) for medical device organizations — not the device performance itself, but the processes ensuring consistent safe design and manufacture (exit-0653).

Design control clauses (conceptual mapping):

Management specification documents QMS requirements including ISO 13485 procedures (exit-0642).

4.2 ISO 14971 Risk Management

ISO 14971 provides the risk management framework — hazard identification, risk estimation, risk control, residual risk evaluation, post-production monitoring.

Risk management in design:

1. Risk management plan at project start
2. Hazard analysis as concepts solidify (electrical, thermal, biocompatibility, use error)
3. Risk control hierarchy: inherent safety → protective measures → information for safety
4. Verification of risk controls linked to design verification
5. Risk-benefit assessment before release

Exam scenarios: Prefer eliminating hazards (larger buttons, simpler IFU) before adding compensating technology with new risks (voice control cybersecurity) — exit-0566 pattern.

4.3 Complete Workflow Example: Low-Cost Pulse Oximeter (Low-Resource Settings)

This worked example mirrors exit-0400 (Q400): primary factor in low-resource design is cost-effectiveness — ruggedness, local maintainability, affordable consumables outweigh premium features.

Step 0 — Mission statement

Develop a fingertip pulse oximeter accurate enough for ward triage, manufacturable below USD 25 BOM, operable by community health workers after 15-minute training, powered by AA batteries or USB, serviceable with locally available spare clip and cable.

Step 1 — Customer needs (interviews: CHWs, nurses, biomedical technicians)

Step 2 — Target specifications (sample metrics)

Benchmarking: Compare against WHO priority device criteria and two market clips (premium hospital unit vs cheap import with motion artifact).

Step 3 — Concept generation (combination table excerpt)

Function decomposition: optical emit → tissue modulation → photodiode detect → AC/DC separation → ratio-of-ratios → SpO₂ lookup → display/alarm.

Step 4 — Concept screening (Pugh; reference = hospital-grade transmittance)

Criteria: cost, battery flexibility, motion robustness, field repair, accuracy.

Combine and improve: Merge A's power architecture with adaptive filtering idea from B → Concept A′.

Step 5 — Concept scoring (weighted)

Select A′ for detailed design.

Step 6 — Final specifications + risk (ISO 14971 snapshot)

Hazards: missed hypoxemia (false negative), unnecessary referral (false positive), electrical leakage, LED eye exposure.

Controls: dual-wavelength calibration protocol; motion flag; IEC 60601-1 electrical safety; IFU limits pediatric finger size.

Step 7 — Prototype pathway

1. Proteus: simulate LED driver, transimpedance amplifier, noise immunity
2. Breadboard + Arduino: test ratio-of-ratios algorithm with recorded PPG waveforms
3. LabVIEW: acquire reference co-oximeter data; compute Bland-Altman limits during V&V
4. 3D-printed enclosure: drop test, outdoor display readability
5. PCB alpha → beta working prototype for field pilot

Step 8 — V&V

• Verification: SpO₂ accuracy vs calibrated simulator; battery life bench test; drop test per spec
• Validation: CHW usability in health post; false alarm rate during walking pediatric patients

Step 9 — Procurement specifications (excerpt)

• Photodiode responsivity at 905 nm: ≥ 0.35 A/W
• MCU: 10-bit ADC minimum, 2× AA boost converter efficiency ≥ 85%
• Display: contrast ratio ≥ 4:1 at 10k lux

Low-resource design lesson (Q400): Cost-effectiveness and maintainability are primary; biocompatibility of a fingertip clip matters but is not the distinguishing design driver vs implantables; "all of the above" overweighting high-tech features is wrong.

4.4 Alternate Example Sketch: Low-Cost Wound Dressing

For non-electronic design exams, the same pipeline applies:

• Needs: exudate management, infection barrier, painless removal, 7-day wear, affordable per cm²
• Concepts: hydrocolloid vs foam vs antimicrobial gauze vs honey-impregnated pad
• Pugh: reference = standard gauze; score breathability, exudate capacity, cost, shelf life
• Specs: fluid handling capacity (g/cm²), MVTR, peel adhesion force
• V&V: ISO 10993 cytotoxicity; clinical wear trial

5. Equipment and Device Focus

5.1 Pulse Oximeter Design Essentials

Primary function: measure oxygen saturation (SpO₂) via red (≈660 nm) and infrared (≈940 nm) absorbance of pulsatile arterial blood (exit-0401).

Design considerations:

• Ratio-of-ratios algorithm; motion artifact mitigation
• Perfusion index gating; low-signal alarms
• Calibration against co-oximeter reference
• Probe fit for pediatric vs adult digits

5.2 Electronic Development Stack

Proteus + Arduino workflow (prosthetic EMG example, exit-0567):

• Proteus: EMG front-end amplifier, motor driver schematic simulation
• Arduino: real-time firmware, sensor integration, actuator control
• Do not expect Proteus to model musculoskeletal dynamics

Smart inhaler power (exit-0568): implement low-power sleep modes between sensor readings — superior to continuous polling or crude sampling rate reduction that misses dose events.

5.3 CAD in Biomedical Engineering

CAD creates digital 3D models of anatomical structures and device geometry for FEA, machining, and additive manufacturing (exit-0402). Role in electronic design: PCB layout (exit-0330).

5.4 Software Selection Quick Reference

6. Practical Biomedical Engineering Perspective

6.1 Ethiopian and Low-Resource Context

Biomedical engineers in Ethiopia face budget constraints, import dependency, and limited biomedical technician density. Design decisions must prioritize:

• Total cost of ownership (not lowest purchase price alone)
• Local spare parts and tooling available in country
• Simplified training and Amharic/afan Oromo IFU where applicable
• EFDA registration pathway alignment early in planning

6.2 Ethics and Clinical Judgment Scenarios

6.3 When Pugh Fails

If usability testing contradicts Pugh winner → re-evaluate with pairwise comparison incorporating new user-feedback criteria — do not ignore clinicians (exit-0579).

6.4 Design Constraints Timing

Formal design constraints (regulatory, sterilization, power, size) established during problem definition / early concept development — before prototyping (exit-0441).

7. Frequently Tested Concepts

EXAM CALLOUT: Master these high-yield clusters: Master these three clusters: (1) requirements vs specifications, (2) customer needs timing and translation, (3) concept selection tools.

7.1 Requirements vs Specifications — Deep Comparison

Common wrong answers:

• Confusing target specification with final dimensions only → it is desired measurable characteristics (exit-0421)
• Confusing procurement spec with executive vision → it defines purchased item requirements (exit-0309)
• Confusing design brief with design specification → spec has measurable technical data for build (exit-0314)

7.2 Customer Needs — Process and Exam Items

Most critical phase for identifying customer needs: Concept development (exit-0422, exit-0617) — not production, not late testing.

Need statement guidelines (from lecture):

• Express in customer language, not engineering jargon
• Be positive (what is needed, not what is wrong)
• Be attribute-free in early statements (avoid prescribing solutions)
• Use importance ratings (***, **, *)

Translation chain:

Customer need → Metric → Target value → Final spec → Verification test

QFD ensures no need is orphaned without an engineering characteristic.

EXAM CALLOUT (product-design-exit-2024): High false-positive rate in a diagnostic → unnecessary procedures (clinical harm + ethics) outweighs 99% accuracy headline.

EXAM CALLOUT (product-design-exit-2024): Coating degrades under standard hospital cleaning → validate cleaning compatibility before launch — not marketing attack on competitor.

EXAM CALLOUT (product-design-exit-2024): Implant in autoimmune population → prioritize device rejection / biocompatibility risk before human trials.

EXAM CALLOUT (product-design-exit-2024): Wearable with continuous transmission → user control over data sharing balances privacy and functionality.

EXAM CALLOUT (product-design-exit-2024): Proteus for circuit simulation; Arduino for firmware/prototyping — Proteus cannot model complex muscle biomechanics; use specialized tools for that layer.

7.3 Concept Selection — Decision Tree

Many rough concepts?
  └─ Yes → Pugh screening (+/0/−)
Few refined concepts with weighted criteria?
  └─ Yes → Concept scoring
Need rigorous pairwise trade-offs?
  └─ Yes → AHP or Pairwise comparison chart
Compare to market leaders?
  └─ Benchmarking
Need real-world performance data?
  └─ Prototype and test

Wearable cardiac monitor comfort + functionality: Concept scoring (exit-0580) — not Pugh alone, not benchmarking alone.

Quantitative alternative selection tool in bank: AHP (exit-0317) — not Pareto, not sensitivity analysis alone.

7.4 Rapid Review Table

Practice each linked question in the app after reading the corresponding subsection.

7.6 Procurement Cycle Overlap (HTM Cross-Items on the exit exam)

Several exam items tagged to Product Design also test HTM procurement vocabulary — know them because they appear on the same exam:

When a stem asks for the first step in equipment planning and budget, answer needs assessment / inventory of clinical requirements (exit-0352) — not jumping to vendor quotes.

7.7 Software and Simulation — Consolidated Trap List

Smart inhaler / closed-loop insulin / prosthetic EMG questions form a repeat cluster — expect one scenario from this trio on any design-themed paper.

8. Comparison Tables

8.1 Pugh Screening vs Concept Scoring

8.2 Target vs Final Specifications

8.3 ISO 13485 vs ISO 14971

8.4 Prototype Types

8.5 Design Process Stage vs Primary Activity

9. Exam-Oriented Memory Aids

9.1 Acronym — SPECS-TRIP

Specifications follow Planning needs
Engineering metrics from customer Expectations
Concepts generated before Concept selection
Screen with Pugh, Score with weights

Target specs early, Final specs late
Risk ISO 14971 throughout
Iterate until requirements met
Prototype proves feasibility

9.2 Pugh Matrix Mnemonic — "RCRCRS"

1. Reference concept
2. Criteria from needs
3. Rate (+/0/−)
4. Combine and improve
5. Rank
6. Select

9.3 Needs-to-Specs Ladder

Need (words) → Metric (number type) → Target (range) → Final (number) → Test (method)

9.4 Tool Picker One-Liner

• Pugh = fast vs baseline
• Scoring = weighted comfort/function
• AHP = math picks winner
• Pairwise = Pugh failed usability
• Proteus = circuits before solder
• LabVIEW = acquire and analyze
• Arduino = firmware brain

9.5 ISO Pair

13485 = Quality (QMS)
14971 = Risk (RM)

10. Chapter Summary

Biomedical product design integrates structured creativity (Ulrich concept development) with regulated rigor (ISO 13485 design controls, ISO 14971 risk management). The exam rewards candidates who:

1. Place customer needs and target specifications in concept development, before detailed design.
2. Distinguish qualitative needs from measurable specifications and procurement documents.
3. Select Pugh screening for early funnel cuts and concept scoring for multi-attribute ergonomic comparisons.
4. Know that prototyping validates feasibility with users — simulation complements but never replaces physical V&V.
5. Apply clinical ethics and low-resource design judgment (Q400: cost-effectiveness first).
6. Map tools correctly: Proteus (circuits), LabVIEW (DAQ), CAD (geometry/PCB), Arduino (embedded control).

The low-cost pulse oximeter workflow demonstrates the full chain from mission statement through Pugh/scoring, risk controls, Proteus-Arduino-LabVIEW prototyping, and V&V — exactly the integrated system-design reasoning the blueprint demands.

Next step: Complete Section 11 practice, then practice related MCQs in the app.md` § Product Design).

11. Exam Practice Section

All questions include full solutions. Difficulty progresses from recall to scenario judgment.

Basic Questions (10 MCQs)

B1. A specification in product design consists of:

• A) A marketing narrative
• B) A metric and its value with appropriate units
• C) A patent claim
• D) A risk hazard list

Solution: B. Per Ulrich Ch.4, a specification = metric + value + unit. Needs are qualitative; specifications are measurable.

B2. Target specifications are established:

• A) After final manufacturing tooling
• B) After customer needs, before concept generation
• C) Only after regulatory approval
• D) During disposal planning

Solution: B. Target specs are preliminary ranges guiding concept generation; final specs come after concept selection.

B3. The goal of concept selection is to:

• A) Eliminate engineering documentation
• B) Develop the best concept by combining and improving alternatives
• C) Avoid prototyping
• D) Select the cheapest concept regardless of safety

Solution: B. Lecture emphasis: goal is to develop the best concept, not merely pick a winner.

B4. ISO 13485 primarily addresses:

• A) Biological evaluation of materials
• B) Quality Management System for medical devices
• C) Clinical trial protocols
• D) Hospital HVAC design

Solution: B. ISO 13485 = QMS. ISO 10993 = biocompatibility; ISO 14155 = clinical investigations.

B5. A prototype is best defined as:

• A) The final commercial design
• B) An early version of a design for learning and testing
• C) A marketing brochure
• D) A regulatory submission dossier

Solution: B. exit-0310, exit-0570.

B6. In Pugh concept screening, "0" means:

• A) Concept rejected
• B) Performance same as reference concept
• C) Best possible score
• D) Missing data

Solution: B. Scale is + (better), 0 (same), − (worse) vs reference.

B7. LabVIEW is primarily used in biomedical product design for:

• A) Mechanical CAD
• B) Real-time data acquisition and analysis
• C) Injection molding simulation
• D) Writing IFU documents

Solution: B. exit-0571, exit-0578.

B8. Which is NOT a common dysfunction during concept generation?

• A) Considering only one alternative
• B) Involving a diverse team
• C) Ignoring competitor solutions
• D) Failing to integrate partial solutions

Solution: B. Involving only 1–2 people is a dysfunction; diverse participation is desired.

B9. The RWW framework stands for:

• A) Reliability, Warranty, Waste
• B) Real, Win, Worth it
• C) Risk, Weight, Workflow
• D) Review, Write, Wrap-up

Solution: B. Product planning opportunity selection.

B10. Design verification asks:

• A) Did we build the right product for the user?
• B) Did we build the product right per design inputs?
• C) Did marketing approve branding?
• D) Did we minimize patent filings?

Solution: B. Verification = outputs meet inputs. Validation = intended use / user needs.

Intermediate Questions (10 MCQs)

I1. What document describes measurable capabilities serving as basis for detailed design?

• A) Design brief only
• B) Design specifications
• C) Disposal record
• D) Purchase invoice

Solution: B. exit-0314.

I2. During design selection, requirements primarily:

• A) Define constraints and functional requirements for comparing concepts
• B) Replace risk analysis
• C) Eliminate need for prototyping
• D) Identify shareholders

Solution: A. exit-0308.

I3. Which stage identifies and obtains equipment, tools, and materials?

• A) Concept generation
• B) Procurement and specifications
• C) Product planning only
• D) Post-market surveillance only

Solution: B. exit-0315.

I4. Feasibility analysis in early development primarily:

• A) Finalizes dimensions
• B) Assesses technical and economic viability
• C) Replaces clinical trials
• D) Automates manufacturing

Solution: B. exit-0575.

I5. Proteus is described as:

• A) Spreadsheet editor
• B) Breadboard and electronic circuit simulator
• C) Hospital inventory system
• D) CT reconstruction software

Solution: B. exit-0325 (both B and C in some stems → electronic circuit + breadboard simulator).

I6. After Pugh selection, usability testing reveals serious flaws in the winner. Best action?

• A) Ignore users; proceed
• B) Re-evaluate using pairwise comparison incorporating user feedback
• C) Abandon project immediately
• D) Skip validation

Solution: B. exit-0579.

I7. For wearable cardiac monitor comparing comfort and functionality across concepts:

• A) Pugh matrix alone
• B) Concept scoring
• C) Patent search only
• D) Autoclave validation

Solution: B. exit-0580 — weighted multi-criteria ergonomic comparison.

I8. A management specification relates to:

• A) LED wavelength
• B) ISO 13485 QMS processes
• C) Patient heart rate
• D) Polymer molecular weight

Solution: B. exit-0642.

I9. Which is NOT an advantage of Proteus simulation?

• A) Time-saving
• B) Cost-effectiveness
• C) Ability to perform physical stress testing
• D) Ease of circuit iteration

Solution: C. exit-0329 — simulation is virtual.

I10. Identifying customer needs is most critical in:

• A) Production scale-up
• B) Concept development
• C) Equipment disposal
• D) Autoclave loading

Solution: B. exit-0422, exit-0617.

Advanced Questions (10 MCQs)

A1. A diagnostic device shows 99% accuracy but high false positives in one demographic. Greatest concern?

• A) Not 100% accurate
• B) Unnecessary procedures from false positives
• C) Manufacturing difficulty
• D) High cost

Solution: B. exit-0564 — clinical harm and ethics of false alarms.

A2. Redesign home BP monitor: elderly struggle with small buttons; voice control adds security risk. Best approach?

• A) Enlarge buttons; simplify instructions
• B) Voice control with security
• C) Two versions
• D) Discourage home use

Solution: A. exit-0566 — ISO 14971 hierarchy: eliminate use hazard before adding connectivity risk.

A3. Competitor surgical coating degrades under standard hospital cleaning. Your best development step?

• A) Marketing attack
• B) Unethical copy
• C) Analyze cleaning compatibility for your design
• D) Abandon surgery instruments

Solution: C. exit-0568 — validate under real reprocessing.

A4. Implantable drug delivery trial in autoimmune-heavy population — prioritize:

• A) Cost-effectiveness
• B) Device rejection risk
• C) Regulatory paperwork delay
• D) Environmental disposal only

Solution: B. exit-0569.

A5. Wearable with continuous transmission — address privacy while keeping function:

• A) Strip all features
• B) User control over data sharing
• C) Hide privacy policy
• D) Transmit anonymously without consent

Solution: B. exit-0570 — privacy by design with granular consent.

A6. Prosthetic with EMG: Proteus lacks muscle modeling. Best integration?

• A) Proteus for circuits; Arduino for real-world control testing
• B) Proteus for biomechanics only
• C) No integration possible
• D) Abandon both

Solution: A. exit-0567.

A7. Smart inhaler battery life — best Arduino strategy?

• A) Continuous sensor polling
• B) Low-power sleep between readings
• C) Only bigger battery
• D) Reduce sampling below dose detection needs

Solution: B. exit-0568.

A8. Proteus shows stable glucose loop; animal trials erratic. Most likely cause?

• A) Proteus cannot model biological variability
• B) Only a coding typo
• C) Ethics not simulated
• D) PCB color

Solution: A. exit-0569 — meal absorption, sensitivity, lag absent in circuit sim.

A9. Primary factor designing devices for low-resource settings (Q400 pattern)?

• A) Cost-effectiveness
• B) Biocompatibility of all externals
• C) Maximum high-tech features
• D) All equally primary

Solution: A. exit-0400 — affordability, ruggedness, maintainability dominate.

A10. Closed-loop insulin discrepancy: simulation vs animal. Risk control lesson?

• A) Simulation suffices for regulatory submission
• B) Biological V&V required; update risk file with observed dosing hazards
• C) Ignore animal data if simulation passed
• D) Skip design inputs

Solution: B. Integrates ISO 14971 — sim gap is hazard; physical testing and risk update mandatory.

Short Answer Questions (10)

SA1. Define product concept vs product idea.

Solution: A concept is a technical description with approximate technology, working principles, and form (sketch + text), evaluable against criteria. An idea lacks sufficient technical detail for feasibility analysis or Pugh comparison.

SA2. List four steps to establish target specifications.

Solution: (1) Prepare metrics list from needs, (2) competitive benchmarking, (3) set ideal and marginally acceptable values, (4) reflect on results and process.

SA3. Name three external search sources in concept generation.

Solution: Lead users, patent databases, published literature — also experts and competitive benchmarking (any three).

SA4. What are design inputs in ISO 13485 terms?

Solution: Functional, performance, safety, and regulatory requirements for the device derived from user needs, standards, and risk controls — forming the basis for design outputs and verification.

SA5. Distinguish verification and validation.

Solution: Verification: confirm design outputs meet design inputs (bench, inspections). Validation: confirm device meets user needs and intended use in realistic conditions (clinical/simulated use).

SA6. Why avoid "exactly X" target specifications when possible?

Solution: Over-constrains design space, prevents trade-offs, and may exclude superior concepts that exceed X on one metric while excelling elsewhere.

SA7. Purpose of opportunity tournament reflection step?

Solution: Assess whether enough opportunities were generated, filtering was biased, charter too narrow, and whether selected opportunities excite the team — continuous improvement of planning process.

SA8. Role of flowchart in design process?

Solution: Graphical representation of process steps — clarifies workflows, software logic, manufacturing sequences for team alignment (exit-0323).

SA9. Why is iterative design essential in medical devices?

Solution: Early assumptions fail bench and user tests; hazards emerge; regulations update — repeating stages until requirements and risk acceptability are met reduces patient harm and costly late rework.

SA10. What is QFD's primary function?

Solution: Quality Function Deployment (House of Quality) links customer needs to engineering characteristics, ensuring each need maps to measurable design features with competitive benchmarking visibility.

Scenario-Based Questions (10)

SC1. A student team skips customer interviews and copies a commercial pulse oximeter schematic. Identify two process violations and consequences.

Solution: Violates customer needs identification and concept generation external/internal search discipline. Consequences: wrong specifications for local power/climate/users; missed hazards; failed validation despite working circuit; regulatory/design control nonconformance.

SC2. Mission: neonatal ward SpO₂ monitor. Nurse needs: "quiet alarms." Engineer spec: "buzzer 90 dB." Fix the error.

Solution: Violated attribute-free need statement and proper translation. Need → metric should be "alarm perceptible to nurse at 3 m without disturbing sleeping infants" → spec might cap SPL, require visual alarm, adjustable volume — derived from further interviews.

SC3. Pugh matrix ranks Concept X highest but manufacturing lead time exceeds hospital tender deadline. Next action?

Solution: Return to combine and improve or final specification trade-off step — merge X's clinical strengths with faster-manufacture architecture; re-score; do not ignore schedule constraint.

SC4. Procurement receives sensors without wavelength tolerance in the spec. Effect?

Solution: Incoming inspection cannot verify compliance; verification gap; risk of inaccurate SpO₂ if supplier drifts — fix procurement specification with metric ± tolerance and acceptance test.

SC5. Field CHWs report oximeter works on adults but not pediatric fingers. Which phase failed?

Solution: Customer needs and validation — pediatric use case not captured in needs/specs; design validation with intended population incomplete.

SC6. Team uses only Proteus results for EFDA submission without bench data. Regulatory gap?

Solution: Missing design verification physical evidence; simulation ≠ clinical performance proof; ISO 13485 requires validated methods on representative units.

SC7. Two concepts tie in concept scoring. Decision options?

Solution: Sensitivity analysis on weights; pairwise comparison; build prototypes of both for critical criterion; combine features per Pugh "combine and improve" philosophy.

SC8. Hospital wants lowest purchase price oximeter. HTM engineer objects. Argue using Q400 principle.

Solution: Cost-effectiveness includes maintenance, spare probes, training, downtime, false alarm referral costs — lowest capital price may raise total cost and patient risk; reference WHO priority device criteria.

SC9. Risk analysis identifies LED eye exposure hazard. Propose hierarchy of controls.

Solution: (1) Inherent: limit optical power, baffling; (2) protective: auto shutoff when probe off finger; (3) information: IFU warnings — document verification per ISO 14971.

SC10. After beta prototype, EMI causes erratic readings near surgical equipment. Iteration path?

Solution: Iterate prototyping/testing → update design outputs (shielding, filtering) → repeat verification EMC tests → update risk file → may revisit final specifications if acceptance criteria change.

Calculation Problems

CALC1. Concept Scoring — Wearable Cardiac Monitor

Criteria and weights: Comfort 0.35, Signal quality 0.30, Battery life 0.20, Cost 0.15.

Ratings (1–5):

Compute totals. Which concept wins?

Solution:

Concept B wins (4.05 > 3.95). If signal quality is clinically dominant, sensitivity analysis raising signal weight above ~0.38 could flip winner — document trade-off in design review.

CALC2. Pugh Screening — Wound Dressing Concepts

Reference: Standard gauze. Count net (+) minus (−):

Solution: Hydrocolloid and Foam tie at +3; Antimicrobial gauze inferior. Proceed to concept scoring or combine hydrocolloid absorption with foam structure for improved concept per Pugh step 4.

CALC3. Target Specification Bounds — Pulse Oximeter Battery

Requirement: operate ≥ 20 h marginal, ≥ 30 h ideal on 2×AA. Bench test: 24 h.

Solution: Meets marginal bound (24 ≥ 20) but not ideal (24 < 30). Design review options: accept with stakeholder sign-off on marginal met, or iterate power firmware (sleep modes per exit-0568) to reach ideal before design freeze.

CALC4. Risk Priority Number (illustrative ISO 14971 math)

Hazard: missed hypoxemia alarm. Severity S=4, Occurrence O=3, Detectability D=2 (scale 1–5). RPN = S × O × D.

Solution: RPN = 4 × 3 × 2 = 24. Team implements alarm limit testing and low-perfusion prompt to reduce O or D; re-evaluate residual risk regardless of RPN threshold policy.

CALC5. SpO₂ Accuracy Specification Check

Spec: ±2% ideal, ±3% marginal vs reference. Prototype errors: +2.5%, −1.8%, +3.1%, +2.2% at calibration points.

Solution: +3.1% exceeds marginal limit → verification fail → iterate optical or algorithm design; cannot transfer to validation until bench compliance achieved.

Answer Key Quick Reference — 2024 Telegram Model Exam (19 items)

*Q11: NOT common prototyping — bank uses CNC machining (exit-0572) as answer; injection molding is production.
†Q9: Prototyping purpose = testing with end-users (B); ignore PDF key "C" error.

Supplement — Wound Dressing Workflow (Alternate Q400 Scenario)

For exams that use consumables instead of devices, apply the same chain:

Mission: Sterile dressing for exuding leg ulcers, ≤ ETB 25/unit, changeable in ≤ 90 s with gloved hands.

Needs → specs: absorption rate (g/24h), wear time (days), peel force (N), bacterial barrier (log reduction), sterility assurance level.

Concepts: hydrocolloid vs foam vs gauze composite via combination table.

Pugh vs imported foam: local foam wins cost (+) and strike-through indicator (+); loses wear time (−) until hybridized with hydrocolloid island.

Procurement spec to local converter: silicone adhesive coat weight, EO/gamma compatibility, peel force range.

Prototype: CNC/laser-cut laminate batches; physical working samples for fluid bench.

V&V: verification = absorption and barrier vs numbers; validation = nurse timed dressing change and patient comfort survey.

ISO 14971: maceration from failed absorption; infection from missed strike-through — control with visible indicator and training label.

This parallel example reinforces that product design process is device-agnostic — the exam tests whether you can name the phase and document type, not memorize one product.

Supplement — Design Input / Output Traceability (ISO 13485 Exam Language)

Regulators and exit items increasingly use design inputs and design outputs vocabulary:

Verification traces output → input (did we meet the number?). Validation traces device → user need in intended environment (did we solve the clinical problem?). Confusing these is as costly as confusing target and final specifications.

Supplement — Opportunity Tournament Numeracy

Lecture emphasis: filter many opportunities early. If 200 ideas → 10% screen → 40% developed one week each → 20% pass RWW, full projects = $200 × 0.10 × 0.40 × 0.20 = 1.6$ → one or two portfolio entries. This explains why product planning is portfolio management, not single-project heroics.

Study sequence after this chapter: Re-read §7.1–7.3, complete app questions exit-0305–exit-0359 and exit-0567–exit-0580, then cross-check HTM procurement items (exit-0352–exit-0365) in Chapter 10 where overlap exists.

End of Chapter 8 — Biomedical Product Design / System Design