Injury Tracking Injury Tracking SystemSystem
Project DefinitionProject Definition
Team Members:Team Members:
Robbie MarshRobbie Marsh– Project Manager/WebmasterProject Manager/Webmaster
Ken MetcalfKen Metcalf– Lead ProgrammerLead Programmer
Julie OstranderJulie Ostrander– Systems AnalystSystems Analyst
Tamae BuechlerTamae Buechler– Systems ArchitectSystems Architect
Client Information:Client Information:
Dan Stephens, ATC/L Dan Stephens, ATC/L – Assistant Director of Athletics Assistant Director of Athletics – Coordinator for Sports Medicine Coordinator for Sports Medicine – Intercollegiate AthleticsIntercollegiate Athletics
Purpose:Purpose:
Create a more efficient method of Create a more efficient method of tracking student athlete’s informationtracking student athlete’s information
Consolidating the two current Consolidating the two current databases into one relational databasedatabases into one relational database
Create a PDA application that will Create a PDA application that will streamline data entry into the systemstreamline data entry into the system
Create a user friendly interfaceCreate a user friendly interface
Project Scope:Project Scope:
Primary goal:Primary goal:– To develop a system that will keep To develop a system that will keep
track of all of the athletes’ injuries at track of all of the athletes’ injuries at SIUE.SIUE.
Other goals:Other goals:– To convert the old system into a new To convert the old system into a new
fully functional database system.fully functional database system.– To implement a side application that To implement a side application that
will run on a Palm OS.will run on a Palm OS.
Current System:Current System:
Two separate databasesTwo separate databases– Injury databaseInjury database
Stores athletes’ injury information. Stores athletes’ injury information.
– Physical databasePhysical database Stores athletes’ physical information.Stores athletes’ physical information.
Insurance Claims folderInsurance Claims folder– Stores information about each Stores information about each
insurance claim into separate files.insurance claim into separate files.
Current System: Current System: (Cont.)(Cont.) DatabasesDatabases
– Written in Symantec Q & A.Written in Symantec Q & A.– The two databases are not currently The two databases are not currently
connected.connected.– The databases are copied from one The databases are copied from one
PC to another.PC to another.
Current System: Current System: (Cont.)(Cont.) Initial FormsInitial Forms
– PhysicalPhysical– HistoryHistory– Flex AssessmentFlex Assessment– Proof of InsuranceProof of Insurance
Injury FormsInjury Forms– There are eight unique injury forms There are eight unique injury forms
for each frequently occurring injury for each frequently occurring injury
Current System: Current System: (Cont.)(Cont.) Archived InformationArchived Information
– Annually, the client archives each Annually, the client archives each database by saving it to disk.database by saving it to disk.
– A hard copy of the athletes’ records A hard copy of the athletes’ records is required to be stored for is required to be stored for forty-forty-twotwo years. years.
Current System: Current System: (Cont.)(Cont.) Sequence ModelsSequence Models
– Creating the new databasesCreating the new databases– Completing an Insurance ClaimCompleting an Insurance Claim– Tracking an injuryTracking an injury
Work Flow ModelWork Flow Model
Intent: To create new databases for the current school year.
Creating the new Databases
Trigger: New school year begins.
A copy of each database from the previous year is made and saved to the desktop
Menu options are then selected to clear fields of their data.
Each copy is then renamed to match the current school year.
Certain selected fields are cleared for every record in the Physical Database using the “Selective Delete” option.
Inadvertent fields may be cleared by accident
Original and copied database could get mixed up
Intent: To clear these databases to begin data-entry for the new school year.
All fields for every record are cleared in the Injury Database using the “Mass Delete” option.
Certain selected fields are cleared for every record in the Physical Database using the “Selective Delete” option.
Certain selected fields are cleared for every record in the Physical Database using the “Selective Delete” option.
Intent: To complete all necessary forms for an insurance claim.
Insurance Claims
Trigger: Athlete suffers an injury severe enough to see a doctor
Four Insurance forms must be completed.
Some Information from this form is then exported to the 3 other forms.
The first formed filled out is the SIUE Sports Medicine Injury Report.
The remaining forms are then completed.
Possible loss of forms
Error while exporting data
Intent: To keep track of an injury
Tracking an Injury
Trigger: Athlete injures themselves.
Athlete is evaluated by trainer.
The user enters injury information from the forms into the injury database.
The proper injury forms are completed.
Trainer is not always present
Forms lack certain fields for a complete
evaluation
A progress report is completed in paper form for the athlete’s therapy.
If hard copy is lost, then progress report is
lost as well
Proposed System:Proposed System:
OverviewOverview– Combine two databases into one Combine two databases into one
relational databaserelational database– Allow for a PDA application to Allow for a PDA application to
interact with the databaseinteract with the database– Allow the user to more easily track Allow the user to more easily track
and query athletes’ information and query athletes’ information – Have a more user-friendly interfaceHave a more user-friendly interface
Proposed System: Proposed System: (Cont.)(Cont.) Functional RequirementsFunctional Requirements
– The system must contain all of the The system must contain all of the information from the currently used information from the currently used forms.forms.
– The system should contain The system should contain information about the time of injury, information about the time of injury, and environmental conditions.and environmental conditions.
Proposed System: Proposed System: (Cont.)(Cont.) Functional Requirements (Cont.)Functional Requirements (Cont.)
– The system must provide a method The system must provide a method to archive each injury after 30 days to archive each injury after 30 days from the date of entry.from the date of entry.
– The system must provide a method The system must provide a method of making reports based on athlete, of making reports based on athlete, sport, and injury.sport, and injury.
Proposed System: Proposed System: (Cont.)(Cont.) Non-functional RequirementsNon-functional Requirements
– The system should have a user-The system should have a user-friendly system.friendly system.
– The current forms group related The current forms group related information into sections. The new information into sections. The new system must maintain the same system must maintain the same sections.sections.
Proposed System: Proposed System: (Cont.)(Cont.) Software ConsiderationsSoftware Considerations
– Microsoft VB 6.0 VS. Microsoft .NET Microsoft VB 6.0 VS. Microsoft .NET Pros and ConsPros and Cons
PDA application toolPDA application tool– Pendragon FormsPendragon Forms– Handspring 3.0.1 H PalmHandspring 3.0.1 H Palm
Proposed System: Proposed System: (Cont.)(Cont.) Database Migration Database Migration
ConsiderationsConsiderations– Export from Symantec Q & A to Export from Symantec Q & A to
dBase format then to Microsoft dBase format then to Microsoft AccessAccess
– The schema of the current system The schema of the current system has not yet been examined, so the has not yet been examined, so the extent of the differences cannot be extent of the differences cannot be determined. determined.
Proposed System: Proposed System: (Cont.)(Cont.) Security IssuesSecurity Issues
– The system will have two levels of The system will have two levels of security.security. Administrator (Dan Stephens)Administrator (Dan Stephens) Grad/Undergrad studentsGrad/Undergrad students
The system will block access after The system will block access after a set time of inactivity until a set time of inactivity until password is re-entered.password is re-entered.
System Models:System Models:
Modular OverviewModular Overview– Main applicationMain application– PDA applicationPDA application
Questions?Questions?