Server equipment, computer programs, and methods for assisting in the creation of medical documents.

JP2026115733APending Publication Date: 2026-07-09KAKEHASHI CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024232623
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-12-27
Publication Date
2026-07-09

AI Technical Summary

Technical Problem

Existing systems lack the ability to efficiently support the creation of medical documents based on interactions between healthcare professionals and patients, particularly in enhancing the format customization and reducing the workload associated with medication history documentation.

Method used

A server device equipped with generative artificial intelligence that generates document preparation data from dialogue data, coupled with a storage system for format data, allows client devices to provide medical documents in user-specific formats, thereby reducing the workload on healthcare professionals.

Benefits of technology

Enhances the support for creating medical documents by providing them in desired formats, allowing healthcare professionals to redirect their efforts from documentation to patient care, thus promoting a shift from medication-centered to patient-centered work.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026115733000001_ABST
    Figure 2026115733000001_ABST
Patent Text Reader

Abstract

To enhance the support for tasks such as creating medical documents based on dialogue between healthcare professionals and patients. [Solution] The input interface 121 receives dialogue data DL corresponding to at least a portion of the dialogue between the medical professional and the patient. The processor 122 causes the generative artificial intelligence 130 to generate document preparation data HP for creating at least a portion of the medical documents based on the dialogue data DL. The storage 123 stores format data indicating the format of at least a portion of the medical documents, associated with the user of the client device 11. The processor 122 makes it possible for the client device 11 to provide at least a portion of the medical documents corresponding to the document preparation data HP in the format corresponding to the format data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0004] , , , , ,

[0005] , , , , ,

[0003] , , , , ,

[0001] The present disclosure relates to a server device capable of communicating with a client device. The present disclosure also relates to a computer program executable by a processor mounted on the server device. The present disclosure also relates to a method for assisting in creating medical documents executed by the client device and the server device.

Background Art

[0002] Patent Document 1 discloses a system for assisting in the task of creating a medication history, which is an example of a medical document, based on an interaction between a medical professional and a patient. The system is configured to store the content of medication guidance as a medication history.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a demand to enhance the supportability of the task of creating medical documents based on an interaction between a medical professional and a patient.

Means for Solving the Problems

[0005] One exemplary aspect provided by the present disclosure is a server device capable of communicating with a client device, an interface that receives dialogue data corresponding to at least a part of the dialogue made between a medical professional and a patient, a processor that causes a generative artificial intelligence to generate document preparation data for creating at least a part of a medical document based on the dialogue data, A storage device that stores format data representing the format of at least some of the medical documents, associated with the user of the client device; It is equipped with, The processor enables the client device to provide at least a portion of the medical documents corresponding to the document preparation data in a format corresponding to the format data.

[0006] One example of an embodiment provided herein is a computer program executable by a processor installed in a server device capable of communicating with a client device, By being executed, the server device will We accept dialogue data that corresponds to at least a portion of the conversations that take place between healthcare professionals and patients. Based on the aforementioned dialogue data, the generative artificial intelligence generates document preparation data for creating at least a portion of the medical documents. Format data representing the format of at least some of the medical documents is stored in association with the user of the client device. The client device makes it possible to provide at least a portion of the medical documents corresponding to the document preparation data in the format corresponding to the format data.

[0007] One example of an embodiment provided in this disclosure is a method for assisting in the creation of medical documents, which is performed by a client device and a server device. The client device transmits dialogue data corresponding to at least a portion of the dialogue between the medical professional and the patient to the server device. In the server device, the generative artificial intelligence generates document preparation data for creating at least a portion of medical documents based on the dialogue data. The server device maintains format data representing the format of at least a portion of the medical documents, associated with the user of the client device. The client device outputs at least a portion of the medical document corresponding to the document preparation data in the format corresponding to the format data.

[0008] According to the configurations described in each of the above examples, it is possible to provide at least a portion of medical documents to the client device based on the dialogue about medication taken between the healthcare professional and the patient, and not only that the documents be provided in the format desired by the user of the client device. This enhances the support for the task of creating medication histories based on the dialogue between the healthcare professional and the patient. Healthcare professionals can then redirect the effort previously required for this task to, for example, patient care, thus increasing the possibility of addressing the social challenge of "shifting from medication-centered work to patient-centered work." [Brief explanation of the drawing]

