Method and System for Choosing Prosthetics Through Cross-Reference of Databases

Abstract

A method and system of choosing a prosthetic liner using cross-references databases which informs a user using a specified interface. Specifically, the method comprises a user accessing a graphical interface wherein amputee attributes are entered in order of (1) level of amputation, (2) residual limb length, (3) activity level, (4) residual limb shape/volume, and (5) clinical conditions with corresponding attribute options. Alternatively, the chosen attributes are (1) class of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for knee joints with corresponding attribute options. Alternatively, the chosen attributes are (1) level of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for foot joints with corresponding attribute options. These amputee attributes are then cross-referenced against one another and compared to a second database containing liners that correspond to the amputee attributes selected thereby educating the user, generally a prosthetist, on the appropriate liner style for a particular amputee.

Claims

1. A method of choosing a prosthetic article comprising: (A) accessing a graphical interface on a user computer, the graphical interface further comprising a tracking bar and a visual depiction; (B) showing at least one amputee attribute having a plurality of attribute options on the graphical interface wherein the visual depiction depicts the amputee attribute shown on the graphical interface; (C) recording a user's choice of attribute option using a decision box; (D) storing each of the plurality of amputee options in a first database via secure connection over a network to a server computer; (E) repeating steps (B)-(D) for at least a total of three amputee options creating an attribute grouping; (F) comparing the attribute grouping to an encrypted second database separated from the first database structurally and comprising columns mapped to corresponding amputee attributes and rows mapped to corresponding attribute options wherein, once a match is made between the attribute grouping and the corresponding amputee attributes and attribute options stored in the second database, a reference is made to a recommendation column comprising a plurality of decision choices in a plurality of rows; (G) sending a decision choice over the network to the user computer; and (H) displaying the decision choice on the user computer.

2. The method of choosing a prosthetic article of claim 1 wherein the amputee attribute is chosen from the group consisting of (1) level of amputation, (2) residual limb length, (3) activity level, (4) residual limb shape/volume, and (5) clinical conditions.

3. The method of choosing a prosthetic article of claim 1 wherein the amputee attribute is chosen from the group consisting of (1) class of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for knee joints.

4. The method of choosing a prosthetic article of claim 1 wherein the amputee attribute is chosen from the group consisting of (1) level of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for foot joints.

5. The method of choosing a prosthetic article of claim 1 wherein the method repeats steps (B)-(D) for at least five amputee options to create the attribute grouping.

6. The method of choosing a prosthetic article of claim 1 wherein a second decision choice is sent to over the network to the user computer if more than one decision choice matches the attribute grouping.

7. A system for choosing a prosthetic article comprising: a user; a user interface to input user choices and receive a decision choice connected to a local server; a first database stored on a server computer to store a plurality of attribute options based on a plurality of amputee attributes creating an attribute grouping; an encrypted second database stored on the server computer but segregated from the first database comprising a plurality of columns mapped to amputee attributes and rows mapped to attribute options and a recommendation column comprising a plurality of decision choices; a network allowing the user to send the attribute grouping to the encrypted second database and to send the decision choice back to the user and then displayed on the user interface on the local server.

8. The system of claim 7 wherein the amputee attribute is chosen from the group consisting of (1) level of amputation, (2) residual limb length, (3) activity level, (4) residual limb shape/volume, and (5) clinical conditions.

9. The system of claim 7 wherein the amputee attribute is chosen from the group consisting of (1) class of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for knee joints.

10. The system of claim 7 wherein the amputee attribute is chosen from the group consisting of (1) level of amputation, (2) residual limb length, (3) body weight, (4) use of the prosthesis, (5) activity level, and 6) uneven paths for foot joints.

11. The system of claim 7 wherein a plurality of decision choices are sent over the network to the user on the local server if more than one decision choice matches the attribute grouping.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0041] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following descriptions, taken in conjunction with the accompanying drawings, in which:

[0042] FIGS. 1-5 depict the user interface of a first embodiment of the present invention;

[0043] FIG. 6 provides a view of the system of a first embodiment of the present invention;

[0044] FIGS. 7-12 depict the user interface of a second embodiment of the present invention;

