<?xml version="1.0" encoding="iso-8859-1"?>
<?xml-stylesheet type="text/xsl" href="srs.xsl"?>

<srsdocument>

<team>BE Design Team 050001</team>

<doc>
	<template>Beta</template>
	<version>2.0</version>
	<for>Project Heart Attack Detection</for>

</doc>

<revhistory>

	<revision>
		<date>09/20/2006</date>
		<version>1.0</version>
		<description>Initial version</description>
		<author>Nicholas Lavin</author>

	</revision>
	
	<revision>
		<date>09/22/2006</date>
		<version>1.1</version>
		<description>Added glossary and stakeholders.</description>
		<author>Nicholas Lavin, JR Shampang</author>
	</revision>

	<revision>
		<date>09/22/2006</date>
		<version>1.2</version>
		<description>Added more goals.</description>
		<author>Nicholas Lavin</author>
	</revision>

	
	<revision>
		<date>9/24/2006</date>
		<version>1.3</version>
		<description>Formatting.</description>
		<author>JR. Shampang</author>
	</revision>
	
	<revision>

		<date>10/2/2006</date>
		<version>1.4</version>
		<description>Added UC1.</description>
		<author>JR. Shampang</author>
	</revision>
	
	<revision>
		<date>10/4/2006</date>

		<version>1.5</version>
		<description>Corrected document</description>
		<author>Elizabeth Keyes</author>
	</revision>
	
	<revision>
		<date>10/7/2006</date>
		<version>1.6</version>

		<description>Added product description, risks. Modified constraints and executive summary.</description>
		<author>JR. Shampang</author>
	</revision>
	
	<revision>
		<date>10/8/2006</date>
		<version>1.7</version>
		<description>Proofreading Revisions</description>

		<author>Kieran Easter</author>
	</revision>
	
	<revision>
		<date>10/8/2006</date>
		<version>1.8</version>
		<description>Improved glossary, edited goals.</description>
		<author>JR. Shampang</author>

	</revision>
	
	<revision>
		<date>10/9/2006</date>
		<version>1.9</version>
		<description>Changed goals, modified risks, added work context image.</description>
		<author>JR. Shampang</author>
	</revision>

<revision>
		<date>10/11/2006</date>
		<version>1.10</version>
		<description>Modified work context diagram and work context table.</description>
		<author>JR. Shampang</author>
	</revision>

<revision>
		<date>10/15/2006</date>
		<version>1.11</version>
		<description>Modified goals.</description>
		<author>Adam Patterson</author>
	</revision>

<revision>

		<date>10/16/2006</date>
		<version>1.12</version>
		<description>Requirements and assumptions update</description>
		<author>Team</author>
	</revision>
<revision>
		<date>10/20/2006</date>

		<version>1.13</version>
		<description>Meeting update</description>
		<author>Nicholas Lavin</author>
</revision>
<revision>
		<date>10/21/2006</date>
		<version>1.14</version>

		<description>Nonfunctional Requirements addition</description>
		<author>Elizabeth Keyes</author>
</revision>
<revision>
		<date>10/22/2006</date>
		<version>1.15</version>
		<description>Requirements changes and removed User requirements (redundant)</description>
		<author>Adam Patterson</author>
</revision>
<revision>
		<date>10/22/2006</date>
		<version>1.16</version>
		<description>Refined requirements.</description>
		<author>JR. Shampang</author>
</revision>
<revision>
		<date>10/04/2007</date>
		<version>1.17</version>
		<description>Updated to reflect changes in the project.</description>
		<author>Elizabeth Keyes and Nicholas Lavin</author>
</revision>
<revision>
		<date>10/12/2007</date>
		<version>1.18</version>
		<description>Began to bring the document up to date with the current version of the project.</description>
		<author>Nicholas Lavin</author>
</revision>
<revision>
		<date>01/08/2008</date>
		<version>2.0</version>
		<description>
		Finish bringing document up to date with the project in preparation for the System Design Review 2 document.
		</description>
		<author>Nicholas Lavin</author>
