Information processing method, information processing device, and computer program

Abstract

To further increase the job efficiency of pharmacies.SOLUTION: An input interface 21 receives first identification information ID1 associated with a patient name registered in a first database 31 pertaining to a pharmaceutical dispensing job, and second identification information ID2 registered in a second database 32 pertaining to a job different from the pharmaceutical dispensing job. When the first identification information ID1 and the second identification information ID2 match, a processor 22 generates linkage data LD in which information stored in the first database 31 in association with the patient name is associated with the second identification information ID2.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to an information processing method executed in a system for supporting the operations of a pharmacy. The present disclosure also relates to an information processing apparatus included in the system and a computer program executable by a processor mounted on the information processing apparatus.

Background Art

[0002] Patent Document 1 discloses a system for supporting the dispensing operation of a pharmacy based on the content of a prescription issued by a doctor.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a demand for further improving the operational efficiency of pharmacies.

Means for Solving the Problems

[0005] One exemplary aspect provided by the present disclosure is an information processing method executed by at least one arithmetic unit, identifying first identification information associated with a patient name registered in a first database related to a dispensing operation, identifying second identification information registered in a second database related to an operation different from the dispensing operation, when the first identification information and the second identification information match, generating association data in which the information stored in association with the patient name in the first database is associated with the second identification information.

[0006] One exemplary aspect provided by the present disclosure is an information processing apparatus, An interface that receives first identification information associated with a patient name registered in a first database related to a dispensing operation and second identification information registered in a second database related to an operation different from the dispensing operation, and A processor that generates association data in which information stored associated with the patient name in the first database is associated with the second identification information when the first identification information and the second identification information match, and is provided.

[0007] One aspect example provided by the present disclosure is a computer program executable by a processor mounted on an information processing device, and when executed, the information processing device identifies first identification information associated with a patient name registered in a first database related to a dispensing operation, identifies second identification information registered in a second database related to an operation different from the dispensing operation, and when the first identification information and the second identification information match, generates association data in which information stored associated with the patient name in the first database is associated with the second identification information.

[0008] According to the configuration according to each of the above aspect examples, the information of the patient stored in the first database related to the dispensing operation, which is essential for the operation of the pharmacy, can be effectively utilized, and the association with the information related to other operations provided to the patient and the linkage with the application that executes the other operations can be automated. As a result, manual processing and the intervention of paper media can be reduced or eliminated, and the business efficiency of the pharmacy can be further improved.

[0009] In the dispensing pharmacy industry, in recent years, the top 10 companies' sales only account for 15% of the whole, and the oligopolization has not advanced. In other words, the dispensing pharmacy industry is mostly occupied by small and medium-sized pharmacies with low capital strength. This situation was one of the reasons why the reduction of manual processing and the intervention of paper media did not progress. Therefore, according to the information processing method according to the present embodiment, the efficiency of operations in small and medium-sized pharmacies in particular can be significantly promoted, and thus the activation of the dispensing pharmacy industry can be promoted.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Embodiments for Carrying Out the Invention

[0011] With reference to the accompanying drawings, examples of embodiments will be described in detail below.

[0012] FIG. 1 illustrates the functional configuration of a business support system 10 according to an embodiment. The business support system 10 is a system for promoting the linkage with operations different from the dispensing operation that can be carried out at a pharmacy.

[0013] The business support system 10 includes an information processing device 20. The information processing device 20 is configured to be used at a pharmacy. The information processing device 20 may be a stationary device installed and used at an appropriate location, or a portable device that can be carried by a user.

[0014] The business support system 10 includes a first database 31. The first database 31 is configured to store information related to the dispensing operation. For example, the first database 31 is configured to store information compliant with the dispensing system prescription sharing specification (NSIPS: New Standard Interface of Pharmacy-system Specifications; registered trademark). The information includes at least the name of the patient and information for creating a dispensing remuneration statement based on the prescription issued by a doctor for the patient.

[0015] The first database 31 can be installed in a device independent of the information processing device 20. Examples of such a device include a reception computer capable of communicating with the information processing device 20. The first database 31 may be constructed in a storage (not shown) built into the information processing device 20.

[0016] The business support system 10 includes a second database 32. The second database 32 is configured to store information related to a business different from the dispensing business. As an example, the second database 32 can be configured to store information related to the expense billing business. The expense billing business is a business of billing a patient for the amount of remuneration calculated based on the dispensing remuneration statement. Therefore, the said information includes at least information for identifying the patient.

