JP2018156311A - Barcode reading program, barcode reading method, and barcode reader - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent from omitting obtaining data through barcode reading.SOLUTION: Disclosed is a barcode reading method that includes: obtaining one or a plurality of code strings converted from a barcode portion included in a photographed image; determining, for each of a plurality of prescribed items, whether or not code strings relating to the prescribed items are obtained; and processing for, when the code strings relating to any one of the prescribed items are not obtained, notifying alerts. Moreover, when the code strings corresponding to any one of the prescribed items are not obtained, the processing of obtaining one or a plurality of code strings converted from a barcode portion included in the following photographed image may be repeated, and when the code strings relating to all prescribed items are obtained, the completion of obtainment may be notified.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a technique for reading a barcode.

  A program for extracting a plurality of barcode portions included in one imaging screen and converting each of the barcodes into a code string is known. This program runs on, for example, a camera-equipped mobile phone.

  On the label affixed to the blood product container, a barcode relating to the blood type, the product type, and the production number is printed. If the above-described program is used, data relating to three items can be acquired by one shooting.

  However, for example, if any barcode is missing on the imaging screen, data cannot be obtained from the barcode.

JP 2005-72764 A JP-A-9-120484 JP 2004-56696 A

  An object of the present invention is, in one aspect, to prevent data acquisition omission due to barcode reading.

  In the barcode reading method according to one aspect, (A) one or a plurality of code strings converted from a barcode portion included in a photographed image is acquired, and (B) a code related to the predetermined item for each of a plurality of predetermined items. It includes determining whether or not a sequence has been acquired, and (C) processing for notifying a warning when a code sequence related to any one of the predetermined items has not been acquired.

  As one aspect, data acquisition omission due to barcode reading can be prevented.

