WO2015125041A1 - Traitement efficace de fichiers de journalisation associés à un dispositif - Google Patents

Traitement efficace de fichiers de journalisation associés à un dispositif Download PDF

Info

Publication number
WO2015125041A1
WO2015125041A1 PCT/IB2015/050944 IB2015050944W WO2015125041A1 WO 2015125041 A1 WO2015125041 A1 WO 2015125041A1 IB 2015050944 W IB2015050944 W IB 2015050944W WO 2015125041 A1 WO2015125041 A1 WO 2015125041A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
interest
file
log
processor
Prior art date
Application number
PCT/IB2015/050944
Other languages
English (en)
Inventor
Shankar Mosur Venkatesan
Biswaroop CHAKRABARTI
Karthik SUBBARAMAN
Nagaraju Bussa
Anand Srinivasan SRINIVASAN NATESAN
Deep Bera
Original Assignee
Koninklijke Philips N.V.
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 Koninklijke Philips N.V. filed Critical Koninklijke Philips N.V.
Priority to US15/116,257 priority Critical patent/US20170011101A1/en
Priority to CN202210246035.8A priority patent/CN114639473A/zh
Priority to EP15713015.4A priority patent/EP3108366A1/fr
Priority to CN201580009225.6A priority patent/CN106030590A/zh
Priority to JP2016569113A priority patent/JP6967350B2/ja
Publication of WO2015125041A1 publication Critical patent/WO2015125041A1/fr

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00—Subject matter not provided for in other main groups of this subclass
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/248—Presentation of query results
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2228—Indexing structures
    • G06F16/2246—Trees, e.g. B+trees
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/81—Indexing, e.g. XML tags; Data structures therefor; Storage structures
    • 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/40—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 management of medical equipment or devices, e.g. scheduling maintenance or upgrades
    • 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
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3476—Data logging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0485—Scrolling or panning
    • G06F3/04855—Interaction with scrollbars

