Method and apparatus for managing blood collection information by using blood collection history code

Abstract

A method for managing blood collection information by using a blood collection history code, according to embodiments of the present invention, comprises the steps of: obtaining, from a first apparatus, information about a blood collection history code of a subject from which blood is to be collected; storing the blood collection history code of the subject from which blood is being collected; receiving, from a second apparatus, a request for provision of the blood collection history code of the subject from which blood is being collected; and transmitting, to the second apparatus, the blood collection history code of the subject from which blood is being collected, wherein the blood collection history code may include at least one of blood collection location information and blood collection difficulty level information.

Description

Method and device for managing blood collection information using blood collection history codes

[0001] The present invention relates to the management of blood collection information, and more specifically, to managing blood collection information using a blood collection history code.

[0002] Blood sampling is the medical practice of withdrawing blood from the body for purposes such as blood donation or blood testing. It's typically performed during a comprehensive physical examination at a hospital or public health center. For testing purposes, blood sampling can be performed for purposes such as blood type determination, confirmation of various physiological indicators, and disease diagnosis.

[0003] To collect blood, a needle is inserted into a blood vessel. The most suitable blood vessel for blood collection varies depending on various characteristics, such as its location, diameter, depth, and shape, and this can vary from person to person. Consequently, finding the most suitable blood vessel for each individual is a cumbersome process. Furthermore, identifying the most suitable blood vessel for each blood draw is time-consuming and inefficient.

[0004] Moreover, blood collection from a site not optimal for blood collection often leads to collection failure. This failure increases the patient's anxiety and can even lead to serious side effects.

[0005] Therefore, a method is needed to increase the success rate of blood collection by making it easy to identify the optimal blood vessel for the blood sample.

[0006] For example, Japanese Patent Application Laid-Open No. 2003-143435 discloses a 'blood collection device' that can reduce the burden on the person receiving the blood sample.

[0007] One object of the present invention is to provide a method and device for increasing the success rate of blood collection.

[0008] Another object of the present invention is to provide a method and device for providing information that can be helpful when collecting blood.

[0009] Another object of the present invention is to provide a method and device for effectively generating and managing information on blood collection history that can be helpful in blood collection.

[0010] A method for managing blood collection information using a blood collection history code, performed by at least one processor according to exemplary embodiments of the present invention, may include the steps of obtaining information on a blood collection history code of a blood sampler from a first device, storing the blood collection history code of the blood sampler, receiving a request for providing the blood collection history code of the blood sampler from a second device, and transmitting the blood collection history code of the blood sampler to the second device. The blood collection history code may include at least one of blood collection location information and blood collection difficulty information.

[0011] In one embodiment, the blood collection history code may further include information about the needle used during blood collection.

[0012] In one embodiment, the blood collection history code may be determined by concatenating at least one numeric value or character value that encodes each of the blood collection location information, the blood collection difficulty information, and the needle information used during the blood collection.

[0013] In one embodiment, a numeric value or character value corresponding to the needle information used during blood collection may be omitted if it is determined to be a predefined value.

[0014] In one embodiment, the information about the blood collection history code of the subject may include the blood collection history code generated by the first device.

[0015] In one embodiment, the information about the blood collection history code of the subject includes at least one of the blood collection location information, the blood collection difficulty information, and the needle information used during the blood collection; and the step of storing the blood collection history code of the subject may include the step of determining the blood collection history code of the subject based on the information about the blood collection history code of the subject and then storing it.

[0016] In one embodiment, the blood collection information management method may further include a step of transmitting, to the first device, questionnaire data inquiring about at least one of the blood collection location information, the blood collection difficulty information, and the needle information used during the blood collection.

[0017] In one embodiment, the blood collection information management method may further include the step of receiving information about the subject of the blood collection from the first device; and, if the blood collection history code of the subject of the blood collection is not stored, the step of transmitting a message requesting the generation of a blood collection history code for the subject of the blood collection to the first device.

[0018] In one embodiment, the blood collection history code transmitted to the second device may be displayed on a display device provided in the second device or printed on a barcode output by an output device connected to the second device.

[0019] In one embodiment, the blood collection information management method may further include the steps of receiving a modified blood collection history code from the second device; and storing the modified blood collection history code as a blood collection history code of the subject.