[0017] The second database 32 can be installed in a device independent of the information processing device 20. Examples of such a device include a computer for expense billing business capable of communicating with the information processing device 20. The second database 32 may be constructed in a storage (not shown) built into the information processing device 20.

[0018] The information processing device 20 includes an input interface 21. The input interface 21 is configured to be able to receive first identification information ID1 associated with the patient name registered in the first database 31. The first identification information ID1 may be the patient's name itself or other information capable of identifying the patient.

[0019] When the first database 31 is installed in a device independent of the information processing device 20, the input interface 21 is configured as a hardware interface. When the first database 31 is constructed in a storage built into the information processing device 20, the input interface 21 may be a hardware interface or a software interface.

[0020] The input interface 21 is configured to be able to receive second identification information ID2 associated with the patient name as the payee registered in the second database 32. The second identification information ID2 may be the patient's name itself or other information capable of identifying the patient. However, the first identification information ID1 and the second identification information ID2 need to refer to the same attribute. That is, when the first identification information ID1 is the patient name, the second identification information ID2 also needs to be the patient name.

[0021] When the second database 32 is installed in a device independent of the information processing device 20, the input interface 21 is configured as a hardware interface. When the second database 32 is constructed in a storage built into the information processing device 20, the input interface 21 may be a hardware interface or a software interface.

[0022] The information processing device 20 includes a processor 22. When the first identification information ID1 and the second identification information ID2 received by the input interface 21 match, the processor 22 is configured to generate linkage data LD by associating the information stored in the first database 31 in association with the patient name with the second identification information ID2. In this example, the dispensing remuneration amount calculated for the patient specified by the first identification information ID1 is associated with the patient specified by the second identification information ID2.

[0023] The information processing device 20 includes an output interface 23. The processor 22 is configured to output the linkage data LD from the output interface 23 to the linked application 40. The linked application 40 according to this example is an application that executes a settlement agency service.

[0024] The associated application 40 may be executed on a device independent of the information processing device 20, or may be executed on the information processing device 20. When the associated application 40 is executed on a device independent of the information processing device 20, the output interface 23 is configured as a hardware interface. When the associated application 40 is executed on the information processing device 20, the output interface 23 may be a hardware interface or a software interface.

[0025] The business support system 10 includes a display device 50. The display device 50 is configured to be able to provide a user interface screen (hereinafter abbreviated as UI screen) for outputting the associated data LD. A specific example of the UI screen will be shown later. The display device 50 may be a device independent of the information processing device 20 or may be a part of the information processing device 20. The processor 22 of the information processing device 20 is configured to output a display control signal DC for causing the display device 50 to display a UI screen from the output interface 23.

[0026] The display control signal DC may be an analog signal or a digital signal according to the specifications of the display device 50. When the display control signal DC is an analog signal, the output interface 23 includes an appropriate conversion circuit including a D / A converter.

[0027] FIG. 2 shows an example of the flow of an information processing method executed by the information processing device 20 configured as described above. FIG. 3 illustrates the initial state of the UI screen displayed on the display device 50. The UI screen includes a task bar 50A. In this example, the "Claim" button image 50B is in a selected state.

[0028] Note that the selection state of the button image can be realized by appropriately operating the button image with a cursor displayed on the UI screen using an input device such as a mouse. Alternatively, when the display device 50 has a touch panel function, the selection state can be realized by appropriately touching the button image on the UI screen.

[0029] When the "Claim" button image 50B is in the selected state, the UI screen includes the "NSIPS Import" button image 50C. When the "NSIPS Import" button image 50C is selected, the UI screen transitions to the state illustrated in FIG. 4.

[0030] The UI screen in the state illustrated in FIG. 4 includes a dialog box 50D for specifying the range of information received from the first database 31. The dialog box 50D includes a text box 50E for specifying the period for which cost claims are to be made. When the user enters the desired period in the text box 50E and sets the "Import" button image 50F to the selected state, data that meets the specified conditions is acquired from the first database 31 through the input interface 21 of the information processing apparatus 20 (STEP1 in FIG. 2).

[0031] The processor 22 outputs a display control signal DC for visualizing the acquired information on the UI screen of the display device 50 from the output interface 23. The UI screen transitions to the state illustrated in FIG. 5.

