Why Science? | MedTech Catapult

Official A*STAR sources describe a national initiative for high-value life-science instruments and regulated medical devices. It combines engineering resources with partners in design, manufacturing, quality and regulation to close the gap between proof of concept and commercial product.

A medical device succeeds through a whole product system: user need, intended use, engineering, usability, risk control, manufacture, service and evidence. A clever prototype is an important start rather than the finish line. The practical capability is institutional literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “MedTech Catapult accelerates productisation” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Participation does not guarantee regulatory clearance or commercial success.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Next chapter

Needs finding observes users, patients, workflow and existing alternatives before fixing a solution. The need statement identifies the problem, population and desired outcome without embedding an untested device concept. Evidence of burden should be distinguished from market enthusiasm.

Design teams learn quickly when each prototype answers a defined question. Early models may explore geometry or workflow, while later builds test performance, reliability and production methods under controlled conditions. The practical capability is needs-finding literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “A meaningful need precedes a device” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A serious clinical problem does not prove a proposed device will solve it.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

The intended use names purpose, user, population, environment and relevant conditions. It informs classification, hazards, usability and tests. Expanding to a new user or indication can change risk and evidence obligations.

Manufacturing partners contribute process knowledge that can change the design. Tolerances, assembly, inspection, suppliers and servicing should be considered before the product is frozen. The practical capability is intended-use reasoning. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Intended use sets the evidence boundary” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A device should not be promoted beyond its supported intended use.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Teams translate observations into requirements for performance, size, timing, cleaning, alarms, connectivity, transport and service. Each requirement should be testable and traceable to a need or control. Conflicting requirements require a documented trade-off.

Regulated product development rewards clear decisions. Requirements, hazards, tests, deviations and revisions form a connected design history that another qualified person can inspect. The practical capability is requirements engineering. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “User needs become measurable requirements” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A stakeholder preference is not automatically a validated requirement.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Mechanical, optical, electrical, fluidic, biological and software subsystems interact. Interface definitions protect teams from local changes that break the whole product. Budgets for power, heat, accuracy, latency and space make trade-offs visible.

A medical device succeeds through a whole product system: user need, intended use, engineering, usability, risk control, manufacture, service and evidence. A clever prototype is an important start rather than the finish line. The practical capability is systems architecture. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Architecture manages interfaces” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Successful components do not guarantee an integrated system will work.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Regulatory class and route depend on intended use, jurisdiction and rules. Early planning identifies standards, studies, documentation and manufacturing controls that may be needed. Official decisions remain with the responsible authority.

Design teams learn quickly when each prototype answers a defined question. Early models may explore geometry or workflow, while later builds test performance, reliability and production methods under controlled conditions. The practical capability is regulatory literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Classification and regulatory planning follow risk and use” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A similar-looking product may have a different regulatory classification.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Use-related risk can arise from labels, controls, displays, setup, maintenance or environment. Teams identify critical tasks, study representative users and revise the interface. Training can support safe use while not compensating for avoidable design problems.

Manufacturing partners contribute process knowledge that can change the design. Tolerances, assembly, inspection, suppliers and servicing should be considered before the product is frozen. The practical capability is human-factors reasoning. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Human factors protect real users” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A successful expert demonstration does not validate use by the intended population.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Sketches, mock-ups, benchtop models and engineering builds serve different purposes. A prototype can explore workflow before expensive architecture decisions. Its materials and tolerances may not represent production.

Regulated product development rewards clear decisions. Requirements, hazards, tests, deviations and revisions form a connected design history that another qualified person can inspect. The practical capability is prototyping strategy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Prototypes should answer one question at a time” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A proof of concept is not evidence of reliability or manufacturability.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Design planning, inputs, outputs, reviews, verification, validation, transfer and changes form a traceable development history. Reviews bring independent perspectives to unresolved risks. Records should show why a decision was made, not only what changed.

A medical device succeeds through a whole product system: user need, intended use, engineering, usability, risk control, manufacture, service and evidence. A clever prototype is an important start rather than the finish line. The practical capability is design-control literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Design controls connect decisions” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Documents created after the fact do not replace controlled development.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Verification uses inspection, analysis or tests to show design outputs meet input requirements. Methods need representative samples, calibrated equipment and predefined acceptance criteria. Coverage should include normal operation and specified limits.