Definitions

  • the following generally relates to efficient processing of device related (e.g., device, service, etc.) log files for devices including, but not limited to, a medical and/or a non-medical imager (e.g., computed tomography (CT), X-ray, Ultrasound (US), magnetic resonance (MR), positron emission tomography (PET), single photon emission computer tomography (SPECT), etc.) and/or non-imaging equipment.
  • CT computed tomography
  • US Ultrasound
  • MR magnetic resonance
  • PET positron emission tomography
  • SPECT single photon emission computer tomography
  • Some electro-mechanical software devices are configured to generate log files that include system and/or operational parameters.
  • the log files from multiple devices located at a facility typically are stored as flat files.
  • a flat file generally, is a single file with a serial stream of all the system and/or operational parameters of the devices.
  • Flat files from multiple facilities within a network of facilities are often periodically sent to and archived in a server and/or database.
  • the flat file with the device log files of the device are retrieved from the archive and manually evaluated by a field service engineer.
  • a flat file of device log files can include megabytes, gigabytes, terabytes, etc. of data, and the field service engineer may have to read through a large volume of this data to locate only kilobytes of data that provide any clue as to why the event might have occurred.
  • An immediate and direct consequence is that an end user or customer may face device downtime and losses that could have been avoided if the pertinent device log files were promptly extracted based on enhanced debug logging mechanism based on types of error events from the flat file, evaluated, and used to predict or prevent reoccurrence of the event.
  • Such information can also be used in connection with the design of future devices, for example, based on the analysis of the event from a technical and/or a reliability point of view.
  • Field service engineers who visit and repair or service the particular device, generate electronically formatted reports or service log files that memorialize the visit. Such reports may include troubleshooting steps, diagnostics performed to determine and/or fix the problem, results of the service visit, etc. Similar to device log files, the service log files typically are just archived, and no attempt is made to derive information from the log files.
  • Automated or semi-automated approaches can be employed to evaluate the log files.
  • approaches lack features, and otherwise well-designed devices that could potentially be serviced in days are serviced in weeks or longer, resulting in loss of customer revenue, satisfaction, and brand loyalty.
  • the following describes an approach to capture and organize device and/or service logs, using layered, efficient, and virtual streams defined by a template and debug levels, which can be machine learned over time to build a knowledge based system over time.
  • the following further describes an approach to present the log data in visual concept maps, which can provide productive and fast navigation along time, topic, item, and concept axes.
  • a method includes searching a single file, which includes a plurality of device log files for one or more devices, based on a template file that at least indicates a sub-set of log data of interest. The method further includes generating reference data for each of the log data of interest that is located in the single file. The method further includes storing the reference data in a data structure.
  • a computing system in another aspect, includes a memory that stores one or more instructions including a log file processing module.
  • the computing system further includes a processor that executes the one or more instructions, which causes the processor to: filter log data based on a template file that indicates streams of data of interest;
  • a computer readable storage medium is encoded with one or more computer executable instructions.
  • the one or more computer executable instructions when executed by a processor of a computing system, causes the processor to: retrieve, using references, a sub-set of log data from a flat file of log data, in response to a user input, which includes at least an indication of data of interest to the user, and display only the retrieved sub-set of log data in a predetermined organized manner in a user-interactive navigational graphical user interface.
  • the invention may take form in various components and arrangements of components, and in various steps and arrangements of steps.
  • the drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention.
  • FIGURE 1 schematically illustrates an example log server, which includes a log file processing module, in connection with a plurality of devices and a device log file memory.
  • FIGURE 2 schematically illustrates an example of the log file processing module of the log server of FIGURE 1.
  • FIGURE 3 schematically illustrates a variation of the log file processing module of FIGURE 2, which includes a search engine.
  • FIGURE 4 schematically illustrates a variation of the log file processing module of FIGURE 2, which includes one or more additional filters.
  • FIGURE 5 schematically illustrates a variation of the log file processing module of FIGURE 2, which includes the search engine of FIGURE 3, the one or more additional filters of FIGURE 4, and a template file updater.
  • FIGURE 6 schematically illustrates a variation of the log file processing module of FIGURE 2, which includes a concept map generator.
  • FIGURE 7 schematically illustrates an example time based concept map generated by the concept map generator of FIGURE 6.
  • FIGURE 8 schematically illustrates an example topic based concept map generated by the concept map generator of FIGURE 6.
  • FIGURE 9 schematically illustrates an example modality based concept map generated by the concept map generator of FIGURE 6.
  • FIGURE 10 schematically illustrates an alternative display using textual indicia instead of a concept map.
  • FIGURE 11 schematically illustrates another alternative display using textual indicia instead of a concept map.
  • FIGURE 12 illustrates an example method in accordance with the
  • a log server 100 is schematically illustrated in connection with a plurality of devices 102 and a device log file memory 104.
  • the illustrated devices include a CT imaging system 128, an MR imaging system 130, a SPECT imaging system 132, a PET imaging system 134, ... , other imaging system 136, a service computer 138, and/or other device 140. Examples of the CT, MR, SPECT, and PET imaging systems 128-134 are described below.
  • the log server 100 processes, at least, log files generated by one or more of the plurality of devices 102.
  • the log files can be obtained, for example, over a (wireless and/or wired) network 106 (e.g., the Internet, a wide area network, a local area network, etc.), by the log server 100, for example, directly from the plurality of devices 102 and/or from the device log file memory 104, which stores at least a sub-portion of the log files.
  • the log files can also be obtained through portable storage medium.
  • a device of the plurality of devices 102 can transmit one or more log files over the network 106 as a single file such as a single flat file.
  • a file may include multiple log files that are serially streamed with no structural relationship between the data and/or the log files therein.
  • Suitable formats include comma-separated, delimiter-separated, and/or other flat files. Other formats, including structured formats are also contemplated herein.
  • a flat file generated by one of the devices 102 can include information about the scans performed since the last flat file transmission and/or system state information, even when no scan is performed.
  • the log file may include patient identifiers, imaging protocol identifiers, scan time lengths, kV settings, mA settings, system temperatures, a list of calibration routines performed, etc.
  • a flat file from one facility may look something like the following:
  • a flat file consists of value pairs which can be parsed using a pre-defined grammar based parser and stored in a file format such as XML and/or file format.
  • a service report log file from the service computer 138 may include textual information such as troubleshooting steps, diagnostics performed, results obtained, etc.
  • the single flat file can by pushed by the one of the plurality of devices 102 and/or pulled by the log server 100, for example, based on a predetermined schedule, on demand, etc.
  • the plurality of devices 102 can include two or more of a same type of device, (i.e., two or more CT imagers, for example).
  • One or more of the plurality of devices 102 can be at a same or different physical location (e.g., within a same physical facility or entity), a same or different geographical location (e.g., same or different state, country, etc.), etc.
  • the log server 100 includes a computing system 108, an output device 110 and an input device 112.
  • the output device 110 includes a human readable output device such as a physical hardware based display monitor and/or the like.
  • the input device 112 includes one or more of a keyboard, mouse, touchscreen region of the display monitor, and/or the like.
  • the computing system 108 includes a computer readable storage medium (“local memory”) 114 and a processor 116.
  • the local memory 114 includes physical memory and/or other non-transitory storage medium and excludes transitory medium.
  • the local memory 114 stores data 118 and at least one computer executable instructions ("instruction") 120.
  • the data 118 includes at least log files 122, which can be the same log files stored in the device log file memory 104 and/or other log files, and virtual log files 124.
  • the virtual log files 124 include only references to a sub-set of the log files stored in the device log file memory 104 and/or the log files 120 stored in the local memory 114.
  • the instruction 120 includes at least a log file processing module 126.
  • the log file processing module 126 processes contents of log files in single files based on predetermined criteria, creates organized references for a sub-set of data in the log files, retrieves at least a sub-portion of the sub-set from the device log file memory 104, extracts most relevant parameters from the log files using processor 116 and/or the log files 122 based on an input signal from the input device 112 using the references, and displays the retrieved sub-portion of the data, which may include displaying retrieved data via one or more content maps visually displayed in a graphical user interface (GUI).
  • GUI graphical user interface
  • the processor 116 decides the amount of the logs to be stored in device memory 104 based on the debug level changes made based on the error events in devices 102.
  • the organization of the data and display of the sub-portion of the data can provide for quick and/or intuitive visual navigation of large volumes of complex device and/or service log files and subsequent resolution of device issues.
  • log files can be efficiently processed and used to troubleshoot and fix devices, identify warning signs and/or rare events, predict device degradation and/or failure, design future devices, etc.
  • device downtime can be mitigated, service time can be reduced, etc., which can reduce the cost of a device associated with device downtime and repair, and increase device uptime and billable time.
  • the processor 116 is, for example, a microprocessor, a central processing unit, a controller, or the like.
  • the processor 116 implements the at least one instruction 120, including the log filed processing module 126.
  • the log server 100 can also communicate with other log servers and/or computing systems.
  • An example CT imaging system 128 includes a stationary gantry and a rotating gantry, which is rotatably supported by the stationary gantry and rotates around an examination region about a z-axis.
  • a radiation source such as an x-ray tube, is rotatably supported by the rotating gantry, rotates with the rotating gantry, and emits radiation that traverses the examination region.
  • a radiation sensitive detector array subtends an angular arc opposite the radiation source across the examination region. The detector array detects radiation traversing the examination region and generates projection data indicative thereof.
  • a reconstructor reconstructs the projection data, generating 3D volumetric image data.
  • An example MR imaging system 130 includes a main magnet, gradient (x, y, and z) coils, and a RF coil.
  • the main magnet (superconducting, resistive, or permanent) produces a substantially homogeneous, temporally constant main magnetic field B 0 in the examination region.
  • the gradient coils generate time varying gradient magnetic fields along the x, y, and z-axes of the examination region.
  • the RF coil produces radio frequency signals (at the Larmor frequency of nuclei of interest (e.g., hydrogen, etc.)) that excite the nuclei of interest in the examination region and receive MR signals emitted by the excited nuclei.
  • a MR data acquisition system processes the MR signals, and a MR reconstructor reconstructs the data and generates MR images.
  • An example SPECT imaging system 132 includes a gamma radiation detector and a collimator, which is disposed between an examination region and the gamma radiation detector.
  • the collimator includes radiation attenuating septa that only allow gamma radiation having a certain angle of incidence to reach the gamma detector.
  • Gamma rays are acquired from a number of angles with respect to the examination region by rotating the gamma radiation detector around the examination region.
  • the detector generally is positioned close to the subject under evaluation.
  • a SPECT reconstructor reconstructs the projections to produce volumetric data representative of the distribution of the radioisotope emitting the gamma rays in the object or subject.
  • An example PET imaging system 134 includes a ring of gamma radiation detectors arranged around an examination region.
  • the detectors are configured to detect 511 keV gamma rays indicative of electron-positron decays occurring in an examination region. Most decays result in two 511 keV gamma rays emitted almost 180 degrees to each other, and PET scanners localize the source along a line of response (LOR) there between.
  • the detectors convert the photons into a corresponding electrical signal, and a coincidence event identifier identifies coincident gamma pairs by identifying photons detected in temporal coincidence. The identified pairs are used to generate data indicative of the spatial distribution of the decays.
  • the other imaging system 136 may include an x-ray imaging system, an ultrasound imaging system, etc.
  • the service computer 138 may include a laptop, a desktop, a tablet, etc. computer, a smartphone, and/or other computing device.
  • the other device 140 may include another medical device and/or a non-medical device.
  • FIGURE 2 illustrates an example of the log file processing module 126.
  • the illustrated log file processing module 126 includes a file filter 202.
  • the file filter 202 in the illustrated embodiment, filters flat files of file logs. As discussed herein, such files can be obtained in streams from the plurality of devices 102, the device log file memory 104.
  • the illustrated log file processing module 126 further includes a template file 204 that indicates the log files and/or log data that references will be created for.
  • the template file 204 may indicate (e.g., via a symbolic tag or regular expression and/or otherwise) that a reference is to be created to a log file for a particular type of device (e.g., "CT"), a particular geographical location (e.g., "OH”), etc.
  • CT type of device
  • OH geographical location
  • the template file 204 may also indicate other information such a debug level for the data.
  • the template file 204 can be formatted in a human and computer readable format such as a markup language (e.g., Extensible Markup Language (XML), etc.), a B-tree, and/or other format.
  • a markup language e.g., Extensible Markup Language (XML), etc.
  • XML Extensible Markup Language
  • An initial template file can be created through user interaction in which a user indicates the log data of interest.
  • the template file 204 can be updated through similar user interaction and/or machine learning approaches.
  • the template file 204 may indicate that a reference is to be created for all instances of log files with the string "OH.”
  • the file filter 202 reads the flat file and locates the string "OH.”
  • the file filter 202 locates the log files /facility:OfficeZ/state:OH/temp:21°C/... and /facility:HospitalX/state:OH/Name: JohnDoe/device:CT/protocol:Chest/kV: 100/....
  • this example is provided for explanatory purposes and is not limiting.
  • the file filter 202 in response to finding a log file in the flat file as indicated by the template file 204, generates a signal.
  • the illustrated log file processing module 126 further includes a reference generator 206 that, in response to receiving the signal, generates a reference for the log file.
  • the reference includes an address to a memory location that stores an address to the corresponding log file in the stored flat file.
  • An example of such a reference is a pointer.
  • the reference generator 206 alternatively, generates a first reference for one or more data elements in the log file and a second reference, or an address to a memory location that stores a debug level value.
  • the template file 204 may indicate that data “kV” is level “5,” “high,” etc. and that data “protocol” is level “3,” “medium,” etc., and not assign a level to data “Name” or assign a level "0,” “low,” etc.
  • the reference generator 206 stores the reference to a log data in reference data 208 of the virtual log files 124. In the instance where a debug level is provided, the reference generator 206 stores the references to the log data and to the debug level in the reference data 208 of the virtual log files 124.
  • the reference data 208 in one non-limiting instance, is stored in a data structure, which provides a predetermined organization of the references.
  • the illustrated log file processing module 126 further includes logic 210.
  • the logic in response to receiving an input signal, which indicates a particular data facility (e.g., "HospitalX") along with a particular debug level (e.g., "medium to high") from the input device 112, retrieves all the references from the reference data 208 that corresponds to the data with the debug level "medium to high” from the log file for "HospitalX".
  • the logic 210 would retrieve the portion of the log file that includes the string "100” or the value 100 and the string "Chest.”
  • the logic 210 will correspondingly increase or decrease the amount of the device log file memory 104 for storing log file information.
  • the logic 210 in response to receiving a subsequent input signal (indicative of data of interest to the user) from the input device 112, which indicates other data and/or debug level, retrieves data and updates the results accordingly.
  • the illustrated log file processing module 126 further includes a rendering engine 212 that formats the retrieved data in a human readable format and displays the formatted data through the output device 112.
  • FIGURE 3 illustrates a variation of FIGURE 2 in which the log file processing module 126 further includes a search engine 302.
  • the search engine 302 allows the user to search the stored log files and/or stored references. This can be achieved by providing, via the input device 112, search terms to the search engine 302, and invoking, via the input device 112, the search engine 302 to perform a search based on the search terms through the logic 210.
  • the search terms in one instance, may correspond to data that is relevant to the user for the particular task.
  • a separate index can be created and persisted for each static stream, and dynamic streams can be created as needed for each debug session.
  • the presented search results can be ranked or unranked.
  • FIGURE 4 illustrates a variation of FIGURE 2 in which the log file processing module 126 further includes a one or more additional filters 402.
  • a particular filter may inhibit or remove certain data from display and/or from data retrieval. Such data may be data that is not relevant or is less relevant to the particular task.
  • a filter(s) can be selected and/or deselected through the input device 112 and/or otherwise. Examples of suitable filters include, but are not limited to, time window; frequency count; rareness criteria (e.g., season, humidity, time of day, etc.), symbolic tag subset restriction, prior event points annotated earlier for debugging purpose showing importance for cause-effect analysis, etc.
  • FIGURE 5 illustrates a variation of FIGURE 2 that includes the search engine 302 of FIGURE 3, the one or more additional filters 402 of FIGURE 4, and template updater 502 and/or the one or more additional filters 402.
  • the template updater evaluates activity and/or results of the search engine 302 and/or the one or more additional filters 402.
  • the evaluation in one instance, trends the results and determines a frequency in which retrieved log data is removed from display and/or previously unretrieved log data is retrieved and displayed.
  • Machine learning and/or other approaches can learn from the evaluation and update the template file 204 to include additional data tags and/or remove data tags.
  • the search engine 302 is omitted.
  • the one or more additional filters 402 are omitted.
  • FIGURE 6 illustrates a variation of FIGURE 2 that includes a concept map generator 602 that generates one or more concepts maps which include graphical indicia that is link or map to the reference data 208 and hence the log files and data, and visually organizes the data, for example, based on time, topic, modality, importance, events, trends, concept, search, etc.
  • a concept map generator 602 that generates one or more concepts maps which include graphical indicia that is link or map to the reference data 208 and hence the log files and data, and visually organizes the data, for example, based on time, topic, modality, importance, events, trends, concept, search, etc.
  • FIGURES 7-10 illustrates the concept map for selecting different metadata information extracted from the device log files along with search interface with filters to dynamically visualize concept maps.
  • a time bar 702 provides a plurality of time ranges, for example, time ranges 704i, ... , 704 N , where N is a positive integer, in which data can be retrieved.
  • the data can correspond to a modality 706, a geographical and/or vendor location 708, a particular model 710 of a modality, cost and/or parts 712, etc.
  • a dialogue box 714 indicates a current selection of choices.
  • a results window 716 includes links to data.
  • FIGURE 8 A non-limiting example of a topic concept map is shown in FIGURE 8.
  • data is available for one or more topics 802, without any time restriction.
  • FIGURE 9 A non-limiting example of a modality concept map is shown in FIGURE 9.
  • the concept in FIGURE 9 also includes individual tabs for switching between modality, time, topic, etc. concept maps.
  • the concept maps included graphical indicia.
  • the information in a concept map can be visualized in a 2D, 3D and/or other form.
  • the information in a concept map may be expandable, zoomable, collapsible, and/or otherwise manipulable via the input device 112 (e.g.,
  • annotations e.g., key concepts
  • links between data can be manually and/or automatically added.
  • log data can be compared and/or analyzed to identify or provide information that can be used to identify warnings, mistakes, erroneous actions, machine deterioration, etc. to identify errors and corrective actions. Furthermore, log data can be used to find or provide information that can be used to find connections between the logs and key performance indicators (KPIs), and/or infer or provide information that can be used to infer multiple and alternate pathways for optimizing KPFs.
  • KPIs key performance indicators
  • the log data can also be used to infer or provide information that can be used to infer future behavior based on the past and the present, and/or predict or provide information that can be used to predict future course of action from the past history.
  • the log data can also be used to estimate or provide information that can be used to estimate and/or volume/velocity/variety and/or project or provide information that can be used to project future needs along multiple dimensions.
  • the log data can also be used to predict or provide information that can be used to predict future rare events such as disastrous machine failure from the past records, and/or provide high alerts in such situations.
  • the foregoing can be achieved in a periodic, a dynamic, and/or automated or semi-automated manner with user confirmation and/or override.
  • FIGURE 12 illustrate methods in accordance with the embodiments herein.
  • flat files including at least device log files and optionally service and/or other log files, are accessed.
  • the flat files can be received in a data stream, retrieved from memory, and/or otherwise accessed.
  • the flat files are filtered based on a template to locate a predetermined set of data in the flat files.
  • the template may include tags to relevant data and, optionally, debug levels and/or other information.
  • references which provide references to the located data in the flat files, are generated for the located data.
  • references are stored based on a predetermined organization.
  • a first signal which includes at least one or more data types of interest, is received.
  • the first signal may also include debug level and/or other information.
  • references are utilized to retrieve data from the flat files based on the first signal.
  • the retrieved data is visually presented in concept map and/or otherwise.
  • a second signal which indicates a filter that removes unwanted data, is received.
  • the displayed data is updated based on the filter results.
  • a third signal which provides at least one search term for data not already displayed, is received.
  • the flat files and/or references are searched based on the third signal.
  • the displayed data is updated based on the search results.
  • acts 1216 and 1218 and/or acts 1220, 1222 and 1224 are omitted.
  • the above methods may be implemented by way of computer readable instructions, encoded or embedded on computer readable storage medium, which, when executed by a computer processor(s), cause the processor(s) to carry out the described acts. Additionally or alternatively, at least one of the computer readable instructions is carried by a signal, carrier wave or other transitory medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Theoretical Computer Science (AREA)
  • Biomedical Technology (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Public Health (AREA)
  • Primary Health Care (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Epidemiology (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Computational Linguistics (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé qui consiste à rechercher un fichier unique, qui comprend une pluralité de fichiers de journalisation de dispositif pour un ou plusieurs dispositifs, sur la base d'un fichier de modèle qui indique au moins un sous-ensemble de données de journalisation d'intérêt, à générer des données de référence pour chacune des données de journalisation d'intérêt qui sont situées dans le fichier unique, et à stocker les données de référence dans une structure de données. Un système informatique (102) comprend une mémoire (114) qui stocke une ou plusieurs instructions (120) comprenant un module de traitement de fichier de journalisation (126), et un processeur (116) qui exécute la ou les instructions, qui amène le processeur : à filtrer des données de journalisation sur la base d'un fichier de modèle qui indique des flux de données d'intérêt ; à modifier dynamiquement la quantité de données d'intérêt sur la base du niveau de débogage ; à stocker les flux de données d'intérêt ; et à afficher, en réponse à un signal d'entrée, un sous-ensemble du flux virtuel stocké de données d'intérêt.
PCT/IB2015/050944 2014-02-18 2015-02-09 Traitement efficace de fichiers de journalisation associés à un dispositif WO2015125041A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US15/116,257 US20170011101A1 (en) 2014-02-18 2015-02-09 Efficient processing of device related log files
CN202210246035.8A CN114639473A (zh) 2014-02-18 2015-02-09 设备相关日志文件的有效处理
EP15713015.4A EP3108366A1 (fr) 2014-02-18 2015-02-09 Traitement efficace de fichiers de journalisation associés à un dispositif
CN201580009225.6A CN106030590A (zh) 2014-02-18 2015-02-09 设备相关日志文件的有效处理
JP2016569113A JP6967350B2 (ja) 2014-02-18 2015-02-09 装置関連のログファイルの効果的な処理

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201461941097P 2014-02-18 2014-02-18
US61/941,097 2014-02-18

Publications (1)

Publication Number Publication Date
WO2015125041A1 true WO2015125041A1 (fr) 2015-08-27

Family

ID=52774292

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2015/050944 WO2015125041A1 (fr) 2014-02-18 2015-02-09 Traitement efficace de fichiers de journalisation associés à un dispositif

Country Status (5)

Country Link
US (1) US20170011101A1 (fr)
EP (1) EP3108366A1 (fr)
JP (2) JP6967350B2 (fr)
CN (2) CN114639473A (fr)
WO (1) WO2015125041A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9524315B1 (en) 2016-03-31 2016-12-20 Sas Institute Inc. Date updating in support of data analysis
WO2017173344A1 (fr) * 2016-03-31 2017-10-05 Mentor Graphics Corporation Identification d'erreurs clé dans un système présentant un grand nombre d'événements d'erreur
WO2018039446A1 (fr) * 2016-08-26 2018-03-01 Nec Laboratories America, Inc. Système de recommandation pour une opération d'édition de motifs de journaux hétérogènes
US11935646B1 (en) * 2018-03-26 2024-03-19 Glassbeam, Inc. Predicting medical device failure based on operational log data

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170011101A1 (en) * 2014-02-18 2017-01-12 Koninklijke Philips N.V. Efficient processing of device related log files
US11278250B2 (en) * 2015-11-13 2022-03-22 Rensselaer Polytechnic Institute Simultaneous interior MRI X-ray imaging system (MRX)
US10339102B2 (en) * 2016-09-30 2019-07-02 Vmware, Inc. Automating script creation for a log file
US11113138B2 (en) 2018-01-02 2021-09-07 Carrier Corporation System and method for analyzing and responding to errors within a log file
WO2023110577A1 (fr) * 2021-12-13 2023-06-22 Koninklijke Philips N.V. Exploration interactive sensible au contexte de bilans de service de maintenance
EP4276626A1 (fr) * 2022-05-13 2023-11-15 Koninklijke Philips N.V. Résolution d'anomalies de dispositif d'imagerie médicale

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060184529A1 (en) * 2005-02-16 2006-08-17 Gal Berg System and method for analysis and management of logs and events
EP2282449A2 (fr) * 2009-08-05 2011-02-09 Loglogic, Inc. Descriptions de messages
US20140025995A1 (en) * 2012-07-19 2014-01-23 Dell Products L.P. Large log file diagnostics system

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6128613A (en) * 1997-06-26 2000-10-03 The Chinese University Of Hong Kong Method and apparatus for establishing topic word classes based on an entropy cost function to retrieve documents represented by the topic words
US5963982A (en) * 1997-07-02 1999-10-05 Webtv Networks, Inc. Defragmentation of stored data without pointer indirection
JP2002245257A (ja) * 2001-02-16 2002-08-30 Glory Ltd 自動機器の監視システム及び監視方法
JP4050497B2 (ja) * 2001-11-06 2008-02-20 インフォサイエンス株式会社 ログ情報管理装置及びログ情報管理プログラム
JP2005141663A (ja) * 2003-11-10 2005-06-02 Hitachi Ltd イベントログ解析支援装置、イベントログ表示方法
US7769709B2 (en) * 2004-09-09 2010-08-03 Microsoft Corporation Method, system, and apparatus for creating an archive routine for protecting data in a data protection system
CN100518079C (zh) * 2004-09-30 2009-07-22 北京航空航天大学 分布式性能数据采集方法
CN100357900C (zh) * 2005-01-20 2007-12-26 上海复旦光华信息科技股份有限公司 基于模板的异构日志信息自动提取与分析方法
US7822850B1 (en) * 2008-01-11 2010-10-26 Cisco Technology, Inc. Analyzing log files
JP5444673B2 (ja) * 2008-09-30 2014-03-19 富士通株式会社 ログ管理方法、ログ管理装置、ログ管理装置を備えた情報処理装置、及びプログラム
CN101609610B (zh) * 2009-07-17 2011-06-15 中国民航大学 一种航班信息数据采集器及其处理方法
US8321433B1 (en) * 2011-05-06 2012-11-27 Sap Ag Systems and methods for business process logging
US9811667B2 (en) * 2011-09-21 2017-11-07 Mcafee, Inc. System and method for grouping computer vulnerabilities
US20170011101A1 (en) * 2014-02-18 2017-01-12 Koninklijke Philips N.V. Efficient processing of device related log files

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060184529A1 (en) * 2005-02-16 2006-08-17 Gal Berg System and method for analysis and management of logs and events
EP2282449A2 (fr) * 2009-08-05 2011-02-09 Loglogic, Inc. Descriptions de messages
US20140025995A1 (en) * 2012-07-19 2014-01-23 Dell Products L.P. Large log file diagnostics system

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "ManageEngine EventLog Analyzer 8 - User Guide", 2012, pages 1 - 218, XP055195399, Retrieved from the Internet <URL:https://www.manageengine.com/products/eventlog/eventloganalyzer-userguide.pdf> [retrieved on 20150612] *
See also references of EP3108366A1 *
VIVEK SUNDARAM: "The Glassbeam for Medical - Analyzing MRI machine logs by Categories", 18 September 2013 (2013-09-18), pages 1 - 3, XP055195915, Retrieved from the Internet <URL:http://www.glassbeam.com/analyzing-mri-machine-logs/> [retrieved on 20150615] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9524315B1 (en) 2016-03-31 2016-12-20 Sas Institute Inc. Date updating in support of data analysis
WO2017173344A1 (fr) * 2016-03-31 2017-10-05 Mentor Graphics Corporation Identification d'erreurs clé dans un système présentant un grand nombre d'événements d'erreur
US11385986B2 (en) 2016-03-31 2022-07-12 Siemens Industry Software Inc. Identification of key errors in a system having a large number of error events
WO2018039446A1 (fr) * 2016-08-26 2018-03-01 Nec Laboratories America, Inc. Système de recommandation pour une opération d'édition de motifs de journaux hétérogènes
US11935646B1 (en) * 2018-03-26 2024-03-19 Glassbeam, Inc. Predicting medical device failure based on operational log data

Also Published As

Publication number Publication date
US20170011101A1 (en) 2017-01-12
JP7313406B2 (ja) 2023-07-24
CN114639473A (zh) 2022-06-17
EP3108366A1 (fr) 2016-12-28
JP2017506790A (ja) 2017-03-09
JP2021185496A (ja) 2021-12-09
JP6967350B2 (ja) 2021-11-17
CN106030590A (zh) 2016-10-12

Similar Documents

Publication Publication Date Title
JP7313406B2 (ja) 装置関連のログファイルの効果的な処理
US10394770B2 (en) Methods and systems for implementing a data reconciliation framework
US9665918B2 (en) Medical data generating apparatus and medical data generating method
US20170004151A1 (en) Specifying and applying rules to data
US20100088346A1 (en) Method and system for attaching objects to a data repository
US20080201350A1 (en) Context-based Information Retrieval
US20080025583A1 (en) System and method for on-demand visual enhancement of clinical conitions in images
US20140310584A1 (en) Medical care information display control apparatus, medical care information display control method, and medical care information display control program
EP3899726A1 (fr) Procédé d&#39;évaluation efficace d&#39;un modèle de journal
CN108352185A (zh) 用于伴随发现的纵向健康患者简档
US20210183487A1 (en) Cognitive patient care event reconstruction
US20220223272A1 (en) Configuration anomaly detection in medical system configurations using frequent pattern mining
US10402967B2 (en) Device, system and method for quality assessment of medical images
Li et al. Automated extraction of radiation dose information from CT dose report images
US8566122B2 (en) Method and apparatus for navigation to unseen radiology images
US20220309474A1 (en) Maintenance history visualizer to facilitate solving intermittent problems
JP4991128B2 (ja) 画像管理システム、画像表示装置、管理サーバ、及び画像データ管理方法
US7639852B2 (en) Method for associating data with medical image datasets
US11189026B2 (en) Intelligent organization of medical study timeline by order codes
JP2013005841A (ja) 画像処理フロー評価方法及び当該方法を実行する画像処理装置
US20210174485A1 (en) Systems and methods for detecting anomalies using image based modeling
Santos et al. DICOM metadata aggregation from multiple healhtcare facilities
JP2005182179A (ja) 画像検索システム、プログラム
CN118215971A (zh) 用于从异构信息源提取诊断和解决流程的系统和方法
WO2023110411A1 (fr) Affichage de rapports antérieurs pertinents dans un contexte de télémédecine

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015713015

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015713015

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15116257

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2016569113

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE