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

Attendees

• Chris Adams
• El Nolley
• Bob Schlentz
  
  

Requirements by Chris Adams

Slide 2 of:

http://www.phoenix.tc-ieee.org/014_Systems_Architecture_and_Engineering/presentations/Phoenix%20Sys%20Req%202008-03-10.ppt

Table of Contents
I. Mission
II. Scope
III. Stakeholders
IV. Goals & Goal Conflicts
V. Dictionary
VI. Scenarios & Exceptions
VII. Requirements
VIII. Justifications
IX. Assumptions
X. Agreed Priorities
XI. Acceptance Criteria
XII. Parking Lot (for items not addressed)

Mission
* Develop an ambulatory blood pressure monitor
- Inexpensive
- Unobtrusive
....
* Develop a means for chronobiological analysis of the collected blood pressure measurements.
* Be a Learning Community
* Deliver the monitor an analytical framework to the Halberg Chronobiology Center (stakeholder)

Scope
* Monitor measures the Wearer
* Wearer records observation s in the Diary.
** Administrator and Physiologist use Data Analysis Software to assess the data collected by the Device.
Diary influences the interpretation of the data.
&* Wear optionally tracks results in a personal Health Record System
* Clinical settings =>

Phoenix must interface 5 systems
* 3rd Party Data Analysis Software
* 3rd Party Personal Identification System. (vendors, public health & policy, researchers)
* Critical Care Support System (stakeholder is clinician)
* Critical Health Record System. (stakeholder= payer, medical insurance)
* Personal Health Record System (patient, consumer advocacy groups).

Dictionary
* Wearable
* Activity of daily living

A quality check is are all the stakeholders referenced in a scenario.

Value Requirements

Requirements
* Will be decomposed by functional and use scenarios.
* Algorithm requirements.

About This Page

This page is maintained by Ellis S Nolley. It was last updated on 22 March 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