data systems and issues ncaemsa winter conference 2004 wednesday february 18, 2004 william e. ott,...
TRANSCRIPT
![Page 1: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/1.jpg)
Data Systems and Issues
NCAEMSA Winter Conference 2004Wednesday February 18, 2004
William E. Ott, MS, Paramedic
CPCS Technologies
www . cpcstech . com
![Page 2: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/2.jpg)
Integrated System
Data
Warehouse
EMSMedical Examiner
Hospitals
Data transformation and scrubbing
MedicalDirection
Data Reporting
LawEnforcement
![Page 3: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/3.jpg)
Wide Area Wide Area Network (WAN)Network (WAN)
9.6 Kbit/s <2Mbs9.6 Kbit/s <2Mbs• Voice• SMS• e-Mail• Web browsing
• mCommerce• Internet access• Document transfer• Low/high quality video
GPS
Mobility – PAN, LAN, WAN
Local Area Network wLAN
802.11b802.11b
LAN
<11Mbs<11Mbs• Access•“hot spots”•LAN equivalent
WirelessBridge
WorkgroupSwitches
Personal Area Network (PAN)
<1Mbs<1Mbs• Access•Synchronization•10 Meters
Bluetooth
![Page 4: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/4.jpg)
![Page 5: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/5.jpg)
EMS as Information Workers
• What is involved?– Electronic patient records– CAD data pre and post response– GIS data pre and post response– System performance data– Application of performance data to the
continuing education program– Personnel data– System / Vehicle data– Facility/Event preplan data
![Page 6: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/6.jpg)
Threats to Information Systems
• Malicious abuse• Denial of Service and related attacks• Virus, Worm, and Trojan attacks• Outside Hacker attacks• Theft of service• Theft of information• Poorly trained IT staff• Not staying current with system patches,
antivirus definitions, etc..• Not performing proper system maintenance• Poor or no backup and contingency plans
![Page 7: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/7.jpg)
Threats to Productivity
• Spam
– wastes resources
– wastes time
– offensive, dangerous
• Popup ads
– wastes resources
– annoying
• Malicious use of resources
– wastes bandwidth, storage
– violates law and privacy
![Page 8: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/8.jpg)
Threats to Privacy / Confidentiality
• No security plan• No security training or awareness• Smart or Meta Tags in shared documents• Social Engineering• Unencrypted network• Unencrypted e-mail• No firewall• No antivirus system• Rogue wireless• PDAs connecting to network and servers
![Page 9: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/9.jpg)
Some Security Options
• Virtual Private Networking (VPN)• Active AntiVirus Screening• Stateful packet inspection Firewalling• Proxy servers• Opt-in e-mail • Database encryption• E-mail encryption• Network / PC security policies• Two Factor User Authentication• Aggressive Audit logging and review
![Page 10: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/10.jpg)
Sources of Threats
• Employees
– Unintentional - acting in good faith
– Intentional - disgruntled or unhappy staff
– Software errors
• Environment
– Equipment failure
– Fire, flood, earthquake
![Page 11: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/11.jpg)
Comprehensive Security Policy
• The policy must address:
– Physical Security
– Computer hardware and software inventory
– Personnel screening and selection
– Ongoing education
– Access and control procedures
![Page 12: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/12.jpg)
Comprehensive Security Policy
• Must also address:
– Procedures for release of information
– Disposal of data
– Data backup and recovery
– Contingency planning
– Sanctions for noncompliance
– Periodic review
![Page 13: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/13.jpg)
Costs of Security
• Reduced access to information.
• Increased time and effort to access information.
• Hardware and software to implement security.
• Staff time to implement and maintain security system.
![Page 14: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/14.jpg)
Physical Security
• Control access to servers and network equipment.
• Locate workstations in secure area, not easily accessible to the public.
• Provide surge protection and uninterruptible power supplies.
• Provide fire alarms and fire suppression equipment.
![Page 15: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/15.jpg)
Hardware Security
• Hardware should be dependable.• Non-proprietary to allow for easy repair and
replacement.• Critical systems should be mirrored and spare
parts available for likely to fail components.• Routine maintenance and tuning should be done.
Have a service contract in place! • Maintain accurate and up to date inventory.
![Page 16: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/16.jpg)
Software Security
• Applications should be chosen with security in mind.
• Should have the capability of encryption for data storage and communication.
• System security software:– Firewall– Intrusion detection– Anti-virus– Disk defragmenter
• Maintain accurate and up to date inventory.
![Page 17: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/17.jpg)
Access control
• Protect critical resources by limiting access to authorized and authenticated users.
• Specify:– who can access the information, – how it can be accessed, – when it can be accessed, and – under what conditions it can be accessed
![Page 18: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/18.jpg)
What Are Potential Disasters? External
• Storms (hurricanes, tornados, floods, hail…)
• Accidents (planes, trains, automobiles, hazardous mat.)
• Regional Outages (power, communications…)
• Violence (civil unrest, terrorist acts, bioterrorism…)
Internal
• Hardware Failures (servers, data stores, cyber attacks..)
• Accidents (fires, water leaks, electrical…)
• Violence (disgruntled employee, corp. sabotage…)
![Page 19: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/19.jpg)
Contingency Planning
• Plan for interruption of service.
• Have alternate plan for data capture and retrieval. (Paper?)
• Have adequate security for alternate plan.
![Page 20: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/20.jpg)
Data Backup and Recovery
• One of the most crucial components!
• Most likely component to be ignored.
• Practice data recovery!
• Use data protection schemes such as mirroring, RAID.
• Large agencies should consider hot sites.
![Page 21: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/21.jpg)
Disposal of Data
• Discarded computer parts and peripherals should be dependably erased or destroyed.
• Removable media should be accounted for.
• Hardcopy printed from computerized records should be controlled.
![Page 22: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/22.jpg)
System Components
Transformation
Input Output
Control Mechanism
![Page 23: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/23.jpg)
Four Parallel Systems
• User system
• Data system
• Software system
• Hardware system
Data
Software
Hardware
User
![Page 24: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/24.jpg)
Input
• Automatic data capture
• User Assisted– Optical Mark
Reader (OMR)– Optical Character
Reader (OCR)– Keyboard– Voice recognition
Transformation
Input Output
Control Mechanism
![Page 25: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/25.jpg)
Transformation
• Data is collected and analyzed
• Aggregation• Analysis• Validation
Transformation
Input Output
Control Mechanism
![Page 26: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/26.jpg)
Output
• Reporting– Ad hoc– Exception reports– Aggregate
• Publishing– Web-based
Transformation
Input Output
Control Mechanism
![Page 27: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/27.jpg)
Control Mechanism
• Quality improvement• Education• Administrative policies• Medical protocols
Transformation
Input Output
Control Mechanism
![Page 28: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/28.jpg)
Systems Architecture
• Stand-alone
• Peer network
• Mainframe-terminal
• Client-server
• Terminal-server
![Page 29: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/29.jpg)
Stand Alone
• Each computer functions alone.• No connection with any other
computers.• Easy to maintain.• File transfer by “sneaker net”
only.
![Page 30: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/30.jpg)
Peer Network
• Computers connected to each other.
• Limited to file and print sharing.
• Connected via local area network.
• Share of data weakens security.
• No central control.
![Page 31: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/31.jpg)
Mainframe-Terminal
• May be mini-computer or mainframe.• Commonly referred to as legacy
system.• “Dumb” terminals.• All activity on main computer.• Connected with cable. • Normally not GUI based application. • Not conducive to ad hoc queries and
reporting.
![Page 32: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/32.jpg)
Client-Server• Client are fully functional
computers.• Server may host applications.• File sharing and printing normally
done through server.• Connected via local or wide area
network.• May be very secure.• High cost of multiple client
workstations (purchase and maintenance)
![Page 33: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/33.jpg)
Terminal-Server
• New technology.• Multiple “dumb” terminals
connected to server.• Applications, printing, file storage
are on server.• Connected via local or wide area
network.• Centrally maintained software.• Low-cost network terminal.
![Page 34: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/34.jpg)
Clustering
• Multiple servers.• Servers are joined and share
processing.• Service is maintained with
failure of single server.• Highly dependable with little
down-time.
![Page 35: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/35.jpg)
Database Systems
![Page 36: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/36.jpg)
Schema
• Pronounced SKEE-mah.
• The organization or structure for a database.
• Often used to refer to a graphical depiction of the database structure.
![Page 37: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/37.jpg)
Data Components
• Database
• Tables
• Records
• Columns
![Page 38: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/38.jpg)
Tables
Table Name
Column Names
Patient
PatientIDAddress
CityState
ZipCodeAgeDOB
Primary Key
![Page 39: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/39.jpg)
Table• A collection of
similar data organized in columns and rows (records).
• Concept similar to a spreadsheet.
Patient TablePatientID City State DOBORA4567 Danville VA11/11/54ORB1111 OrlandoFL 08/26/17ORA1234 Bithlo FL 05/03/38ORB5678 Taft FL 01/01/74
ColumnRow
(Record)
Table
![Page 40: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/40.jpg)
Column
• Each column is a data element.
• The storage format for each column is defined
• Column names are listed at the top
Patient TablePatientID City State DOBORA4567 Danville VA11/11/54ORB1111 OrlandoFL 08/26/17ORA1234 Bithlo FL 05/03/38ORB5678 Taft FL 01/01/74
ColumnData
ColumnName
![Page 41: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/41.jpg)
Data Element
• Data elements have different types
• All data in a column will be of the same type.
Patient TablePatientID City State DOBORA4567 Danville VA11/11/54ORB1111 OrlandoFL 08/26/17ORA1234 Bithlo FL 05/03/38ORB5678 Taft FL 01/01/74
ColumnData
![Page 42: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/42.jpg)
Data Element Types
• Character or text• Numerical
– Integer– Fixed – Real
• Date (time)• Binary or raw• Memo or long• Link
![Page 43: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/43.jpg)
Data Elements
• Each field has a type.
• The length of the field is set for character fields.
• Most other fields can expand to accommodate more data.
![Page 44: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/44.jpg)
Data Elements
• Beware! – Not all fields containing numbers should be number fields.
• Numbers that are not used in any arithmetic should be in character fields.
• Examples are Social Security numbers, telephone numbers and any other identification number.
![Page 45: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/45.jpg)
Database Front-End
• Front-end: the interface that the user sees to input and manipulate data.
• Front-ends are usually built using some programming language such as: – PowerBuilder– Visual Basic– Java– Delphi
• Usually connect to some relational database.
![Page 46: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/46.jpg)
Database Back-end
• Back-end: the relational database used to store and manipulate the data.
• Relational database management (RDBM)
![Page 47: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/47.jpg)
Relational Database
• A collection of data items organized as a set of tables (like spreadsheets).
• Tables may be linked to form new tables.
• Has rows and columns to show the relationships between items.
• Tree-like structure.
![Page 48: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/48.jpg)
Flat File Database
• Stores information in single file.
• Does not allow a one-to-many relationship.
• Limits the amount of data that may be input per record.
![Page 49: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/49.jpg)
Desktop DB vs. RDBMS
• Desktop include:– Access– Approach– Filemaker Pro– FoxPro
• All processing occurs on the standalone.
• Intended for smaller databases.
• Front-end included.
• RDBMS include:– Oracle– Informix– DB2– MS SQL
• Processing occurs on the server.
• Has tools for larger databases.
• Requires front-end programming.
![Page 50: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/50.jpg)
One-to-Many Relationship
Incident
Patient
Event
Event
Event
Event
Patient
Event
Event
Event
Event
Patient
Event
Event
Event
Event
One Incident-Many Patients
![Page 51: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/51.jpg)
One-to-Many Relationship
Patient
Event – IV Access
Event – O2 Admin
Event - Medication
Event - Procedure
One Patient-Many Events
![Page 52: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/52.jpg)
Many-to-Many Relationship
Doctor
Patient
Patient
Patient
Patient
One Doctor-Many
Patients
Doctor
Doctor One Patient-Many
Doctors
![Page 53: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/53.jpg)
One-to-One Relationships
Patient
One Patient-One Home Address
Home Address
Ambulance
One Ambulance-One Defibrillator
Defibrillator
![Page 54: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/54.jpg)
Keys
• A key field should be present in each table.
• Tables are related (linked) using keys.
• A key may be made of multiple combined fields.
![Page 55: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/55.jpg)
Primary Keys
• Primary keys are values that uniquely identify each record within the table.
• Primary keys must always be filled in and not duplicate any of the other values in the table.
![Page 56: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/56.jpg)
Foreign Keys
• Tables may contain a “foreign” key.
• Foreign keys are the primary key for a related table.
• Multiple records may have the same foreign key that link them to a single record in the related table.
![Page 57: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/57.jpg)
Table Relationship
Patient
PatientIDName
AddressCity
StateZipCode
AgeDOB
Foreign Key
TreatmentPatientID
Treatment IDMedication
DosageRoute
Primary Key
Same valueLinks the two tables
![Page 58: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/58.jpg)
Table Joins
• May create a new table, “target”, from the source tables.
• May be temporary – called a “query”.
• May use many tables to assemble the desired data set.
![Page 59: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/59.jpg)
Table Join
Name Patient ID Og Oglesby OR13567John Doe OR54321
Patient ID Medication DosageOR54321 Epinephrine 1.0 mgOR13567 ASA 162 mgOR54321 Oxygen 12 l/mOR13567 Atropine 1.0 mg
Tables are associated with the primary key
Note: One-to-many relationship
![Page 60: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/60.jpg)
Relational vs. Flat File
• Flat file databases are limited to predefined number of data occurrences.
• Most desktop databases are relational, however, some applications are designed as flat file.
![Page 61: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/61.jpg)
Relational vs. Flat File
Note: One-to-many relationship
Name Patient ID Og Oglesby OR13567
Patient ID B/P B/P Time OR13567 110/80 13:45OR13567 116/82 13:55 OR13567 120/82 14:05
Name Patient ID B/P1 Time1 B/P2 Time2 Og Oglesby OR13567 110/80 13:45 116/82 13:55
Flat File Database
Relational Database
![Page 62: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/62.jpg)
Table Join
Name Patient ID Og Oglesby OR13567John Doe OR54321
Patient ID Medication DosageOR54321 Epinephrine 1.0 mgOR13567 ASA 162 mgOR54321 Oxygen 12 l/mOR13567 Atropine 1.0 mgNote: One-to-many relationship
The Patient ID is the primary key in the patient table and the foreign key in the medication table
![Page 63: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/63.jpg)
Table Joins
Name Patient ID Medication DosageOg Oglesby OR13567 ASA 162 mgOg Oglesby OR13567 Atropine 1.0 mgJohn Doe OR54321 Epinephrine 1.0 mgJohn Doe OR54321 Oxygen 12 l/m
Patient ID Medication DosageOR54321 Epinephrine 1.0 mgOR13567 ASA 162 mgOR54321 Oxygen 12 l/mOR13567 Atropine 1.0 mg
Name Patient IDOg Oglesby OR13567John Doe OR54321
SourceSource
Target
![Page 64: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/64.jpg)
Table Joins
Name Patient ID Medication DosageOg Oglesby OR13567 ASA 162 mgOg Oglesby OR13567 Atropine 1.0 mgJohn Doe OR54321 Epinephrine 1.0 mgJohn Doe OR54321 Oxygen 12 l/m
Patient ID Medication DosageOR54321 Epinephrine 1.0 mgOR13567 ASA 162 mgOR54321 Oxygen 12 l/mOR13567 Atropine 1.0 mg
Name Patient IDOg Oglesby OR13567John Doe OR54321
SourceSource
Target
![Page 65: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/65.jpg)
Reporting
Name Patient ID Medication DosageOg Oglesby OR13567 ASA 162 mgOg Oglesby OR13567 Atropine 1.0 mgJohn Doe OR54321 Epinephrine 1.0 mgJohn Doe OR54321 Oxygen 12 l/m
Name Patient ID Medication DosageOg Oglesby OR13567 ASA 162 mgOg Oglesby OR13567 Atropine 1.0 mgJohn Doe OR54321 Epinephrine 1.0 mgJohn Doe OR54321 Oxygen 12 l/m
![Page 66: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/66.jpg)
Reporting
Name Patient ID Medication DosageOg Oglesby OR13567 ASA 162 mgOg Oglesby OR13567 Atropine 1.0 mgJohn Doe OR54321 Epinephrine 1.0 mgJohn Doe OR54321 Oxygen 12 l/m
Name Patient ID Medication DosageOg Oglesby OR13567
ASA 162 mgAtropine 1.0 mg
John Doe OR54321 Epinephrine 1.0 mgOxygen 12 l/m
![Page 67: Data Systems and Issues NCAEMSA Winter Conference 2004 Wednesday February 18, 2004 William E. Ott, MS, Paramedic CPCS Technologies www. cpcstech. com](https://reader036.vdocuments.net/reader036/viewer/2022070306/5516f534550346fe558b4c07/html5/thumbnails/67.jpg)