[0045] FIG. 13 provides a view of the system of a second embodiment of the present invention; and

[0046] FIGS. 14-20 depict the user interface of a third embodiment of the present invention.

[0047] Similar reference numerals refer to similar parts throughout the several views of the drawings.

DETAILED DESCRIPTION OF THE DRAWINGS

[0048] The present invention relates to a method and system for choosing a prosthetic liner through cross-referencing databases. The present invention begins by determining the level of amputation an amputee has; transfemoral or transtibial. As shown in FIG. 1, the first amputee attribute 100 having a plurality of attribute options 148, in this case level of amputation which can be transfemoral or transtibial, is recorded using a first decision box 102 which stores the recorded first amputee attribute 100 in a first database. Each step of the process can be followed along by use of a tracking bar 104 and further comprises a visual depiction 106 of the amputee attribute being chosen. After the first amputee attribute 100 is made using the first decision box 102, the user moves onto a determination of residual limb length. As shown in FIG. 2, a residual limb can be short, medium, or long. This second amputee attribute 108 is recorded using a second decision box 110 which is then also stored in the first database. As shown in FIG. 3, the next amputee attribute determination is activity level of the amputee which can be high, medium, or low. This third amputee attribute 112 is recorded using a third decision box 114 which is also then stored in the first database 132. As shown in FIG. 4, the next amputee attribute determination is the shape and volume of the residual limb which can either be regular, bony, or redundant/fleshy. This fourth amputee attribute 116 is recorded using a fourth decision box 118 which is also then stored in the first database. Finally, as shown in FIG. 5, the fifth amputee attribute 120 determination is other clinical conditions. The user has a choice between (1) normal conditions, (2) diabetic or sensitive skin, (3) abundant perspiration, or (4) daily volume fluctuations. The user makes a choice and then the fifth amputee attribute 120 is recorded using a fifth decision box 122 which is also then stored in the first database. During each step of the process, the user has the option of choosing a “back” choice 124 to go back a step or choosing a “next” choice 126 to move onto the next step with the exception of the first amputee attribute choice step (no “back” choice 124) and the fifth amputee attribute choice step which instead has a submission option 128.

[0049] It is important to note that the number of amputee attributes may vary in the system and more or less than five attributes can be implemented using this system. Similarly, the attributes described herein may have modified options depending on the amputee using the system which can be easily added by modifying the options presented in the user interface 136. For example, the clinical condition associated with the fifth amputee attribute may include other conditions that amputees or prosthetists may suggest.

[0050] Once the amputee attributes are chosen and recorded in the first database 132, a check is made to a second database 134 housing every combination of amputee attribute associated with choosing a prosthetic liner, as described above. The second database 134 is preferably encrypted to maintain any trade secret determinations for liner choice and is preferably kept separate from the first database. After the last amputee attribute is stored in the first database 132, the system then maps each amputee attribute to associated columns 152, with the first amputee attribute 100 mapping to a first column 154, the second amputee attribute 108 mapping to a second column 156, the third amputee attribute mapping to a third column 158, the fourth amputee attribute mapping to a fourth column 160, and the fifth amputee attribute mapping to a fifth column 162. Each of the attribute options 148 are then matched in associated rows. Once the system finds a match for each attribute option 148, a check is then made to at least one additional column 164 containing the information associated with a specific type of liner and the liner information is returned to the user. Preferably, in situations where more than one liner may be used for specific amputee attributes, more than one column of data may be returned.

[0051] As can be seen in FIG. 6, the system of the present invention comprises a user 130, the first database 132, the second database 134, and a user interface 136. Once the amputee attributes 138 are input into the user interface 136, the information is sent over a network 140 to a server computer 142 which stores the first database 132. After all of the amputee attributes 138 are stored in the first database 132, the attribute grouping 144 is then sent to the second database 134 for mapping as described in the paragraph above. When the desired liner type is determined, the second database 134 sends out a decision choice 146 over the network 140 back to the user's local server 148 which provides a display of the decision choice 146 to the user 130.

