User and engine code handling in medical coding system
First Claim
Patent Images
1. A method comprising:
- (a) outputting for presentation to one or more human users, via a user interface implemented using at least one processor, a set of one or more medical billing codes derived from first documentation for a clinical patient encounter by a natural language understanding (NLU) engine, the NLU engine being an automated language processing component implemented by the at least one processor;
(b) receiving user input, that was input via the user interface, to approve at least one of the one or more medical billing codes derived by the NLU engine, and/or to manually input one or more codes, resulting in a set of one or more user-approved medical billing codes for the clinical patient encounter;
(c) after the act (b), applying the NLU engine, implemented by the at least one processor, to a free-form text that relates to the clinical patient encounter and is not part of the first documentation documenting the clinical patient encounter, to derive a first engine-derived medical billing code for the clinical patient encounter and a first link between the first engine-derived medical billing code and a corresponding first portion of the free-form text and a second engine-derived medical billing code for the clinical patient encounter and a second link between the second engine-derived medical billing code and a corresponding second portion of the free-form text;
(d) automatically determining whether the first engine-derived medical billing code and the second engine-derived medical billing code overlap with at least one user-approved medical billing code of the set of user-approved medical billing codes;
(e) in response to automatically determining that the first engine-derived medical billing code overlaps with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the at least one user-approved medical billing code instead of the first engine-derived medical billing code;
(f) in response to automatically determining that the second engine-derived medical billing code does not overlap with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the second engine-derived medical billing code;
(g) generating a finalized sequence of medical billing codes for the clinical patient encounter, the finalized sequence of medical billing codes including the retained at least one user-approved medical billing code and the second engine-derived medical billing code; and
(h) training the NLU engine based on training data including the finalized sequence of medical billing codes for the clinical patient encounter, the training comprising providing the training data as input to one or more models associated with the automated language processing component.
2 Assignments
0 Petitions
Accused Products
Abstract
Techniques for medical coding include applying a natural language understanding (NLU) engine to a free-form text documenting a clinical patient encounter, to derive a first set of one or more medical billing codes for the clinical patient encounter and a link between each code in the first set and a corresponding portion of the free-form text. The first set of codes may be compared to a second set of one or more medical billing codes approved by one or more human users for the patient encounter, to identify at least one code in the first set that overlaps with at least one code in the second set. The code in the second set approved by the one or more human users may be retained instead of the overlapping code in the first set derived by the NLU engine.
72 Citations
20 Claims
-
1. A method comprising:
-
(a) outputting for presentation to one or more human users, via a user interface implemented using at least one processor, a set of one or more medical billing codes derived from first documentation for a clinical patient encounter by a natural language understanding (NLU) engine, the NLU engine being an automated language processing component implemented by the at least one processor; (b) receiving user input, that was input via the user interface, to approve at least one of the one or more medical billing codes derived by the NLU engine, and/or to manually input one or more codes, resulting in a set of one or more user-approved medical billing codes for the clinical patient encounter; (c) after the act (b), applying the NLU engine, implemented by the at least one processor, to a free-form text that relates to the clinical patient encounter and is not part of the first documentation documenting the clinical patient encounter, to derive a first engine-derived medical billing code for the clinical patient encounter and a first link between the first engine-derived medical billing code and a corresponding first portion of the free-form text and a second engine-derived medical billing code for the clinical patient encounter and a second link between the second engine-derived medical billing code and a corresponding second portion of the free-form text; (d) automatically determining whether the first engine-derived medical billing code and the second engine-derived medical billing code overlap with at least one user-approved medical billing code of the set of user-approved medical billing codes; (e) in response to automatically determining that the first engine-derived medical billing code overlaps with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the at least one user-approved medical billing code instead of the first engine-derived medical billing code; (f) in response to automatically determining that the second engine-derived medical billing code does not overlap with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the second engine-derived medical billing code; (g) generating a finalized sequence of medical billing codes for the clinical patient encounter, the finalized sequence of medical billing codes including the retained at least one user-approved medical billing code and the second engine-derived medical billing code; and (h) training the NLU engine based on training data including the finalized sequence of medical billing codes for the clinical patient encounter, the training comprising providing the training data as input to one or more models associated with the automated language processing component. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. At least one computer-readable storage medium storing computer-executable instructions that, when executed, perform a method comprising:
-
(a) outputting for presentation to one or more human users, via a user interface, a set of one or more medical billing codes derived from first documentation for a clinical patient encounter by a natural language understanding (NLU) engine, the NLU engine being an automated language processing component implemented by at least one processor; (b) receiving user input, that was input via the user interface, to approve at least one of the one or more medical billing codes derived by the NLU engine, and/or to manually input one or more codes, resulting in a set of one or more user-approved medical billing codes for the patient encounter; (c) after the act (b), applying the NLU engine to a free-form text that relates to the clinical patient encounter and is not part of the first documentation documenting the clinical patient encounter, to derive a first engine-derived medical billing code for the clinical patient encounter and a first link between the first engine-derived medical billing code and a corresponding first portion of the free-form text and a second engine-derived medical billing code for the clinical patient encounter and a second link between the second engine-derived medical billing code and a corresponding second portion of the free-form text; (d) automatically determining whether the first engine-derived medical billing code and the second engine-derived medical billing code overlap with at least one user-approved medical billing code of the set of user-approved medical billing codes; (e) in response to automatically determining that the first engine-derived medical billing code overlaps with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the at least one user-approved medical billing code instead of the first engine-derived medical billing code; (f) in response to automatically determining that the second engine-derived medical billing code does not overlap with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the second engine-derived medical billing code; (g) generating a finalized sequence of medical billing codes for the clinical patient encounter, the finalized sequence of medical billing codes including the retained at least one user-approved medical billing code and the second engine-derived medical billing code; and (h) training the NLU engine based on training data including the finalized sequence of medical billing codes for the clinical patient encounter, the training comprising providing the training data as input to one or more models associated with the automated language processing component. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. Apparatus comprising:
-
at least one processor; and at least one storage medium storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising; (a) outputting for presentation to one or more human users, via a user interface, a set of one or more medical billing codes derived from first documentation for a clinical patient encounter by a natural language understanding (NLU) engine, the NLU engine being an automated language processing component; (b) receiving user input, that was input via the user interface, to approve at least one of the one or more medical billing codes derived by the NLU engine, and/or to manually input one or more codes, resulting in a set of one or more user-approved medical billing codes for the patient encounter; (c) after the act (b), applying the NLU engine to a free-form text that relates to the clinical patient encounter and is not part of the first documentation documenting the clinical patient encounter, to derive a first engine-derived medical billing code for the clinical patient encounter and a first link between the engine-derived medical billing code and a corresponding first portion of the free-form text and a second engine-derived medical billing code for the clinical patient encounter and a second link between the second engine-derived medical billing code and a corresponding second portion of the free-form text; (d) automatically determining whether the first engine-derived medical billing code and the second engine-derived medical billing code overlap with at least one user-approved medical billing code of the set of user-approved medical billing codes; (e) in response to automatically determining that the first engine-derived medical billing code overlaps with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the at least one user-approved medical billing code instead of the first engine-derived medical billing code; (f) in response to automatically determining that the second engine-derived medical billing code does not overlap with the at least one user-approved medical billing code of the set of user-approved medical billing codes, retaining the second engine-derived medical billing code; (g) generating a finalized sequence of medical billing codes for the clinical patient encounter, the finalized sequence of medical billing codes including the retained at least one user-approved medical billing code and the second engine-derived medical billing code; and (h) training the NLU engine based on training data including the finalized sequence of medical billing codes for the clinical patient encounter, the training comprising providing the training data as input to one or more models associated with the automated language processing component. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification
-
- Resources
Litigation Campaign Assessment
Thank you for your request. You will receive a custom alert email when the Litigation Campaign Assessment is available.
×
-
Current AssigneeMicrosoft Technology Licensing LLC (Microsoft Corporation)
-
Original AssigneeNuance Communications, Inc. (Microsoft Corporation)
-
InventorsReiser, Gregory, D'Souza, Howard, Subramanian, Aparna, Spitznagel, Regina
-
Primary Examiner(s)Nguyen, Hiep V
-
Assistant Examiner(s)Nguyen, Trang T
-
Application NumberUS14/296,303Publication NumberTime in Patent Office1,833 DaysField of Search705 2, 705 3US Class CurrentCPC Class CodesG06F 40/10 Text processing natural lan...G06Q 10/00 Administration; ManagementG06Q 10/10 Office automation; Time man...G06Q 30/04 Billing or invoicingG06Q 40/08 InsuranceG16H 10/60 for patient-specific data, ...G16H 40/20 for the management or admin...G16H 50/70 for mining of medical data,...