[0009] [Figure 1] This illustrates the configuration of a document creation support system according to one embodiment. [Figure 2] Figure 1 illustrates the functional configuration of the client device, server device, and AI service provider device. [Figure 3] Figure 1 shows an example of the processing flow performed by the document creation support system. [Figure 4] Figure 2 shows an example of a screen displayed in the user interface. [Figure 5] Figure 2 shows another example of the screen displayed in the user interface. [Figure 6] Figure 1 shows another example of the processing flow performed by the document creation support system. [Figure 7] Figure 1 shows another example of the processing flow performed by the document creation support system. [Modes for carrying out the invention]

[0010] An example of an embodiment will be described in detail below with reference to the attached drawings. In the drawings referenced below, the scale has been changed as necessary to make the elements shown recognizable.

[0011] FIG. 1 illustrates the configuration of a document creation support system 10 according to an exemplary embodiment. The document creation support system 10 is configured for the purpose of assisting in the task of creating medical documents based on the conversation regarding medication between medical staff and patients.

[0012] As used herein, the term "medical document" means a document created in a specific format based on the conversation between medical staff and patients and containing medical information. Examples of such documents include a patient's medication history, documents related to inquiries, medication information provision documents (tracking reports), home medical reports, home medical plans, and the like.

[0013] As used herein, the term "conversation" means the exchange of information between medical staff and patients. Examples of conversations include conversations accompanied by face-to-face meetings in a medical institution, conversations made during telephone or online interviews, and text-based question-and-answer made through e-mails, etc.

[0014] Examples of "medical staff" as used herein include physicians, nurses, pharmacists, care managers, dietitians, and the like. The term "patient" as used herein is used to mean not only the patient himself / herself but also includes the caregiver of the patient. Examples of caregivers include guardians when the patient is a child, and caregivers when the patient is a person requiring care.

[0015] As used herein, the term "medical institution" means an institution where medical staff provides explanations about pharmaceuticals to patients. Examples of medical institutions include hospitals, clinics, medical clinics, dispensaries, pharmacies, drugstores, care facilities, care houses, nursing homes, and the like.

[0016] The document creation support system 10 includes a client device 11, a server device 12, and an AI service providing device 13.

[0017] Client device 11 is the device on which information is provided. Client device 11 is used by a medical institution or a patient. Therefore, there may be multiple client devices 11. Note that the same client device used by multiple users with different accounts may be considered multiple client devices. Client device 11 may be a stationary device installed in a specific location, or a portable device that can be carried by a user.

[0018] The server device 12 is installed in a location separate from the client device 11. The client device 11 and the server device 12 are configured to communicate data bidirectionally via the communication network 20.

[0019] The AI ​​service provider 13 (hereinafter abbreviated as "service provider 13") is a device that provides services using generative artificial intelligence 130. The service provider 13 is installed in a location separate from the client device 11 and the server device 12. The server device 12 and the service provider 13 are configured to enable bidirectional data communication via the communication network 20.

[0020] As used herein, the term "generative artificial intelligence" includes not only a trained model (computer algorithm) capable of generating response data not included in the training data in response to input data (prompts), but also the software that operates the computer algorithm and the hardware that operates the software. Input data can take the form of text, audio, images, etc. Response data can also take the form of text, audio, images, etc.

[0021] As illustrated in Figure 2, the client device 11 is equipped with a communication interface 111. On the other hand, the server device 12 is equipped with a communication interface 121. Both the communication interface 111 and the communication interface 121 are hardware interfaces configured to enable bidirectional data communication between the client device 11 and the server device 12.

[0022] Similarly, the service provider 13 is equipped with a communication interface 131. Each of the communication interfaces 121 and 131 is a hardware interface configured to enable bidirectional data communication between the server device 12 and the service provider 13.

