CVM Mediator Team 6 Eduardo Flores Ivan Olmos

CVM Mediator Team 6 Eduardo Flores Ivan Olmos Jandry Guerra Luis Bautista Mentor: Dr. Peter Clarke 1

Copyrights and Trademarks Microsoft® Health. Vault™ Copyright© 2010 Microsoft®. All contents of the Service are Copyright Microsoft Corporation. Teges Corp™ i. Rounds™ Copyright © 2001 -2002 Teges Corp. All rights reserved. All of the deliverable code in SQLite has been dedicated to the public domain by the authors. Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original SQLite code. Microsoft® SQL Server® JDBC Driver 3. 0 © 2007 Microsoft® Corporation. All rights reserved. 2

Problem Definition Patient has to be responsible for its medical documents, which include its past and present information. Retrieving information with the current system has proving to be an expensive and time consuming task for the provider. Current System Problems/Limitations üTime Consuming and Expensive §(ex. Physical pick up approach) üUnreliable §(ex. Store & Secure information) 3

Project Management Main Task: • Feasibility Study • Implementation • • Use Case Identification System Design • High Level Requirements • Testing Name Deliverable 1 Deliverable 2 Final Deliverable 3 Eduardo Flores Minute Taker/ Time Keeper/ Team Leader/ Business Analyst Developer Designer Ivan Olmos System Analyst Minute Taker/ Team Leader/ Time Keeper/ System Analyst QA Manager Designer Jandry Guerra Team Leader Minute taker/ Time Keeper Architect Developer Luis Bautista Time Keeper/ Team Leader QA Analyst/ Minute taker/ Business Analyst Developer Integrator 4

UML Use Case Diagram Total Number of test cases: 25 Implemented Use Cases: 11 5

Functional Non Requirements CVM-M - HL - 07 - Query Information Frequency CVM-M - HL - 07 -are Query Information On, average, 600 queries made daily by CVM-M users. Pre-Conditions Criticality Description Risk Reliability The CVM-M user has successfully logged onto the system -Use case begins when CVM-M user enters the patient id. Medium. Implementing this use case requires the knowledge of SQL -Use case ends when the CVM- user clicks on the Search Syntax. button. High. Allows CVM-M users to request patient’s health records Mean time to Failure – 5% failures for every twenty four hours of Post-Conditions The patient’s data will be query from the data sources of operation is acceptable. which the patient is linked to. Availability – System should be available all the time except during server maintenance. Performance System shall be able to handle 10 requests per second. 6

Functional Non Requirements CMV-M-SL-10 -Compiling Information Frequency CMV-M-SL-10 -Compiling Information An average of 600 request are made daily by users. Pre-Conditions The CVM-M user has successfully logged onto the system Criticality High. User needs to know if patient has any medical history Description -Use case begins when CVM-M user clicks on Search button. available. -System shall start to compile all data sources base on Risk High. This implements data base searches and storing. patient ID. Performance System should be able to handle on average of 100 request -Use case ends when compile information is put into per hour. temporary storage. Supportability Should handle a database, data file such as documents, Post-Conditions System save information to file. photos, videos, and any file that contains information. 7

System Design 8

System Decomposition Client-Server Architecture Model-View-Controller 9

System Deployment 10

Persistent Data Design 11

Detailed Design 12

Proxy Pattern • Source_Interface • Organized_DS • CCD_DS • Teges. ICU_DS Mediator. Pattern • DS_Mediator • DS_Objects 13

State Machine 14

Algorithm Depth First Search Clinical Lab Results Document 2) Record • Runtime: O(V Target e. i Chemistry Adjacency Matrix Lab (1) Name ID Phone Address … • The depths first search e. i Glucose Lab test … Lab test algorithm is used to traverse a Lab tree structure to print an XML Alerts Medications Results 105 Value file Teges Database Health Vault CCD <results> <entry> <organizer> <name>Chemistry</name> CDA (RIM) Health Teges ICU <result> Info Structure DB Structure Lab (n) <name>Glucose</name> <value>105</value> </result> </organizer> Graph </entry> </results> Problems • The leafs of Record Target and Health Info are indexed Immunization XML Procedures

Test Cases Sunny Day Rainy Day Test Case ID CVM-M-Query Information-SD-01 CVM-M-Query Information-RD-01 Purpose To test is the system allows to search an non-existing patient To test if the system allows to search an existing patient Test Setup • The CVM-M application is running • Patient ID: “ 77777” and isand linked to linked both Health Patient with ID: “ 88888” doesexist not exist, is not to Health Vault and Teges. ICU Vault or Teges. ICU Test Inputs Patient ID: “ 88888” is entered Patient ID: “ 77777” is entered Click on “Search” button Expected Output Message is displayed “User Does not Exist in the System” See Test Demo 16

Test Cases Rainy Day Sunny Day Test Case ID CVM-M-Compile Information-SD-01 CVM-M-Compile Information-RD-01 Purpose Test Setup To test if data is compiled, when patient Id does not exist To test if data is compiled using only the Health Vault database The CVM-M application is running Patient with ID: “ 66666” does not exist and is not linked to the User “drjohn” is logged onto the system Teges. ICU or. ID: Health Vaultexist in our system and is linked to only Patient with “ 99999” Test Inputs Expected Output Patient ID: “ 66666” is entered Health Vault patient “Jane” Click on “Search” button Patient ID: “ 99999”is entered Message is displayed “User Does not Exist in the System” Click on “Search” button Patient 99999 Health information is compiled and displayed *See Test Demo 17

Subsystem Testing Subsystem tests and coverage were performed using the following tools Automated Testing Tool �JUnit Coverage Tool �Ecl. Emma Subsystem line coverage Obtained: 95. 4% 18

Demo 19

Questions 20