FIG. 1 is a diagram illustrating a hardware configuration example of a user terminal. FIG. 2 is a diagram showing an example of a label attached to a blood product container. FIG. 3A is a diagram illustrating a module configuration example of a user terminal. FIG. 3B is a diagram illustrating a module configuration example of the reading control unit. FIG. 4 is a diagram illustrating a configuration example of the item table. FIG. 5 is a diagram illustrating a configuration example of a blood type table. FIG. 6 is a diagram illustrating a configuration example of a formulation type table. FIG. 7 is a flowchart showing the main process (A). FIG. 8 is a diagram showing a first item processing flow. FIG. 9 is a diagram showing a second item processing flow. FIG. 10 is a diagram showing a third item processing flow. FIG. 11 is a diagram illustrating an example of a pop-up window indicating completion of acquisition. FIG. 12 is a diagram showing a main process (A) flow. FIG. 13 is a diagram illustrating an example of a first warning popup window. FIG. 14 is a diagram showing a main process (A) flow. FIG. 15 is a diagram showing a main process (A) flow. FIG. 16 is a diagram showing a flow of the main process (B). FIG. 17 is a diagram showing a main process (B) flow. FIG. 18 is a diagram showing a main process (B) flow. FIG. 19 is a diagram showing a main process (B) flow. FIG. 20 is a diagram showing a main process (B) flow. FIG. 21 is a diagram illustrating an example of a reading result window.

  The user terminal 100 in the present embodiment may be a digital camera, a mobile phone terminal (for example, a smartphone) provided with a camera, or a tablet terminal. FIG. 1 shows a hardware configuration example of the user terminal 100. The user terminal 100 in this example is a smartphone. The user terminal 100 includes a processor 101, a storage unit 103, an antenna 111, a wireless control unit 113, an audio control unit 115, a speaker 117, a microphone 119, a display 121, a touch sensor 123, a camera 125, and a GPS (Global Positioning System) device 127. Have.

  The processor 101 may include a modem CPU (Central Processing Unit) and an application CPU. The storage unit 103 includes, for example, a ROM (Read Only Memory) 105, a RAM (Random Access Memory) 107, and a flash memory 109. For example, the ROM 105 stores preset data and programs. The RAM 107 is an example of a volatile memory. The RAM 107 includes, for example, an area for developing programs such as applications and data. The RAM 107 also includes an area for storing temporary data such as a through image and a photographed photograph image. The flash memory 109 stores programs such as an operating system and applications, and further stores data as needed.

  The touch sensor 123 is, for example, a panel-shaped sensor arranged on the display screen of the display 121, and accepts a touch operation (for example, a shutter operation or a button touch operation). For example, the display 121 displays various screens (for example, screens including through images) displayed by the application. Specifically, it is used as a touch panel in which the display 121 and the touch sensor 123 are integrated. A touch event is generated by a touch operation on the touch sensor 123. In addition to the touch sensor 123, a key may be provided.

  The antenna 111 receives cellular radio data, for example. The wireless control unit 113 controls wireless communication. The voice communication and data communication of the telephone are performed by controlling the wireless communication.

  The audio control unit 115 performs analog / digital conversion and digital / analog conversion on sound data. The speaker 117 outputs analog data as sound. The microphone 119 converts sound into analog data.

  The camera 125 is used for capturing a through image and a stored image. The camera 125 may capture a still image, or may capture both a still image and a moving image.

  FIG. 2 shows an example of a label attached to a blood product container. On the label, a barcode 201 relating to blood type, a barcode 203 relating to the preparation type, and a barcode 205 relating to the production number are printed. The user uses the camera 125 of the user terminal 100 to take an image so that these barcodes 201 to 205 are included in one image.

  FIG. 3A shows a module configuration example of the user terminal 100. The user terminal 100 includes a barcode reading unit 301, a verification unit 309, and an order database 311. The barcode reading unit 301 reads a barcode. The barcode reading unit 301 includes an imaging unit 303, a conversion unit 305, and a reading control unit 307. The imaging unit 303 performs imaging using the camera 125. The photographing unit 303 is realized by the processor 101 executing a photographing program (for example, a camera application) loaded in the RAM 107. The conversion unit 305 extracts a barcode part from the photographed image and converts the barcode part into a code string. The code string in this example is a numeric string. However, the code included in the code string may be a symbol string or a character. When the barcode part is extracted from the captured image, the conversion unit 305 converts each barcode part into a code string. The conversion unit 305 is realized by the processor 101 executing the conversion program loaded in the RAM 107. In this example, it is assumed that the shooting program is started by the conversion unit 305. The conversion program is started by the reading control unit 307.

  A reading control unit 307 controls barcode reading processing. The reading control unit 307 activates the conversion unit 305 and acquires a code string from the conversion unit 305. Then, the reading control unit 307 determines that the data acquisition is completed when the code string related to the predetermined item is obtained. The module configuration of the reading control unit 307 will be described later with reference to FIG. 3B.

  The type of application using the result of barcode reading is arbitrary. In this example, the verification unit 309 verifies the data acquired by the reading control unit 307. Specifically, the verification unit 309 determines whether the data acquired by the reading control unit 307 matches an order stored in the order database 311.

  The barcode reading unit 301, the photographing unit 303, the conversion unit 305, the reading control unit 307, the verification unit 309, and the order database 311 described above execute the hardware resource (for example, FIG. 1) and the processing described below on the processor 101. This is realized using a program to be executed.

  FIG. 3B shows a module configuration example of the reading control unit 307. The reading control unit 307 includes an acquisition unit 321, a determination unit 323, a display processing unit 325, a reception unit 327, an output unit 329, an extraction unit 331, an item table storage unit 341, a blood type table storage unit 343, and a formulation type table storage unit 345. Have

  The acquisition unit 321 starts a conversion program and acquires one or more code strings from the conversion unit 305. For example, the determination unit 323 determines whether data related to a predetermined item has been obtained. The display processing unit 325 displays various windows. The display processing unit 325 is an example of a notification unit that notifies a warning. The accepting unit 327 accepts an instruction operation from the user. The accepting unit 327 accepts, for example, a button touch operation. The output unit 329 outputs the obtained data. The output data is passed to another software module (in this example, the verification unit 309). The extraction unit 331 extracts a part of codes included in the code string.

  The item table storage unit 341 stores an item table. The item table will be described later with reference to FIG. The blood type table storage unit 343 stores a blood type table. The blood type table will be described later with reference to FIG. The formulation type table storage unit 345 stores a formulation type table. The formulation type table will be described later with reference to FIG.

  The acquisition unit 321, the determination unit 323, the display processing unit 325, the reception unit 327, the output unit 329, and the extraction unit 331 described above are hardware resources (for example, FIG. 1) and a program that causes the processor 101 to execute processing described below. It is realized using.

  The item table storage unit 341, blood group table storage unit 343, and formulation type table storage unit 345 described above are realized using hardware resources (for example, FIG. 1).

  FIG. 4 shows a configuration example of the item table. The item table in this example has records corresponding to the items. The record of the item table includes a field in which an item ID is set, a field in which an item name is set, a field in which an item code is set, a field of a reading result, and a field in which a content code is set. have.

  The item ID identifies the item. The item name specifies the content of the item. The item code is included in the code string and specifies that it is a code string related to the item. The item ID, item name, and item code are set in advance.

  The reading result indicates whether or not a code string is obtained from the barcode related to the item. Specifically, a code indicating “success” or a code indicating “failure” is set in the field of the reading result. If a code indicating “success” is set, it means that a code string has already been obtained from the barcode related to the item. When a code indicating “failure” is set, it means that a code string has not yet been obtained from the barcode related to the item.

  The content code specifies the content related to the item. The content code regarding the blood type item is a blood type code. The blood type code will be described later. The content code regarding the item of the formulation type is a formulation type code. The formulation type code will be described later. The content code regarding the item of the production number is the production number. Note that the item code in this example is a two-digit number. The blood type code is also a two-digit number. Similarly, the formulation type code is also a two-digit number. The serial number is a 10-digit number.

  The present embodiment may be applied to products other than blood products. In that case, a set of predetermined items (corresponding to FIG. 4) may be provided for each product.

  FIG. 5 shows a configuration example of the blood type table. The blood type table in this example has a record corresponding to the blood type. The record of the blood type table has a field in which a blood type code is set and a field in which a blood type name is set. The blood type code identifies the blood type. The blood type name is the name of the blood type. It is assumed that the blood type table is provided in advance.

  FIG. 6 shows a configuration example of the formulation type table. The formulation type table in this example has a record corresponding to the formulation type. The record of the formulation type table has a field in which the formulation type code is set and a field in which the formulation name is set. The formulation type code identifies the formulation type. The formulation name is the name of the formulation related to the formulation type. It is assumed that the formulation type table is provided in advance.

  Subsequently, processing of the reading control unit 307 will be described. FIG. 7 shows a main process (A) flow. The acquisition unit 321 starts a conversion program (S701). The processor 101 executes processing of the conversion program loaded in the RAM 107, thereby realizing the conversion unit 305.

  Note that the conversion unit 305 activates a shooting program. The processor 101 executes processing of the shooting program loaded in the RAM 107, thereby realizing the shooting unit 303. The conversion unit 305 extracts a barcode part included in the image photographed by the photographing unit 303 and converts the barcode part image into a code string. When it is determined that one bar code portion is included in the photographed image, the conversion unit 305 identifies one code string. When it is determined that the captured image includes two barcode portions, the conversion unit 305 identifies two code strings. In addition, when it is determined that the captured image includes three barcode portions, the conversion unit 305 specifies three code strings.

  The code string converted from the blood type bar code includes an item code indicating a blood type item and a blood type code which is a content code in the blood type. The code string converted from the barcode relating to the formulation type includes an item code indicating that it is an item of the formulation type and a formulation type code that is a content code in the formulation type. The code string converted from the barcode relating to the manufacturing number includes an item code indicating that the item is a manufacturing number item and a manufacturing number which is a content code in the manufacturing number.

  When the conversion unit 305 specifies one or more code strings, the conversion unit 305 stops the shooting program. Then, the code string is delivered to the reading control unit 307, and the conversion unit 305 ends the processing.

  The acquisition unit 321 waits for the end of the conversion program (S703). At this time, the acquisition unit 321 acquires one or more code strings from the conversion unit 305 (S705).

  The determination unit 323 executes the first item process (S707). FIG. 8 shows a first item processing flow. The determination unit 323 specifies one code string acquired in S705 (S801). The determination unit 323 determines whether the code string includes a blood type item code (S803).

  If it is determined that the code string identified in S801 includes a blood type item code, the determination unit 323 adds a code indicating “success” to the read result field included in the blood type record in the item table. Setting is made (S805). Further, the extraction unit 331 extracts a blood type code from the code string (S807). The extraction unit 331 sets the blood type code in the content code field included in the blood type record in the item table (S809). Then, the determination unit 323 finishes the first item process and returns to the main process (A) of the caller.

  On the other hand, when it is determined that the code string specified in S801 does not include the blood type item code, the determination unit 323 determines whether there is an unspecified code string (S811). If it is determined that there is an unspecified code string, the process returns to the process shown in S801 and the above-described process is repeated.

  On the other hand, if it is determined that there is no unspecified code string, the determination unit 323 sets a code indicating “failure” in the field of the reading result included in the blood type record in the item table (S813). Then, the determination unit 323 finishes the first item process and returns to the main process (A) of the caller.

  Returning to the description of FIG. The determination unit 323 executes the second item process (S709). FIG. 9 shows a second item processing flow. The determination unit 323 specifies one code string acquired in S705 (S901). The determination unit 323 determines whether or not the code string includes an item code of the formulation type (S903).

  If it is determined that the code string identified in S901 includes the item code of the formulation type, the determination unit 323 adds a code indicating “success” to the field of the read result included in the record of the formulation type in the item table. Set (S905). Further, the extraction unit 331 extracts a formulation type code from the code string (S907). The extraction unit 331 sets the formulation type code in the content code field included in the formulation type record in the item table (S909). Then, the determination unit 323 finishes the second item process and returns to the caller main process (A).

  On the other hand, when it is determined that the code string specified in S901 does not include the item code of the formulation type, the determination unit 323 determines whether there is an unspecified code string (S911). If it is determined that there is an unspecified code string, the process returns to S901 and the above-described process is repeated.

  On the other hand, if it is determined that there is no unspecified code string, the determination unit 323 sets a code indicating “failure” in the field of the read result included in the formulation type record in the item table (S913). Then, the determination unit 323 finishes the second item process and returns to the caller main process (A).

  Returning to the description of FIG. The determination unit 323 executes third item processing (S711). FIG. 10 shows a third item processing flow. The determination unit 323 specifies one code string acquired in S705 (S1001). The determination unit 323 determines whether or not the code string includes an item code of a manufacturing number (S1003).

  If it is determined that the code string specified in S1001 includes the item code of the production number, the determination unit 323 adds a code indicating “success” to the field of the read result included in the record of the production number in the item table. Setting is made (S1005). Further, the extraction unit 331 extracts the production number from the code string (S1007). The extraction unit 331 sets the production number in the content code field included in the production number record in the item table (S1009). Then, the determination unit 323 finishes the third item process and returns to the caller main process (A).

  On the other hand, when it is determined that the code string specified in S1001 does not include the item code of the manufacturing number, the determination unit 323 determines whether there is an unspecified code string (S1011). If it is determined that there is an unspecified code string, the process returns to the process shown in S1001 and the above-described process is repeated.

  On the other hand, when determining that there is no unspecified code string, the determination unit 323 sets a code indicating “failure” in the field of the read result included in the record of the production number in the item table (S1013). Then, the determination unit 323 finishes the third item process and returns to the caller main process (A).

  Returning to the description of FIG. The determination unit 323 determines whether data acquisition has succeeded for all items (S713). Specifically, the determination unit 323 reads the reading result field included in the blood type record in the item table, the reading result field included in the formulation type record, and the reading result field included in the production number record. It is determined whether or not a code indicating “success” is set. If it is determined that data acquisition has succeeded for all items, the conversion unit 305 displays a pop-up window indicating acquisition completion (S715).

  FIG. 11 shows an example of an acquisition completion pop-up window. In the acquisition completion pop-up window, a message indicating that the reading of data has been completed is displayed. In addition, the blood type name corresponding to the read blood type code, the preparation name corresponding to the read preparation type code, and the read manufacturing number are also displayed in the pop-up window indicating completion of acquisition. Furthermore, the acquisition completion pop-up window includes a confirmation button. When the confirmation button is touched, the acquisition completion pop-up window disappears.

  The acquisition completion pop-up window is an example of a form for notifying completion of acquisition of data relating to a predetermined item. For example, a voice output unit may be provided in the user terminal 100, and the voice output unit may output a voice indicating completion of acquisition of data related to a predetermined item. Alternatively, a transmission unit may be provided in the user terminal 100, and the transmission unit may transmit a message notifying completion of data acquisition related to a predetermined item.

  Returning to the description of FIG. When the reading control unit 307 receives a touch of a confirmation button (S717), the conversion unit 305 finishes displaying the pop-up window indicating completion of acquisition. Then, the verification unit 309 outputs the reading result (S719). The read result includes the read blood type code, the read formulation type code, and the read manufacturing number. Then, the reading control unit 307 finishes the main process (A).

  If it is not determined in S713 that data acquisition has succeeded for all items, that is, if data acquisition has failed for some items, the process proceeds to S1201 shown in FIG.

  Turning to the description of FIG. The determination unit 323 determines whether data acquisition has failed for the first item (blood type) and the second item (formulation type) (S1201). Specifically, the determination unit 323 sets a code indicating “failure” in the reading result field included in the blood type record and the reading result field included in the formulation type record in the item table. Determine whether or not.

  When it is determined that data acquisition has failed for the first item (blood type) and the second item (formulation type), the display processing unit 325 displays a first warning pop-up window (S1203).

  FIG. 13 shows an example of the first warning popup window. In the first warning pop-up window, a message indicating that the reading of the blood type barcode and the reading of the barcode of the preparation type has failed is displayed. Further, the first warning pop-up window includes a continue button and a cancel button. When the continuation button is touched, the barcode reading operation starts again. When the cancel button is touched, the main process (A) ends.

  Returning to the description of FIG. The accepting unit 327 accepts a button touch (S1205). The determination unit 323 determines whether or not the touched button is a continuation button (S1207). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1209). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, if it is determined in S1207 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1211). Then, the processing returns to S701 illustrated in FIG.

  In S1201, when it is not determined that data acquisition has failed for the first item (blood type) and the second item (formulation type), the determination unit 323 determines whether the first item (blood type) and the third item ( It is determined whether or not the data acquisition for the production number) has failed (S1213). Specifically, the determination unit 323 sets a code indicating “failure” in the reading result field included in the blood type record and the reading result field included in the formulation type record in the item table. Determine whether or not.

  If it is determined that data acquisition has failed for the first item (blood type) and the third item (manufacturing number), the display processing unit 325 displays a second warning pop-up window (S1215).

  In the second warning pop-up window, a message indicating that reading of the blood type barcode and reading of the serial number barcode has failed is displayed. Further, the second warning pop-up window includes a continuation button and a cancel button similar to the case of the first warning pop-up window.

  The accepting unit 327 accepts a button touch (S1217). The determination unit 323 determines whether or not the touched button is a continuation button (S1219). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1221). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, if it is determined in S1219 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1223). Then, the processing returns to S701 illustrated in FIG.

  In S1213, when it is not determined that data acquisition has failed for the first item (blood type) and the third item (manufacturing number), the process proceeds to S1401 shown in FIG.

  Turning to the description of FIG. The determination unit 323 determines whether data acquisition has failed for the second item (formulation type) and the third item (manufacturing number) (S1401). Specifically, the determination unit 323 sets a code indicating “failure” in the reading result field included in the formulation type record and the reading result field included in the record of the manufacturing number in the item table. Determine whether or not.

  If it is determined that data acquisition has failed for the second item (formulation type) and the third item (manufacturing number), the display processing unit 325 displays a third warning pop-up window (S1403).

  In the third warning pop-up window, a message indicating that reading of the barcode of the preparation type and reading of the barcode of the production number has failed is displayed. Further, the third warning pop-up window includes a continue button and a cancel button similar to the case of the first warning pop-up window.

  The accepting unit 327 accepts a button touch (S1405). The determination unit 323 determines whether or not the touched button is a continuation button (S1407). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1409). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, when it is determined in S1407 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1411). Then, the processing returns to S701 illustrated in FIG.

  In S1401, if it is not determined that data acquisition has failed for the second item (formulation type) and the third item (manufacturing number), the determination unit 323 fails to acquire data for the first item (blood type). It is determined whether or not (S1413). Specifically, the determination unit 323 determines whether or not a code indicating “failure” is set in the field of the reading result included in the blood type record in the item table.

  If it is determined that data acquisition has failed for the first item (blood type), the display processing unit 325 displays a fourth warning pop-up window (S1415).

  In the fourth warning pop-up window, a message indicating that reading of the blood group barcode has failed is displayed. Further, the fourth warning pop-up window includes a continuation button and a cancel button similar to the case of the first warning pop-up window.

  The accepting unit 327 accepts a button touch (S1417). The determination unit 323 determines whether or not the touched button is a continuation button (S1419). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1421). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, if it is determined in S1419 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1423). Then, the processing returns to S701 illustrated in FIG.

  In S1413, if it is not determined that data acquisition has failed for the first item (blood type), the process proceeds to the process of S1501 illustrated in FIG.

  Turning to the description of FIG. The determination unit 323 determines whether data acquisition has failed for the second item (formulation type) (S1501). Specifically, the determination unit 323 determines whether or not a code indicating “failure” is set in the field of the read result included in the formulation type record in the item table.

  If it is determined that data acquisition has failed for the second item (formulation type), the display processing unit 325 displays a fifth warning pop-up window (S1503).

  In the fifth warning pop-up window, a message indicating that reading of the barcode of the preparation type has failed is displayed. Further, the fifth warning pop-up window includes a continuation button and a cancel button similar to the case of the first warning pop-up window.

  The accepting unit 327 accepts a button touch (S1505). The determination unit 323 determines whether the touched button is a continuation button (S1507). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1509). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, if it is determined in S1507 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1511). Then, the processing returns to S701 illustrated in FIG.

  In S1501, if it is not determined that data acquisition has failed for the second item (formulation type), that is, if data acquisition has failed for the third item (manufacturing number), the display processing unit 325 displays a sixth warning. A pop-up window is displayed (S1513).

  In the sixth warning pop-up window, a message that the reading of the serial number barcode has failed is displayed. Further, the sixth warning pop-up window includes a continuation button and a cancel button similar to the case of the first warning pop-up window.

  The accepting unit 327 accepts a button touch (S1515). The determination unit 323 determines whether or not the touched button is a continuation button (S1517). If it is determined that the touched button is not a continuation button, that is, if the touched button is a cancel button, the output unit 329 outputs a reading failure code (S1519). Then, the reading control unit 307 finishes the main process (A). In this example, the read failure code is passed to the verification unit 309.

  On the other hand, when it is determined in S1517 that the touched button is a continuation button, the determination unit 323 clears the code set in the read result field in each record of the item table (S1521). Then, the processing returns to S701 illustrated in FIG.

  According to the present embodiment, a warning pop-up window is displayed when a barcode related to any item is not read, so that data acquisition omission due to barcode reading can be prevented.

