Philadelphia Drexel Eagles Emergency Response PDEER

1
Philadelphia Drexel Eagles Emergency Response
(P-DEER)

• 4 out of 5 Doctors
• Chris Cozine, Ron DeLuca, Jason Edonick,
• Matt Fanning

2
Questions

• This is our FINAL presentation
• Any questions you may have will be happily
  answered at the end.

3
The Product

• A medical identification card containing the
  following information
• Users Name and address
• Emergency contact and phone number
• Doctors name and location
• Current and past prescriptions
• Adverse drug reactions
• Medical history
• Allergies
• Living Will Information

4
Highlighted Features

• Patient data including known allergies and drug
  reactions
• Allows for the medical personnel to react faster
  to the patients needs by having pertinent
  information. Eliminating the worry of not knowing
  about these conditions.
• Patient medical history
• Allows for the medical personnel to have the
  background of the patient which will help with a
  faster diagnosis.
• Patients medical insurance information
• Using the systems RFID capabilities, this
  provides medical personnel the ability to treat
  patients faster by not requiring direct access
  to the patients insurance card.
• Patients living will information
• Provides medical personnel with knowledge
  regarding the patients will to live and what
  actions can be performed within legal bounds.

5
Highlighted Features

• Patients current doctor information
• Provides medical personnel with knowledge of the
  patients doctor information, if there are any
  questions which only the primary doctor can
  answer.
• Patients preferred hospital
• Provides medical personnel with knowledge of the
  patients preferred hospital.
• Patients medical treatments
• Provides the insurance company with information
  on the services performed for the patient.
• Provides for faster approval of the services by
  the insurance company.

6
System Objectives

• Eliminates healthcare professionals need to
  search for hard copies of their patients
  records.
• Allowing for diagnoses of patients faster,
  accurately, and therefore more efficiently.
• Providing quicker access to soft copies of
  patients records.
• Enables easier in house operations.
• Transportation of information digitally instead
  of via paper.
• Cut costs and reduce the down time of current
  resources.
• Eliminates the need for paper copies,
  reproduction of paper copies of information,
  disposal of paper information and storage of
  paper information.

7
System Objectives

• Highest level of security standards at or above
  HIPAA levels.
• Required log in to gain access to the system.
• Must be fail proof, as misdiagnosing will
  invalidate its use.
• With clustering of the servers, uptime will be at
  100, eliminating the chance of downtime.
• Must be portable for users.
• The product is structured with the N to 1
  principal in mind. All the system requires is an
  internet connection and an interface.
• (i.e. computer terminal, PDA)
• Easy to use and not a replacement for human
  diagnosis.
• The system was built to be a supplement to assist
  users with the most up to date information on
  their patients.
• The system was NOT built to replace human
  diagnosis.

8
P-DEER Databaseand Diagram Designs
9
Database Model
10
Entity Relationship Diagram
11
Relational Schema
12
Use Case Diagram
13
Use Case Diagram cont.
14
Actors

• Cardholder (Not in Use Case Diagram, but a vital
  part of system)
• Carries medical insurance with a company
  implementing P-DEER.
• NOTE It is assumed that all the cardholders
  will be in possession of a card.
• Customer Service Representatives
• Employed by the insurance company and will be
  entering, modifying, querying, or deleting
  records using the P-DEER interface.
• Database Administrator
• Responsible for the maintenance of the database.
• Healthcare Professionals
• EMT, nurses, doctors, medical secretaries, etc.
• System
• Processing of the information for users.

15
Required Data
16
Who does P-DEER work for?

• In the field (Medical Personnel)
• With the use of a PDA (Personal Digital
  Assistant) RFID (Radio Frequency Identification)
  technology, ASP (Active Server Pages) interface
  and an Access database. The medical card is
  scanned and then linked to a central database
  which contains all patient information.
• In the office (Insurance Companies)
• The CSR (Customer Service Representative) logs in
  an ASP and Access database driven web site to
  view or modify information on patients.
• In patients need (Cardholder)
• The Cardholder logs in an ASP and Access database
  driven web site to view his/her medical and
  insurance information.

17
How does P-DEER work?

• The P-DEER interface has two versions
• Read Only Healthcare Professionals/ Cardholders
• Read / Write Insurance Company Professionals
• Interface Design Active Server Pages
• The interface has been developed with the ability
  to be common to all of the system users.
• Back-end Design Access Database
• The database has been developed with the ability
  to expand to meet business demands.

18
How does P-DEER work?

• Read Only Healthcare Professionals/ Cardholders
• The user logs into the system via the web
  interface with their user id and password.
• After the user id and password has been
  authenticated with the server the following
  scenarios come into place
• If the healthcare professional is in the field
  such as an EMT, the user can scan the patients
  insurance card to gain information on the
  patient.
• If the healthcare professional is in the
  hospital, the user can enter the patients
  customer id in order to gain the patients
  information.
• If the cardholder is at home, he/she can enter
  his/her customer id in order to gain their
  personal medical information.
• In all cases the customer id is used as the
  primary key to contact the access database, which
  is located on a central clustered server, for the
  patients information. The information is then
  returned to the interface and can only be viewed
  and NOT modified.

19
How does P-DEER work?

• Read / Write Insurance Company Professional
• The user logs into the system via the web
  interface with their user id and password.
• After the user id and password has been
  authenticated with the server, the user is
  granted access