</revision>
</revhistory>

<tabofcontents/>

<exesummary>
This System Requirements Specification describes the functionality and requirements stated by Biomedical Engineering Team 050001 in regards to the Heart Attack Detection System. This document ascertains the people involved with this product, the metrics for success, and the constraints and risks involved with the creation of this product.
</exesummary>

<prodescription>
<a href="#glossary">Myocardial infarction (MI)</a> is the leading cause of death for men and women worldwide. Early detection of MI has become a vital concern in the medical industry. People experiencing chest discomfort are at risk, and early diagnosis and treatment can prevent fatal heart damage from occurring. Medical professionals continue to pursue an efficient means of detecting and preventing a MI.<br /><br />

Biomedical Engineering Team 050001 aims to create a system that can determine the stage of myocardial infarction from a chest pain patient by analyzing a sample of the patient's blood. The system will determine the status of myocardial infarction within a reasonable time so that medical action can be taken if the patient is discovered to be suffering from a myocardial infarction. By analyzing the blood sample for enzymes and protein complexes that occur during myocardial infarction, the system will be able to calculate pertinent information from the blood sample, which a physician can then examine to determine a diagnosis.<br /><br />

</prodescription>

<progoals>
	<goal>
		<description>
			The lives of myocardial infarction victims will be saved through early detection of myocardial infarction.
		</description>
		<advantage>
			Myocardial infarction victims will live longer.
		</advantage>
		<metric>
			System will correctly detect myocardial infarction in 95% of tests.
		</metric>
	</goal>
	
	<goal>
		<description>
			System will detect myocardial infarction earlier than existing alternatives.
		</description>
		<advantage>
			System will have a greater value to customers making it easier to distribute.
		</advantage>
		<metric>
			Myocardial infarction detection time reduced by 95% from existing alternatives.
		</metric>
	</goal>
	
	<goal>
		<description>
			Medical professionals using the system will have an easier time providing diagnoses to patients.
		</description>
		<advantage>
			Facilitating diagnosis process allows medical professionals to tend to patients more quickly.
		</advantage>
		<metric>
			90% of medical professionals surveyed approve use of machine.
		</metric>
	</goal>
</progoals>


<stakeholders>
	<group>
		<name>Biomedical Engineering Team 050001</name>
		<category>Project Team</category>

		<information>Aaron Anderson</information>
		<information>Paige Ganske</information>
		<information>Bill Johnson</information>
		<information>Mike Kallin</information>
		<information>Elizabeth Keyes</information>
		<information>Nicholas Lavin</information>
	</group>

	<group>
		<name>Hospital</name>
		<category>Investor</category>

		<information>The hospital will invest money in the system to help save lives every day. If it does not work 
		they will lose money and lives. Possibly have lawsuits due to the system.</information>
	</group>
	<group>
		<name>Patients</name>

		<category>Patient</category>
		<information>The patients count on the system to help save their lives in cases of myocardial infarctions.</information>
	</group>
	<group>
		<name>Technician</name>
		<category>Maintenance</category>
		<information>Maintenance personnel must remove waste and used antibodies in order to keep the system operational.</information>

	</group>
	<group>
		<name>Distributor</name>
		<category>Distributors</category>
		<information>Distributors will count on the product to sell well to users in order to make a profit.</information>
	</group>
	<group>

		<name>Nurse</name>
		<category>User</category>
		<information>Gathers then injects the blood sample into the machine in order to administer the test.</information>

	</group>
	<group>
		<name>Medical Professional</name>

		<category>User</category>
		<information>Analyzes results displayed from machine.</information>
	</group>
</stakeholders>

