Skip to main content

Right time, right place - new diagnostic devices


In watching advances in medical devices, it's obvious the trend is pushing devices out into patients hands. This allows diagnostic tests to happen when they are needed during the patients normal life, rather than simply at the point of care. This allows right time diagnostics.  For other patients isn't the necessity of catching a problem at the right time, but getting the diagnostic devices to where the patient is, rather than the patient coming to the diagnostics. This allow devices to be in the right place.

This is enabled by the ubiquity of smartphones - capable computers which disguise themselves as consumer communications devices. In this arena, there is a recently introduced ECG device from Sanatmetal called WIWE. It communicates via Bluetooth to the users smartphone, which provides the visual output and feedback as well as communications back to the clinicians who will use the data collected. This is a good example of creating a "Right Time" diagnostic tool. It's only a single lead ECG, but it is enough to capture a fleeting bout of cardiac arrhythmia. Often an in-clinic ECG offers no tell-tales of arrhythmia's and the other options are longer term portable monitoring (such as a Holter) and hope.

An example of a "Right Place" diagnostic tool, is a handheld colposcope for cervical screening. This is an easily portable device, that again relies on a smartphone. Cervical cancer screening and detection is much lower in places where the few fixed colposcopes are difficult for women to access. This mobile device also simplifies testing, ideally making it easier, more comfortable and less error-prone.

For details on the ECG collection device, you can see the WIWE website: http://mywiwe.com/en/
For details on the cervical screening device, see the Duke university site: http://pratt.duke.edu/about/news/ditch-the-speculum.

Comments

Popular posts from this blog

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...

Threat Modeling Manifesto

Secure Your Code with Threat Modeling As a software developer, security should be a top priority. By proactively identifying and addressing potential vulnerabilities, you can significantly reduce the risk of breaches and data loss. What is Threat Modeling?   Threat modeling is a systematic approach to identifying, assessing, and mitigating security threats. It involves looking at your system from a hacker's perspective to uncover weaknesses and devise strategies to protect against attacks. See the  OWASP Cheat Sheet   Why is Threat Modeling Important? Proactive Security: By anticipating potential threats, you can take steps to prevent them. Risk Mitigation: Identify and address vulnerabilities before they can be exploited. Regulatory Compliance: Adhere to industry standards and regulations. Enhanced Security Posture: Strengthen your overall security posture. How to Get Started with Threat Modeling   The Threat Modeling Manifesto provides a valuable framewor...

When you're the Hero - is it all good, or does it have a dark side?

Examining the risks of IT hero culture This ISACA article examines a situation that is commonplace - since people often have an uneasy working relationship with technology, such that if one is able to help such a person out of a jam and save hours or more of work, for instance, then one is lauded as a hero in the eyes of the person saved.  This article presents how this model is sub-par, wearing on both the heroes and those counting on them, resulting in an unsustainable situation. This is directly related to the sorts of relationships that project and program managers have with cybersecurity: they bring in cybersecurity expertise to apply patches on-top of code and systems to perform 'cybersecurity' rather than making it a fundamental characteristic of the built system - from design through maintenance. Unfortunately we are in a time and world of persistent threats and supply chain vulnerabilities. Cybersecurity is an everyday, everybody, all-the-time activity, broken out of t...