Automated adverse drug event alerts

• US 9,412,369 B2
• Filed: 06/17/2011
• Issued: 08/09/2016
• Est. Priority Date: 06/17/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Wang, Tao, Zhou, Bin
• Primary Examiner(s): YEN, ERIC L
• Application Number:
  US13/162,585
• Publication Number:
  US 20120323576A1
• Time in Patent Office: 1,880 Days
• Field of Search: 704/236, 704/270.1
• US Class Current: 1/1
• CPC Class Codes: G08B 3/10 using electric transmission; using electromagnetic transmission
• CPC Class Codes: G10L 15/26 Speech to text systems G10L15/08 takes precedence
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients

Abstract

Event audio data that is based on verbal utterances associated with a pharmaceutical event associated with a patient may be received. Medical history information associated with the patient may be obtained, based on information included in a medical history repository. At least one text string that matches at least one interpretation of the event audio data may be obtained, based on information included in a pharmaceutical speech repository, information included in a speech accent repository, and a drug matching function, the at least one text string being associated with a pharmaceutical drug. One or more adverse drug event (ADE) alerts may be determined based on matching the at least one text string and medical history attributes associated with the at least one patient with ADE attributes obtained from an ADE repository. An ADE alert report may be generated, based on the determined one or more ADE alerts.

Claims

1. A system comprising:

at least one device processor; and

a machine readable storage device storing a pharmaceutical alert speech engine that executes on one or more of the at least one device processor, the pharmaceutical alert speech engine including;

a medical history interface engine that accesses a medical history repository, the medical history repository storing medical history information, the medical history information being associated with a plurality of patients;

an audio data receiving engine that receives event audio data, the event audio data being based on verbal utterances, the verbal utterances being associated with a pharmaceutical event, the pharmaceutical event being associated with at least one of the patients;

a recognition engine that obtains at least one text string, wherein the at least one text string matches at least one interpretation of the received event audio data, wherein the obtaining the at least one text string includes transforming physical audio data into electrical data via an input device, the obtaining the at least one text string is based on information obtained from a pharmaceutical speech repository, the obtaining the at least one text string is based on information obtained from a speech accent repository, and the obtaining the at least one text string is based on a drug matching function, wherein the at least one text string is associated with a pharmaceutical drug, wherein the drug matching function includes an alternative drug matching function that determines the at least one text string, wherein the determining the at least one text string includes determining a name that is associated with an alternative drug, wherein the alternative drug is associated with the pharmaceutical drug;

a record retrieval engine that obtains medical history information, the obtained medical history information being associated with the at least one of the patients;

an adverse drug event (ADE) scanning engine that determines, via at least one of the at least one device processor, one or more adverse drug event alerts, the determining the one or more ADE alerts being based on results of a matching operation that compares a first set of information with ADE attributes, the determining the one or more ADE alerts including receiving the ADE attributes from an ADE repository, wherein the first set of information includes the at least one text string and includes medical history attributes which are associated with the at least one of the patients, the ADE repository being hosted on another system that is configured separately from a hosting system that hosts the medical history repository; and

an audio data output interface engine that initiates a transmission of an audio alert to an audio output device, wherein the audio alert is associated with the one or more ADE alerts.

2. The system of claim 1, further comprising:

a pharmaceutical speech corpus interface engine that accesses the pharmaceutical speech repository, wherein the pharmaceutical speech repository includes information which is associated with a corpus of pharmaceutical terms;

a speech accent interface engine that accesses the speech accent repository, wherein the pharmaceutical speech repository includes information which is associated with database objects, wherein the database objects indicate speech accent attributes, the speech accent attributes being associated with one or more speakers; and

an adverse drug event (ADE) interface engine that accesses the ADE repository, wherein the ADE repository includes attributes which are associated with adverse drug events, wherein