[0023] The client device 11 comprises a processor 112 and a user interface 113. The user interface 113 is a hardware interface that mediates the exchange of information between the user and the processor 112 and receives user instructions to cause the client device 11 to perform a predetermined operation. In this embodiment, the user interface 113 includes a display.

[0024] The processor 112 and the user interface 113 may be mounted in a common chassis, or they may be provided in a manner distributed across separate chassis.

[0025] Figure 3 shows an example of the processing flow performed by the document creation support system 10. The predetermined operation performed by the client device 11 includes the creation of dialogue data DL (STEP 11).

[0026] The dialogue data DL corresponds to at least a portion of the dialogue that takes place between healthcare professionals and patients regarding medication. The dialogue data DL can be created based on dialogues acquired through the user interface 113.

[0027] As an example, the user interface 113 may include a microphone. The conversation between the healthcare worker and the patient, input through the microphone, is converted into text data by a computer application with a transcript function. At least a portion of this text data may be provided as dialogue data DL.

[0028] As an alternative example, text data corresponding to at least a portion of the question-and-answer sessions conducted via email between healthcare professionals and patients can be extracted as dialogue data download.

[0029] As an alternative example, text data corresponding to at least a portion of the patient's responses to predetermined questions included in a questionnaire form provided by a healthcare professional may be acquired as dialogue data download.

[0030] Figure 4 shows an example of a screen 113a displayed on the user interface 113. This screen includes a text input area 113b. Text corresponding to the text data acquired by the various methods described above is displayed in the text input area 113b. If the user interface 113 includes a keyboard, text may also be entered directly through the keyboard.

[0031] Screen 113a includes a medication history creation request button image 113c. When the medication history creation request button image 113c is selected via a pointing device or touch operation included in the user interface 113, the processor 112 sends dialogue data DL from the communication interface 111 to the server device 12 (STEP 12 in Figure 3). The transmitted dialogue data DL is received by the communication interface 121 of the server device 12.

[0032] As illustrated in Figure 2, the server device 12 includes a processor 122. As illustrated in Figure 3, the processor 122 is configured to create prompt data PR based on the dialogue data DL received via the communication interface 121 (STEP 21).

[0033] The prompt data PR corresponds to at least one prompt that causes the generative artificial intelligence 130 of the service provision device 13 to generate medication history preparation data HP. The medication history preparation data HP is data for creating a patient's medication history based on a dialogue corresponding to the dialogue data DL. A medication history is an example of a medical document. The medication history preparation data HP is an example of document preparation data.

[0034] As an example, the prompt includes an instruction to the generative artificial intelligence 130 to create a patient medication history in SOAP (Subjective, Objective, Assessment, and Plan) format based on the dialogue data DL. In this example, the patient medication history includes information classified as S items, O items, A items, P items, and OP items. The overview of the information included in each item is as follows: S(Subjective) item: Information that can provide insight into the patient's way of thinking, their views on illness and medication. Patient's questions and requests, chief complaint, subjective symptoms, living environment, preferences, etc. O(Objective) item: Objective information Constitution, medical history, allergy history, history of side effects, diagnosis, test results, prescribed medications, concomitant medications, etc. A (Assessment) item: Matters judged or evaluated by healthcare professionals Drug evaluation (efficacy, side effects, interactions, etc.) Assessment of the patient's psychological and social aspects Determination when S item information and O item information differ. P(Plan) items: Matters related to medication guidance actually provided by healthcare professionals OP (Observation Plan) items: Things to ask your healthcare professional about during your next medication consultation.

[0035] The processor 122 is configured to send the generated prompt data PR to the service provider 13 via the communication interface 121 (STEP 22). The transmitted prompt data PR is received by the communication interface 131 of the service provider 13.

[0036] As illustrated in Figure 2, the service provision device 13 includes a processor 132. As illustrated in Figure 3, the processor 132 is configured to generate medication history preparation data HP by inputting prompt data PR received via the communication interface 131 to the generative artificial intelligence 130 (STEP 31).

