Information processing system and information processing method

Abstract

It is possible to efficiently aggregate data from medical institutions. [Solution] An information processing system that is connected to a first management system that manages communication schedules with clients and a second management system that manages call histories with clients, and is characterized by comprising: an information acquisition unit that acquires schedules for each client from the first management system and acquires call histories corresponding to the schedules from the second management system; and a display unit that displays the call histories for each client and schedule.

Description

[Technical Field]

[0001] The present invention relates to an information processing system and an information processing method. [Background technology]

[0002] US Patent No. 6,299,649 discloses a medical information system that compiles protected health information (PHI) from medical images and related documents. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] U.S. Patent No. 10,496,788 Summary of the Invention [Problem to be solved by the invention]

[0004] Healthcare providers typically use separate systems for managing client schedules and recording detailed communication information. While this separation helps protect sensitive patient data, it creates operational inefficiencies as staff must switch between multiple systems to track client interactions.

[0005] The present invention has been made in view of the above background, and aims to provide a technique that can efficiently aggregate data from medical institutions. [Means for solving the problem]

[0006] The main invention of the present invention for solving the above problem is an information processing system that is connected to a first management system that manages communication schedules with clients and a second management system that manages call histories with the clients, and is characterized by comprising: an information acquisition unit that acquires the schedule for each client from the first management system and acquires the call history corresponding to the schedule from the second management system; and a display unit that displays the call history for each client and each schedule.

[0007] Other problems and solutions disclosed in this application will be made clear in the section on preferred embodiments of the invention and the drawings. [Effects of the Invention]

[0008] According to the present invention, data from medical institutions can be efficiently aggregated. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram showing the overall configuration of an information processing system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a management server according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram illustrating a software configuration of a management server according to an embodiment of the present invention. [Figure 4] 1 is a flowchart illustrating a processing flow executed by an information processing system according to an embodiment of the present invention. [Figure 5] FIG. 2 is a sequence diagram illustrating interactions between components during a typical operation of an information processing system according to an embodiment of the present invention. [Figure 6] 2 is a diagram showing a data structure stored in a storage unit of a management server according to an embodiment of the present invention and relationships between data entities. FIG. [Figure 7] FIG. 10 is a diagram illustrating an example of a user interface for displaying a client communication history according to an embodiment of the present invention. [Figure 8]1 is a flowchart illustrating a verification process using a large-scale language model according to an embodiment of the present invention. [Figure 9] 10 is a flowchart illustrating an alternative verification process using rule-based filtering according to an alternative embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] <System Overview>

[0011] The information processing system according to this embodiment is a system for healthcare service providers, particularly mental health clinics, and is connected to multiple management systems used in these clinics.

[0012] Mental health clinics typically use separate systems for different operational functions: one system manages appointment scheduling and client acquisition, and another system records detailed communication data that may contain protected health information (PHI).

[0013] The information processing system of this embodiment connects to these different management systems. The system obtains schedule data from the SFA management system 3 (sales force automation) and obtains corresponding call history metadata from the PHI management system 4 (protected health information). The system then correlates and displays this information without disclosing the protected health information.

[0014] <System configuration> 1 is a diagram showing the overall configuration of an information processing system according to this embodiment. The information processing system includes a management server 2. The management server 2 is communicably connected to a user terminal 1 via a communication network. The communication network is, for example, the Internet, and is constructed using a public telephone network, a mobile phone network, a wireless communication path, Ethernet (registered trademark), or the like.

[0015] The user terminal 1 is a computer operated by a user, and may be, for example, a smartphone, a tablet computer, or a personal computer.

[0016] The management server 2 may be a general-purpose computer such as a workstation or personal computer, or may be logically realized using cloud computing. The management server 2 executes various processes related to the information processing system of the present invention.

[0017] The management server 2 is connected to an SFA management system 3 that manages communication schedules with clients, and a PHI management system 4 that manages call histories with clients. The connection between the management server 2 and these management systems may be implemented via the same communication network that connects the management server 2 and the user terminal 1, or may be implemented via a separate dedicated network.

[0018] <Administration Server> 2 is a diagram showing an example of the hardware configuration of the management server 2. Note that the configuration shown in the figure is an example, and other configurations may also be used. The management server 2 includes a CPU 201, a memory 202, a storage device 203, a communication interface 204, an input device 205, and an output device 206.

[0019] The storage device 203 stores various data and programs, and is, for example, a hard disk drive, a solid state drive, a flash memory, etc. The communication interface 204 is an interface for connecting to a communication network, and is, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone network, a wireless communication device for wireless communication, a USB (Universal Serial Bus) connector or an RS232C connector for serial communication, etc.

