EP1590758A1 - Procédé et syst me de traitement de données d'évaluation - Google Patents
Procédé et syst me de traitement de données d'évaluationInfo
- Publication number
- EP1590758A1 EP1590758A1 EP03782536A EP03782536A EP1590758A1 EP 1590758 A1 EP1590758 A1 EP 1590758A1 EP 03782536 A EP03782536 A EP 03782536A EP 03782536 A EP03782536 A EP 03782536A EP 1590758 A1 EP1590758 A1 EP 1590758A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- entity
- data
- events
- function
- initial state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
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
- 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
-
- 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/20—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for electronic clinical trials or questionnaires
-
- 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
-
- 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 invention relates to a method and a system for processing evaluation data. It finds a particularly interesting application in any context where one wishes to analyze (evaluate) the effects of one or more actions on a population of entities of the same nature which can be in one or more initial states, the action or actions considered inducing a modification of this initial state and an evolution of this state over time.
- the present invention relates in particular, but not exclusively, to the medical field in which a user such as a doctor for example, wishes to follow the evolution of the condition of a patient throughout one or more treatments.
- the invention is of a broader scope, since it could be applied in particular to a system of evaluation of companies, the characteristics of which are liable to change over time as a function of certain internal and external actions.
- An object of the present invention is to provide a module allowing the simple and rapid entry of information with complex structure via a specific interface.
- Another object of the invention is to propose the use of this information in a simple and rapid manner.
- Another object of the invention is to propose a data entry and processing module which can be adapted to numerous fields of application.
- At least one of the aforementioned objectives is achieved with an evaluation data processing method comprising a data entry phase in which: a) at least one entity is created as a function of intrinsic characteristics of this entity, b) an initial state of said entity is created and filled in, c) an action is created and filled in according to the initial state, then d) creates and informs, during the evolution of the state of said entity and at determined times, resulting states, these resulting states being at least a function of the initial state and of the action.
- Icons representing the Entities, states and actions thus created visually align on a chronological line. Clicking on one of these icons gives access to the corresponding data.
- the method also includes a data exploitation phase in which statistical data are produced as a function of criteria determined by browsing the structure of at least one of the events a), b), c) and d) of the input phase .
- the data relating to each entity is stored in a first "Information” database, while the structure of the events is contained in a second independent "Metabase” database.
- the Metabase is a database containing the description (hierarchy, structure and contents) of the various objects and events. It does not contain any information related to the individual entities in themselves. It is only used to describe the structure of objects and events on which an input module and operating modules are based (sampling and analysis as described below).
- the input module allows you to create the different events and display their respective structures based on the information it finds in the Metabase.
- the data entered is then stored in the "Information" database.
- the operating modules also use the Metabase to display the global and specific structure of the events, to allow the user to choose his criteria and variables for the operation.
- the input and operation modules are entirely independent of the structure of the events studied, and therefore of the user's "profession". These modules constitute a generic interface.
- the structure of events can change (addition or deletion of events or items to be entered): the modifications are then automatically reflected in the entry and processing modules.
- the structure of each event can be of tree type.
- the tree structure can be in the form of cascading files or in graphic form or in any other form.
- the operation can include a sampling step in which a given sub-population of entities is selected.
- the selection can be made by choosing at least one variable in the structure of at least one event a), b), c) or d), and by assigning a given constraint to this variable.
- This constraint can be a value or a set of values, or the character "entered” or "not entered", making it possible to sample all the entities for which a specific variable has been entered or not.
- Data mining can also include an analysis step in which data is produced statistics in the form of values, tables or graphs.
- the sampling and the analysis are distinct, that is to say that one of the two functions can be performed without the other. We can also perform the analysis by choosing at least one variable in the structure of at least one event a), b), c) or d).
- the events a), b), c) and d) are created in chronological order, in particular as the activity of the user progresses. Entering information is therefore logical and simplified.
- the entry is carried out by means of intuitive graphical interfaces. It is also possible to have several successive interfaces detailing the elements entered.
- the input mode can be via a keyboard, on a touch screen or even audibly via a microphone.
- the structure of each event can be configured using the Metabase.
- a system for processing evaluation data comprising input means for: a) creating at least one entity as a function of intrinsic characteristics of this entity, b) creating and informing a initial state of said entity, c) create and inform an action as a function of the initial state, then d) create and inform, during the evolution of the state of said entity and at determined times, of the resulting states , these resulting states being at least a function of the initial state and of the action.
- the system also includes data processing means for developing statistical data according to criteria determined by browsing the structure of at least one of the events a), b), c) and d).
- the data processing means comprise a sampling module for selecting a given sub-population of entities and an analysis module, preferably separate, for developing statistical data in the form of values, tables or graphics.
- the input and exploitation means can consist of generic interfaces capable of exploring the structure of events.
- Other advantages and characteristics of the invention will appear on examining the detailed description of a mode of implementation which is in no way limitative, and the attached drawings, in which:
- FIG. 1 is a global schematic view of the environment in which a system according to the invention can be integrated;
- FIG. 2 is a diagram illustrating the events included in the entry phase as well as the processing modules for the operation phase;
- Figure 3 is a diagram illustrating the logical relationships between event structures;
- FIG. 4 is a diagram illustrating the principle of an input interface according to the invention.
- FIG. 5 is a diagram illustrating the principle of an input interface during a patient identification phase
- FIG. 6 is a diagram illustrating the principle of an input interface during a preoperative examination of the patient
- FIG. 7 is a diagram illustrating the principle of an intuitive graphic input interface during a pre-operative examination of the patient
- FIG. 8 is a diagram illustrating the principle of an input interface during an intraoperative examination (surgery) of the patient
- FIG. 9 is a diagram illustrating the principle of an operating interface during sampling
- FIG. 10 is a diagram illustrating the principle of an operating interface during an analysis.
- FIG. 11 is a diagram illustrating a processing mode of the sampling module and of the analysis module according to the invention.
- FIG. 1 there is a system with a data server 3 called “Server”.
- This data server brings together in an "Information” database, all of the information relating to each patient for whom medical monitoring is carried out by means of a method according to the invention.
- the information can be entered by a doctor 1 in a microcomputer 2 and then transmitted to the server 3 for storage. They can then be shared with other institutions such as a clinic 4 or a hospital 5. Institutions 4 and 5 can also enter information in order to complete a patient's file.
- the doctor and institutions 4 and 5 each have a microcomputer used for implementing the method according to the invention.
- Each microcomputer comprises a "Metabase” database according to the invention in which the structure of various objects and events.
- each microcomputer can contain both an "Information” database and a "Metabase” database.
- Figures 2 and 3 we see the logical flow of data processing according to the invention.
- FIG. 2 there is a microcomputer 6 allowing data entry and use according to the invention.
- the microcomputer 6 contains an "Information” database and a configured “Metabase” database.
- the user that is to say the doctor, to follow the evolution of the state of a patient, will create a set of events in chronological order, as and when his activity.
- the first step is to identify or define the entity (the patient).
- This step 7 can for example correspond to data such as the patient's first and last name, date of birth, file number, weight, height, profession, sports activities ... These elements are intrinsic characteristics of the patient.
- the next step 8 concerns a pre-operative examination (diagnosis) during which the doctor examines the patient in order to define the pathology related to this patient.
- the elements seized by the doctor can for example be a degenerative spine in the form of a herniated disc resulting in an inability to walk.
- the doctor can then implement a treatment such as a surgical operation, taking medication, or others.
- This treatment is a step 9 of intraoperative examination (therapeutic treatment).
- the surgical operation can be carried out in clinic 4, and the information relating to this operation is therefore introduced during step 9.
- Step 10 is a post-operative (follow-up) step during which the doctor performs several examinations at given times so as to check the evolution of the patient's condition. All the information obtained during these examinations is integrated into the "Information" database within the microcomputer 6.
- Steps 7 to 10 therefore relate to the entry step. This information will be used to carry out samples 11 so as to select sub-populations within all of the entities. Analyzes 12 can also be performed to develop statistical data in the form of values, tables or graphs.
- Each step 7, 8, 9 or 10 of the entry phase constitutes an event. These events follow a particular chronology as shown in FIG. 3.
- the identification 7 of the patient therefore corresponds to a first step during which the entity E (the patient) is defined. This identification makes it possible to grasp the intrinsic characteristics of the entity E (fig. 3) regardless of its pathology. This pathology is determined during the pre-operative examination (diagnosis) 8 (fig. 2) corresponding in fact to the definition of an initial state.
- To an entity E can correspond several initial states El, E2 and E3 for example (fig.3).
- a given action can be applied such as for example a medical treatment or a surgical operation.
- the actions Al-1, Al-2 or Al-3 can be applied.
- an initial state can correspond to several actions.
- to an action corresponds one and only one resulting state Ri-i.
- a doctor examines a patient who has undergone medical treatment the patient's condition is the only condition observed at the time of this post-operative examination.
- several post-operative (follow-up) exams can succeed each other by giving each a specific resulting state.
- Figure 4 is an example of an input interface.
- This interface includes an upper part comprising a first zone 13 for indicating some elements of identification of the patient such as for example the name, first name, date of birth and number of the corresponding file.
- the upper part also includes a second zone 14 for the creation of preoperative, intraoperative and postoperative events; and a third general information zone 15 such as returning to a summary menu, launching printing or displaying images associated with the current event.
- the input interface also includes an intermediate zone 16 illustrating the chronological line.
- This historic zone 16 comprises several events arranged one after the other in chronological order.
- the first element is the identification of entity E, of the patient.
- the next event is the definition of an initial state E-1 carried out during a pre-operative examination (diagnosis).
- the medical treatment or surgery applied to the patient during the intraoperative step 9 corresponds to an Al-1 action.
- Three postoperative (follow-up) exams (Rl-l (l), Rl-1 (2), Rl-1 (3)) are successively arranged on the chronological line before the definition of a second initial state E-2.
- This second initial state is followed by a second action A2-1 and by a resulting state R2-1 (1) corresponding to this second action.
- the structure of this event is developed in a lower left zone 17.
- the structure shown in area 17 is of the tree type. This type of structure can be the same for all events, but we can also have a given type of structure for each type of event.
- the selected event includes sub- events or files, and each sub-event includes other sub-events or other files and so on.
- Each file can be configured according to the user's wishes. That is to say that depending on the activity (medical or not) of the user, the latter can define the tree structure as well as the content of each file, sub-event and event.
- the settings are made within the "Metabase". Any modification to the Metabase is automatically reflected in the input and processing modules.
- the description of events contained in the Metabase includes in particular a hierarchy as represented in FIG. 3, and structures such as those represented in area 17 of FIG. 4.
- the files notably include variables which will later be used for sampling and analysis. These variables are in fact fields containing or not information entered by the doctor. This information is entered via an input area 18 in different forms such as drop-down menus, multiple choice lists, manual input fields, automatically calculated fields, graphical interfaces ...
- FIG. 5 is a view of an interface illustrating the entry of information during the identification of the patient.
- Area 17 shows the detailed structure tree, and area 18 shows the type of data to be entered.
- FIG. 6 is a view corresponding to a step 8 of pre-operative examination (diagnosis) during which the doctor firstly defines that it is a pathology of the "generative spine" type by means of graphic interfaces representing the human skeleton as well as the zoom of a part of this skeleton pointed by the doctor.
- FIG. 7 is a view of the continuation of the preoperative examination (diagnosis) making it possible to define more precisely the type of the "generative spine". The doctor can thus define that it is a herniated disc and specify the exact location on the spine. This definition is carried out by means of intuitive interactive graphics, a sort of graphic tree structure, each part of the skeleton being configured.
- Step 9 (fig. 2) of intraoperative examination involves a surgical operation for which an input interface is as shown in FIG. 8. In tree 17, there is a tree structure illustrating the sub-events and the index cards. The selected file contains the general characteristics of the surgical operation (therapeutic action), these characteristics being detailed in zone 18 of FIG. 8.
- FIG. 9 shows an interface for defining a sampling.
- the doctor selects one of the events displayed in the historical area 16.
- the event corresponding to "patient identification” is selected, it is the first event.
- zone 17 the tree structure corresponding to the patient identification event is displayed. It is the same structure as that represented in zone 17 of FIG. 5.
- the doctor will go through the structure until selecting the desired variable, in this case the weight. He can then specify the constraint, for example a weight less than 50 kg. We have thus simply isolated a subpopulation of patients weighing less than 50 kg.
- Several sampling criteria can also be combined according to logical operations (Boolean operations).
- the patient sub-population thus selected can then be analyzed.
- the doctor can launch either a pre-established analysis such as of elementary statistical type, bi-varied-regression diagram, evolution diagram, survival curve, non-parametric test (t or Chi-square) ..., or a new analysis that it will create by exploring the information available in the meta-base.
- a pre-established analysis such as of elementary statistical type, bi-varied-regression diagram, evolution diagram, survival curve, non-parametric test (t or Chi-square) ..., or a new analysis that it will create by exploring the information available in the meta-base.
- the doctor needs to define a variable. To do this, he first selects an event in the historic zone 16, in this case the pre-operative event (diagnosis) (fig. 10). In zone 17 of FIG. 10, the tree structure corresponding to the selected pre-operative event (diagnosis) is then displayed. We find the structure of area 17 in Figure 6. The doctor can then browse the structure until reaching the variable "main diagnosis”.
- FIG. 11 is an overall diagram illustrating the information flows between the meta-base, the "Information” database, the events, the sampling module and the analysis module. These last two modules take the information from the. meta-base to perform their functions.
- the analysis function may also require data from sampling to establish graphs in particular 19.
- the dotted flows relate to the "METABASE” information flows, and the solid lines flow relate to the information entered and used. Events are created using data from both METABASE and the database "Information”. Likewise, the input and the exploitation take into account the two databases.
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0214074A FR2847056B1 (fr) | 2002-11-08 | 2002-11-08 | Procede et systeme de traitement de donnees d'evaluation |
FR0214074 | 2002-11-08 | ||
PCT/FR2003/003339 WO2004044813A1 (fr) | 2002-11-08 | 2003-11-07 | Procédé et système de traitement de données d'évaluation |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1590758A1 true EP1590758A1 (fr) | 2005-11-02 |
Family
ID=32116514
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03782536A Withdrawn EP1590758A1 (fr) | 2002-11-08 | 2003-11-07 | Procédé et syst me de traitement de données d'évaluation |
Country Status (5)
Country | Link |
---|---|
US (1) | US20060036408A1 (fr) |
EP (1) | EP1590758A1 (fr) |
AU (1) | AU2003290172A1 (fr) |
FR (1) | FR2847056B1 (fr) |
WO (1) | WO2004044813A1 (fr) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8903794B2 (en) * | 2010-02-05 | 2014-12-02 | Microsoft Corporation | Generating and presenting lateral concepts |
US8983989B2 (en) * | 2010-02-05 | 2015-03-17 | Microsoft Technology Licensing, Llc | Contextual queries |
US8150859B2 (en) | 2010-02-05 | 2012-04-03 | Microsoft Corporation | Semantic table of contents for search results |
US20110231395A1 (en) * | 2010-03-19 | 2011-09-22 | Microsoft Corporation | Presenting answers |
US20110302149A1 (en) * | 2010-06-07 | 2011-12-08 | Microsoft Corporation | Identifying dominant concepts across multiple sources |
US11061918B2 (en) | 2017-04-05 | 2021-07-13 | Splunk Inc. | Locating and categorizing data using inverted indexes |
US11106713B2 (en) * | 2017-04-05 | 2021-08-31 | Splunk Inc. | Sampling data using inverted indexes in response to grouping selection |
US10853399B2 (en) | 2017-04-05 | 2020-12-01 | Splunk Inc. | User interface search tool for locating and summarizing data |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6230142B1 (en) * | 1997-12-24 | 2001-05-08 | Homeopt, Llc | Health care data manipulation and analysis system |
US6820235B1 (en) * | 1998-06-05 | 2004-11-16 | Phase Forward Inc. | Clinical trial data management system and method |
GB2354853A (en) * | 1999-06-09 | 2001-04-04 | Curapath Systems Inc | Computer modelling of health care procedures |
IL152740A0 (en) * | 2000-05-31 | 2003-06-24 | Fasttrack Systems Inc | Clinical trials management system and method |
-
2002
- 2002-11-08 FR FR0214074A patent/FR2847056B1/fr not_active Expired - Fee Related
-
2003
- 2003-11-07 EP EP03782536A patent/EP1590758A1/fr not_active Withdrawn
- 2003-11-07 WO PCT/FR2003/003339 patent/WO2004044813A1/fr not_active Application Discontinuation
- 2003-11-07 US US10/534,297 patent/US20060036408A1/en not_active Abandoned
- 2003-11-07 AU AU2003290172A patent/AU2003290172A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO2004044813A1 * |
Also Published As
Publication number | Publication date |
---|---|
FR2847056A1 (fr) | 2004-05-14 |
WO2004044813A1 (fr) | 2004-05-27 |
AU2003290172A1 (en) | 2004-06-03 |
US20060036408A1 (en) | 2006-02-16 |
FR2847056B1 (fr) | 2006-03-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Al Jarullah | Decision tree discovery for the diagnosis of type II diabetes | |
US20080208624A1 (en) | Methods and systems for providing clinical display and search of electronic medical record data from a variety of information systems | |
US20120066000A1 (en) | Clinical decision support systems with external context | |
AU2006210141A1 (en) | Knowledge discovery tool navigation | |
AU2006210142A1 (en) | Knowledge discovery tool relationship generation | |
CN110709864A (zh) | 人机回环交互式模型训练 | |
US20200303071A1 (en) | Implementation of machine-learning based query construction and pattern identification through visualization in user interfaces | |
Jasper et al. | MouseTrace: A better mousetrap for catching decision processes | |
EP1590758A1 (fr) | Procédé et syst me de traitement de données d'évaluation | |
WO2012093363A2 (fr) | Accès intégré et interaction avec une multiplicité de modules d'analyse de données cliniques | |
EP2504756A1 (fr) | Outil d'exploration et d'analyse de données cliniques | |
US20080270183A1 (en) | Systems and methods for presentation of clinical evidence for diagnostic interpretation | |
Kavitha et al. | Systematic view and impact of artificial intelligence in smart healthcare systems, principles, challenges and applications | |
WO2011163234A1 (fr) | Affichage à facettes sélectionnables par cohorte | |
US8423553B2 (en) | Graphically displaying a file system | |
FR2892840A1 (fr) | Procede et systeme de generation d'un manuel technique. | |
Wietlisbach et al. | Statistical approaches in the development of clinical practice guidelines from expert panels: the case of laminectomy in sciatica patients | |
WO2018229429A1 (fr) | Dispositif de gestion patient | |
Ledieu et al. | Clinical data analytics with time-related graphical user interfaces: Application to pharmacovigilance | |
JP5176617B2 (ja) | メニュー画面表示プログラム、メニュー画面表示方法およびメニュー画面表示装置 | |
JP5003004B2 (ja) | バリアンス根本原因分析支援システム | |
US20130218593A1 (en) | Usage of assigned treatment in clinical decision support systems | |
WO2013177422A1 (fr) | Système de mise en ordre et d'agencement d'un ensemble de données | |
Munsaka et al. | Visual analytics of safety and benefit-risk from clinical trial data | |
EP3686897A1 (fr) | Procédé et unité de traitement de données de sélection d'un programme informatique d'évaluation du risque |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20050527 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
DAX | Request for extension of the european patent (deleted) | ||
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: CHERRAK, ILHEM Inventor name: NODE-LANGLOIS, LAURENT Inventor name: TEMPLIER, ALEXANDRE |
|
17Q | First examination report despatched |
Effective date: 20090409 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20090603 |