[Embodiment 2]
In the above-described embodiment, an example has been described in which, when a code string related to any item is not acquired, code strings related to all items are acquired again. In the present embodiment, an example will be described in which the code strings related to the remaining items are supplementarily acquired when the code strings related to any of the items are not acquired.

  FIG. 16 shows a main process (B) flow. The processing shown in S1601 to S1605 is the same as the processing in S701 to S705 shown in FIG.

  The determination unit 323 determines whether data acquisition is successful for the first item (blood type) (S1607). Specifically, the determination unit 323 determines whether or not a code indicating “success” is set in the field of the read result included in the blood type record in the item table.

  If it is determined that data acquisition is successful for the first item (blood type), the process proceeds to S1611. On the other hand, when it is determined that the data acquisition for the first item (blood type) is not successful, that is, when the data acquisition for the first item (blood type) is unsuccessful, the determination unit 323 determines the first item. Processing is executed (S1609). The first item process is the same as in the first embodiment. When the first item process is completed, the process proceeds to S1611.

  The determination unit 323 determines whether data acquisition has succeeded for the second item (formulation type) (S1611). Specifically, the determination unit 323 determines whether or not a code indicating “success” is set in the field of the read result included in the formulation type record in the item table.

  If it is determined that data acquisition has succeeded for the second item (formulation type), the process proceeds to S1615. On the other hand, when it is determined that the data acquisition for the second item (formulation type) is not successful, that is, when the data acquisition for the second item (formulation type) is unsuccessful, the determination unit 323 sets the second item. Processing is executed (S1613). The second item process is the same as that in the first embodiment. When the second item process ends, the process proceeds to S1615.

  The determination unit 323 determines whether data acquisition is successful for the third item (manufacturing number) (S1615). Specifically, the determination unit 323 determines whether or not a code indicating “success” is set in the field of the reading result included in the record of the production number in the item table.

  If it is determined that the data acquisition for the third item (manufacturing number) is successful, the process proceeds to the process of S1701 shown in FIG. On the other hand, when it is determined that the data acquisition for the third item (manufacturing number) has not been successful, that is, when the data acquisition for the third item (manufacturing number) has failed, the determining unit 323 determines that the third item Processing is executed (S1617). The third item process is the same as that in the first embodiment. When the third item process is finished, the process proceeds to the process of S1701 shown in FIG.

  Turning to the description of FIG. The processing shown in S1701 to S1707 is the same as the processing in S713 to S719 shown in FIG.

  If it is not determined in S1701 that data acquisition has succeeded for all items, that is, if data acquisition has failed for some items, the process proceeds to S1801 shown in FIG.

  Turning to the description of FIG. The processing shown in S1801 to S1809 is the same as the processing in S1201 to S1209 shown in FIG. If it is determined in S1807 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the field of the reading result in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  The processing shown in S1811 through S1819 is the same as the processing in S1213 through S1221 shown in FIG. If it is determined in S1817 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the read result field in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  If it is not determined in S1811 that data acquisition has failed for the first item (blood type) and the third item (manufacturing number), the process proceeds to S1901 shown in FIG.

  Turning to the description of FIG. The processing shown in S1901 to S1909 is the same as the processing of S1401 to S1409 shown in FIG. If it is determined in S1907 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the read result field in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  The processing shown in S1911 through S1919 is the same as the processing in S1413 through S1421 shown in FIG. If it is determined in S1917 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the field of the reading result in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  In S1911, if it is not determined that data acquisition has failed for the first item (blood type), the process proceeds to the process of S2001 illustrated in FIG.

  Turning to the description of FIG. The processes shown in S2001 to S2009 are the same as the processes in S1501 to S1509 shown in FIG. If it is determined in S2007 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the read result field in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  The processing shown in S2011 to S2017 is the same as the processing of S1513 to S1519 shown in FIG. If it is determined in S2015 that the touched button is a continuation button, the determination unit 323 does not clear the code set in the read result field in each record of the item table, and does not clear the code through the terminal F. Then, the process returns to S1601 shown in FIG.

  Note that, for example, the reading result window shown in FIG. 21 may be displayed while the through image is displayed by the processing of the photographing program. In the reading result window, whether the barcode reading for each item is completed or not is displayed. For example, before or after S1601 shown in FIG. 16, the display processing unit 325 displays a reading result window. Then, for example, before or after S1605 shown in FIG. 16, the display processing unit 325 erases the reading result window.

  According to the present embodiment, the process of acquiring the code string is repeated, and when the code strings related to all items are acquired, the completion of acquisition is notified, so that the completion of data acquisition by barcode reading can be confirmed.

  Although the embodiment of the present invention has been described above, the present invention is not limited to this. For example, the functional block configuration described above may not match the program module configuration.

  Further, the configuration of each storage area described above is an example, and the above configuration is not necessarily required. Further, in the processing flow, if the processing result does not change, the processing order may be changed or a plurality of processes may be executed in parallel.

  The embodiment of the present invention described above is summarized as follows.

  In the barcode reading method according to the present embodiment, (A) one or a plurality of code strings converted from a barcode portion included in a captured image is acquired, and (B) the predetermined item for each of a plurality of predetermined items. (C) includes a process of notifying a warning when a code string related to any one of the predetermined items is not acquired.

  In this way, data acquisition omission due to barcode reading can be prevented.

  Further, when the code string corresponding to any one of the predetermined items is not acquired, the process of acquiring one or a plurality of code strings converted from the barcode part included in the next photographed image is repeated, and all the predetermined items are obtained. The acquisition completion may be notified when the code string regarding is acquired.

  In this way, completion of data acquisition by reading a barcode can be confirmed.

  A program for causing a computer to perform the processing according to the above method can be created. The program can be a computer-readable storage medium such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. It may be stored in a storage device. Note that intermediate processing results are generally temporarily stored in a storage device such as a main memory.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1)