Design teams learn quickly when each prototype answers a defined question. Early models may explore geometry or workflow, while later builds test performance, reliability and production methods under controlled conditions. The practical capability is verification reasoning. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Verification checks specifications” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A passed subsystem test cannot establish every system requirement.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Validation evaluates the final or production-equivalent product in relevant conditions with representative users or evidence. It asks whether the device supports the intended purpose. Clinical evaluation may be part of the evidence depending on the product.

Manufacturing partners contribute process knowledge that can change the design. Tolerances, assembly, inspection, suppliers and servicing should be considered before the product is frozen. The practical capability is validation literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Validation checks user needs and intended use” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Validation in a convenient setting may not represent actual use.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Material choice affects strength, cleaning, sterilisation, chemicals, ageing and biocompatibility. Contact type and duration guide evaluation. Supplier or process changes can alter the finished surface even when the nominal material name stays the same.

Regulated product development rewards clear decisions. Requirements, hazards, tests, deviations and revisions form a connected design history that another qualified person can inspect. The practical capability is materials-safety reasoning. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Materials and biological contact shape safety” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A biocompatible raw material does not automatically make the finished device safe.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Sensors, light sources, detectors, power and signal processing must operate across expected environments and ageing. Calibration relates output to reference quantities. Electromagnetic compatibility and electrical safety may matter depending on the design.

A medical device succeeds through a whole product system: user need, intended use, engineering, usability, risk control, manufacture, service and evidence. A clever prototype is an important start rather than the finish line. The practical capability is instrumentation literacy. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Electronics and optics need tolerance and calibration” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A precise laboratory module is not automatically robust in a fielded instrument.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Software requirements, architecture, testing, anomaly handling and version control should match risk. Connected products also need authentication, updates, vulnerability response and safe failure modes. Data privacy and device safety overlap but are not identical.

Design teams learn quickly when each prototype answers a defined question. Early models may explore geometry or workflow, while later builds test performance, reliability and production methods under controlled conditions. The practical capability is software assurance. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Software and cybersecurity remain product responsibilities” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Encryption alone does not establish a secure or safe product.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Tolerances, assembly, inspection, tooling, service and supplier capability influence design. Local contract manufacturers can identify process constraints and cost drivers. Pilot builds reveal whether instructions and controls produce consistent outputs.

Manufacturing partners contribute process knowledge that can change the design. Tolerances, assembly, inspection, suppliers and servicing should be considered before the product is frozen. The practical capability is manufacturing readiness. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Design for manufacture begins before transfer” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A buildable unit is not yet a validated production process.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

A quality system controls records, suppliers, nonconformances and corrective action. Sustainable design considers materials, energy, service, lifetime and end of life. Business evidence tests value, price, reimbursement, scale and support without weakening safety.

Regulated product development rewards clear decisions. Requirements, hazards, tests, deviations and revisions form a connected design history that another qualified person can inspect. The practical capability is responsible productisation. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Quality, sustainability and economics share decisions” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: A lower-cost design is not better if it shifts risk or lifecycle burden.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter · Next chapter

Archive need statement, intended use, requirements, architecture, risk file, design versions, prototypes, verification, validation, usability, software, suppliers, manufacturing lots, deviations and regulatory status. Students can practise safe product-design reasoning while qualified teams control regulated development.

A medical device succeeds through a whole product system: user need, intended use, engineering, usability, risk control, manufacture, service and evidence. A clever prototype is an important start rather than the finish line. The practical capability is MedTech career preparation. Keep the question, method, controls, observation, uncertainty, review and next decision in one evidence receipt. That record makes progress visible without enlarging the claim beyond the stage reached. MedTech Catapult and its partners control current project selection, engineering resources and released results; product owners, manufacturers, healthcare institutions and regulators control qualification and use.

Put this into practice by turning the idea into a small, reviewable action: Build a dated evidence card for “Keep a medical-device evidence receipt” with the question, method, observation, limitation and next test. Then ask what the resulting note or artefact actually demonstrates. A useful record names context, source or instruction, action, observation, interpretation and uncertainty. It also preserves this limit: Only current responsible authorities can approve manufacture, marketing and clinical use.

An evidence check keeps confidence proportional to what the work can show. Separate the original observation or official statement from the learner’s explanation. Record feedback and any revision. If information is missing, write “not shown” or “not yet known” rather than guessing. That honest gap can become the next question.

Contents · Previous chapter