[0020] The input device 205 is used to input data and includes, for example, a keyboard, a mouse, a touch panel, a button, a microphone, etc. The output device 206 is used to output data and includes, for example, a display, a printer, a speaker, etc.

[0021] Each functional unit of the management server 2 described below is realized by the CPU 201 reading a program stored in the storage device 203 into the memory 202 and executing it, and each storage unit of the management server 2 is realized as part of the storage area provided by the memory 202 and the storage device 203.

[0022] 3 is a diagram showing an example of the software configuration of the management server 2. The management server 2 includes an information acquisition unit 211, a data processing unit 212, a display control unit 213, a verification unit 214, a communication unit 215, and a storage unit 231.

[0023] The information acquisition unit 211 is configured to acquire schedule data from the SFA management system 3 and acquire call history data from the PHI management system 4. The data processing unit 212 processes and associates the acquired data. The display control unit 213 controls the information display on the user terminal 1. The verification unit 214 verifies that the displayed data does not include protected health information. The communication unit 215 processes communication with the user terminal 1, the SFA management system 3, and the PHI management system 4. The memory unit 231 stores data necessary for the operation of the information processing system.

[0024] <Storage section 231> The storage unit 231 is implemented in the storage device 203 of the management server 2. The storage unit 231 stores various data necessary for the operation of the information processing system. Specifically, the storage unit 231 can store client information, schedule information acquired from the SFA management system 3, call history information acquired from the PHI management system 4, and correlation information that associates the schedule information with the call history information.

[0025] Client information may include a client identifier, client name, and other basic information about the client. Schedule information may include scheduled communication events with the client, such as appointment time, scheduled call duration, and the purpose of the scheduled communication. Call history information includes metadata about the call, such as call start and end times and staff identification information, but does not include the actual content of the call or any protected health information.

[0026] <Data Structure> FIG. 6 is a data structure diagram showing the relationships between different types of data stored in the storage unit 231 of the management server 2. As shown in FIG. 6, client information includes a client ID, a client name, and contact information. Schedule information includes a schedule ID, a client ID as a foreign key referencing the client information, a scheduled time, a purpose, a staff ID, and a status. Call history information includes a call ID, a schedule ID as a foreign key referencing the schedule information, a client ID as a foreign key referencing the client information, a staff ID, a start time, an end time, a call type, a call status, and a session status. As shown in FIG. 6, there is a one-to-many relationship between client information and schedule information, meaning that one client can have multiple schedules. Similarly, there is a one-to-many relationship between schedule information and call history information, meaning that multiple call histories may be associated with one schedule.

[0027] <Information acquisition unit 211> The information acquisition unit 211 is realized by the CPU 201 executing a program stored in the storage device 203. The information acquisition unit 211 is configured to acquire data from both the SFA management system 3 and the PHI management system 4.

[0028] Specifically, the information acquisition unit 211 acquires schedule information for each client from the SFA management system 3. This schedule information includes data regarding planned communications with the client, such as appointments, scheduled calls, and the purpose of these communications. The information acquisition unit 211 also acquires call history information corresponding to the schedule from the PHI management system 4. This call history information includes comprehensive metadata regarding the communications, such as:

[0029] Call start and end times Staff identification information · Whether a staff member or client answered the call Whether the staff member or client ended the call - Recording of voicemails left Therapy session start and end times Whether the therapy session was completed successfully

[0030] Call history information does not include the actual content of calls, voicemails, or therapy sessions, and does not include any other protected health information.

[0031] The information acquisition unit 211 can establish connections with both management systems using appropriate communication protocols via the communication interface 204. The acquired information is stored in the storage unit 231 for further processing.

[0032] <Data processing unit 212> The data processing unit 212 is realized by the CPU 201 executing a program stored in the storage device 203. The data processing unit 212 is configured to process the information acquired by the information acquisition unit 211.

[0033] Specifically, the data processing unit 212 associates the schedule information obtained from the SFA management system 3 with the call history information obtained from the PHI management system 4. This association is performed based on a client identifier, time information, a staff identifier, or other suitable parameters that can associate a particular call history event with a particular scheduled communication.

[0034] The data processor 212 organizes the associated information into a structured format suitable for display, including arranging the information chronologically or grouping it by client, staff member, or communication event. The data processor 212 may also filter the information to exclude protected health information that may have been inadvertently included in the retrieved data.

[0035] The processed information is stored in the storage unit 231, and the display control unit 213 can present it to the user.

