WO2008127918A1 - Procédé et système permettant d'établir un programme de traitement dans un dossier médical informatisé - Google Patents

Procédé et système permettant d'établir un programme de traitement dans un dossier médical informatisé Download PDF

Info

Publication number
WO2008127918A1
WO2008127918A1 PCT/US2008/059656 US2008059656W WO2008127918A1 WO 2008127918 A1 WO2008127918 A1 WO 2008127918A1 US 2008059656 W US2008059656 W US 2008059656W WO 2008127918 A1 WO2008127918 A1 WO 2008127918A1
Authority
WO
WIPO (PCT)
Prior art keywords
diagnosis
treatment plan
patient
database
generating
Prior art date
Application number
PCT/US2008/059656
Other languages
English (en)
Inventor
Walid A. Hindo
Yemiru Chanyalew
Original Assignee
Hindo Walid A
Yemiru Chanyalew
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 Hindo Walid A, Yemiru Chanyalew filed Critical Hindo Walid A
Publication of WO2008127918A1 publication Critical patent/WO2008127918A1/fr
Priority to US12/847,946 priority Critical patent/US20110029322A1/en

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
    • 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
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/40—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for data related to laboratory analysis, e.g. patient specimen analysis
    • 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
    • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems

Definitions

  • the present disclosure relates generally to the field of electronic medical records.
  • the disclosure more specifically relates to a method of generating a medical diagnosis and/or treatment plan based on electronic medical records.
  • Computer systems also allow for standardized communication of medical information and patient records over networks, such as the Internet, using protocols such as Current Procedural Technology (CPT®), International Classification of Diseases (ICD-9), or Health Level Seven® (HL7).
  • CPT® Current Procedural Technology
  • ICD-9 International Classification of Diseases
  • HL7 Health Level Seven®
  • Computer programs have been written that are intended to aid medical professionals in the diagnosis and/or treatment of patients by analyzing the symptoms and/or or medical history of a patient, however these systems tend to provide false diagnoses, for example due to a lack of relevant information, low cost effectiveness, or lack of a comprehensive treatment plan.
  • Other systems may require the medical professional to form a hypothesis and later verify the hypothesis with evaluation and testing, however if the original hypothesis is wrong, the process must be started over.
  • One embodiment of the disclosure relates to an apparatus for generating a medical diagnosis or treatment plan includes a computing system, a user interface, a network, a database, and a server.
  • the server is configured to provide a diagnosis and recommended treatment plan based on one or more symptoms, a physical examination, and a laboratory and/or imaging test.
  • Another embodiment of the disclosure relates to a method on a computer-readable medium for generating a medical diagnosis and/or treatment plan.
  • the method includes the steps of identifying a symptom, ordering a suggested laboratory or imaging test, recording a result of said test, generating a diagnosis based on said symptom, said laboratory and/or imaging test, and generating a treatment plan based on said diagnosis.
  • Another embodiment of the disclosure relates to an apparatus for managing patient medical records and generating a medical diagnosis and/or treatment plan.
  • the apparatus includes means for identifying a symptom, means for ordering a suggested laboratory and/or imaging test, means for recording a result of said test, means for generating a diagnosis based on said symptom, said laboratory and/or imaging test, and means for generating a treatment plan based on said diagnosis.
  • FIG. 1 is a block diagram of a medical records and treatment plan system according to one exemplary embodiment.
  • FIG. 2 is a process flow diagram illustrating a process for maintaining medical records and generating a patient diagnosis and treatment plan with in the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 3 is a process flow diagram illustrating details of the method of FIG. 2, according to two exemplary embodiments.
  • FIG. 4 is a process flow diagram illustrating details of the diagnosis and treatment plan method of FIG. 2, according to one exemplary embodiment.
  • FIG. 5 is a process flow diagram illustrating decision logic used to find a medical diagnosis in the method of FIG. 4, according to one exemplary embodiment.
  • FIG. 6 is a process flow diagram illustrating the process for managing electronic medical records in the method of FIG. 2, according to one exemplary embodiment.
  • FIG. 7 is a schematic diagram illustrating entities that may communicate with or access a medical record of a user via the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 8 is a schematic diagram illustrating a user interaction in an assessment process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 9 is a schematic diagram illustrating administrator management of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 10 is a process flow diagram illustrating administrator management of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 11 is a schematic diagram illustrating user interaction in a patient management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 12 is a schematic diagram illustrating user interaction in a treatment plan communication process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 13 is a schematic diagram illustrating agent interaction in a patient management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 14 is a schematic diagram illustrating customer interaction in a subscription management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 15 is a schematic diagram illustrating administrator interaction in a CPT management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 16 is a schematic diagram illustrating administrator interaction in an ICD-9 management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 17 is a schematic diagram illustrating administrator interaction in a treatment plan management process of the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 18 is a computer screenshot of a patient management page in the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 19 is a computer screenshot of a symptom page in the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 20 is a computer screenshot of a diagnosis page in the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 21 is a computer screenshot of a treatment plan page in the system of FIG. 1 , according to one exemplary embodiment.
  • FIG. 22 is a computer screenshot of a patient history page in the system of FIG. 1 , according to one exemplary embodiment.
  • FIG. 23 is a computer screenshot of a services provided summary page in the system of FIG. 1, according to one exemplary embodiment.
  • FIG. 24 is a computer screenshot of a patient summary page in the system of FIG. 1 , according to one exemplary embodiment.
  • a system 10 is configured to manage the diagnosis and/or treatment provided to a patient.
  • system 10 can be configured to provide a patient electronic medical record (EMR) operation, provide a patient diagnosis information operation, and provide a patient treatment plan operation.
  • EMR electronic medical record
  • System 10 generally includes an application server 12, a database server 14, a data repository 16, a web server 18, a network 20, and a computing system 22.
  • Application server 12 is configured to provide and receive information related to medical records and medical diagnosis and treatment to and from a user of computing system 22.
  • Server 12 typically includes an EMR business rule engine 24 and a diagnostic and treatment engine 30.
  • EMR business rule engine 24 is configured to add patient EMRs to database server 14, manage or edit existing EMRs in EMR database server 14, and retrieve and send EMR information using predefined business rules as requested by a user.
  • EMR business rule engine 24 communicates with data repository 16 so that patient EMRs conforms to medical documentation standards and may be usable with other medical systems.
  • Application server 12 may be of any past, present, or future technology that is capable performing logical operations related to medical information.
  • EMR diagnosis engine 26 is configured to use existing EMRs, user inputs and/or other EMR systems to provide a medical diagnosis and/or treatment plan to the user.
  • the diagnosis or treatment plan may be generated by EMR diagnosis engine 26 based on Gender, Age, Symptom, Physical Exam, Lab Procedure, Image, other medication information, or any combination thereof, that is used in decision logic to determine the diagnosis and treatment plan.
  • EMR diagnosis engine 26 may also communicate with data repository 16 so that medical diagnosis and treatment information conforms with medical documentation standards that may be saved in an EMR and may be usable with other medical systems.
  • Database server 14 is configured to interface with data repository 16 in order to manage EMRs, diagnosis templates, disease classifications, and procedural terminology. According to various exemplary embodiments, database server 14 generally interfaces with data repository 16 using a database programming language, for example Sybase®, Oracle®, MS SQL Server®, MySQL Engine®, another language, or any combination thereof.
  • database programming language for example Sybase®, Oracle®, MS SQL Server®, MySQL Engine®, another language, or any combination thereof.
  • Data repository 16 is configured to store data used by system 10 through database server 14. According to one exemplary embodiment, data repository 16 may be located on database server 14. According to another exemplary embodiment, data repository 16 may be located remotely from and in communication with database server 14. Data repository 16 includes a CPT® database 28 (i.e., to store procedural terminology), an ICD-9® database 30 (i.e., to store disease classifications), an EMR database 32 (i.e., to store patient medical records), and a diagnosis template database 34. Diagnosis template database 30 is typically configured to store the relations between elements of the diagnosis algorithm, for example with a number of data tables. Diagnosis template database 30 defines the relationships between EMRs, symptoms, physical exams, laboratory tests, diagnoses, and treatment plans together.
  • Web server 18 is configured to provide a world-wide-web page to computing system 22 based on information from application server 12 and database server 14. According to various exemplary embodiments, web server 18 may provide Active Server Pages (ASPTM), JavaServer Pages (JSPTM), any other type of webpage, or any combination thereof. According to various exemplary embodiments, web server 18 may provide a webpage using Extensible Markup Language (XML), HyperText Markup Language (HTML), any other type of a programming or scripting language, or any combination thereof.
  • ASPTM Active Server Pages
  • JSPTM JavaServer Pages
  • XML Extensible Markup Language
  • HTML HyperText Markup Language
  • Network 20 is configured to facilitate communication (e.g., EMR information, diagnosis information, treatment plan information, etc.) application server 12, database server 14, web server 18, and computing system 22.
  • Network 20 may be a wired or wireless network, for example , a LAN, WAN, the Internet, or any other network that is capable of facilitating communication between application server 12, database server 14, web server 18, and computing system 22.
  • Communication with the network may be achieved via IEEE 802.11 Wi-Fi, IEEE 802.3 Ethernet, or modulate and demodulate (modem) technologies, or any other suitable communication technology.
  • Computing system 22 is configured to interact with application server 12, database server 14, and web server 18 so that the user may retrieve and manage EMRs and diagnosis or treatment plan information.
  • Computing system 22 may include a user interface 31 , a processor 32, an input device 34, and an output device 36.
  • User interface 22 is configured to provide a graphical and interactive screen to facilitate user interaction between computing system 22, application server 12, database server 14, and web server 18 (e.g., see FIG. 18-23).
  • user interface 22 may be embodied on computing system 22, on application server 12, or a removable medium such as a disk or CD-ROM.
  • Processor 32 may be any processor capable of past, present or future design that is capable of receiving input, providing output, and communicating with server 12.
  • Input device 34 may include a keyboard, a mouse, a light pen, a track pad, a disk drive, a voice interface, or any other suitable computer input device or combination thereof.
  • Output device may include a monitor, a printer, a speaker, a disk drive, or any other suitable computer output or combination thereof.
  • system 10 is shown to include four remote systems in communication with each other, it is noted that in other exemplary embodiments, computing system 22, application server 12, database server 14, and web server 18 may be integrated into a single computing system or multiple nodes of computers performing the role specified by application server 12, database server 14, and web server 18.
  • multiple computing systems may be included to facilitate user interaction from multiple locations or by multiple users.
  • additional servers may be included to provide data backup, distributed processing, etc.
  • multiple computing systems and additional servers may be used.
  • a method 40 is configured to manage patient EMRs and generate a Subjective Objective Assessment Plan (SOAP); a medical diagnosis and treatment plan.
  • system 10 performs a patient management process.
  • Patient EMRs may be added, updated/edited, or deleted.
  • system 10 performs a symptom identification process. Based on inputs by a patient, medical professional, or from data extracted from an EMR, system 10 may identify symptoms.
  • system 10 recommends medical tests, procedures, or exams and records the results of the tests or procedures once performed by a medical professional.
  • system 10 At a step 48, system 10 generates a diagnosis based on one or more patient EMRs, identified symptoms from step 44, and/or test results recorded at step 46. At step 50, system 10 recommends a treatment plan based on the diagnosis generated at step 48 and any applicable information from a patient EMR (e.g., medications, risk factors, etc.).
  • a treatment plan based on the diagnosis generated at step 48 and any applicable information from a patient EMR (e.g., medications, risk factors, etc.).
  • a process flow 52 illustrates that prior to the identification of symptoms, gender, concern or history of a diagnosis area (i.e., head, face, neck, bones, heart, chest, gastrointestinal, genital urinary, vascular, and breasts), and age are factored into the diagnosis and treatment plan generated. These additional factors may be extracted from an EMR or entered by the patient or a medical professional. Once symptoms have been identified, a medical professional performs a physical exam independent of lab and/or imaging test orders. The results (i.e., a lab or image finding and the physical exam) are recorded, which factors in to the diagnosis and treatment plan(s) system 10 generates.
  • a diagnosis area i.e., head, face, neck, bones, heart, chest, gastrointestinal, genital urinary, vascular, and breasts
  • a method 60 includes a number of steps that may be taken in system 10 to generate and use a diagnosis and treatment plan.
  • a diagnosis area is identified based on an EMR, history, or area of patient or medical professional concern.
  • symptoms e.g., major symptoms, specific symptoms, etc.
  • system 10 recommends a physical exam, lab test, and/or imaging test.
  • system 10 records the results of the physical exam, lab test, and imaging test of step 66.
  • system 10 performs or generates a diagnosis based on the diagnosis area, symptoms, physical exam, lab test, and/or imaging test.
  • system 10 suggests a possible treatment plan based on the diagnosis and patient information (e.g., medications, risk factors, etc.).
  • system 10 delivers the treatment plan, for example by printing and/or emailing, to the patient, medical professional, and or insurance company.
  • system 10 adds the patient diagnosis and treatment plan to the patient history or EMR.
  • a method 80 determines a medical diagnosis used in step 70 of method 60.
  • system 10 analyzes demographic data related to a patient from the patient EMR or from information entered manually.
  • system 10 uses decision logic to traverse a diagnosis tree based on patient demographic data, symptoms, physical exam results, lab test results, and/or imaging results.
  • system 10 determines one or more possible diagnoses based on the diagnosis tree traversal.
  • the decision logic and diagnosis tree may be of any past, present, or future design that is capable of providing a diagnosis based on patient demographic data, symptoms, physical exam results, lab test results, and/or imaging results.
  • a method 80 manages patient EMRs on system 10.
  • system 10 searches for a patient based on user inputs (e.g., name, social security number, etc.). If the patient is not new, the patient profile may be retrieved and updated at step 84. If the patient is new, a patient profile is added at step 86 using information from other EMR systems at step 88, if available.
  • user inputs e.g., name, social security number, etc.
  • system 10 may include a number of different types of users.
  • a patient may have access to personal diagnosis and treatment information as well as personal EMRs.
  • An insurance company may have access to various information in a patient EMR, for example billing information, diagnosis information, procedures ordered, and/or procedures performed.
  • a nurse may have access to the EMRs of various patients for use in treatment, for documentation of test results, etc.
  • a doctor may similarly have access to the EMRs of various patients as well as be able to confirm and prescribe diagnoses, treatment plans, and medications.
  • a primary contact doctor may have full access to all of the aspects of system 10 so that he or she may act as a source of information, troubleshooter, administrator, etc.
  • FIG. 8 a further characterization is given of the interaction between a user (e.g., a patient, doctor, nurse, insurance company, etc.) and system 10 following a diagnosis and treatment plan process similar to those of FIG. 2-4.
  • a user e.g., a patient, doctor, nurse, insurance company, etc.
  • system 10 following a diagnosis and treatment plan process similar to those of FIG. 2-4.
  • a user with administrator access rights has the ability to manage various aspects of system 10 including patient treatment plans, terminology database 18, and disease classification database 20, order subscriptions, and user addition.
  • Management of a patient treatment plan may include verification or override of a diagnosis or plan suggested by system 10, an update in the logic used by EMR diagnosis engine 26, or any other function related to treatment plan management.
  • Management of terminology database 18 may include updating a CPT® version, or any other function related to terminology management (see FIG. 15).
  • management of disease classification database 20 may include updating an ICD-9 version, or any other function related to disease classification management (see FIG. 16).
  • Management of order subscriptions may include verification or editing of lab procedures, for example.
  • an administrator may also perform general diagnosis, treatment, and EMR tasks, for example as a doctor may perform.
  • any user may use system 10 to send an e-mail including an attached treatment plan and order confirmation.
  • the email may be sent to other users, for example from a patient to an insurance company.
  • an agent for example from an insurance company, may use system 10 to search for patients, add new patients, update patient information.
  • An insurance agent may wish to use the patient information internally for procedure approval, proper diagnosis, and/or proper coding.
  • Order subscription typically includes product selection (e.g., type of lab test) and submission of customer information (e.g., name, insurance information, etc.).
  • customer information e.g., name, insurance information, etc.
  • FOP forecast for procurement
  • an administrator may update or manage CPT® database 27, ICD-9® database 28, and/or EMR diagnosis engine 26.
  • Updating of CPT® database 27 and ICD-9® database 28 typically includes obtaining the latest CPT® or ICD-9 data (e.g., over network 20), loading the data into staging tables, and importing the data to a respective reference table (i.e., in database 27 or 28).
  • Management of EMR diagnosis engine 26 generally includes the initiation of a search of ICD-9® database 28 for an entry of interest and insertion or an update of a treatment plan into EMR diagnosis engine 26 for the corresponding entry.
  • a plurality of screenshots give exemplary embodiments of user interface 31 in system 10.
  • a patient EMR management screen allows editing and entry of various patient information including name, social security number (SSN), date of birth, language preference, address, phone number, etc.
  • a symptom selection screen gives a patient summary and history along with drop-down boxes to choose a general symptom area and type followed by checkboxes to select specific symptoms.
  • a diagnosis review and assessment screen summarizes patient information as well as symptoms and patient history.
  • the screen also provides an area for objective assessment of diagnoses and physical exams or test that have been or will be ordered as well as an assessment of the test result as it relates to the diagnosis.
  • a treatment plan review and assessment screen provides a number of diagnosis possibilities to select from based on symptoms and laboratory/imaging tests ordered. The diagnosis may be followed by a number of treatment plan options to select from that correspond to various diagnosis codes.
  • a patient history screen provides details of a patient and his or her associated treatment plan history. Each treatment plan history may individually selected and reviewed more fully.
  • a service history screen outlines the services previously provided as well as when, a current status, and who last updated the status.
  • FIG. 24 an example summary of a treatment plan (that may be emailed or printed as shown in FIG. 4, for example) is shown.
  • This document generally includes patient information, significant findings resulting from physical or lab tests, diagnosis information, and any treatment plan information available.
  • Attached as Exhibit A to the provisional application is a business requirement document that further characterizes other exemplary aspects of system 10 described above.
  • Attached as Exhibit B to the provisional application is the "Health Level Seven Implementation Support Guide for HL7 Standard Version 2.3" (Health Level Seven, 1998), which characterizes an exemplary electronic medical record type that may be used in system 10.
  • the exemplary embodiments illustrated in the Figures and described above are presently preferred, it should be understood that these embodiments are offered by way of example only. Accordingly, the present invention is not limited to a particular embodiment, but extends to various modifications that nevertheless fall within the scope of the appended claims. The order or sequence of any processes or method steps may be varied or re-sequenced according to alternative embodiments.
  • Embodiments within the scope of the present invention may include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon.
  • machine-readable media can be any available media which can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media.
  • Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
  • Software implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Biomedical Technology (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Pathology (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

La présente invention concerne un procédé, sur un support pouvant être lu par ordinateur, destiné à générer un diagnostic médical et/ou un programme de traitement. Ledit procédé inclut les étapes consistant à identifier un symptôme, à ordonner une proposition de test d'imagerie ou de test de laboratoire, à enregistrer un résultat dudit test, à produire un diagnostic basé sur ledit symptôme, ledit test de laboratoire ou ledit test d'imagerie, et à générer un programme de traitement basé sur ledit diagnostic.
PCT/US2008/059656 2007-04-11 2008-04-08 Procédé et système permettant d'établir un programme de traitement dans un dossier médical informatisé WO2008127918A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/847,946 US20110029322A1 (en) 2007-04-11 2010-07-30 Health care system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US91124107P 2007-04-11 2007-04-11
US60/911,241 2007-04-11

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US59520408A A-371-Of-International 2003-09-23 2008-01-25
US12/847,946 Continuation-In-Part US20110029322A1 (en) 2007-04-11 2010-07-30 Health care system

Publications (1)

Publication Number Publication Date
WO2008127918A1 true WO2008127918A1 (fr) 2008-10-23

Family

ID=39864302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/059656 WO2008127918A1 (fr) 2007-04-11 2008-04-08 Procédé et système permettant d'établir un programme de traitement dans un dossier médical informatisé

Country Status (1)

Country Link
WO (1) WO2008127918A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012019110A1 (fr) * 2010-08-05 2012-02-09 Abbott Laboratories Procédé et système permettant de gérer des soins de santé d'un patient
WO2016178973A1 (fr) * 2015-05-01 2016-11-10 Laboratory Corporation Of America Holdings Prise en charge de décision améliorée pour des systèmes, procédés et support pour des services de prestation de laboratoire

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020019749A1 (en) * 2000-06-27 2002-02-14 Steven Becker Method and apparatus for facilitating delivery of medical services
US20060161456A1 (en) * 2004-07-29 2006-07-20 Global Managed Care Solutions, d/b/a Med-Vantage® , a corporation Doctor performance evaluation tool for consumers

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020019749A1 (en) * 2000-06-27 2002-02-14 Steven Becker Method and apparatus for facilitating delivery of medical services
US20060161456A1 (en) * 2004-07-29 2006-07-20 Global Managed Care Solutions, d/b/a Med-Vantage® , a corporation Doctor performance evaluation tool for consumers

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012019110A1 (fr) * 2010-08-05 2012-02-09 Abbott Laboratories Procédé et système permettant de gérer des soins de santé d'un patient
US8930222B2 (en) 2010-08-05 2015-01-06 Abbott Laboratories Method and system for managing patient healthcare
WO2016178973A1 (fr) * 2015-05-01 2016-11-10 Laboratory Corporation Of America Holdings Prise en charge de décision améliorée pour des systèmes, procédés et support pour des services de prestation de laboratoire

Similar Documents

Publication Publication Date Title
US20210005297A1 (en) Method and system for generating a medical report and computer program product therefor
Demner-Fushman et al. Preparing a collection of radiology examinations for distribution and retrieval
RU2497193C2 (ru) Обнаружение ошибок в машине логического вывода системы поддержки принятия клинического решения
JP4573818B2 (ja) 医用画像管理方法及び医用画像管理装置並びに医用ネットワークシステム
US20130226617A1 (en) Scoring system for rating a level of adherence to steps in a treatment plan
US20110029322A1 (en) Health care system
US20100094656A1 (en) Physician documentation workflow management methods
US11615890B2 (en) Method and system for the computer-assisted implementation of radiology recommendations
US20200243169A1 (en) Research study data acquisition and quality control systems and methods
US20140214451A1 (en) Adaptive Medical Documentation System
Simpao et al. The design and implementation of an automated system for logging clinical experiences using an anesthesia information management system
Törnqvist et al. Double documentation in electronic health records
Kinard et al. Medical device tracking—how it is and how it should be
US20120284051A1 (en) Method and system for personalizing and transforming patient interaction records
JP2008073397A (ja) 解剖図選択方法及び解剖図選択装置並びに医用ネットワークシステム
Tomes Identification and market removal of risky medical devices
US20200176127A1 (en) Systems and methods for guideline concordance
Salahuddin et al. Exploring the contributing factors to workarounds to the hospital information system in Malaysian hospitals
JP7216664B2 (ja) 実行可能な推奨事項を有する臨床レポート
WO2008127918A1 (fr) Procédé et système permettant d'établir un programme de traitement dans un dossier médical informatisé
JP5729049B2 (ja) 情報管理プログラム、情報管理装置および情報管理方法
Url et al. Challenges of an additive manufacturing service platform for medical applications
US20160364531A1 (en) Physician study manager method, system, and apparatus
Li et al. Implementation of enterprise imaging strategy at a Chinese Tertiary Hospital
US20230343454A1 (en) Method and system for the computer-assisted implementation of radiology recommendations

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: 08733165

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: 08733165

Country of ref document: EP

Kind code of ref document: A1