JP2010224741A - Medical examination appointment receiving method, system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To accurately manage appointment information from the outside of a medical facility without manual operation. <P>SOLUTION: A CPU 36 of an internal server 17 installed in a central hospital 11 functions as an appointment receiving processing part 17a and a DB (database) access part 17b. When receiving appointment information from a clinic terminal 24 by the appointment receiving processing part 17a, the DB access part 17b retrieves, from a patient information DB 19, patient basic information 30 coinciding with patient basic information 30 attached to the appointment information. In finding the coincident patient basic information 30, the DB access part attaches a patient ID of the patient basic information 30 to the appointment information and registers it in an internal appointment information DB 18. In not finding the coincident patient basic information, the DB access part 17b attaches a patient ID issued anew by the appointment receiving processing part 17a, to the appointment information and registers it in the internal appointment information DB 18. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a medical examination reservation receiving method and system for receiving medical examination reservation information through a network, and a program.

  Recently, there is an increasing need to strengthen medical cooperation between medical facilities in the region. As part of this, a medical examination request is received from a relatively small medical facility such as a clinic, and a relatively large medical facility with advanced medical examination equipment such as a core hospital in the region conducts the medical examination. To be done. Patent Document 1 discloses an examination reservation system that can make online reservations for medical examinations between medical facilities via a data center that provides such medical cooperation services.

JP 2005-301434 A

  The medical facility uniquely issues a patient ID for uniquely identifying a patient in order to facilitate management of patient information. Of course, examination reservation information is also managed by the patient ID. However, the patient ID is valid only at the issued medical facility, and the data center does not have the patient ID of each medical facility as information. Accordingly, the information on the examination reservation from the clinic is not, of course, attached with the patient ID of the core hospital to which the examination reservation is requested.

  Because of this situation, the core hospital needs to check whether the patient is a new patient or a new patient who has previously issued a patient ID when accepting an examination appointment from a clinic. It was. In addition, if there is a human error and a new patient is mistaken for a new patient, there is a trouble of issuing a new patient ID to a patient who already has a patient ID, and the patient information cannot be managed correctly. In addition, the site may be confused.

  The present invention has been made in view of the above background, and an object of the present invention is to correctly manage reservation information from outside the medical facility without manpower.

  In order to achieve the above object, the medical examination reservation reception system of the present invention includes a hospital server for receiving medical examination reservation information addressed to a medical facility including basic patient information necessary for identifying a patient from outside the medical facility; A patient information database for storing received reservation information, and a patient information database for storing patient basic information in a medical facility, wherein the in-hospital server matches patient basic information attached to the reservation information. Is searched from the patient information database, and reservation information is registered in the reservation information database according to the search result.

  The patient information database stores basic patient information for each patient ID for uniquely identifying a patient. When the patient basic information matching the patient basic information attached to the reservation information is found in the patient information database, the in-hospital server adds the patient ID of the patient basic information to the reservation information and registers it in the reservation information database To do. On the other hand, when the patient basic information that matches the patient basic information attached to the reservation information is not found in the patient information database, a new patient ID is issued, and the patient ID is added to the reservation information to the reservation information database. Register with.

  Further, the in-hospital server registers the basic patient information attached to the reservation information with the newly issued patient ID in the patient information database.

  The in-hospital server receives reservation information via a center server of a data center outside the medical facility. When the in-hospital server receives the reservation information via the center server, the in-hospital server transmits the patient ID information registered in the reservation information database attached to the reservation information to the center server. The hospital server creates and distributes screen information representing a list of search results for each reservation information.

  The basic patient information includes at least information indicating the patient name, sex, and age. The information representing the age may be the age number itself or the date of birth.

  The medical examination reservation acceptance method of the present invention includes a reception step for accepting medical examination reservation information addressed to a medical facility including patient basic information necessary for identifying a patient from outside the medical facility, and basic patient information in the medical facility. A search step for searching patient basic information that matches the basic patient information attached to the reservation information from the patient information database storing the information, and information for registering the reservation information in the reservation information database according to the search result of the search step And a registration step.

  The medical examination reservation acceptance program of the present invention includes a reception step for accepting medical examination reservation information addressed to a medical facility including patient basic information necessary for identifying a patient from outside the medical facility, and basic patient information in the medical facility. A search step for searching patient basic information that matches the basic patient information attached to the reservation information from the patient information database storing the information, and information for registering the reservation information in the reservation information database according to the search result of the search step The registration step is executed by a computer.

  According to the present invention, it is searched whether the basic patient information attached to the reservation information received from outside the medical facility matches the basic patient information stored in the patient information database, and according to the search result. Since reservation information is registered in the reservation information database, reservation information from outside the medical facility can be correctly managed without manpower.