[0037] The processor 132 is configured to send the generated medication history preparation data HP to the server device 12 via the communication interface 131 (STEP 32). The transmitted medication history preparation data HP is received by the communication interface 121 of the server device 12.

[0038] As illustrated in Figure 2, the server device 12 is equipped with storage 123. Storage 123 stores format data FM, which represents at least some of the formats of the patient's medical history, associated with the user of the client device 11. In other words, if multiple users are using the document creation support system 10, multiple sets of format data FM are stored in storage 123.

[0039] The storage device 123 is a memory device implemented by semiconductor memory, a hard disk drive, a magnetic tape drive, etc. The processor 122 and the storage device 123 may be mounted in a common enclosure, or they may be provided in a distributed manner in separate enclosures.

[0040] As illustrated in Figure 4, the screen 113a displayed on the user interface 113 includes a medication history display area 113d. In response to selecting the medication history creation request button image 113c, the text of the medication history created by the generative artificial intelligence 130 based on the text entered in the text input area 113b is displayed in the medication history display area 113d. In this example, the text containing content corresponding to the S item, O item, A item, P item, and OP item is displayed in the medication history display area 113d.

[0041] The required format for patient medication history may vary from user to user. Figure 5 illustrates a case where a patient medication history written in the format of an alternative example is displayed in the patient medication history display area 113d. The patient medication history in this example includes "Patient Information" items, "Evaluation" items, "Instruction" items, and "Next Visit Confirmation" items. The "Patient Information" item is structured to include content corresponding to the above-mentioned S and O items. The "Evaluation" item, "Instruction" item, and "Next Visit Confirmation" item are structured to include the above-mentioned A, P, and OP items, respectively.

[0042] If the first user wishes to display the medication history in the format illustrated in Figure 4, authentication data for authenticating the first user or the client device 11 used by the first user is stored in storage 123, associated with the format data FM corresponding to that format.

[0043] Similarly, if a second user wishes to display their medication history in the format illustrated in Figure 5, authentication data for authenticating the second user or the client device 11 used by the second user is stored in storage 123, associated with the format data FM corresponding to that format.

[0044] As used in this disclosure, the term "format" generally includes not only the method of recording medication history but also any format that can specify the appearance of the medication history as a document. Examples of such formats include the number of characters, font size, font type, writing style, number of items, recording rules, and level of detail of the recorded content.

[0045] The storage of such information in storage 123 is performed in advance by a user of the client device 11 or server device 12 through a predetermined registration process.

[0046] The processor 112 of the client device 11 sends authentication data from the communication interface 111 prior to or concurrently with the transmission of the dialogue data DL. The processor 122 of the server device 12 performs user authentication processing for the client device 11 based on this authentication data. Specifically, it checks whether authentication data matching the authentication data received via the communication interface 121 is stored in the storage 123. If a match in the authentication data is confirmed, user authentication is successful.

[0047] Once user authentication is successful, as illustrated in Figure 3, the processor 122 reads the format data FM associated with the authentication data for that user from the storage 123 (STEP 23), and modifies the medical history preparation data HP based on the read format data FM (STEP 24).

[0048] For example, if the retrieved format data FM specifies the format exemplified in Figure 4, the text corresponding to the medication history preparation data HP will be modified so that it is displayed in the medication history display area 113d in that format.

[0049] Similarly, if the retrieved format data FM specifies the format exemplified in Figure 5, the text corresponding to the medication history preparation data HP will be modified so that it is displayed in the medication history display area 113d in that format.

[0050] As illustrated in Figure 3, the processor 122 of the server device 12 is configured to send the corrected medication history preparation data HP' from the communication interface 121 to the client device 11 (STEP 25). The corrected medication history preparation data HP' is received by the communication interface 111 of the client device 11.

[0051] The processor 112 of the client device 11 is configured to generate medical history data based on the modified medical history preparation data HP' (STEP 13). The medical history data is configured to display the text corresponding to the modified medical history preparation data HP' in the medical history display area 113d in a specified format.

[0052] The display of medication history on a screen is just one example of how medical documents can be provided. Medication history may also be provided through projection using a projector or printing using a printer.