[0032] The UI screen illustrated in FIG. 5 includes a patient display pane 50G, a subtotal display pane 50H, and a details display pane 50I.

[0033] In the patient display pane 50G, at least information indicating the patient name among the information included in the data acquired from the first database 31 is listed. In the illustrated example, the patient named "NAME 1" is in the selected state.

[0034] The subtotal display pane 50H lists the subtotal of the remuneration amount for each dispensing date for the patients selected in the patient display pane 50G among the information included in the data acquired from the first database 31. In the illustrated example, the subtotal of the remuneration amount is shown for each of the three dispensings performed in July 2023 for the patient "NAME 1".

[0035] The details display pane 50I lists the details of the dispensing remuneration for the patients selected in the patient display pane 50G among the information included in the data acquired from the first database 31. The details of the dispensing remuneration include the dispensing date, applicable item, remuneration points, and total remuneration amount.

[0036] The subtotal display pane 50H includes checkboxes that can be toggled between a selected state and a non - selected state for each dispensing date. The illustrated state corresponds to the selected state. When a checkbox is in the non - selected state, the information related to the details of the dispensing remuneration on the dispensing date corresponding to the checkbox is excluded from the display target of the details display pane 50I and also subtracted from the total remuneration amount.

[0037] When the "Patient List" button image 50J on the task bar 50A is selected, the UI screen transitions to the state illustrated in FIG. 6. The UI screen in this state includes a patient display pane 50K and a details display pane 50L.

[0038] The patient display pane 50K lists at least the information indicating the patient name and date of birth among the information included in the data acquired from the first database 31. In the illustrated example, the patient named "NAME 3" is in the selected state.

[0039] The details display pane 50L displays more detailed attribute information for the patients selected in the patient display pane 50K among the information included in the data acquired from the first database 31. In the illustrated example, the kana name, date of birth, age, and gender are displayed.

[0040] When the "Claimant List" button image 50M of the task bar 50A is in the selected state, the UI screen transitions to the state illustrated in FIG. 7. The UI screen in this state includes the "Data Import" button image 50N. When the "Data Import" button image 50N is in the selected state, a dialog box for specifying the file stored in the second database 32 is displayed (not shown). By specifying the file through the dialog box, data corresponding to the file is acquired from the second database 32 through the input interface 21 of the information processing apparatus 20 (STEP2 in FIG. 2).

[0041] The UI screen in the state illustrated in FIG. 7 includes a claimant display pane 50O and a detailed display pane 50P.

[0042] In the claimant display pane 50O, at least the patient name and CID as the claimant of the dispensing remuneration among the information included in the data acquired from the second database 32 are listed. The CID is information that can uniquely identify the claimant. In this example, the claimant is identified by a six-digit number. In the illustrated example, the patient named "NAME 6" is in the selected state.

[0043] The detailed display pane 50P displays more detailed attribute information about the claimant in the selected state in the claimant display pane 50O among the information included in the data acquired from the second database 32. In the illustrated example, the kana name and CID of the patient as the claimant are displayed. In the detailed display pane 50P, the date of birth, gender, information related to the transfer account used for settlement of the dispensing remuneration, etc. of the patient may be displayed.

[0044] The UI screen in the state illustrated in FIG. 7 includes a "Link" button image 50Q. When the "Link" button image 50Q is in the selected state, the UI screen transitions to the state illustrated in FIG. 8.

[0045] The UI screen in the state illustrated in FIG. 8 includes a verification dialog box 50R. In the verification dialog box 50R, the patient name obtained from the first database 31 and the patient name as the billing destination obtained from the second database 32 that has the same reading are displayed side by side in the same row. A check box is assigned to each row and is displayed in a selected state.

[0046] In the verification dialog box 50R, the patient name as the billing destination obtained from the second database 32, which has the same reading as the patient name obtained from the first database 31 but different notations, is also displayed side by side in the same row. A check box is also assigned to this row and is displayed in a non - selected state.

[0047] In this example, the fact of homophonic characters is pointed out for the patients of "NAME 5" and "NaME 5". This fact may be due to the case where "NAME 5" and "NaME 5" are different people with homophonic characters, or when there is a character encoding problem because the character standard used in the first database 31 does not conform to the character standard used in the second database 32 although they are the same person.

[0048] An example of the process performed by the processor 22 of the information processing apparatus 20 when displaying the verification dialog box 50R will be described with reference to FIG. 2.