[0036] <Display control unit 213> The display control unit 213 is realized by the CPU 201 executing a program stored in the storage device 203. The display control unit 213 is configured to display the information processed by the data processing unit 212 on the user terminal 1.

[0037] Specifically, the display control unit 213 generates user interface elements for displaying the call history associated with each client and each schedule. The display includes client identification information, the identification information of the staff member who handled the communication, the start and end times of the call, the start and end times of the session, and other relevant metadata about the communication. The display control unit 213 ensures that the information is presented in a clear and organized manner, such as a chronological list or table format.

[0038] The display controls 213 may allow a user to filter or sort the displayed information according to various parameters, such as by client, by date range, by staff member, or by communication type. The display controls 213 may also provide visual indicators to highlight important information, such as missed calls, voicemails, or aborted sessions.

[0039] The display control unit 213 transmits the generated display information to the user terminal 1 via the communication unit 215.

[0040] <User interface example> 7 is a diagram illustrating an example of a user interface for a client communication history that may be displayed on the user terminal 1. The interface includes a header section that shows client identification information such as the client ID, client name, and contact information. Below this header, a timeline of communication events is displayed.

[0041] Each event includes details such as the purpose of the scheduled appointment, the staff member responsible, and the status. Within each event, there is a call history section that displays the sequence of communication activities that occurred, including timestamps of when the call was made, answered, or ended. It also includes voicemail recordings and information about rescheduling the session.

[0042] The interface organizes information in a clear hierarchy that allows users to quickly understand the communication history for each client and each scheduled event without displaying protected health information. Important information, such as status, may be displayed in different colors to visually distinguish between states, such as completed or rescheduled.

[0043] <Verification Unit 214> The verification unit 214 is realized by the CPU 201 executing a program stored in the storage device 203. The verification unit 214 is configured to verify that the acquired call history does not include information related to the content of the call or other protected health information.

[0044] Specifically, the verification unit 214 analyzes data obtained from the PHI management system 4 before displaying it to the user. The verification unit 214 may use pattern matching, keyword filtering, or other analytical techniques to identify and filter sensitive information that should not be displayed. As recited in claim 4, in some implementations, the verification unit 214 may utilize large-scale language models by providing prompts with instructions for determining whether the call history contains information related to the content of the call or other protected health information.

[0045] The validator 214 may flag suspicious content for manual review or automatically redact information that appears to contain protected health information. If protected health information is detected, the validator 214 may prevent the information from being displayed or replace it with a notice indicating that some information has been suppressed due to privacy concerns.

[0046] <Verification process flow> 8 is a detailed flowchart of the verification process performed by the verification unit 214 to verify that the displayed data does not contain protected health information. The process begins by receiving associated data for verification (S104-1) and then extracting text content from the data fields (S104-2). The verification unit prepares a prompt for the large-scale language model (S104-3) and sends the prompt to the large-scale language model (S104-4).

[0047] The large-scale language model analyzes the content for protected health information (S104-5). If protected health information is detected, the content is flagged for review (S104-6) and the protected health information is removed (S104-7). If no protected health information is detected, the content is approved for display (S104-8). Finally, the verified data is returned (S104-9) for display on the user terminal.

[0048] <Communications Department 215> The communication unit 215 is realized by the CPU 201 executing a program stored in the storage device 203. The communication unit 215 is configured to process communications between the management server 2 and other systems (including the user terminal 1, the SFA management system 3, and the PHI management system 4).

[0049] Specifically, the communication unit 215 establishes and maintains network connections with these systems via the communication interface 204. The communication unit 215 implements appropriate communication protocols and data formats to enable information exchange. When the information acquisition unit 211 needs to acquire data from the SFA management system 3 or the PHI management system 4, it does so through the communication unit 215. Similarly, when the display control unit 213 needs to send display information to the user terminal 1, it also does so through the communication unit 215.

[0050] The communications unit 215 may also handle authentication and security measures for these communications, for example, implementing secure connection protocols, encryption, and access control mechanisms to ensure that sensitive information is protected during transmission.

[0051] <Processing flow> FIG. 4 is a flowchart showing an example of processing executed by the information processing system according to the embodiment of the present invention.

[0052] First, the information acquisition unit 211 acquires schedule information of each client from the SFA management system 3 (S101). This schedule information includes data on planned communication with the client, such as reservations and scheduled calls.

[0053] Next, the information acquisition unit 211 acquires call history information corresponding to the schedule from the PHI management system 4 (S102). This call history information includes metadata related to communication, such as the start and end times of the call, whether the call was answered, and the timing of the therapy session.