[0020] In one embodiment, the step of transmitting the blood collection history code of the subject to the second device may include, when a plurality of blood collection history codes of the subject are stored, a step of selecting an optimal blood collection history code from among a plurality of blood collection history codes; and a step of transmitting the optimal blood collection history code.

[0021] In one embodiment, the optimal blood collection history code may include: a most recently stored blood collection history code among the plurality of blood collection history codes; a blood collection history code corresponding to the largest number of blood collection history codes among the plurality of blood collection history codes; or a blood collection history code of a blood collection location corresponding to the largest number of blood collection history codes having the lowest difficulty among the plurality of blood collection history codes.

[0022] In one embodiment, the optimal blood collection history code may include the blood collection history code with the lowest difficulty level if the ratio of the blood collection history codes with the lowest difficulty level among the plurality of blood collection history codes is greater than or equal to a threshold value. The optimal blood collection history code may include the most recently stored blood collection history code if the ratio of the blood collection history codes with the lowest difficulty level among the plurality of blood collection history codes is less than the threshold value.

[0023] A device for managing blood collection information using a blood collection history code according to exemplary embodiments of the present invention may include a communication unit; a memory; and at least one processor connected to the communication unit and the memory. The at least one processor may control to obtain information on a blood collection history code of a subject from a first device, store the blood collection history code of the subject, receive a request for providing the blood collection history code of the subject from a second device, and transmit the blood collection history code of the subject to the second device. The blood collection history code may include at least one of blood collection location information and blood collection difficulty information.

[0024] An application program stored in a recording medium according to exemplary embodiments of the present invention can execute the above-described method when operated by a processor.

[0025] According to exemplary embodiments of the present invention, information related to blood collection performed in the past is recorded and provided during subsequent blood collection, thereby enabling blood collection to be performed more effectively.

[0026] Figure 1 illustrates the structure of a blood collection information management system according to one embodiment of the present invention.

[0027] Figure 2 illustrates the structure of a device according to one embodiment of the present invention.

[0028] Figure 3 illustrates the structure of a blood collection history code according to one embodiment of the present invention.

[0029] Figures 4a, 4b and 4c illustrate the results of encoding blood collection location information included in a blood collection history code according to one embodiment of the present invention.

[0030] Figure 5 illustrates a flowchart for managing blood collection history codes according to one embodiment of the present invention.

[0031] FIG. 6 illustrates an attachment barcode output utilizing a blood collection history code according to one embodiment of the present invention.

[0032] Figure 7 illustrates a flowchart for modifying a blood collection history code according to one embodiment of the present invention.

[0033] FIG. 8 illustrates a program interface for modifying a blood collection history code according to one embodiment of the present invention.

[0034] FIG. 9 illustrates a flowchart for storing and displaying information on blood collection according to one embodiment of the present invention.

[0035] Figure 10 illustrates the structure of an application for managing blood collection history codes according to one embodiment of the present invention.

[0036] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below, along with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms.

[0037] To clearly explain embodiments of the present invention, portions irrelevant to the description may be omitted. Furthermore, when describing embodiments of the present invention, if a detailed description of a related known configuration or function is deemed to obscure the gist or description of the present invention, a detailed description thereof may be omitted.

[0038] When describing components of exemplary embodiments of the present invention, terms such as "first," "second," etc. may be used. These terms are intended to distinguish one component from another for convenience of explanation, and unless otherwise specified, the nature, order, etc. of the components are not limited by these terms. Furthermore, it is not intended to be assumed that the components to which these terms are attached are different from each other.

[0039] Additionally, when it is described herein that a first component is “connected” or “coupled” to a second component, it may mean that the first component is directly connected or coupled to the second component, or it may mean that the first component is connected or coupled to the second component via a third component.

[0040] In this specification, "and / or" may mean each of the listed components and any combination of two or more of the listed components. For example, "A and / or B" may mean the same as "at least one of A and B."

[0041] Figure 1 illustrates the structure of a blood collection information management system according to one embodiment of the present invention.

[0042] Referring to FIG. 1, the blood collection information management system may include a first device (101a), a second device (101b), and a server (102).

[0043] The first device (101a) can generate a blood collection history code based on information about blood collection. The second device (101b) can utilize the blood collection history code generated by the first device (101a). The first device (101a) can generate a blood collection history code based on the acquired blood collection information and provide the blood collection history code to the server (102). The server (102) can store the blood collection history code and provide the blood collection history code upon request from the second device (101b). The first device (101a) and the second device (101b) can access the server (102) via a network and interact with the server (102).