[0053] In other words, the processor 122 of the server device 12 makes it possible for the client device 11 to provide at least a portion of the medical history corresponding to the medical history preparation data HP in a format corresponding to the format data FM.

[0054] According to the configuration of this embodiment, it is possible to provide the client device 11 with at least a portion of the patient's medication history based on the dialogue between the healthcare professional and the patient, and to provide it in a format desired by the user of the client device 11. This enhances the support for the task of creating patient medication history based on the dialogue between the healthcare professional and the patient. Healthcare professionals can then redirect the effort previously required for this task to, for example, patient care, thus increasing the possibility of addressing the social challenge of "shifting from medication-centered work to patient-centered work."

[0055] Figure 6 shows another example of the processing flow performed by the document creation support system 10. Elements common to the processing flow described with reference to Figure 3 are given the same reference numerals, and redundant explanations are omitted.

[0056] In this example, the processor 122 of the server device 12 is configured to transmit the format data FM read from the storage 123, along with the medication history preparation data HP received from the service provision device 13, to the client device 11 via the communication interface 121 (STEP 26). The transmitted medication history preparation data HP and format data FM are received by the communication interface 111 of the client device 11.

[0057] In this example, the processor 112 of the client device 11 is configured to modify the medication history preparation data HP based on the received format data FM (STEP 14). The modification is performed in the same manner as the process in STEP 24, which was explained with reference to Figure 3.

[0058] In other words, the corrected medication history preparation data HP' is acquired by the client device 11. Subsequently, the processor 112 generates medication history data based on the corrected medication history preparation data HP' (STEP 13).

[0059] Even with this configuration, the processor 122 of the server device 12 can provide at least a portion of the medical history corresponding to the medical history preparation data HP to the client device 11 in a format corresponding to the format data FM.

[0060] In addition, since the format data FM can be set so that the medication history preparation data HP can be modified on the client device 11, it may be possible to customize the format to conform to the specifications of the client device 11.

[0061] Figure 7 shows another example of the processing flow performed by the document creation support system 10. Elements common to the processing flow described with reference to Figure 6 are given the same reference numerals, and redundant explanations are omitted.

[0062] In this example, the processor 122 of the server device 12 is configured to cause the generative artificial intelligence 130 of the service provision device 13 to generate medication history preparation data HP based on dialogue data DL and format data FM.

[0063] Specifically, when the processor 122 has authenticated the user of the client device 11 based on the authentication data received from the client device 11, it reads the format data FM associated with that user from the storage 123 (STEP 27). Subsequently, the processor 122 creates prompt data PR based on the dialogue data DL received from the client device 11 and the format data FM read from the storage 123 (STEP 28).

[0064] For example, if the retrieved format data FM identifies a format exemplified in Figure 4, the prompt data PR is configured to correspond to at least one prompt that causes the generative artificial intelligence 130 to generate medication history preparation data HP so that the medication history created based on the dialogue corresponding to the dialogue data DL is written in that format.

[0065] As an alternative example, if the retrieved format data FM identifies a format as illustrated in Figure 5, the prompt data PR is configured to correspond to at least one prompt that causes the generative artificial intelligence 130 to generate medication history preparation data HP so that the medication history created based on the dialogue corresponding to the dialogue data DL is written in that format.

[0066] In other words, in this example, the prompt data PR input to the generative artificial intelligence 130 is dynamically changed in advance according to the format data FM associated with the user of the client device 11.

[0067] The created prompt data PR is transmitted from the communication interface 121 of the server device 12 to the service provider device 13 (STEP 29). The transmitted prompt data PR is received by the communication interface 131 of the service provider device 13.

[0068] The processor 132 of the service provision device 13 generates medication history preparation data HP by inputting prompt data PR received via the communication interface 131 to the generative artificial intelligence 130 (STEP 31).

[0069] The generated medication history preparation data HP is transmitted from the communication interface 131 to the server device 12 (STEP 32). The transmitted medication history preparation data HP is received by the communication interface 121 of the server device 12.

