JP2010055338A - Acceptance processing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an acceptance processing system, capable of preventing any trouble caused by a person to be accepted in a waiting room. <P>SOLUTION: By means of an imaging camera 37, a server 23 images patient appearance whose acceptance is completed, and preserves it into an individual master database 27, as an image data. Also, the server 23 monitors a patient state in the waiting room by a monitoring camera 38, and displays the monitored image on each screen of a first PC 40 and a second PC 41 via a LAN 39, together with a list of accepted persons. When a particular patient is specified from the list via the screen of the first PC 40, the patient appearance image of the day and problem information proper to the patient are displayed on the screen. By this, the state of the particular patient in the waiting room can easily be grasped, enabling prevention of trouble. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a reception processing system, and more particularly to a reception processing system for visiting patients in a hospital or the like.

  2. Description of the Related Art Conventionally, a hospital reception system has been proposed that accepts examinations and prescriptions issued via a communication line (Patent Document 1). According to this, it is said that the patient can easily accept at the hospital, and the waiting time can be shortened even when the examination is accepted, for example, immediately before the examination.

Furthermore, a waiting time management system that can effectively use a waiting time until a user of a facility such as a patient in a hospital actually uses the facility has been proposed (Patent Document 2). According to this, in order to be able to spend a waiting time at a place outside the facility, these places are introduced. When the time for using the facility approaches, an e-mail to that effect is sent to the user.
JP 2005-339309 A JP 2006-079208 A

  In the conventional reception system as described above, even though the waiting time can be shortened or the waiting time can be effectively utilized, it is not actually a countermeasure for people waiting in the waiting room. In reality, there are an increasing number of troubles caused by patients who have been waiting for a long time and patients such as Kramer.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a reception processing system capable of preventing a trouble caused by a person to be received in a waiting room.

  In order to achieve the above object, the invention described in claim 1 is a reception processing system in a hospital or the like, and includes information display means capable of displaying various characters, images, etc., and information for each recipient. Information storage means for storing information, waiting room photographing means for photographing the situation of the waiting room where the recipients wait, situation control means for displaying the photographed waiting room situation on a part of the information display means, and the recipient List control means for displaying the list of information on the other part of the information display means, a recipient designation means for designating a desired recipient from the displayed list, and information on the designated recipient information is saved Information control means for reading out from the means and displaying the information on another part of the information display means.

  If comprised in this way, the condition of a waiting room and the information of a desired recipient will be displayed simultaneously.

  According to a second aspect of the present invention, in the configuration of the first aspect of the invention, the information on the recipient includes a photographed image obtained by photographing the appearance at the time of acceptance of the recipient.

  If comprised in this way, identification of the to-be-received person in a waiting room will become easy.

  According to a third aspect of the invention, in the configuration of the first or second aspect of the invention, the list includes a waiting time for each recipient, and the list control means has a waiting time equal to or longer than a predetermined time. The display state of the received person is controlled to change.

  If comprised in this way, it will become easy to confirm the to-be-received person whose waiting time is long.

  According to a fourth aspect of the present invention, in the configuration of the invention according to any one of the first to third aspects of the present invention, the invention further comprises data input means capable of inputting desired data for each recipient as information. At least a part of the data is displayed as part of the list.

  If comprised in this way, the specific data for every recipient will be displayed on a list.

  According to a fifth aspect of the present invention, in the configuration of the fourth aspect of the invention, the input data is displayed in a list as a plurality of color information according to the contents.

  With this configuration, visually unique data is grasped.

  The invention according to claim 6 is the configuration of the invention according to any one of claims 1 to 5, wherein the recipient includes a patient who has come to a hospital or the like, and the information is obtained by photographing the present state of the insurance card. The presentation image obtained in this way and the return image obtained by photographing the return state of the insurance card are included.

  If comprised in this way, the state of presentation and return of an insurance card will be preserve | saved as an image.

  As described above, according to the first aspect of the present invention, since the status of the waiting room and the desired recipient information are displayed at the same time, it is possible to appropriately cope with the recipient who is likely to be a problem. Become.

  In addition to the effect of the invention described in claim 1, the invention described in claim 2 makes it easier to identify the recipient in the waiting room, so that a more appropriate response can be made to the recipient.

  In addition to the effect of the invention of claim 1 or claim 2, the invention described in claim 3 facilitates confirmation of a recipient who has a long waiting time. Can be prevented in advance.

  In addition to the effects of the invention according to any one of claims 1 to 3, the invention described in claim 4 displays specific data for each recipient in the list, so Detailed response is possible.

  According to the fifth aspect of the invention, in addition to the effect of the fourth aspect of the invention, since the specific data is visually grasped, the possibility of oversight or the like is reduced.

  In addition to the effects of the invention according to any one of claims 1 to 5, the invention according to claim 6 reduces the trouble related to the insurance card because the state of presenting and returning the insurance card is stored as an image. can do.

  FIG. 1 is a block diagram showing a schematic configuration of a reception processing system according to the first embodiment of the present invention.

  Referring to the figure, for example, a reception processing system 21 installed in a hospital is configured with a server 23 as a center. The server 23 includes an input device 24 (data input means) such as a mouse and a keyboard, and various characters and images. A display device 25 serving as a display for displaying the information and the like and a database 26 for storing various information are connected. These configurations are performed using the personal computer (PC) 31 in this embodiment, but may be used by combining independent devices. As will be described later, the database 26 includes a personal master database 27 in which data for each recipient is stored, a reception status database 28 in which information on reception on the day is stored, a congestion status on the day, and the like. A waiting situation database 29 in which information is stored is included, and these constitute information storage means.

  On the other hand, in order to read the information on the presented examination ticket, the server 23 issues a ticketing machine 33 for issuing a receipt number tag, a display machine 34 installed in a waiting room for displaying the congestion status of the day, and the like. The reader 35 is connected. Further, the server 23 is installed in the reception room, and a camera 37 for photographing the appearance of the person to be accepted on the day and the state of delivery of the insurance card, and the monitoring for photographing the state of the waiting room and grasping the situation thereof A camera 38 (waiting room photographing means) is connected.

  Each room in the hospital is connected by a LAN 39, and a first PC 40 and a second PC 41 installed in each room different from the server 23 are connected via the LAN 39. Each of the first PC 40 and the second PC 41 is connected to a display device such as a liquid crystal display that can display various characters, images, and the like, and an input device such as a mouse and a keyboard. This display device constitutes an information display means, and the input device constitutes a recipient designation means for designating a particular recipient for the recipient list displayed on the display device.

  The reception processing system is controlled mainly by the server 23. That is, information such as the recipient is stored in various databases, and the information is read according to the request and displayed on a display device or the like. Specifically, the server 23 becomes a status control unit that displays the status of the waiting room photographed by the monitoring camera 38 on a part of the information display unit, and the list of recipients is made another part of the information display unit. It becomes a list control means to be displayed. Further, the information control means is configured to read out the information of the recipient who is designated from the displayed list from the information storage means and display it on another part of the information display means.

  FIG. 2 is a plan view showing a specific arrangement of the hospital in which the reception processing system shown in FIG. 1 is installed.

  Referring to the figure, hospital 43 has a reception room 44 for receiving patients (recipients), a staff room 45 for managing hospital affairs, etc., and an examination room in which doctors and the like who perform actual examinations reside. 46 and a waiting room 47 for waiting until the visiting patient is called.

  In this embodiment, the personal computer 31 having the server function shown in FIG. 1 is installed in the reception room 44, and the ticket issuing machine 33 and the reader 35 are installed near the window 48. Further, the reception room 44 is provided with a photographing camera 37 for photographing the appearance and the like of the person who is to be accepted through the window 48 on the day. Each of the staff room 45 and the examination room 46 is provided with a first PC 40 and a second PC 41 connected to the personal computer 31 via the LAN 39 shown in FIG.

  On the other hand, the waiting room 47 is provided with a display 34 for a receptionist waiting for a call to check the waiting time or the like. The waiting room 47 is provided with a monitoring camera 38 for photographing the status of the waiting recipient.

  FIG. 3 is a diagram showing a schematic content of the personal master database shown in FIG.

  Referring to the figure, personal master database 27 stores various types of information for each recipient. Specifically, the presence / absence of a reservation, an examination ticket number, and an insurance card number are stored in correspondence with the name and address. If there is caution information for the recipient, the contents are also stored. Specifically, it is judged by whether or not acts such as rants and violence have occurred in the past. If there is an unpaid amount, the amount is stored.

  And the appearance image of the day image | photographed with the imaging camera 37 shown in FIG. 1 is stored via the file name. When the insurance card is presented, a flag indicating whether or not the insurance card is present is stored. At the same time, an image handling the insurance card and a returned image are stored via the file name. Furthermore, a color information flag for indicating information such as the previous trouble is stored as information unique to the recipient. The color information flag is configured so that “1” corresponds to red, “2” corresponds to yellow, and “0” corresponds to white depending on the size of the color information flag.

  FIG. 4 is a schematic diagram showing specific contents of the reception status database shown in FIG.

  Referring to the figure, reception status database 28 is set and stored as a data group of one group every time reception is performed. Specifically, the reception number is stored as a continuous numerical value, and the examination ticket number corresponding to this is stored. In addition, the reception time, call time, and end time for the reception are stored. Furthermore, a status flag corresponding to the reception status is stored. Specifically, “0” indicates reception, “1” corresponds to the call, and “2” corresponds to the end of the examination. Furthermore, the color information flag stored in the personal master database corresponding to the examination ticket number is also stored in the reception status database 28 with the same contents.

  FIG. 5 is a schematic diagram showing specific contents stored in the waiting situation database shown in FIG.

  Referring to the figure, in the waiting situation database 29, it is set and stored as one data group as a whole. Specifically, the ticket issue number issued at that time is stored, and this number is incremented by one for each reception. Further, the reservation waiting status is stored as character information, and a specific reservation waiting delay time is also stored. At that time, the first and last numerical values of the number that has been called are stored, and the waiting number and waiting delay time are also stored.

  FIG. 6 is a flowchart showing a specific main operation performed by the server shown in FIG.

  Referring to the figure, the screen as shown in FIG. 14 is usually displayed on the display device 25 of FIG. Each operation is performed by performing various requested operations on this screen. For example, when a reception operation is selected as the request operation in step S50, a reception operation process as described later is performed (S51). Similarly, when a call operation is performed, an operation related to the call is performed (S52). Similarly, when the operation for ending the examination is selected, an operation relating to the completion of the examination is performed (S53). Similarly, when an information input operation is selected, an operation related to information input is performed (S54). Further, similarly, when the operation for resetting the waiting situation is selected, the processing of the operation relating to the waiting situation setting is performed (S55). In the screen shown in FIG. 14, when the requested operation is not selected, the operation relating to the screen re-display is automatically performed (S56).

  FIG. 7 is a flowchart showing specific contents of the receiving operation (S51) shown in FIG.

  Referring to the figure, when the accepting operation is selected, it is first determined whether or not the recipient is a revisited patient (S60). In the case of reexamination (YES in S60), since the examination ticket has already been issued, the number is read by the reader 35 in response to the presentation of the examination ticket (S61), and the flow proceeds to step S63. On the other hand, if the patient is the first visit (NO in S60), after issuing the examination ticket, the number issuing button is pushed down by clicking with the mouse or the like on the main screen 75 in FIG. Proceed to S63.

  Next, it may be necessary to present an insurance card when the month changes even in the case of the first visit or revisit. Therefore, it is determined whether or not it is not necessary to present an insurance card for the visit on the day (S63). When it is necessary to present an insurance card (NO in S63), the insurance card receipt button is pushed down on the main screen 75 of FIG. 14 (S64). In response to this, an image in a state where the insurance card is received is taken by the photographing camera 37 of FIG. 1, and this image information is stored in the personal master database 27 (S65). Then, the insurance card receipt flag is set to ON and stored in the personal master database 27 (S66), and the process proceeds to step S67.

  On the other hand, if it is not necessary to present an insurance card (YES in S63), the process proceeds to step S67. Then, the ticket issue number information is obtained from the waiting situation database 29, the reception number is assigned, and the result is stored in the waiting situation database 29 (S67). The numbered reception number is printed by the ticket issuing machine 33 in FIG. 1 and issued to the patient (S68).

  Since the reception for one patient is processed in this way, “0”, the reception time, the reception number, and the examination ticket number are stored in the reception status database 28 as a status flag, and the personal master database corresponding to this patient The color information flag is acquired from 27 and set in the reception status database 28 (S69).

  Along with this reception process, the patient's appearance image at that time is taken by the photographing camera 37 and stored in the personal master database 27 (S70). As the number of persons accepted increases in this way, the waiting situation is recalculated and stored in the waiting situation database 29 (S71). Then, the patient's name is acquired from the personal master database 27, and the stored data in the reception status database 28 is displayed again on the screen of the receptionist list on the main screen 75 in FIG. 14 (S72).

  Then, the changed information of the waiting situation database 29 is re-displayed on the screen on the left side of the main screen 75 in FIG. 14 and the waiting situation screen in the waiting situation screen 76 shown in FIG. 15 (S73).

  FIG. 8 is a flowchart showing specific contents of the calling operation (S52) shown in FIG.

  Referring to the figure, in order to select the call operation, first, the call button is pushed down on the screen of the main screen 75 of FIG. 14 (S80). Next, the user is selected by clicking the corresponding person to be called from the acceptor list on the main screen 75 (S81). Next, an execution button (not shown) on the main screen 75 is depressed (S82). Then, “1” is set as the status flag, and the call time is stored in the reception status database 28 (S83). Based on the stored data in the reception status database 28, the screen of the receiver list on the main screen 75 is displayed again (S84).

  Since the waiting number changes due to the call, the waiting situation is recalculated, and the result is stored in the waiting situation database 29 (S85). Based on the data stored in the waiting status database 29, the contents of the waiting status change are redisplayed on the screen on the left side of the main screen 75 and the screen shown in FIG. 15 (S86).

  FIG. 9 is a flowchart showing the specific contents of the examination ending operation (S53) shown in FIG.

  Referring to the figure, when the examination of a certain patient is completed, first, the examination end button is pushed down on the screen of the main screen 75 in FIG. 14 (S90). Next, a patient who has been examined is selected from the list of recipients on the main screen 75 (S91). Next, it is confirmed whether the insurance card receipt flag is ON or OFF. The contents of the receipt flag are not shown, but are assumed to be shown for each patient in the acceptor list on the main screen 75 of FIG.

  Therefore, if the insurance card receipt flag is ON, it is necessary to return the insurance card, so the insurance card return button is pressed on the main screen 75 (S93). In response to this, an image of the insurance card returned is taken and stored in the personal master database 27 (S94). Then, after setting the insurance card receipt flag to OFF and setting it in the personal master database 27, "2" is set in the reception status database 28 as a status flag indicating the end of the examination (S96).

  On the other hand, when the insurance card receipt flag is OFF, since the insurance card return operation is not required, only the status flag “2” is set to the reception status database 28 (S96). Then, the end time is stored in the reception status database 28 based on the data of the personal master database 27 corresponding to the corresponding person, and the contents obtained by deleting the corresponding person from the reception person list on the main screen 75 are redisplayed (S97).

  Next, since the waiting situation has changed with the completion of the examination, this is recalculated and the contents are stored in the waiting situation database 29 (S98). Based on the data stored in the wait status database 29, the wait status screen is redisplayed on the left screen of the main screen 75 and the wait status screen 76 in FIG. 15 (S99).

  FIG. 10 is a flowchart showing specific contents of the information input operation (S54) shown in FIG.

  In order to select the information input operation, the information transmission button is pushed down on the screen of the main screen 75 of FIG. 14 (S110). Next, a patient whose information is to be input is selected from the list of recipients on the main screen 75, and the name portion is double-clicked (S111). Then, the screen of the detailed screen 77 shown in FIG. 16 reflecting the personal data stored in the personal master database 27 is displayed (S112). After editing each content such as additional update on this screen (S113), the information update button on the detail screen 77 is pushed down (S114). As a result, the edited input content is updated, the content is stored in the personal master database 27, the process returns to the main screen 75 (S115), and the flow proceeds to step S117.

  On the other hand, when the color information portion is clicked from the acceptor list after the information transmission button is pressed in S110, the displayed color information changes from red to yellow, yellow to white, and white to red. (S116). After changing to the desired color information, it is determined whether or not an execution button (not shown) on the main screen 75 has been pressed (S117). If the execution button has not been depressed, the flow returns to step S111, but if the execution button has been depressed (YES in S117), the color information flag is updated and the personal master database 27 and the reception status database are updated. 28 (S118). The data stored in the personal master database 27 is reflected in the reception status database 28, and the result is re-displayed as a screen of the receiver list on the main screen 75 (S119). In the display example of FIG. 14, the three columns to the right of the waiting time column are items for displaying this color information, and one yellow information is displayed for the patient “Jimtaro”. Two red information items are displayed for the patient “Bentengorou”.

  FIG. 11 is a flowchart showing specific contents of the waiting state setting operation (S55) shown in FIG.

  Referring to the figure, in order to select the waiting state setting operation, the operation setting button is pushed down on the main screen 75 of FIG. 14 (S120). Then, the congestion status is set on the main screen 75, and this content is stored in the waiting status database 29 (S121). Next, it is determined whether or not an execution button (not shown) has been pressed on the main screen 75 (S123). If the execution button is not pressed down, the flow returns to S121, but if the execution button is pressed down (YES in S123), a screen showing the congestion status based on the data stored in the waiting status database 29 Is displayed again (S124).

  FIG. 12 is a flowchart showing specific contents of the screen redisplay operation (S56) shown in FIG.

  Referring to the figure, as shown in FIG. 6, when the requested action is not particularly selected, this flow is automatically entered. First, a waiting time is calculated as a difference between the current time and the reception time of each patient displayed in the reception list (S130). When this waiting time is within the set time, there is no particular change, but when it is longer than the set time, the color information of the waiting time item of the patient is changed (S132). Then, the waiting time color information in the acceptor list shown on the main screen 75 of FIG. 14 is redisplayed. Specifically, when the waiting time is less than the predetermined time, the color of the waiting time item does not change, but when the waiting time becomes equal to or longer than the set time, the color of the waiting time item is changed to the content changed in S132. It will change. This makes it possible to visually recognize a patient who has been waiting for a long time.

  In the display example of FIG. 14, since the waiting time of the patient “Narita Takayoshi” is equal to or longer than the set time, the color of the waiting time item is displayed in red, which is a situation in which attention is urged. Depending on the situation, the above-mentioned other color information may also be displayed in red or yellow at the same time for one patient. In this case, particularly urgent treatment is urged for the patient.

  FIG. 13 is a flowchart specifically showing the processing contents in each of the first PC 40 and the second PC 41 shown in FIG.

  Referring to the figure, in these PCs, the contents of the monitoring screen 78 shown in FIG. 17 are always displayed. Specifically, a list of recipients is displayed (S140), and a screen showing the status of the waiting room taken by the monitoring camera 38 of FIG. 1 is displayed on the upper left side of the monitoring screen 78 (S141). . Thereby, in the staff room 45 and the examination room 46 in FIG. 2, it is possible to simultaneously grasp the waiting state of the patient and the state of the waiting room. In addition, as described above, color information indicating the length of the waiting time, a problem specific to the patient, and the like are also displayed in the receptionist list. This allows staff and doctors to know which patients are likely to have problems.

  Therefore, when a specific recipient is designated from the recipient list on the monitoring screen 78 (YES in S142), the designated recipient details screen 77 is also displayed as shown in FIG. 18 (S143). The receptionist list, waiting room status, receptionist information, and the like are stored in the first PC 40 and the second PC 41 via the LAN 39 as shown in FIG. 1 under the control of the server 23 based on the data stored in the database 26. Has been sent to. Accordingly, real-time information can be grasped also in the staff room 45 and the examination room 46.

  As shown in FIG. 18, the detailed screen 77 also displays an image that captures the appearance of the receptionist on the day. This makes it possible to easily identify the recipient from the image showing the state of the waiting room and judge the situation. And since the staff and doctor can respond individually according to the trend of the receptionist in the waiting room, it becomes possible to prevent troubles and the like.

  When the detailed screen 77 is deleted from the situation shown in FIG. 18, the display may be deleted by depressing the close button shown on the detailed screen 77 (S144). Then, the screen of the detailed screen 77 is deleted (S145), and the flow returns to S140. Accordingly, when it is desired to confirm information of other recipients, the corresponding person may be selected from the list in the same manner. As a result, while confirming the list of recipients, patients who are likely to have problems can be freely and specifically confirmed visually, and troubles can be prevented.

  In the above-described embodiment, the reception processing system has a patient in the hospital as a person to be received. However, the present invention can be similarly applied to other facilities that require reception and calling, and has similar effects.

  In the above embodiment, the server and the PC are connected via the LAN. However, the system may not be a PC. In this case, as the information display means, instead of the PC display device, the display device 25 connected to the server may be associated by switching the screen.

  Furthermore, in the above-described embodiment, a list, a button, or the like on the displayed screen is specified by a mouse or the like. However, if the display device is a touch panel type, usability is further improved.

  Further, in the above embodiment, the elapse of the waiting time and the information specific to the recipient are displayed as color information, but the information is blinked instead of the color information, or the color information itself is blinked. Anyway.

  Furthermore, in the above-described embodiment, two images of the insurance card presentation status and the return status are stored. However, only the most recent image may be stored.

