Medic Alert Passport System - PowerPoint PPT Presentation

medic alert passport system n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Medic Alert Passport System PowerPoint Presentation
Download Presentation
Medic Alert Passport System

play fullscreen
1 / 18
Medic Alert Passport System
154 Views
Download Presentation
jace
Download Presentation

Medic Alert Passport System

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Medic Alert Passport System Advancing the Medic Alert Bracelet

  2. Team Structure • Team Leader Ryan Abel • Team Members Jim Bodmer Li Li Raghunath Poreddy

  3. Medic Alert Passport privileges

  4. Risk Management • Identified Risks • Group Dynamics • Development environment • Technology bias • Strict schedule • Configuration management

  5. Development Process • Life Cycle Model • Rapid prototype • Ensures a workable development environment • Ensures technology interoperability • Evolutionary Model • In the event of “schedule creep”, we need to ensure that we have a demo-able product

  6. Configuration Management • SourceForge.net • CVS system for source code management and file sharing • Provide a central location for posting FAQ’s and information

  7. M.A.P.S. Stake Holders • Users • Patients • Pharmacists • Doctors • Emergency Room • Hospital Billing Department • Insurance • Legal • System Management / Tech Support • Developers • Pseudo-Stake Holder: Jon Kuhl (Project Management)

  8. Patient: Passport Holder • Convenience • Small: Should be able to wear the passport or keep it in a wallet and/or purse • Durable: Comparable to a watch, ring or drivers license (water proof, impact resistant, flexible) • Ease of Use: Low learning curve, user friendly • System should not require technology in the home • Cost: Initially free, low replacement cost • Privacy • User should be able to block/restrict access to medical records • View a history log of past transactions • Verify Transactions before they occur

  9. Pharmacist • Convenience: • Low learning curve • System should be easy to integrate into current software systems • Accuracy in information • Information should be stable, and changeable by authorized personal only • Information logging: Information stored at “prescription fill” should be auditable in the case of a mal-practice law-suit • Contract: Provide a patient verification of past allergies and medications (I “insert name”, herby…)

  10. Doctors • Convenience • Low learning curve • Easily integrated into software system • Accuracy in Information • Information should be stable, and changeable by authorized personal only • Information logging: Information stored at “prescription issue” should be auditable in the case of a mal-practice law-suit • Contract: Provide a patient verification of past allergies and medications (I “insert name”, herby…)

  11. Emergency Room • Emergency Read Access • ER should have emergency access to information stored on passport if patient is unable to communicate • Convenience • Low learning curve • Easily integrated into software system • Accuracy in Information • Information should be stable, and changeable by authorized personal only

  12. Hospital Billing Department • Convenience • Low learning curve • Easily integrated into software system

  13. Insurance • Authentication • Addition of Insurance Plans should require Authentication • If a policy is cancelled it should be disabled against fraudulent claims

  14. Legal • Protect patient confidentiality • Data stores, and data protection mechanisms should be secure enough to be admissible in a court of law

  15. System Managers, Tech Support • Debugging • Software should include a debugging mode which would allow for system trouble shooting • As errors are encountered, they should be added to an error log • Expandability: should be able to add new passport types, and upgrade software

  16. Developers (self-management) • Maintainability / Versioning / Scalability • Reusable, extendable software components… • Stable requirements • Reasonable system foresight

  17. Pseudo Stake Holder: Jon KuhlProject Management • Why? Sets project deadlines / schedule… • Timely development (sets deadlines) • Good Software Process (how we do what we do) • System Quality (product approval)

  18. Applause!!!