Doctors Office System

1
Doctors Office System

• Group 3

Monday, December 3, 2007
2
Project Proposal

• Initially, we wanted to design a college
  recruiting system for the Howard County High
  School football league
• Issues encountered
• A similar system was already in existence
• The scope was too large (12 different schools to
  manage)
• Due to these reasons, we decided to forgo with
  this proposal

3
Project Proposal

• We then proposed automating Dr. Tahoora Kawajas
  medical office
• Business Need
• More efficient method of storing patient records
• Existing system was cumbersome and hard to
  maintain
• Ability to manage patient information quickly and
  accurately
• Benefits
• One of our group members previously worked at
  the office and had good knowledge of the as-is
  system
• Scope only one entity to work with

4
Preliminary Analysis

• Goal To perform an initial assesement of the
  medical center in question and to the problems
  associated with a system wide upgrade.
• Implementation
• Analysis of Medical Center daily operations and
  procedures.
• Analysis of needs and goals of the medical center
  staff.
• Analysis of general solutions to stated needs and
  goals.

5
Feasibility Analysis

• Goal to provide the office with a Information
  System which manages patient files, accept
  electronic payment, and schedule appointments
• Operational Feasibility
• Administrative Assistant schedule patient
  appointments
• Dr. Kawaja produce patient notes and
  prescriptions
• Training

6
Feasibility Analysis

• Technical Feasibility
• Federal regulations
• Electronic Medical Record (EMR) software
• Stand-alone
• Web-based
• Back-up plans
• Schedule Feasibility
• Task scheduling and dependencies
• Economic Feasibility
• Projected costs
• Tangible/Intangible benefits

7
Requirements Analysis

• Information Gathering Methods
• Interviews
• Physician learned about overall practice
  regulations
• Administrative Assistant learned about
  scheduling and payment processes
• Medical Assistant learned about referrals,
  medication and vital collection processes
• Open-ended questions
• Questionnaires
• Distributed to patients
• Important/interesting statistics

8
Requirements Analysis

• Functional Requirements
• Process-oriented
• Information-oriented
• Non-functional Requirements
• Performance
• Security
• Cultural/Political
• Use cases

9
System Analysis Report

• Diagrams
• E-R Diagram illustrates the as-is system
• Data Flow Diagram illustrates proposed system
• Information Gathering
• Observation by group members
• Physical locations
• Documents and files
• Interviews with office staff
• Questionnaires filled by patients

10
System Analysis Report

• Business Rules
• Current Rules
• HIPAA
• Privacy Rule
• Organizational Rules
• Implementation
• Electronic Health Transactions

11
System Design Report

• Packaged vs. Custom solution
• Web-based EMR
• Common features
• Elysium EMR Lite
• Specific features
• Aquifer EMR
• Specific features
• Alternate Solution Feasibility

12
System Design Report

• Alternative matrix chart
• Decision on appropriate solution
• Hardware/software required

13
Lessons Learned

• Importance of communication within our group
• Dividing tasks within deliverables instead of
  assigning one to each member
• Maintaining good relationship with our clients