<worcontext img="workcontext.png">
	<adjsystem>
		<name>Nurse</name>
		<type>Active</type>

		<inevent>Input patient information using a barcode reader.</inevent>
		<inevent>Inserts the blood vial into the system.</inevent>
		<inevent>Replenishes the system's materials (antibodies, wash solution, reset solution).</inevent>
		<outevent>Removes waste products from the system.</outevent>
	</adjsystem>
	<adjsystem>

		<name>Technician</name>
		<type>Active</type>
		
		<outevent>System displays an error code for technician to diagnose.</outevent>
		<inevent>Technician follows repair instructions for the provided error code.</inevent>
		<inevent>Technician begins the setup procedure.</inevent>
		<outevent>System guides technical through setup procedure.</outevent>
	</adjsystem>
	<adjsystem>
		<name>Medical Informatics System</name>
		<type>Automated</type>

		
		<outevent>The system interacts with a Medical Informatics System in order to retrieve patient information and store test results.
		</outevent>
	</adjsystem>
	
	<adjsystem>
		<name>Medical Professional</name>
		<type>Active</type>

		<outevent>System displays percentage concentration results for the medical professional.</outevent>
	</adjsystem>
</worcontext>

<usecasehierarchy>
	<usecase id="testing" href="SE3821UC1.xml">Testing a Blood Sample</usecase>
	<usecase id="cleaning" href="SE3821UC2.xml">Waste Removal</usecase>
	<usecase id="refilling" href="SE3821UC3.xml">Refilling the System</usecase>

	<usecase id="information input" href="SE3821UC4.xml">Entering Information Into the System</usecase>
	<usecase id="initialization" href="SE3821UC5.xml">System Initialization</usecase>
	<usecase id="data" href="SE3821UC6.xml">Data Transmission</usecase>
</usecasehierarchy>
<!--
<allassumptions>
	<assumption></assumption>
</allassumptions>
-->

<!--
<alldependencies>
	<dependency>(Dependency)</dependency>
</alldependencies>
-->

<allconstraints>
	<constraint>The project must be completed by senior year.</constraint>
	<constraint>The project is funded with a limited budget of under $1000.</constraint>
	<constraint>The product must comply with the standards and regulations set by the Occupational Safety and Health Administration (OSHA), such as the handling and storage of blood and biological wastes.</constraint>
	<constraint>The product must comply with the standards and regulations set by the Food and Drug Administration (FDA), such as the regulation of medical systems.</constraint>
	<constraint>The product shall have a display that utilizes pastel colors to display pertinent information. (Studies have shown that pastel colors are visually appealing to most nurses and result in increased productivity.)</constraint>
</allconstraints>

<allrisks>
	<risk severity="Medium" likelihood="Medium" lastupdated="Jan 8, 2006">
		<comment>Testing the system is expensive due to the materials required (i.e., enzymes).</comment>
		<mitigation>Seek funding.</mitigation>

	</risk>
	<risk severity="High" likelihood="Low" lastupdated="Jan 8, 2006">
		<comment>Failure of the device could be devastating to the patient.</comment>
		<mitigation>Thorough testing before released into market.</mitigation>
	</risk>
	<risk severity="Medium" likelihood="High" lastupdated="Jan 8, 2006">
		<comment>Project members do not have the training required for handling blood and therefore cannot properly test the system.</comment>
		<mitigation>The device will be tested using enzyme substitutes similar to blood.</mitigation>
	</risk>
	<risk severity="Medium" likelihood="Medium" lastupdated="Jan 8, 2006">
		<comment>A patent is found of a very similar product.</comment>
		<mitigation>Attempt to add differing functionality.</mitigation>
	</risk>
</allrisks>

