G06F16/245

CUSTOM METADATA COLLECTION FOR APPLICATION COMPONENTS IN A VIRTUALIZED COMPUTING SYSTEM

An example method includes: executing, by application analysis software executing in the virtualized computing system, process discovery agents on the VMs; receiving, at the application analysis software from the process discovery agents, process metadata describing processes executing on the VMs; generating signatures for the processes based on the process metadata; determining components of an application based on the signatures; determining components of an application based on the signatures; identifying, for a first component of the components, a component-specific metadata collector; executing, by the application analysis software, the component-specific metadata collector on a first VM of the VMs; and receiving, at the application analysis software from the component-specific metadata collector, custom metadata further describing a first process of the processes associated with the first component.

EVENT-BASED RECORD MATCHING

A method, a structure, and a computer system for event-based record matching. The exemplary embodiments may include extracting one or more events from a first record and a second record, as well as calculating an event-based score based on comparing the one or more events extracted from the first record with the one or more events extracted from the second record. The exemplary embodiments may further include matching the first record to the second record based on the event-based score exceeding a threshold.

EVENT-BASED RECORD MATCHING

A method, a structure, and a computer system for event-based record matching. The exemplary embodiments may include extracting one or more events from a first record and a second record, as well as calculating an event-based score based on comparing the one or more events extracted from the first record with the one or more events extracted from the second record. The exemplary embodiments may further include matching the first record to the second record based on the event-based score exceeding a threshold.

SYSTEM AND METHOD FOR PROVIDING INTELLIGENT ASSISTANCE USING A WARRANTY BOT

Systems and methods are disclosed for a specialized warranty bot that can interact with users to evaluate warranty coverage. A warranty interpreter interprets warranty aspects of a given system and converts the warranty terms it into human understandable text. A situation analyzer enhances warranty interpretation by scanning logs across various components that are covered by the warranty and identifying whether the current problems are covered by the warranty. Assessment guidance processing anticipates questions from the customer and provides information regarding why a problem may not be covered by the warranty. Using a solution advisor, based on the problem details and historical analysis, the warranty bot provides insights regarding potential minimum time for resolution of a problem in order to assist the user to decide whether the system needs to be isolated or if the system can remain in production in a non-critical path.

Methods and apparatus to associate transactions with media impressions

Methods and apparatus to associate transactions with media impressions are disclosed. An example method includes transmitting a request for commercial transaction information to a database proprietor, the request including an identifier corresponding to a media impression associated with media presented via a computing device; receiving the commercial transaction information in response to the request, the commercial transaction information comprising data associated with a commercial transaction conducted using an account accessed by the computing device; and associating the media impression with the commercial transaction.

Methods and apparatus to associate transactions with media impressions

Methods and apparatus to associate transactions with media impressions are disclosed. An example method includes transmitting a request for commercial transaction information to a database proprietor, the request including an identifier corresponding to a media impression associated with media presented via a computing device; receiving the commercial transaction information in response to the request, the commercial transaction information comprising data associated with a commercial transaction conducted using an account accessed by the computing device; and associating the media impression with the commercial transaction.

Computer implemented method for secure management of data generated in an EHR during an episode of care and a system therefor

There is provided a computer implemented method for secure management of data generated in an Electronic Health Record (EHR) during an episode of care, for a user, wherein the EHR is being maintained in a medical database (140) comprised within a Healthcare Service Provider (HSP) server (130), the computer implemented method comprising the steps of sending an identification hash corresponding to the user to an Application Program Interface (API) server (150) from a first client device (110a); extracting the data from the HSP server (130) and de-identifying the data to obtain de-identified data at the API server (150); generating a record hash at the API server (150); transmitting the identification hash, the record hash and the de-identified data from the API server (150) to a core server (160); receiving the identification hash, the record hash and the de-identified data at the core server (160) and transmitting the identification hash, the record hash and the de-identified data from the core server (160) to a repository database (170) to generate a record identification; transmitting the de-identified data, the record hash and the record identification from the repository database (170) to the first client device (110a), via the core server (160); generating a data hash by hashing the de-identified data and a plurality of attributes corresponding to the de-identified data; generating at the core server (160) a register package based on the data hash, the identification hash and the record hash; storing the register package, from the core server (160), on to a blockchain (180) to generate a transaction identification; transmitting the data hash and the transaction identification from the core server (160) to the repository database (170); and transmitting the transaction identification and the data hash from the repository database (170) to the first client device (110a), via the core server (160).

Computer implemented method for secure management of data generated in an EHR during an episode of care and a system therefor

There is provided a computer implemented method for secure management of data generated in an Electronic Health Record (EHR) during an episode of care, for a user, wherein the EHR is being maintained in a medical database (140) comprised within a Healthcare Service Provider (HSP) server (130), the computer implemented method comprising the steps of sending an identification hash corresponding to the user to an Application Program Interface (API) server (150) from a first client device (110a); extracting the data from the HSP server (130) and de-identifying the data to obtain de-identified data at the API server (150); generating a record hash at the API server (150); transmitting the identification hash, the record hash and the de-identified data from the API server (150) to a core server (160); receiving the identification hash, the record hash and the de-identified data at the core server (160) and transmitting the identification hash, the record hash and the de-identified data from the core server (160) to a repository database (170) to generate a record identification; transmitting the de-identified data, the record hash and the record identification from the repository database (170) to the first client device (110a), via the core server (160); generating a data hash by hashing the de-identified data and a plurality of attributes corresponding to the de-identified data; generating at the core server (160) a register package based on the data hash, the identification hash and the record hash; storing the register package, from the core server (160), on to a blockchain (180) to generate a transaction identification; transmitting the data hash and the transaction identification from the core server (160) to the repository database (170); and transmitting the transaction identification and the data hash from the repository database (170) to the first client device (110a), via the core server (160).

Database search method and apparatus

A search apparatus (1) coupled to a database, the apparatus (1) comprising: a processor configured to execute instructions; a memory storing instructions which, when executed by the processor, cause the processor to: search the database for items containing a search term, wherein items containing the search term are matched items; identify fields corresponding to attributes of the matched items; define a range of values for each field; divide the range of values for each field into a plurality of ranged field buckets; distribute the matched items between the ranged field buckets based on attributes of the matched items that are within the range of values for each ranged field bucket; calculate an effectiveness value for each field based on the number of matched items in each of the ranged field buckets; select one or more top fields, each top field having an effectiveness value that is greater than a predetermined effectiveness value; and provide an effectiveness indicator output which is indicative of the effectiveness of each top field such that a user can use the effectiveness indicator output to select a top field for use as a filter in a further search.

System and method of smart framework for troubleshooting performance issues

A system for displaying a performance dashboard comprises an input interface, a processor, and an output interface. The input interface is configured to receive log data. The log data comprises a set of process log entries. The processor is configured to determine one or more daemon response times and to determine dashboard information. The dashboard information is based at least in part on the log data and the one or more daemon response times. The output interface is configured to provide the dashboard information.