the recognition engine obtains the at least one text string, wherein the at least one text string matches the at least one interpretation of the received event audio data, wherein the matching the at least one interpretation is based on information obtained from the pharmaceutical speech corpus interface engine, wherein the matching the at least one interpretation is based on information received from the speech accent interface engine, and wherein the matching the at least one interpretation is based on the drug matching function,

the record retrieval engine obtains the medical history information, the obtained medical history information being associated with the at least one of the patients, wherein the obtained medical history information is obtained via the medical history interface engine, and

the adverse drug event (ADE) scanning engine determines the one or more adverse drug event alerts, wherein the determining the one or more adverse drug event alerts is based on the results of the matching operation that compares the first set of information with the ADE attributes, wherein the ADE attributes are obtained via the ADE interface engine.

3. The system of claim 1 wherein the at least one text string includes one or more of:

a name attribute associated with the pharmaceutical drug,

a strength attribute associated with the pharmaceutical drug, or

a dosage attribute associated with the pharmaceutical drug.

4. The system of claim 1, wherein the pharmaceutical event includes one or more of:

a medical prescription receiving event associated with the at least one of the patients, or

a medical prescription review event associated with the at least one of the patients.

5. The system of claim 1, wherein the drug matching function includes:

a user history matching function configured to determine the at least one text string, wherein the determining the at least one text string is based on a history of selected text strings, wherein the history of selected text strings is associated with a user.

6. The system of claim 1, wherein the obtained medical history information that is associated with the at least one of the patients includes one or more of:

a consumption history associated with the at least one of the patients,

an allergy history associated with the at least one of the patients,

an allergy history associated with at least one family member that is biologically related to the at least one of the patients,

a medical condition associated with the at least one of the patients, or

a medical condition associated with at least one family member that is biologically related to the at least one of the patients.

7. The system of claim 1, wherein:

the medical history repository includes a plurality of electronic medical records associated with the plurality of patients.

8. The system of claim 1, further comprising:

an ADE alert interface engine that accesses an ADE alert repository, wherein the ADE alert repository is configured to store information which is associated with a plurality of ADE alerts, the ADE alerts including one or more of;

a plurality of recorded audio alerts each associated with a predetermined ADE alert,

a plurality of textual alerts, each textual alert associated with a predetermined ADE alert, or

a plurality of alert text strings, each alert text string associated with a predetermined attribute associated with a predetermined adverse condition.

9. The system of claim 8, further comprising:

an ADE alert report engine that generates an ADE alert report, wherein the generating the ADE alert report is based on obtaining one or more strings of text alert information, wherein the one or more strings of text alert information is obtained via the ADE alert interface engine and wherein the generating the ADE alert report is based on populating one or more fields which are associated with an ADE alert report form.

10. The system of claim 8, wherein:

the audio data output interface engine is configured to initiate the transmission of the audio alert based on obtaining one or more strings of text alert information, wherein the one or more strings of text alert information is obtained via the ADE alert interface engine, and wherein the initiating the transmission of the audio alert is based on initiating a text-to-speech transmission to the audio output device, wherein the text-to-speech transmission is based on a text-to-speech transmission of the text alert information, wherein the text-to-speech transmission is accomplished via the audio alert.

11. A computer program product comprising a hardware machine readable storage device, storing executable code that, when executed, causes at least one data processing apparatus to:

receive event audio data that is based on verbal utterances, the verbal utterances being associated with a pharmaceutical event, the pharmaceutical event being associated with a patient;

obtain medical history information associated with the patient, based on information included in a medical history repository;

obtain at least one text string that matches at least one interpretation of the event audio data, the obtaining the at least one text string including transforming physical audio data into electrical data via an input device, the obtaining the at least one text string being based on information included in a pharmaceutical speech repository, the obtaining the at least one text string being based on information included in a speech accent repository, and the obtaining the at least one text string being based on a drug matching function, the at least one text string being associated with a pharmaceutical drug, wherein the drug matching function includes an alternative drug matching function that determines the at least one text string, wherein the determining the at least one text string includes determining a name that is associated with an alternative drug, wherein the alternative drug is associated with the pharmaceutical drug;