[0052] A second embodiment of the present invention is shown in FIGS. 7-12. The present invention begins by determining the level of amputation an amputee has; transfemoral or bilateral transtibial/transfemoral or bilateral transfemoral/transfemoral. As shown in FIG. 7, the first amputee attribute 200 comprising a plurality of attribute options 272, in this case class of amputation which can be transfemoral or bilateral transtibial/transfemoral or bilateral transfemoral/transfemoral, is recorded using a first decision box 202 which stores the recorded first amputee attribute 200 in a first database. Each step of the process can be followed along by use of a tracking bar 204 and further comprises a visual depiction 206 of the amputee attribute being chosen. After the first amputee attribute 200 is made using the first decision box 202, the user moves onto a determination of residual limb length. As shown in FIG. 8, a residual limb can be short, medium, long or knee disarticulation. This second amputee attribute 208 is recorded using a second decision box 210 which is then also stored in the first database. As shown in FIG. 9, the next amputee attribute determination is the body weight of the amputee. The user has a choice between (1)<50 Kg/110 lb, (2)<100 kg/220 lb, (3)<125 Kg/275 lb, (4) above 125 kg/275 lb. This third amputee attribute 212 is recorded using a third decision box 214 which is also then stored in the first database. As shown in FIG. 10, the next amputee attribute determination is the use of the prosthesis which can either be (1) initial prosthesis (2) everyday life or (3) sport only. This fourth amputee attribute 216 is recorded using a fourth decision box 218 which is also then stored in the first database. As shown in FIG. 11, the fifth amputee attribute 220 determination is the level of activity of the amputee. The user has a choice between indoor walker (K1), limited outdoor walker (K2), ordinary walker (K3), dynamic walker (K3+) or very active user (K4). The user makes a choice and then the fifth amputee attribute 220 is recorded using a fifth decision box 222 which is also then stored in the first database. Finally, as shown in FIG. 12, the sixth amputee attribute is related to his lifestyle, specifically if he has to deal with uneven paths. The user has a choice between (1) YES and (2) NO. This sixth amputee attribute 224 is recorded using a fourth decision box 226 which is also then stored in the first database During each step of the process, the user has the option of choosing a “back” choice 228 to go back a step or choosing a “next” choice 230 to move onto the next step with the exception of the first amputee attribute choice step (no “back” choice 228) and the sixth amputee attribute choice step which instead has a submission option 232.

[0053] Once the amputee attributes are chosen and recorded in the first database 236, a check is made to a second database 238 housing every combination of amputee attribute associated with choosing a prosthetic knee joints, as described above. The second database 238 is preferably encrypted to maintain any trade secret determinations for knee choice and is preferably kept separate from the first database. After the last amputee attribute is stored in the first database 236, the system then maps each amputee attribute to associated columns 256, with the first amputee attribute 200 mapping to a first column 258, the second amputee attribute 208 mapping to a second column 260, the third amputee attribute mapping to a third column 262, the fourth amputee attribute mapping to a fourth column 264, the fifth amputee attribute mapping to a fifth column 266 and the sixth amputee attribute mapping to a sixth column 268. Each of the attribute options 272 are then matched in associated rows. Once the system finds a match for each attribute option 272, a check is then made to at least one additional column 270 containing the information associated with a specific type of knee joints and the prosthetic knee joint information is returned to the user. Preferably, in situations where more than one knee joint may be used for specific amputee attributes, more than one column of data may be returned.

[0054] As can be seen in FIG. 13, the system of the present invention comprises a user 130, the first database 236, the second database 238, and a user interface 240. Once the amputee attributes 242 are input into the user interface 240, the information is sent over a network 244 to a server computer 246 which stores the first database 236. After all of the amputee attributes 242 are stored in the first database 236, the attribute grouping 248 is then sent to the second database 238 for mapping as described in the paragraph above. When the desired knee joint type is determined, the second database 238 sends out a decision choice 250 over the network 244 back to the user's local server 252 which provides a display of the decision choice 250 to the user 130.

