Skip to main content

Training Aids and Standards Automation

While reading through a mountain of standard operating procedures related to my company's policies for the development and operation of medical devices, it occurred to me that being fully aware of and to make full utilization of sed policies requires a full-time position. This not necessarily reasonable for everyone involved in the process of engineering medical devices and information systems in support of the same.

The scope and complexity of so many procedures also incurs a tremendous amount of overhead. Time and money spent performing many boilerplate tasks is time and money that can be spent providing better value elsewhere.

I am reminded of AWS's "Well Architected Framework" or "Well Architected Tool" (whatever it's being called). The WAF or WATool provides a comprehensive strategy and checklist for meeting various important criteria in an AWS deployment. The content and guidance could easily be externalized and declarative and therefor easily extensible for capturing baseline and evolutionary system state.

Come up with a taxonomy that supports a decalrative model to capture and guide persons to achieve comprehensive policies over stringent product development lifecycles.

Comments

Popular posts from this blog

Astronauts?

Something happened today that me disturbed. I didn't notice this "thing" that has been occurring over the past two months, but had I, I'd have spoken out sooner. Today, Blue Origin sent another group of tourists into space for a short time. The headliner was William Shatner, a cultural icon. I'm happy for him and the rest of the group for being able to have the experience. This isn't the thing that's bothering me. On their descent back to earth, the mission control commander dubbed them America's newest astronauts, designating them an incremental astronaut number somewhere in the 500's. Astronauts? If what they did, which was to sit in a seat, qualifies them as astronauts, then everyone flying as passengers on an airliner should be anointed "pilots". Correct me if I'm wrong, but astronauts spend decades learning and practicing science, engineering, or aeronautics before applying to and being accepted into one of the most rigorous prog...

Judging UCSD's HealthHack 2016 this Weekend

This weekend, I will have the opportunity to advise and judge some 200 UCSD engineering students during this year's HealthHack . I am excited and honored to represent my company ( ResMed ) while also getting an opportunity to meet some motivated and talented students. From the "brief" briefing I received, my responsibilities include assisting various teams of competitors develop their prototypes and judging the entries in the end to select an overall winner.

Introduction to Spring Roo Shell

Spring Roo is available as a CLI shell-style application and as an STS plugin. Since I'm not a fan of the Eclipse IDE (no offense and I don't need to debate it), the focus will be on using the CLI. The first step is to download the latest release from the Spring Roo project homepage . Before getting too far into it, it will be helpful to understand some basics about the Roo Shell (RS) application. The startup script can be used to bootstrap RS commands or to simply launch the shell program when no commands are included. The commands are applied relative to the current working directory, so be prepared for that. The recommended approach is to unpack the Spring Roo distribution to its own folder, add its /bin directory to the path, and execute RS from your project directories. This will become more obvious in the examples below. To keep it simple, I've created a directory under my Linux home directory and unpacked the distro: ~ $ mkdir spring-roo ~ $ cd spring-roo/...