determine, via at least one device processor, one or more adverse drug event (ADE) alerts, the determining the ADE alerts being based on results of a matching operation that compares a first set of information with ADE attributes, the determining the one or more ADE alerts including receiving the ADE attributes from an ADE repository, wherein the first set of information includes the at least one text string and includes the obtained medical history information, the ADE repository being hosted on another system that is configured separately from a hosting system that hosts the medical history repository; and

generate an ADE alert report, based on the determined one or more ADE alerts.

12. The computer program product of claim 11, wherein the executable code, when executed, causes the at least one data processing apparatus to:

initiate a transmission of an audio alert associated with the one or more ADE alerts to an audio output device.

13. The computer program product of claim 11, wherein the executable code, when executed, causes the at least one data processing apparatus to:

obtain an identification of a user, wherein the user is associated with the verbal utterances.

14. The computer program product of claim 13, wherein the obtaining of the identification of the user is based on one or more of:

receiving an indication of the identification from the user, or

obtaining the identification based on matching a portion of the event audio data with a portion of the information included in the speech accent repository, wherein the matching of the portion of the event audio data is based on voice recognition.

15. The computer program product of claim 11, wherein:

the pharmaceutical event includes one or more of a medical prescription receiving event associated with the patient, or a medical prescription review event associated with the patient; and

the verbal utterances are associated with pharmaceutical personnel designated as pharmaceutical personnel who are responsible for pharmaceutical requests which are associated with the patient.

16. The computer program product of claim 11, wherein the executable code, when executed, causes the at least one data processing apparatus to:

receive training audio data that is based on verbal training utterances, wherein the verbal training utterances are associated with a user of the ADE alert report; and

initiate an update event associated with the speech accent repository, wherein the update event is based on the received training audio data.

17. A method comprising:

accessing a medical history repository, the medical history repository storing medical history information, the medical history information being associated with a plurality of patients;

receiving event audio data, the event audio data being based on verbal utterances, the verbal utterances being associated with a pharmaceutical event, the pharmaceutical event being associated with at least one of the patients;

obtaining at least one text string, wherein the at least one text string matches at least one interpretation of the received event audio data, wherein the obtaining the at least one text string includes transforming physical audio data into electrical data via an input device, the obtaining the at least one text string is based on information obtained from a pharmaceutical speech repository, the obtaining the at least one text string is based on information obtained from a speech accent repository, and the obtaining the at least one text string is based on a drug matching function, wherein the at least one text string is associated with a pharmaceutical drug, wherein the drug matching function includes an alternative drug matching function that determines the at least one text string, wherein the determining the at least one text string includes determining a name that is associated with an alternative drug, wherein the alternative drug is associated with the pharmaceutical drug;

obtaining medical history information, the obtained medical history information being associated with the at least one of the patients;

determining, via at least one device processor, one or more adverse drug event (ADE) alerts, the determining the one or more ADE alerts being based on results of a matching operation that compares a first set of information with ADE attributes, the determining the one or more ADE alerts including receiving the ADE attributes from an ADE repository, wherein the first set of information includes the at least one text string and includes medical history attributes which are associated with the at least one of the patients, the ADE repository being hosted on another system that is configured separately from a hosting system that hosts the medical history repository; and

initiating a transmission of an audio alert to an audio output device, wherein the audio alert is associated with the one or more ADE alerts.

18. The method of claim 17, wherein the at least one text string includes one or more of:

a name attribute associated with the pharmaceutical drug,

a strength attribute associated with the pharmaceutical drug, or

a dosage attribute associated with the pharmaceutical drug.

19. The method of claim 17, wherein the pharmaceutical event includes one or more of:

a medical prescription receiving event associated with the at least one of the patients, or

a medical prescription review event associated with the at least one of the patients.

20. The method of claim 17, wherein the drug matching function includes:

a user history matching function configured to determine the at least one text string, wherein the determining the at least one text string is based on a history of selected text strings, wherein the history of selected text strings is associated with a user.