Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal

Abstract

Embodiments are directed to providing remote healthcare services including remote diagnostics, and facilitating third-party healthcare payments. In one embodiment, a computer system receives an input including authentication credentials from a healthcare entity, and also requests assistance from another healthcare entity. The computer system authenticates the first healthcare entity using the authentication credentials, receives an input including authentication credentials from the other healthcare entity, and authenticates the other healthcare entity using these authentication credentials. The computer system further receives real-time information related to a health condition of a patient, where the real-time health condition information is provided to the second healthcare entity. The computer system also receives, from the other healthcare entity, diagnostic information related to the patient's health condition, and provides the received diagnostic information to the first healthcare entity, the patient and/or a payment entity.

1 . A computer program product for implementing a method for securely messaging a healthcare entity, the computer program product comprising one or more non-transitory computer-readable storage media having stored thereon computerize-executable instructions that, when executed by one or more processors of a computing system, cause the computing system to perform the method, the method comprising:
 providing to a user a menu of one or more user-selectable options, the user-selectable options comprising at least one compliance parameter;   receiving an input from the user indicating that the message is to be securely transmitted to a specified healthcare entity, wherein the message is part of a conversation between the user and the specified healthcare entity;   prior to transmission of the message:
 at least in part in response to the at least one compliance parameter, adding at least one compliance indicator to the message; 
 accessing a user defined-communication policy; 
 receiving an indication of a transmission location from which the message will be transmitted; 
 determining that the transmission location is referenced within the user defined-communication policy; and 
 based upon the reference to the transmission location within the user defined-communication policy, determining that the message is to be encrypted; 
   upon determining that the message is to be encrypted, the one or more processors encrypting the message using at least one encryption algorithm, such that the message is encrypted during the transfer from the user to the specified healthcare entity;   initiating transmission of the encrypted message such that the encrypted message is sent to the specified healthcare entity; and   processing at least one of the at least one compliance indicators.   
     
     
         2 . The computer program product of  claim 1 , wherein the at least one compliance parameter specifies that the message must automatically perish after being received and read by the specified healthcare entity. 
     
     
         3 . The computer program product of  claim 2 , wherein the encrypted message perishes automatically after a specified period of time. 
     
     
         4 . The computer program product of  claim 1 , wherein the indication of the transmission location is generated by a global positioning system. 
     
     
         5 . The computer program product of  claim 1 , wherein the non-transitory computer-readable storage media is configured to avoid storing message-related data. 
     
     
         6 . The computer program product of  claim 1 , wherein intervening transmission entities between the user and the specified healthcare entity are prevented from accessing the encrypted messages. 
     
     
         7 . The computer program product of  claim 1 , wherein the user selects the specified healthcare entity with whom the user wishes to converse by selecting a picture associated with the specified healthcare entity. 
     
     
         8 . The computer program product of  claim 1 , wherein a messenger application is instantiated, the messenger application being configured to authenticate the user prior to facilitating message transmission. 
     
     
         9 . The computer program product of  claim 8 , wherein the user and the specified healthcare entity are authenticated to instances of the messenger application, such that the messages are transmitted and received as push messages between the messenger application instances. 
     
     
         10 . The computer program product of  claim 8 , wherein the messenger application provides one or more portions of structural data that allow the specified healthcare entity to perform one or more specified functions. 
     
     
         11 . A computer system comprising the following:
 one or more processors;   system memory;   one or more non-transitory computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, cause the computing system to:
 access a user defined-communication policy, 
 receive an indication of a transmission location from which the message will be transmitted; 
 determine that the transmission location is referenced within the user defined-communication policy; 
 based upon the reference to the transmission location within the user defined-communication policy, determine that the message is to be encrypted; 
 receive, at a receiving module, the encrypted message that includes message content intended for a specified healthcare entity; 
 receive, at the receiving module, an input defining at least one compliance parameter, wherein the input is generated as a result of user selection of one or more user-selectable options; 
 determine, with the one or more processors, that the encrypted message was received as part of an established session between the secure messaging service and a user-side instance of a messenger application; 
 transmit, with a transmission module, the encrypted message to the specified healthcare entity, the encrypted message being accessible by the specified healthcare entity via an instance of the messenger application; and 
 process at least one of the at least one compliance parameters. 
   
     
     
         12 . The computer system of  claim 11 , wherein the user-selectable options include an option to have the message perish automatically after being received and read by the healthcare entity such that the message is readable by the healthcare entity but is not stored. 
     
     
         13 . The computer system of  claim 11 , wherein the at least one compliance parameter specifies that the message automatically perishes after being received and read by the specified healthcare entity. 
     
     
         14 . The computer program product of  claim 13 , wherein the encrypted message perishes automatically after a specified period of time. 
     
     
         15 . The computer system of  claim 11 , wherein the secure messaging service is configured to store received encrypted messages in a data store. 
     
     
         16 . The computer system of  claim 15 , wherein the stored messages are auditable and retrievable for at least a specified amount of time. 
     
     
         17 . The computer system of  claim 11 , wherein the indication of the transmission location is generated by a global positioning system. 
     
     
         18 . The computer system of  claim 11 , wherein the secure messaging service allows users to attach files to messages. 
     
     
         19 . The computer system of  claim 11 , wherein the secure messaging service facilitates secure messaging between at least a first specified healthcare entity and a second specified healthcare entity. 
     
     
         20 . A method, implemented at a computer system including at least a processor, a transmitter or receiver and a memory, for securely messaging a healthcare entity, the method comprising:
 accessing a user defined-communication policy,   receiving an indication of a transmission location from which the message will be transmitted;   determining that the transmission location is referenced within the user defined-communication policy;   based upon the reference to the transmission location within the user defined-communication policy, determining that the message is to be encrypted;   receiving at a receiving module, the encrypted message that includes message content intended for a specified healthcare entity;   receiving, at the receiving module, an input indicating that the encrypted message is to perish automatically upon being read by the specified healthcare entity, wherein the input is generated as a result of user selection of one or more user-selectable options, including an option to have the message perish automatically after being received and read by the healthcare entity such that the message is readable by the healthcare entity but is not stored;   determining that the encrypted message was received as part of an established session between the secure messaging service and a user-side instance of a messenger application; and   transmitting the encrypted message to the specified healthcare entity, the encrypted message being accessible by the specified healthcare entity via an instance of the messenger application.