It is a block diagram which shows the outline of the reservation reception system of a medical examination. It is explanatory drawing which shows the content of the reservation information from a clinic. It is explanatory drawing which shows the content of patient information and in-hospital reservation information. It is a figure which shows the basic composition of a hospital, a clinic terminal, a hospital, a center, and a relay server. It is a figure which shows the function part constructed | assembled in CPU of a hospital and a center server. It is explanatory drawing which shows the process of the function part of the hospital server when the search result of patient basic information corresponds. It is explanatory drawing which shows the process of the function part of the hospital server when the search result of patient basic information is inconsistent. It is a flowchart which shows the process sequence of the hospital server. It is explanatory drawing which shows the example which attaches patient ID to the reservation completion notification. It is explanatory drawing which shows the example which produces and distributes the list screen information of a search result.

  In FIG. 1, a reservation reception system 2 connects a data center 10 and computer systems installed in a plurality of medical facilities via a communication network, and receives reservations for medical examinations online. The data center 10 connects computers of a plurality of medical facilities through a network and provides an online reservation service.

  A plurality of medical facilities include a core hospital 11 and a clinic 12. The core hospital 11 is a relatively large medical facility in the area. The core hospital 11 possesses advanced medical examination equipment such as CT (Computed Tomography) equipment and MRI (Magnetic Resonance Imaging) equipment, and requests medical examination not only from the in-hospital department but also from external medical facilities such as the clinic 12. Receive. The clinic 12 does not have an advanced medical examination device and requests a medical examination from the core hospital 11.

  In the core hospital 11, an in-hospital information system (HIS) 14 in which various in-hospital computers are connected by a LAN (Local Area Network) 13 is constructed. The in-hospital information system 14 performs in-hospital information processing such as medical examination reservation acceptance processing, medical treatment acceptance processing, and accounting processing. The LAN 13 is a network laid in the hospital, and the in-hospital information system 14 is blocked from a public external network such as the Internet 15 that is open to an unspecified number of users. This avoids information security risks such as unauthorized access from outside.

  In the hospital information system 14, a medical examination can be reserved online via a LAN 13 from a terminal 16 (hereinafter referred to as “hospital terminal”) installed in each department in the hospital. The in-hospital server 17 of the in-hospital information system 14 accepts such reservations and performs medical examination schedule management.

  An in-hospital reservation information database (hereinafter referred to as in-hospital reservation information DB) 18 and a patient information database (hereinafter referred to as patient information DB) 19 are connected to the in-hospital server 17. The in-hospital reservation information DB 18 stores in-hospital reservation information 20 indicating the reservation status of medical examinations and the like, and the patient information DB 19 stores patient information 21 in which information on patients who have been examined at the core hospital 11 is collected.

  The in-hospital server 17 accepts access from the in-hospital terminal 16 and reports the reservation status to the in-hospital terminal 16 based on the in-hospital reservation information 20. And the reservation from the hospital terminal 16 is received and the hospital reservation information 20 is updated. For appointments from the in-hospital terminal 16, the examination type / purpose, date and time of appointment (reservation frame) specified by the patient, patient ID issued in the core hospital 11, patient name, gender, age / date of birth Information such as date, name of injury and illness, reservation source (medical department of the core hospital 11) ID automatically attached at the time of transmission from the hospital terminal 16, reservation reception date and time, and the like are included. One reservation frame is set for each time slot divided at intervals of 30 minutes, such as 9: 00 to 9:30. The reservation reception date and time is the time at which the reservation information from the hospital terminal 16 is received by the hospital server 17 and is given by the hospital server 17. When receiving the reservation information from the in-hospital terminal 16, the in-hospital server 17 gives a reservation ID to the received reservation information.

  The in-hospital terminal 16 is a personal computer in which browser software for communicating with the in-hospital server 17 is installed. The in-hospital terminal 16 communicates with the in-hospital server 17 to display the received reservation status on a display or transmit reservation information. .

  The core hospital 11 performs a medical examination in response to a request for a medical examination from each clinic 12. The data center 10 serves as a reception desk for medical examinations of the core hospital 11 and accepts reservations for medical examinations online from the terminals 22 (hereinafter referred to as clinic terminals) installed in the clinics 12 through the Internet 15. .

  The data center 10 includes a center server 23 and a center reservation information database (hereinafter abbreviated as center reservation information DB) 24. The center server 23 functions as a WEB server and corresponds to a document system (WWW: World Wide Web) that is used as a standard on the Internet. The center server 23 transmits and receives data in response to a request from the clinic terminal 22 which is a client terminal. The clinic terminal 22 is a personal computer in which browser software is installed, and can access the center server 23.

  The center reservation information DB 24 stores center reservation information 25 representing the medical examination reservation status of the core hospital 11. The center server 23 accepts access from the clinic terminal 22 and reports the reservation status to the clinic terminal 22 based on the center reservation information 25. Then, the reservation from the clinic terminal 22 is accepted and the center reservation information 25 is updated.

  As shown in FIG. 2, in one piece of reservation information from the clinic terminal 22, the ID of the core hospital 11 designated as the examination request destination and the clinic 12 instead of the name of the clinic as the reservation source information The same items as the reservation information from the in-hospital terminal 16 are included except that the patient ID issued by the core hospital 11 is not attached. In the following description, each item of patient name, gender, age / date of birth is collectively referred to as patient basic information 30.

  Returning to FIG. 1, the relay server (gateway) 26 is connected between the hospital server 17 and the center server 23 connected via different networks such as a LAN 13 and a VPN (Virtual Private Network) 27. The reservation information received from 22 is relayed. The relay server 26 performs data format conversion and protocol conversion in communication between the servers 17 and 23 and functions as a firewall that prevents unauthorized access to the hospital information system 14 from the outside.

  The relay server 26 and the center server 23 are connected via the VPN 27. The VPN 27 uses an encryption technique, and a logical dedicated communication channel is established in a shared network shared by a plurality of users. As a result, confidentiality between communication bases is maintained, and robust information security within the network is ensured.

  As shown in FIG. 3A, the patient information 21 stored in the patient information DB 19 includes basic patient information 30 similar to the reservation information from the clinic terminal 22 for each patient ID issued by the core hospital 11. Various items such as the name of injury and sickness are stored. The patient ID is assigned to each patient at the first visit, and is a number that can only be used at the core hospital 11. In-hospital information system 14 performs various information processing in the hospital based on this patient ID. Moreover, as shown in (B), the in-hospital reservation information 20 stores various items of patient information and reservation information listed above for each patient ID. The in-hospital reservation information 20 also stores data indicating which reservation frame is free and which reservation frame is filled (reservation status).

  Each of the terminals 16 and 22 and each of the servers 17, 23, and 26 is configured based on a computer such as a personal computer, a server computer, and a workstation. As shown in FIG. 4, a control program such as an operating system and an application program (hereinafter abbreviated as AP) 35 are installed in each terminal 16, 22 and each server 17, 23, 26. The AP 35 installed in each of the servers 17 and 23 includes a reservation reception program that provides a reservation reception service.

  Each terminal 16, 22 and each server 17, 23, 26 include a CPU 36, a memory 37, a storage device 38, a communication I / F (interface) 39, and a console 40. These are interconnected via a data bus 41.

  The storage device 38 is, for example, an HDD (Hard Disk Drive). The storage device 38 stores a control program and AP 35.

  The memory 37 is a work memory for the CPU 36 to execute processing. The CPU 36 controls each unit of the computer by loading a control program stored in the storage device 38 into the memory 37 and executing processing according to the program.

  The communication I / F 39 is a LAN port, a WAN port, a router, or the like, and is connected to a communication cable for connecting to a network such as the LAN 13, the VPN 27, or the Internet 15. The communication I / F 39 exchanges data via the LAN 13, the VPN 27, or the Internet 15. The console 40 includes a display 42 and an input device 43 such as a keyboard, a mouse, and a microphone.

  The CPUs 36 in the hospital and center servers 17 and 23 respectively load the reservation acceptance program from the storage device 38 and execute the processing steps described in the program. As a result, as shown in FIG. 5, reservation acceptance processing units 17a and 23a, DB access units 17b and 23b, and synchronization processing units 17c and 23c are constructed in the CPUs 36 of the servers 17 and 23, respectively.

  Each reservation acceptance processing unit 17a, 23a exchanges data with the corresponding terminal 16, 22. The data sent from each reservation acceptance processing unit 17a, 23a to each terminal 16, 22 is information that reports the availability of the reservation frame, and the data received by each reservation acceptance processing unit 17a, 23a from each terminal 16, 22 is Reservation information and the like.

  Each reservation acceptance processing unit 17a, 23a generates a text file described in a markup language such as HTML format or XML format as data representing the reservation status based on each reservation information 20, 25, and stores it in each terminal. 16 and 22. The browsers of the terminals 16 and 22 configure a screen for reporting the availability of a reservation frame in a calendar format, for example, according to the description of the received text file, and output the screen to the display 42.

  Each reservation acceptance processing unit 17a, 23a accepts reservation information from each terminal 16, 22 and delivers it to the DB access units 17b, 23b. Each DB access unit 17b, 23b accesses the in-hospital reservation information DB 18 or the patient information DB 19 and the center reservation information DB 24, and based on the reservation information acquired through the reservation reception processing units 17a, 23a, Each reservation information 20, 25 or patient information 21 in the patient information DB 19 is updated.

  Each of the synchronization processing units 17c and 23c communicate with each other via the LAN 13 or the VPN 27. The synchronization processing units 17c and 23c appropriately communicate and share the availability of the reservation slots so as not to cause so-called double booking in which reservations from the terminals 16 and 22 overlap in the same reservation slot, The reservation information 20 and 25 in each DB 18 and 24 are synchronized. By the operation of the synchronization processing units 17c and 23c, about the data representing the reservation status in the reservation information 20 and 25, substantially the same contents including reservations from both the clinic 12 and the hospital are stored.

  When the reservation information from the clinic terminal 22 is received via the synchronization processing unit 23c of the center server 23, each unit of the hospital server 17 executes the processing shown in FIG. 6 or FIG. First, as shown in the upper part of each figure, when the reservation reception processing unit 17a receives the reservation information from the clinic terminal 22, it issues a search command to the DB access unit 17b. In response to the search command, the DB access unit 17b searches the patient information 21 of the patient information DB 19 to determine whether there is patient basic information 30 that matches the patient basic information 30 of the received reservation information. The DB access unit 17b judges that all three items (patient name, gender, age / date of birth) constituting the basic patient information 30 match as “match”, and even if the same name is the same and the age is the same If any one of the three items does not match, such as when the date is different, it is determined as “mismatch”.

  When there is patient basic information 30 that matches the patient basic information 30 of the received reservation information, as shown in the upper part of FIG. 6, the DB access unit 17b receives a reservation indicating a signal indicating “match” as a search result. Return to the processing unit 17a.

  Subsequently, as shown in the lower part, the reservation acceptance processing unit 17a issues a registration command to the DB access unit 17b. In response to the registration command, the DB access unit 17b registers the reservation information from the clinic terminal 22 and various items of the patient information 21 of the patient information DB 19 in the in-hospital reservation information 20 as a newly received reservation. At this time, the DB access unit 17b attaches the patient ID (existing patient ID) of the patient information 21 having the patient basic information 30 that matches the patient basic information 30 of the received reservation information.

  On the other hand, if the patient basic information 30 that matches the patient basic information 30 of the received reservation information is not found in the patient information 21, the DB access unit 17b indicates that the information does not match, as shown in the upper part of FIG. A signal is returned to the reservation acceptance processing unit 17a as a search result.

  In this case, as shown in the lower part, the reservation acceptance processing unit 17a issues a new patient ID and sends it to the DB access unit 17b together with a registration command. The DB access unit 17b receives a registration command with a new patient ID, attaches a new patient ID, and registers various items of reservation information from the clinic terminal 22 in the in-hospital reservation information 20. Further, the DB access unit 17b registers the patient basic information 30 of the reservation information from the clinic terminal 22 with a new patient ID, and updates the patient information 21. Although illustration is omitted, in both cases of FIGS. 6 and 7, the reservation processing unit 17a issues a search command after the synchronization processing unit 17c determines that there is no reservation overlap.

  After completing the registration of various information by the DB access unit 17b, the synchronization processing unit 17c sends a reservation completion notification to the center server 23 that indicates that the reservation has been received. The reservation completion notification includes the name of the core hospital 11 for which reservation has been made and information on the date and time of consultation. The reservation reception processing unit 23 a of the center server 23 delivers a reservation completion notification to the clinic terminal 22.

  Hereinafter, with reference to the flowchart of FIG. 8, the process of the hospital server 17 when the reservation information from the clinic terminal 22 is received will be described. In S (step) 10, when reservation information from the clinic terminal 22 is received by the reservation reception processing unit 17a, a search command is issued from the reservation reception processing unit 17a to the DB access unit 17b, and the DB access unit 17b causes the patient to It is searched whether there is patient basic information 30 that matches the patient basic information 30 of the received reservation information in the patient information 21 of the information DB 19 (S11).

  If there is patient basic information 30 that matches the patient basic information 30 of the received reservation information (YES in S12), the DB access unit 17b adds the existing patient ID and the reservation information from the clinic terminal 22 and Various items of the patient information 21 of the patient information DB 19 are registered in the in-hospital reservation information 20, and the in-hospital reservation information 20 is updated (S13).

  On the other hand, when the patient basic information 30 that matches the patient basic information 30 of the received reservation information is not in the patient information 21 (NO in S12), a new patient ID is issued by the reservation reception processing unit 17a ( S14). Then, the DB access unit 17b adds a new patient ID and registers various items of reservation information from the clinic terminal 22 in the in-hospital reservation information 20. Further, the DB access unit 17b adds the new patient ID, registers the basic patient information 30 of the reservation information from the clinic terminal 22, and updates the patient information 21 (S15). These processes are repeatedly performed every time reservation information from the clinic terminal 22 is received.

  When the series of processes shown in FIG. 8 is completed, a screen representing the content of the reservation completion notification is output on the display 42 of the clinic terminal 22. The doctor at the clinic 12 tells the patient the date and time of the visit, and the patient visits the core hospital 11 for the examination at the date and time of the notified visit.

  As described above, when a reservation is received from the clinic 12, the reservation information from the clinic 12 and the basic patient information 30 of the patient information 21 are matched. If the patient IDs do not match, the in-hospital reservation information 20 is registered with the newly issued patient ID, so that the reservation from the clinic 12 can be reflected in the in-hospital reservation information 20 without manpower.

  In addition, a patient who has visited the hospital and has already issued a patient ID will not be mistaken for a new patient, and conversely, a new patient will not be mistaken for a reexamined patient. Furthermore, when the reservation information and the patient basic information 30 of the patient information 21 do not match, the patient information 21 is registered with the newly issued patient ID, so that the patient information 21 can be managed correctly.

  In order to further enhance the convenience of information management, the modes shown in FIGS. 9 and 10 may be implemented.

  In the aspect shown in FIG. 9, when sending the reservation completion notification from the synchronization processing unit 17c to the synchronization processing unit 23c, the patient ID used when the in-hospital reservation information 20 is registered is attached. The synchronization processing unit 23c passes the attached patient ID to the reservation reception processing unit 23a, and the reservation reception processing unit 23a issues a registration command to the DB access unit 23b. The DB access unit 23b registers the attached patient ID in association with the corresponding reservation information of the center reservation information 25.

  In this way, for example, when the core hospital 11 independently modifies the reservation information, if the correction content and the patient ID information are sent to the center server 23, the center server 23 specifies the reservation information based on the patient ID. You can synchronize your corrections. Alternatively, when a patient ID is newly issued, if the patient ID information is transmitted from the center server 23 to the clinic terminal 22, the patient ID can be reported to the patient in advance through a doctor at the clinic 12.

  In the mode shown in FIG. 10, the reservation reception processing unit 17a describes the search result received from the DB access unit 17b in the log file 50 for each reservation. The log file 50 is stored in the storage device 38, for example. The log file 50 stores the search result of the DB access unit 17b together with the reservation reception date and time, the patient basic information 30, the patient ID, and the like.

  The reservation acceptance processing unit 17a reads the log file 50 in response to a screen distribution request from the in-hospital terminal 16. Then, list screen information is created based on the stored contents of the log file 50 and distributed to the in-hospital terminal 16. The browser of the hospital terminal 16 outputs the list screen 51 to the display 42 based on the list screen information from the reservation reception processing unit 17a. The basic contents of the list screen 51 are substantially the same as the storage contents of the log file 50, and the storage contents of the log file 50 are edited in a format that is easy to visually recognize by adding item titles or changing the layout. It is a thing.

  Thus, if the search result of the DB access part 17b is visually displayed as the list screen 51, the reservation status and search result from the clinic 12 can be easily grasped. Also, when a patient visits and accepts, it is useful for reference when checking whether the patient is a new patient or a revisited patient.

  In the above embodiment, three items of patient name, sex, age and date of birth are illustrated as basic patient information, but the present invention is not limited to this. An item such as a patient name reading pseudonym, a patient address, a contact telephone number, or a name of a sick or an attending physician may be added. In short, any device that can identify a patient may be used. If the number of items to be searched increases, a certain amount of processing time is required for the search, but the accuracy of determination of matching or mismatching increases.

  In the above embodiment, each functional unit such as the reservation reception processing unit and the DB access unit is provided in the hospital server. However, even if each functional unit is constructed in the relay server and the relay server is responsible for some of these processes. Good.

