WO2019196211A1 - 一种筛选病历的方法、终端设备及计算机可读存储介质 - Google Patents

一种筛选病历的方法、终端设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2019196211A1
WO2019196211A1 PCT/CN2018/093706 CN2018093706W WO2019196211A1 WO 2019196211 A1 WO2019196211 A1 WO 2019196211A1 CN 2018093706 W CN2018093706 W CN 2018093706W WO 2019196211 A1 WO2019196211 A1 WO 2019196211A1
Authority
WO
WIPO (PCT)
Prior art keywords
disease
medical record
label
category
record file
Prior art date
Application number
PCT/CN2018/093706
Other languages
English (en)
French (fr)
Inventor
金晓辉
徐亮
阮晓雯
肖京
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019196211A1 publication Critical patent/WO2019196211A1/zh

Links

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
    • G16H70/00—ICT specially adapted for the handling or processing of medical references
    • 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
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • 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
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
    • Y02A90/00—Technologies having an indirect contribution to adaptation to climate change
    • Y02A90/10—Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a method, a terminal device, and a computer readable storage medium for screening a medical record.
  • the International Classification of Diseases is a system that classifies diseases according to certain characteristics according to certain characteristics of the disease and uses a coding method to represent each type of disease and all subtypes of diseases under each type of disease.
  • the corresponding ICD code is configured.
  • the ICD code of the disease is the carrier for recording diagnostic information, and is the basis for carrying out medical data analysis, medical insurance control and other activities.
  • the encoded electronic medical record such that if the target medical record is screened directly from the medical record database based on the ICD code, there will be a missed selection; if the screening is based on the name of a certain type of disease, the name of the subtype disease under each type of disease The name of the disease may not be included in the disease, and there will also be a missed selection, resulting in incomplete screening of the medical records.
  • the embodiment of the present application provides a method for screening a medical record, a terminal device, and a computer readable storage medium, which are intended to solve the problem that the existing medical record screening method may miss the screening when the medical record is screened, resulting in incomplete screening of the medical record. problem.
  • a method of screening medical records comprising:
  • the unique identifier being an International Classification of Disease ICD code or disease name
  • the target medical record file is screened from all of the medical record files based on the disease tags configured for each of the medical record files.
  • a computer readable storage medium is stored, the computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the steps of the method of screening medical records described above.
  • a server comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions The steps of the method of screening medical records.
  • the unique identifier of the disease of the patient is obtained from each medical record file, and the disease label corresponding to the unique identifier of the disease of the patient is determined based on the preset correspondence between the unique identifier of the disease and the disease label, and Each medical record file is configured with a corresponding disease label, and the target medical record file is selected from all medical record files based on the disease label configured in each medical record file.
  • the unique identifier of the disease of the patient in the embodiment of the present application may be an international classification ICD code or a disease name, and therefore, whether it is an ICD-encoded medical record file in which only the disease is recorded, or only a medical record file in which the disease name is recorded.
  • the embodiments of the present application may be configured with corresponding disease labels for describing the disease category to which the disease belongs. Therefore, when the target medical record file of a certain type of disease is selected and screened based on the disease label configured in each medical record file, the present invention does not exist. In the case of missing elections, it is possible to ensure that the medical records of the recorded diseases with a certain type of disease are complete.
  • FIG. 1 is a flowchart of an implementation of a method for screening medical records according to a first embodiment of the present application
  • FIG. 2 is a flowchart of an implementation of a method for screening a medical record according to a second embodiment of the present application
  • FIG. 3 is a flowchart of an implementation of a method for screening a medical record according to a third embodiment of the present application.
  • FIG. 4 is a flowchart of an implementation of a method for screening a medical record according to a fourth embodiment of the present application.
  • FIG. 5 is a flowchart of an implementation of a method for screening a medical record according to a fifth embodiment of the present application.
  • FIG. 6 is a structural block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 7 is a structural block diagram of a terminal device according to another embodiment of the present application.
  • FIG. 1 is a flowchart of an implementation of a method for screening medical records according to an embodiment of the present application.
  • the execution subject of the method for screening medical records in this embodiment is a terminal device, and the terminal device includes but is not limited to: a notebook computer, a computer, a server, a tablet computer, and a smart phone.
  • the method of screening medical records as shown in FIG. 1 includes the following steps:
  • S11 Obtain a unique identifier of the disease of the patient from each medical record file, the unique identifier being an international disease classification ICD code or a disease name.
  • a plurality of medical record files are stored in the medical record database, and the plurality of medical record files respectively correspond to a plurality of different patients, that is, one medical record file corresponds to one patient.
  • the medical record database can be stored in the local memory of the terminal device, that is, the local medical record database; the medical record database can also be stored in the cloud storage, that is, the cloud medical record database.
  • the medical record file is an electronic medical record file.
  • the electronic medical record file may be an electronic medical record file in a text format editable by the content, or may be an electronic medical record file in an image format that is not editable by scanning the paper medical record.
  • the unique identifier of the patient's disease is recorded in each medical record file.
  • the unique identifier of the disease recorded by the patient recorded in the medical record file may be the International Classification of Diseases (International Classification of Diseases, ICD) at least one of the coding and disease names. It should be noted that the ICD is the World Health Organization (World Health Organization).
  • the International Organization for Disease Classification which is based on the etiology, location, pathology, and clinical manifestations of diseases, classifies diseases according to rules and uses coding methods to represent diseases.
  • the 10th edition of the ICD (ICD-10) uses English letters and numbers to represent a type of disease or a disease. Specifically, ICD-10 divides the disease into multiple categories (ie categories) and divides certain categories into multiple sub-headings or breakdowns. A category corresponds to a type of disease, and multiple suborders or sub-categories under a category are multiple subtypes of diseases that are involved in a disease. Each category and each subhead or detail under each category corresponds to an ICD code.
  • the category is a three-digit code, including one letter and two digits.
  • D50 iron deficiency anemia
  • the suborder is a four-digit code, including one letter, three digits, and one decimal point, such as D50.0.
  • D50.1 is an iron deficiency swallowing abnormality
  • the breakdown is a five-digit code, including one letter, four digits, and one decimal point.
  • S02.01 is an open fracture of the parietal bone. Is a selectively used code that provides a different axis classification than the sub-category axis.
  • the ICD code and disease name of the disease of the patient recorded in the medical record file may be an ICD code and a disease name based on the disease in ICD-10.
  • the ICD code or disease name of the disease recorded by the patient recorded in the medical record may be the ICD code or disease name of a subtype of disease under a certain type of disease, for example, the patient's disease recorded in the medical record file.
  • the ICD code can be D50.0, and the corresponding disease name is iron deficiency anemia secondary to blood loss. It can be understood that when a certain type of disease does not include any subtype of disease, or the physician's description of the patient's disease is more general, the ICD code or disease name of the disease recorded by the patient recorded in the medical record file may be a certain type of disease.
  • the ICD code or disease name for example, the ICD code of the disease recorded by the patient recorded in the medical record file may be D50, and the corresponding disease is iron deficiency anemia.
  • the ICD code or disease name of the disease recorded by the patient recorded in each medical record file may be one or at least two.
  • the patient has only one disease; when the patient records the disease, the ICD code or disease name of the disease is at least two. At the time, the patient has at least two diseases.
  • the embodiment of the present application first configures each medical record file in the medical record database to describe the record recorded in the medical record file.
  • the terminal device may configure a disease label for each medical record file currently stored in the medical record database when the medical record file is firstly selected from the medical record database, and filter the target medical record file based on the disease label configured by each medical record file.
  • the terminal device In the subsequent non-first screening of the medical record file from the medical record database, if the medical record file is not added in the medical record database, the terminal device does not need to perform the step of configuring the disease label for the medical record file, which may be based on the first medical record file for each medical record file.
  • the disease label is configured to directly filter the medical record file; if the medical record file is added to the medical record database, the terminal device can configure the disease label only for the newly added medical record file, and the disease label is configured based on each medical record file. Screening the target medical record file can greatly improve the screening efficiency of the medical record file.
  • the terminal device when configuring the corresponding disease label for each medical record file, the terminal device first obtains the unique identifier of the disease of the patient from each medical record file in the case database.
  • the terminal device may obtain a unique identifier of the disease of the patient from each medical record file stored in the local medical record database, or obtain a unique identifier of the disease of the patient from each medical record file stored in the cloud medical record database.
  • the terminal device can scan the contents of each medical record file stored in the medical record database to obtain the ICD code or disease name of the disease of the patient recorded in each medical record file.
  • the terminal device can obtain the ICD code or disease name of the disease of the patient by directly scanning the medical record file; the electronic medical record file of the image format in which the content is not editable, the terminal device
  • the medical image file can be image-recognized by a preset image recognition tool, and the ICD code or disease name of the disease of the patient can be identified from the image.
  • S12 Determine a disease label corresponding to the unique identifier of the disease of the patient based on a preset correspondence between the unique identifier of the disease and the disease label, and the disease label is used to describe the disease category to which the disease belongs.
  • the terminal device After obtaining the unique identifier of the disease of the patient from each medical record file, the terminal device determines the unique identifier of the disease of the patient obtained from each medical record file based on the preset correspondence between the unique identifier of the disease and the disease label.
  • Corresponding disease label is a custom label used to describe the disease category to which the disease belongs and to distinguish between different types of diseases. Different disease labels describe different types of diseases, and different disease labels display different forms. The specific display form of the disease label can be set according to actual needs, and there is no limitation here. For example, a disease tag can be displayed as an icon of a preset color and/or a preset shape, and different categories of diseases are distinguished by icons of different colors and/or different shapes.
  • the preset correspondence between the unique identifier of the disease and the disease label includes: a preset correspondence between the ICD code of the disease and the disease label, a preset between the disease name of the disease and the disease label. Correspondence relationship. Among them, the disease label corresponding to the ICD code or disease name of all diseases under the same disease is the same, and the disease label corresponding to the ICD code or disease name of the disease under different diseases is different.
  • the preset correspondence between the unique identifier of the disease and the disease tag can be preset and stored in the terminal device local or in the cloud server.
  • the terminal device determines the ICD of the disease according to the disease according to the preset correspondence between the ICD code of the disease and the disease tag. Encoding the corresponding disease label; if the terminal device obtains the disease name of the disease of the patient from the medical record file, the terminal device determines the disease of the patient according to the preset correspondence relationship between the disease name of the disease and the disease label The disease label corresponding to the disease name.
  • the terminal device After determining the disease label corresponding to the unique identifier of the disease of the patient obtained from each medical record file, the terminal device configures a corresponding disease label for each medical record file, that is, configures the recorded disease of the patient for each medical record file.
  • the unique identifier corresponds to the disease label.
  • the terminal device configures the first disease label for the medical record file. If the disease label corresponding to the unique identifier of the disease of the patient acquired by the terminal device from a medical record file is the first disease label, the terminal device configures the first disease label for the medical record file. If the disease label corresponding to the unique identifier of the disease of the patient acquired by the terminal device from a medical record file is the second disease label, the terminal device configures the second disease label for the medical record file. Among them, the content and display form of the first disease label are different from the second disease label.
  • the first disease label may be a disease label for describing a cholera-like disease, the content of which may be "cholera”, the display form may be a purple diamond icon; the second disease label may be used to describe typhoid and paratyphoid fever.
  • the disease label of the disease, the content of which can be "typhoid fever and paratyphoid fever”, and the display form can be a white square icon.
  • the terminal device configured the disease label for the medical record file may be: storing the disease label corresponding to the unique identifier of the disease of the patient recorded in the medical record file and the medical record file, that is, establishing the medical record file.
  • the terminal device configured the disease label for the medical record file may be: adding the disease label corresponding to the unique identifier of the disease of the patient recorded in the file attribute information of the medical record file. That is, the disease tag corresponding to the unique identifier of the disease of the patient recorded in the medical record file is configured as the file attribute information of the medical record file.
  • the terminal device acquires the at least two different ICD codes or disease names, and determines each of the ICD codes or disease names respectively. Corresponding disease tags, at least two disease tags are obtained, and the terminal device configures at least two disease tags to the medical record file. It should be noted that if at least two different ICD codes or disease names recorded in the medical record file belong to the same category of diseases, the medical record file will eventually be configured with at least two identical disease labels; If at least two different ICD codes or diseases corresponding to the disease name do not belong to the same category of disease, the medical record file will eventually be configured with at least two different disease tags.
  • S14 Filter the target medical record file from all the medical record files based on the disease labels configured in each of the medical record files.
  • the user can use the disease label corresponding to a certain type of disease as a screening condition, and filter the target medical record file recorded with the disease from the medical record database.
  • the user may select a disease label corresponding to the disease category to be screened from all preset disease labels, and the terminal device will The disease label selected by the user is identified as the target disease label, and the medical record file configured with the target disease label is selected from the medical record database, and the medical record file obtained by the screening is the target medical record file to be screened by the user.
  • the embodiment of the present application provides a unique identifier for obtaining a disease of a patient from each medical record file, and determines a disease of the patient based on a preset correspondence between the unique identifier of the disease and the disease label.
  • the unique identifier of the disease of the patient in the embodiment of the present application may be an international classification ICD code or a disease name, and therefore, whether it is an ICD-encoded medical record file in which only the disease is recorded, or only a medical record file in which the disease name is recorded.
  • the embodiments of the present application may be configured with corresponding disease labels for describing the disease category to which the disease belongs. Therefore, when the target medical record file of a certain type of disease is selected and screened based on the disease label configured in each medical record file, the present invention does not exist. In the case of missing elections, it is possible to ensure that the medical records of the recorded diseases with a certain type of disease are complete.
  • FIG. 2 is a flowchart of an implementation of a method for screening medical records according to a second embodiment of the present application.
  • the present embodiment further includes S01 ⁇ S03 before S11, which is as follows:
  • the user can set a corresponding disease label for each type of disease in advance, that is, the user can pre-establish the correspondence between the disease category and the disease label.
  • users can set different disease labels for different types of diseases in order to distinguish between different types of diseases.
  • the content of the disease label set by the user for each type of disease may be the disease name or ICD code of the disease, and the specific display form of the disease label may be set according to actual needs, and no limitation is made here. .
  • the content of the disease label set by the user for diseases such as cholera may be “cholera” or “A00”, and the specific display form of the disease label may be a purple diamond icon; the user is set for diseases such as typhoid fever and paratyphoid fever.
  • the content of the disease label may be "typhoid and paratyphoid fever” or "A01”, and the specific display form of the disease label may be a white square icon or the like.
  • the terminal device may configure a corresponding preset disease label for each type of disease based on the disease label set by the user for each type of disease.
  • the ICD code library is a database composed of ICD codes and disease names for each type of diseases based on ICD classification, and ICD codes and disease names of multiple subtype diseases included in each type of disease.
  • the ICD coding library is specifically used to describe the correspondence between the disease name of each disease under the ICD classification and its ICD code, and the disease category used to describe each disease.
  • the terminal device can obtain all ICD codes and all disease names under each type of disease from the ICD code library. It can be understood that if a certain type of disease contains N subtype diseases, the terminal device can obtain N ICD codes and N disease names from the diseases.
  • the terminal equipment can obtain three disease names from cholera-like diseases, namely classical cholera, Erto cholera and unclear cholera, and 3 ICD codes. They are A00.0, A00.1 and A00.3.
  • the terminal device may separately filter all ICD codes and all disease names under each type of disease from the ICD code library by executing a preset screening script file.
  • the preset screening script file is a script file preset by the user for screening certain diseases from the ICD encoding library.
  • Different screening script files are used to filter different types of diseases from the ICD encoding library, that is, the same kind of diseases correspond to the same screening script file, and different types of diseases correspond to different screening script files.
  • the screening script file can be configured according to the regularity or commonality between the ICD codes of all subtype diseases under each type of disease.
  • the screening script file can be specifically expressed as an ICD code of a certain type of disease.
  • the first screening script file may be J44, corresponding to screening for chronic obstructive pulmonary diseases, and then, when the first screening script file is executed, the terminal device may select all the diseases of the chronic obstructive pulmonary disease from the ICD encoding library. ICD code and all disease names.
  • S03 Associate the disease label of each type of disease with all ICD codes and all disease names under the disease, and obtain a preset correspondence between the unique identifier of the disease and the disease label.
  • all ICD codes under each type of disease are associated with the disease label of the disease, that is, all ICD codes under each type of disease are The disease label of this type of disease establishes a corresponding relationship; at the same time, all disease names under each type of disease are associated with diseases of the disease, that is, all disease names under each type of disease and the disease label of the disease Establish a correspondence.
  • the correspondence between all ICD codes under each type of disease and the disease label of the disease, and the correspondence between all disease names under each type of disease and the disease label of the disease constitute the unique identifier and disease of the disease. Preset correspondence between tags.
  • the present embodiment normalizes the identification of all types of diseases by configuring corresponding pre-set disease labels for each type of disease; by establishing a preset correspondence between the ICD codes of the diseases and the disease labels, And establishing a correspondence between the disease name of the disease and the disease label, so that when the disease label is subsequently configured for the medical record file, the ICD code of the disease or the disease name can be found regardless of whether the disease file is obtained from the medical record file.
  • the standardized disease label can further ensure that when the target medical record file of a certain type of disease is screened and recorded based on the disease label configured in each medical record file, the medical record file recorded with a certain type of disease is complete.
  • FIG. 3 is a flowchart of an implementation of a method for screening medical records according to a third embodiment of the present application.
  • the present embodiment further includes S15 ⁇ S16 after S13 and before S14, as follows:
  • At least two different ICD codes or disease names may be recorded in a medical record file, so a medical record file may be configured with at least two disease labels.
  • the terminal device detects the number of disease labels configured in each medical record file, and if a medical record file is configured with at least two disease labels, the terminal The device detects whether the same disease label exists in the at least two disease labels, and if the same disease label exists in the at least two disease labels, the medical record records that at least two ICDs of the subtype diseases belonging to the same disease are recorded in the medical record file.
  • the terminal device performs S16; if the same disease label does not exist in the at least two disease labels, it indicates that at least two ICD codes of the subtype diseases not belonging to the same type are recorded in the case file. Or the base name, at this time, the terminal device does not do any processing.
  • the terminal device if the terminal device detects that a medical record file is configured with at least two disease tags, and the same basic tags exist in the at least two disease tags, the terminal device retains only one disease from the same disease tag. Label and exclude other disease labels other than the one disease label. For example, if the terminal device detects that a medical record file is configured with four disease labels, and three of the four disease labels have the same disease label, the terminal device retains only one disease label from the three same disease labels. The two disease labels other than the one disease label are removed, so that there is no duplicate disease label in the disease label finally configured for each medical record file.
  • the embodiment performs deduplication operation on the same disease label in at least two disease labels configured by the medical record file, so that there is no duplicate disease label in the disease label finally configured in each medical record file, so that When the target medical record file of a certain type of disease is screened and screened based on the disease label configured in each medical record file, the efficiency of screening the medical record file can be improved.
  • FIG. 4 is a flowchart of an implementation of a method for screening medical records according to a fourth embodiment of the present application.
  • this embodiment further includes S17 ⁇ S19 after S13, which is as follows:
  • S17 Display the disease label as an icon of a preset color and/or a preset shape.
  • the user can preset a specific display form for each disease tag.
  • the user can set the display form of the disease tag to an icon of a preset color and/or a preset shape.
  • the icons and icons of different disease labels have different colors and/or shapes.
  • the user may set the display form of the disease label for describing the cholera-like disease as a purple diamond icon, and display the display form of the disease label of typhoid and paratyphoid fever diseases as a white square icon or the like.
  • the disease category to which the disease of the patient recorded in each medical record file belongs is known.
  • the terminal device may display the disease tag configured by each medical record file as an icon of a preset color and/or a preset shape that the user has previously configured for. For example, if the display form set by the user for describing the disease label for the cholera-like disease is a purple diamond icon, the terminal device may display the disease label configured for describing the cholera-like disease as a purple diamond icon.
  • the terminal device may further configure a text comment for the disease category described by the disease tag for the icon corresponding to each disease tag. For example, if the disease category described by a disease label is "cholera", the terminal device can configure the text annotation of the disease label as "cholera.”
  • the terminal device displays a text comment configured by the selected icon. For example, if an icon corresponding to a disease label configured to describe a cholera-like disease is selected in a medical record file, the terminal device may display the words "cholera". Specifically, the terminal device can display a corresponding text comment at a preset position of the selected icon.
  • the preset position may be set according to actual needs, for example, the preset position may be directly below the icon.
  • the terminal device detects that the icon corresponding to a certain disease label is selected, which may be: detecting that the selection pointer falls within the display range of the icon corresponding to a disease label, or detecting a corresponding disease label. The icon is clicked.
  • the disease label as an icon of a preset color and/or a preset shape, and when an icon corresponding to a disease label is selected, the text annotation corresponding to the icon is displayed, thereby making the user
  • the disease label configured for each medical record file, and to know the disease type to which the disease of the patient recorded in each medical record file belongs.
  • FIG. 5 is a flowchart of a specific implementation of S14 in a method for screening medical records according to a fifth embodiment of the present application.
  • S14 in this embodiment specifically includes S141 ⁇ S143, which are as follows:
  • S141 Obtain a disease category to be screened by the user.
  • the user may use the disease label corresponding to a certain type of disease as a screening condition, and filter the target medical record file recorded with the disease from the medical record database.
  • the disease category input box may be displayed on the interactive interface. The user can enter the disease category to be screened in the disease category input box. If the terminal device detects that the user inputs the content in the disease category input box, the content input by the user is acquired, and the content input by the user is identified as the disease category to be screened.
  • the terminal device detects that the instruction for screening the medical record file from the medical record database may be: detecting the medical record file filtering option in the toolbar of the user clicking the medical record database.
  • S142 Determine a disease label corresponding to the disease category to be screened based on a preset correspondence between the disease category and the disease label.
  • the user may pre-establish a correspondence between the disease category and the disease label, and store the preset correspondence between the disease category and the disease label in the local storage or cloud storage of the terminal device.
  • the terminal device After acquiring the disease category to be selected by the user, the terminal device obtains a preset correspondence between the disease category and the disease label from the local storage or the cloud storage, and based on the preset correspondence between the disease category and the disease label, Determine the disease label corresponding to the disease category to be screened.
  • S143 Filter, from all the medical record files, a medical record file configured with the disease label corresponding to the disease category to be screened.
  • the terminal device After determining the disease label corresponding to the disease category to be screened, the terminal device selects the medical record file of the disease label corresponding to the disease category to be screened from all the medical record files based on the disease label configured for each medical record file.
  • the terminal device may detect the disease label configured in each medical record file in the medical record database. If a medical record file is configured with a disease label corresponding to the disease category to be screened, the medical record file is identified as the target to be screened. The medical record file and the target medical record file are filtered from the medical record database.
  • the terminal device detects the disease label configured in each medical record file, and if a medical record file is configured with the first The disease label identifies the medical record file as the target medical record file to be screened, and filters the target medical record file from the medical record database.
  • FIG. 6 is a structural block diagram of a terminal device according to an embodiment of the present application, where each unit included in the terminal device is used to perform each step in the embodiment corresponding to FIG. 1 to FIG.
  • the terminal device 600 includes: a first obtaining unit 61, a first determining unit 62, a first configuration unit 63, and a screening unit 64. among them:
  • the first obtaining unit 61 is configured to obtain, from each medical record file, a unique identifier of the disease of the patient, the unique identifier being an international disease classification ICD code or a disease name.
  • the first determining unit 62 is configured to determine, according to a preset correspondence between the unique identifier of the disease and the disease label, a disease label corresponding to the unique identifier of the disease of the patient, and the disease label is used to describe the disease category to which the disease belongs. .
  • the first configuration unit 63 is configured to configure a corresponding disease label for each of the medical record files.
  • the screening unit 64 is configured to filter the target medical record file from all of the medical record files based on the disease tags configured by the respective medical record files.
  • the terminal device 600 further includes: a second configuration unit 65, a second obtaining unit 66, and a first association unit 67.
  • the second configuration unit 65 is configured to configure respective disease labels for each type of disease.
  • the second obtaining unit 66 is configured to obtain, from the ICD encoding library, all ICD codes and all disease names under each type of disease, the ICD code library is used to describe the correspondence between the disease name of the disease and the ICD code of the disease, and Describe the type of disease each disease belongs to.
  • the first associating unit 67 is configured to associate the disease label of each type of disease with all ICD codes and all disease names under the disease, respectively, to obtain a preset correspondence between the unique identifier of the disease and the disease label.
  • the terminal device 600 further includes: a first detecting unit 68 and a de-weighting unit 69. among them:
  • the first detecting unit 68 is configured to detect whether the same disease tag exists in the at least two disease tags if the medical record file is configured with at least two disease tags.
  • the de-emphasis unit 69 is configured to retain a disease tag from the same disease tag if the same disease tag exists in the at least two disease tags, and exclude other disease tags other than the one disease tag.
  • the terminal device 600 further includes: a display unit 610, a third configuration unit 611, and a display unit 612. among them:
  • the display unit 610 is configured to display the disease label as an icon of a preset color and/or a preset shape.
  • the third configuration unit 611 is configured to configure a text annotation for the icon corresponding to the disease label, where the text annotation is used to describe the disease category described by the disease label.
  • the display unit 612 is configured to display the text comment if it is detected that an icon corresponding to the disease tag is selected.
  • the screening unit 64 may specifically include: a third obtaining unit, a second determining unit, and a medical record screening unit.
  • the third obtaining unit is configured to acquire a disease category to be screened by the user.
  • the second determining unit is configured to determine a disease label corresponding to the disease category to be screened based on a preset correspondence between the disease category and the disease label.
  • the medical record screening unit is configured to filter, from all of the medical record files, a medical record file configured with the disease label corresponding to the disease category to be screened.
  • FIG. 7 is a structural block diagram of a terminal device according to another embodiment of the present application.
  • the terminal device 7 of this embodiment includes a processor 70, a memory 71, and computer readable instructions 72 stored in the memory 71 and operable on the processor 70, such as screening medical records. Method of procedure.
  • the steps in the various embodiments of the method for individually screening the medical records described above are performed by the processor 70 when the computer readable instructions 72 are executed, such as S101 through S104 shown in FIG.
  • the processor 70 executes the computer readable instructions 72
  • the functions of the units in the embodiment corresponding to FIG. 6 are implemented, for example, the functions of the units 61 to 64 shown in FIG. 6.
  • FIG. The related description in the embodiment is not described here.
  • the computer readable instructions 72 may be partitioned into one or more units, the one or more units being stored in the memory 71 and executed by the processor 70 to complete the application.
  • the one or more units may be a series of computer readable instruction segments capable of performing a particular function for describing the execution of the computer readable instructions 72 in the terminal device 7.
  • the computer readable instructions 72 may be partitioned into a first acquisition unit, a first determination unit, a first configuration unit, and a screening unit, each unit having a specific function as described above.
  • the terminal device may include, but is not limited to, a processor 70 and a memory 71. It will be understood by those skilled in the art that FIG. 7 is only an example of the terminal device 7, and does not constitute a limitation of the terminal device 7, and may include more or less components than those illustrated, or combine some components or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 70 can be a central processing unit (Central Processing Unit, CPU), can also be other general purpose processors, digital signal processors (DSP), application specific integrated circuits (Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 71 may be an internal storage unit of the terminal device 7, such as a hard disk or a memory of the terminal device 7.
  • the memory 71 may also be an external storage device of the terminal device 7, for example, a plug-in hard disk provided on the terminal device 7, a smart memory card (SMC), and a secure digital (SD). Card, flash card, etc. Further, the memory 71 may also include both an internal storage unit of the terminal device 7 and an external storage device.
  • the memory 71 is configured to store the computer readable instructions and other programs and data required by the terminal device.
  • the memory 71 can also be used to temporarily store data that has been output or is about to be output.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

本申请公开了一种筛选病历的方法，用于现有的病历筛选方法在筛选病历时会存在漏选的情况，导致筛选到的病历不齐全的问题。本申请提供的方法包括：从各个病历文件中获取患者所患疾病的唯一标识；唯一标识为国际疾病分类ICD编码或疾病名称；基于疾病的唯一标识与疾病标签之间的预设对应关系，确定患者所患疾病的唯一标识对应的疾病标签；为各个病历文件配置相应的疾病标签；基于各个病历文件所配置的疾病标签，从所有病历文件中筛选目标病历文件。

Description

一种筛选病历的方法、终端设备及计算机可读存储介质
本申请申明享有2018年4月9日递交的申请号为201810309684.1、名称为“一种筛选病历的方法、终端设备及计算机可读存储介质”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种筛选病历的方法、终端设备及计算机可读存储介质。
 背景技术
国际疾病分类（International Classification of Diseases，ICD）是依据疾病的某些特性，按照规则将疾病分门别类，并用编码的方法来表示的系统，其为每类疾病以及每类疾病下的所有亚型疾病均配置了相应的ICD编码。疾病的ICD编码是记录诊断信息的载体，是开展医疗数据分析、医保控费等活动的基础。
在需要对患有某类疾病的患者的病历数据进行分析时，需要从病历库中筛选记录有该类疾病的病历。虽然现有的医疗机构在制作电子病历时都会在病历中添加相应的ICD编码，以便进行疾病分类和筛选，但病历库中还存在一些通过对原有的纸件病历进行扫描得到的不具有ICD编码的电子病历，这样，如果直接基于ICD编码从病历库中筛选目标病历，则会存在漏选的情况；而如果基于某类疾病的名称进行筛选，由于每类疾病下的亚型疾病的名称中不一定包含该类疾病的名称，也同样会存在漏选的情况，从而导致筛选得到的病历不齐全。
 技术问题
本申请实施例提供了一种筛选病历的方法、终端设备及计算机可读存储介质，旨在解决现有的病历筛选方法在筛选病历时会存在漏选的情况，导致筛选到的病历不齐全的问题。
 技术解决方案
第一方面，提供了一种筛选病历的方法，包括：
从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称；
基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别；
为各个所述病历文件配置相应的所述疾病标签；
基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
第二方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被处理器执行时实现上述的筛选病历的方法的步骤。
第三方面，提供了一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时上述的筛选病历的方法的步骤。
 有益效果
本申请实施例通过从各个病历文件中获取患者所患疾病的唯一标识，基于疾病的唯一标识与疾病标签之间的预设对应关系，确定患者所患疾病的唯一标识对应的疾病标签，并为各个病历文件配置相应的疾病标签，基于各个病历文件所配置的疾病标签，从所有病历文件中筛选目标病历文件。本申请实施例中患者所患疾病的唯一标识既可以是国际分类ICD编码，也可以是疾病名称，因此，无论是仅记录有疾病的ICD编码的病历文件，还是仅记录有疾病名称的病历文件，本申请实施例均可以为其配置相应的用于描述疾病所属疾病类别的疾病标签，因此，在基于各个病历文件所配置的疾病标签筛选记录有某类疾病的目标病历文件时，不会存在漏选的情况，能够保证所筛出的记录有某类疾病的病历文件是齐全的。
 附图说明
图1是本申请第一实施例提供的一种筛选病历的方法的实现流程图；
图2是本申请第二实施例提供的一种筛选病历的方法的实现流程图；
图3是本申请第三实施例提供的一种筛选病历的方法的实现流程图；
图4是本申请第四实施例提供的一种筛选病历的方法的实现流程图；
图5是本申请第五实施例提供的一种筛选病历的方法的实现流程图；
图6是本申请实施例提供的一种终端设备的结构框图；
图7是本申请另一实施例提供的一种终端设备的结构框图。
 本发明的实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
请参阅图1，图1是本申请实施例提供的一种筛选病历的方法的实现流程图。本实施例中筛选病历的方法的执行主体为终端设备，终端设备包括但不限于：笔记本电脑、计算机、服务器、平板电脑以及智能手机等设备。如图1所示的筛选病历的方法包括以下步骤：
S11：从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称。
病历库中存储有多个病历文件，多个病历文件分别对应多个不同的患者，即一个病历文件对应一个患者。在实际应用中，病历库可以存储在终端设备的本地存储器中，即为本地病历库；病历库也可以存储在云存储器，即为云病历库。
在本申请实施例中，病历文件为电子病历文件。其中，电子病历文件可以是内容可编辑的文本格式的电子病历文件，也可以是通过对纸质病历进行扫描得到的内容不可编辑的图像格式的电子病历文件。无论是哪种格式的病历文件，每个病历文件中均记录了患者所患疾病的唯一标识。其中，病历文件中记录的患者所患疾病的唯一标识可以是国际疾病分类（International Classification of Diseases，ICD）编码和疾病名称中的至少一种。需要说明的是，ICD是世界卫生组织（World Health Organization，WHO）制定的国际统一疾病分类方法，它根据疾病的病因、部位、病理、临床表现等特征，按照规则将疾病分门别类，并用编码的方法来表示疾病。ICD第10版（ICD-10）采用英文字母加数字的方法来表示一类疾病或一个疾病。具体的，ICD-10将疾病分为多个类目（即类别），并将某些类目分为多个亚目或细目。一个类目即对应一类疾病，一个类目下的多个亚目或细目即对应该类疾病所包含的多个亚型疾病。每个类目以及每个类目下的每个亚目或细目均对应一个ICD编码。其中，类目为三位数编码，包括一个字母和两位数字，例如，D50为缺铁性贫血；亚目为四位数编码，包括一个字母、三位数字及一个小数点，例如D50.0为继发于失血的缺铁性贫血，D50.1为缺铁性吞咽异常；细目为五位数编码，包括一个字母、四位数字及一个小数点，例如S02.01为顶骨开放性骨折，细目是选择性使用的编码，其提供一个与亚目分类轴心不同的轴心分类。
需要说明的是，在本申请实施例中，病历文件中记录的患者所患疾病的ICD编码和疾病名称可以是基于ICD-10中的疾病的ICD编码和疾病名称。
在实际应用中，病历文件中记录的患者所患疾病的ICD编码或疾病名称可以是某类疾病下的某个亚型疾病的ICD编码或疾病名称，例如，病历文件中记录的患者所患疾病的ICD编码可以是D50.0，对应的疾病名称为继发于失血的缺铁性贫血。可以理解的是，当某类疾病下不包括任何亚型疾病，或医师对患者所患疾病的描述较为笼统时，病历文件中记录的患者所患疾病的ICD编码或疾病名称可以是某类疾病的ICD编码或疾病名称，例如，病历文件中记录的患者所患疾病的ICD编码可以是D50，对应的疾病为缺铁性贫血。
每个病历文件中所记录的患者所患疾病的ICD编码或疾病名称可以是一个，也可以是至少两个。当病历文件中所记录的患者所患疾病的ICD编码或疾病名称为一个时，说明患者仅患有一种疾病；当病历文件中所记录的患者所患疾病的ICD编码或疾病名称为至少两个时，说明患者患有至少两种疾病。
在从病历库中筛选记录有某类疾病的目标病历文件时，为了保证不存在漏选的情况，本申请实施例先为病历库中的每个病历文件配置用于描述病历文件中所记录的疾病所属的疾病类别的疾病标签。在实际应用中，终端设备可以在首次从病历库中筛选病历文件时，为病历库中当前存储的各个病历文件配置疾病标签，并基于各个病历文件所配置的疾病标签筛选目标病历文件。而在后续非首次从病历库中筛选病历文件时，若病历库中未新增病历文件，则终端设备无需再执行为病历文件配置疾病标签的步骤，其可以基于首次筛选病历时为各个病历文件所配置的疾病标签，直接进行病历文件的筛选；若病历库中新增了病历文件，则终端设备该次可以仅为新增的病历文件配置疾病标签，并基于各个病历文件所配置的疾病标签筛选目标病历文件，这样可以大大提高病历文件的筛选效率。具体的，在为各个病历文件配置相应的疾病标签时，终端设备先从病例库中的各个病历文件中获取患者所患疾病的唯一标识。在实际应用中，终端设备可以从本地病历库中存储的各个病历文件中获取患者所患疾病的唯一标识，也可以从云病历库中存储的各个病历文件中获取患者所患疾病的唯一标识。更具体的，终端设备可以对病历库中存储的各个病历文件的内容进行扫描，进而得到各个病历文件中记录的患者所患疾病的ICD编码或疾病名称。例如，对于内容可编辑的文本格式的电子病历文件，终端设备可以通过直接对病历文件进行扫描得到患者所患疾病的ICD编码或疾病名称；对于内容不可编辑的图像格式的电子病历文件，终端设备可以调用预设的图像识别工具对病历文件进行图像识别，进而从图像中识别出患者所患疾病的ICD编码或疾病名称。
S12：基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别。
终端设备从各个病历文件中获取到患者所患疾病的唯一标识后，基于疾病的唯一标识与疾病标签之间的预设对应关系，确定从各个病历文件中获取到的患者所患疾病的唯一标识对应的疾病标签。其中，疾病标签是用于描述疾病所属的疾病类别，并用于对不同类别的疾病进行区分的一种自定义标签。不同的疾病标签所描述的疾病类别不同，且不同的疾病标签的展示形式不同。疾病标签的具体展示形式可以根据实际需求设置，此处不做限制。例如，疾病标签可以展示为预设颜色和/或预设形状的图标，不同类别的疾病通过不同颜色和/或不同形状的图标进行区分。
在本申请实施例中，疾病的唯一标识与疾病标签之间的预设对应关系包括：疾病的ICD编码与疾病标签之间的预设对应关系、疾病的疾病名称与疾病标签之间的预设对应关系。其中，同类疾病下的所有疾病的ICD编码或疾病名称对应的疾病标签均相同，不同类疾病下的疾病的ICD编码或疾病名称对应的疾病标签不同。疾病的唯一标识与疾病标签之间的预设对应关系可以预先设置并存储在终端设备本地或云服务器中。在实际应用中，若终端设备从病历文件中获取到的是患者所患疾病的ICD编码，则终端设备根据疾病的ICD编码与疾病标签之间的预设对应关系，确定患者所患疾病的ICD编码对应的疾病标签；若终端设备从病历文件中获取到的是患者所患疾病的疾病名称，则终端设备根据疾病的疾病名称与疾病标签之间的预设对应关系，确定患者所患疾病的疾病名称对应的疾病标签。
S13：为各个所述病历文件配置相应的所述疾病标签。
终端设备在确定了从各个病历文件中获取到的患者所患疾病的唯一标识对应的疾病标签后，为各个病历文件配置相应的疾病标签，即为各个病历文件配置其所记录的患者所患疾病的唯一标识对应的疾病标签。
例如，若终端设备从某一病历文件中获取到的患者所患疾病的唯一标识对应的疾病标签为第一疾病标签，则终端设备为该病历文件配置该第一疾病标签。若终端设备从某一病历文件中获取到的患者所患疾病的唯一标识对应的疾病标签为第二疾病标签，则终端设备为该病历文件配置该第二疾病标签。其中，第一疾病标签的内容和展示形式均不同于第二疾病标签。例如，第一疾病标签可以是用于描述霍乱类疾病的疾病标签，其内容可以是“霍乱”，展示形式可以是紫色菱形图标；第二疾病标签可以是用于描述伤寒和副伤寒热这类疾病的疾病标签，其内容可以是“伤寒和副伤寒热”，展示形式可以是白色方形图标。
在本申请一实施例中，终端设备为病历文件配置疾病标签具体可以为：将病历文件中记录的患者所患疾病的唯一标识对应的疾病标签与该病历文件进行关联存储，即，建立病历文件中记录的患者所患疾病的唯一标识对应的疾病标签与该病历文件的对应关系。
在本申请另一实施例中，终端设备为病历文件配置疾病标签具体可以为：在病历文件的文件属性信息中添加其所记录的患者所患疾病的唯一标识对应的疾病标签。即，将病历文件中记录的患者所患疾病的唯一标识对应的疾病标签配置为该病历文件的文件属性信息。
可以理解的是，当一个病历文件中记录有至少两个不同的ICD编码或疾病名称时，终端设备获取该至少两个不同的ICD编码或疾病名称，并分别确定该每一个ICD编码或疾病名称对应的疾病标签，得到至少两个疾病标签，终端设备将该至少两个疾病标签均配置给该病历文件。需要说明的是，若病历文件中记录的至少两个不同的ICD编码或疾病名称对应的疾病属于同一类别的疾病，则该病历文件最终会配置有至少两个相同的疾病标签；若病历文件中记录的至少两个不同的ICD编码或疾病名称对应的疾病不属于同一类别的疾病，则该病历文件最终会配置有至少两个不同的疾病标签。
S14：基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
终端设备为病历库中的所有病历文件配置好疾病标签后，用户可以将某类疾病对应的疾病标签作为筛选条件，从病历库中筛选记录有该类疾病的目标病历文件。具体的，在实际应用中，当用户需要从病历库中筛选记录有某类疾病的病历文件时，其可以从所有预设疾病标签中选择其所要筛选的疾病类别对应的疾病标签，终端设备将用户所选择的疾病标签识别为目标疾病标签，并从病历库中筛选配置有该目标疾病标签的病历文件，筛选得到的病历文件即为用户所要筛选的目标病历文件。
以上可以看出，本申请实施例提供的一种通过从各个病历文件中获取患者所患疾病的唯一标识，基于疾病的唯一标识与疾病标签之间的预设对应关系，确定患者所患疾病的唯一标识对应的疾病标签，并为各个病历文件配置相应的疾病标签，基于各个病历文件所配置的疾病标签，从所有病历文件中筛选目标病历文件。本申请实施例中患者所患疾病的唯一标识既可以是国际分类ICD编码，也可以是疾病名称，因此，无论是仅记录有疾病的ICD编码的病历文件，还是仅记录有疾病名称的病历文件，本申请实施例均可以为其配置相应的用于描述疾病所属疾病类别的疾病标签，因此，在基于各个病历文件所配置的疾病标签筛选记录有某类疾病的目标病历文件时，不会存在漏选的情况，能够保证所筛出的记录有某类疾病的病历文件是齐全的。
请参阅图2，图2是本申请第二实施例提供的一种筛选病历的方法的实现流程图。相对于图1对应的实施例，本实施例在S11之前，还包括S01~S03，详述如下：
S01：为每类疾病分别配置相应的疾病标签。
在本实施例中，在为病历库中的各个病历文件配置相应的疾病标签之前，需要先为每类疾病分别配置相应的用于对其进行描述的疾病标签。
在实际应用中，用户可以预先为每类疾病设置相应的疾病标签，即，用户可以预先建立疾病类别与疾病标签之间的对应关系。其中，用户可以为不同类别的疾病设置不同的疾病标签，以便对不同类别的疾病进行区分。在本申请一实施例中，用户为每类疾病所设置的疾病标签的内容可以是该类疾病的疾病名称或ICD编码，而疾病标签的具体展示形式可以根据实际需求设置，此处不做限制。例如，用户为霍乱这类疾病所设置的疾病标签的内容可以是“霍乱”或“A00”，疾病标签的具体展示形式可以是紫色菱形图标；用户为伤寒和副伤寒热这类疾病所设置的疾病标签的内容可以是“伤寒和副伤寒热”或“A01”，疾病标签的具体展示形式可以是白色方形图标等。在本实施例中，终端设备可以基于用户预先为每类疾病所设置的疾病标签，为每类疾病分别配置相应的预设疾病标签。
S02：从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别。
需要说明的是，ICD编码库是由基于ICD分类下的每类疾病的ICD编码和疾病名称，以及每类疾病所包含的多个亚型疾病的ICD编码和疾病名称所构成的数据库。ICD编码库具体用于描述ICD分类下的每个疾病的疾病名称与其ICD编码之间的对应关系，以及用于描述每个疾病所述的疾病类别。在本实施例中，终端设备可以从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称。可以理解的是，若某类疾病包含N个亚型疾病，则终端设备便可从该类疾病下获取到N个ICD编码和N个疾病名称。例如，若霍乱类疾病（疾病名称为“霍乱”，对应的ICD编码为A00）包含3个亚型疾病，分别为古典型霍乱、爱尔托霍乱及未明确的霍乱，对应的ICD编码分别为A00.0、A00.1及A00.3，则终端设备可以从霍乱类疾病下获取到3个疾病名称，分别为古典型霍乱、爱尔托霍乱及未明确的霍乱，以及3个ICD编码，分别为A00.0、A00.1及A00.3。
在本申请一实施例中，终端设备可以通过执行预设的筛选脚本文件，来从ICD编码库中分别筛选每类疾病下的所有ICD编码及所有疾病名称。
其中，预设的筛选脚本文件是用户预先设置的用于从ICD编码库中筛选某类疾病的脚本文件。不同的筛选脚本文件用于从ICD编码库中筛选不同类别的疾病，也就是说，同类疾病对应同一筛选脚本文件，不同类疾病对应不同的筛选脚本文件。在实际应用中，筛选脚本文件可以根据每类疾病下的所有亚型疾病的ICD编码之间的规律或共性进行配置，例如，筛选脚本文件具体可以表示为某类疾病的ICD编码。示例性的，第一筛选脚本文件可以为J44，对应筛选慢阻肺病类疾病，那么，终端设备在执行第一筛选脚本文件时，可以从ICD编码库中筛选出慢阻肺病类疾病下的所有ICD编码和所有疾病名称。
S03：将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
终端设备获取到每类疾病下的所有ICD编码和所有疾病名称后，将每类疾病下的所有ICD编码均与该类疾病的疾病标签进行关联，即，将每类疾病下的所有ICD编码与该类疾病的疾病标签建立对应关系；同时，还将每类疾病下的所有疾病名称均与该类疾病的疾病进行关联，即，将每类疾病下的所有疾病名称与该类疾病的疾病标签建立对应关系。
每类疾病下的所有ICD编码与该类疾病的疾病标签之间的对应关系，以及每类疾病下的所有疾病名称与该类疾病的疾病标签之间的对应关系即构成疾病的唯一标识与疾病标签之间的预设对应关系。
以上可以看出，本实施例通过为每类疾病配置相应的预先设置的疾病标签，从而将所有类别的疾病的标识进行规范化；通过建立疾病的ICD编码与疾病标签之间的预设对应关系，以及建立疾病的疾病名称与疾病标签之间的对应关系，从而使得在后续为病历文件配置疾病标签时，无论从病历文件中获取到的是疾病的ICD编码还是疾病名称，均可以找到与其对应的标准化的疾病标签，进而能够保证在基于各个病历文件所配置的疾病标签筛选记录有某类疾病的目标病历文件时，所筛出的记录有某类疾病的病历文件是齐全的。
请参阅图3，图3是本申请第三实施例提供的一种筛选病历的方法的实现流程图。相对于图1对应的实施例，本实施例在S13之后，在S14之前，还包括S15~S16，详述如下：
S15：若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签。
在实际应用中，一个病历文件中可能会记录有至少两个不同的ICD编码或疾病名称，因此，一个病历文件可能会配置有至少两个疾病标签。在本实施例中，终端设备为每个病历文件配置好相应的疾病标签后，检测每个病历文件所配置的疾病标签的个数，若某一病历文件配置有至少两个疾病标签，则终端设备检测该至少两个疾病标签中是否存在相同的疾病标签，若该至少两个疾病标签中存在相同的疾病标签，则说明该病历文件中记录有至少两个属于同类疾病的亚型疾病的ICD编码或基本名称，此时，终端设备执行S16；若该至少两个疾病标签中不存在相同的疾病标签，则说明该病例文件中记录有至少两个不属于同类基本的亚型疾病的ICD编码或基本名称，此时，终端设备不做任何处理。
S16：若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
在本实施例中，终端设备若检测到某一病历文件配置有至少两个疾病标签，且该至少两个疾病标签中存在相同的基本标签，则终端设备从相同的疾病标签中仅保留一个疾病标签，并剔除该一个疾病标签之外的其他疾病标签。例如，终端设备若检测到某一病历文件配置有4个疾病标签，该4个疾病标签中存在3个相同的疾病标签，则终端设备从该3个相同的疾病标签中仅保留一个疾病标签，并剔除该一个疾病标签之外的其他2个疾病标签，这样可以使得每个病历文件最终配置的疾病标签中没有重复的疾病标签。
以上可以看出，本实施例通过对病历文件所配置的至少两个疾病标签中的相同的疾病标签进行去重操作，从而使得每个病历文件最终配置的疾病标签中没有重复的疾病标签，这样，在后续基于各个病历文件所配置的疾病标签筛选记录有某类疾病的目标病历文件时，可以提高筛选病历文件的效率。
请参阅图4，图4是本申请第四实施例提供的一种筛选病历的方法的实现流程图。相对于图1至图3对应的实施例，本实施例在S13之后，还包括S17~S19，详述如下：
S17：将所述疾病标签展示为预设颜色和/或预设形状的图标。
在本实施例中，用户可以为每个疾病标签预先设置具体的展示形式。具体的，用户可以将疾病标签的展示形式设置为预设颜色和/或预设形状的图标。其中，不同疾病标签对应的图标的颜色和/或形状不同。例如，用户可以将用于描述霍乱类疾病的疾病标签的展示形式设置为紫色菱形图标，将伤寒和副伤寒热类疾病的疾病标签的展示形式设置为白色方形图标等。
在本实施例中，为了使用户在查看病历库时可以一目了然地知晓为每个病历文件所配置的疾病标签，进而获知每个病历文件中记录的患者所患疾病所属的疾病类别。终端设备可以将每个病历文件所配置的疾病标签展示为用户预先为其配置的预设颜色和/或预设形状的图标。例如，若用户预先为用于描述霍乱类疾病的疾病标签所设置的展示形式为紫色菱形图标，则终端设备可以将病历文件所配置的用于描述霍乱类疾病的疾病标签展示为紫色菱形图标。
S18：为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别。
在本实施例中，更进一步的，终端设备还可以为每个疾病标签对应的图标配置用于说明该疾病标签所描述的疾病类别的文字注释。例如，若某一疾病标签所描述的疾病类别为“霍乱”，则终端设备可以将该疾病标签的文字注释配置为“霍乱”。
S19：若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
在本实施例中，终端设备若检测到某一病历文件所配置的某一疾病标签对应的图标被选定，则终端设备显示为被选定的图标所配置的文字注释。例如，若某一病历文件所配置的用于描述霍乱类疾病的疾病标签对应的图标被选定，则终端设备可以显示“霍乱”字样。具体的，终端设备可以在被选定的图标的预设位置显示相应的文字注释。其中，预设位置可以根据实际需求设置，例如预设位置可以是图标的正下方。在实际应用中，终端设备检测到某一疾病标签对应的图标被选定具体可以是：检测到选择指针落入某一疾病标签对应的图标的显示范围内，或检测到某一疾病标签对应的图标被点击。
以上可以看出，本实施例通过将疾病标签展示为预设颜色和/或预设形状的图标，并在某疾病标签对应的图标被选定时，显示该图标对应的文字注释，从而使得用户在查看病历库时，可以一目了然地知晓为每个病历文件所配置的疾病标签，进而获知每个病历文件中记录的患者所患疾病所属的疾病类别。
请参阅图5，图5是本申请第五实施例提供的一种筛选病历的方法中S14的具体实现流程图。相对于图1对应的实施例，本实施例中的S14具体包括S141~S143，详述如下：
S141：获取用户输入的待筛选的疾病类别。
在本实施例中，终端设备为病历库中的所有病历文件配置好疾病标签后，用户可以将某类疾病对应的疾病标签作为筛选条件，从病历库中筛选记录有该类疾病的目标病历文件。具体的，终端设备若检测到用于从病历库中筛选病历文件的指令，则可以在交互界面显示疾病类别输入框。用户可以在该疾病类别输入框中输入待筛选的疾病类别。终端设备若检测到用户在疾病类别输入框中输入内容，则获取用户所输入的内容，并将用户所输入的内容识别为待筛选的疾病类别。在实际应用中，终端设备检测到用于从病历库中筛选病历文件的指令可以是：检测到用户点击病历库的工具栏中的病历文件筛选选项。
S142：基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签。
在实际应用中，用户可以预先建立疾病类别与疾病标签之间的对应关系，并将疾病类别与疾病标签之间的预设对应关系存储在终端设备本地存储器或云存储器中，具体请参阅S01，此处不再赘述。终端设备获取到用户输入的待筛选的疾病类别后，从本地存储器或云存储器中获取疾病类别与疾病标签之间的预设对应关系，并基于疾病类别与疾病标签之间的预设对应关系，确定待筛选的疾病类别对应的疾病标签。
S143：从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
终端设备在确定了待筛选的疾病类别对应的疾病标签后，基于为各个病历文件所配置的疾病标签，从所有病历文件中筛选配置有待筛选的疾病类别对应的疾病标签的病历文件。
具体的，终端设备可以对病历库中的每个病历文件所配置的疾病标签进行检测，若某一病历文件配置有待筛选的疾病类别对应的疾病标签，则将该病历文件识别为待筛选的目标病历文件，并从病历库中筛选目标病历文件。
例如，若待筛选的疾病类别为“霍乱”，其对应的疾病标签为第一疾病标签，则终端设备对每个病历文件所配置的疾病标签进行检测，若某一病历文件配置有该第一疾病标签，则将该病历文件识别为待筛选的目标病历文件，并从病历库中筛选目标病历文件。
图6示是本申请实施例提供的一种终端设备的结构框图，该终端设备包括的各单元用于执行图1至图5对应的实施例中的各步骤。具体请参阅图1至图5以及图1至图5所对应的实施例中的相关描述。为了便于说明，仅示出了与本实施例相关的部分。参见图6，终端设备600包括：第一获取单元61、第一确定单元62、第一配置单元63及筛选单元64。其中：
第一获取单元61用于从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称。
第一确定单元62用于基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别。
第一配置单元63用于为各个所述病历文件配置相应的所述疾病标签。
筛选单元64用于基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
可选的，终端设备600还包括：第二配置单元65、第二获取单元66及第一关联单元67。
第二配置单元65用于为每类疾病分别配置相应的疾病标签。
第二获取单元66用于从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别。
第一关联单元67用于将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
可选的，终端设备600还包括：第一检测单元68和去重单元69。其中：
第一检测单元68用于若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签。
去重单元69用于若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
可选的，终端设备600还包括：展示单元610、第三配置单元611及显示单元612。其中：
展示单元610用于将所述疾病标签展示为预设颜色和/或预设形状的图标。
第三配置单元611用于为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别。
显示单元612用于若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
可选的，筛选单元64具体可以包括：第三获取单元、第二确定单元及病历筛选单元。
第三获取单元用于获取用户输入的待筛选的疾病类别。
第二确定单元用于基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签。
病历筛选单元用于从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
图7是本申请另一实施例提供的一种终端设备的结构框图。如图7所示，该实施例的终端设备7包括：处理器70、存储器71以及存储在所述存储器71中并可在所述处理器70上运行的计算机可读指令72，例如筛选病历的方法的程序。处理器70执行所述计算机可读指令72时实现上述各个筛选病历的方法各实施例中的步骤，例如图1所示的S101至S104。或者，所述处理器70执行所述计算机可读指令72时实现上述图6对应的实施例中各单元的功能，例如，图6所示的单元61至64的功能，具体请参阅图6对应的实施例中的相关描述，此处不赘述。
示例性的，所述计算机可读指令72可以被分割成一个或多个单元，所述一个或者多个单元被存储在所述存储器71中，并由所述处理器70执行，以完成本申请。所述一个或多个单元可以是能够完成特定功能的一系列计算机可读指令段，该指令段用于描述所述计算机可读指令72在所述终端设备7中的执行过程。例如，所述计算机可读指令72可以被分割成第一获取单元、第一确定单元、第一配置单元及筛选单元，各单元具体功能如上所述。
所述终端设备可包括，但不仅限于，处理器70、存储器71。本领域技术人员可以理解，图7仅仅是终端设备7的示例，并不构成对终端设备7的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如所述终端设备还可以包括输入输出设备、网络接入设备、总线等。
所称处理器70可以是中央处理单元（Central Processing Unit，CPU），还可以是其他通用处理器、数字信号处理器（Digital Signal Processor，DSP）、专用集成电路（Application Specific Integrated Circuit，ASIC）、现成可编程门阵列（Field-Programmable Gate Array，FPGA）或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器71可以是所述终端设备7的内部存储单元，例如终端设备7的硬盘或内存。所述存储器71也可以是所述终端设备7的外部存储设备，例如所述终端设备7上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器71还可以既包括所述终端设备7的内部存储单元也包括外部存储设备。所述存储器71用于存储所述计算机可读指令以及所述终端设备所需的其他程序和数据。所述存储器71还可以用于暂时地存储已经输出或者将要输出的数据。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种筛选病历的方法，其特征在于，包括：
    从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称；
    基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别；
    为各个所述病历文件配置相应的所述疾病标签；
    基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
  2. 根据权利要求1所述的筛选病历的方法，其特征在于，所述从各个病历文件中获取患者所患疾病的唯一标识之前，还包括：
    为每类疾病分别配置相应的疾病标签；
    从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别；
    将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
  3. 根据权利要求1所述的筛选病历的方法，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件之前，还包括：
    若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签；
    若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
  4. 根据权利要求1所述的筛选病历的方法，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，还包括：
    将所述疾病标签展示为预设颜色和/或预设形状的图标；
    为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别；
    若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
  5. 根据权利要求1至4中任一项所述的筛选病历的方法，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件，包括：
    获取用户输入的待筛选的疾病类别；
    基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签；
    从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
  6. 一种终端设备，其特征在于，包括：
    第一获取单元，用于从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称；
    第一确定单元，用于基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别；
    第一配置单元，用于为各个所述病历文件配置相应的所述疾病标签；
    筛选单元，用于基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
  7. 根据权利要求6所述的终端设备，其特征在于，还包括：
    第二配置单元，用于为每类疾病分别配置相应的疾病标签；
    第二获取单元，用于从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别；
    第一关联单元，用于将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
  8. 根据权利要求6所述的终端设备，其特征在于，还包括：
    第一检测单元，用于若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签；
    去重单元，用于若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
  9. 根据权利要求6所述的终端设备，其特征在于，还包括：
    展示单元，用于将所述疾病标签展示为预设颜色和/或预设形状的图标；
    第三配置单元，用于为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别；
    显示单元，用于若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
  10. 根据权利要求6至9任一项所述的终端设备，其特征在于，所述筛选单元具体包括：
    第三获取单元，用于获取用户输入的待筛选的疾病类别；
    第二确定单元，用于基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签；
    病历筛选单元，用于从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
  11. 一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称；
    基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别；
    为各个所述病历文件配置相应的所述疾病标签；
    基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
  12. 根据权利要求11所述的服务器，其特征在于，所述从各个病历文件中获取患者所患疾病的唯一标识之前，所述处理器执行所述计算机可读指令时还实现如下步骤：
    为每类疾病分别配置相应的疾病标签；
    从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别；
    将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
  13. 根据权利要求11所述的服务器，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件之前，所述处理器执行所述计算机可读指令时还实现如下步骤：
    若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签；
    若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
  14. 根据权利要求11所述的服务器，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，所述处理器执行所述计算机可读指令时还实现如下步骤：
    将所述疾病标签展示为预设颜色和/或预设形状的图标；
    为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别；
    若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
  15. 根据权利要求11至14任一项所述的服务器，其特征在于，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件，包括：
    获取用户输入的待筛选的疾病类别；
    基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签；
    从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现如下步骤：
    从各个病历文件中获取患者所患疾病的唯一标识，所述唯一标识为国际疾病分类ICD编码或疾病名称；
    基于疾病的唯一标识与疾病标签之间的预设对应关系，确定所述患者所患疾病的唯一标识对应的疾病标签，所述疾病标签用于描述疾病所属的疾病类别；
    为各个所述病历文件配置相应的所述疾病标签；
    基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述从各个病历文件中获取患者所患疾病的唯一标识之前，所述计算机可读指令被处理器执行时还实现如下步骤：
    为每类疾病分别配置相应的疾病标签；
    从ICD编码库中获取每类疾病下的所有ICD编码及所有疾病名称，所述ICD编码库用于描述疾病的疾病名称与疾病的ICD编码之间的对应关系，以及描述每个疾病所属的疾病类别；
    将每类疾病的疾病标签与该类疾病下的所有ICD编码及所有疾病名称分别进行关联，得到疾病的唯一标识与疾病标签之间的预设对应关系。
  18. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件之前，所述计算机可读指令被处理器执行时还实现如下步骤：
    若所述病历文件配置有至少两个疾病标签，则检测所述至少两个疾病标签中是否存在相同的疾病标签；
    若所述至少两个疾病标签中存在相同的疾病标签，则从所述相同的疾病标签中保留一个疾病标签，剔除所述一个疾病标签之外的其他疾病标签。
  19. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述为各个所述病历文件配置相应的所述疾病标签之后，所述计算机可读指令被处理器执行时还实现如下步骤：
    将所述疾病标签展示为预设颜色和/或预设形状的图标；
    为所述疾病标签对应的图标配置文字注释，所述文字注释用于说明所述疾病标签所描述的疾病类别；
    若检测到所述疾病标签对应的图标被选定，则显示所述文字注释。
  20. 根据权利要求16至19任一项所述的计算机可读存储介质，所述基于各个所述病历文件所配置的疾病标签，从所有所述病历文件中筛选目标病历文件，包括：
    获取用户输入的待筛选的疾病类别；
    基于疾病类别与疾病标签之间的预设对应关系，确定所述待筛选的疾病类别对应的疾病标签；
    从所有所述病历文件中筛选配置有所述待筛选的疾病类别对应的疾病标签的病历文件。
PCT/CN2018/093706 2018-04-09 2018-06-29 一种筛选病历的方法、终端设备及计算机可读存储介质 WO2019196211A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810309684.1A CN108710636B (zh) 2018-04-09 2018-04-09 一种筛选病历的方法、终端设备及计算机可读存储介质
CN201810309684.1 2018-04-09

Publications (1)

Publication Number Publication Date
WO2019196211A1 true WO2019196211A1 (zh) 2019-10-17

Family

ID=63866550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093706 WO2019196211A1 (zh) 2018-04-09 2018-06-29 一种筛选病历的方法、终端设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN108710636B (zh)
WO (1) WO2019196211A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114388085A (zh) * 2021-11-23 2022-04-22 皖南医学院第一附属医院（皖南医学院弋矶山医院） 一种基于病案的实时智能辅助icd编码方法及系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111524569A (zh) * 2020-04-24 2020-08-11 常州昊泽信息科技有限公司 一种电子病历诊断维护系统
CN112541064B (zh) * 2020-12-09 2024-07-02 联仁健康医疗大数据科技股份有限公司 健康评测方法、装置、计算机设备及存储介质
CN117251556A (zh) * 2023-11-17 2023-12-19 北京遥领医疗科技有限公司 一种登记队列中患者筛选系统及方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070299692A1 (en) * 2006-06-09 2007-12-27 Kristi Lee Sonsteby Electronic medical documentation and assessment system
CN102129519A (zh) * 2011-03-11 2011-07-20 广东巨龙信息技术有限公司 一种电子病历档案的记载传输方法
CN105844566A (zh) * 2016-03-25 2016-08-10 东华软件股份公司 一种电子病历归档管理系统及方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010044783A (ja) * 2009-10-14 2010-02-25 Yuyama Manufacturing Co Ltd Ｉｃｄコード付与装置
WO2014194118A2 (en) * 2013-05-29 2014-12-04 Revon Systems, Llc Schedule-based electronic medical record modules, applications, and uses thereof
CN107705839B (zh) * 2017-10-25 2020-06-26 山东众阳软件有限公司 疾病自动编码方法及系统
CN107731269B (zh) * 2017-10-25 2020-06-26 山东众阳软件有限公司 基于原始诊断数据和病历文件数据的疾病编码方法及系统
CN107577826B (zh) * 2017-10-25 2018-05-15 山东众阳软件有限公司 基于原始诊断数据的疾病分类编码方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070299692A1 (en) * 2006-06-09 2007-12-27 Kristi Lee Sonsteby Electronic medical documentation and assessment system
CN102129519A (zh) * 2011-03-11 2011-07-20 广东巨龙信息技术有限公司 一种电子病历档案的记载传输方法
CN105844566A (zh) * 2016-03-25 2016-08-10 东华软件股份公司 一种电子病历归档管理系统及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114388085A (zh) * 2021-11-23 2022-04-22 皖南医学院第一附属医院（皖南医学院弋矶山医院） 一种基于病案的实时智能辅助icd编码方法及系统

Also Published As

Publication number Publication date
CN108710636A (zh) 2018-10-26
CN108710636B (zh) 2024-02-23

Similar Documents

Publication Publication Date Title
US11055789B1 (en) Systems and methods for insurance fraud detection
WO2019196211A1 (zh) 一种筛选病历的方法、终端设备及计算机可读存储介质
CN103221972B (zh) 医用系统
CN101944154A (zh) 医用图像读影系统
WO2019146357A1 (ja) 医療画像処理装置、方法及びプログラム並びに診断支援装置、方法及びプログラム
CN104240171A (zh) 电子病历生成方法及系统
CN105095332B (zh) 信息处理装置和信息处理方法
US20120101981A1 (en) Notification methods for non-programmatic integration systems
US9336377B2 (en) Synchronized sign-on methods for non-programmatic integration systems
CN113297853B (zh) 一种电子病历的质控方法、装置、电子设备及存储介质
CN111477289A (zh) 检测报告的存储和读取方法及装置
US20170018020A1 (en) Information processing apparatus and method and non-transitory computer readable medium
US20120102397A1 (en) Safety methods for non-programmatic integration systems
US20120102118A1 (en) Collaboration methods for non-programmatic integration systems
US20180356958A1 (en) Information processing apparatus, and information processing method
KR101484766B1 (ko) 의료정보 시스템에서의 전자서식 작성기 및 전자서식 작성 방법
JP2019106137A (ja) 表示プログラム、表示方法、表示装置、コメント表示制御プログラム、コメント表示制御方法及びコメント表示制御装置
JP6292837B2 (ja) 画像入力装置、画像出力装置およびそれらの方法
JP6996092B2 (ja) 情報処理装置、医療監査用装置及びプログラム
US20210065878A1 (en) Data Transmission System for Transmitting and Receiving Medical Information Data and Data Transmission Method Thereof
US20170075875A1 (en) Medical-document management apparatus, electronic medical record system, medical-document management system, and non-transitory computer readable medium
JP6713118B1 (ja) Ｐｄｉ規約の準拠性分析プログラム、ｐｄｉ規約の準拠性分析装置及びｐｄｉ規約の準拠性分析方法
CN112700835B (zh) 医疗护理期电子体温单填写监督管理方法、装置及介质
US20220165394A1 (en) Method, apparatus, and non-transitory computer readable medium for managing medical images
US10818051B2 (en) Relative signature traits of cohorts

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01.02.2021)

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

Ref document number: 18914499

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18914499

Country of ref document: EP

Kind code of ref document: A1