[0049] First, the processor 22 identifies the first identification information ID1 assigned to a specific patient among the information obtained from the first database 31 (STEP3). In this example, the first identification information ID1 is the patient name and its reading (Kana name). For example, "NAME 1" and "ネーム イチ" are identified as the first identification information ID1 corresponding to the patient of "NAME 1".

[0050] Subsequently, the processor 22 determines whether there is second identification information ID2 that matches the first identification information ID1 among the information acquired from the second database 32 (STEP4). In this example, the second identification information ID2 is the patient name as the billing destination and its reading (Kana name). The matching of both patient names can be made, for example, by comparing the character codes assigned to the patient name. Similarly, the matching of both Kana names can be made, for example, by comparing the character codes assigned to the Kana name.

[0051] When there is second identification information ID2 that matches the first identification information ID1 (YES in STEP4), the processor 22 generates linking data LD (STEP5). Specifically, the linking data LD is generated by associating the information for creating the dispensing remuneration statement stored in association with the first identification information ID1 in the first database 31 with the second identification information ID2. A part of the linking data LD is used for display in the verification dialog box 50R in FIG. 8. That is, the patient name "NAME 1" and the patient name "NAME1" as the billing destination are associated and displayed together with the fact that both match (a checked checkbox in the selected state).

[0052] Subsequently, the processor 22 determines whether the collation with the second identification information ID2 has been made for all the first identification information ID1 acquired from the first database 31 (STEP6). When it is determined that the collation has been made for all the first identification information ID1 (YES in STEP6), the process ends. When it is determined that the collation has not been made for all the first identification information ID1 (NO in STEP6), the process returns to STEP3. For example, "ネーム ニ" is specified as the first identification information ID1 corresponding to the patient "NAME 2", and the same process is repeated.

[0053] When there is no second identification information ID2 that matches the first identification information ID1 (NO in STEP4), the processor 22 proceeds to STEP6 without generating the linking data LD.

[0054] As illustrated in FIG. 9, the collation dialog box 50R includes a "Registration" button image 50S. When the "Registration" button image 50S is selected, the UI screen transitions to the state illustrated in FIG. 10.

[0055] Comparing with the UI screen illustrated in FIG. 3, it can be seen that the display content of the patient display pane 50G has changed. Specifically, for the patient for whom the associated data LD has been generated, the character displayed in the "Classification" column has changed from "Unprocessed" to "Billed". In addition, information is entered in the "CID" column and the "Claim Amount" column which were blank in FIG. 3.

[0056] That is, the character "Unprocessed" displayed in the "Classification" column means that the associated data LD necessary for linking to the fee billing operation has not been generated. The character "Billed" means that the associated data LD has been generated and linking to the fee billing operation is possible.

[0057] As illustrated in FIG. 11, the UI screen includes a "Billing" button image 50T. When the "Billing" button image 50T is selected, the processor 22 of the information processing apparatus 20 outputs the associated data LD illustrated in FIG. 12 from the output interface 23 to the associated application 40 that executes the settlement agency service. The associated data LD output from the output interface 23 may be in, for example, the file format of CSV (Comma-Separated Value) according to the specifications of the associated application 40.

[0058] As described above, according to the information processing method according to the present exemplary embodiment, the information of the patients stored in the first database 31 related to the dispensing operation essential for the operation of the pharmacy can be effectively utilized, and the association with the information related to other services provided to the patients and the linking with the applications that execute the other services can be automated. Thereby, manual processing and the intervention of paper media can be reduced or made unnecessary, so that the operational efficiency of the pharmacy can be further improved.

[0059] In the dispensing pharmacy industry, in recent years, the sales of the top 10 companies only account for 15% of the total, and the industry has not seen a significant trend towards oligopoly. In other words, the dispensing pharmacy industry is mainly occupied by small and medium-sized pharmacies with low capital strength. This situation was one of the reasons why the reduction of manual processing and the intervention of paper media did not progress. Therefore, according to the information processing method according to the present embodiment, it is possible to significantly promote the efficiency of operations, especially in small and medium-sized pharmacies, and thus promote the activation of the dispensing pharmacy industry.

[0060] Especially when there is a connection with the billing operation as in the example of the present embodiment, the contribution to the efficiency of operations in the dispensing pharmacy providing home medical care is significant. The settlement of the remuneration related to home medical care tends to be requested to be debited by bank transfer rather than cash collection on-site. Since the information for creating the dispensing remuneration statement obtained from the first database 31 has a high affinity with the billing operation, it is easy to meet the said requirement.