[0054] Next, the data processing unit 212 associates the acquired schedule information with the acquired call history information (S103), based on the client identifier, time information, and other appropriate parameters.

[0055] The validation component 214 verifies that the associated information does not contain protected health information (S104), which may include pattern matching, keyword filtering, or analyzing the data using large-scale language models.

[0056] Finally, the display control unit 213 displays the verified associated information for each client and each schedule on the user terminal 1 (S105). The displayed information includes client identification information, staff identification information, and communication metadata that does not include protected health information.

[0057] <Sequence diagram> 5 is a sequence diagram illustrating interactions between a user terminal 1, a management server 2, an SFA management system 3, and a PHI management system 4 during typical operation of an information processing system according to an embodiment of the present invention. As shown in FIG. 5, when a user requests a client communication history via the user terminal 1, the request is sent to the management server 2. The management server 2 then requests schedule information from the SFA management system 3, and the SFA management system 3 returns the requested schedule information. The management server 2 then requests call history information from the PHI management system 4, and the PHI management system 4 returns the requested call history information. The management server 2 associates and verifies this information, and then sends the processed information to the user terminal 1 to display it to the user.

[0058] Each step in the sequence diagram shown in FIG. 5 will be described in detail.

[0059] First, the user requests the display of the client communication history by operating the user terminal 1. This request is made, for example, by the user clicking a specific button on the user interface displayed on the user terminal 1 or by selecting a specific client.

[0060] Next, based on the request from the user, the user terminal 1 generates a request for client communication history data and transmits it via the communication network to the management server 2. This request may include information such as the identification information of the client to be acquired and the period for which acquisition is to be performed.

[0061] When the management server 2 receives a request from the user terminal 1, it first uses the information acquisition unit 211 to request schedule information from the SFA management system 3. This request includes the identifier of the target client, the target period, and so on.

[0062] In response to a request from the management server 2, the SFA management system 3 searches for the schedule information of the corresponding client and returns the found schedule information to the management server 2. The returned schedule information includes information such as the reservation time, the scheduled call duration, the purpose of the call, and the staff member in charge.

[0063] Next, the management server 2 uses the information acquisition unit 211 to request call history information from the PHI management system 4. This request includes an identifier and time information corresponding to the schedule information acquired from the SFA management system 3.

[0064] In response to a request from Management Server 2, PHI Management System 4 searches for the relevant call history information and returns the found call history information to Management Server 2. The returned call history information includes the start and end times of the call, the identification information of the person who answered the call, the call status (answered, not answered, etc.), whether there was a voicemail, the session status, etc., but does not include protected health information such as the content of the call or diagnosis results.

[0065] The management server 2 performs an association process on the information received from the SFA management system 3 and the PHI management system 4 using the data processing unit 212, and further verifies using the verification unit 214 that protected health information is not included.

[0066] Finally, the management server 2 transmits the information for which the association and verification have been completed to the user terminal 1 using the display control unit 213 and the communication unit 215. The user terminal 1 displays the received information on the screen and presents it to the user.

[0067] As described above, the information processing system of this embodiment provides several advantages. The system allows for unified viewing of client communication schedules and histories stored in separate management systems without disclosing protected health information. This allows clinic staff to efficiently monitor client interactions across multiple platforms while complying with healthcare privacy regulations.

[0068] The system also allows clinic staff to quickly verify that planned communications were properly executed without having to access multiple systems separately. A verification component automatically filters sensitive information, reducing the risk of inadvertent disclosure of protected health information.

[0069] Additionally, by displaying communication metadata in a chronological and organized manner, the system enables communication issues, such as missed calls or aborted sessions, to be quickly identified and addressed, improving operational efficiency while maintaining a clear record of all client interactions.

[0070] Although the present invention has been described above with reference to specific embodiments, the above detailed description is not intended to limit the scope of the present invention. Various modifications, changes, and improvements can be made without departing from the spirit of the present invention, and the present invention also includes equivalents thereof. The described embodiments are provided to facilitate understanding of the technical aspects of the present invention, and the present invention is defined not by the description of the embodiments but by the appended claims and their legal equivalents. All modifications, changes, and improvements that come within the meaning and range of equivalence of the claims are intended to be within the scope of the present invention.

[0071] The processing by each of the functional units of the management server 2 described above may be performed by any of the functional units. Also, a different functional unit that performs part of the processing by each of the functional units described above may be added. Furthermore, the functional units of the management server 2 may be distributed across multiple computers.

