Systems and methods for real-time patient record transcription and medical form population via mobile devices
Systems and methods for real-time patient record transcriptions and medical form population via mobile devices are described. A user (e.g., a medical professional) may speak into or near a mobile device operable to detect or record spoken language, and furthermore the mobile device may initiate real-time transcription of the spoken language to generate unstructured transcription text data corresponding to the spoken language. The unstructured transcription text data may be parsed for words or phrases indicative of medical information for generating structured data, where the structured data includes terms, phrases, and values identified via delineators and/or natural language processing techniques. Discrete data from the structured data may be directly inserted into corresponding locations (e.g., appropriate medical form text fields) in electronic medical records via APIs and service bus relays.
1. A system for processing spoken language data into an electronic health record (“EHR”) system, wherein the EHR system is associated with a healthcare provider and operatively connected to a mobile computing device, the EHR system further comprising electronic healthcare records associated with a particular patient, and wherein the electronic healthcare records are formatted according to a particular standard, the system comprising:
a mobile computing device associated with the healthcare provider, wherein the mobile computing device detects spoken language and initiates generation of transcription data corresponding to the spoken language, wherein the transcription data includes unstructured text data;
an application programming interface (“API”) system, wherein the API system comprises one or more API instances operable to:
receive the transcription data over a network connection;
parse the transcription data with one or more delineators for generating structured text data, wherein the one or more delineators comprise preconfigured healthcare terms;
identify discrete data within the structured text data, the discrete data comprising classifiable medical data; and
insert the classifiable medical data into a particular memory location at the EHR system according to the particular standard, wherein the particular memory location corresponds to a form field in the electronic health records associated with the classifiable medical data; and
an API traffic manager for assigning tasks to the one or more API instances based on a volume of requests received from the mobile computing device.
2. The system of claim 1 , wherein initiating generation of the transcription data comprises transmitting the detected spoken language to a real-time transcription service for transcribing the detected spoken language into the transcription data.
3. The system of claim 1 , further comprising a remote EHR system not associated with the healthcare provider, wherein particular API instances of the API system access particular memory locations within the remote EHR system.
4. The system of claim 1 , wherein prior to inserting the classifiable medical data into a particular memory location at the EHR system, the one or more API instances are further operable to normalize the discrete data into the particular standard.
5. The system of claim 1 , wherein the mobile computing device associated with the healthcare provider is authenticated via an authentication directory at the API system.
6. The system of claim 5 , wherein the mobile computing device associated with the healthcare provider is authenticated via a token included in the transcription data.
7. The system of claim 5 , wherein the mobile computing device associated with the healthcare provider is authenticated via multi-factor authentication.
8. The system of claim 1 , wherein electronic communications with the API system are transmitted via port 443 .
9. The system of claim 1 , wherein the network connection is a TLS encrypted HTTPS network connection.
10. The system of claim 1 , wherein the one or more delineators are determined via natural language processing algorithms trained to identify the particular standard.
11. A cloud-supported system for directly inserting electronic medical data into one or more disparate electronic health record (“EHR”) systems, the cloud-supported system comprising:
an application programming interface (“API”) traffic manager operable to receive requests, over a network connection, from a healthcare provider computing system for electronic health record data corresponding to a particular patient, wherein the API traffic manager is configured to forward the requests to API processing instances based on a volume of the requests received from the healthcare provider computing system, and wherein healthcare providers at the healthcare provider computing system are authenticated via an authentication directory operatively connected to the API traffic manager; and
an API service module comprising the API processing instances and operatively connected to the API traffic manager, wherein the API service module determines an EHR location at an external EHR system including the requested electronic health record data and initiates access to the requested electronic health record data via a service bus relay, wherein the service bus relay is operable to:
retrieve the requested electronic health record data from the external EHR system;
initiate normalization of the retrieved electronic health record data according to a standard format; and
directly insert the retrieved electronic health record data, in the normalized standard format, into an EHR system at the healthcare provider computing system.
12. The system of claim 11 , wherein the healthcare providers at the healthcare provider computing system are authenticated via a token included in the requests for the electronic health record data.
13. The system of claim 11 , wherein the healthcare providers at the healthcare provider computing system are authenticated via multi-factor authentication.
14. The system of claim 11 , wherein electronic communications with the API service module are transmitted via port 443 .
15. The system of claim 11 , wherein the network connection is a TLS encrypted HTTPS network connection.