<allrequirements>

	<functional>	
   		<requirement trace="testing" id="sufficientInfo">The system shall provide enough information for a medical professional to determine the presence and severity of myocardial infarction.  Fit Criterion: 99% of medical professionals who use the system will correctly determine myocardial infarction.</requirement>
		<requirement trace="testing" id="medicalInformatics">The system shall provide the ability to transfer the results of the test to a Medical Informatics System.  Fit Criterion: The system will provide a valid HL7 message to a Medical Informatics System when it is configured properly.</requirement>
		<requirement trace="testing" id="medicalInformatics">The system shall restart after a given amount of time after encountering an error.  Fit Criterion: After encountering an error the system shall restart 99% of the time.</requirement>
	</functional>
	
	<usability>
		<requirement id="display">The product shall be able to display the results in a way that a medical professional can understand it in a short amount of time.  Fit Criterion: Trained professional reading the display correctly understands the information 100% of the time.</requirement>
		
		<requirement id="input">The product shall be simple for medical personnel to operate. Fit Criterion: 95 out of 100 medical personnel using the machine will be able to correctly operate the machine without additional training.</requirement>
		
	</usability>
	
	<performance>
		<requirement id="timeFrame">The product shall have a short time frame between inserting the blood sample and displaying the results.  Fit Criterion: Blood sample testing process takes less than 20 minutes.</requirement>
		
		<requirement id="volume">The product shall not be noisy.  Fit Criterion: Volume level stays below 50 dB (rainfall or normal conversation).</requirement>
		
		<requirement id="smell">The product shall not emit an offensive odor. Fit Criterion: 0% of medical personnel using machine provide complaints of the machine's odor.</requirement>
		
		<requirement id="droppable">The product shall sustain little or no damage when dropped from a reasonable height. Fit Criterion: System continues to function properly after being dropped from a height of up to four feet a number of times TBD.</requirement>

	</performance>
	
	<legal>
		<requirement id="legality">The machine and creation process must follow FDA and OSHA standards.  Fit Criterion: Machine complies to the rules laid out by the FDA and OSHA.</requirement> 
		<requirement id="confidentiality">The machine may not display results of previous patients to users.  Fit Criterion: 100% of tests do not display previous results. </requirement>
	</legal>

	<lookandfeel>
		<requirement id="look">
			The product shall have a design that is friendly to the users. 
			Fit Criterion: 9 out of 10 users find the product friendly to use.
		</requirement>
		<requirement id="pastels">
			The product shall have a display that uses pastel colors.
		</requirement>
	</lookandfeel>
		
	<maintainability>
		<requirement id="refilling">The machine shall be easy to refill with enzymes.  Fit Criterion: The refilling process takes less than 10 minutes.</requirement>
		
		<requirement id="cleaning">The machine shall have a removable waste receptacle for easy cleaning.  Fit Criterion: The system shall be able to be cleaned in less than 10 minutes. </requirement>

		<requirement id="cleaning">The machine shall have a removable enzyme cartridge.  Fit Criterion: The system's enzymes shall be able to be replaced in less than 10 minutes. </requirement>
	</maintainability>

	<!--
	<licensing>
	</licensing>
	-->
	
	<reliability>
		<requirement id="accuracy">The results from the machine must be accurate.  Fit Criterion: The device's results correctly match alternative myocardial infarction detection systems 95% of the time.</requirement>
	</reliability>
	
	<security>
		<requirement id="secure">System secures blood sample preventing removal until test is complete.  Fit Criterion: Blood sample can not be removed from system during test.</requirement>
		<requirement id="information">The system shall maintain the confidentiality of personal information used by the system. Fit Criterion: Personal information can only be found during the testing use case.</requirement>
		<requirement id="information">The system shall not contain the information from a test if power is lost. Fit Criterion: No personal information can be access after a power failure.</requirement>
	</security>

	<!--
	<supportability>
	</supportability>
	
	<software>
	</software>
	-->
	
	<operational>
		<requirement id="size">The product shall be small and portable.  Fit Criterion: System fits onto a crash cart.</requirement>
		
	</operational>

	<!--
	<appstandards>
	</appstandards>
	-->
		
</allrequirements>