[0044] In one embodiment, the first device (101a) is a device used by a clinical pathologist performing blood collection, and the clinical pathologist can input information about the blood collection into the first device (101a). For example, the information about the blood collection may include at least one of the following: difficulty of the blood collection, the location of the blood collection, and the type of needle used. For example, the first device (101a) or the server (102) may generate a blood collection history code from the blood collection information input by a predefined algorithm.

[0045] In one embodiment, the second device (101b) is a device used by a clinical pathologist performing blood collection, and can obtain information on the subject's past blood collections from the server (102) and output the information to be provided to the clinical pathologist. Here, the information on the past blood collections can be obtained in the form of a blood collection history code. In another embodiment, the second device (101b) can be a device used by the subject, and in this case, the second device (101b) can execute an application that manages information on the subject's blood collections.

[0046] FIG. 2 illustrates the structure of a device according to one embodiment of the present invention. FIG. 2 illustrates an example of the structure of the first device (101a), the second device (102a), or the server (102) of FIG. 1. That is, the structure illustrated in FIG. 2 can be viewed as the structure of the first device (101a) or the second device (102a), or the structure of at least a portion of the server (102).

[0047] Referring to FIG. 2, the device may include a control unit (201), a communication unit (202), and a storage unit (203).

[0048] The control unit (201) can control the overall functions and operations of the device. The control unit (201) can control components of the device, for example, the communication unit (202), the storage unit (203), and at least one other component. That is, the control unit (201) can provide information or data necessary for the operation of the components of the device, and perform operations based on information or data generated or managed by the components. For example, the control unit (201) can include at least one processor, at least one circuit, etc. For example, the processor can include at least one of a central processing unit (CPU), a graphics processing unit (GPU), and a neural processing unit (NPU). The control unit (201) can perform necessary controls so that the device operates according to various embodiments described herein.

[0049] The communication unit (202) can perform a function for transmitting and receiving signals with other devices. The communication unit (202) performs wired communication or wireless communication, and can process signals according to the control of the control unit (201). For example, the communication unit (202) may include an RF (radio frequency) circuit, an antenna, etc. for wireless communication, or a connection terminal, a modem, a driver module, etc. for wired communication. For example, the communication unit (202) may be configured to perform LTE (Long Term Evolution), 5G (5 the It can support at least one of various communication protocols, such as cellular communication such as cellular generation, short-range wireless communication such as WiFi (wireless Fidelity) and Bluetooth, and short-range wired communication such as Ethernet.

[0050] The storage unit (203) can store data used in the device, software for the operation of the device, programs, and commands. In addition, the storage unit (203) provides stored data under the control of the control unit (201). In addition, the storage unit (203) can store applications, drivers, etc. to be driven by the control unit (201). The storage unit (203) can include random access memory (RAM) such as dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), hard disk drive (HDD), solid state drive (SSD), or flash storage means.

[0051] Additionally, although not shown in FIG. 2, the device may further include at least one of a power supply device, a display device, an input device, and an output device, depending on the type of the device.

[0052] Figure 3 illustrates the structure of a blood collection history code according to one embodiment of the present invention.

[0053] As illustrated in FIG. 3, a blood collection history code according to an embodiment of the present invention may be defined as a combination of multiple information items regarding blood collection. For example, the multiple information items may include blood collection difficulty information (301; hereinafter, may be abbreviated as difficulty information), blood collection location information (302), needle information used during blood collection (303; hereinafter, may be abbreviated as used needle information), etc. Blood collection location information (302) may include information regarding the location of a blood collection vessel. For example, blood collection location information (302) may include left / right information, detailed location information, etc. Difficulty information (301) may include information regarding the difficulty of blood collection during the corresponding blood collection. That is, difficulty information (301) may include information regarding the difficulty of blood collection when blood collection was performed at the corresponding blood collection location. Used needle information (303) may include information regarding the needle used during the corresponding blood collection. For example, the needle information used (303) may include information on the type of needle used, information on the thickness of the needle used, etc.

[0054] The blood collection history code can be composed as a string encoding each of the information items listed above. For example, the blood collection history code can be generated by converting each information item into numbers or characters and concatenating the converted numbers or characters in a predefined order. Depending on the value of the number or character, the number or character corresponding to the corresponding information item may be omitted.

[0055] For a specific example, difficulty information (301) can be coded into a numeric value according to the rules shown in [Table 1] below.

