Problem Solving - Page 2 of 6

27 Nov How Key Tech Innovates with Quality in Mind

Posted at 18:40h in Engineering Challenges, Problem Solving, Product Design, Project Management, Quality

At Key Tech it is our nature to be creative and think differently. This is how we find the solutions to the toughest technical challenges. Innovation is at the heart of the product development work we do. We just understand that this must be done...

03 Oct Cool It! Full Scope Development of a ‘New Technology’ Med-Device has Key Tech Feeling Chill

Posted at 19:29h in Engineering Challenges, Problem Solving, Product Design, Project Management

CoolTech LLC, a med-tech startup in Baltimore, approached Key Tech with an interesting proposition; could we help them develop their new CoolStat ™ device, used to lower body temperature in patients that have stubborn, unresponsive fever? Their device would cool the patient using nothing but...

31 Jul Understanding Our “Why”: A 20 Year Look Back and Look Forward @ Key Tech

Posted at 19:09h in Business, Engineering Challenges, Problem Solving, Product Design

Are engineers, programmers, physicists and designers born or are they crafted? Is it the unquenchable curiosity about how things work that defines us? Is it the innate passion for taking things apart, figuring out what makes them go, putting them back together, making them better,...

06 Jul The Bubble Challenge Part II : Minimizing the Risk of Bubbles

Posted at 13:51h in Engineering Challenges, Problem Solving

Here's a truism about medical devices: It's impossible to design an application that handles fluids and expect not to have to address the trouble with bubbles. They're a bit like taxes: They're unavoidable, but with advance planning you can minimize the impact. This is the second...

12 Jan Bloody Hell

Posted at 16:32h in Engineering Challenges, Mistakes, Problem Solving, Uncategorized

My colleagues at Key Tech take great pleasure in the fact that I’ve spent years of my career designing blood testing devices, when I tend to faint at the sight of blood coming out of someone. Yet I persist. And I have learned, often the...

17 Nov Integrating Wireless into Medical Devices

Posted at 15:38h in Engineering Challenges, Problem Solving

Patients are increasingly using mobile healthcare devices in the home, and everyone, including patients, caregivers and insurance payers, is interested in access to the wide range of data associated with patient healthcare. This is driving increased demand for wireless communication of healthcare data. While the...

09 Jun Thermal Modeling – Quick!

Posted at 15:22h in Engineering Challenges, Problem Solving

Medical devices often contain built-in heating and cooling elements; diagnostic devices must comply with assay thermal protocols and therapy devices must maintain biologics at optimum temperatures. Performing quick thermal finite element analyses (FEA) on device components early in the design process can help to optimize...

24 Mar No More Batteries! Try Energy Harvesting

Posted at 10:30h in Engineering Challenges, Problem Solving, Product Design

Energy harvesting is a technology that gathers tiny wattages of power from hidden sources such as motion, temperature or vibration. It can generate enough kinetic energy to run your wristwatch and sufficient piezoelectric energy to sparkle your child’s light-up shoes. Modern energy harvesting technology took off...

17 Feb Finding Bite-Sized Solutions to Product Development Problems

Posted at 17:29h in Problem Solving, Project Management

A medical device should work like a clock: simple on the surface while built on a complex collection of interdependent moving parts, from sensors to software, all working together in harmony. Getting from an initial idea to a finished product isn't straightforward. Complex challenges inevitably...

27 Jan Get To Market Faster With These Software Programming Tips

Posted at 18:19h in Engineering Challenges, Problem Solving

Software design for medical devices naturally invokes a paradox. On one hand, you want to have the software completed early. Prototypes can't be tested until the software is in place. On the other hand, you can't fully develop and test the software without the hardware...