# US 2014/0156303 A1 · Processing of clinical data for validation of selected clinical procedures

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

- Number: US 2014/0156303 A1
- Document ID: US20140156303A1
- Status: Published application
- Kind: A1
- Application number: 13/705,011
- Filed: 2012-12-04
- Published: 2014-06-05
- Earliest claimed: 2012-12-04
- Inventors: Gary Pacheco; John Delong; Paul Van Arragon; Jeremy Hossfeld; Tiffany Quinlan
- Web page: https://patentgrep.com/patent/US20140156303A1

## CPC

- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 30/20: for handling medical images, e.g. DICOM, HL7 or PACS
- G16H 40/67: for remote operation
- G16H 50/20: for computer-aided diagnosis, e.g. based on medical expert systems
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A processing system determines a validation status of an examination request for a patient. The examination request includes examination data that defines a clinical condition of the patient. A receipt module receives the examination request via a communication network; a storage module adapted for storing a plurality of predefined clinical definitions, predefined clinical definitions associated with at least one examination type. A matching module conducts a first stage analysis of the content, compares the content with the predefined clinical definitions in order to determine one or more matching definitions. A validation module compares the matching definitions against the match threshold of at least one examination type to determine a validation indicator of the examination request. A response module transmits the validation status of the exam request as an exam response via the communications network.

## Claims

### Claim 1

A method for integrating decision support into user systems, the method comprising:
receiving examination information associated with an examination request in a user system, wherein the user system comprises at least one system from the group of electronic medical record (“EMR”) system, radiology information system (“RIS”) or a hospital information system (“HIS”);
generating a first applications program interface (“API”) call, from the user system to a decision support system, that comprises the examination information;
generating, at the decision support system, a return to the first API call a procedure list for display on the user system;
receiving input from the user, at the user system, to select a procedure from the procedure list;
generating a second API call, from the user system to the decision support system, to obtain a list of the indications for the selected procedure;
generating, at the decision support system, a return to the second API call that comprises an indication list that identifies indications appropriate for the selected procedure based on the examination data;
sending updated data associated with the exam request and a unique session from the user system to the decision support system, through a third API;
generating a fourth API call, from the user system to the decision support system, to obtain advise; and
generating, at the decision support system, a return to the fourth API call a procedure to return any applicable advice.

### Claim 2 (depends on 1)

The method of claim 1, further comprising returning from the decision support system, in response to the fourth API call, a question for prompting an answer for use in updating the examination data associated with the unique session to result in updated content of the examination request.

### Claim 3 (depends on 1)

The method of claim 1, wherein the examination request comprises a preliminary request that includes parameters selected from the group comprising: Procedure Coding Scheme; Procedure/Exam ID; Session ID; Patient Date of Birth; Patient Gender; and Physician Specialty, and in response a return communication to the second API call comprises the predefined clinical indications including suggested display logic as a list of indications with user interface display attributes for use in describing the clinical condition in detail.

### Claim 4 (depends on 1)

The method of claim 1, wherein the examination request comprises a final request in the third API call for the submission of the exam data, the final request includes parameters selected from the group comprising: Session ID; Procedure/Exam Coding Scheme; Procedure/Exam ID; Patient Class; Patient Date of Birth; Patient Gender; Physician Specialty; Body Part; Selected Indications; Answers to Questions asked by Advice; and Procedure/Exam Description.

### Claim 5 (depends on 4)

The method of claim 4, further comprising transmitting an answer to the question as an API return based on analysis of parameters associated with the unique session selected from the group comprising: Session ID; Procedure/Exam Coding Scheme; Procedure/Exam ID; Patient Class; Patient Date of Birth; Patient Gender; Physician Specialty; Body Part; Selected Indications; Answers to Questions asked by Advice; and Procedure/Exam Description, and the answer content is selected from the group comprising: Advice Text; Session Status; Requested Procedure/Exam; Recommended Procedure; Actions; Supporting Information about the advice; and further Questions.

### Claim 6 (depends on 1)

The method of claim 1, further comprising storing an outcome of the unique session, wherein stored parameters of the outcome are selected from the group comprising: Session ID; Action Taken; Procedure/Exam Coding Scheme; Final Procedure/Exam ID; Physician ID; Physician Name; and Patient ID.