Obtain one or more code strings converted from the barcode part included in the captured image,
For each of the plurality of predetermined items, determine whether a code string related to the predetermined item has been acquired,
A barcode reading program for causing a processor to execute a process of notifying a warning when the code string related to any one of the predetermined items is not acquired.

(Appendix 2)
Furthermore,
When the code string corresponding to any one of the predetermined items is not acquired, the process of acquiring one or a plurality of code strings converted from the barcode part included in the next captured image is repeated,
The barcode reading program according to supplementary note 1, including a process of notifying completion of acquisition when the code strings related to all the predetermined items are acquired.

(Appendix 3)
Obtain one or more code strings converted from the barcode part included in the captured image,
For each of the plurality of predetermined items, determine whether a code string related to the predetermined item has been acquired,
A bar code reading method executed by a processor, including: notifying a warning when the code string related to any one of the predetermined items is not acquired.

(Appendix 4)
An acquisition unit that acquires one or a plurality of code strings converted from the barcode part included in the captured image;
For each of the plurality of predetermined items, a determination unit that determines whether or not a code string related to the predetermined item has been acquired;
A barcode reader having a notification unit that notifies a warning when the code string related to any of the predetermined items is not acquired.

DESCRIPTION OF SYMBOLS 100 User terminal 301 Barcode reading part 303 Imaging | photography part 305 Conversion part 307 Reading control part 309 Verification part 311 Order database 321 Acquisition part 323 Determination part 325 Display processing part 327 Reception part 329 Output part 331 Extraction part 341 Item table storage part 343 Blood Type table storage unit 345 Formulation type table storage unit

Claims (4)

Obtain one or more code strings converted from the barcode part included in the captured image,
For each of the plurality of predetermined items, determine whether a code string related to the predetermined item has been acquired,
A barcode reading program for causing a processor to execute a process of notifying a warning when the code string related to any one of the predetermined items is not acquired. Furthermore,
When the code string corresponding to any one of the predetermined items is not acquired, the process of acquiring one or a plurality of code strings converted from the barcode part included in the next captured image is repeated,
The barcode reading program according to claim 1, further comprising a process of notifying completion of acquisition when the code strings related to all the predetermined items are acquired. Obtain one or more code strings converted from the barcode part included in the captured image,
For each of the plurality of predetermined items, determine whether a code string related to the predetermined item has been acquired,
A bar code reading method executed by a processor, including: notifying a warning when the code string related to any one of the predetermined items is not acquired. An acquisition unit that acquires one or a plurality of code strings converted from the barcode part included in the captured image;
For each of the plurality of predetermined items, a determination unit that determines whether or not a code string related to the predetermined item has been acquired;
A barcode reader having a notification unit that notifies a warning when the code string related to any of the predetermined items is not acquired.

Images