referring now to fig1 there is shown a diagram for a system 400 for measuring and predicting an insulin dosing rate to bring a patient &# 39 ; s blood glucose level into a preferred target range . the measurement and prediction system 400 may be a stand alone system or may be portable to be carried by the attending physician or caregiver from one patient to another , as will be described in following paragraphs . measurement and prediction system 400 includes microprocessor 402 which is used for actuating a computer program for measurement and prediction of the patient &# 39 ; s blood glucose level and further for storing and maintaining the patient &# 39 ; s blood glucose level taken at predetermined time intervals . the microprocessor 402 of the prediction and measurement system 400 may be incorporated with a hard drive 404 and includes a display 406 , which may be in the form of an lcd monitor or some other well known type of display system . the display 406 may incorporate keyboard 416 for input of data from data block 408 . alternatively , display 406 may be a touch screen type of input device which is well known in the art . the input mechanism 408 inputs a preferred target range for a particular patient &# 39 ; s blood glucose level . measurement and prediction system 400 further includes alarm mechanism 410 which alerts a user when the patient &# 39 ; s glucose level is external to the preferred patient glucose target range . the alarm may be an audio alarm in the form of a buzzer or some like audio sounding mechanism or may be visual in nature to provide a warning message or other type indicia indication on display 406 . it is to be understood that microprocessor 402 , input block 408 , alarm 410 , hard drive 404 and display 406 with keyboard 416 may all be incorporated into a single handheld unit comprising system 400 . referring to fig2 a and 2b , there is shown the overall block diagram associated with the prediction and measurement system 400 as provided in fig1 . initially , block 10 refers to a start procedure block where microprocessor 402 and associated display 406 are actuated . initially , the information flow passes to decision block 14 where there is a decision made as to whether this is the start of a new patient or whether there is a resumption of the iv treatment for the patient which is determined in decision block 16 . referring again to fig2 a and 2b showing the overall block diagram for computer actuation programs in processor 402 , the initialization begins in block 10 where the logic inquires as to whether this is the start of a new patient in decision block 14 . if the start of the new patient is to be actuated , logic flows to decision block 22 deciding whether this is an intravenous treatment or subcutaneous treatment . input may be made on keyboard 46 or directly on display 406 if it is a touch screen actuation . if intravenous treatment is input , logic flow extends to the decision block 24 where it is determined whether a standard intravenous dosing is to be provided or whether an express intravenous treatment is to be entered as shown in block 26 . if express intravenous treatment is either chosen by the user or is preset within prediction and measurement system 400 , the logic flow passes to fig3 through information line 500 where patient information and settings are entered into microprocessor 402 at logic block 64 ( shown in fig3 ). in the express intravenous treatment provided in block 26 much fewer options are needed to be entered by the attending physician or caregiver than the standard options as will be seen in following paragraphs . in block 64 the patient general id information is provided including patient id , age , weight and height . once entered in logic block 64 , the logic flows to decision block 66 where a determination is made as to whether a custom sensitivity factor is to be provided . if a custom sensitivity factor is to be used in the dosing rate , then the logic flows to logic block 68 where the sensitivity factor is entered by the attending physician or caregiver . the initial sensitivity factor is an empirically defined sensitivity factor which may be entered as 0 . 01 , 0 . 02 , 0 . 03 , or 0 . 04 , etc . which defines the speed at which the blood sugar initially falls during a time interval . for older patients a lower sensitivity factor will cause the dosing rate to be adjusted in a slower manner whereas in younger patients there would be a more aggressive approach and a higher initial sensitivity factor would be selected . the sensitivity factor which is entered into processor 402 may be provided by the physician or caregiver . once the sensitivity factor is entered in block 68 , which is the patient &# 39 ; s sensitivity to insulin , the logic flow passes to target range 70 wherein the preferred blood - glucose target range for a particular patient is entered . the target range is the range which would be acceptable for the patient with respect to the blood glucose level . in general , there are options available to choose for an appropriate target range . the choice of an option is dependent upon a patient &# 39 ; s physical state and may generally be between 70 - 100 mg / dl for a hyperosmoler patient . for a non - hyperosmoler patient the range may be between 120 - 160 mg / dl . for a pregnant female the range most often chosen is between 90 - 120 mg / dl . where the patient &# 39 ; s physical state is improving , the target range is between 100 - 140 mg / dl . the preferred target range is individualistic between patients and is chosen by the attending physician as a function of the aforementioned variables as well as a particular patient &# 39 ; s history . once the blood - glucose target range has been inserted , the logic flows to logic block 40 on line 510 ( shown in fig2 b and 3 ). in block 40 the patient &# 39 ; s initial blood glucose level is entered into processor 402 and the logic then flows to logic block 42 ( in fig2 b ). in block 42 the blood glucose level entered in block 40 is confirmed . if there is a confirmation then the logic flows to block 44 where various parameters external to the patient &# 39 ; s parameters are entered such as the attending physician &# 39 ; s ( or nurse / caregiver ) name and identification . the logic then flows to block 54 where identification of any changes in the patient &# 39 ; s condition are shown which could affect the blood sugar level . such changes are then listed and provided on display 406 . such changes may be the addition or discontinuation of specific medication , physical condition change such as a stroke or myocardial infarction or bleeding or any other condition which must be taken into account by the physician . also , medications and nutritional changes which may require more or less insulin to offset any nutritional changes is taken into account in block 54 . once all the inputs are inserted into the computer , the logic flows to algorithm block 52 through information line 610 to determine the blood - glucose dosing rate . the algorithm block 52 and subcomponents of the logic flow are seen in fig5 . a display warning in block 96 is provided if the blood glucose is greater than 250 ( which shows diabetic ketoacidosis ) in block 98 or blood glucose is greater than 500 ( warning for hyperglycemic / hyperosmolarity ) in block 100 ; or blood glucose is lower than the range of 30 - 85 in block 102 ( which provides for a hypoglycemia warning ). additionally , a warning is given for a change in the blood glucose level from the last time interval initiation if it shows a change of blood glucose greater than 100 in block 104 providing for a glucose velocity warning ; and , if there is an insulin rate high insulin resistance warning in block 106 . all of these are provided in the display warning 96 block and are provided directly to the user as a visual warning or may be transmitted to a server 412 or remote station 414 or some paging system or a text message or e - mail to be sent over the internet . if no warning is necessary in blocks 96 , 98 , 100 , 102 , 104 , or 106 the logic flows to decision block 108 from block 92 which determines whether the blood glucose level is in the target range which has previously been input in decision block 40 in fig2 b . if the blood glucose is determined to be within the target range in decision block 108 , logic flows to decision block 116 where it is determined whether the blood sugar level has been within the target range for more than a predetermined time ( standardly being three hours ). if the blood glucose level has not been within the target range within the predetermined time interval the timer is then set in block 128 to a default time interval ( which may be one hour or two hours , etc .). in the event that the blood glucose level has been within the target range for the previous time interval then the logic flows to block 126 where the timer is set to some maximum time interval empirically dependent upon the physician or attending caregiver . referring back to decision block 108 , if the blood glucose level is not within the target range then the logic flows to decision block 110 to determine whether the blood glucose level at this time is greater than the previous blood glucose level . if the current blood glucose level is greater than the previous blood glucose level then the logic flows to block 118 where the sensitivity factor is increased between 10 %- 50 % ( the actual percentage being protocol dependent ). having increased the sensitivity factor by a predetermined amount ( either based upon the physician &# 39 ; s or caregiver &# 39 ; s empirical input or protocol ), the flow then goes to block 132 where the dosing rate or iv insulin infusion rate is calculated . the calculation is made in accordance with the formula : in the above formula , the constant k may also vary based on rate of blood glucose change and the target blood sugar range , however , such still being in accordance with the constant k being within the range 40 & lt ; k & lt ; 80 . in logic block 134 the carbohydrate insulin ratio is calculated in general as being 0 . 4 - 0 . 6 divided by a sensitivity factor . the carbohydrate insulin ratio is a number used to calculate how much insulin is needed to offset carbohydrate intake so that a patient &# 39 ; s blood glucose level is not affected . once the carbohydrate insulin ratio is determined in block 134 , the logic flows to decision logic block 136 where a determination is made as to whether the blood glucose is less than or equal to the constant k . if the blood glucose in block 136 is less than k then the logic flows to logic block 140 where insulin dosing is terminated . instructions are then provided in block 146 to administer d50 which is dextrose 50 % in accordance with the formula amount of d50 =( 100 − bg )×( 0 . 3 - 0 . 5 ). the timer is then set to the hypoglycemic time interval in block 148 where the hypoglycemic time interval is reset to a predetermined time interval which may be in general 30 minutes . in the event that the blood glucose level is greater than k then the logic flows to decision block 138 where it is determined whether the blood glucose is within the range of k & lt ; bg & lt ;( low end of the preferred blood - glucose target range ). if the bg is within the range then the logic flows to block 142 where the timer is set to a time interval to prevent hypoglycemia . if the bg is not within the range of k & lt ; bg & lt ;( low end of target range ) then the logic flows to logic block 128 setting the timer to a default time interval . in the event that the blood glucose is not within the target range in decision block 108 the logic flows to decision block 110 where a decision is made as to whether the current blood glucose level is greater than the previous blood glucose level at the previous time interval . if the current blood glucose level is determined to be less than the previous blood glucose level in decision block 110 the logic then flows to logic block 112 where a decision block is provided to determine whether the blood glucose level is above the target range . if the blood glucose level in block 112 is determined to be above the target range , the logic then flows to decision logic block 120 to determine whether the blood glucose decrease is less than 15 % from the previous interval . if the blood glucose decrease is less than 15 % of the previous time interval , the logic flows to logic block 118 which provides for an increase in the sensitivity factor within the range of 10 - 50 % which is empirically entered by the attending physician or caregiver . once the sensitivity factor has been increased the logic then flows to block 132 as previously discussed to provide for the iv insulin infusion in accordance with the previous formula . if the blood glucose decreases between the previous interval and the present time is equal to or greater than 15 % than the logic flows to decision block 122 where the blood glucose decrease is determined as to whether it is greater than 66 %. if the blood glucose level has decreased greater than 66 % then the logic flows to block 130 where the sensitivity factor is decreased in accordance with the protocol of the physician or caregiver . once the sensitivity factor decrease has been entered the logic then flows to block 132 to determine the insulin dosing rate in accordance with the previously derived formulas . if the blood glucose decrease is equal to or less than 66 % then the logic flows to block 123 and no sensitivity factor change is provided . once no sensitivity factor change is inserted , the logic flow then once again passes to iv insulin infusion block 132 . referring back to decision block 112 , if the blood glucose level is below the target range , the data flow passes to decision block 124 where a decision is made as to whether the blood glucose increase between the previous interval and the present time is less than 15 %. if the blood glucose increase between the last time interval and the current time is less than 15 % then logic flows to block 130 where the sensitivity factor is decreased and the information flow then passes to block 132 for the iv insulin infusion calculation . if the blood glucose increase is not less than 15 % then the logic flow passes to block 123 where there is no sensitivity factor change and flow of data passes to block 132 for determining the dosage rate in accordance with the previous detailed formulas . returning to fig2 b and algorithm block 52 , once the insulin dosing rate has been determined , a confirmation is displayed on display 406 as to the insulin and glucose infusion . at this point the attending physician or caregiver may override the dosing in decision block 46 . if the algorithm dosing rate is confirmed and no override is provided in decision block 46 the logic passes to iv treatment information page block 18 which will be detailed in following paragraphs . if it is determined to override the dosing rate as provided by algorithm block 52 , the attending physician or caregiver enters the glucose / saline rate in block 48 and the logic passes to a decision block 56 where a display is provided to confirm the override . if the override is canceled , then the logic flows back to block 50 where a confirmation of the insulin and glucose infusion rate from algorithm 42 is confirmed . if override is confirmed in decision block 56 , the logic flows back to block 50 for a confirmation of the insulin and glucose infusion as previously discussed . referring back to fig2 a , if in decision block 24 a standard intravenous route is to be performed , the logic flows to standard intravenous treatment block 28 where the patient information such as patient id , weight , age , medications , disease state and further identification factors are inserted into microprocessor 402 through the display 406 and keyboard 416 or other touch screen input . once the patient information has been entered in block 30 the user has the option to go back to standard intravenous treatment block 28 in order to modify the treatment . however , once the information has been entered in block 30 , the logic flows to flow block 32 where the insulin concentration and sensitivity factor for the patient is entered . flow then continues to decision block 34 where it is determined whether a custom sensitivity factor is to be inserted by the user . a custom sensitivity factor may be entered in block 36 based upon the empirical knowledge of the physician or caregiver . in the event there is no custom sensitivity factor to be entered , the flow goes directly to selection of the target range infusion variables in flow block 38 . thus , whether a custom sensitivity factor is to be entered or a standard sensitivity factor is to be entered , the flow logic ends at information block 38 where a selection of the blood glucose target range is made . from block 38 posing on information line 520 ( to fig2 b ), the blood glucose level of the patient is provided in flow block 40 in the same manner as derived from the express intravenous treatment block 26 previously discussed . once the blood glucose level of the patient has been entered , the logic flow passes to a confirmation of the blood glucose in block 42 , entering caregiver &# 39 ; s identification in block 44 and then to changes in condition in block 54 prior to passing to algorithm block 52 . the algorithm block 52 calculates the dosing rate of the insulin as previously discussed for the express intravenous treatment flow in block 26 . finally , in accordance with the previously discussed data flow , the information passes to confirmation of the insulin and glucose infusion in block 50 and then to the override dosing decision block 46 and decision block 56 . where there is no override dosing in decision block 46 , logic flow passes to the intravenous treatment information page block 18 . thus , whether in decision block 16 entitled “ resume iv patient ” where there is a resumption of the iv patient or in either the express intravenous treatment or standard intravenous treatment calculations , all information flows to iv treatment information page 18 as shown in fig2 a and 2b . further discussion of iv treatment information page 18 will be provided in following paragraphs . referring back to fig2 a , what has previously been discussed is the follow on logic flow from decision block entitled “ intravenous treatment ” where a standard or express intravenous treatment has been entered . in the event that the treatment is to be subcutaneous , the information flow passes from intravenous treatment decision block 22 to subcutaneous block 20 and then enters fig4 on information line 530 . referring to fig4 , subcutaneous block 20 ( shown on fig2 a ) is provided for information to be entered as to the patient &# 39 ; s physical parameters in block 74 . once the patient information has been entered in block 74 , a selection of a short acting type subcutaneous treatment is provided in block 76 and a long acting type subcutaneous treatment is entered in block 78 . at the physician &# 39 ; s or caregiver &# 39 ; s directions , both a short - acting type subcutaneous treatment and a long - acting type subcutaneous treatment may be entered . from block 78 , the information passes to the subcutaneous algorithm block 84 . with regard to the subcutaneous algorithm block 84 , the calculations made therein are provided in information block 80 , information block 82 and information block 87 dependent upon a decision as to be made in decision block 83 as will be described in following paragraphs . the subcutaneous algorithm block 84 acts on both a pre - prandial dosing rate calculation or on a post - prandial dosing rate . where there is a pre - prandial dosing rate to be provided to the patient the calculation is made in accordance with the following formulation : cir = 2 . 8 ⁢ xw t tdd ( 3 ) with regard to a post - prandial dosing rate the subcutaneous algorithm 84 calculates the dosing rate in accordance with the following formula : thus , as far as the logic flow is concerned , the carbohydrate insulin ratio is calculated in block 80 and then the total daily dose ( tdd ) is calculated or provided in information block 82 dependent upon whether the patient is a type 1 patient or a type 2 patient . the type 1 patient is for a patient who is insulin dependent and a type 2 patient is for a patient which is non - insulin dependent , such terms well known in the art and discussed above . the information then passes to decision block 83 where it is determined whether this is a post - prandial treatment or a pre - prandial treatment . if it is not a post - prandial treatment the information passes directly back to subcutaneous algorithm block 84 and in the event it is a pre - prandial treatment decision in block 83 it passes to block 87 where a correction factor is provided to the algorithm and then the dosing rate is calculated based upon the correction factor , the blood glucose level , the target blood glucose level of the patient and the correction factor itself . from the subcutaneous algorithm block 84 , confirmation is made as to the dosage rate in block 88 which is displayed on display 406 for the physician or caregiver &# 39 ; s review . once this is confirmed , the information passes to the subcutaneous treatment page 90 on information line 540 ( fig7 a ), to be discussed in following paragraphs . referring back to fig2 a and 2b , whether the resumption of the intravenous patient in decision block 16 is answered “ yes ” and the override dosing decision in block 46 is answered “ no ”, then information passes to the iv treatment information page 18 . the iv treatment information page 18 provides for numerous options to be taken by the physician or caregiver as well as a decision as to whether a conversion to subcutaneous treatment is to be made from the intravenous treatment . referring now to fig6 a and 6b , the intravenous treatment information page 18 is provided as an initialization point and the caregiver can choose to transfer a patient ( information ) in block 146 and selects a transfer unit in block 152 for transference of the data to the data block 160 . the transfer information block 146 is provided to allow transfer of the information provided to the display 406 , the remote station 414 , to a server 412 or some other transfer unit . the data 160 is stored within the microprocessor 402 or some external transfer device . the physician or caregiver may also view the history of the blood glucose level for the particular patient and other parameters of the patient in the view history block 148 and this can be transferred to a display graph in block 150 . additionally , the patient information may be updated in block 154 and inserted into microprocessor 402 in patient information block 156 wherein patient information may be directly sent to the iv treatment information page 18 for viewing or insulin / infusion settings may be provided in block 158 and passed to data block 160 . additionally , data from the iv treatment information page 18 may be passed to a print data information block 162 where a decision is made as to print options in decision block 164 where the information may be printed in block 166 or whether no print information is to be sent back to the information treatment information page block 18 . in some cases , the attending physician or caregiver may decide to convert the intravenous settings to a subcutaneous dosing rate through information line 620 to block 172 where the settings in microprocessor 402 are set to a subcutaneous dosing rate . the information then flows to a decision block 174 where it is determined whether the patient is stable or not stable . if the patient is not stable , information passes to information block 168 and then back to the intravenous treatment information page 18 on line 640 . if the patient is stable in decision block 174 information then passes to information block 178 where a selection is made as to a long - acting type dosing rate and / or a short - acting dosing rate . once the selection is made in block 178 , information is then passed to the information block 182 where a calculation is made in accordance with the formula : basal ⁢ ⁢ dose = ( . 1 - . 9 ) × tdd ⁢ ⁢ total ⁢ ⁢ daily ⁢ ⁢ dose ⁡ ( tdd ) = 1000 × sf ⁢ ⁢ correction ⁢ ⁢ factor ⁡ ( cf ) = cfr tdd ⁢ ⁢ cfr = 1500 + ( ( 0 . 06 - sf ) × 10 ⁢ , ⁢ 000 ) ( 6 ) information then passes to decision block 184 entitled “ back to iv / discharge ”. if it is decided to maintain the patient on an intravenous dosing rate the information then simply flows back to intravenous treatment information page 18 through information line 650 . if the decision is made to discharge the patient from subcutaneous dosing treatment in block 186 information passes to “ confirm discharge ” block 186 . information is inserted into information block 196 “ diagnostic check ”. the information then flows to decision block 197 which determines whether the hemoglobin aic is less than or equal to 7 . 2 . if the hemoglobin aic in decision block 197 is less then or equal to 7 . 2 the information passes to block 195 where an alert is displayed to the user recommending that the physician consider oral agent prescription for the patient . information then passes to block 198 where the patient is discharged and returns to the start block 10 . if the aic is greater than 7 . 2 oral agent block 195 is bypassed and information simply enters patient discharged block 198 . another branch of the intravenous treatment information page 18 in fig6 b is provided where the exit block 188 may be entered on line 620 which is a discharge patient block information data input . the decision to discharge goes to decision block 190 which gives the option to either “ exit ”, “ discharge ”, or “ cancel ”. if it is desired cancel this portion of the program the information passes back to intravenous treatment information page 18 on line 630 for new input to be inserted . if the patient is to simply exit the program , the information passes back to the start block 10 for new insert of data as provided in fig2 a . if a discharge of the patient is to be made , the confirmation of discharge is made in block 192 and then passes to decision block 194 where a confirmation is required . if there is no confirmation of the discharge of the patient then the information passes back to exit block 188 . if confirmation of the discharge is made in block 194 the information passes once again to diagnostic check 196 and then through decision block 197 , oral agent 195 and then to patient discharge block 198 . referring now to fig7 a and 7b there is provided a subcutaneous treatment page 90 which refers back to the subcutaneous treatment page on fig4 . in the subcutaneous treatment page 90 the user may once again transfer data in block 146 to a selected transfer unit in block 152 for transfer into some external data system 160 . similarly , the patient &# 39 ; s history may be viewed in block 148 and a graph representation provided in block 150 . the user &# 39 ; s update information may be updated in block 154 with dosing information provided in block 210 and further patient information given in block 156 for passage to the subcutaneous treatment page 90 as shown in fig7 a . the usual data options may be chosen by the user in the print data input block 162 and decision block 164 for either printing in block 166 on some external peripheral device or if there is no print the information simply passes back to the subcutaneous treatment page 90 . if a decision is made to discharge the patient in block 222 a confirmation of the discharge is made in block 224 and decision block 226 where if there is no confirmation of discharge of the patient , the information passes to the subcutaneous treatment page 90 and alternatively passes to the diagnostic check block 228 in the event of confirmation of the discharge . the patient information as to discharge is then passed to patient discharge block 234 through information line 570 and then back to the initial block “ start ” 10 . if in the subcutaneous treatment page 90 it is decided to exit the subcutaneous phase , the information passes to information block 188 through information line 560 and then to decision block 232 to confirm the exiting . if exit is confirmed the information passes to start block 10 and if is not confirmed then information passes back to subcutaneous treatment page 90 through information line 590 for display of information to the user . in the event that dosing rate is to be determined with respect to pre - prandial or post - prandial dosing rates , information passes from the initial block 90 to conformation block 230 through information line 550 and decision block 240 . in information block 230 the user enters whether the blood sugar is pre - prandial or post - prandial blood glucose levels . if the blood glucose level which has been entered is pre - prandial then the logic flows to block 242 where a selection of the meal type is made by the attending physician . the flow of data is determined in block 244 depending upon the type of meal as to whether it is a “ snack ” or “ breakfast ”, “ lunch ”, or “ dinner ” is made . if this is a snack type meal , the information moves to block 246 where the number of carbohydrates in the meal are entered and confirmed in information block 250 . once the number of carbohydrates has been entered in block 250 , the information is directed to block 257 where the blood glucose level is entered . the confirmation of the blood glucose is made in block 256 and then the information moves to decision block 252 to determine whether the blood glucose is within the target range . if the blood glucose is within the target range then the information moves to block 254 where the instructions are confirmed and all information is then passed back to subcutaneous treatment page 90 through line 600 . if the blood glucose is not within the target range but the blood glucose is less than 60 then the information moves to hypoglycemic block 258 . once the hypoglycemic treatment is confirmed in block 254 the information then passes back to subcutaneous treatment page 90 through information line 600 . if the blood glucose is greater than 250 as found in decision block 252 , information is directed to the “ confirm treatment to iv ” block 236 and then passes to decision block 238 where it is decided to either continue the subcutaneous treatment or to transition back to iv . if it transitions back to iv the information simply passes back to start block 10 . if the decision is made to continue the subcutaneous treatment , the information then passes to confirm instruction block 254 and then back to the subcutaneous treatment page 90 . returning back to decision block 252 , if the blood glucose is not in the target range but is less than 250 , the information is passed to correction bolus block 253 where a correction bolus is provided by the attending physician in an empirical manner . once this is completed , the information then passes to subcutaneous treatment page 90 through information line 580 . going back to decision block 244 where the type of meal is decided by attending physician or caregiver , if the meal is to be a breakfast , lunch or dinner , the information block 248 selects the percentage of the meal which is non - meat . the blood glucose level of the patient is entered in block 251 as previously discussed and the conformation of the blood glucose is made in block 256 . once again the information passes to decision block 252 where it is determined what range the blood glucose is with respect to the target range . if the blood glucose is less than 250 but external to the target to the target range the information then passes to correction bolus information block 253 and then back to the subcutaneous treatment page 90 on information line 580 . if in block 252 the blood glucose is greater than 250 information passes once again to the “ conformation treatment to iv block ” 236 and then to the decision block 238 where it is either decided to continue the subcutaneous treatment or whether there is a transition to intravenous to be made as previously described . if the blood glucose level is less than 60 the information then passes to hypoglycemic treatment block 258 with a confirmation of the instruction being made in block 254 and then passage to the subcutaneous treatment page 90 as previously discussed . it would be appreciated by those skilled in the art that changes could be made to the embodiment described above without departing from the broad inventive concept thereof . it is understood , therefore , that this invention is not limited to the particular embodiments disclosed , but to cover modifications within the spirit and scope of the present invention as defined by the appended claims .
the method and system for managing a patient &# 39 ; s blood glucose level predicts an insulin dosing rate to bring a patient &# 39 ; s blood glucose level into a preferred target range within a predetermined time interval . the system includes a processor which actuates a blood glucose computer program to measure and predict the patient &# 39 ; s blood glucose level . an input mechanism allows for insertion of a preferred target range of the patient &# 39 ; s blood glucose level and further permits input of various patient data parameters . the processor calculates the optimum insulin dosing rate for the patient based upon the type of insulin dosing whether it be intravenous dosing and / or subcutaneous dosing . a display mechanism displays the patient dosing parameters and an alarm mechanism alerts a user when the patient &# 39 ; s blood glucose level is outside of the preferred patient blood glucose target range .