[0070] The processor 122 of the server device 12 transmits the medication history preparation data HP received from the service provision device 13 to the client device 11 via the communication interface 121 (STEP 20). The transmitted medication history preparation data HP is received by the communication interface 111 of the client device 11.

[0071] The processor 112 of the client device 11 generates medication history data based on the medication history preparation data HP received from the server device 12 (STEP 15).

[0072] Even with this configuration, the processor 122 of the server device 12 can provide at least a portion of the medical history corresponding to the medical history preparation data HP to the client device 11 in a format corresponding to the format data FM.

[0073] In addition, since the prompts input to the generative artificial intelligence 130 are modified based on the format data FM, the format of the generated medical history can be customized more flexibly. For example, it becomes easier to be freed from the structural constraints of the SOAP format and to specify the number of characters and writing style.

[0074] The processor 122 of the server device 12 may be configured to allow editing of format data FM stored in storage 123 if the user of the client device 11 satisfies predetermined authentication conditions. Examples of predetermined authentication conditions include administrator privileges. Information related to privileges is stored in storage 123 in advance in association with the authentication data. The processor 122 compares the authentication data transmitted from the client device 11 with the authentication data stored in storage 123 to determine whether the authentication conditions are satisfied.

[0075] Editing the format data FM involves initializing the format, modifying or deleting at least part of the initialized format, and adding new formats. Editing instructions for the format data FM are entered through the user interface 113. As illustrated in Figure 2, the editing data ED corresponding to the editing instructions is transmitted from the communication interface 111 to the server device 12.

[0076] The transmitted editing data ED is received by the communication interface 121 of the server device 12. The processor 122 applies the changes corresponding to the editing data ED to the formatting data FM stored in the storage 123.

[0077] This configuration allows the user of the client device 11 to have a greater degree of customization freedom regarding the format of the medical history records that are created.

[0078] Each of the processors 112 of the client device 11, 122 of the server device 12, and 132 of the service provision device 13, which have the various functions described above, can be implemented by at least one general-purpose microprocessor operating in cooperation with at least one general-purpose memory. Examples of general-purpose microprocessors include CPUs, MPUs, and GPUs. Examples of general-purpose memory include ROMs and RAMs. In this case, the ROM may store a computer program that performs the processing described above. ROM is an example of a non-temporary computer-readable medium in which a computer program is stored. The general-purpose microprocessor selects at least a portion of the program stored in the ROM and loads it onto the RAM, and then works with the RAM to execute the processing described above. The computer program may be pre-installed in the general-purpose memory, or it may be downloaded from an external server device via a communication network and then installed in the general-purpose memory. In this case, the external server device is an example of a non-temporary computer-readable medium in which a computer program is stored.

[0079] Each of processors 112, 122, and 132 may be implemented by at least one dedicated integrated circuit capable of executing the above-described computer program. Examples of dedicated integrated circuits include microcontrollers, ASICs, FPGAs, etc. In this case, the above-described computer program is pre-installed in a memory element included in the dedicated integrated circuit. The memory element is an example of a computer-readable medium in which the computer program is stored. Each of processors 112, 122, and 132 can also be implemented by a combination of a general-purpose microprocessor and a dedicated integrated circuit.

[0080] The configurations described herein are merely examples to facilitate understanding of this disclosure. Each configuration example may be modified or combined with other configuration examples as appropriate, as long as it does not deviate from the intent of this disclosure.

[0081] In the above embodiment, the service provision device 13 is installed at a location separate from the server device 12. In this case, the administrators of the server device 12 and the service provision device 13 may be the same or different. At least a portion of the functions provided by the processor 132 of the service provision device 13 may be provided by the processor 122 of the server device 12.

[0082] The medication history preparation data HP in the processing example described with reference to Figure 7 may be obtained through multiple inputs to the generative artificial intelligence 130. That is, the text may be modified or altered by re-inputting data corresponding to the text related to the medication history generated based on the input of prompt data PR into the generative artificial intelligence 130. When re-inputting, prompt data PR corresponding to a different prompt than the previous one may also be used.

