Status
* Larry: He has been working on website design and has others
using the blood pressure monitor. Been working with Franz to get
specific information out of the IRB. No one has done this before;
their current rules require that the researcher can talk to them
in person to assure that they understand the risks of the risks.
Bob noted that there are always subject needs that are not understood
by researchers. Chris noted that in requirements analysis, there
is an assumption that software engineers are in the same room
as the analyst is in the same room as the stakeholder. IRB's main
concern is assuring that there is informed consent in the subjects
and the interaction between the researcher and the subjects. We
discussed that this is done with patient management systems, but
the patients have a strong relationship with the data acquisition
process, so they give their consent. What about those who don't
have such a strong relationship to the data collection organization,
i.e. Arbitron or Neilson in measuring entertainment preferences?
The IRB is involved whenever data is collected for potential publication.
We asked if members of the IRB were using a monitor they might
be predisposed to help us. In such a case, the IRB member would
have to recuse themselves, and it might create an adverse reaction.
The IRB is protection against causing harm and we shouldn't try
for a quick solution, but a good solution that satisfied their
mission and provided a good research outcome. Chris thought that
separating the data collection system from an identity management
system could satisfy these needs, so that the data collection
system never knows the personal identify. We thought that sounded
like an encryption key server. Germaine said they only needed
to distinguish the data from another data point and to match with
another data point from the same person for longitudinal studies,
and for follow up. Larry called it "identify escrow".
* Bob: Has been thinking about hardware requirements. Wants blood
pressure measurement, and max and min. Chris thinks that we need
a requirements specification. Can formalize the systems requirements
specification so that we can spawn off more subprojects. Or work
on the Java prototype of the Sphygmochron. The project seems to
need a requirements and Chris would like to do that so that we
can effectively engage volunteers without them attending meetings
in the Twin Cities. Larry asked if we were ready to write a requirements
specification. Are the prototypes of the "unsolved problems"
far enough along, like sensors and power? Chris thought they were,
and it is a matter of trade-offs. Larry: Can we supply the functionality
with something as simple as a micro. Chris: It's just a matter
of documenting what we know. Requirements are needed to develop
prototypes and prototypes lead to changes in requirements. It
is an iterative process among systems requirements specification
and architecture. You need architecture to allocate requirements
and requirements are need to validate the architecture and complete
it.
* Chris: what he wants to use him for is someone to review the
requirements. Someone who has the advantage of being a quality
check on the requirements and g3etting him involved in the project.
* Dewayne: Franz requires that he have fun, but he isn't having
fun. He wants to use Java to analyze data but he hates it. Chris
will look at it. It doesn't plot his data. He publishes the data
plot of the Sphygmochron and send it to the printer. He has magnetic
field data for the last 5-7 years. Likes the idea of Java's buffered
image, but wants to preview it. Java only prints to the printer
at 72 dots per inch. Chris asked if he is using the Sun JDK latest.
Has he used any 2D plotting programs like Matlab. Dwaynes problem
in Java is, "Do you have a buffered image that you can send
to the printer. We suggested SciLab, an open source alternative
to MatLab.
* Mary Jo: She just returned to the Twin Cities. She met Inanc,
they made a board, talked about two inputs, their project is due
5/27, didn't have access to LabView and MatLab, and 500G external
HD. She gave them her data, they want to solve the constants in
another way, they don't have the exercise data, just the "at
rest", they need more data. There were 5 people at the sensor
meeting.
This page is maintained by Ellis S Nolley. It was last updated on 13 May 2007.
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) 2007 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