1 is a block diagram showing a schematic configuration of a reception processing system according to a first embodiment of the present invention. FIG. 2 is a layout diagram of a hospital showing a situation where the reception processing system shown in FIG. 1 is specifically applied. It is the schematic which showed the specific content of the personal master database shown in FIG. It is the schematic which showed the specific content of the reception status database shown in FIG. It is the schematic which showed the specific content of the waiting condition database shown in FIG. 2 is a flowchart showing a main operation of the server shown in FIG. 1. It is the flowchart which showed the specific content of the reception operation | movement shown in FIG. It is the flowchart which showed the specific content of the calling operation | movement shown in FIG. It is the flowchart which showed the specific content of the medical examination end operation | movement shown in FIG. It is the flowchart which showed the specific content of the information input operation | movement shown in FIG. It is the flowchart which showed the specific content of the waiting condition setting operation | movement shown in FIG. It is the flowchart which showed the specific content of the screen redisplay operation | movement shown in FIG. It is the flowchart which showed the specific operation content of 1st PC or 2nd PC shown in FIG. It is the schematic which showed the specific content of the main screen which appears on the display apparatus 25 of FIG. It is the schematic which showed the specific content of the waiting condition screen which appears on the indicator 34 of FIG. It is the schematic which showed the content of the detailed screen which shows the information of each to-be-received person who appears on the display apparatus 25 of FIG. It is the schematic which showed the specific content of the monitoring screen which appears on the screen of 1st PC or 2nd PC shown in FIG. It is the schematic which showed the specific content which appears when a specific recipient is designated from the screen state of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 21 ... Reception processing system 23 ... Server 24 ... Input device 25 ... Display screen 26 ... Database 27 ... Personal master database 28 ... Reception status database 29 ... Waiting status database 37 ... Shooting camera 38 ... Surveillance camera 39 ... LAN
40 ... 1st PC
41 ... 2nd PC
43 ... Hospital 44 ... Reception room 45 ... Staff room 47 ... Waiting room 75 ... Main screen 77 ... Detailed screen 78 ... Monitoring screen In addition, the same code | symbol in each figure shows the same or an equivalent part.