[0061] As described with reference to FIG. 8, in the collation dialog box 50R, the patient names obtained from the second database 32, which have different notations but match in terms of the patient name and its reading obtained from the first database 31, are displayed side by side in the same row. The check boxes assigned to this row are displayed in an unselected state. FIG. 13 shows another example of the flow of the information processing method executed by the information processing apparatus 20 to realize this display mode. The same reference numerals are assigned to the processing elements that are substantially the same as those illustrated in FIG. 2, and repeated explanations are omitted.

[0062] In this example, when there is second identification information that does not exactly match but partially matches the first identification information ID1 (NO in STEP4), the processor 22 causes the display device 50 to display a notification of this fact as illustrated in FIG. 8. As a result, the user is requested to confirm whether the mismatch between the first identification information ID1 and the second identification information ID2 is acceptable (STEP7).

[0063] As described above, one of the reasons for the inconsistency is that, although "NAME 5" and "NaME 5" refer to the same person, character encoding used in the first database 31 may not match that used in the second database 32, resulting in character garbling.

[0064] Since the inconsistency in this case is acceptable, the user changes the checkbox, which is in a non - selected state in the matching dialog box 50R illustrated in FIG. 8, to a selected state. As illustrated in FIG. 14, when the "Register" button image 50S is selected in this state, the processor 22 of the information processing apparatus 20 determines that the inconsistency is allowed (YES in STEP7). The process proceeds to STEP5, and linkage data LD is generated for the patient "NAME 5". The UI screen transitions to the state illustrated in FIG. 15.

[0065] Comparing with the UI screen illustrated in FIG. 10, it can be seen that the information related to the patient name "NAME5" displayed in the patient display pane 50G is in a state where it can be linked to the billing operation.

[0066] That is, depending on the circumstances on the second database 32 side, it is possible to generate the linkage data LD without modifying the second identification information ID2. This can further improve the efficiency of business cooperation.

[0067] As another example of the reason for the mismatch between the first identification information ID1 and the second identification information ID2, it may be due to a typo input into the second database 32. Alternatively, the patient corresponding to the first identification information ID1 and the patient corresponding to the second identification information ID2 may be homophonic different people. In such a case, the user sets the "Cancel" button image 50U included in the collation dialog box illustrated in FIG. 8 to the selected state. The processor 22 determines that the mismatch is not allowed based on the operation (NO in STEP7). After taking measures such as setting a flag indicating that the collation has been performed for the first identification information ID1, the process proceeds to STEP6 without generating the association data LD.

[0068] For the first identification information, an appropriate UI (not shown) for correcting the second identification information ID2 or associating it with the correct second identification information ID2 is provided, and the collation process can be performed again as necessary.

[0069] As illustrated in FIG. 8, in the collation dialog box 50R, in addition to the name of the patient obtained from the first database 31, the date of birth of the patient is displayed. By displaying such auxiliary information for identifying the patient, it is possible to assist in determining whether the patient corresponding to the first identification information ID1 and the patient as the claimant corresponding to the second identification information ID2 are the same person. In addition to or instead of the date of birth, the gender of the patient may be displayed.

[0070] As illustrated in FIG. 13, after it is determined that the collation process has been performed for all the first identification information (YES in STEP6), the processor 22 may be configured to be able to change the association data LD.

[0071] In the fee billing operation, it is not always the case that the patient for whom the dispensing has been performed and the claimant of the dispensing fee match. For example, a patient's relative or the like may pay the dispensing fee. FIG. 16 illustrates a UI screen for changing the claimant of the dispensing fee in such a case.

[0072] For example, when a patient wishes to change the billing destination for "NAME 1", if the patient "NAME 1" displayed on the patient display pane 50G is selected and the option to change the billing destination is selected by appropriate operation input, a billing destination setting dialog box 50V will be displayed. That is, when the option to change the billing destination is selected, the processor 22 determines that a change in the second identification information ID2 is necessary (YES in STEP8 of FIG. 13).

[0073] The billing destination setting dialog box 50V includes a text box 50W for entering the CID after the change and a text box 50X for entering the name of the billed party after the change. By entering appropriate information in these text boxes and selecting the "Register" button image 50Y, the change in the second identification information ID2 is reflected (STEP9 of FIG. 13). The UI screen transitions to the state illustrated in FIG. 17. It can be seen that the CID of "NAME 1" in the patient display pane 50G has been changed to the one set using the billing destination setting dialog box 50V.

