• No se han encontrado resultados

METODOLOGIA DE TRABAJO DE AUDITORÍA INTERNA Y CONSEJO DE

In document MANUAL DE AUDITORíA INTERNA (página 43-47)

The software development provides a description of the design of the application for Android Based Application for Pressure and Real-Time Pulse Rate Monitor with SMS Alert Notification. The programming part for the

Microcontroller was developed using ProtonIDE which is similar to visual basic commands. The nature of the program is to gather data stored in the memory of the digital blood pressure and then transmit to the microcontroller then transfer the data to the android device with the help of Bluetooth unit. Meanwhile in order for the android phone to be able to communicate with the microcontroller it requires application software installed on the smart phone, the researchers apply the JAVA programming schemes deploying it on a particular software known as Basic4android.

In Figure 3.7 (a) to (c), it displays the program flow of the proposed design system. The system starts when sufficient power is supplied. After powering on the device, the system is now ready and will initialize all of the variables, input ports and output ports in order to ready the necessary requirements for the other processes and to avoid unwanted and unstable states. After initializing the variables and ports, the restricted activity which can either be lying, standing or walking, is sent by the PC and is received by the wireless

34 module. A delay of 1 second is placed to ensure that no data loss occurs from the PC to the wireless module. After which, the current activity is detected by the microcontroller's interpretation of the accelerometer's input which can result to lying, standing or walking. A delay of 0.5 second is placed to properly process the data. Now, the microcontroller will check if the restricted activity is equal to the current activity, and will trigger on the buzzer if found true and will trigger off if not. After checking the restriction, the microcontroller will check if the current activity is not equal to the last activity. If it is equal, the value of the last activity will be replaced by the current activity. If it is not equal, the current activity will be sent to the PC through the wireless module. By this time, the system flow will repeat and will go back to the step where the restricted activity is obtained.

As shown in Figure 3.7(a), assuming that the patient wishes to monitor their pulse rate first, the system starts by supplying the MCU with enough power to turn it on. When the MCU is turned on, the system will establish connection via Bluetooth connectivity, it will search for the available connection for the system to connect to. After the connection has been established the system’s prerequisite is for the patient to input the necessary information, as soon as the information is saved in the database the user can precede to initial values of the readings which is set to initial value of 0 or to choose either to modify the existing record or to create new one. Once the patient proceeds to calibration, the system will display the pulse rate measurement. If the system calibration

35 fails, the system will recalibrate until it successfully acquires the data from the heart rate circuit.

There is a small delay for the calibration to finish then values for the real- time heart rate will be displayed. It will then be stored on the database for record access purposes. The system will then compare the measured heart rate to the registered heart rate of the patient if the heart rate is above or below the assigned rate the system will send an SMS to the doctor/physician indicating irregular heart rate or pulse rate which can be seen on Figure 3.7 (b). The patient can choose to view history or to continue with the blood pressure monitor. If the patient selects the blood pressure monitor, the device must be on for the smart phone application to obtain data from the digital blood pressure device, as shown in figure 3.7 (c) the system will display the values from the device as long as the device is turned on, the system will fail to acquired data if the system is offline. The system performs comparison between assigned systolic and diastolic blood pressure and the measured values, the system will send an SMS if the patient has irregular blood pressure which is similar to heart rate. History viewing can be seen on figure 3.7 (a), the gathered numbers are stored in an individual patient record with data and time of the patient’s diagnosis.

36 Start Establish Connection with Bluetooth Yes Reconnect MCU turned on? No Yes No Login Information Complete? Calibration Success? Modify and Save on Database Tapped Start Calibration on Android Application Yes No Yes No Input Patient’s Information Recalibrate ShowBP button Tapped 2 1 3 Exit? Yes Yes No No View History Tapped Display Reading Real Time Display of HR Values Save Record to Database

37

2

Heart Rate Above or Below

Assigned Rate

Send Message 1 and 2

Yes No Is the heart rate

normal Yes No 1 Exit? End Yes No No

38 3 Blood Pressure Above or Below Assigned Rate Display Blood Pressure Values

Send Message 1 and 2 Yes 1 Exit? End Yes No Save Record to Database No Check Device Connected Reconnect Yes No

39 Data Model

Figure 3.8: Case Model Diagram

The figure above shows the case model of the system. It displays the basic functionalities of the system. Initially, the user is capable of doing three functionalities; create a patient record, measure blood pressure and heart rate, and to display previous records/readings. Two of these tasks have sub-processes that could be done upon choosing the task. For the measurement of the BP and heart rate, real time measurement of the heart rate is obtained once the smart phone is connected to the device via Bluetooth, and blood pressure can be obtained by pressing the “inquire BP” button on the smart phone. For the display of the readings/records, the latest blood pressure and heart rate reading can be viewed, and lastly, the logs, which contains the time when the data is acquired.

40

C. Prototype Development

In document MANUAL DE AUDITORíA INTERNA (página 43-47)

Documento similar