Automated electronic medical record (EMR) analysis via point of care computing systems
A central computing entity receives an encrypted request for performance of a back-end function, the encrypted request associated with a provider and a corresponding practice management system; generates a trigger indication that comprises patient identifying information based on the encrypted request; processes the trigger indication using a program code module corresponding to the back-end function and operating on the central computing entity to generate a response; converts the response into a notification in a format corresponding to the practice management system; and encrypts and provides the notification such that a user computing entity receives the notification. The user computing entity may be configured to provide at least a part of the notification or a graphical representation thereof via a user interface of the user computing entity.
1. A computer-implemented method comprising:
receiving, by a computing entity configured to execute a first back-end process and a second back-end process for either of a first practice management computing system or a second practice management computing system, a request for initiating execution of the first back-end process for the first practice management computing system, wherein each of the first back-end process and the second back-end process is configured to provide a respective graphical user interface (GUI) notification, wherein (a) the request is generated by the first practice management computing system based at least in part on user input received from a user accessing a displayed interactive user interface of the first practice management computing system, (b) the displayed interactive user interface comprises one or more display elements, (c) the request comprises (1) data that identifies the first back-end process, and (2) data that identifies the displayed interactive user interface of the first practice management computing system, and (d) the request is encrypted;
generating, by the computing entity and based at least in part on the request, a trigger indication for selecting the first back-end process and not the second back-end process for execution, wherein the trigger indication comprises data that identifies a patient, the first practice management computing system, and the first back-end process to initiate execution of the first back-end process;
initiating, by the computing entity, execution of the first back-end process based at least in part on the trigger indication by to generate a response;
converting, by the computing entity, the response into the respective GUI notification, wherein (a) the respective GUI notification is aesthetically matched to the displayed interactive user interface of the first practice management computing system for insertion into at least one display element of the one or more display elements of the displayed interactive user interface, and (b) the respective GUI notification is based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system; and
encrypting and providing, by the computing entity, the respective GUI notification to the first practice management computing system, to cause the first practice management computing system to update the displayed interactive user interface to include the respective GUI notification in at least one display element of the one or more display elements of the displayed interactive user interface.
2. The computer-implemented method of claim 1 , further comprising accessing, by the computing entity, secondary input data for initiating the first back-end process, wherein the secondary input data is used to initiate one or more application program interface (API) calls based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system.
3. The computer-implemented method of claim 1 , wherein the trigger indication is generated responsive to user interaction as determined by a listener.
4. The computer-implemented method of claim 1 , wherein the first back-end process is executed based at least in part on eligibility data associated with the patient, and the computer-implemented method further comprises performing, by the computing entity, an eligibility check based at least in part on the data that identifies the patient.
5. The computer-implemented method of claim 1 , further comprising authenticating, by the computing entity, the user prior to encrypting the respective GUI notification.
6. The computer-implemented method of claim 5 , wherein the respective GUI notification is encrypted based at least in part on the authentication of the user.
7. The computer-implemented method of claim 1 , wherein execution of the first back-end process comprises requesting and documenting, by the computing entity, prior authorization for one or more services.
8. The computer-implemented method of claim 1 , wherein the request for initiating execution of the first back-end process is a care gap request; and wherein initiating execution of the first back-end process comprises:
extracting the data that identifies the patient from the trigger indication;
initiating a plurality of application program interface (API) calls to an electronic medical record (EMR) database storing medical history data of the patient to retrieve the medical history data of the patient;
identifying one or more care standards relevant to the patient based at least in part on the medical history data of the patient, wherein each corresponding care standard of the one or more care standards relevant to the patient identifies one or more care event codes for satisfying the corresponding care standard, and the one or more care standards are identified from a plurality of care standards stored in a memory media;
identifying one or more gaps in care for the patient based at least in part on the medical history data and the one or more care event codes identified for each of the one or more care standards, wherein the one or more gaps in care are identified as care event codes that are required by the one or more care standards and are missing from the medical history data;
wherein the response is a care gap response reflecting the one or more gaps in care that were identified.
9. The computer-implemented method of claim 8 , wherein initiating the plurality of API calls to the EMR database comprises:
identifying the EMR database storing the medical history data of the patient; and
identifying the plurality of API calls to retrieve the medical history data of the patient from the EMR database.
10. The computer-implemented method of claim 8 , wherein:
the one or more care standards relevant to the patient are identified based at least in part on demographic data for the patient;
at least a portion of the demographic data is identified within the trigger indication; and
each particular care standard of the plurality of care standards are stored in the memory media together with data identifying relevant demographic data for the particular care standard.
11. A computing entity comprising at least one processor, a communications interface, and memory including computer program code, the memory and computer program code configured to, with the at least one processor, cause the computing entity to:
receive a request for initiating execution of a first back-end process for a first practice management computing system, wherein the first back-end process and a second back-end process are each configured to provide a respective graphical user interface (GUI) notification for either of the first practice management computing system or a second practice management computing system, wherein (a) the request is generated by the first practice management computing system based at least in part on user input received from a user accessing a displayed interactive user interface of the first practice management computing system, (b) the displayed interactive user interface comprises one or more display elements, (c) the request comprises (1) data that identifies the first back-end process, and (2) data that identifies the displayed interactive user interface of the first practice management computing system, (d) the request is encrypted, and (e) the computing entity is in communication with the first practice management computing system and the second practice management computing system;
generate, based at least in part on the request, a trigger indication for selecting the first back-end process and not the second back-end process for execution, wherein the trigger indication comprises data that identifies a patient, the first practice management computing system, and the first back-end process to initiate execution of the first back-end process;
initiate execution of the first back-end process based at least in part on the trigger indication to generate a response;
convert the response into the respective GUI notification, wherein (a) the respective GUI notification is aesthetically matched to the displayed interactive user interface of the first practice management computing system for insertion into at least one display element of the one or more display elements of the displayed interactive user interface, and (b) the respective GUI notification is based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system; and
encrypt and provide the respective GUI notification to the first practice management computing system, to cause the first practice management computing system to update the displayed interactive user interface to include the respective GUI notification in at least one display element of the one or more display elements of the displayed interactive user interface.
12. The computing entity of claim 11 , wherein the memory and computer program code are further configured to, with the at least one processor, cause the computing entity to access secondary input data for initiating the first back-end process by issuing one or more application program interface (API) calls based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system.
13. The computing entity of claim 11 , wherein the trigger indication is generated responsive to user interaction as determined by a listener.
14. The computing entity of claim 11 , wherein the first back-end process is executed based at least in part on eligibility data associated with the patient, and the memory and computer program code are further configured to, with the at least one processor, cause the computing entity to perform an eligibility check based at least in part on the data that identifies the patient.
15. The computing entity of claim 11 , wherein the memory and computer program code are further configured to, with the at least one processor, cause the computing entity to authenticate the user prior to encrypting the respective GUI notification.
16. The computing entity of claim 15 , wherein the respective GUI notification is encrypted based at least in part on the authentication of the user.
17. The computing entity of claim 11 , wherein the execution of first back-end process comprises requesting and documenting prior authorization for one or more services.
18. The computing entity of claim 11 , wherein the request for initiating execution of the first back-end process is a care gap request; and wherein the computer-executable program code instructions initiate execution of the first back-end process by:
extracting the data that identifies the patient from the trigger indication;
initiating a plurality of application program interface (API) calls to an electronic medical record (EMR) database storing medical history data of the patient to retrieve the medical history data of the patient;
identifying one or more care standards relevant to the patient based at least in part on the medical history data of the patient, wherein each corresponding care standard of the one or more care standards relevant to the patient identifies one or more care event codes for satisfying the corresponding care standard, and the one or more care standards are identified from a plurality of care standards stored in a memory media;
identifying one or more gaps in care for the patient based at least in part on the medical history data and the one or more care event codes identified for each of the one or more care standards, wherein the one or more gaps in care are identified as care event codes that are required by the one or more care standards and are missing from the medical history data;
wherein the response is a care gap response reflecting the one or more gaps in care that were identified.
19. The computing entity of claim 18 , wherein initiating the plurality of API calls to the EMR database comprises:
identifying the EMR database storing the medical history data of the patient; and
identifying the plurality of API calls to retrieve the medical history data of the patient from the EMR database.
20. The computing entity of claim 18 , wherein:
the one or more care standards relevant to the patient are identified based at least in part on demographic data for the patient;
at least a portion of the demographic data is identified within the trigger indication; and
each particular care standard of the plurality of care standards are stored in the memory media together with data identifying relevant demographic data for the particular care standard.
21. A computer program product comprising a non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions, when executed by at least one processor of a computing entity, are configured to cause the computing entity to:
receive a request for initiating execution of a first back-end process for a first practice management computing system, wherein the first back-end process and a second back-end process are each configured to provide a respective graphical user interface (GUI) notification for either of the first practice management computing system or a second practice management computing system, wherein (a) the request is generated by the first practice management computing system based at least in part on user input received from a user accessing a displayed interactive user interface of the first practice management computing system, (b) the displayed interactive user interface comprises one or more display elements, (c) the request comprises (1) data that identifies the first back-end process, and (2) data that identifies the displayed interactive user interface of the first practice management computing system, (d) the request is encrypted, and (e) the computing entity is in communication with the first practice management computing system and the second practice management computing system;
generate, based at least in part on the request, a trigger indication for selecting the first back-end process and not the second back-end process for execution, wherein the trigger indication comprises data that identifies a patient, the first practice management computing system, and the first back-end process to initiate execution of the first back-end process;
initiate execution of the first back-end process based at least in part on the trigger indication to generate a response;
convert the response into the respective GUI notification, wherein (a) the respective GUI notification is aesthetically matched to the displayed of the first practice management computing system; (b) the GUI notification is configured for insertion into at least one display element of the one or more display elements of the displayed interactive user interface, and (b) the respective GUI notification is based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system; and
encrypt and provide the respective GUI notification to the first practice management computing system, to cause the first practice management computing system to update the displayed interactive user interface to include the respective GUI notification in at least one display element of the one or more display elements of the displayed interactive user interface.
22. The computer program product of claim 21 , wherein the computer-executable program code instructions, when executed by the at least one processor of the computing entity, are further configured to cause the computing entity to access secondary input data for initiating the first back-end process by issuing one or more application program interface (API) calls based at least in part on the data that identifies the displayed interactive user interface of the first practice management computing system.
23. The computer program product of claim 21 , wherein the trigger indication is generated responsive to user interaction as determined by a listener.
24. The computer program product of claim 21 , wherein the first back-end process is executed based at least in part on eligibility data associated with the patient, wherein the computer-executable program code instructions, when executed by the at least one processor of the computing entity, are further configured to cause the computing entity to perform an eligibility check based at least in part on the data that identifies the patient.
25. The computer program product of claim 21 , wherein the respective GUI notification is encrypted based at least in part on an authentication of the user.
26. The computer program product of claim 21 , wherein execution of the first back-end process comprises requesting and documenting prior authorization for one or more services.
27. The computer program product of claim 21 , wherein the request for initiating execution of the first back-end process is a care gap request; and wherein the computer-executable program code instructions initiate execution of the first back-end process by:
extracting the data that identifies the patient from the trigger indication;
initiating a plurality of application program interface (API) calls to an electronic medical record (EMR) database storing medical history data of the patient to retrieve the medical history data of the patient;
identifying one or more care standards relevant to the patient based at least in part on the medical history data of the patient, wherein each corresponding care standard of the one or more care standards relevant to the patient identifies one or more care event codes for satisfying the corresponding care standard, and the one or more care standards are identified from a plurality of care standards stored in a memory media;
identifying one or more gaps in care for the patient based at least in part on the medical history data and the one or more care event codes identified for each of the one or more care standards, wherein the one or more gaps in care are identified as care event codes that are required by the one or more care standards and are missing from the medical history data;
wherein the response is a care gap response reflecting the one or more gaps in care that were identified.
28. The computer program product of claim 27 , wherein initiating the plurality of API calls to the EMR database comprises:
identifying the EMR database storing the medical history data of the patient; and
identifying the plurality of API calls to retrieve the medical history data of the patient from the EMR database.
29. The computer program product of claim 27 , wherein:
the one or more care standards relevant to the patient are identified based at least in part on demographic data for the patient;
at least a portion of the demographic data is identified within the trigger indication; and
each particular care standard of the plurality of care standards are stored in the memory media together with data identifying relevant demographic data for the particular care standard.