Performance Analysis of Integration of Different Medical Systems by Cloudsim
Implementation Plan:
——————
Step 1: Initially, we create a CloudSim environment with defined numbers of users, data centers, virtual machines, brokers, and cloud service providers. Configure a model of 3 hospitals, each with a private cloud, connected through a community cloud.
Step 2: Then, we register the patients with a fingerprint-based authentication system using a dataset.
Step 3: Then, we Set up dedicated virtual machines in each hospital’s private cloud to store updated EMR data. These VMs include one active and one standby VM for patient record exchange.
step 4: we should create a cloud for Government for example( Government ID ,name, date of birth, gender) based on dataset values.
Step 5:Next, we retrieve the patient’s data based on their fingerprint identification.
Step 6: Next, we implement HL7 FHIR (Fast Healthcare Interoperability Resources) for effective communication between VMs.
Step 7: Then, we implement the Least Response Time (LRT) Load Balancing to Load the patient records under high Demand.
Step 8: The subsequent performance metrics were used to validate the recommended techniques:
8.1: Number of Tasks vs Execution Time (s)
8.2: Number of Tasks vs Memory Utilization Rate (%)
8.3: Number of Tasks vs Throughput (%)
8.4: Number of Tasks vs Latency (ms)
8.5: Number of Users vs scalability (%)
8.6: Number of cloudlets Vs Failure Rate (%)
8.7: Number of cloudlets Vs Recovery Time (s)
8.8: Time(s) vs Data Transfer (%)
Software Requirement:
1. Tools: Net-beans 12.3 or above with Cloud-sim
2. Programming Language: JAVA – 1.8
3. Operating System: Windows – 10 (64-bit) or above
Note :-
1) If the above plan does not satisfy your requirement, please provide the processing details, like the above step-by-step.
2) Please note that this implementation plan does not include any further steps after it is put into implementation.
3) If the plan satisfies your requirement, Please confirm with us.
4) Project based on Simulation only, not a real time project.
5) Please understand that any modifications made to the confirmed implementation plan will not be made before or after the project development.
| Technology | Ph.D | MS | M.Tech |
|---|---|---|---|
| NS2 | 75 | 117 | 95 |
| NS3 | 98 | 119 | 206 |
| OMNET++ | 103 | 95 | 87 |
| OPNET | 36 | 64 | 89 |
| QULANET | 30 | 76 | 60 |
| MININET | 71 | 62 | 74 |
| MATLAB | 96 | 185 | 180 |
| LTESIM | 38 | 32 | 16 |
| COOJA SIMULATOR | 35 | 67 | 28 |
| CONTIKI OS | 42 | 36 | 29 |
| GNS3 | 35 | 89 | 14 |
| NETSIM | 35 | 11 | 21 |
| EVE-NG | 4 | 8 | 9 |
| TRANS | 9 | 5 | 4 |
| PEERSIM | 8 | 8 | 12 |
| GLOMOSIM | 6 | 10 | 6 |
| RTOOL | 13 | 15 | 8 |
| KATHARA SHADOW | 9 | 8 | 9 |
| VNX and VNUML | 8 | 7 | 8 |
| WISTAR | 9 | 9 | 8 |
| CNET | 6 | 8 | 4 |
| ESCAPE | 8 | 7 | 9 |
| NETMIRAGE | 7 | 11 | 7 |
| BOSON NETSIM | 6 | 8 | 9 |
| VIRL | 9 | 9 | 8 |
| CISCO PACKET TRACER | 7 | 7 | 10 |
| SWAN | 9 | 19 | 5 |
| JAVASIM | 40 | 68 | 69 |
| SSFNET | 7 | 9 | 8 |
| TOSSIM | 5 | 7 | 4 |
| PSIM | 7 | 8 | 6 |
| PETRI NET | 4 | 6 | 4 |
| ONESIM | 5 | 10 | 5 |
| OPTISYSTEM | 32 | 64 | 24 |
| DIVERT | 4 | 9 | 8 |
| TINY OS | 19 | 27 | 17 |
| TRANS | 7 | 8 | 6 |
| OPENPANA | 8 | 9 | 9 |
| SECURE CRT | 7 | 8 | 7 |
| EXTENDSIM | 6 | 7 | 5 |
| CONSELF | 7 | 19 | 6 |
| ARENA | 5 | 12 | 9 |
| VENSIM | 8 | 10 | 7 |
| MARIONNET | 5 | 7 | 9 |
| NETKIT | 6 | 8 | 7 |
| GEOIP | 9 | 17 | 8 |
| REAL | 7 | 5 | 5 |
| NEST | 5 | 10 | 9 |
| PTOLEMY | 7 | 8 | 4 |