[0074] If the option to change the billing destination is not selected (NO in STEP8 of FIG. 13), the process ends.

[0075] According to such a configuration, it is possible to flexibly respond to the situation where the patient for whom the dispensing was done does not match the billed party for the dispensing fee. This effect is particularly remarkable in contributing to the efficiency of operations at a dispensing pharmacy that provides home medical care where such situations often occur.

[0076] As illustrated in FIG. 1, the input interface 21 of the information processing apparatus 20 may be configured to receive feedback FB from the associated application 40. For example, when the payment of the dispensing fee for a certain patient is not made by a predetermined due date, information including the patient and the outstanding amount may be fed back.

[0077] In this case, the processor 22 can be configured to refer to such information when generating the next associated data LD. When there is an outstanding amount for a certain patient, the processor 22 is configured to automatically add the outstanding amount to the next billing amount.

[0078] According to such a configuration, since the operation of calculating the billing amount considering the outstanding amount can be automated, the efficiency of the expense billing operation can be further improved.

[0079] The processor 22 of the information processing apparatus 20 having the various functions described so far is an example of an arithmetic unit. The processor 22 can be realized by a general-purpose microprocessor that operates in cooperation with a general-purpose memory. Examples of the general-purpose microprocessor may include a CPU, an MPU, and a GPU. Examples of the general-purpose memory may include a ROM and a RAM. In this case, a computer program for executing the above-described processing may be stored in the ROM. The ROM is an example of a non-transitory computer-readable medium in which a computer program is stored. The general-purpose microprocessor designates at least a part of the program stored on the ROM and expands it on the RAM, and executes the above-described processing in cooperation with the RAM. The computer program may be pre-installed in the general-purpose memory, or may be downloaded from an external server device via a communication network and then installed in the general-purpose memory. In this case, the external server device is an example of a non-transitory computer-readable medium in which a computer program is stored.

[0080] The processor 22 may also be realized by an application-specific integrated circuit capable of executing the above computer program, such as a microcontroller, an ASIC, or an FPGA. In this case, the computer program is pre-installed in the storage element included in the application-specific integrated circuit. The storage element is an example of a computer-readable medium in which a computer program is stored. The processor 22 can also be realized by a combination of a general-purpose microprocessor and an application-specific integrated circuit.

[0081] Each configuration described so far is merely an example for facilitating the understanding of the present disclosure. Each configuration example can be appropriately modified or combined with other configuration examples without departing from the spirit of the present disclosure.

[0082] The associated destination application 40 to which the association data LD is passed is not limited to those for performing the agency settlement service. In addition to or instead of the agency settlement service, the associated destination application 40 can be for performing the invoice sending service. The invoice sending service is a service of sending invoices such as receipts, dispensing remuneration statements, and documents with contact matters to a predetermined destination.

[0083] In this case, the second database 32 is configured to store information related to the invoice sending service. The information includes second identification information ID2 associated with the patient name as the destination of the invoice.

[0084] Similar to the embodiment example related to the fee billing service, the processor 22 of the information processing apparatus 20 identifies the first identification information ID1 assigned to a specific patient among the information acquired from the first database 31 through the input interface 21. Subsequently, the processor 22 determines whether there is second identification information ID2 that matches the first identification information ID1 among the information acquired from the second database 32 through the input interface 21.

[0085] When there is second identification information ID2 that matches the first identification information ID1, the processor 22 generates the association data LD. Specifically, the association data LD is generated by associating the information for creating the dispensing remuneration statement stored in association with the patient name corresponding to the first identification information ID1 in the first database 31 with the second identification information ID2 corresponding to the patient name as the destination of the invoice. The generated association data is output from the output interface 23 to the associated destination application 40 that performs the invoice sending service.

[0086] The information for creating the dispensing remuneration statement obtained from the first database 31 has a high affinity with the invoice sending operation, so the connection with this operation can be smoothed.

[0087] In the invoice sending operation, the patient who has received the dispensing and the recipient of the invoice do not always match. For example, the patient's relatives or guardians may receive the invoice. Even in this case, the destination of the invoice can be changed through the same UI screen as illustrated in FIG. 16.