[0083] The configurations listed below also constitute part of this disclosure. Item 1: A server device capable of communicating with client devices, An interface that accepts dialogue data corresponding to at least a portion of the dialogue between healthcare professionals and patients, A processor that causes generative artificial intelligence to generate document preparation data for creating at least a portion of medical documents based on the aforementioned dialogue data, A storage device that stores format data representing the format of at least some of the medical documents, associated with the user of the client device; It is equipped with, The processor enables the client device to provide at least a portion of the medical documents corresponding to the document preparation data in a format corresponding to the format data. Server device. Item 2: The processor modifies the document preparation data based on the format data and transmits the modified document preparation data to the client device, thereby causing the client device to output at least a portion of the medical document in the format. The server device described in item 1. Item 3: The processor transmits the document preparation data and the format data to the client device, thereby enabling the client device to provide at least a portion of the medical documents in the format. The server device described in item 1. Item 4: The processor causes the generative artificial intelligence to generate the document preparation data based on the dialogue data and the format data, and transmits the document preparation data to the client device, thereby causing the client device to output at least a portion of the medical document in the format. The server device described in item 1. Item 5: The processor allows the user to edit the format data if the user satisfies predetermined authentication conditions. A server device as described in any one of items 1 through 4. Item 6: The aforementioned medical documents include the patient's medication history, A server device as described in any one of items 1 through 5. [Explanation of Symbols]

[0084] 11: Client device, 12: Server device, 121: Communication interface, 122: Processor, 123: Storage, 130: Generative artificial intelligence, DL: Dialogue data, FM: Format data, HP: Medication history preparation data, HP': Modified medication history preparation data, PR: Prompt data

Claims

1. A server device capable of communicating with client devices, An interface that accepts dialogue data corresponding to at least a portion of the dialogue between healthcare professionals and patients, A processor that causes generative artificial intelligence to generate document preparation data for creating at least a portion of medical documents based on the aforementioned dialogue data, A storage device that stores format data representing the format of at least some of the medical documents, associated with the user of the client device; It is equipped with, The processor enables the client device to provide at least a portion of the medical documents corresponding to the document preparation data in a format corresponding to the format data. Server device.

2. The processor modifies the document preparation data based on the format data and transmits the modified document preparation data to the client device, thereby causing the client device to output at least a portion of the medical document in the format. The server device according to claim 1.

3. The processor transmits the document preparation data and the format data to the client device, thereby enabling the client device to provide at least a portion of the medical documents in the format. The server device according to claim 1.

4. The processor causes the generative artificial intelligence to generate the document preparation data based on the dialogue data and the format data, and transmits the document preparation data to the client device, thereby causing the client device to output at least a portion of the medical document in the format. The server device according to claim 1.

5. The processor allows the user to edit the format data if the user satisfies predetermined authentication conditions. The server device according to claim 1.

6. The aforementioned medical documents include the patient's medication history, The server device according to claim 1.

7. A computer program that can be executed by a processor installed in a server device capable of communicating with a client device, By being executed, the server device will We accept dialogue data that corresponds to at least a portion of the conversations that take place between healthcare professionals and patients. Based on the aforementioned dialogue data, the generative artificial intelligence generates document preparation data for creating at least a portion of the medical documents. Format data representing the format of at least some of the medical documents is stored in association with the user of the client device. The client device makes it possible to provide at least a portion of the medical documents corresponding to the document preparation data in a format corresponding to the format data. Computer program.

8. A method for assisting the creation of medical documents, which is performed by a client device and a server device, The client device transmits dialogue data corresponding to at least a portion of the dialogue between the medical professional and the patient to the server device. In the server device, the generative artificial intelligence generates document preparation data for creating at least a portion of medical documents based on the dialogue data. The server device maintains format data representing the format of at least a portion of the medical documents, associated with the user of the client device. In the aforementioned client device, at least a portion of the medical document corresponding to the document preparation data is output in a format corresponding to the format data. Methods for assisting with the creation of medical documents.

Citation Information

Patent Citations

  • Medication counseling support device, medication counseling support method, and medication counseling support program

    JP2021064161A