[0056] Numerical Value Content Judgment Criteria 1 Easy Blood vessels that can be immediately confirmed with the naked eye. 2 Moderate Blood vessels that cannot be confirmed with the naked eye but can be confirmed by palpation. * Basilic veins are given a level higher than this because they are painful due to their high innervation. 3 Difficult Blood vessels that are deep or thin when palpated and therefore difficult to collect blood. * Pain is also often complained of when collecting blood from the back of the hand or wrist. 4 Very difficult Blood vessels that are deep or thin when palpated and therefore difficult to collect blood. Many failed blood vessels. Experienced side effects from blood collection.

[0057] For a specific example, the left / right information among the blood collection location information (302) can be coded as a character value indicating left / right according to the rules as shown in [Table 2] below.

[0058] Character value content L left arm R right arm

[0059] For a specific example, detailed location information among blood collection location information (302) can be coded into a character value indicating a detailed location according to a rule as shown in [Table 3] below.

[0060] Character value content M center of arm C outer arm BB inner arm W wrist H back of hand

[0061] For example, examples of the results of encoding left / right information and detailed location information are as shown in FIGS. 4A, 4B, and 4C. FIG. 4 illustrates the results of encoding blood collection location information included in a blood collection history code according to one embodiment of the present invention. Referring to FIGS. 4A, 4B, and 4C, a blood collection location can be expressed based on a combination of left / right information (e.g., L or R) and detailed location information (e.g., M, C, B, W, or H).

[0062] For example, the used needle information (303) may be coded as a numeric value representing the thickness of the needle. For example, the numeric values ​​as the used needle information (303) may include 21, 22, 23, etc. Here, any specific value among the available numeric values ​​(for example, the most commonly used value, e.g., 21) may be omitted. In this case, if the blood collection history code does not include a numeric value corresponding to the used needle information (303), the used needle information (303) represented by the blood collection history code may be interpreted as a specific value. For another example, the used needle information (303) may be coded as a character value representing the type of needle. In addition, the used needle information (303) may be coded by combining a numeric value representing the thickness of the needle and a character value representing the type of needle.

[0063] The coded values ​​described with reference to FIGS. 3, 4A, 4B, and 4C are merely examples. Therefore, the numerical or character values ​​presented as examples can be implemented by changing them to other values, and the present invention is not limited to the examples described above. However, it is preferable to use numerical or character values ​​with a minimum length based on the number of values ​​to be expressed.

[0064] Figure 5 illustrates a flowchart for managing blood collection history codes according to one embodiment of the present invention. Figure 5 illustrates an example of a procedure for generating and storing blood collection history codes and providing stored blood collection history codes.

[0065] Referring to FIG. 5, in step 501, the first device (101a) can obtain information about blood collection. The information about blood collection can be entered by a first clinical pathologist using the first device (101a). For example, in the case where there is no blood collection history code, the first clinical pathologist can identify the subject of the blood collection, determine the optimal blood collection site (i.e., the optimal blood collection vessel), finally determine the blood collection site, explain the blood collection site and the needle to be used, and then perform the blood collection. Thereafter, the first clinical pathologist can input information about the subject of the blood collection, the needle used, and the difficulty level of the blood collection into the first device (101a).

[0066] In step 502, the first device (101a) may generate a blood collection history code. The blood collection history code may be generated according to a predefined algorithm. For example, the first device (101a) may encode each of the information items included in the blood collection information and generate a blood collection history code (e.g., 2RB22) by listing the coded values. At this time, if the coded value of a specific information item is a designated specific value, the coded value of the information item may be omitted. According to a specific embodiment, the coding rules described above with reference to FIGS. 3, 4A, 4B, and 4C may be applied. The blood collection history code may be generated by a program designed to generate a blood collection history code, and the first clinical pathologist may initiate the generation of the blood collection history code simply by entering the required information.

[0067] However, in one embodiment, in step 501, the first clinical pathologist may directly generate a blood collection history code based on information about the blood collection site, the needle used, and the difficulty of the blood collection and input it into the first device (101a).

[0068] In step 503, the first device (101a) may transmit a blood collection history code to the server (102). Once the blood collection history code is generated, it may be transmitted to the server (102) that manages the blood collection history code. For this purpose, an explicit transmission order from the first clinical pathologist may be required, or a procedure may be defined so that the code is transmitted upon generation without a transmission order. At this time, in addition to the blood collection history code (e.g., 2RB22), information about the subject of the blood collection is transmitted, and further, related additional information may be transmitted. For example, the additional information may include information about the first clinical pathologist (e.g., qualification information, career information, affiliation information, etc.). The server (102) may manage the received blood collection history code so that it can be searched by storing it in a database.

[0069] In step 504, the second device (101b) may request a blood collection history code. The blood collection history code may be requested by a second clinical pathologist to perform the blood collection. For example, if a blood collection history code is stored in the server (102), the second device (101b) may identify the subject of the blood collection and control the second device (101b) to request the blood collection history code using the subject's information. The second device (101b) may transmit a message or signal requesting the subject's blood collection history code along with the subject's information to the server (102).

[0070] In step 505, the server (102) may transmit a blood collection history code to the second device (101b). The server (102) may search for the blood collection history information of the subject within the database using the information of the subject received from the second device (101b), and then transmit the searched blood collection history information to the second device (101b). Accordingly, the second clinical pathologist may confirm the blood collection history code, confirm the previous blood collection site and needle used, explain the previous blood collection site and needle used to the subject, and then perform the blood collection.

[0071] The blood collection history code provided by the second device (101b) can allow the second clinical pathologist to confirm the blood collection site, etc. In this case, the blood collection history code can be provided to the second clinical pathologist by being visually output. For example, the blood collection history code can be displayed on a monitor.

[0072] As another example, the blood collection history code may be provided to the second clinical pathologist by being printed on an attachment barcode output used during the blood collection process, as illustrated in FIG. 6. FIG. 6 illustrates an attachment barcode output utilizing a blood collection history code according to one embodiment of the present invention.

[0073] As shown in Fig. 6, a blood collection code (601) can be printed on a barcode for attaching a blood collection tube. For this purpose, a blood collection history code input field can be implemented in the medical treatment program. Through the code printed along with the barcode, a second clinical pathologist can immediately identify the previous blood collection site. To this end, the second device (101b) can work with a printing device that prints the attached barcode output and provide the blood collection history code received from the server (102) to the printing device.

[0074] In the procedure of FIG. 5, the first device (101a) generates and transmits a blood collection history code. According to another embodiment of the present invention, the first device (101a) provides information necessary to generate a blood collection history code, and the server (102) can generate the blood collection history code. To this end, the server (102) transmits questionnaire data inquiring about necessary information (e.g., blood collection location information, blood collection difficulty information, needle information used during blood collection, etc.) to the first device (101a), and the first device (101a) transmits necessary information in response to the questionnaire data, and the server (102) can generate and store the blood collection history code.

[0075] Additionally, depending on whether the blood collection history code of the subject is stored in the server (102), a message requesting the generation of a blood collection history code may be transmitted from the server (102) to the first device (101a). For example, the first device (101a) may transmit information about the subject to the server (102) prior to generating the blood collection history code. Accordingly, the server (102) may search for the blood collection history code of the subject in the database, and if the search fails, may transmit a message requesting the generation of a blood collection history code to the first device (101a). In this case, as an example, the message requesting the generation of a blood collection history code may include the aforementioned questionnaire data.

[0076] According to one embodiment of the present invention, a blood collection history code containing information on past blood collections may be utilized. However, whether to follow the blood collection history code may be determined by the clinical pathologist performing the blood collection. In other words, there is no mandatory requirement to collect blood from the site indicated by the blood collection history code. The use of the blood collection history code means that information regarding the most suitable blood vessel for blood collection is provided in advance before the blood collection. For example, if a better blood vessel is discovered, the clinical pathologist may perform the blood collection from a site other than the site indicated by the blood collection history information. Furthermore, the clinical pathologist may request modification or addition of the blood collection history code to the server (102) using the second device (101b).

[0077] Figure 7 illustrates a flowchart for modifying a blood collection history code according to one embodiment of the present invention. Figure 7 illustrates an example of a procedure for modifying a blood collection history code.

[0078] Referring to FIG. 7, in step 701, the second device (101b) may request a blood collection history code. In step 702, the server (102) may transmit the blood collection history code to the second device (101b). Steps 701 and 702 may be identical to steps 504 and 505 of FIG. 5. Through this, the second clinical pathologist may use the previous blood collection history code to identify the optimal blood vessel and determine whether to proceed with blood collection. If the location indicated by the blood collection history code is determined to be not a suitable blood vessel for blood collection, the second clinical pathologist may search for another site, conduct blood collection at a site determined to be suitable, and modify the blood collection history code according to the performed blood collection site.