[0072] Similarly, the information stored in the storage unit 231 of the management server 2 can be organized in various ways. For example, the information described as being stored in the storage unit 231 may be divided and stored in multiple different storage units. Conversely, information that may be stored in multiple storage units in the described embodiment may be integrated into a single storage unit. In another variation, certain information stored in the storage unit 231 may be partially distributed and stored in other storage units.

[0073] These implementation variations do not depart from the spirit and scope of the present invention as defined by the appended claims.

[0074] <Variation 1: Alternative Verification Method>

[0075] While the above-described embodiments illustrate the use of large-scale language models to verify that displayed data does not contain protected health information, this verification process can also be implemented using rule-based filtering or pattern matching techniques instead of large-scale language models.

[0076] 9 is a flowchart illustrating a validation process using rule-based filtering according to an alternative embodiment of the present invention. In this alternative embodiment, validation component 214 maintains a database of predefined rules and patterns that characterize protected health information. These rules may include regular expressions to identify common forms of protected health information, such as social security numbers, medical record numbers, specific medical terms, diagnostic codes, and descriptions of symptoms and treatments.

[0077] The validation process begins with receiving associated data for validation (S201). Next, the validation unit 214 applies a set of rules to the data (S202). For each field of the data, the validation unit 214 compares the content to a predefined pattern (S203). If a match is found (S204), the matching content is flagged (S205) and deleted or edited (S206). If no match is found, the content is approved for display (S207). The validation unit 214 then returns the validated data (S208).

[0078] This rule-based approach may be advantageous in situations where protected health information types are well-defined and consistent. Rule patterns can be tailored to specific healthcare domains and updated as needed. Furthermore, rule-based validation may require fewer computational resources than using large language models, potentially improving system performance in resource-constrained environments.

[0079] <Disclosures> The present disclosure also includes the following configurations. [Item 1] connected to a first management system that manages schedules of communication with clients and a second management system that manages call histories with the clients; an information acquisition unit that acquires the schedule for each client from the first management system and acquires the call history corresponding to the schedule from the second management system; a display unit that displays the call history for each of the clients and the schedules; An information processing system comprising: [Item 2] Item 1, an information processing system according to item 1, The call history includes a start and end time of the call and a representative identification identifying the representative who answered the call; the display unit displays, for each of the clients and each of the schedules, the start and end times of the call and information indicating the person in charge based on the person in charge identification information; An information processing system characterized by: [Item 3] Item 1, an information processing system according to item 1, a confirmation unit that confirms that the acquired call history does not include information related to the content of the call; An information processing system characterized by: [Item 4] Item 3. The information processing system according to item 3, the verification unit provides a prompt including an instruction to determine whether the call history and information about the content of the call are included to a large-scale language model to determine whether the call history includes information about the content of the call; An information processing system characterized by: [Item 5] a computer connected to a first management system that manages schedules of communication with clients and a second management system that manages call histories with the clients; obtaining the schedule for each of the clients from the first management system; acquiring the call history corresponding to the schedule from the second management system; displaying the call history for each of the clients and the schedules; An information processing method comprising: [Explanation of symbols]

[0080] 1. User terminal 2 Management Server

Claims

1. connected to a first management system that manages a schedule of communication with a client and a second management system that manages a call history with the client; an information acquisition unit that acquires the schedule for each client from the first management system and acquires the call history corresponding to the schedule from the second management system; a confirmation unit that confirms that the acquired call history does not include information related to the content of the call; a display unit that displays the call history in association with the acquired schedule for each client; Equipped with The information processing system is characterized in that the confirmation unit provides a prompt including an instruction to determine whether the call history and information about the content of the call are included to a large-scale language model, thereby determining whether the call history includes information about the content of the call.

2. 2. The information processing system according to claim 1, The call history includes a start and end time of the call and a representative identification identifying the representative who answered the call; the display unit displays, in association with the acquired schedule for each of the clients, the start and end times of the call, which are included in the corresponding call history, and information indicating the person in charge based on the person in charge identification information; An information processing system characterized by:

3. a computer connected to a first management system that manages schedules of communication with clients and a second management system that manages call histories with the clients, obtaining the schedule for each of the clients from the first management system; acquiring the call history corresponding to the schedule from the second management system; confirming that the acquired call history does not include information regarding the content of the call; displaying the call history for each of the clients and the schedules; Run an information processing method, characterized in that in the checking step, a prompt including an instruction to determine whether the call history and information about the content of the call are included is provided to a large-scale language model, thereby determining whether the call history includes information about the content of the call.

Images