<glossary id="glossary">
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Myocardial_infarction">Myocardial Infarction</a></name>
			<definition>A common form of a heart attack. Occurs when there is a cutoff to the heart's blood supply, causing damage to cardiac muscle and the death of heart tissue.</definition>
	</term>

	<term>

		<name><a href="http://www.lifediagnostics.com/troponin-i.htm">Troponin I</a> and <a href="http://en.wikipedia.org/wiki/Myoglobin">Myoglobin</a></name>
		<definition>Cardiac markers used to determine whether a patient is suffering a heart attack.</definition>
	</term>
	
	<term>
		<name><a href="http://www.lifediagnostics.com/Cardiac%20Intro.htm">Cardiac Markers</a></name>

		<definition>Proteins and enzymes normally contained within heart muscle that are released into the blood stream when damage to the heart muscle cells causes an opening through the cell walls.</definition>
	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Enzyme">Enzymes</a></name>
		<definition>Proteins that accelerate chemical reactions.</definition>
	</term>
	
	<term>

		<name><a href="http://en.wikipedia.org/wiki/Immunoassay">Immunoassay Reactions</a></name>
		<definition>Biochemical tests that occur between antigens and antibodies.</definition>
	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Antigen">Antigen</a></name>
		<definition>Substance that, when released into the body, triggers a response from the body's immune system (usually the production of antibodies).</definition>
	</term>

	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Antibody">Antibody</a></name>
		<definition>Y-shaped protein released into the blood in reponse to an antigen stimulus. Each antibody released targets a specific antigen, attaching itself to the antigen to neutralize it.</definition>
	</term>
	
	<term>
		<name>Binding Receptacle</name>
		<definition>Binding site for which antibodies attach during immunoassay reactions.</definition>

	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Spectrum_analysis">Spectra Analysis</a></name>
		<definition>Method of analyzing the chemical properties of matter by observing the bands of light in their optical spectrum.</definition>
	</term>
	
	<term>
		<name>Reset Solution</name>

		<definition>High-salt solution used within the Heart Attack Detection System to re-ionize the binding receptacles, allowing new antibodies to bind to it.</definition>
	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Substrate_%28biochemistry%29">Substrate</a></name>
		<definition>Molecule an enzyme acts upon during a chemical reaction.</definition>
	</term>
	
	<term>

		<name>Reactant Solution</name>
		<definition>During the <a href="SE3821UC1.xml">blood sample testing process</a>, the resulting solution containing antibodies and substrates and which has been cleaned of unwanted materials with the wash 

solution.</definition>
	</term>
	
	<term>
		<name>Wash</name>
		<definition>Low-salt solution that removes unwanted materials from the blood sample.</definition>

	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Occupational_Safety_and_Health_Administration">OSHA</a></name>
		<definition>Occupational Safety and Health Administration. Branch of the U.S. Department of Labor responsible for enforcing safety and health standards in the workplace.</definition>
	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/FDA">FDA</a></name>

		<definition>Food and Drug Administration.  Branch of the U.S. Department of Health and Human Services responsible for regulating food, drugs, cosmetics, dietary supplements, medical systems, biological goods, and blood 

products.</definition>
	</term>
	
	<term>
		<name><a href="http://en.wikipedia.org/wiki/Crash_cart">Crash Cart</a></name>
		<definition>A wheeled cart used in hospital wards and emergency rooms.</definition>
	</term>
	
	<term>
		<name>Medical Database</name>
		<definition>A database system that is used to store the test results for hospital patients.</definition>
	</term>
	<term>
		<name>Medical Personnel</name>
		<definition>
			A member of the medical staff of a hospital.
		</definition>
	</term>
	<term>
		<name>Health Level 7</name>
		<definition>
			HL7 is a messaging standard used by medical systems in order to communicate data between the systems.
		</definition>
	</term>
	<term>
		<name>Medical Informatics System</name>
		<definition>
			A repository that the hospital uses in order to store the large amount of information a hospital uses to operate.
		</definition>
	</term>
</glossary>



<allreferences>
	<reference><a href="http://www.hl7.org/">Health Level 7</a> messaging standard</reference>
</allreferences>

</srsdocument>