De-duplication and contextually-intelligent recommendations based on natural language understanding of conversational sources

Abstract

Methods, systems, and computer-readable media are disclosed herein that provide a comprehensive view that reveals all or nearly all possible method dependencies that are present in client workflows. In aspects, when computer code for a particular method is going to be edited, other methods are identified that have upstream or downstream dependencies relative to the particular method. The methods that will be affected based on the computer code editing can be presented in a user-interactive graphical user interface that facilitates exploration of upstream and downstream dependencies.

What is claimed: 
     
       1. A computer-implemented method comprising:
 receiving an indication to perform a patient consent check; 
 determining electronically whether a patient consent status is satisfied based on electronic documentation in an electronic medical record of the patient; 
 when the patient consent status is not satisfied:
 blocking a voice transcription service, wherein blocking the voice transcription service includes preventing a clinician from activating the voice transcription service through voice commands and/or via a graphical user interface; 
 
 when the patient consent status is satisfied:
 activating the voice transcription service; 
 receiving, one or more voice inputs based on the activation of the voice transcription service; 
 populating a transcription with the one or more voice inputs in an unstructured format; 
 extracting at least one clinical condition from the one or more voice inputs; 
 identifying one or more clinical concepts related to the at least one clinical condition using one or more clinical ontologies for the at least one clinical condition, wherein each clinical ontology provides contextual relationships between the clinical condition and the one or more clinical concepts; 
 utilizing the one or more clinical concepts, populating the graphical user interface with the one or more clinical concepts into one or more classification groups, the one or more classification groups corresponding to standard classifications; 
 populating the graphical user interface with a proposed actions tab, wherein the proposed action tab includes one or more proposed actions, wherein the one or more proposed actions include one or more concepts sorted into corresponding classification groups, and wherein each of the one or more proposed actions includes one or more selectable options; 
 receiving a user selection of the one or more proposed actions through the selectable options; and 
 in response to the user selection of the one or more proposed actions, automatically placing one or more medical orders based on the one or more proposed actions. 
 
 
     
     
       2. The computer-implemented method of  claim 1 , wherein the indication is received based on an active user interaction with a system via a user or clinician interface. 
     
     
       3. The computer-implemented method of  claim 2 , wherein the user interaction includes a user selection of a button, icon, or other graphical object presented within the graphical user interface. 
     
     
       4. The computer-implemented method of  claim 1 , wherein the indication is received passively in response to a launch of a particular application. 
     
     
       5. The computer-implemented method of  claim 1 , further comprising:
 searching the electronic medical record of the patient through querying, scanning, or parsing to locate a specific field or a particular value, wherein the specific field or the particular value provides an indication of the patient consent whether being recorded or not during a prior or present visit. 
 
     
     
       6. The computer-implemented method of  claim 1 , wherein each clinical concept of the one or more clinical concepts is assigned ‘positive’ or ‘negative’ marker to indicate presence or absence of the clinical concept in the patient. 
     
     
       7. The computer-program product of  claim 1 , further comprising:
 in response to the user selection of the one or more proposed actions, triggering a corresponding clinical concept to be automatically electronically documented into a patient's electronic health record (EHR); 
 updating the graphical user interface to remove the corresponding clinical concept that is updated to the patient's EHR; and 
 automatically adding electronic documentation of the corresponding clinical concept and the one or more medical orders to the patient's EHR. 
 
     
     
       8. A system comprising:
 one or more data processors; and 
 a non-transitory computer readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform actions including: 
 receive an indication to perform a patient consent check; 
 determine electronically whether a patient consent status is satisfied based on electronic documentation in an electronic medical record of the patient; 
 when the patient consent status is not satisfied:
 block a voice transcription service, wherein blocking the voice transcription service includes preventing a clinician from activating the voice transcription service through voice commands and/or via a graphical user interface; 
 
 when the patient consent status is satisfied:
 activate the voice transcription service; 
 receive, one or more voice inputs based on the activation of the voice transcription service; 
 populate a transcription with the one or more voice inputs in an unstructured format; 
 extract at least one clinical condition from the one or more voice inputs; 
 identify one or more clinical concepts related to the at least one clinical condition using one or more clinical ontologies for the at least one clinical condition, wherein each clinical ontology provides contextual relationships between the clinical condition and the one or more clinical concepts; 
 utilize the one or more clinical concepts, populating the graphical user interface with the one or more clinical concepts into one or more classification groups, the one or more classification groups corresponding to standard classifications; 
 populate the graphical user interface with a proposed actions tab, wherein the proposed action tab includes one or more proposed actions, wherein the one or more proposed actions include one or more concepts sorted into corresponding classification groups, and wherein each of the one or more proposed actions includes one or more selectable options; 
 receive a user selection of the one or more proposed actions through the selectable options; and 
 in response to the user selection of the one or more proposed actions, automatically place one or more medical orders based on the one or more proposed actions. 
 
 
     
     
       9. The system of  claim 8 , wherein the indication is received based on an active user interaction with the system via a user or clinician interface. 
     
     
       10. The system of  claim 9 , wherein the user interaction includes a user selection of a button, icon, or other graphical object presented within the graphical user interface. 
     
     
       11. The system of  claim 8 , wherein the indication is received passively in response to a launch of a particular application. 
     
     
       12. The system of  claim 8 , further comprising:
 searching the electronic medical record of the patient through querying, scanning, or parsing to locate a specific field or a particular value, wherein the specific field or the particular value provides an indication of the patient consent whether being recorded or not during a prior or present visit. 
 
     
     
       13. The system of  claim 8 , wherein each clinical concept of the one or more clinical concepts is assigned ‘positive’ or ‘negative’ marker to indicate presence or absence of the clinical concept in the patient. 
     
     
       14. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause one or more data processors to perform actions including:
 receiving an indication to perform a patient consent check; 
 determining electronically whether a patient consent status is satisfied based on electronic documentation in an electronic medical record of the patient; 
 when the patient consent status is not satisfied:
 blocking a voice transcription service, wherein blocking the voice transcription service includes preventing a clinician from activating the voice transcription service through voice commands and/or via a graphical user interface; 
 
 when the patient consent status is satisfied:
 activating the voice transcription service; 
 receiving, one or more voice inputs based on the activation of the voice transcription service; 
 populating a transcription with the one or more voice inputs in an unstructured format; 
 extracting at least one clinical condition from the one or more voice inputs; 
 identifying one or more clinical concepts related to the at least one clinical condition using one or more clinical ontologies for the at least one clinical condition, wherein each clinical ontology provides contextual relationships between the clinical condition and the one or more clinical concepts; 
 utilizing the one or more clinical concepts, populating the graphical user interface with the one or more clinical concepts into one or more classification groups, the one or more classification groups corresponding to standard classifications; 
 populating the graphical user interface with a proposed actions tab, wherein the proposed action tab includes one or more proposed actions, the one or more proposed actions include one or more concepts sorted into corresponding classification groups, and each of the one or more proposed actions include selectable options; 
 receiving a user selection of the one or more proposed actions through the selectable options; and 
 in response to the user selection of the one or more proposed actions, automatically placing one or more medical orders based on the one or more proposed actions. 
 
 
     
     
       15. The computer-program product of  claim 14 , wherein the indication is received based on an active user interaction with a system via a user or clinician interface. 
     
     
       16. The computer-program product of  claim 14 , wherein the indication is received passively in response to a launch of a particular application. 
     
     
       17. The computer-program product of  claim 14 , further comprising:
 searching the electronic medical record of the patient through querying, scanning, or parsing to locate a specific field or a particular value, wherein the specific field or the particular value provides an indication of the patient consent whether being recorded or not during a prior or present visit. 
 
     
     
       18. The computer-program product of  claim 14 , wherein each clinical concept of the one or more clinical concepts is assigned ‘positive’ or ‘negative’ marker to indicate presence or absence of the clinical concept in the patient.