[0079] For example, examples of cases where the blood vessel indicated in the received blood collection history code is unsuitable for blood collection include cases where the blood vessel is rarely hidden due to the physical condition of the person being drawn, cases where the blood vessel is constricted due to the weather, cases where the blood vessel is constricted due to the effects of dehydration, and cases where the person who assigned the previous blood collection history code made a mistake (for example, assigning the blood vessel to the left arm instead of the right arm).

[0080] In step 703, the second device (101b) may obtain a modified blood collection history code. Here, the modified blood collection history code may refer to a blood collection history code different from the blood collection history code received in step 702. For example, the modified blood collection history code may be obtained by the second clinical pathologist modifying at least one letter or number of the blood collection history code. In another example, when the second clinical pathologist performs a blood collection and then inputs information about the performed blood collection, the second device (101b) may generate a blood collection history code corresponding to the input information, and if it is confirmed that the generated blood collection history code is not the same as the received blood collection history code, the generated blood collection history code may be treated as a modified blood collection history code.

[0081] In step 704, the second device (101b) may transmit the modified blood collection history code to the server (102). At this time, additional information may be transmitted along with the modified blood collection history code. For example, the additional information may include a reason for modifying the blood collection history code. Furthermore, information about the subject of the blood collection may be transmitted along with the modified blood collection history code. However, according to another embodiment, if the modified blood collection history code is received within a certain period of time after the server (102) transmits the blood collection history code upon request, the server (102) may determine that the modified blood collection history code is information about blood collection performed on the subject of the blood collection related to the previously transmitted blood collection history code. In this case, the information about the subject of the blood collection may be omitted. Accordingly, the server (102) may store the modified blood collection history code in a database. At this time, the revised blood collection history code may replace the existing blood collection history code, or the revised blood collection history code may be stored additionally with the existing blood collection history code. If the revised blood collection history code is stored additionally with the existing blood collection history code, the two blood collection history codes can be indexed and managed in the order of occurrence.

[0082] A blood collection history code can be modified as in the procedure of FIG. 7. An interface such as FIG. 8 can be used to modify a blood collection history code. FIG. 8 illustrates a program interface for modifying a blood collection history code according to one embodiment of the present invention. FIG. 8 illustrates an example of an interface of a program used in a second device (101b). As shown in FIG. 8, the interface includes an input window (801) related to a blood collection history, and a second clinical pathologist can input a new blood collection history code into the input window (801).

[0083] According to an embodiment of the present invention, a clinical pathologist can obtain and utilize information on past blood collections through blood collection history codes. However, the clinical pathologist may not be aware of the existence of blood collection history codes or may not have the equipment to utilize them. In this case, the person being drawn can use an application to store and present the blood collection history codes.

[0084] Figure 9 illustrates a flowchart for storing and displaying information about blood collection according to one embodiment of the present invention. Figure 9 illustrates an example of a procedure in which a device of a blood collection subject stores and provides a blood collection history code.

[0085] Referring to FIG. 9, in step 901, the device can execute a blood collection history code management application. The device can install a dedicated application for managing blood collection history codes and execute the installed application according to input from a user, i.e., a blood sampler.

[0086] In step 902, the device may obtain and store a blood collection history code. The blood collection history code may be obtained in various ways. For example, after a blood draw is performed on a subject, the subject may receive the blood collection history code from a clinical pathologist, and the subject may then enter the professional blood collection history code. Alternatively, the device may obtain the blood collection history code by connecting to the server (102) and requesting the blood collection history code from the server (102).

[0087] In step 903, the device may display a blood collection history code. While the application is running, the device may display a stored blood collection history code. For example, the device may display a screen as shown in FIG. 10. Specifically, referring to FIG. 10, the device may display a screen including a code storage button (1001), a code list output button (1002), and a blood collection history code output window (1003). Accordingly, the user, i.e., the subject, may check the blood collection history code for their past blood collection.

[0088] In step 904, the device can determine whether an image guide display command is detected. For example, the image guide display command can be input by touching the blood collection history code output window (1003).