• The Insurance Company Professional can enter the
  patients customer id to gain the patients
  information.
• The customer id is used as the primary key to
  contact the access database, which is located on
  a central clustered server, for the patients
  information. The information is then returned to
  the interface and is available to be modified.

20
Issues of concern

• Security
• Health Insurance Portability and Accountability
  Act of 1996 (HIPAA) requirements.
• Radio Frequency Identification (RFID).
• Cost
• Cost of national deployment.
• Integration with existing systems.
• Staff
• Expansion for national deployment.
• Implementation
• Integration of older technologies that support
  similar functions.

21
Security of PDEER

• HIPAA
• After every internet session the cache will be
  cleared.
• The system will timeout after a predetermined
  amount of time.
• The system is a role-based system in order to
  limit the amount of information individuals can
  access.
• RFID Technology
• Originally designed to be an open technology.
• The chip will only contain the patient id
  information.
• NO personal information will be located on the
  chip.

22
Functional Requirements

• Query Cardholder Information
• Collect Cardholder Query Input
• Cardholder Query
• Input New Cardholder Information
• Collect New Cardholder Data
• Modify Cardholder Information
• Collect Cardholder Update Information
• Delete Information
• Delete Cardholder
• Delete Cardholder Information
• Scan Card
• Connect Handheld Device to Remote Server
• Customer Query
• Create Database Reports
• Database Query
• Access System
• Check User
• Redirect User
• System Availability

23
Non-Functional Requirements Constraints

• HIPAA
• Data Secrecy - viewing
• Data Integrity - modifying
• Data Availability 24/7
• RFID Range
• Data Migration Updates
• Backup / Recovery

24
Design decisions and tradeoffs

• P-DEER is designed for medical personnel and
  insurance company personnel.
• P-DEER is designed as a stand-alone database
  currently using Microsoft Access.
• Integrated with scanners to read RFIDs located
  in medical insurance cards.
• The system will be available only in English at
  this time.
• The development of the system was in this order
  database, interface, RFID cards. Due to the
  reliance of the other components on the database.
  
• The GUI will require an internet browser.

25
Quality Attributes

• Security - a certain level can be assured.100 is
  our goal.
• VPN
• Firewalls
• Windows 2003 Servers
• Availability 100
• Reliability 100
• Maintainability Qualified DBAs

26
P-DEER User Scenarios
27
User Overview Mike (EMT)

• User Mike, an experienced EMT, who sometimes
  cant communicate with a person who is in need of
  medical help. Mike would really like a way to get
  accurate information from people that doesnt
  require verbal response. He is not bilingual, and
  frequently his patients are in pain or
  unconscious when he gets to them. He uses a lot
  of specialized equipment and learns quickly.

28
Scenario Mike (EMT)

• Mike arrives on an emergency scene and sees an
  unconscious person lying on the floor, in obvious
  need of medical attention. Mike takes from his
  belt a small scanning device and waves it over
  the persons body. Mike is using the scanning
  device because the unidentified person has the
  P-DEER RFID insurance card. Mikes P-DEER card
  scanner responds and displays the persons name,
  medical insurance number, allergies, preferred
  hospital, and primary care physician along with
  any other crucial, immediate care information.

29
User Overview Billy (Cardholder)

• User Billy, a patient with many allergies, works
  for a law firm that provides full medical
  insurance coverage to its employees. He is
  allergic to shellfish, raw vegetables and cats.
  Billy eats from vendor carts on regular basis
  that are near his work, as that is where his
  co-workers eat.

30
Scenario Billy (Cardholder)

• Billy walks in to an emergency room a couple
  hours after lunch with a serious case of food
  poisoning. Billy walks up to registration and the
  nurse at the desk asks for his insurance card.
  She scans it with a standard RFID identifier. The
  nurses computer displays the persons name,
  medical insurance number, allergies, preferred
  hospital, and primary care physician along with
  any other vital information, using the P-DEER
  interface.

31
Synopsis of Development

• CYCLE ONE
• The Birth of P-DEER

32
Cycle 1 Objectives Achieved

• Determine if the system objectives are obtainable
  and reassess the system.
• Strategize our plan for creating the system.
• Finalized system requirements by 2nd week of the
  term.
• Test specifications and successful test criteria
  by the 3rd week of the term.

33
Cycle 1 Objectives Achieved

• Design the system by the 4th week of the term.
• Build the system prototype during the 5th and 6th
  weeks of the term.
• Test the system prototype by the 7th week of the
  term.
• Evaluate the system prototype and address any
  issues by the 8th week of the term.

34
Synopsis of Development

• CYCLE TWO
• ITS ALIVE!!!!!

35
Cycle 2 Objectives Achieved

• Fixed any issues with the interface.
• Added searching capabilities by customer ID.
• Improved on the layout of the interface.
• Produced a smoother interface.
• Developed a database for system users.
• Developed for authentication to the database.
• Tested the system for any issues.
• Performed testing of the system and found only
  minor issues regarding searching limitation.

36
Synopsis of Development

• CYCLE THREE
• P-DEER IS COMPLETE

37
Cycle 3 Objectives Achieved

• Completion of all documentation.
• System Requirements Specifications
• Software Design Specifications
• Test Specifications
• Functional Requirements Matrix
• Improved searching capabilities of the system.
• Conversations about taking the next step.

38
Demonstration of System

• 4 out of 5 doctors