WO2022176936A1 - 処方支援システム、処方支援方法、情報処理装置、通信端末およびそれらの方法およびプログラム - Google Patents

処方支援システム、処方支援方法、情報処理装置、通信端末およびそれらの方法およびプログラム Download PDF

Info

Publication number
WO2022176936A1
WO2022176936A1 PCT/JP2022/006315 JP2022006315W WO2022176936A1 WO 2022176936 A1 WO2022176936 A1 WO 2022176936A1 JP 2022006315 W JP2022006315 W JP 2022006315W WO 2022176936 A1 WO2022176936 A1 WO 2022176936A1
Authority
WO
WIPO (PCT)
Prior art keywords
prescription
patient
symptoms
dispensing
attributes
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2022/006315
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
雄士 山本
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Minacare Co Ltd
Original Assignee
Minacare Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Minacare Co Ltd filed Critical Minacare Co Ltd
Publication of WO2022176936A1 publication Critical patent/WO2022176936A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients

Definitions

  • the present invention relates to a prescription support system, a prescription support method, an information processing device, a communication terminal, and methods and programs thereof.
  • Patent Document 1 discloses that an electronic medical record server stores electronic medical record information from a plurality of medical institutions and statistical information that associates symptoms with prescription drugs, and symptoms can be input from an electronic medical record input screen.
  • a technique is disclosed in which, upon input, associated prescription drugs are retrieved and displayed as prescription drug reference information.
  • the symptoms are associated with the prescription drug based on the electronic medical record information, and the quality of the electronic medical record information varies depending on the doctor, and the dispensing is not inspected. Medication reference could not be provided.
  • An object of the present invention is to provide a technology that solves the above problems.
  • the prescription assistance system comprises: a receipt data acquisition unit that acquires receipt data including medical receipts and dispensing receipts; a database for linking and accumulating patient attributes, the patient's symptoms or disease name, and the patient's dispensing drug set dispensed according to the symptom or disease name based on the receipt data; a medical examination information acquisition unit that acquires patient attributes and symptoms or disease names input by a doctor; a prescription medicine set presentation unit that refers to the database and presents to the doctor at least one prescription medicine set corresponding to the patient's attributes and symptoms or disease names acquired by the examination information acquisition unit; Prepare.
  • the prescription assistance method comprises: a receipt data acquisition step of acquiring receipt data including a medical receipt and a dispensing receipt; an accumulating step of linking patient attributes, symptoms or disease names of the patients, and a set of dispensed medicines for the patients dispensed according to the symptoms or disease names based on the receipt data, and accumulating them in a database; a medical examination information acquisition step of acquiring the patient's attributes and symptoms or disease names input by the doctor; a prescription medicine set presenting step of referring to the database and presenting to the doctor at least one prescription medicine set corresponding to the patient's attributes and symptoms or disease names acquired by the examination information acquisition unit; including.
  • an information processing device includes: a receipt data acquisition unit that acquires receipt data including medical receipts and dispensing receipts; a dispensed medicine set extracting unit that associates patient attributes, symptoms or disease name of the patient, and the patient's dispensed medicine set dispensed according to the symptom or disease name based on the receipt data; a storage instruction unit for storing the attribute, the symptom or disease name, and the dispensing drug set linked by the dispensing drug set extracting unit in a database so as to be searchable by the attribute and the symptom or disease name; Prepare.
  • an information processing method comprises: a receipt data acquisition step of acquiring receipt data including a medical receipt and a dispensing receipt; A dispensed medicine set extracting step of linking a patient attribute, a symptom or disease name of the patient, and a dispensed medicine set of the patient dispensed according to the symptom or disease name based on the receipt data; a storage instruction step of storing the attribute, the symptom or disease name, and the dispensing drug set associated in the dispensing drug set extraction step in a database so as to be searchable by the attribute and the symptom or disease name; including.
  • an information processing program comprises: a receipt data acquisition step of acquiring receipt data including a medical receipt and a dispensing receipt; A dispensed medicine set extracting step of linking a patient attribute, a symptom or disease name of the patient, and a dispensed medicine set of the patient dispensed according to the symptom or disease name based on the receipt data; a storage instruction step of storing the attribute, the symptom or disease name, and the dispensing drug set associated in the dispensing drug set extraction step in a database so as to be searchable by the attribute and the symptom or disease name; run on the computer.
  • an information processing device includes: Based on receipt data including medical receipts and dispensing receipts, the attributes of the patient, the symptoms or disease name of the patient, and the patient's dispensed drug set dispensed according to the symptom or disease name are linked and accumulated.
  • a database a medical examination information acquisition unit that acquires patient attributes and symptoms or disease names input by a doctor; a prescription medicine set presentation unit that refers to the database and presents to the doctor at least one prescription medicine set corresponding to the patient's attributes and symptoms or disease names acquired by the examination information acquisition unit; Prepare.
  • an information processing method comprises: a medical examination information acquisition step of acquiring patient attributes and symptoms or disease name entered by a doctor; Based on receipt data including medical receipts and dispensing receipts, the attributes of the patient, the symptoms or disease name of the patient, and the patient's dispensed drug set dispensed according to the symptom or disease name are linked and accumulated.
  • a prescription medicine set presenting step of referring to a database and presenting to the doctor at least one prescription medicine set corresponding to the patient's attributes and symptoms or disease names acquired by the examination information acquisition unit; including.
  • an information processing program comprises: a medical examination information acquisition step of acquiring patient attributes and symptoms or disease name entered by a doctor; Based on receipt data including medical receipts and dispensing receipts, the attributes of the patient, the symptoms or disease name of the patient, and the patient's dispensed drug set dispensed according to the symptom or disease name are linked and accumulated.
  • a prescription medicine set presenting step of referring to a database and presenting to the doctor at least one prescription medicine set corresponding to the patient's attributes and symptoms or disease names acquired by the examination information acquisition unit; run on the computer.
  • a communication terminal includes: a first display unit for displaying an input screen for accepting input of at least patient attributes and symptoms or disease names; a transmitting unit configured to transmit to a server at least the patient's attributes and the symptom or disease name input from the input screen; Based on receipt data including medical receipts and dispensing receipts, patient attributes, the patient's symptoms or disease names, and the patient's dispensed drug set dispensed according to the symptoms or disease names are linked and accumulated.
  • a receiving unit that receives from the server at least one set of prescription drugs retrieved from the database based on at least the patient's attributes and the symptom or disease name; a second display unit that displays at least the patient's attributes and symptoms or disease name, and the at least one prescription drug set; Prepare.
  • an application program a first display step of displaying on the display unit an input screen for accepting input of at least patient attributes and symptoms or disease names; a sending step of sending to a server at least the patient's attributes and the symptom or disease name input from the input screen; A patient attribute, a symptom or disease name of the patient, and a set of dispensed medicines for the patient dispensed according to the symptom or disease name are linked and accumulated in the issuer of the claim data including the medical receipt and the dispensing receipt.
  • a highly reliable prescription drug set can be presented.
  • FIG. 10 is a diagram showing the configuration of receipt data according to the second embodiment;
  • FIG. 10 is a diagram showing the configuration of a search database according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for adults according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for adults according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for adults according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for adults according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for infants and children according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for infants and children according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for infants and children according to the second embodiment;
  • FIG. 11 is a diagram showing large classification/small classification for infants and children according to the second embodiment;
  • FIG. 11 is a diagram showing major classification/small classification in gynecology according to the second embodiment;
  • FIG. 11 is a diagram showing major classification/small classification in gynecology according to the second embodiment;
  • FIG. 11 is a diagram showing major classification/small classification in gynecology according to the second embodiment;
  • FIG. 11 is a diagram showing major classification/small classification in gy
  • FIG. 11 is a diagram showing major classification/small classification in gynecology according to the second embodiment;
  • FIG. 11 is a diagram showing major classification/small classification in gynecology according to the second embodiment; It is a flowchart which shows the processing procedure of the dispensing medicine set extraction part which concerns on 2nd Embodiment.
  • FIG. 9 is a block diagram showing the functional configuration of an information processing device as a dispensing information search server according to the second embodiment;
  • FIG. 11 is a diagram showing the configuration of a search result acquisition table according to the second embodiment;
  • FIG. 10 is a flow chart showing a processing procedure of a dispensing information search server according to the second embodiment;
  • FIG. 9 is a block diagram showing the functional configuration of a communication terminal according to the second embodiment;
  • FIG. 9 is a flow chart showing a processing procedure of a communication terminal according to the second embodiment;
  • FIG. 12 is a diagram showing the configuration of a search database according to the third embodiment;
  • FIG. 12 is a diagram showing the configuration of a claim issuer weighting table according to the fourth embodiment. It is a figure which shows the search-results display screen of the communication terminal in the prescription assistance system which concerns on 5th Embodiment.
  • a set of medicines dispensed at a pharmacy based on receipt data is called a set of medicines dispensed
  • a set of medicines presented to assist doctors is called a set of prescription medicines.
  • a prescription assistance system 100 as a first embodiment of the present invention will be described with reference to FIG.
  • the prescription assistance system 100 is a system that assists doctors in issuing prescriptions.
  • the prescription support system 100 includes a receipt data acquisition unit 101, a database 102, a medical examination information acquisition unit 103, and a prescription medicine set presentation unit 104.
  • the receipt data acquisition unit 101 acquires receipt data including medical receipts and dispensing receipts.
  • the database 102 associates and accumulates the patient's attribute 121, the patient's symptom or disease name 122, and the patient's dispensing drug set 123 dispensed according to the symptom or disease name 122.
  • the medical examination information acquisition unit 103 acquires the patient's attribute and symptoms or disease name input by the doctor 110 .
  • the prescription drug set presenting unit 104 refers to the database 102 and presents to the doctor 110 at least one prescription drug set 143 corresponding to the patient's attribute 141 and the symptom or disease name 142 acquired by the examination information acquiring unit 103. .
  • the receipt data including medical receipts and dispensing receipts is used, there is no variation in the quality of the information, the dispensing has been checked, and a highly reliable set of prescription drugs can be presented.
  • a prescription support system based on receipt data including medical receipts and dispensing receipts, when patient attributes, diseases or symptoms are entered as search conditions, a prescription drug set that serves as a reference for prescriptions issued by doctors is exemplified.
  • the prescription medicine sets are listed in descending order of appearance frequency. Also, when the doctor designates medicines to be included or not to be included in the search results, a prescription medicine set corresponding to the designation is presented.
  • FIG. 2A is a diagram showing a display screen of communication terminal 210 in the prescription support system according to this embodiment.
  • FIG. 2A shows a prescription search screen 211 for a doctor to request a prescription drug set search based on patient attributes, patient symptoms or disease names, and a search result screen 212 for displaying the search result prescription drug sets.
  • patient's generation is input to the prescription search screen 211 as a patient attribute.
  • hierarchized "disease/symptom major classification” and "minor classification” are input as the patient's symptom or disease name.
  • major classification and “minor classification” are classifications according to the classification table newly generated in this embodiment shown in FIGS. 6D to 6O below. With such classification, it is possible to input patient symptoms that are not biased by doctors as search conditions.
  • the prescription search screen 211 of FIG. 2A allows the physician to specify drugs to be included in the search results. It is also possible to specify medicines that should not be included in the search results based on the patient's allergies or medical history.
  • the input conditions in the prescription search screen 211 are not limited to FIG. 2A.
  • the search result screen 212 displays a summary of the search conditions, the search results, and their prescription drug sets.
  • the search result screen 212 of FIG. 2A there are 32 search results, and outlines of the searched prescription medicine sets are displayed in order of frequency.
  • FIG. 2B is a diagram showing a display screen 213 of detailed contents of each prescription medicine set, which is a search result of the communication terminal 210 in the prescription support system according to this embodiment.
  • the display screen 213 presents combinations of the same set of prescribed medicines with different usages/dosages and prescription days.
  • the drug information of that prescription drug is displayed in more detail.
  • the usage/dosage and prescription days of the prescription drug in FIG. 2B are taken into consideration.
  • information such as an indication master linked to an external master (medical information center, etc.) can also be written together.
  • FIG. 2C is a diagram showing display screens 214 and 215 of the communication terminal 210 for feeding back the doctor's evaluation of each prescription set that is the search result.
  • Display screen 214 is a screen where the doctor selects "Dood! and gives feedback on the evaluation.
  • the display screen 215 is a screen on which the doctor selects "Bad! and feeds back the bad evaluation. The doctor's evaluation result fed back is reflected in subsequent searches for prescription drug sets by changing the weighting.
  • FIG. 3A is a diagram showing the configuration of a prescription support system 300 according to this embodiment.
  • the prescription support system 300 includes a general-purpose communication terminal 210 used by doctors 381 to 38n and a prescription information providing server 330, which are connected by a network 390.
  • the prescription support system 300 also includes a dispensing information search server 320 and a payment processing server 370 that are connected to the prescription information providing server 330 .
  • the prescription information providing server 330, the dispensing information search server 320, and the payment processing server 370 may be implemented as a server in which any one of them is integrated.
  • the prescription support system 300 includes a dispensing medicine set extraction unit 340, a DWH (data warehouse) 350, and an external master 360, which are connected via a network 390 or not via the network 390.
  • the DWH 350 includes the Ministry of Health, Labor and Welfare, medical institutions, pharmacies, and the like.
  • the external master 360 includes a medical information center and the like.
  • the prescription information providing server 330 presents to the communication terminal 210, according to the search conditions input from the communication terminal 210, past prescription drug sets by other doctors searched by the dispensing information search server 320 as a reference. Based on the data from the DWH 350 and the external master 360, the dispensing information search server 320 searches the dispensing medicine set from the search database generated by the dispensing medicine set extraction unit 340 using the patient's attributes, symptoms, or disease name as search keys. do. The settlement processing server 370 also settles the service charge for the communication terminal 210 .
  • FIG. 3B is a block diagram showing the functional configuration of the prescription support system 300 according to this embodiment.
  • the same reference numerals are given to the same components as in FIG. 3A.
  • doctors 381-38n of FIG. 3A are represented as doctor 380 in FIG. 3B.
  • a prescription support application (prescription support app in the figure) 310 is installed in the communication terminal 210 .
  • the prescription information providing server 330 stores a member database for registering the doctor 380, an application record for storing a search application for a prescription medicine set from the communication terminal 210, a search result for holding search results, and notifications to the doctor 380. It has a list of notifications to be held.
  • the prescription information providing server 330 has an inquiry function for inquiring the dispensing information search server 320 about a search application.
  • the dispensing information search server 320 has a search database 321, and has a response function for responding to a search application inquiry from the prescription information providing server 330, and sends a search code according to the search conditions to the search database 321 to obtain search results. and a search engine that acquires and replies to the prescription information providing server 330.
  • the contents of the search database 321 are based on the medical product master 351 obtained from the DWH 350, the medical receipt data 352 including the medical department receipt and the dispensing receipt, and the indication master 361 obtained from the external master 360. It is extracted and generated by the dispensing medicine set extraction unit 340 .
  • FIG. 4 is a sequence diagram showing the operation procedure of the prescription support system 300 according to this embodiment.
  • the dispensing medicine set extraction unit 340 receives the receipt data and the medicine master from the DWH 350 in step S401. Also, the dispensed medicine set extraction unit 340 receives an indication master from the external master 360 in step S403. Dispensed medicine set extraction unit 340 accumulates these medical data in step S405. And the dispensed medicine set extraction part 340 extracts a dispensed medicine set based on the accumulated data in step S407.
  • FIG. 4 describes extraction of a set of dispensing drugs, in reality, a similar set of dispensing drugs is extracted based on data that serves as a search code (key), in this embodiment, the patient's attributes, symptoms, or disease name.
  • the extraction result of the dispensing medicine set is stored in the search database 321 .
  • the extraction result of the dispensed medicine set is sent to the dispensing information search server 320, and in step S409, a standardized search code (key) for searching the dispensed medicine set accumulated in the search database 321 is generated.
  • the generated search code is accumulated in the search database 321 so that the dispensing medicine set can be searched.
  • the prescription information providing server 330 generates a prescription search screen for entering search conditions corresponding to the generated search code.
  • FIG. 4 shows only the initial collection of receipt data, drug masters, and indication masters. However, collection of receipt data, drug masters, and indication masters, especially collection of receipt data, is continuously performed, and the search database 321 is updated. is learned so that it can be searched for.
  • step S421 the communication terminal 210, the prescription information providing server 330, and the dispensing information search server 320 start up the prescription support application.
  • a prescription assistance application may be configured to be downloaded to the communication terminal 210 and activated, or may be configured to be connected via a browser.
  • the doctor 380 performs registration for receiving prescription support from the communication terminal 210 in step S423.
  • the prescription information providing server 330 outputs the prescription search screen generated in step S411 to the communication terminal 210 in step S425.
  • a prescription search screen is displayed in step S427.
  • the doctor 380 inputs search conditions from the communication terminal 210 to the prescription search screen in step S429.
  • the search conditions are sent to the dispensing information search server 320 via the prescription information providing server 330 .
  • step S431 the dispensing information search server 320 converts the acquired search conditions into search codes for searching the search database 321 and sets them. Then, the dispensing information search server 320 instructs the search database 321 to perform search processing in step S433.
  • the search database 321 searches using a search code, and outputs the search results to the dispensing information search server 320 .
  • the search code corresponds to the patient's attribute and the patient's symptom or disease name
  • the search result is at least one dispensing drug set linked to the patient's attribute and the patient's symptom or disease name
  • a plurality of search results are If there is, it is output with frequency ranking.
  • the search result is directly fed back to the search database 321 or fed back from the dispensing medicine set extraction unit 340 to the search database 321 as in step S441, and the contents of the search database 321 are updated.
  • the dispensing information search server 320 returns the retrieved dispensing medicine set to the prescription information providing server 330 in step S435.
  • the prescription information providing server 330 generates a screen displaying the prescription medicine set of the search results, and transmits the screen to the communication terminal 210.
  • FIG. Communication terminal 210 displays the received prescription drug set as a result of the search.
  • the prescription information providing server 330 selects prescription drug sets containing drugs that the doctor 380 has instructed to include from the prescription drug sets of the search results, and on the other hand, includes drugs that the doctor 380 has instructed not to include.
  • the prescription set is omitted and displayed on communication terminal 210 .
  • step S443 when the doctor inputs an evaluation for each prescription drug set in the search results from the communication terminal 210, the contents of the search database 321 are fed back from the dispensing drug set extraction unit 340 to the search database 321 in step S445. is updated (see FIG. 2C).
  • FIG. 5 is a block diagram showing the functional configuration of the dispensing medicine set extraction unit 340 according to this embodiment.
  • the dispensing medicine set extraction unit 340 includes an input interface/communication control unit 501 , a medical data collection unit 502 , and a medical database 503 . Dispensed medicine set extraction unit 340 also includes extraction condition storage unit 504 , dispensed medicine set reading unit 505 , statistical processing unit 506 , and search data storage instructing unit 507 .
  • the input interface/communication control unit 501 controls connections for collecting data from the DWH 350 and the external master 360 .
  • the medical data collection unit 502 collects drug masters and receipt data from the DWH 350 and indication masters (drugs and corresponding disease name data) from the external master 360 via the input interface/communication control unit 501 .
  • the medical database 503 accumulates data collected by the medical data collecting unit 502 .
  • the extraction condition storage unit 504 stores extraction conditions corresponding to search conditions at the time of searching.
  • a dispensed medicine set reading unit 505 extracts a dispensed medicine set from the medical database 503 according to the extraction conditions stored in the extraction condition storage unit 504 .
  • the statistical processing unit 506 statistically processes the extracted set of dispensing medicines.
  • the frequency of appearance is obtained from the number of appearances of the same set of dispensing drugs extracted under similar extraction conditions, and the ranking is set in descending order of frequency of appearance.
  • the retrieval data storage instructing unit 507 instructs the retrieval database 321 to store the dispensing medicine sets retrieved by the retrieval conditions so that they are presented in descending order of appearance frequency.
  • the extraction condition storage unit 504 stores a classification table of large classification and small classification according to the present embodiment, which is added as a search key in the search database 321 in the subsequent processing.
  • FIG. 6A is a diagram showing data processed in the dispensing medicine set extraction unit 340 according to this embodiment.
  • the data collected and stored in the medical care database 503 includes receipt data 352 including medical receipts 353 and dispensing receipts 354, a medical product master 351, and an indication master 361.
  • the medical receipt 353 includes the patient's date of birth, diagnosed disease name, prescription information, and the like.
  • the dispensing receipt 354 includes prescription information, dispensing medical products, prescription quantity (corresponding to prescription days), usage/dosage, and the like.
  • the medical product master 351 includes standards and drug prices for each medical product.
  • the indication master 361 stores correspondence between existing medical products and indications.
  • the dispensing drug set search table 622 accumulated in the search database 321 includes generation, symptom, dispensing drug set information, frequency order of dispensing drug set, usage/dosage, number of prescription days, etc. as patient attributes.
  • FIG. 6B is a diagram showing the structure of the receipt data according to this embodiment.
  • the receipt data includes a medical receipt 353 and a dispensing receipt 354 .
  • the upper diagram of FIG. 6B shows an example of the format of the medical receipt 353 and an example of data items that can be extracted from the medical receipt 353.
  • “date of medical treatment” is obtained from the medical treatment date column of the medical receipt 353, "name (patient ID)", “sex”, and “age” are read from the patient column, and " Name of medical institution (facility ID)", “Location”, “Number of beds”, and “Department” are obtained.
  • "name of injury”, “name of suspected disease”, “date of treatment start”, “actual number of days of treatment", and “outcome” are obtained from the injury and disease column of the medical receipt 353, and the "medical product name” and "administration name” of the prescription are obtained from the summary column.
  • the lower diagram of FIG. 6B shows a format example of the dispensing receipt 354 and an example of data items that can be extracted from the dispensing receipt 354.
  • "dispensing date” is obtained from the dispensing date column of the dispensing receipt 354
  • "name (patient ID)", “gender”, and "age” are obtained from the patient column
  • "pharmacy name” is obtained from the pharmacy column.
  • (facility ID)" and “location” are obtained, and from the medical institution column, "medical institution name (facility ID)", “location”, and “doctor name” are obtained.
  • the data obtained from the medical receipt 353 and the data obtained from the dispensing receipt 354 are collated to link the patient's attributes, the patient's symptoms or disease name, and the dispensing medicine set.
  • FIG. 6C is a diagram showing the configuration of the search database 321 according to this embodiment.
  • the search database 321 is a database for accumulating sets of dispensed medicines in such a manner that patient attributes and symptoms or disease names of patients are used as search keys, and sets of dispensed medicines arranged in order of frequency are output as search results.
  • the search database 321 stores at least one piece of dispensing drug set information 603 in association with the patient's attribute 601 and the patient's symptom or disease name 602 .
  • the patient attributes 601 include sex and generation, but "sex" is optional in this embodiment. Generations are, for example, infants/children and adults. In addition, gynecology (pregnant women) is another independent attribute. In addition, by using the major classification and minor classification proposed in this embodiment as the patient's symptoms or disease name 602, individual differences due to medical doctors are absorbed, and the database is free of bias. Note that the attributes are not limited to this example, and the method of dividing generations is not limited to this example either.
  • the order of appearance frequency 604 is stored.
  • a plurality of dispensed medicines 605 are stored corresponding to each dispensed medicine set information 603, and each dispensed medicine 605 stores usage/dose 606, number of prescription days 607, and medical product information 608 acquired from the medical product master. do.
  • Figures 6D-6O are diagrams showing generational and gynecological major and minor categories used in this embodiment.
  • Figures 6D-6G show adult major and minor classification tables 621
  • Figures 6H-K show infant and pediatric major and minor classification tables 622
  • a table 623 of categories and subcategories is shown.
  • the usability of the search is improved by searching for the same symptom (small category) in different major categories.
  • the existing disease classification table for example, ICD10
  • the structure of disease classification means the method of grouping diseases, and this grouping is not only based on symptoms, but also on the basis of similarities in the causes and parts of diseases, so it is not always possible to It doesn't match your thought pattern.
  • the applicable disease name and the disease name described in the disease classification do not necessarily match, it is expected that there will be variations in the notation of the input keyword at the time of searching.
  • the names of diseases and symptoms that frequently appear in the field are listed from the viewpoint of the field and combined with the names of applicable diseases and the like.
  • FIG. 7 is a flowchart showing the processing procedure of the dispensing medicine set extraction unit 340 according to this embodiment. This flowchart is executed by the CPU that controls the dispensed medicine set extraction unit 340 using the RAM, and implements the constituent elements of the dispensed medicine set extraction unit 340 in FIG.
  • the dispensing medicine set extraction unit 340 acquires an existing indication master from the external master 360 in step S701. Dispensed medicine set extraction unit 340 acquires a medicine master from DWH 350 in step S703. In step S707, the dispensed medicine set extraction unit 340 initializes search conditions and prescribed medicine sets in the search database 321 having the configuration shown in FIG. 6C from the existing indication master and medical product master.
  • the dispensing medicine set extraction unit 340 acquires the medical receptor from the DWH 350 in step S709, and acquires the dispensing receptor in step S711. It should be noted that, if the medical receptor and the dispensing receptor have already been combined, both the receipts are obtained in step S710. In step S713, the dispensed medicine set extraction unit 340 associates patient attributes, symptoms or disease names, and dispensed medicine sets based on the medical receptor and the dispensing receptor. At this time, the major classification and minor classification of this embodiment are used as symptoms or disease names to improve search results.
  • step S715 the dispensing medicine set extraction unit 340 determines whether there is a new medicine in the dispensing medicine set extracted from the receipt. Then, if there is a new medicine in the dispensing medicine set, the dispensing medicine set extraction unit 340 acquires information on the new medicine from the medicine master of the DWH 350 in step S717. It is also useful to separately collect dispensing histories of new medicines and present them to doctors.
  • step S719 the dispensed medicine set extraction unit 340 performs statistical processing such as setting the ranking from the frequency of appearance of the dispensed medicine set under similar conditions of patient attributes and symptoms or disease names. Then, in step S721, the dispensed medicine set extraction unit 340 updates the search database 321 by adding the information of the dispensed medicine set based on the newly acquired receipt data to the search database 321. FIG. If there is little claim data, the reliability of the search database 321 is low, so the dispensing medicine set extraction unit 340 determines in step S723 whether the claim data is sufficient.
  • step S709 S710
  • the dispensing medicine set extraction unit 340 enables search use of the search database 321 in step S725.
  • Dispensed medicine set extraction unit 340 determines whether to suspend or terminate the dispensing medicine set extraction process, and continues the processes of steps S709 (S710) to S727 unless an instruction to suspend or terminate the dispensing medicine set extraction process is given. Learning in the search database 321 is advanced repeatedly.
  • Dispensing information search server> 8 to 10 the configuration and operation of the information processing apparatus as the dispensing information search server 320 for searching for a dispensing drug set based on patient attributes, symptoms or disease name of the patient will be described below.
  • FIG. 8 is a block diagram showing the functional configuration of the dispensing information search server 320 according to the second embodiment.
  • the dispensing information search server 320 includes an application interface (API) 801, a search condition acquisition unit 802, a search code (formula) generation unit 803, a search result acquisition unit 804, and a search result response unit 805.
  • API application interface
  • search condition acquisition unit 802 a search condition acquisition unit 802
  • search code (formula) generation unit 803 a search result acquisition unit 804
  • An application interface (API) 801 controls data exchange with the prescription information providing server 330 that connects to the communication terminal 210 and presents a set of prescription drugs.
  • the search condition acquisition unit 802 acquires search conditions input from the communication terminal 210 via the prescription information providing server 330 .
  • a search code (formula) generation unit 803 generates a search code (formula) capable of searching the search database 321 from the search conditions acquired by the search condition acquisition unit 802 .
  • the search result acquisition unit 804 has a search result acquisition table 841 , acquires the results of a search from the search database 321 using a search code (formula), and generates search results to reply to the prescription information providing server 330 .
  • the search result answering unit 805 answers the search results obtained and generated by the search result obtaining unit 804 to the prescription information providing server 330 .
  • FIG. 9 is a diagram showing the configuration of the search result acquisition table 841 according to this embodiment.
  • the search result acquisition table 841 is used by the search result acquisition unit 804 to organize the search results acquired from the search database 321 using the search code (formula) into an answer format.
  • the search result acquisition table 841 stores the dispensed medicine set information 903 ranked according to the frequency ranking 904 in the case of multiple search results, in association with the patient attribute 901 and the patient symptom or disease name 902 of the search condition. .
  • a plurality of dispensed medicines 905 are stored corresponding to each dispensed medicine set information 903, and each dispensed medicine 905 stores usage/dose 906, number of prescription days 907, and medical product information 908 acquired from the medical product master. do.
  • the gender in the patient attribute 901 is an option.
  • FIG. 10 is a flow chart showing the processing procedure of the dispensing information search server 320 according to this embodiment. This flowchart is executed by the CPU that controls the dispensing information search server 320 using the RAM, and implements the constituent elements of the dispensing information search server 320 in FIG.
  • the dispensing information search server 320 waits for a search request from the prescription information providing server 330 in step S1001. If there is a search request, the dispensing information search server 320 acquires search conditions from the prescription information providing server 330 in step S1003. Then, the dispensing information search server 320 converts the acquired search condition into a search code (formula) for searching the search database 321 in step S1005.
  • the dispensing information search server 320 searches the search database 321 using the search code (formula) in step S1007. Dispensing information search server 320 acquires the search result from search database 321 in step S1009. The dispensing information search server 320 replies the search result to the prescription information providing server 330 in step S1011. Dispensing information search server 320 determines to cancel the search process in step S1013, and repeats the search process of steps S1001 to S1013 if not canceled.
  • ⁇ Prescription information providing server> upon receiving a search request for a dispensing drug set from the communication terminal 210, a prescription information providing request is made to the dispensing information search server 320 and the search result is presented to the communication terminal 210.
  • the configuration and operation of an information processing device as server 330 will be described.
  • FIG. 11 is a block diagram showing the functional configuration of the prescription information providing server 330 according to this embodiment.
  • the prescription information providing server 330 includes a communication control unit 1101, a doctor information acquisition unit 1102, a member database 1103, a doctor authentication unit 1104, and an application interface 1105.
  • the prescription information providing server 330 also includes a search condition acquisition unit 1106 , a prescription search screen generation unit 1107 , and a prescription search screen transmission unit 1108 .
  • the prescription information providing server 330 includes a prescription search screen reception unit 1109, a search condition transmission unit 1110, a search result acquisition unit 1111, a prescription drug set selection instruction unit 1112, a prescription information screen generation unit 1113, prescription information and a screen transmission unit 1114 .
  • the communication control unit 1101 controls communication with the communication terminal 210.
  • the doctor information acquisition unit 1102 acquires, from the communication terminal 210, the information of the doctor who requests the presentation of the prescription medicine set using the communication terminal 210.
  • the member database 1103 registers the acquired doctor information.
  • the doctor authentication unit 1104 authenticates the requesting doctor using the member registration information of the member database 1103 when the doctor requests presentation of the prescription drug set.
  • Application interface 1105 controls connection with dispensing information retrieval server 320 .
  • the search condition acquisition unit 1106 acquires search conditions for the search database 321 from the dispensing information search server 320 .
  • the prescription search screen generation unit 1107 generates a prescription search screen for inputting search conditions to be displayed on the communication terminal 210 according to the acquired search conditions.
  • the prescription search screen transmission unit 1108 transmits the prescription search screen to the communication terminal 210 that started the prescription support application.
  • the prescription search screen receiving unit 1109 receives, from the communication terminal 210, a prescription search screen on which the doctor has set search conditions such as patient attributes, patient symptoms, or disease names.
  • the search condition transmission unit 1110 extracts search conditions such as attributes, patient's symptoms or disease name from the prescription search screen, transmits them to the dispensing information search server 320, and requests a search for a dispensed medicine set.
  • the search result acquisition unit 1111 acquires search results corresponding to the search conditions transmitted by the search condition transmission unit 1110 from the dispensing information search server 320 . If the prescription search screen received by the prescription search screen receiving unit 1109 contains instruction information for selecting a prescription drug set to be presented to the doctor from the dispensed drug sets of the search results, the prescription drug set selection instructing unit 1112 selects the prescription.
  • the information screen generation unit 1113 is instructed to select a prescription medicine set. For example, when drugs to be included in the search and drugs not to be included in the search result are set on the prescription search screen, the prescription drug set selection instruction unit 1112 selects a prescription drug set without a drug to be included in the search from the prescription information screen or a prescription drug set not to be included in the search. Delete a prescription drug set that has a drug.
  • the prescription information screen generation unit 1113 has a prescription information screen generation table 1131, and generates a prescription information screen from the acquired search results, taking into consideration the instructions of the prescription medicine set selection instruction unit 1112 as well.
  • the prescription information screen transmission unit 1114 transmits the generated prescription information screen to the communication terminal 210 that is the search source.
  • FIG. 12 is a diagram showing the configuration of the prescription information screen generation table 1131 according to this embodiment.
  • the prescription information screen generation table 1131 is used by the prescription information screen generation unit 1113 to generate a prescription information screen from the acquired search results.
  • the same reference numerals are given to the same components as those in FIG. 9, and redundant explanations are omitted.
  • the prescription information screen generation table 1131 displays a table 1210 for generating a screen for displaying search conditions, a table 1220 for generating a screen for displaying prescription drug sets of search results, and detailed information on prescription drugs. and a table 1230 for generating screens.
  • the table 1210 stores search condition display images 1211 in association with search conditions.
  • the table 1220 is associated with the prescription drug set of the search result, the prescription drug display image 1221, and the instruction from the prescription drug set selection instruction unit 1112, whether or not to display by specifying the "included medicine” for each prescription drug set ( ⁇ is displayed, x is not displayed) 1222, and whether or not display is possible by designating “medicine not included” (o is displayed, x is not displayed) 1223 is stored.
  • the table 1230 stores a medical product detail display image 1231 based on medical product information of prescription drugs.
  • FIG. 13 is a flow chart showing the processing procedure of the prescription information providing server 330 according to this embodiment. This flow chart is executed by the CPU that controls the prescription information providing server 330 using the RAM, and implements the constituent elements of the prescription information providing server 330 in FIG. 11 .
  • step S1311 the prescription information providing server 330 determines whether or not the registration is for a doctor. In the case of doctor registration, the prescription information providing server 330 acquires doctor information from the communication terminal 210 in step S1313. Then, the prescription information providing server 330 registers the doctor's information in the member database 1103 in step S1315.
  • the prescription information providing server 330 determines in step S1321 whether or not a prescription support request has been received from the communication terminal 210.
  • the prescription information providing server 330 transmits a prescription search screen for inputting search conditions to the communication terminal 210 in step S1323. Then, the prescription information providing server 330 waits for reception of search conditions from the communication terminal 210 in step S1325.
  • the prescription information providing server 330 transmits the search conditions to the dispensing information search server 320 in step S1327.
  • step S1329 the prescription information providing server 330 waits for a search result response from the dispensing information search server 320.
  • the prescription information providing server 330 acquires the search result reply in step S1331.
  • the prescription information providing server 330 determines whether or not to select a prescription medicine set to be displayed in the search results.
  • the prescription information providing server 330 selects the prescription medicine set to be presented according to the medicine to be included/the medicine not to be included in step S1335.
  • the prescription information providing server 330 generates a prescription medicine set display screen in step S1337, and transmits the prescription medicine set display screen to the communication terminal 210 that requested the search in step S1339.
  • Communication terminal 210 that displays the search results when a doctor instructs to search for a set of prescription drugs as prescription assistance will be described below.
  • FIG. 14 is a block diagram showing the functional configuration of the communication terminal 210 according to this embodiment.
  • the communication terminal 210 includes a communication control unit 1401, a prescription support application acquisition unit 1402, a prescription support application execution unit 1403, and an input/output interface 1404.
  • the communication control unit 1401 controls communication with the prescription information providing server 330.
  • a prescription assistance application acquisition unit 1402 acquires a prescription assistance application to be executed on the communication terminal 210 .
  • the prescription support application executing unit 1403 executes the acquired prescription support application.
  • An input/output interface 1404 connects to input/output devices such as a display unit 1441 and an operation unit 1442 .
  • the prescription support application execution unit 1403 includes a doctor information acquisition unit 1431, a doctor information registration instruction unit 1432, a search condition input screen acquisition unit 1433, and a search condition input screen display control unit 1434.
  • Prescription support application execution unit 1403 also includes search condition acquisition unit 1435 , search condition transmission unit 1436 , prescription medicine set display screen reception unit 1437 , and prescription medicine set display screen display control unit 1438 .
  • the doctor information acquisition unit 1431 acquires doctor information input from the operation unit 1442 for doctor registration.
  • the doctor information registration instruction unit 1432 transmits the acquired doctor information to the prescription information providing server 330 to instruct doctor registration.
  • the search condition input screen acquisition unit 1433 acquires a prescription search screen as a screen for entering search conditions from the prescription information providing server 330 .
  • the search condition input screen display control unit 1434 causes the display unit 1441 to display the acquired prescription search screen.
  • the search condition acquisition unit 1435 acquires search conditions input from the operation unit 1442 on the prescription search screen.
  • the search condition transmission unit 1436 transmits the acquired search condition to the prescription information providing server 330 as a prescription medicine set search request.
  • the prescription medicine set display screen receiving unit 1437 receives the prescription medicine set display screen of the search result from the prescription information providing server 330 as a reply to the search request.
  • the prescription medicine set display screen display control unit 1438 causes the display unit 1441 to display the display screen of the received prescription medicine set as the search result.
  • FIG. 15 is a flow chart showing the processing procedure of the communication terminal 210 according to this embodiment. This flowchart is executed by the CPU that controls communication terminal 210 using the RAM, and implements the components of communication terminal 210 in FIG.
  • step S1511 the communication terminal 210 determines whether or not the prescription support application is activated. If the prescription assistance application is activated, the communication terminal 210 acquires the prescription assistance application in step S1513, and activates the prescription assistance application in step S1515.
  • step S1517 the communication terminal 210 determines whether registration of a doctor is required (unregistered). If registration of a doctor is necessary, the communication terminal 210 acquires doctor information in step S1519, and transmits the acquired doctor information to the prescription information providing server 330 in step S1521.
  • the communication terminal 210 determines in step S1531 whether or not the search request is for a prescription medicine set. If it is a prescription medicine set search request, the communication terminal 210 acquires a prescription search screen, which is a search condition input screen, from the prescription information providing server 330 in step S1533. Then, communication terminal 210 displays a prescription search screen in step S1535.
  • the communication terminal 210 waits for input of search conditions from the operation unit 1442 in step S1537. If search conditions are input, the communication terminal 210 transmits the search conditions to the prescription information providing server 330 in step S1539. Then, the communication terminal 210 waits for a search result response from the prescription information providing server 330 in step S1541. If there is a search result reply, communication terminal 210 displays a prescription medicine set as a search result in step S1543.
  • the receipt data including medical receipts and dispensing receipts is used, there is no variation in the quality of the information, the dispensing has been checked, and a highly reliable set of prescription drugs can be presented.
  • the doctor can specify the medicines to be included in the prescription medicine set, it is possible to know, for example, prescription examples of new medicines.
  • the doctor can specify medicines that the doctor does not want to include in the prescription medicine set, for example, appropriate prescription examples corresponding to the patient can be known.
  • the prescription support system according to this embodiment differs from the second embodiment in that it presents a prescription drug set that takes into consideration the timing of issuing a prescription.
  • the timing of issuing a prescription includes, for example, the time of the first visit, the time of continuation of medical care, and the time of changing the prescription medicine set. Since other configurations and operations are similar to those of the second embodiment, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof will be omitted.
  • FIG. 16 is a diagram showing a search input screen 1611 of the communication terminal 210 in the prescription support system according to this embodiment.
  • the description of the same component as the prescription search screen 211 of FIG. 2A is omitted.
  • the search input screen 1611 has a field for setting whether the issuing time of the prescription is "at the time of first visit”, “at the time of continuing medical treatment", or "at the time of prescription change” during the medical treatment period. 1612, and a column 1613 for entering a medical history. In the present embodiment, it is possible to optimize a set of prescribed medicines, especially the dosage and administration, or the number of prescription days, depending on the timing of issuing a prescription.
  • FIG. 17 is a diagram showing the configuration of the search database 1721 according to this embodiment.
  • the same reference numerals are given to the same components as those in FIG. 6C, and redundant explanations are omitted.
  • the search database 1721 further subdivides the dispensing drug set according to the prescription time 1701 and stores the dispensing drug set suitable for the prescription time.
  • the prescription support system according to this embodiment differs from the second and third embodiments in that it supports prescription issuance in consideration of the issuer of the receipt data. Since other configurations and operations are the same as those of the second and third embodiments, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof will be omitted.
  • FIG. 18 is a block diagram showing the functional configuration of an information processing device as the dispensing medicine set extraction unit 1840 according to this embodiment.
  • the same reference numerals are given to the same components as those in FIG. 5, and redundant explanations are omitted.
  • the dispensing medicine set extraction unit 1840 includes a statistical processing unit 1806 having a claim issuer weighting table 1861 .
  • the appearance frequency is calculated by weighting the receipt according to whether the receipt is issued from a general hospital or a clinic, etc., so that the individual doctor is not biased. It may be possible to search for non-dispensing drug sets.
  • FIG. 19 is a diagram showing the configuration of the claim issuer weighting table 1861 according to this embodiment.
  • the claim issuer weighting table 1861 is used by the statistical processing unit 1806 of the dispensing drug set extraction unit 1840 to generate the search database 321 that enables searching for a dispensing drug set that is not biased toward individual doctors.
  • the claim issuer weighting table 1861 stores prescription issuers 1902 and ranking weights 1903 in addition to data 1901 of dispensing drug sets corresponding to patient attributes and patient symptoms or disease names. Gender is an option in patient attributes.
  • the prescription support system according to this embodiment differs from the above-described second to fourth embodiments in that it supports prescription issuance in consideration of medical history. Since other configurations and operations are the same as those of the second to fourth embodiments, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof will be omitted.
  • FIG. 20 is a diagram showing a search result display screen 2011 of the communication terminal 2010 in the prescription support system according to this embodiment.
  • the search conditions and the history of prescription doses for each prescription drug A, B, and B of the prescription drug set of the search results are displayed in graph form.
  • physicians can refer to current appropriate doses.
  • only the course of the dosage was taken up, but it is not limited to this. For example, even when changing a prescription drug, the progress and dosage can be viewed at a glance.
  • the present invention may be applied to a system composed of a plurality of devices, or may be applied to a single device. Furthermore, the present invention can also be applied when an information processing program that implements the functions of the embodiments is supplied to a system or apparatus and executed by a built-in processor.
  • the technical scope of the present invention includes an application program installed in a computer, a medium storing the program, a server for downloading the program, and a processor executing the program.
  • non-transitory computer readable media storing programs that cause a computer to perform at least the processing steps included in the above-described embodiments are included within the technical scope of the present invention.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Medicinal Chemistry (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
PCT/JP2022/006315 2021-02-19 2022-02-17 処方支援システム、処方支援方法、情報処理装置、通信端末およびそれらの方法およびプログラム Ceased WO2022176936A1 (ja)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021025660A JP6890364B1 (ja) 2021-02-19 2021-02-19 処方支援システム、処方支援方法、情報処理装置およびそれらの方法およびプログラム
JP2021-025660 2021-02-19

Publications (1)

Publication Number Publication Date
WO2022176936A1 true WO2022176936A1 (ja) 2022-08-25

Family

ID=76429601

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/006315 Ceased WO2022176936A1 (ja) 2021-02-19 2022-02-17 処方支援システム、処方支援方法、情報処理装置、通信端末およびそれらの方法およびプログラム

Country Status (2)

Country Link
JP (3) JP6890364B1 (https=)
WO (1) WO2022176936A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117112772A (zh) * 2023-08-22 2023-11-24 康键信息技术（深圳）有限公司 药品搜索方法及装置、存储介质、计算机设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114550870A (zh) * 2022-03-23 2022-05-27 康键信息技术（深圳）有限公司 基于人工智能的处方审核方法、装置、设备及介质
CN116682526B (zh) * 2023-08-03 2023-10-24 中国中医科学院中国医史文献研究所 基于古籍知识单元处理的中医知识推荐系统
KR102626898B1 (ko) * 2023-10-04 2024-01-18 한국엠바이오(주) 의사 데이터 베이스 관리 서비스 제공 방법 및 장치

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003108665A (ja) * 2001-09-28 2003-04-11 Srl Inc 診療支援システム
JP2010128718A (ja) * 2008-11-26 2010-06-10 Lotus:Kk 処方薬管理システム
JP2018081528A (ja) * 2016-11-17 2018-05-24 きりんカルテシステム株式会社 電子カルテシステム
JP2019159700A (ja) * 2018-03-12 2019-09-19 日本調剤株式会社 薬剤情報管理支援装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003271740A (ja) * 2002-03-12 2003-09-26 Shared Pharma:Kk 処方設計支援システム
JP2007272751A (ja) * 2006-03-31 2007-10-18 Hitachi Software Eng Co Ltd 薬品選択支援システムおよび薬品選択支援プログラム
JP5245804B2 (ja) * 2008-12-19 2013-07-24 富士通株式会社 データ選択支援プログラム、データ選択支援装置およびデータ選択支援方法
JP6177527B2 (ja) * 2013-01-07 2017-08-09 日本メディカルソリューションズ株式会社 医薬品利用情報提供システム
EP2782064A1 (en) * 2013-03-18 2014-09-24 Optimal Medicine Ltd Personalised medicine system
JP2016218684A (ja) * 2015-05-19 2016-12-22 株式会社日立システムズ 医療処方提示システム及び方法
WO2017149530A1 (en) * 2016-02-29 2017-09-08 Mor Research Applications Ltd System and method for selecting optimal medications for a specific patient
JP2018156149A (ja) * 2017-03-15 2018-10-04 オムロン株式会社 投薬支援装置、方法およびプログラム
CN107526933A (zh) * 2017-08-31 2017-12-29 乌耶含 一种远程医疗系统
JP2020064665A (ja) * 2019-12-27 2020-04-23 日本メディカルソリューションズ株式会社 情報提供システム、サーバ装置、情報提供プログラム、および情報提供方法
CN112289401A (zh) * 2020-11-10 2021-01-29 桃江县缘湘聚文化传媒有限责任公司 基于大数据智能化开具处方的方法、存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003108665A (ja) * 2001-09-28 2003-04-11 Srl Inc 診療支援システム
JP2010128718A (ja) * 2008-11-26 2010-06-10 Lotus:Kk 処方薬管理システム
JP2018081528A (ja) * 2016-11-17 2018-05-24 きりんカルテシステム株式会社 電子カルテシステム
JP2019159700A (ja) * 2018-03-12 2019-09-19 日本調剤株式会社 薬剤情報管理支援装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117112772A (zh) * 2023-08-22 2023-11-24 康键信息技术（深圳）有限公司 药品搜索方法及装置、存储介质、计算机设备

Also Published As

Publication number Publication date
JP2025023277A (ja) 2025-02-14
JP7605473B2 (ja) 2024-12-24
JP2022127484A (ja) 2022-08-31
JP6890364B1 (ja) 2021-06-18
JP2022127563A (ja) 2022-08-31

Similar Documents

Publication Publication Date Title
Pendergrass et al. Using electronic health records to generate phenotypes for research
WO2022176936A1 (ja) 処方支援システム、処方支援方法、情報処理装置、通信端末およびそれらの方法およびプログラム
US20020147615A1 (en) Physician decision support system with rapid diagnostic code identification
US20020147614A1 (en) Physician decision support system with improved diagnostic code capture
US10593428B2 (en) Diagnosis support apparatus and method, and non-transitory computer readable medium
JP6376838B2 (ja) 診療支援装置、診療支援装置の作動方法及びプログラム、並びに診療支援システム
US20080059229A1 (en) Prescription assisting apparatus and prescription assisting method
JP2013239158A (ja) 医療情報検索支援装置及び医療情報検索支援システム
WO2003096164A2 (en) Medical information system
JP2008102665A (ja) 医用画像読影支援システム及びプログラム
US20080046293A1 (en) Electronic medical chart producer
WO2007105165A2 (en) Display and method for medical procedure selection
JP6527771B2 (ja) 情報分析支援装置とその作動方法および作動プログラム、並びに情報分析支援システム
JP7689997B2 (ja) 診療支援装置、その作動方法及び作動プログラム、並びに診療支援システム
JP6675182B2 (ja) 複数の医療機関が保有する患者情報を医療情報提示端末に提示するシステム
US20240266016A1 (en) Automated extraction and unification of health record resources through fast healthcare interoperability resource conversion
US20160378922A1 (en) Methods and apparatuses for electronically documenting a visit of a patient
JP2006040246A (ja) 添付文書適応症コード変換方法
JP2021185543A (ja) 診療支援装置、診療支援装置の作動方法、診療支援装置の作動プログラム
JP2008250415A (ja) 医薬品処方支援方法、医薬品処方支援システム及びコンピュータプログラム
JP4298255B2 (ja) シート・タイプの検査結果表示方法および装置
US20110161103A1 (en) Systems and methods for electronic medical support
JP3600914B2 (ja) レセプト事務共助支援装置、レセプト審査支援装置及びそれらの方法並びにプログラム
JP2023161265A (ja) レセプト管理システム及びレセプト管理プログラム
JP7272288B2 (ja) 医療情報共有システム、医療情報共有方法、および、医療情報共有プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22756254

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22756254

Country of ref document: EP

Kind code of ref document: A1