2 Reservation acceptance system 10 Data center 11 Core hospital 12 Clinic 16 Terminal (in-hospital terminal)
17 In-hospital server 17a, 23a Reservation reception processing unit 17b, 23b DB access unit 18 In-hospital reservation information database (in-hospital reservation information DB)
19 Patient information database (patient information DB)
20 In-hospital reservation information 21 Patient information 22 Terminal (clinic terminal)
23 Center server 24 Center reservation information database (center reservation information DB)
25 Center reservation information 30 Patient basic information 35 Application program (AP)
36 CPU
51 List screen

Claims (9)

An in-hospital server that accepts medical examination reservation information addressed to a medical facility including basic patient information necessary for identifying a patient from outside the medical facility;
A reservation information database for storing received reservation information;
A patient information database for storing basic patient information in a medical facility,
The in-hospital server searches the patient information database for patient basic information that matches the patient basic information attached to the reservation information, and registers the reservation information in the reservation information database according to the search result. Reservation reception system for medical examinations. The patient information database stores patient basic information for each patient ID for uniquely identifying a patient,
When the patient basic information matching the patient basic information attached to the reservation information is found in the patient information database, the in-hospital server adds the patient ID of the patient basic information to the reservation information and registers it in the reservation information database And
If patient basic information matching the patient basic information attached to the reservation information is not found in the patient information database, a new patient ID is issued, and the patient ID is added to the reservation information and registered in the reservation information database. The medical examination reservation acceptance system according to claim 1, wherein:   The medical examination reservation acceptance system according to claim 2, wherein the in-hospital server registers patient basic information attached to reservation information with a newly issued patient ID in the patient information database.   4. The medical examination reservation reception system according to claim 2, wherein the in-hospital server receives reservation information via a center server of a data center outside the medical facility.   The hospital server, when receiving reservation information via the center server, transmits information of a patient ID attached to the reservation information and registered in the reservation information database to the center server. 4. A medical examination reservation reception system according to 4.   6. The medical examination reservation receiving system according to claim 1, wherein the in-hospital server creates and distributes screen information representing a list of search results for each reservation information.   7. The medical examination reservation reception system according to claim 1, wherein the basic patient information includes at least information indicating a patient name, sex, and age. A reception step for accepting medical examination reservation information addressed to a medical facility including basic patient information necessary for identifying a patient from outside the medical facility;
A search step of searching for patient basic information that matches the patient basic information attached to the reservation information from a patient information database storing the patient basic information in the medical facility;
An information registration step for registering reservation information in a reservation information database in accordance with the search result of the search step. A reception step for accepting reservation information for medical examinations directed to a medical facility including basic patient information necessary for identifying a patient from outside the medical facility;
A search step of searching for patient basic information that matches the patient basic information attached to the reservation information from a patient information database storing the patient basic information in the medical facility;
A medical examination reservation reception program causing a computer to execute an information registration step of registering reservation information in a reservation information database in accordance with a search result of the search step.

Images