Phoenix Ambulatory Blood Pressure Monitor Project
8/10/2008 Meeting Notes


Attendees

 

Status

* Chris: Been working on requirement use cases.
* Larry: Assessing resources at the lab.
* Dick: Been working with Germaine on the database, specifically command line scripts, and working on interface description, specifically between sensor and processor, and am considering USB and analog vs. digital.
* Gerry: Clinical information systems knowledge area and needs.
* Bob: working on the functional requirements of the prototype, especially beat-to-beat heart rate and blood

 

Clinical Information Minitopic by Gerry Werth

The Professional Identity Blues

What is Electrical Engineering?
* What Problems does it solve
* What issues were not previously solvable?
* What issues were not previously recognized?
* How important/Necessary is this Expertise?

What is Cardiology?
What is Clinical Informatics?
Why are organizations advertising for Directors of Clinical Informatics but require no formal education in clinical informatics.

Dealing with information in support of clinical care. Perhaps there is no awareness of its value.
Organizations continue to conduct projects on medical informatics and typically the outcomes are not considered acceptable because a lot of money is spent and the outcomes are not considered useful, but often decrease the value of the informatics.

 

Prototype Requirements by Chris Adams

Use cases and gaping holes.

* Wearer signals the device to log an event
- Assures data-acquisition logic despite sensor failure.
* Technical confirm device functions.
* Technician confirms data acquisition.
* Technician connects device to wearer
* System collects data
* Wearer confirms device is work
* Wearer restarts data collection.
* Technician downloads data to a file.

Wearer Signals Device to Log Event
1. Wearer pushes button
2. System activates status light
3. System logs button down.
4. Wearer observes stratus light.
5. Wearer may pause.
6. Wearer releases button.
7. System logs button-up
8. System de-activates status light.
9. Wearer may pause.
10. Wearer repeats sequence according to predefined code.

Technician Confirms Device Functions

Confirms Data Acquisition.
* Status light

Technician Downloads Data to File
* Status light pattern.
- Start
- Continuation
- Completion

Algorithms
* Waveform peak
* Waveform trough
'* Heart Rate
* Systolic BP
* Diastolic BP

Remaining questions:
* Power management: how to determine if there is sufficient power: Dick will recommend whether there is sufficient value in learning about this from the prototype and what behavior is to be observed.
* Data Acquisition: how confirm to it is making a measurement. Can an on-off switch and an on-off light provide sufficient information and is it easy to do this.

 

 

About This Page

This page is maintained by Ellis S Nolley. It was last updated on 24 August 2008.

The author(s) provide this information as a public service, and agree to place any novel and useful inventions disclosed herein into the public domain. They are not aware that this material infringes on the patent, copyright, trademark or trade secret rights of others. However, there is a possibility that such infringement may exist without their knowledge. The user assumes all responsibility for determining if this information infringes on the intellectual property rights of others before applying it to products or services.

Copyright (C) 2008 Ellis S. Nolley. Copying and distribution of this page is permitted in any medium, provided this notice is preserved.

Back to the Meeting Archive Page

Back to the Phoenix Home Page