[0089] When a command to display an image guide is detected, in step 905, the device displays an image guide corresponding to the blood collection history code. The image guide is provided through an image (1003-1) representing the blood collection location indicated by the blood collection history code. Specifically, the image (1003-1) includes information about the blood collection location, the difficulty of the blood collection, the needle used, etc. Accordingly, the user, i.e., the subject of the blood collection, can provide information about previously performed blood collections to the clinical pathologist.

[0090] Although not shown in FIG. 9, in step 903, when the code list output button (1002) is pressed, the device can display a list (1002-1) of image guides according to the blood collection history code. The list of image guides can be configured in a form similar to FIG. 4.

[0091] Through a procedure similar to that shown in Figure 9, the subject can save the blood collection history code and then present it via the application during the next blood collection. This method is possible without introducing the blood collection history code into the clinical program used by clinical pathologists. This means that it becomes possible to provide previous information to clinical pathologists who are unfamiliar with blood collection codes.

[0092] In addition to the embodiments described above, the present invention further proposes an embodiment for a case where multiple blood collection history codes exist for one blood collection subject. When multiple blood collection history codes exist for one blood collection subject (for example, when clinical pathologist A inputs blood collection input code X and clinical pathologist B inputs blood collection history code Y), the server (102) can provide an optimal one of the blood collection history codes. Here, the optimal blood collection history code can be defined based on various criteria. For example, the most recently stored blood collection history code among the multiple blood collection history codes can be defined as the optimal blood collection history code. As another example, the blood collection history code corresponding to the largest number of blood collection history codes can be defined as the optimal blood collection history code. As another example, among a plurality of blood collection history codes, the blood collection history code having the most blood collection locations among the blood collection history codes having the lowest difficulty can be defined as the optimal blood collection history code (i.e., when the blood collection history codes having the lowest difficulty among a plurality of blood collection history codes are selected, the blood collection history code having the most blood collection locations among the selected blood collection history codes can be defined as the optimal blood collection history code).

[0093] In another embodiment, the optimal blood collection history code may be adaptively selected depending on the situation. For example, if the ratio of the lowest difficulty blood collection history codes (number: N) to multiple blood collection history codes (number: T) (i.e., the ratio of the numbers: N / T) is greater than or equal to a threshold, the blood collection history code with the lowest difficulty may be selected as the optimal blood collection history code. Conversely, if the ratio of the lowest difficulty blood collection history codes to the blood collection history codes is less than the threshold, the most recently stored blood collection history code may be selected as the optimal blood collection history code.

[0094] The above-described embodiments have been described using a single blood sampler as an example. However, the server (102) can manage and provide blood sample history codes for multiple blood samplers, and the above-described procedures can be applied to each of the blood samplers.

[0095] According to the existing blood collection practice, the system is operated to the extent that only records are left for those subjects who had issues with blood collection (e.g., failure, side effects, etc.) in reference matters, etc. However, the blood collection history code according to the embodiment of the present invention can be applied to all subjects. Specifically, from the perspective of the clinical pathologist, it is possible to reduce blood collection failures by providing the subject's previous blood collection information in a simple code, and it is possible to reduce the failure rate by increasing concentration in the process of checking various sites (before assigning a code) to find the optimal blood vessel. Furthermore, by performing blood collection from a verified blood vessel, blood collection techniques can be improved, and concentration and confidence in blood collection can be enhanced. From the perspective of the subject, since the previous blood collection site and the size of the needle used can be explained in detail in advance, the anxiety or fear that may be felt before blood collection can be alleviated to some extent, and as a result, satisfaction with blood collection can be improved and side effects of blood collection can be minimized.

[0096] References to "one embodiment" of the principles of the present invention and various variations of this expression in this specification mean that a particular feature, structure, characteristic, etc., is included in at least one embodiment of the principles of the present invention in connection with that embodiment. Accordingly, the expression "in one embodiment" and any other variations disclosed throughout this specification are not necessarily all referring to the same embodiment.

[0097] The methods according to the various embodiments of the present invention described above may be implemented as a computer program or mobile application to be executed by combining a computer as hardware and stored on a medium. Alternatively, the steps of the methods or algorithms described in connection with the embodiments of the present invention may be implemented directly in hardware, implemented as a software module executed by hardware, or implemented by a combination thereof. The software module may reside in a random access memory (RAM), a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable recording medium well known in the art to which the present invention pertains. In addition, the algorithm may be produced in the form of an installation file and provided in the form of an online download, and for this purpose, may be stored on a server accessible through an online software market.

