# US 10,482,427 B2 · System and method for concept discovery with online information environments

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,482,427 B2
- Document ID: US10482427B2
- Status: Granted
- Kind: B2
- Application number: 14/202,277
- Filed: 2014-03-10
- Published: 2014-10-16
- Granted: 2019-11-19
- Earliest claimed: 2013-03-14
- Assignees: Worldone, Inc.
- Applicants: Worldone, Inc.
- Inventors: George Abraham; Lik Fun Chan-Do; Jason Robert Hillebrecht; Jonathan S. Michaeli; Pieter Sheth-Voss
- Web page: https://patentgrep.com/patent/US10482427B2

## CPC

- G06Q 10/1053: Employment or hiring
- G06F 3/0484: 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
- G06F 16/2457: with adaptation to user needs
- G06F 16/30: of unstructured textual data (document management systems G06F16/93)
- G06F 16/951: Indexing; Web crawling techniques
- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Provided are systems and methods for referencing intent-based taxonomies to enable more natural approaches for users to specify problems to be solved, questions to be answered, and other content requests that can be delivered within online communities. In the medical setting, physicians and medical personnel are accustomed to provide medical information and ask questions of other physicians in the form of a narrative which can be organized around medical cases. Intuitive user interfaces are provided that facilitate definition of intent during case generation and case searching. Linking UI displays and narrative data structures associated with intent information can enable definition and navigation of intent-based models of the cases. Intent-based models can reflect standardize concepts (e.g., medical diagnoses and medical concept ontologies) facilitating their navigation based on intent. Further, the intent-based models of cases can include additional close-ended selections in the UI to further interact with intent-based models of cases.

## Claims

### Claim 1

A system for interacting with an online information environment, the system comprising:
at least one processor operatively connected to a memory, the at least one processor configured to execute a plurality of system components from the memory, the system components comprising a user interface component configured to:
display a creation view configured for creating a case and comprising an open-ended text field to receive text indicative of a chief complaint of a patient and a first close-ended data field to receive a parameter indicative of an age of the patient;
generate and display a list of suggested clinical terms to add to the open-ended text field using at least one text fragment from the text indicative of the chief complaint of the patient and the age of the patient;
identify and emphasize key terms in the text indicative of the chief complaint of the patient the open-ended text field;
assign one or more classification tags to the case based on the identified key terms;
display a response view configured for responding to the case and comprising a display of information regarding the case, a display of at least one previously submitted response to the case, and an open-ended text field to receive a response to the case;
display a search view configured for searching a database of cases, the database configured to store the cases as data objects including case information, the case information including a question, a specialty requirement for the case, and at least one concept, and comprising a search field; and
match terms in the search field with the one or more classification tags to identify relevant cases.

### Claim 2 (depends on 1)

The system according to claim 1, further comprising an ontology database storing clinical terms organized by concept and wherein the user interface component is configured to generate the list of suggested clinical terms at least on part by matching the at least one text fragment with concepts from the ontology database.

### Claim 3 (depends on 1)

The system according to claim 1, wherein the creation view includes a first section comprising the first close-ended data field and a second close-ended data field.

### Claim 4 (depends on 3)

The system according to claim 3, wherein the second close ended data field in the first section of the creation view accepts data into the specialty requirement parameter of the case.

### Claim 5 (depends on 3)

The system according to claim 3, wherein the creation view includes a second section comprising at least one data field that is configurable between an open-ended data field and a close-ended data field.

### Claim 6 (depends on 5)

The system according to claim 5, wherein the at least one data field that is configurable between an open-ended data field and a close-ended data field accepts data into the question parameter of the case.

### Claim 7 (depends on 1)

The system according to claim 1, wherein the response view includes a first section configured to display the question, the specialty requirement, and the at least one concept of the case.

### Claim 8 (depends on 1)

The system according to claim 1, wherein the user interface component is configured to continuously update a list of cases in a second section of the search view responsive to text input into a first open-ended text parameter in a first section of the search view.

### Claim 9 (depends on 8)

The system according to claim 8, wherein the search view includes a third section configured to graphically display statistics of the list of cases in the second section of the search view.

### Claim 10 (depends on 9)

The system according to claim 9, wherein the search view includes a fourth section configured to graphically display the frequency of concepts in the list of cases.

### Claim 11 (depends on 1)

The system according to claim 1, wherein the user interface component is configured to transition from the creation view to the search view responsive to user input.

### Claim 12

A computer implemented method for interacting with an online environment, the method comprising:
displaying a creation view configured for creating a case and comprising an open-ended text field to receive text indicative of a chief complaint of a patient and a first close-ended data field to receive a parameter indicative of an age of the patient;
generating and displaying a list of suggested clinical terms to add to the open-ended text field using at least one text fragment from the text indicative of the chief complaint of the patient and the age of the patient;
identifying and emphasizing key terms in the open-ended text field;
assigning one or more classification tags to the case based on the identified key terms;
displaying a response view configured for responding to a case and comprising a display of information regarding the case, a display of at least one previously submitted response to the case, and an open-ended text field to receive a response to the case;
displaying a search view configured for searching a database of cases, the database configured to store the cases as data objects including case information, the case information including a question, a specialty requirement for the case, and at least one concept, and comprising a search field; and
matching terms in the search field with the one or more classification tags to identify relevant cases.

### Claim 13 (depends on 12)

The method according to claim 12, wherein generating and displaying the list of suggested clinical terms comprises communicating with an ontology database storing medical terms organized by concept and matching the at least one text fragment with concepts from the ontology database.

### Claim 14 (depends on 12)

The method according to claim 12, wherein displaying the creation view includes displaying a first section comprising the first close-ended data field and a second close-ended data field.

### Claim 15 (depends on 14)

The method according to claim 14, wherein displaying the creation view includes accepting the specialty requirement parameter of the case in the second close ended data field in the first section of the creation view.

### Claim 16 (depends on 14)

The method according to claim 14, wherein displaying the creation view includes displaying a second section comprising at least one data field that is configurable between an open-ended data field and a close-ended data field.

### Claim 17 (depends on 16)

The method according to claim 16, wherein displaying the creation view includes accepting the question parameter of the case in the at least one data field that is configurable between an open-ended data field and a close-ended data field.

### Claim 18 (depends on 12)

The method according to claim 12, wherein displaying the response view includes displaying a first section configured to display the question, the specialty requirement, and the at least one concept of the case to the user.

### Claim 19 (depends on 12)

The method according to claim 12, wherein displaying the search view includes continuously updating a list of cases in a second section of the search view responsive to text input into a first open-ended text parameter in a first section of the search view.

### Claim 20 (depends on 19)

The method according to claim 19, wherein displaying the search view includes displaying a third section configured to graphically display statistics of the list of cases in the second section of the search view.

### Claim 21 (depends on 20)

The method according to claim 20, wherein displaying the search view includes displaying a fourth section configured to graphically display the frequency of concepts in the list of cases.

### Claim 22 (depends on 20)

The method according to claim 20, wherein displaying the list of cases in the second section of the search view includes ranking the cases responsive to user input on a button in the second section of the search view.

### Claim 23 (depends on 12)

The method according to claim 12, wherein displaying the creation view includes transitioning to displaying the search view responsive to user input.