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

Let's Not Mess Around with Security on our Personal Systems Either!

Essential Security Practices for Your Personal Systems Ensuring a minimal level of cybersecurity, privacy, and availability on your personal systems means you need to manage the following essential practices. This is a brief overview of recommendations from sources like CISA, NSA, etc., focused on personal laptop, phone, and other systems' security. Anti-virus  I've found you'll get the best anti-virus protection and usability from a paid product - I've always had good luck with Norton labeled products. If you are looking for current vendor offerings see:  https://www.pcmag.com/picks/the-best-antivirus-protection Regardless of whether you choose to use a commercial product or open-source anti-virus tool, it is absolutely something you need to use. This is the minimally needed level of system security. Once installed, ideally, it should be invisible until there's a security problem it can't prevent or solve.   Backups You need to have at least a minimal level of ...

RACI, Cybersecurity and NICE Framework

The NICE framework from a RACI point of view The NICE framework ( NIST SP 800-181 rev. 1) established a standard approach for describing cybersecurity work, in order to help stakeholders share a common language and ideally improve how to identify, recruit, develop and retain talent. It breaks down cybersecurity work role categories into: Oversight and Governance; Design and Development; Implementation and Operation; Protection and Defense; Investigation.  Which is very cybersecurity-centric and not related to common tools for project management within companies. Especially smaller enterprises that do not have dedicated people to mange and coordinate cybersecurity needs. A  RACI chart  is   a project management tool used to define and clarify roles and responsibilities within a project team.   It stands for Responsible, Accountable, Consulted, and Informed, and visually represents who is responsible for what, who is accountable for the outcome, who needs to be c...

Typescript - It might not be easier, but but it's surely different

Typescript is a statically typed language, that is a superset of JavaScript. I've had the discussions and debates about that aspect of the language. I am all for static typing. Any way my tools can help me be better is alright by me. So I avoid the ' any ' type designation and make sure I have guards on ' unknown ' types, as much as I can.  Any  does not carry any useful type information, while unknown does, and allows it to enforce type checking.  Anything can be assigned to a variable of type unknown , but an unknown value cannot be assigned to variables of other types without explicit type assertion or narrowing. Similarly, no operations are permitted on an unknown value until its type is refined. This behavior ensures type safety and prevents runtime errors. (Refined with help from google). I bring this up because I was arguing with the compiler recently because I'd assumed both made no use on any type information in any circumstance - because I haven't ...