[0098] All embodiments and conditional examples disclosed in this specification are intended to help those skilled in the art understand the principles and concepts of the present invention. Those skilled in the art will appreciate that the present invention can be implemented in modified forms without departing from the essential characteristics thereof. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is set forth in the claims, not the foregoing description, and all differences within the scope equivalent thereto should be construed as being included in the present invention.

Claims

1. A method for managing blood collection information using a blood collection history code performed by at least one processor, A step of obtaining information on a blood collection history code of a subject from a first device; A step of storing the blood collection history code of the above blood sampler; A step of receiving a request for provision of a blood collection history code of the subject from a second device; and A step of transmitting the blood collection history code of the subject to the second device; A method for managing blood collection information, wherein the blood collection history code includes at least one of blood collection location information and blood collection difficulty information.

2. In paragraph 1, A method for managing blood collection information, wherein the above blood collection history code further includes information on the needle used during blood collection.

3. In paragraph 2, A method for managing blood collection information, wherein the blood collection history code is determined by concatenating at least one numeric value or character value that encodes each of the blood collection location information, the blood collection difficulty information, and the needle information used during the blood collection.

4. In paragraph 3, A method for managing blood collection information, wherein a numeric value or character value corresponding to needle information used during the above blood collection is omitted if determined to be a predefined value.

5. In paragraph 1, A blood collection information management method, wherein information on the blood collection history code of the subject of the blood collection includes the blood collection history code generated by the first device.

6. In paragraph 1, Information about the blood collection history code of the above blood sampler includes at least one of the blood collection location information, the blood collection difficulty information, and the needle information used during blood collection. A method for managing blood collection information, wherein the step of storing the blood collection history code of the subject of the blood collection includes the step of determining the blood collection history code of the subject of the blood collection based on information about the blood collection history code of the subject of the blood collection, and then storing it.

7. In paragraph 6, A method for managing blood collection information, further comprising the step of transmitting questionnaire data inquiring about at least one of the blood collection location information, the blood collection difficulty information, and the needle information used during the blood collection to the first device.

8. In paragraph 1, A step of receiving information about the subject of the blood collection from the first device; and A method for managing blood collection information, further comprising the step of transmitting a message requesting generation of a blood collection history code for the blood collection subject to the first device if the blood collection history code of the blood collection subject is not stored.

9. In paragraph 1, A method for managing blood collection information, wherein the blood collection history code transmitted to the second device is displayed on a display device provided in the second device or printed on a barcode output by an output device connected to the second device.

10. In paragraph 1, A step of receiving a modified blood collection history code from the second device; and A method for managing blood collection information, further comprising the step of storing the modified blood collection history code as a blood collection history code of the subject of the blood collection.

11. In paragraph 1, The step of transmitting the blood collection history code of the subject to the second device is as follows: If the blood collection history code of the above blood collection subject is stored multiple times, A step of selecting an optimal blood collection history code among multiple blood collection history codes; and A method for managing blood collection information, comprising a step of transmitting the optimal blood collection history code.

12. In paragraph 11, The above optimal blood collection history code is, Among the above multiple blood collection history codes, the most recently stored blood collection history code; Among the above multiple blood collection history codes, the blood collection history code that corresponds to the largest number; or, A method for managing blood collection information, comprising a blood collection history code of a blood collection location corresponding to the largest number of blood collection history codes among the plurality of blood collection history codes having the lowest difficulty.

13. In paragraph 11, The above optimal blood collection history code is, If the ratio of the blood collection history codes with the lowest difficulty among the above multiple blood collection history codes is greater than or equal to the threshold, the blood collection history code with the lowest difficulty is included. A blood collection information management method, wherein the blood collection history code includes the most recently stored blood collection history code if the ratio of the blood collection history codes with the lowest difficulty among the above multiple blood collection history codes is less than a threshold.

14. In a device for managing blood collection information using a blood collection history code, Department of Communications; memory; and comprising at least one processor connected to the communication unit and the memory; At least one processor of the above, Obtain information about the blood collection history code of the subject from the first device, Save the blood collection history code of the above blood sampler, Receive a request for provision of the blood collection history code of the subject from the second device, Control to transmit the blood collection history code of the subject to the second device, A blood collection information management device, wherein the above blood collection history code includes at least one of blood collection location information and blood collection difficulty information.

15. An application program stored in a recording medium that executes the method according to claim 1 when operated by a processor.

Images