* Mary Jo: Got data and good signal. Now needs to do the cross
correlation.
* Larry Beaty: Tom and he discussed the Sphygmochron spreadsheet
with Franz and Germain and identified graphs. He is meeting with
Grand Avenue Software to ask them: 1) is productization regulated,
2) who is responsible, 3) when should we get FDA involved? When
do we cross over the line from analyzing data to diagnosing?
He needs source control selection and an umbrella structure on
SourceForge.
* Gerry Werth: Been working on clinical coding and open source
tools.
* Chris: Been working on his presentation and it will take two
sessions. His objective is to assure we understand the data analysis
so that we can construct the solution.
* Mike: Is working on characterizing the waveform. Wants to measure
blood flow and calibrate the sensor. What happens when you go
outside?
Presentation on Test-Drive Software Development by Larry Beaty
Criticisms include:
* Longer development time
* Miss the boat:
- Software development cycles take months to years.
- Freeze requirements and requirements change.
* Agile Methodologies
- Allow requirements to change.
- Continuous software evolution
* Extreme Programming
- Test Drive Development
- Examples: Grand Avenue Software, Daimler-Chrysler
- Extreme Programming drives Test Driven Development (TDD)
- TDD provides an automated test mechanism and development mechanism.
* Test Driven Design vs Test Driven Development. They are different.
Test Driven Development was created by Ken Beck.
Definition - Test Driven Development:
* Software development process
* Write tests first, the tests determine what code is to be written.
* Testing is done.
Process:
* Write a test that fails
* Write a line of code.
* Show that it succeeds.
* Refactor: Determine if it is this really needed?
Technique:
* Write a single failing test
* Run the failing test. Prove that the test is correct.
* Write minimal code that fixes the test.
* Run the test again. Prove that the code is correct.
* Refactor towards a better design.
* Run the test again.
- Proves that the better code is still correct.
Define Refactoring:
* Eliminate everything that isn't necessary.
Mock Resources
* Code that emulates the resources that are prohibitively difficult
to obtain now but are required.
Technique 3
* Just test the higher-level function.
* Test the new higher-level code.
* Test the new lower level code.
* Prove that the lower level called the higher level.
Clinical Coding Minitopic - Gerry Werth
History
* PF: Problem focused
* EPF: Expanded problem.
How to document in real time and it would score in real time.
(Gerry used HTML SLIDY - Slide Shows in HTML).
Clinical Information for Business
* Documentation Standards.
- Bullet Point count for history
- Bullet Point Count for Physical Exam/ Organ System
* Clinical Interface
- How to assist the clinical to document to these standards.
- Real time Display of current level score.
This page is maintained by Ellis S Nolley. It was last updated on 20 April 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