Claims (6)

A reception processing system in a hospital or the like,
Information display means capable of displaying various characters, images, etc .;
Information storage means for storing information for each recipient,
Waiting room photographing means for photographing the situation of the waiting room where the recipients wait,
Status control means for displaying the captured status of the waiting room on a part of the information display means;
List control means for displaying a list of recipients on another part of the information display means;
A recipient designation means for designating a desired recipient from the displayed list;
An acceptance processing system comprising: information control means for reading the designated recipient information from the information storage means and displaying the information on another part of the information display means.   The reception processing system according to claim 1, wherein the information on the recipient includes a photographed image obtained by photographing the appearance at the time of acceptance of the recipient. The list includes the waiting time for each recipient,
The reception processing system according to claim 1, wherein the list control unit performs control so that a display state of a receptionee whose waiting time is equal to or longer than a predetermined time is changed. The information further comprises data input means capable of inputting predetermined data for each recipient.
The reception processing system according to claim 1, wherein at least a part of the input data is displayed as a part of the list.   The reception processing system according to claim 4, wherein the input data is displayed in the list as a plurality of color information according to the contents. The recipient includes patients who have come to hospitals,
The said information contains the presentation image obtained by image | photographing the presentation state of a health insurance card, and the return image obtained by imaging | photographing the return status of a health insurance card. Reception processing system.