Transcript Add New Record

Medication History Solicitation:
Architecture Presentation
Team A
Presenter:
Alex Jackson
10/22/09
Search
Has Internet
Sync
Nurse
Login
Not
Found
Found
Not Found
Patient
Record
New
Record
Annotate
Pharmacist’s
Search
System
Administrator
Database
Administrator
Log View
User
Administrator
Edit
Drugs
Logout
Add
Drug
New
Record
Patient info
Record
Page
Record Entry Complete
Edit
Drug
Verify
Verify
Complete
Logout
Overview
Login
User Type
Nurse
Pharmacist
System Admin
Login
No
User Login
Valid User
and
Login?
Yes
User Type
Nurse
Pharmacist
System Admin
Nurse: New Record
No
New Record
User Fills out
Patient
Record
Is the
info
correct
?
Yes
Yes
Nurse
submits
record to
Client DB
More
Patients
?
No
System
Admin
updates EMR
User syncs
Patient
Schema to
Server DB
Nurse: Main Functionality
Yes
Has
Internet
?
Yes
Search
No
New Record
Exists?
Add Note
Add Drug
Add Flags
No
More
Patients
?
No
Logout
Yes
Pharmacist
Search for patient
Yes
View Info or Add
Notes
No
Advised to
check EMR
Exists?
Yes
More
Patients
?
No
Logoff
Patient Record
Exit
Enter Drug
Yes
No
Flag
Yes
Drug In
Database?
No
Interaction
& Proper
Dosage?
No
Flag
Client
Database
Server
Application
Connector
Patient
Schema
Patient
Schema
System
Schema
Client
Server
EMR Database
Patient and
System
Schema
Patient
Schema
MHS
Software
Client
Database
Server
Database
Client/Server Relationship
Logging In Use Case
Primary Actor: User (e.g.
Nurse)
Precondition: User hasn't
logged in yet
Main Success Scenario:
1) User enters credentials
2) System validates user
3) System presents user
with main page
Exception Scenarios:
2)
a. Username does not exist
•System alerts user and aborts
log in
b. Password does not match
username
• System alerts user and aborts
log in
Logging In Sequence Diagram
Search for Patient Use Case
Primary actor: User (e.g.
Nurse)
Precondition: User has
successfully logged in.
Main Success Scenario:
1) User enters patient's first
name, last name, and date of
birth
2) System searches database
for patient record
3) System returns a record
Exception Scenarios:
1)
a. User enters invalid characters.
• System alerts user
2)
a. Patient is not in database
• System returns empty record
3)
a. Database can't be accessed
• System alerts user
Search for Patient Sequence Diagram
Verify Drug Use Case
Primary Actor: Nurse
Precondition: Nurse is viewing
the summary
Main Success Scenario:
1) Nurse submits drug
information
2) Drug information
checked against Database
3) Nurse is notified of
nonexistent drugs, spelling
errors, or invalid dosage range at
the verification page.
4) Nurse confirms and makes the
appropriate changes
5) System removes the
Questionable Marker for Drugs
that are verified
Exception Scenarios:
4)
a. Nurse fails to confirm, but attempts to
write to Database
• System prompts to confirm
Verify Drug Sequence Diagram
Add Drug Use Case
Exception Scenarios:
Primary Actor: Nurse
Precondition: Nurse is currently
2) Drug does not exist
filling out patient record
a) Highlight nonexistent drug and mark as
Main Success Scenario:
questionable in the patient record schema
1) Nurse types in drug info
2) System checks for
proper
drug info
3) System writes drug to
client DB
2) Drug dosage out of range
a) Highlight drug and mark as questionable
in the patient record schema
Add Drug Sequence Diagram
Add New Record Use Case
Primary Actor: Nurse
Exception Scenarios:
Precondition: Nurse logged in,
patient not in Client DB
2)
Main Success Scenario:
1)Nurse fills out patient info
2)Nurse clicks "Add" button
3)Patient record created
4)Nurse shown patient record
a. Patient exists in Client DB
• Prompt with option to append
data to existing record
Add New Record Sequence Diagram
Add Note To Patient Use Case
Primary Actor: Pharmacist
Precondition: Pharmacist is
currently looking at a patient's
record
Main Success Scenario:
1) Pharmacist types in note.
2) Note is added to the patient
record in the server database.
Exception Scenarios:
1)
a. Pharmacist is unable to
access the add note function.
2)
a. Note is not added to the
patient record in the server
database.
Add Note Sequence Diagram
Mark Drug As Questionable Use Case
Primary Actor: Nurse
Exception Scenarios:
Precondition: Nurse is entering
patient drug information.
1)
a. Drug is accepted by the
system.
2)
a. Drug is ignored by the system.
3)
a. There is no notification of the
questionable drug.
Main Success Scenario:
1) Nurse enters an unknown
drug.
2) Drug is not recognized in the
server database.
3) Drug is marked as
questionable by the system.
Mark Drug As Questionable
Sequence Diagram
Sync Client DB with Server DB Use Case
Primary Actor: System
Exception Scenarios:
Precondition: Nurse has
finished reconciliation.
1)
a. No network connectivity.
• Data continues to be stored on
local database. User may be
warned if necessary.
Main Success Scenario:
1) Program connects to Server
DB
2) data is inserted into Server DB
3) Server DB sends
acknowledgement to program
4) Patient data is deleted from
Client DB
2)
a. Server DB does not update
successfully
• No acknowledgement would
have been sent and information
would continue to be safer on
Client DB.
Sync Client DB with Server DB
Sequence Diagram
Sync Server DB with Client DB Use Case
Primary Actor: System
Exception Scenarios:
Precondition: program has
active connection to project
database
1)
a. Cannot reach Server DB.
• Client DB will not be updated.
Main Success Scenario:
2)
a. Version number of Client DB
is greater than version number of
Server DB
• Do nothing
1) Client DB sends version
number to Server DB
2) Server DB compares Client
version with Server DB version
3) Client DB updates
Sync Server DB with Client DB
Sequence Diagram