Patient Monitor (Scope)

(Previous article: https://medium.com/abhishek-pratapa/patient-monitor-introduction-820cc8eb32e#.om448g9wm)

Introduction

The first thing to do when starting any project is to define what you want to do, more specifically a scope. In this article I go through how to create scope, and how to approach making a scope.

I’m not saying that this is the way to do it. Nor am I saying that from a corporate perspective this scope is enough, its not. However, if your a builder or an aspiring entrepreneur this would be the bare minimum needed to complete a project successfully. This article, in my opinion, isn’t technical per se. Its the first step to creating a blueprint for the whole project.

When determining the scope for any project, I think you must know what you want from the project, and more importantly what you don’t want from the project. I break this down into the technical spec and functional spec. These are listed Below

What we want the Patient Monitor to do

  1. SpO2 readings
  2. Blood Pressure Sensor
  3. EEG readings
  4. feedback including an LCD and a speaker

What we don’t want the Patient Monitor to do

  1. Electrocute the patient
  2. Be Expensive
  3. Die if power to the device runs out
  4. Dirt clog up the internals
  5. Get Fried due to voltage fluctuations

As you can see, the first is to define what components you want in your device, the second are contingencies that you want to consider when designing the device. Both are necessary. Also notice, in the spec above nothing is said about certain visual aspects of the device. Including things like size and shape is okay, but things like colors are unnecessary.

The next step is to design a technical spec. This may or may not require an engineering background, depending on how good you are at Googling. Remember, you are only making an MVP that follows the specs above. Maybe all of them, or maybe not all of them depending on your engineering expertise. You may make one prototype, or you may make many prototypes that embody a certain feature or sets of features. Prioritizing the features above is important. A technical diagram for the patient monitor is shown below.

Technical Diagram for the Patient Moniter

As you can see, its a pretty high level diagram of the workings of the patient monitor. I know it may seem trivial, but its gonna serve as a blueprint later on when we design the device.

Conclusion

In summary, creating a technical and functional diagram is crucial to the success of any project in my belief. Realizing the key components serves as a guide to what direction to take the technology. The next article is going to be about prototyping the device. Look forward to it in the coming days.

If you have any comments, questions or critiques, please email me at: abhishekpratapa@gmail.com

This series is for you, so let me know how I can help. I wish the best in all of your current and future endeavors.

Best,
Abhishek Pratapa

Like what you read? Give Abhishek Pratapa a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.