WO2015175721A1 - Diagnostic à distance d'états et fourniture de prescriptions au moyen d'un portail de fournisseur de soins de santé multi-accès - Google Patents

Diagnostic à distance d'états et fourniture de prescriptions au moyen d'un portail de fournisseur de soins de santé multi-accès Download PDF

Info

Publication number
WO2015175721A1
WO2015175721A1 PCT/US2015/030664 US2015030664W WO2015175721A1 WO 2015175721 A1 WO2015175721 A1 WO 2015175721A1 US 2015030664 W US2015030664 W US 2015030664W WO 2015175721 A1 WO2015175721 A1 WO 2015175721A1
Authority
WO
WIPO (PCT)
Prior art keywords
healthcare
entity
healthcare entity
patient
user
Prior art date
Application number
PCT/US2015/030664
Other languages
English (en)
Inventor
Michael A. Liberty
Mike Love
Original Assignee
Liberty Michael A
Mike Love
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/278,980 external-priority patent/US11354623B2/en
Application filed by Liberty Michael A, Mike Love filed Critical Liberty Michael A
Priority to MX2016014969A priority Critical patent/MX2016014969A/es
Priority to SG11201610509SA priority patent/SG11201610509SA/en
Publication of WO2015175721A1 publication Critical patent/WO2015175721A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • Mobile phones and other digital devices have become increasingly popular in recent years. These devices are used on a daily basis for a variety of different tasks. For instance, mobile devices allow users to check email, send and receive instant messages, check calendar items, take notes, set up reminders, browse the internet, play games or perform any number of different actions using specialized applications or "apps". These applications allow mobile devices to communicate with other computer systems and perform a wide variety of network-connected tasks previously not possible with a mobile device.
  • Embodiments described herein are directed to targeting specific items to health care users based on determined health concerns.
  • a computer system determines that a user is subscribed to a health care service, where the health care service is configured to facilitate secure communication between the user and other health care entities.
  • the computer system accesses health care information associated with the user.
  • the health care information is stored as part of the health care service.
  • the computer system determines, from the accessed health care information, various health care concerns associated with the user and, based on this determination, provides the user targeted items according to the determined health care concern.
  • the health care service is designed to be compliant with communication requirements outlined in the Health Insurance Portability and Accountability Act (HIPAA).
  • HIPAA Health Insurance Portability and Accountability Act
  • the user and the various health care entities may be able to communicate with each other in a HIPAA-compliant manner using their own (mobile) computing devices.
  • a computer system receives an input from a user indicating that a message including text or other characters is to be securely transmitted to a specified healthcare entity.
  • the message is part of a conversation between a user and the specified healthcare entity.
  • the computer system encrypts the characters of the message using at least one encryption algorithm, so that the message is encrypted during the transfer from the user to the specified healthcare entity.
  • the computer system then initiates transmission of the encrypted message such that the encrypted message is sent to the specified healthcare entity.
  • the encrypted message is transferred in accordance with legal regulations governing healthcare communications.
  • a computer system provides a secure messaging service that receives an encrypted message that includes message content intended for a specified healthcare entity.
  • the encrypted message is part of a conversation between a user and the specified healthcare entity.
  • the computer system determines 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 transmits the encrypted message to the specified healthcare entity, where the encrypted message is accessible by the specified healthcare entity via an instance of the messenger application.
  • a computer system receives an input from a first healthcare entity (such as a nurse) where the input includes authentication credentials, and also requests assistance from another healthcare entity (such as a doctor). The computer system authenticates the first healthcare entity using these authentication credentials. The computer system then receives an input from the other healthcare entity, where the input includes authentication credentials identifying the other healthcare entity as one authorized to perform specified healthcare functions. The computer system 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, portions of diagnostic information related to the patient's health condition, and provides the received diagnostic information to at least one of the following: the first healthcare entity, the patient and a payment entity.
  • a computer system facilitates a third-party healthcare payment by receiving an input from a healthcare entity identifying at least one healthcare item that is to be paid for by a third party, where the healthcare entity is authenticated to a third-party healthcare payment service.
  • the computer system then sends an indication of the identified healthcare item to the third party for payment.
  • the computer system receives authorization from the third party to pay for the identified healthcare item and initiates a transaction conducted by the third-party healthcare payment service, where the transaction allows the third party to pay for the identified healthcare item.
  • the computer system further notifies the third party that the transaction is complete and that the identified healthcare item has been paid for.
  • Figure 1 illustrates a computer architecture in which embodiments described herein may operate including targeting specific items to health care users based on determined health concerns.
  • Figure 2 illustrates an architecture in which patient and provider views of health information are shown.
  • Figure 3 illustrates a business architecture of a managed health care service.
  • Figure 4 illustrates a context diagram that includes providers, service- oriented architectures and purpose-based engines.
  • Figure 5 illustrates various stages of change within a set of purpose-based engines.
  • Figure 6 illustrates a reference architecture for one embodiment of an enterprise portal platform.
  • Figure 7 illustrates a flowchart of an example method for targeting specific items to health care users based on determined health concerns.
  • Figure 8 illustrates a computer architecture in which embodiments may operate including targeting specific items to health care users based on determined health concerns.
  • Figure 9 illustrates a computer architecture in which embodiments may operate including securely messaging a healthcare entity.
  • Figure 10 illustrates a flowchart of an example method for securely messaging a healthcare entity.
  • Figure 11 illustrates a flowchart of an example method for providing a secure messaging service.
  • Figure 12 illustrates a computing environment in which users and healthcare entities may send and receive secure messages to and from each other.
  • Figure 13 illustrates a computing environment in which a user requests a prescription from a doctor and receives notification that the prescription has been filled by a pharmacy.
  • Figure 14 illustrates a computing environment in which a doctor requests and receives an X-ray using the secure messaging service.
  • Figure 15 illustrates an embodiment of a messenger application that provides various message-related options.
  • Figure 16 illustrates a computing environment in which remote healthcare services are provided.
  • Figure 17 illustrates an example flowchart of a method for providing remote healthcare services.
  • Figure 18 illustrates an example flowchart of a method for facilitating a third-party healthcare payment.
  • Figure 19 illustrates a computing environment in which third-party healthcare payments are processed.
  • Figure 20 illustrates a computing environment in which remote diagnostic services are provided.
  • Embodiments described herein are directed to targeting specific items to health care users based on determined health concerns.
  • a computer system determines that a user is subscribed to a health care service, where the health care service is configured to facilitate secure communication between the user and other health care entities.
  • the computer system accesses health care information associated with the user.
  • the health care information is stored as part of the health care service.
  • the computer system determines, from the accessed health care information, various health care concerns associated with the user and, based on this determination, provides the user targeted items according to the determined health care concern.
  • the health care service is designed to be compliant with communication requirements outlined in the Health Insurance Portability and Accountability Act (HIPAA).
  • HIPAA Health Insurance Portability and Accountability Act
  • the user and the various health care entities may be able to communicate with each other in a HIPAA-compliant manner using their own (mobile) computing devices.
  • a multi-access (HIPAA-compliant) health care provider portal may be provided which allows multiple different authenticated providers to access patients' medical records.
  • the portal allows specified portions of the medical records to be transmitted to certain care givers based on a policy defined by the user.
  • the portal further facilitates communication between care givers, including communication of a patient's prescription compliance data.
  • a computer system receives an input from a user indicating that a message including text or other characters is to be securely transmitted to a specified healthcare entity.
  • the message is part of a conversation between a user and the specified healthcare entity.
  • the computer system encrypts the characters of the message using at least one encryption algorithm, so that the message is encrypted during the transfer from the user to the specified healthcare entity.
  • the computer system then initiates transmission of the encrypted message such that the encrypted message is sent to the specified healthcare entity.
  • the encrypted message is transferred in accordance with legal regulations governing healthcare communications.
  • a computer system provides a secure messaging service that receives an encrypted message that includes message content intended for a specified healthcare entity.
  • the encrypted message is part of a conversation between a user and the specified healthcare entity.
  • the computer system determines 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 transmits the encrypted message to the specified healthcare entity, where the encrypted message is accessible by the specified healthcare entity via an instance of the messenger application.
  • a computer system receives an input from a first healthcare entity (such as a nurse) where the input includes authentication credentials, and also requests assistance from another healthcare entity (such as a doctor). The computer system authenticates the first healthcare entity using these authentication credentials. The computer system then receives an input from the other healthcare entity, where the input includes authentication credentials identifying the other healthcare entity as one authorized to perform specified healthcare functions. The computer system 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, portions of diagnostic information related to the patient's health condition, and provides the received diagnostic information to at least one of the following: the first healthcare entity, the patient and a payment entity.
  • a computer system facilitates a third-party healthcare payment by receiving an input from a healthcare entity identifying at least one healthcare item that is to be paid for by a third party, where the healthcare entity is authenticated to a third-party healthcare payment service.
  • the computer system then sends an indication of the identified healthcare item to the third party for payment.
  • the computer system receives authorization from the third party to pay for the identified healthcare item and initiates a transaction conducted by the third-party healthcare payment service, where the transaction allows the third party to pay for the identified healthcare item.
  • the computer system further notifies the third party that the transaction is complete and that the identified healthcare item has been paid for.
  • Embodiments described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below.
  • Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
  • Computer-readable media that store computer-executable instructions in the form of data are computer storage media.
  • Computer-readable media that carry computer-executable instructions are transmission media.
  • embodiments described herein can comprise at least two distinctly different kinds of computer- readable media: computer storage media and transmission media.
  • Computer storage media includes RAM, ROM, EEPROM, CD-ROM, solid state drives (SSDs) that are based on RAM, Flash memory, phase-change memory (PCM), or other types of memory, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions, data or data structures and which can be accessed by a general purpose or special purpose computer.
  • SSDs solid state drives
  • PCM phase-change memory
  • a "network” is defined as one or more data links and/or data switches that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices.
  • a network either hardwired, wireless, or a combination of hardwired or wireless
  • Transmission media can include a network which can be used to carry data or desired program code means in the form of computer-executable instructions or in the form of data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
  • program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa).
  • computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a network interface card or "NIC"), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system.
  • a network interface module e.g., a network interface card or "NIC”
  • NIC network interface card
  • Computer-executable (or computer-interpretable) instructions comprise, for example, instructions which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
  • the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
  • cloud computing is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services).
  • configurable computing resources e.g., networks, servers, storage, applications, and services.
  • the definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.
  • cloud computing is currently employed in the marketplace so as to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources.
  • the shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.
  • a cloud computing model can be composed of various characteristics such as on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth.
  • a cloud computing model may also come in the form of various service models such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”).
  • SaaS Software as a Service
  • PaaS Platform as a Service
  • IaaS Infrastructure as a Service
  • the cloud computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth.
  • a "cloud computing environment” is an environment in which cloud computing is employed.
  • the functionally described herein can be performed, at least in part, by one or more hardware logic components.
  • illustrative types of hardware logic components include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and other types of programmable hardware.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Program-specific Integrated Circuits
  • ASSPs Program-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • system architectures described herein can include a plurality of independent components that each contribute to the functionality of the system as a whole.
  • This modularity allows for increased flexibility when approaching issues of platform scalability and, to this end, provides a variety of advantages.
  • System complexity and growth can be managed more easily through the use of smaller-scale parts with limited functional scope.
  • Platform fault tolerance is enhanced through the use of these loosely coupled modules.
  • Individual components can be grown incrementally as business needs dictate. Modular development also translates to decreased time to market for new functionality. New functionality can be added or subtracted without impacting the core system.
  • FIG. 1 illustrates an example system architecture for a mobile wallet platform.
  • Integration tier 101 is configured to manage mobile wallet sessions and maintain integrity of financial transactions.
  • Integration tier 101 can also include a communication (e.g., Web services) API and/or other communication mechanisms to accept messages from channels 111.
  • Other mechanisms include, but are not limited to: International Standards Organization ("ISO") 8583 for Point of Sale (“POS”) and Automated Teller Machines (“ATM”) devices and Advanced Message Queuing Protocol (“AMQP”) for queue based interfaces.
  • ISO International Standards Organization
  • POS Point of Sale
  • ATM Automated Teller Machines
  • AMQP Advanced Message Queuing Protocol
  • Each of channels 111 can be integrated to one or more mechanisms for sending messages to integration tier 101.
  • Notification services 102 is configured to send various notifications through different notification channels 112, such as, for example, Short Message Peer-to-Peer (“SSMP") for Short Messaging Service (“SMS”) and Simple Mail Transfer Protocol (“SMTP”) for emails.
  • Notification services 102 can be configured through a web services API.
  • Service connectors 103 are a set of connectors configure to connect to 3rd party systems 113. Each connector can be a separate module intended to integrate an external service to the system architecture.
  • Business process services 104 are configured to implement business workflows, including executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects.
  • Payment handler 105 is configured to wrap APIs of different payment processors, such as, for example, banking accounts, credit/debit cards or processor 121. Payment handler 105 exposes a common API to facilitate interactions with many different kinds of payment processors.
  • Security services 106 are configured to perform subscriber authentication.
  • Authorization services 107 are configured to perform client authorization, such as, for example, using a database-based Access Control List (“ACL”) table.
  • ACL Access Control List
  • Database 108 is configured to manage customer accounts (e.g., storing customer accounts and properties), manage company accounts (e.g., storing company accounts and properties), manage transaction histories (e.g., storing financial transaction details), store customer profiles, storing dictionaries used by the mobile wallet platform, such as, for example, countries, currencies, etc., and managing money containers.
  • Rules engine 109 is configured to gather financial transaction statistics and uses the statistics to provide transaction properties, such as, for example, fees and bonuses.
  • Rules engine 109 is also configured to enforce business constraints, such as, for example, transactions and platform license constraints.
  • Name matching engine 110 is configured to match different objects according to specified configuration rules. Matching engine 110 can be use to find similarities between names, addresses, etc.
  • Transaction processor 121 is configured to manage financial accounts and transactions. The transaction processor 121 can be used to hold, load, withdraw and deposit funds to mobile wallet accounts. Transaction processor 121 can also be used as a common interface to a third party processor system. When used as a common interface, financial operations may be delegated to the external processor. A Clearing House subsystem of transaction processor 121 can be used to exchange the financial information with a bank.
  • Components of a mobile wallet platform can be connected to one another over (or be part of) a system bus and/or a network.
  • Networks can include a Local Area Network ("LAN”), a Wide Area Network (“WAN”), and even the Internet.
  • LAN Local Area Network
  • WAN Wide Area Network
  • Accorindlgy, components of the mobile wallet platform can be "in the cloud”.
  • mobile wallet platform components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the system bus and/or network.
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • HTTP Hypertext Transfer Protocol
  • SMTP Simple Mail Transfer Protocol
  • the components depicted in Figure 1 can interoperate to provide a number of financial and other services including but not limited to enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
  • a stored value account either hosted by a mobile wallet platform or a third party
  • adding a bank or credit union account to a mobile wallet
  • adding a debit or credit card account to a mobile wallet
  • depositing funds in a mobile wallet withdrawing funds from a mobile wallet
  • paying bills from a mobile wallet paying bills from a mobile wallet
  • Embodiments herein are directed to a transparent, seamless, multi-access portal that facilitates communication between parties (e.g. health care entities).
  • parties e.g. health care entities
  • those parties may include a patient or "user” and the user's health care providers.
  • the term "health care provider” may refer to any person or entity that provides health care services to the user.
  • people or entities may include, but are not limited to, any of the following: caregivers, doctors, hospitals, emergency medical technicians (EMTs), insurance companies, nongovernmental organizations (NGOs), health maintenance organizations (HMOs) and pharmaceutical companies.
  • the multi-access portal may be accessed by one or more of these health care providers, once the provider is properly authenticated.
  • the multi-access portal may implement a service-oriented architecture (SOA) that allows for service-oriented communications (SOCs).
  • SOA service-oriented architecture
  • SOCs allow for secure communication between parties and, indeed, allow patients' medical information to be shared in a secure manner.
  • Figure 2 illustrates a picture of an activated patient with a health care provider 205.
  • the patient may be asked by their doctor to monitor their condition in some fashion, including monitoring glucose, activity level, weight, medication compliance, or other items.
  • the user may use a mobile device such as a cellular phone, tablet, wearable device or other mobile computing system to report their monitoring/compliance data 201.
  • the user may use a traditional desktop, laptop or other computing device to enter their monitoring data.
  • the data may be entered into a software application such as a health care service.
  • the monitoring data may be stored on the user's device and/or sent to the provider.
  • the user's phone or other mobile device may be used to show their self-reported data.
  • This data may be shown in charts, graphs, text, pictures or a combination thereof.
  • the data may be shown over time, such that the user can view data for the current day, the day before, the week before, the month before, etc. As such, the user can view their self-reported data over time.
  • the user's compliance over time may be shown, for example, in the plot- line chart of the application 202 in Figure 2.
  • the health care provider may access the user's monitoring/compliance data upon providing proper authentication credentials.
  • the health care provider's view 204 may be specific to each provider, and may show some or all of the user's compliance data (in application view 203). For example, a doctor may have access to some or all of the user's self-reported data, while a receptionist or data entry clerk may have access to limited portions thereof.
  • Each health care provider's credentials indicate to the system who the provider is and what level of access they have to the user's self-reported data.
  • the health care provider may contact the user to remind them of goals, to provide motivation or to let them know they may be placing themselves in danger by not taking their medication.
  • the health care provider may also provide tips on how to properly comply with a given prescription or recommendation.
  • FIG. 3 illustrates an architecture in which a mobile health management platform 303 is shown.
  • the mobile health management platform may include and may interact with a managed health care (MHC) service 301.
  • MHC managed health care
  • the mobile health management platform 303 alone or in combination with MHC service 301, may facilitate communication between users and health care providers.
  • the mobile health management platform 303 may, at least in some embodiments, run on the user's mobile device, and may be used by the user to provide health- or compliance-related information 302.
  • This health- or compliance-related information 302 may include medication adherence information, chronic disease management information, post acute care information, patient monitoring information, mobility integration information and/or pharmacy information.
  • the managed health care service 301 may receive this information 302 from the mobile health management platform 303 and store it, process it and/or pass it on to one or more other health care entities.
  • the MHC service 301 may provide the health- or compliance-related information 302 to health care entities (such as doctors) upon authentication of the entity.
  • the mobile health management platform 303 may allow the health- or compliance-related information to be sent directly to any of the health-care entities 304, without sending it to the MHC service 301 (or in addition to sending it to MHC service 301).
  • the MHC service 301 and the mobile health management platform (303) may work in tandem to allow secure communication between parties, and may allow the user to share their medical information with certain specified health care or other authenticated entities.
  • a data receiving module may be part of the multiaccess health care provider portal.
  • the data receiving module may be configured to receive authentication requests from health care providers.
  • the health care providers may include caregivers, doctors, hospitals, EMTs, insurance companies, pharmaceutical companies, hospice providers or other persons or entities that provide health care in some manner (including products and services).
  • the authentication requests received from the health care providers may include a perishable, tokenized personal identification number (PIN) assigned to that health care provider.
  • PIN personal identification number assigned to that health care provider.
  • the PIN may be encrypted and tokenized, such that it is only valid for a specified amount of time, or is valid for only a single data transfer.
  • the PIN may be tokenized using a random sequence that is provided along with the PIN upon authentication. Alternatively, the tokenized PIN may be encrypted and tokenized using various other methods.
  • the health care provider's authentication request may also include an indication of medical records that are to be transferred to the health care provider. If the provider is a doctor, the medical records may be transferred in whole; if the provider is an insurance company or pharmaceutical company, the medical records may be transferred in part. Indeed, the user to whom the medical records belong may decide how much of their data is accessible by the multi-access portal, and how much of their data is transferrable to each health care provider. EMTs, for example, may need to know allergy information, current prescription information and a health history. Other providers may need to know more or less information. The amount of information shared with each health care provider may be outlined in a policy, and may be specified by the patient. Then, the health information may be sent out to the designated health care providers according to the established policy.
  • an authenticating module of the multi-access portal may be configured to authenticate the health care provider using the received tokenized PIN.
  • the authenticating module may use the tokenized, encrypted PIN to verify the identity of the health care provider.
  • the multi-access portal may retrieve the requested portions of the user's medical records from a data store.
  • the data store may be configured to store medical information for multiple different users in accordance with the security requirements mandated by HIPAA and other prevailing regulatory requirements such as Gramm-Leach/Bliley (GLBA).
  • the data store may be any type of local or distributed store, including a storage area network (SAN).
  • the information stored in the data store may include the user's medical records and a listing of the user's health care providers. This data may then be transmitted or otherwise transferred using a transmitting module of the multi-access portal to the authenticated health care provider.
  • the portion of medical information accessible by each health care provider may be variable, and may be specified in a policy associated with the user.
  • the policy (which may be defined by the patient) specifies which health care providers are allowed to access the patient's medical records and which portions of the patient's medical records are accessible by each health care provider.
  • the multi-access health care provider portal is compliant with the Health Insurance Portability and Accountability Act (HIPAA).
  • HIPAA-compliant multi-access health care provider portal facilitates transfer of the patient's medical records to properly authenticated health care providers.
  • the requested portions of the user's medical records are transferred to the provider.
  • specific portions of the user's medical records i.e. those specified in a policy are automatically transferred to specified health care providers upon the occurrence of one or more specified events.
  • a user may be notified by text, email, phone or other means of communication.
  • Portions of that user's medical records may be automatically sent to one or more of the caregivers. It will be understood that this is only one example of an event, and that substantially any number of different events may trigger a communication to a caregiver. That communication may include some portion of the user's medical records, and may include information that is specifically pertinent to that caregiver.
  • the caregivers instead of automatically transferring portions of the user's medical records to the caregivers upon the occurrence of an event, the caregivers are merely notified that an event has occurred, and that they are to log in to the multi-access portal to receive more information.
  • the HIPAA-compliant multi-access health care provider portal may be accountable care organization (ACO)-compliant.
  • ACOs typically provide services to hospitals, and are paid when they are in compliance with a set of accountability rules. As such, upon determining that an ACO has complied with the regulations, the ACO may be paid (by any of the health care providers) through the multi-access health care provider portal.
  • a HIPAA-compliant portal may include a medication adherence module, which may be configured to monitor the user's medication usage.
  • the medication adherence module may receive medication usage inputs from the user, and further communicate the user's medication usage to one or more of the health care providers (as specified by a policy).
  • the user may be incented to provide their medication usage information in a variety of ways. For instance, the user may receive a reward in their mobile wallet for providing their medication usage. This mobile wallet reward may be provided by an insurance or pharmaceutical company.
  • the reward may be coupon, buy-one-get-one-free offer, a monetary reward, a discount on a specific product, or other type of reward.
  • a user may enter their compliance data
  • a pharmaceutical company may access that portion of the user's medical records using their tokenized PIN, and provide the user with rewards based on their compliance.
  • the multi- access portal may be used to monitor aspects of a user's chronic disease, or home hospice care, or any of a variety of different medical conditions or procedures.
  • a HIPAA-compliant portal may include a breach notification module (as one of the "Other" nodes referenced in health care entities 304).
  • the breach notification module is operable to track and report unauthorized disclosure of medical records as required under the Health Information Technology for Economic and Clinical Health (HITECH) Act portion of the American Recovery and Reinvestment Act (ARRA).
  • HITECH Health Information Technology for Economic and Clinical Health Act
  • ARRA American Recovery and Reinvestment Act
  • FIG. 4 describes an architecture which shows various components of a health care engine 401.
  • the health care engine 401 may include the multi-access portal as a component part, or may itself comprise the multi-access portal.
  • the health care engine 401 may include modules for authentication, authorization, device- specific display, role-based (e.g. policy-based) access to the user's data, personalization and personalization profiling, logging and user events.
  • the health care engine 401 may thus facilitate the authentication of users (e.g. patients) and health care providers. Once authenticated, the MHC engine 401 can determine what the user is allowed to access.
  • different health care providers may have different roles regarding the user's health, and may thus need access to different portions of the user's health information.
  • the health information may be distributed to providers based on predefined policies, and may be personalized for each provider. Thus, doctors may have one view of the user's data, EMTs may have a different view, pharmacists may have another view and hospice caregivers may have still a different view.
  • the MHC engine 401 can ensure that each health care provider receives personalized data, in the format that they prefer.
  • the health care engine may further interact with other internal or external services. These services may allow interaction with pharmacy systems (including billing and retail systems), 3 rd party systems (including mobile wallet systems), analytics and reporting systems and other systems (as shown in greater detail with regard to the enterprise portal platform 601 in Figure 6).
  • the MHC engine 401 may be configured to provide certain portions of the user's health information to analytics and reporting services that aggregate information for a wide variety of users. This information may be anonymized so that it is not traceable back to individual users.
  • the user's (anonymized) information may also be sent to recommendation services or engines that take a set of facts (e.g. a medical history along with prescription information) and provide diagnostic recommendations to a health care provider.
  • other services provided by a service-oriented architecture may be used. These services may allow users to pay bills (e.g. using a mobile wallet application), purchase products, check lab results from outside labs, or perform other functions.
  • enterprise portal platform of Figure 6 other third- party platforms may be integrated such as web analytics, enterprise search, web content management and document management. It should be noted that these are merely examples, and that many other third party services or other services may be used.
  • the enterprise portal platform 601 of Figure 6 implements corporate services that provide business process management, enterprise service business systems. These services may, in turn, interact with other portal services, as generally described with reference to Figure 4.
  • the health engine 401 of Figure 4 may be used to provide recommendations to care givers.
  • a knowledge engine 503 may look at the user's medical records and determine that the user 501 regularly takes their heart medication two times per day.
  • the user's medical records may be stored in data store 502, and may be accessible to authorized users. If the user hasn't taken their medication, and hasn't responded for a certain period of time, the user's medical records may be transferred to certain care givers including relatives or hospice care givers 506. If the care givers, after reviewing the medical records, indicate that there may be a problem, an EMT may be dispatched to the user 501.
  • the recommender system 504 may generate a recommendation that is specific to user 501.
  • the recommender system 504 may send the recommendation to the notification engine 505 which distributes the recommendation to the appropriate health care entities 506.
  • the EMT in the example above may be provided with a recommendation specifically for that patient, based on their medical history, current medications, recent (or long-term) compliance data, etc.
  • the notifications engine 505 may send notices (including the generated recommendations) to the proper care givers, including doctors, pharmacies, hospitals and other care givers 506.
  • the notification engine may, accordingly, notify a heart doctor that the patient has not taken their heart medication, and that an EMT/ambulance will be bringing them to the hospital shortly.
  • FIG. 7 a flowchart is illustrated of a method 700 for targeting specific items to health care users based on determined health concerns. The method 700 will now be described with frequent reference to the components and data of environment 800 of Figure 8.
  • Method 700 includes determining that a user is subscribed to a health care service, where the health care service is configured to facilitate secure communication between the user and one or more other health care entities (710).
  • user 805 may provide input 806 to computer system 801 indicating that the user intends to subscribe to health care service 814.
  • the user's subscription information 818 may be transferred from computer system 801 to computer system 813.
  • computer system 801 is a mobile computer system while computer system 813 is a server computer system.
  • Each computer system includes a hardware processor 802A/802B, memory 803A/803B and a communications module 804A/804B, respectively.
  • the communications modules may be used to communicate with other computer systems over wired or wireless communication means (such as Ethernet network cards, WiFi radios, GPS radios, Bluetooth radios or similar).
  • the health care service 814 may be hosted by computer system 813, which itself may be a local or distributed (e.g. cloud) computing system.
  • the health care service 814 may receive the user's subscription information 818 and subscribe the user to the service. In this process, the user becomes a member of the health care service 814.
  • the health care service 814 is the same as (or is substantially the same as) the multi-access portal described above.
  • the health care service 814 can facilitate secure (and, at least in some cases, HIPAA- compliant) communication between user 805 and various health care entities 820.
  • the health care service 814 may also be run on computer system 801 (in addition to or as an alternative to running on computer system 813).
  • the health care service 814 may have a client aspect and a server aspect.
  • the computer system 801 may be a mobile computer system that runs a client-side application portion of the health care service 814.
  • the health care service 814 may comprise the multiaccess portal application mentioned above.
  • the multi-access portal application may be displayed in display 807 of computer system 801.
  • Method 700 next includes accessing one or more portions of health care information associated with the user, where the health care information is stored as part of the health care service (720).
  • the user 805 may submit subscription information 818 that includes health care information. This information may be submitted upon signing up for the health care service 814.
  • the health care information may include all or parts of a user's medical records including past or present conditions, past or present medications, past or present caregivers, and other health- related information.
  • This user health care information 815 may be submitted as part of the subscribing process, or may be submitted at some other time. In some cases, such as with prescription compliance information, the information 815 may be sent on a continual basis (e.g. daily or weekly).
  • the information may then be stored as part of the health care service 814, or may be stored elsewhere.
  • the computer system 813 may then access the user health care information 815 as needed in order to perform functions approved by the user 805.
  • Method 700 further includes determining, from the accessed health care information, one or more health care concerns associated with the user (730).
  • the determining module 816 may determine, for example, based on the health care information 815 that user 805 has one or more health concerns (e.g. the user is diabetic, or is supposed to be taking a blood thinner, or any of thousands of other health concerns). These health concerns may be simple or complex, and may be life- threatening or benign. Regardless, the determining module 816 may determine various health concerns associated with the user 805. These health concerns may be based on previous illnesses, surgeries, allergies, diseases, complications, emergency procedures, rehabilitation information, prescriptions, dietary restrictions or other information.
  • the determining module may then provide the user one or more targeted items based on the determined health care concern (740).
  • the targeted items may comprise goods or services, for example,
  • the targeted items 808 may be products 809, services 810, offers 811, tips 812 or other items such as coupons or discounts that the user may need as a result of their determined health care concerns 817 or conditions.
  • a drug manufacturer may be able to provide prescription discounts directly to a user that has been prescribed a drug that they produce.
  • a wheelchair manufacturer may be able to provide discounts or services (such as house pickup or a house sales call) to show their wheelchair products. Healthy food manufacturers may be able to provide food supplement samples or free products or buy-one-get-one-free offers, or tips on how to make healthy snacks to patients or other users that have been given dietary restrictions.
  • the targeted goods or services, etc. may be presented within the health care service (i.e. the multi-access portal application) 814.
  • the targeted items 808 may be displayed on display 807 for viewing by the user 805.
  • the user may browse through the various tips, offers, services and/or products offered by different manufactures, service providers, health care entities 820 or other providers.
  • a health care entity such as a doctor or pharmacist may provide targeted tips to the user based on at least one determined health care concern associated with that user.
  • the tip may be a reminder to take a pill, or a reminder of a goal to lose weight, or a link to an exercise routine or video, or may be a motivational quote, or any other information usable by the user.
  • the tip may, for example, educate the user about new information related to their health care concern 817. Or, the tip may a reminder to refill a prescription, and may explain the benefits of taking the prescribed medication.
  • Prescription information may be provided by the user 805 and may be stored as part of health care information 815.
  • the determining module 816 may determine which goods or services might be associated with of useful for users of a certain medication or combination of medications.
  • the determined targeted items 808 may then be sent to the user based on their prescription information.
  • the targeted items may include offers 811 for cheaper refills, offers to refill at different local pharmacies, offers to get other medications at cheaper prices upon fulfillment of a given prescription, etc.
  • the user's compliance with the prescription may be monitored.
  • the user may submit prescription compliance information 819 on a daily, weekly or other basis. Then, based on the user's compliance, the user may receive more or fewer rewards.
  • the user may receive a greater discount for the next prescription fulfillment. If the user complies for a given length of time, he or she may receive a reward upon successful completion of that time period.
  • the reward may be based on the prescription taken, or may be based on health concerns associated with that prescription. For example, cholesterol reducing drugs are often associated with heart disease. If heart disease is a determined health concern for a given patient, the targeted items 808 may each be related to alleviating symptoms of or causes of heart disease.
  • the reward may be provided to the user's mobile device via an application such as a mobile wallet application.
  • the mobile wallet application may allow the user to immediately use the reward to purchase a product or service or redeem an offer.
  • the manufacturer, service provider or other provider of targeted items 808 may then be notified that the user purchased the targeted goods or services, or redeemed the offer or viewed the tip. As such, the targeted items provider may be apprised as to the effectiveness of their offer, tip, good or service.
  • the user 805 and/or the health care entities 820 may be asked to authenticate to the health care service 814 before being granted access to or being able to alter the user's health care information 815.
  • the user 805 and the health care entities may be assigned unique identifiers. These unique identifiers may be tokenized, personal identification numbers (PINs). By verifying the unique identifiers, the health care service 814 may be able to ensure that only authorized users access the user's health care information 815.
  • PINs personal identification numbers
  • users may use the health care service 814 to communicate with each other in real-time and, at least in some cases, using their own mobile devices or other computer systems. These communications may occur in a HIPAA- compliant manner, which preserves the user's privacy.
  • all or a portion of the user's health care information 815 may be automatically transferred to one or more of the health care entities 820 upon the occurrence of a specified event. For instance, if a diabetic user has an abnormally low reading, certain caregivers, relatives, doctors or other entities may be notified via email, text message, voice message or other means. Many other scenarios are possible. The notifications may be sent to a preset list of people, depending on the event that occurred, and may send a predetermined amount of health care information 815 also based on which event occurred. In cases where a doctor is notified of an event, the doctor may perform a remote diagnostic based on the information available to them (i.e. the information provided in the event notification). The doctor may then provide this remote diagnostic to one or more other health care entities 820. In this manner, doctors and other caregivers may share pertinent information about a patient, which may help to save a patient's life.
  • Computer architecture 900 includes multiple computer systems including mobile device 901, computer system 911 and any computer systems run by the various healthcare entities 919.
  • mobile device 901 and computer system 911 each include a processor 902/912 and memory 903/913.
  • Each computing system also includes a communications module 904/914 that allows the computer system to communicate with other computer systems via wired or wireless communication means.
  • mobile device 901 will be a single, mobile computing device such as a mobile phone (smart phone or feature phone), laptop, tablet, wearable computing device or other mobile device.
  • This mobile device 901 may include multiple processors or types of memory, and may draw on shared (e.g.
  • Computer system 911 may be any type of local or distributed computer system, including a cloud computing system.
  • the computer system 911 may also be mobile in some embodiments, and may similarly have any number of physical processors, memory types or other hardware.
  • Each of the computing systems includes modules for performing a variety of different functions.
  • mobile device 901 includes encryption module 907.
  • the encryption module 907 includes various encryption algorithms 908 for encrypting messages.
  • user 905 may desire to have the messages they send encrypted. For example, if user 905 is using messenger application 91 OA to communicate with another user, the user 905 may indicate via a selectable option in the messenger application 91 OA that messages are to be encrypted. The user may choose whether to encrypt a single message or set of messages, all messages in a given conversation, or all messages all the time. Additionally or alternatively, messages may be encrypted according to a policy established by the user 905 or by another user such as an administrator.
  • the policy may indicate that messages between certain specified entities or persons are to be encrypted, or messages between certain types of entities or persons are to be encrypted or messages sent at a certain time of day or from certain locations (e.g. from a hospital, pharmacy or other healthcare entity's location).
  • the encryption module 907 may use any one or more encryption algorithms 908 to encrypt outgoing messages and decrypt incoming messages.
  • the encryption module 907 may be part of the messenger application 91 OA. In other cases, it may be a standalone module.
  • the messenger application 91 OA may be used to send encrypted messages (e.g. 915) from users (e.g. patients) to healthcare entities (e.g. 919) including doctors, emergency medical technicians (EMTs), pharmacists, hospice providers, nurses, doctor's offices, hospitals, pharmacies and other healthcare entities.
  • the messenger application e.g. 910B
  • the doctor may use his or her messenger application 910B to send an encrypted message to a selected pharmacy or pharmacist (e.g. one that is currently near the user that requested the medication).
  • a selected pharmacy or pharmacist e.g. one that is currently near the user that requested the medication.
  • the pharmacy or pharmacist may then use the messenger application 910B to notify the user 905 that their prescription has been filled and is ready for pickup.
  • this is only one among many different examples of entities securely messaging each other using a secure messaging service 917. Additional examples will be provided below, although it will be understood that these are merely a small number of examples among a plurality of possible use cases.
  • the computer system 911 also includes modules for facilitating secure messaging between parties, especially between patients and healthcare entities.
  • the secure messaging service 917 may be configured to facilitate secure communication that complies with applicable regulations governing health- and healthcare-related communications.
  • the secure messaging service 917 may be any type of function, application or service that allows users to authenticate, create a session, and transfer messages securely.
  • user 905 may provide input 906 logging in (or authenticating) via their messenger application 91 OA.
  • the user may authenticate to the messenger application 91 OA directly, or may use the messenger application as a conduit to authenticate to the secure messaging service 917.
  • logging in to the messenger application 91 OA may automatically authenticate the user 905 to the secure messaging service 917.
  • the secure messaging service establishes a session 918 between the user (or healthcare entity) and the service.
  • the session established between the user or entity and the secure messaging service 917 allows the user or entity to send secure, encrypted messages to other parties that are similarly authenticated.
  • the secure messaging service 917 may operate in the cloud, and may thus allow any user with an internet connection to send messages using the messenger.
  • the secure messaging service 917 thus avoids the traditional (and unsecure) short message service (SMS), allowing user to send text messages (or messages including pictures, videos, or other files) using messenger applications. At least in some embodiments, these messenger applications are configured to send push messages to each other. The user's text and other data may be transferred in these push messages.
  • the push messages may be encrypted and otherwise processed by the secure messaging service 917.
  • Other processing may include ensuring that the messages are backed up and stored so that they are retrievable and auditable per healthcare communications regulations 909 (e.g. HIPAA).
  • HIPAA healthcare communications regulations
  • the message may not be stored and, conversely, may perish automatically upon being delivered, or upon termination of the conversation.
  • Various regulations may prompt changes or updates in the secure messaging service 917. These can easily be added and promulgated in real time.
  • FIG. 10 illustrates a flowchart of a method 1000 for securely messaging a healthcare entity.
  • the method 1000 will now be described with frequent reference to the components and data of environment 900.
  • Method 1000 includes receiving an input from a user indicating that a message including one or more characters is to be securely transmitted to a specified healthcare entity, the message being part of a conversation between a user and the specified healthcare entity (1010).
  • the communications module 904 of the mobile device 901 may receive input 906 from user 905 indicating that a message including text or other characters is to be transmitted to a doctor, pharmacist, hospital or other healthcare entity 919.
  • This message may be the first of a string of messages that are part of a conversation.
  • the conversation may include the user and one or more healthcare entities, and may include messages sent between healthcare entities that are not sent to the user.
  • Method 1000 further includes encrypting the one or more characters of 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 (1020).
  • the encryption module 907 may encrypt the inputted text characters using any one or more of a plurality of different encryption algorithms 908.
  • the encryption module 907 may encrypt all or select portions of the message 915.
  • the encrypted message may include portions of metadata that are or are not encrypted that include data about the user 905 and/or about the user's location or current state.
  • the metadata may further include information indicating whether the user has authenticated to the secure messaging service 917 of computer system 911, and/or whether a session 918 has been established.
  • the session 918 may be established between the user 905 and the secure messaging service 917, and may be expandable to include other healthcare entities. Alternatively, each user and healthcare entity may establish their own separate session with the secure messaging service 917. These sessions may be established through the messenger application 91 OA/910B, through a web page or through some other means of authentication.
  • Method 1000 also includes an act of initiating transmission of the encrypted message such that the encrypted message is sent to the specified healthcare entity, wherein the encrypted message is transferred in accordance with legal regulations governing healthcare communications (1030).
  • the messenger application 91 OA or the communications module 904 may initiate transmission of the encrypted message 915 to at least one healthcare entity 919.
  • the encrypted message may be sent directly to a specified healthcare entity or may be routed through one or more intervening computer systems.
  • the encrypted message 915 may be sent to the secure messaging service 917 of computer system 911.
  • the communications module 914 of computer system 911 may receive the encrypted message and may analyze any associated metadata to determine details about the sender (e.g. user 905).
  • a messenger application 1501 (which may be the same as or different than messenger application 91 OA) may provide various options 1503 to the user.
  • the user may create a message by entering text in the window provided 1502.
  • the user may then be able to select various options including whether to encrypt the message (1503 A), whether to have the message (or conversation) perish automatically upon delivery or completion or upon determining that a certain time period has elapsed since the transfer of the message (1503B), whether the message is to be sent in a HIPAA-compliant manner (1503C), whether the message is a privileged communication (e.g. as between a lawyer and a client) (1503D), or whether the user would like to add a file to the message (1503E).
  • Many other options may be provided that are not shown in Figure 15.
  • Metadata sent along with the message may indicate whether any of these options have been selected. Some of the options may necessitate the selection of other options. For instance, selecting the HIPAA-compliant option 1503C may automatically select the encrypt message option 1503 A). Similarly, selecting the privileged communication option 1503D may automatically select the perish automatically option 1503B. Some options, when selected, may cause processing to occur prior to transmission (e.g. encryption) while other options may cause processing to occur on intervening computer systems such as 911 or on other user's or healthcare entity's computing systems. Thus, in this manner, a user may select how the user wants their message to be sent, and what is to occur to their message after being sent (or after being read by the recipient).
  • these selected options may be overridden by other concerns such as regulations governing healthcare-related communications. For instance, if user 905 selects the HIPAA-compliant option 1503C and the perish automatically option 1503B, the perish automatically option will likely need to be ignored, as HIPAA compliance requires most types of healthcare-related communications to be stored, at least for some period of time. Thus, in such cases, option 1503C would trump option 1503B, and the messages would be stored and would not perish automatically. Policies may be established and promulgated by the secure messaging service 917 to determine which selectable options are ultimately applied to a given message.
  • that data may be retained on computer-readable storage media on the mobile device 901, on computer system 911 (or on a database accessible thereto), on a healthcare entity's computer system or on another system.
  • these messages may be stored in accordance with legal guidelines regulating healthcare communications (e.g. HIPAA-specified regulations).
  • the storage on computer systems 901 or 911 may be configured not to store messages or conversation-related data such as metadata.
  • the messages may be store in encrypted form and may only be accessible to authenticated users that have the proper credentials (i.e. they have the proper keys to decrypt the messages). Because the stored messages are encrypted, intervening entities involved in transmission between the user and the healthcare entity are prevented from accessing the encrypted messages.
  • user 905 may select which healthcare entity to send a message to by typing in the healthcare entity's name or by selecting a picture of the healthcare entity.
  • the messenger application 91 OA may display a picture of a doctor or a particular doctor's office. The user 905 may select that picture and begin typing their message. Once typed, the message is encrypted and transmitted to the specified healthcare entity in a HIPAA-compliant manner.
  • the messenger application 91 OA may determine, based on who the message is being sent to, that the message is to be sent in a HIPAA-compliant manner. In other cases, the user 905 may simply select HIPAA-compliance as an option for that message or conversation.
  • the encrypted message 915 is then transmitted to the specified healthcare entity over one or more computer systems including computer system 911.
  • the messenger application 91 OA may include an authentication module that is configured to authenticate the user prior to facilitating message transmission.
  • each healthcare entity's messenger application 91 OB may also be configured to receive authentication credentials from the healthcare entity and authenticate the entity before they can access received messages or send messages themselves.
  • the messages 915 are transmitted and received as push messages between the messenger application instances.
  • the messenger application 91 OA may provide portions of structural data that allow the healthcare entity to perform one or more specified functions such as filling prescriptions or filling out insurance or other forms.
  • FIG 11 illustrates a flowchart of a method 1100 for providing a secure messaging service. The method 1100 will now be described with frequent reference to the components and data of environment 900 of Figure 9.
  • Method 1100 includes receiving, at the secure messaging service, an encrypted message that includes message content intended for a specified healthcare entity, the encrypted message being part of a conversation between a user and the specified healthcare entity (1110).
  • secure messaging service 917 may receive encrypted message 915 that includes the content of the message as well as any corresponding metadata.
  • the determining module 916 may be configured to determine that the encrypted message 915 was received as part of an established session 918 between the secure messaging service and a user-side instance of a messenger application (1 120).
  • the communications module 914 of computer system 911 may then transmit the encrypted message to the specified healthcare entity 919, the specified healthcare entity can access the encrypted message via an instance of the messenger application 910B (1130).
  • the user/patient 1201 may use a messenger application 1202 A on their mobile or other device to the secure messaging service 1204 which is hosted on one or more virtual or physical computer system on the cloud 1203.
  • the secure messaging service 1204 may store and/or pass the message on to one or more specified healthcare recipients.
  • the user 1201 may directly message their doctor 1206 to request a prescription, or may directly message a doctor's office to request an appointment, or may message a nurse or doctor 1210 at a hospital 1209 to inquire on the health status of a relative.
  • healthcare providers may message each other using the secure messaging service 1204.
  • an emergency medical technician (EMT) 1205 may use their messenger application 1202B to message the hospital 1209 to notify them of a patient's current state, or a doctor 1206 may use their messenger application 1202C to message a pharmacy 1207 or pharmacist 1208 to call in a prescription for a patient, or the doctor 1206 may message a hospice provider 1211 with questions regarding a current or former patient.
  • EMT emergency medical technician
  • Each of these healthcare providers may use their messenger applications (e.g. 1202B, 1202C, 1202D, 1202E, 1202F) to reply back to any received messages.
  • healthcare providers and patients may communicate over secure channels in a HIPAA-compliant manner. It will be understood that the present application is not limited to those healthcare entities shown in Figure 12, and that many other entities (including non-healthcare entities) may use the secure messaging service 1204 to send secure messages.
  • a user or patient 1301 may use secure messaging service 1304 to request that a prescription be filled or refilled.
  • the user 1301 may initiate transmission of a prescription request 1302. That request is sent to the doctor 1306 (or pharmacist) through the secure messaging service 1304, which is hosted in the cloud 1303.
  • the prescription request 1302 may include form data 1305 that allows the doctor to easily fill in data for the prescription.
  • the form data may also include insurance and other appertaining information.
  • the doctor 1306 may then send the prescription 1307 to a specified pharmacy 1308 via the secure messaging service 1304. Once the prescription 1307 has been filed, the pharmacy may use their messenger application to send a notification 1309 to the user/patient 1301 indicating that the prescription is ready for pickup.
  • the doctor may message in the prescription to substantially any pharmacy, including one the user has previously used (perhaps many times) or to a new pharmacy (perhaps one that is currently located near the user (as determined by GPS on the user's mobile device)).
  • the secure messaging service 1304 can facilitate fulfillment of prescriptions for users.
  • users of the secure messaging service 1404 may use the service to send files securely.
  • a radiologist 1401 may send a request for an X-ray 1202 to a doctor's office through the secure messaging service 1404.
  • the secure messaging service 1404, hosted on cloud 1403, may send that X-ray request 1202 on to the doctor's office 1405, where the doctor's office is notified that the radiologist's request has been received.
  • the doctor's office 1405 may then attach a file including the patient's X-rays 1406 and message it to the radiologist via the secure messaging service 1404. It will be understood that many other use scenarios are possible, and that these are just a few of many different examples of healthcare entities securely messaging each other in the course of their everyday duties.
  • the secure messaging service 1204 of Figure 12 may be configured to store the corresponding encrypted messages in a data store.
  • the stored messages are thus auditable and retrievable for at least a specified amount of time.
  • Regulations governing the transmission of healthcare communications may dictate how long the messages and/or corresponding metadata are stored.
  • the message may perish automatically upon being read by the receiving entity.
  • the message is sent in a HIPAA-compliant manner, the message is encrypted and is only accessible by healthcare entities that are authorized to view the message or conversation.
  • Each healthcare entity can use their own messenger application instance to authenticate to the secure messaging service and communicate with other healthcare entities and/or the patient using application push messages transferred in encrypted form over the internet.
  • Computer architecture 1600 includes multiple computer systems including mobile device 1601, computer system 1613 and mobile device 1614.
  • Each computer system includes a processor (1602 A, 1602B and 1602C, respectively), a memory (1603A, 1603B and 1603C, respectively), and a communications module (1604A, 1604B and 1604C, respectively).
  • processor (1602 A, 1602B and 1602C, respectively
  • memory (1603A, 1603B and 1603C, respectively
  • communications module (1604A, 1604B and 1604C, respectively.
  • mobile device or “computer system”
  • each computing device may be any type of mobile or stationary, local or distributed computer system, including a cloud computing system.
  • Each computer system includes modules for performing a variety of different functions.
  • mobile device 1601 includes an authentication module 1605 A.
  • the authentication module 1605 A may be configured to receive authentication credentials from one or more users and authenticate those users.
  • one form of authentication may take place on the mobile device 1601 (or 1614) while a second form of authentication may take place on computer system 1613.
  • a user may login to a mobile device using a PIN number or other type of password or biometric authentication, and may login to the computer system 1613 (or to a service provided by the computer system 1613) using a different password or different type of authentication.
  • each computing device may have its own authentication module (i.e. 1605 A, 1605B or 1605C, respectively).
  • the mobile device 1601 may also include a health information module 1606.
  • the health information module 1606 may be configured to receive and/or store health information related to one or more patients. The health information may be entered directly into a health information application, or it may be received from one or more devices. For example, in cases where the first healthcare entity 1608 is a nurse working with patient 1607, the nurse may use a stethoscope or blood pressure cuff or other medical device to take health-related measurements for the patient. The nurse may then enter these measurements into a health information application, into a form or other information entry means. Additionally or alternatively, the medical device itself may be capable of providing health data directly to another computer system such as mobile device 1601 and/or computer system 1613. This information may be transferred and/or stored in a HIPAA-compliant manner. In some cases, this health information 1612 is transferred through computer system 1613 to mobile device 1614.
  • the doctor may receive this health condition information 1612 and analyze it to determine a diagnosis for the patient 1607.
  • the doctor may be remotely located from the patient, and may not be in the same state, country or continent.
  • the doctor may view the measurement data taken by the nurse, and may also view live streaming information (e.g. from a probe or video camera) that may show the patient's inner ear, throat, or other bodily region of interest.
  • live streaming information e.g. from a probe or video camera
  • the doctor may be able to determine that the patient has an ear infection, or has strep throat or has some other illness.
  • the doctor may send their diagnostic information 1618 either through computer system 1613 or directly to mobile device 1601. This diagnosis information may also be sent directly to the patient, and/or to a payment entity 1619.
  • the payment entity 1619 is a third party payment entity (e.g. a non-profit healthcare organization) that pays for medicines for patients who cannot afford them.
  • the computer architecture 1600 of Figure 16 allows health professionals to perform remote diagnostics and send those diagnostics to patients, healthcare providers such as nurses and/or to payment organizations.
  • Figure 17 illustrates a flowchart of a method 1700 for providing remote healthcare services. The method 1700 will now be described with frequent reference to the components and data of environment 1600.
  • Method 1700 includes receiving an input from a first healthcare entity that includes one or more authentication credentials, the input requesting assistance from at least a second healthcare entity (1710).
  • computer system 1613 may receive input 1609 from first healthcare entity 1608.
  • the input includes authentication credentials 1610 and a request for assistance 1611 from second healthcare entity 1617.
  • the authentication credentials may include, for example, a username and password, a PIN number, biometric credentials such as a fingerprint or other types of credentials. Substantially any type of authentication algorithm or scheme may be used to authenticate the first healthcare entity 1608.
  • first healthcare entity or “second healthcare entity” may refer to any of a variety of healthcare professionals (e.g.
  • the first healthcare entity 1608 may be a nurse or medical assistant located in a place that is remote to the second healthcare entity 1617, which may be a doctor or other licensed medical professional.
  • the healthcare entities may communicate with each other using the messenger application 91 OA/91 OB of Figure 9, as will be explained further below.
  • Method 1700 includes authenticating the first healthcare entity using the authentication credentials received from the first healthcare entity (1720). Either the authentication module 1605 A of mobile device 1601 or the authentication module 1605B or computer system 1613 may authenticate the first healthcare entity 1608 using authentication credentials 1610. Method 1700 also receives an input 1615 from the second healthcare entity 1617, where the input includes one or more authentication credentials 1616 identifying the second healthcare entity as one authorized to perform specified healthcare functions (1730).
  • the credentials 1616 may authenticate a single user, such as a doctor, or may authenticate an organization or specified group of users. This group of users may collaborate on a given diagnosis to determine the best course of action for a given patient.
  • the doctors i.e. second healthcare entity 1617
  • Method 1700 further includes authenticating the second healthcare entity using the authentication credentials received from the second healthcare entity (1740).
  • mobile device 1614 or computer system 1613 may authenticate the second healthcare entity 1617.
  • the authentication may include identifying the second healthcare entity as a medical professional, assistant or entity that is authorized to provide a level of healthcare, including potentially diagnosing illnesses, treating diseases, prescribing medications, examining x-rays, analyzing blood results, or performing any of a wide variety of healthcare-related functions not mentioned.
  • the second healthcare entity 1617 may receive (either directly or through computer system 1613) real-time information related to a health condition of at least one patient (1750).
  • the second healthcare entity 1617 may receive health condition information 1612 from the first healthcare entity, which may be a nurse or assistant that is working with the patient 1706.
  • Method 1700 further includes receiving, from the second healthcare entity, one or more portions of diagnostic information related to the patient's health condition (1760) and providing the received diagnostic information to at least one of the following: the first healthcare entity, the patient and a payment entity (1770).
  • the second healthcare entity 1617 can view the totality of the health condition information 1612 including verbal descriptions from a nurse, test results, still images, live video feeds, instrumentation data from diagnostic devices or other health condition information, and make a determination as to the best course of action related to the patient 1607.
  • the second healthcare entity (or group of entities such as collaborating doctors) may provide a diagnosis 1618 which is sent to the patient, to the first healthcare entity 1608 and/or to a payment entity 1619.
  • the diagnosis may include a drug prescription or other prescribed course of action (e.g. a cast for a broken arm or a leg brace for a sprained knee).
  • This prescribed drug or other course of action may be paid for or reimbursed by a payment entity 1619 such as a third-party non-profit organization.
  • providing real-time health condition information 1612 to the second healthcare entity 1617 includes streaming images or video from the first healthcare entity 1608 to the second healthcare entity 1617.
  • the video may include video taken from a mobile device's camera, video taken from a medical instrument such as a probe, still images taken with a digital camera or with the mobile device's camera, audio information such as verbal descriptions of the patient's medical issues or other health condition information.
  • a doctor 2007 or other health professional may use the real-time streaming data 2004 to assist in making a diagnosis.
  • the real-time health condition streaming data may also be communicated to other entities using various forms of communication including a messenger application (e.g. 91 OA).
  • the doctor 2007 and the nurse 2003 may each have mobile devices (2006 and 2005, respectively) which may be smartphones, tablets, laptops or other computing systems.
  • the nurse 2003 may use the mobile device to take pictures, provide streaming video or perform other functions.
  • the nurse's mobile device 2005 may be used in combination with a diagnostic device 2002 (such as a stethoscope or an otoscope) to provide the streaming health condition data 2004.
  • a diagnostic device 2002 such as a stethoscope or an otoscope
  • the diagnostic device itself 2002 may have a communication means that allows it to transmit the streaming data 2004 to other entities.
  • the nurse 2003 may thus analyze the patient's condition or provide health condition data for the patient 2001 to the doctor 2007.
  • the nurse 2003 and doctor 2007 may use the secure messaging service 917 to conduct a real-time conversation 2008 over messenger application push messages 2009.
  • doctors and nurses can communicate using text messages over a secure network (other than the traditional SMS text network).
  • the text messages may be transmitted in a HIPAA-compliant manner, or may be transmitted in another manner that complies with regulations governing health-related communications in a foreign country.
  • diagnostic information 1618 may also be transferred between the first healthcare entity and the second healthcare entity using the messenger application. In this manner, information relating to the patient's health conditions and the patient's diagnosis may be transferred using the messenger application 91 OA/910B.
  • the computer system 1613 may receive an indication from the third-party payment entity indicating that the medication or other specified course of action has been paid for. The computer system 1613 may then provide an indication to the first healthcare entity 1608 indicating that the specified medication has been paid for. Once the first healthcare entity receives this notification, they can give the patient the prescription, or in cases where the first healthcare entity is a pharmacy, the pharmacy can fill the prescription for the patient. The second healthcare entity 1617 may then be notified that the patient received the medication.
  • a doctor may be able to view a patient's current condition, recommend a course of action, have that course of action paid for by a third party organization, and receive an indication that the intended course of action has been carried out (e.g. that the patient has received Amoxicillin for an ear infection).
  • the doctor or other healthcare entity may maintain contact with the patient using the messenger application.
  • a messenger application allows the second healthcare entity to follow-up on the patient's prescription compliance to ensure that they are taking the prescribed medication or are wearing their brace or are otherwise complying with the doctor's wishes.
  • Any or all of the health condition information 1612, the diagnostic information 1618, the payment information, the messenger application messages or other remote diagnostic-related information may be stored in a HIPAA-compliant manner, so as to ensure that the process is transacted within the confines of regulations governing the practice of medicine and the communication of patient health-related data.
  • Figure 18 illustrates a flowchart of a method 1800 for facilitating a third- party healthcare payment. The method 1800 will now be described with frequent reference to the components and data of environment 1900 of Figure 19.
  • Method 1800 includes receiving an input from a healthcare entity identifying at least one healthcare item that is to be paid for by a third party, the healthcare entity being authenticated to a third-party healthcare payment service (1810).
  • computer system 1901 may receive indication 1902 indicating one or more healthcare items.
  • the indication 1902 may be sent by healthcare entity 1903.
  • the healthcare entity 1903 may be a doctor, nurse or other health professional.
  • Method 1800 next includes sending an indication of the at least one identified healthcare item to the third party for payment (1820).
  • the computer system 1901 may thus send the healthcare item indication 1902 to a payment organization such as a third-party non-profit organization 1905 that has been established to pay for healthcare items.
  • a payment organization such as a third-party non-profit organization 1905 that has been established to pay for healthcare items.
  • the third-party organization 1905 may be designed to pay for prescriptions, vaccinations, casts, braces or any of a variety of other medical devices, tools, medicines or other related items which may be used to help a person heal from a malady of some sort.
  • the third-party organization 1905 may pay for such items for persons who cannot afford those items themselves.
  • a nurse may examine a patient in a foreign country, have a doctor review the analysis or provide their own diagnosis, and have that doctor (e.g. 1903) indicate to a third-party organization that the patient's prescribed medical items are to be paid for.
  • doctor e.g. 1903
  • Method 1800 further includes receiving authorization from the third party to pay for the at least one identified healthcare item (1830).
  • computer system 1901 may receive a payment authorization 1906 from the third-party organization 1905.
  • the payment authorization 1906 indicates that the third-party organization 1905 is willing to pay for the item(s) mentioned in the indication 1902.
  • the third-party healthcare payment service 1904 of computer system 1901 may then initiate a transaction that allows the third party organization 1905 to pay for the identified healthcare item(s) (1840).
  • the transaction 1908 may take place between a banking or credit entity 1909 and the third-party organization 1905.
  • the third-party healthcare payment service may be configured to transfer money between the banking or credit entity 1909 and the third-party organization 1905.
  • a notification 1907 is sent to the third party organization 1905 notifying them that the transaction is complete and that the identified healthcare item(s) has/have been paid for (1850).
  • the third-party healthcare payment service may further notify at least one beneficiary that one or more of the identified healthcare item have been paid for by the third party.
  • the third-party healthcare payment service may work in conjunction with the secure messaging service 917 of Figure 9 to notify the third party organization 1905 that the transaction is complete and that the at least one identified healthcare item has been paid for.
  • the third-party healthcare payment service 19904 facilitates payments between third parties and banking or credit institutions.
  • the third-party organization 1905 may be a single individual, a group of individuals or an entity (such as a non- profit entity or other organization).
  • members of the third-party organization 1905 may analyze and approve a diagnosis as being proper before a payment authorization is given. Such secondary analysis may be used to reduce fraud, ensuring that healthcare items are only purchased for those who are truly sick and need the items.
  • a computer program product may be provided for implementing a method for providing a remote diagnostic for a patient.
  • the computer program product includes one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of a computing system, cause the computing system to perform the method.
  • the method may be from the perspective of the second healthcare entity 1617 of Figure 16 (or from the perspective of their mobile device 1614).
  • the method includes receiving an input 1615 from a user that includes one or more authentication credentials 1616 corresponding to the user 1617.
  • the communications module 1604C of the mobile device 1614 may transmit the received authentication credentials 1616 to a remote diagnostic service.
  • the mobile device 1614 may receive real-time information related to a health condition of at least one remotely-located patient, and may provide one or more portions of diagnostic information related to the patient's health condition to the remote diagnostic service for distribution to other healthcare entities (e.g. 1608), to the remotely-located patient 1607 or to a payment entity 1619.
  • a healthcare entity may work with a patient to determine the patient's current health condition.
  • Information related to the patient's health can be sent to a remote doctor or other health professional. This doctor may reach a conclusion and provide a diagnosis that includes recommended healthcare items, such as prescriptions.
  • This information may be sent to a third-party payment organization for payment, upon which the original healthcare entity is notified that the healthcare items were paid for and can now be distributed to the patient.
  • the healthcare entities may communicate throughout the process using a secure messaging service and messenger applications which allow users and healthcare entities to communicate via text (or picture or video) messages in a secure and HIPAA- compliant manner.
  • Other embodiments include a multi-access (HIPAA-compliant) health care provider portal which allows multiple different authenticated providers to access patients' medical records. Moreover, the portal allows specified portions of the medical records to be transmitted to certain care givers based on user-established policies. The portal further facilitates communication between care givers, including communication of a patient's prescription compliance data, and allows manufacturers and service providers to provide targeted items to users based on their health concerns.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

Des modes de réalisation consistent à fournir des services de soins de santé à distance comprenant des diagnostics à distance, ainsi qu'à faciliter les paiements de soins de santé de tiers. Dans un mode de réalisation, un système informatique reçoit une entrée comprenant des justificatifs d'authentification d'une entité de soins de santé, et demande également de l'aide à une autre entité de soins de santé. Le système informatique authentifie la première entité de soins de santé au moyen de justificatifs d'authentification, reçoit une entrée comprenant des justificatifs d'authentification de l'autre entité de soins de santé, et authentifie l'autre entité de soins de santé au moyen de ces justificatifs d'authentification. Le système informatique reçoit également des informations en temps réel relatives à un état de santé d'un patient, les informations sur l'état de santé en temps réel étant fournies à la seconde entité de soins de santé. Le système informatique reçoit également, de l'autre entité de soins de santé, des informations de diagnostic relatives à l'état de santé du patient, et fournit les informations de diagnostic à la première entité de soins de santé, au patient et/ou à une entité de paiement.
PCT/US2015/030664 2014-05-15 2015-05-13 Diagnostic à distance d'états et fourniture de prescriptions au moyen d'un portail de fournisseur de soins de santé multi-accès WO2015175721A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
MX2016014969A MX2016014969A (es) 2014-05-15 2015-05-13 Diagnostico de manera remota de afecciones y provision de prescripciones usando portal de proveedor de cuidado de salud de acceso multiple.
SG11201610509SA SG11201610509SA (en) 2014-05-15 2015-05-13 Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/278,980 US11354623B2 (en) 2013-02-15 2014-05-15 Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal
US14/278,980 2014-05-15

Publications (1)

Publication Number Publication Date
WO2015175721A1 true WO2015175721A1 (fr) 2015-11-19

Family

ID=54480646

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/030664 WO2015175721A1 (fr) 2014-05-15 2015-05-13 Diagnostic à distance d'états et fourniture de prescriptions au moyen d'un portail de fournisseur de soins de santé multi-accès

Country Status (3)

Country Link
MX (1) MX2016014969A (fr)
SG (1) SG11201610509SA (fr)
WO (1) WO2015175721A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104199835A (zh) * 2014-08-01 2014-12-10 广州中大电讯科技有限公司 一种基于Web的居家养老健康服务的资源整合方法
US9959385B2 (en) 2013-02-15 2018-05-01 Davincian Healthcare, Inc. Messaging within a multi-access health care provider portal
US11354623B2 (en) 2013-02-15 2022-06-07 Dav Acquisition Corp. Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010034618A1 (en) * 2000-02-24 2001-10-25 Kessler David G. Healthcare payment and compliance system
US20040034550A1 (en) * 2002-08-16 2004-02-19 Menschik Elliot D. Methods and systems for managing distributed digital medical data
US20080004904A1 (en) * 2006-06-30 2008-01-03 Tran Bao Q Systems and methods for providing interoperability among healthcare devices
US20110218814A1 (en) * 2010-03-05 2011-09-08 Applied Health Services, Inc. Method and system for assessing a patient's condition
US20140088998A1 (en) * 1998-02-27 2014-03-27 Realmed Corporation Point of service third party financial management vehicle for the health care industry

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140088998A1 (en) * 1998-02-27 2014-03-27 Realmed Corporation Point of service third party financial management vehicle for the health care industry
US20010034618A1 (en) * 2000-02-24 2001-10-25 Kessler David G. Healthcare payment and compliance system
US20040034550A1 (en) * 2002-08-16 2004-02-19 Menschik Elliot D. Methods and systems for managing distributed digital medical data
US20080004904A1 (en) * 2006-06-30 2008-01-03 Tran Bao Q Systems and methods for providing interoperability among healthcare devices
US20110218814A1 (en) * 2010-03-05 2011-09-08 Applied Health Services, Inc. Method and system for assessing a patient's condition

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9959385B2 (en) 2013-02-15 2018-05-01 Davincian Healthcare, Inc. Messaging within a multi-access health care provider portal
US11354623B2 (en) 2013-02-15 2022-06-07 Dav Acquisition Corp. Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal
US11455597B2 (en) 2013-02-15 2022-09-27 Dav Acquisition Corp. Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal
CN104199835A (zh) * 2014-08-01 2014-12-10 广州中大电讯科技有限公司 一种基于Web的居家养老健康服务的资源整合方法

Also Published As

Publication number Publication date
SG11201610509SA (en) 2017-01-27
MX2016014969A (es) 2018-01-12

Similar Documents

Publication Publication Date Title
US9959385B2 (en) Messaging within a multi-access health care provider portal
US11455597B2 (en) Remotely diagnosing conditions and providing prescriptions using a multi-access health care provider portal
US11881291B2 (en) Patient directed data synchronization of electronic health records using a patient controlled health record
Malvey et al. mHealth: transforming healthcare
US20190214116A1 (en) Digital health platform for chronic disease management, secure messaging, prescription management, and integrated e-commerce curation
US11443855B2 (en) Secure dispersed network for improved communications between healthcare industry participants
US9734287B2 (en) Linking health care applications for information management
US8990834B2 (en) Managing healthcare information in a distributed system
US20170329922A1 (en) Telemedicine platform with integrated e-commerce and third party interfaces
US11710132B2 (en) User controlled event record system
US20230223126A1 (en) Digital Health Platform with Prescription Management and Integrated E-Commerce Curation
CA3197581A1 (fr) Systeme de dossiers medicaux axe sur les humains et methodes connexes
WO2016144784A1 (fr) Plateforme de télémédecine comprenant des interfaces de commerce électronique et de tiers intégrées
US20210158945A1 (en) Identifying referral patterns between healthcare entities based on billed claims
US20190267122A1 (en) Systematic patient information, records and appointment library system
US20140236612A1 (en) Multi-access health care provider portal
US20230385450A1 (en) Human-centric health record system and related methods
WO2015175721A1 (fr) Diagnostic à distance d'états et fourniture de prescriptions au moyen d'un portail de fournisseur de soins de santé multi-accès
US20180293358A1 (en) Prescription drug customer messaging systems and methods
US20230317255A1 (en) Dynamic administrative system for healthcare and telehealth management
EP2779000A1 (fr) Système de boîte à outils et procédé de gestion de livraison de contenu et services de soins de professionnels de soins de santé via un système de dossiers médicaux électroniques
Gawade et al. Trusty Medicare: An Online Virtual Care System
CA3108555A1 (fr) Systeme de dossiers medicaux axe sur les humains et methodes connexes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15792974

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/014969

Country of ref document: MX

122 Ep: pct application non-entry in european phase

Ref document number: 15792974

Country of ref document: EP

Kind code of ref document: A1