[0088] According to such a configuration, it is possible to flexibly respond to the situation where the patient who has received the dispensing and the recipient of the invoice do not match. This effect is particularly remarkable in contributing to the efficiency improvement of the operations in a dispensing pharmacy that conducts home medical care where such situations often occur.

[0089] In addition to or instead of the settlement agency operation and the invoice sending operation, an appropriate operation that handles information with a high affinity to the information related to the dispensing operation can be selected as the associated party. Examples of such operations include the pharmacy's management analysis operation, the support operation for home medical care, and the like.

[0090] In the above embodiment example, the information related to the dispensing operation performed at a specific pharmacy (Pharmacy A) is stored in the first database 31. However, the information related to the dispensing operations performed at multiple pharmacies may be stored in the first database 31. In this case, the desired pharmacy can be specified through the text box 50Z included in the dialog box 50D illustrated in FIG. 4.

[0091] Note that information related to another pharmacy may be stored in the first database 31 at the pharmacy where the information processing device 20 is installed, or information related to another pharmacy may be obtained from the first database 31 installed at another pharmacy via a communication network.

[0092] The configurations listed below also constitute a part of the present disclosure. Item 1: An information processing method executed by at least one arithmetic unit, comprising: identifying first identification information associated with a patient name registered in a first database related to a dispensing operation; identifying second identification information registered in a second database related to an operation different from the dispensing operation; when the first identification information matches the second identification information, generating association data in which the information stored in association with the patient name in the first database is associated with the second identification information; An information processing method. Item 2: The different operation is a billing operation, The second identification information is information for identifying a billing destination, The information associated with the second identification information includes information for creating a dispensing remuneration statement. The information processing method according to Item 1. Item 3: generating the association data with reference to information indicating whether payment has been made from the billing destination; The information processing method according to Item 2. Item 4: The different operation is a document sending operation, The second identification information is information for identifying a document sending destination, The information associated with the second identification information includes information for creating a dispensing remuneration statement. The information processing method according to Item 1. Item 5: The second identification information can be changed after the generation of the association data. The information processing method according to any one of Items 1 to 4. Item 6: When the first identification information and the second identification information do not match, confirm with the user whether to allow the mismatch. When confirmation is obtained that the inconsistency is acceptable, generate the associated data while maintaining the second identification information. The information processing method according to any one of items 1 to 5.

Description of symbols

[0093] 20: Information processing apparatus, 21: Input interface, 22: Processor, 31: First database, 32: Second database, ID1: First identification information, ID2: Second identification information, LD: Associated data

Claims

1. An information processing method executed by at least one computing device, comprising: identifying first identification information associated with a patient name registered in a first database related to a dispensing operation; identifying second identification information registered in a second database related to an operation different from the dispensing operation; when the first identification information and the second identification information match, generating association data in which the information stored in association with the patient name in the first database is associated with the second identification information; An information processing method.

2. wherein the different operation is a billing operation, the second identification information is information for identifying a billing destination, and the information associated with the second identification information includes information for creating a dispensing remuneration statement; The information processing method according to claim 1.

3. generating the association data with reference to information indicating whether payment has been made from the billing destination; The information processing method according to claim 2.

4. wherein the different operation is a document sending operation, the second identification information is information for identifying a document sending destination, and the information associated with the second identification information includes information for creating a dispensing remuneration statement; The information processing method according to claim 1.

5. the second identification information can be changed after the generation of the association data; The information processing method according to claim 1.

6. when the first identification information and the second identification information do not match, asking the user to confirm whether to allow the mismatch, and when confirmation is obtained that the mismatch is allowed, generating the association data while maintaining the second identification information; The information processing method according to claim 1.

7. an interface for receiving first identification information associated with a patient name registered in a first database related to a dispensing operation and second identification information registered in a second database related to an operation different from the dispensing operation; a processor that, when the first identification information and the second identification information match, generates association data in which the information stored in association with the patient name in the first database is associated with the second identification information; An information processing apparatus comprising the same.

8. A computer program executable by a processor mounted on an information processing apparatus, which, when executed, causes the information processing apparatus to: ​ ​ Identify first identification information associated with a patient name registered in a first database related to a dispensing operation, Identify second identification information registered in a second database related to an operation different from the dispensing operation, When the first identification information matches the second identification information, generate linkage data in which the information stored in association with the patient name in the first database is associated with the second identification information, A computer program.

Images