[0055] A third embodiment of the present invention is shown in FIGS. 14-20. The present invention begins by determining the level of amputation an amputee has: transfemoral or transtibial or ankle/foot amputation. As shown in FIG. 14, the first amputee attribute 300 comprising a plurality of attribute options 372, in this case class of amputation which can be transfemoral or transtibial or ankle/foot amputation, is recorded using a first decision box 302 which stores the recorded first amputee attribute 300 in a first database. Each step of the process can be followed along by use of a tracking bar 304 and further comprises a visual depiction 306 of the amputee attribute being chosen. After the first amputee attribute 300 is made using the first decision box 302, the user moves onto a determination of residual limb length. As shown in FIG. 15, a residual limb can be short, medium or long. This second amputee attribute 308 is recorded using a second decision box 310 which is then also stored in the first database. As shown in FIG. 16, the next amputee attribute determination is the body weight of the amputee. The user has a choice between (1)<75 Kg/165 lb, (2)<100 kg/220 lb, (3)<125 Kg/275 lb, (4) above 125 kg/275 lb. This third amputee attribute 312 is recorded using a third decision box 314 which is also then stored in the first database. As shown in FIG. 17, the next amputee attribute determination is the use of the prosthesis which can either be (1) initial prosthesis (2) everyday life or (3) sport only. This fourth amputee attribute 316 is recorded using a fourth decision box 318 which is also then stored in the first database. As shown in FIG. 18, the fifth amputee attribute 320 determination is the level of activity of the amputee. The user has a choice between indoor walker (K1), limited outdoor walker (K2), ordinary walker (K3), dynamic walker (K3+) or very active user (K4). The user makes a choice and then the fifth amputee attribute 320 is recorded using a fifth decision box 322 which is also then stored in the first database. Finally, as shown in FIG. 19, the sixth amputee attribute is related to his lifestyle, specifically if he has to deal with uneven paths. The user has a choice between (1) YES and (2) NO. This sixth amputee attribute 324 is recorded using a sixth decision box 326 which is also then stored in the first database During each step of the process, the user has the option of choosing a “back” choice 328 to go back a step or choosing a “next” choice 330 to move onto the next step with the exception of the first amputee attribute choice step (no “back” choice 328) and the sixth amputee attribute choice step which instead has a submission option 332.

[0056] Once the amputee attributes are chosen and recorded in the first database 336, a check is made to a second database 338 housing every combination of amputee attribute associated with choosing a prosthetic foot, as described above. The second database 338 is preferably encrypted to maintain any trade secret determinations for foot choice and is preferably kept separate from the first database. After the sixth amputee attribute 324 is stored in the first database 336, the system then maps each amputee attribute to associated columns 356, with the first amputee attribute 300 mapping to a first column 358, the second amputee attribute 308 mapping to a second column 360, the third amputee attribute mapping to a third column 362, the fourth amputee attribute mapping to a fourth column 364, the fifth amputee attribute mapping to a fifth column 366 and the sixth amputee attribute mapping to a sixth column 368. Each of the attribute options 372 are then matched in associated rows. Once the system finds a match for each attribute option 372, a check is then made to at least one additional column 370 containing the information associated with a specific type of foot and the prosthetic foot information is returned to the user. Preferably, in situations where more than one foot may be used for specific amputee attributes, more than one column of data may be returned.

[0057] As can be seen in FIG. 20, the system of the present invention comprises a user 334, the first database 336, the second database 338, and a user interface 340. Once the amputee attributes 342 are input into the user interface 340, the information is sent over a network 344 to a server computer 346 which stores the first database 336. After all of the amputee attributes 342 are stored in the first database 336, the attribute grouping 348 is then sent to the second database 338 for mapping as described in the paragraph above. When the desired foot type is determined, the second database 338 sends out a decision choice 350 over the network 344 back to the user's local server 352 which provides a display of the decision choice 350 to the user 334.

[0058] The present disclosure includes that contained in the appended claims, as well as that of the foregoing description. Although this invention has been described in its preferred form with a certain degree of particularity, it is understood that the present disclosure of the preferred form has been made only by way of example and that numerous changes in the details of construction and the combination and arrangement of parts may be resorted to without departing from the spirit and scope of the invention.