Systems and methods for direct-to-patient platform

Abstract

A method includes: receiving, by one or more computing devices, patient information; generating, by the one or more computing devices, identifiable patient information and de-identifiable patient information, using the patient information; aggregating, by the one or more computing devices, the identifiable patient information and the de-identifiable patient information; transmitting, by the one or more computing devices, the de-identifiable patient information to a direct-to-patient platform; determining, by the one or more computing devices, one or more of a status or an association for the de-identifiable patient information; and displaying, by the one or more computing devices, one or more prescription services, based on the one or more of the status or the association.

Description

Attorney Docket No.: 00401-0002-00304SYSTEMS AND METHODS FOR DIRECT-TO-PATIENT PLATFORMCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Application No. 63 / 730,571 , filed December 11 , 2024, which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] Various embodiments of the present disclosure relate generally to a direct-to-patient platform, and, more particularly, to a direct-to-patient platform that provides an integrated patient experience.BACKGROUND

[0003] Health care systems can provide a granular and complicated patient experience with regard to using different products for disease awareness, diagnosis, prescription fulfillment, and on-going treatment.

[0004] The present disclosure is directed to overcoming one or more of these above-referenced challenges.SUMMARY OF THE DISCLOSURE

[0005] In some aspects, the techniques described herein relate to a method including: receiving, by one or more computing devices, patient information; generating, by the one or more computing devices, identifiable patient information and de-identifiable patient information, using the patient information; aggregating, by the one or more computing devices, the identifiable patient information and the de- identifiable patient information; transmitting, by the one or more computing devices, the de-identifiable patient information to a direct-to-patient platform; determining, by the one or more computing devices, one or more of a status or an association for the de-identifiable patient information; and displaying, by the one or more computing devices, one or more prescription services, based on the one or more of the status or the association.

[0006] In some aspects, the techniques described herein relate to a method,Attorney Docket No.: 00401-0002-00304 wherein the patient information include one or more of a patient profile, a patient insurance coverage, or a prescription.

[0007] In some aspects, the techniques described herein relate to a method, further including: verifying, by the one or more computing devices, prescription benefits, in response to receiving the patient information.

[0008] In some aspects, the techniques described herein relate to a method, further including: prioritizing, by the one or more computing devices, a pharmacy selection in response to determining one or more of the status and the association for the patient information.

[0009] In some aspects, the techniques described herein relate to a method, further including: tracking, by the one or more computing devices, an end-to-end patient journey using one or more of the status, the identifiable patient information, or the de-identifiable patient information.

[0010] In some aspects, the techniques described herein relate to a method, further including: generating, by the one or more computing devices, a dashboard displaying the end-to-end patient journey, wherein the end-to-end patient journey includes one or more status indicators associated with one or more operations in the end-to-end patient journey.

[0011] In some aspects, the techniques described herein relate to a method, further including: notifying, by the one or more computing devices, a patient during a pharmacy selection indicating product inventory availability at one or more pharmacies.

[0012] In some aspects, the techniques described herein relate to a method, wherein displaying the one or more prescription services includes providing a plurality of pharmacy options to a patient device, the plurality of pharmacy options including one or more of a specialty pharmacy, a retail pharmacy, or a digital pharmacy.

[0013] In some aspects, the techniques described herein relate to a system including: a patient experience layer configured to receive information via an application programming interface (API) layer; a components layer configured to interact with the patient experience layer via the API layer; an artificial intelligence (Al) layer configured to optimize and personalize a patient experience in response to the received information in the patient experience layer; and an analytics layer configured to track and store the received information and display a dashboard to aAttorney Docket No.: 00401-0002-00304 patient via a patient device.

[0014] In some aspects, the techniques described herein relate to a system, wherein the patient experience layer includes one or more of a patient omni-channel, a patient self-service channel, or a contact center channel.

[0015] In some aspects, the techniques described herein relate to a system, wherein the components layer includes a plurality of sub-components, wherein the plurality of sub-components include one or more of an audience management module, a journey management module, a campaign management module, a patient customer relationship management module, a digital intake pharmacy module, a telehealth module, a self-assessment module, a specialist finder module, a patient community module, an electronic benefits verification module, or an electronic prior authorization module.

[0016] In some aspects, the techniques described herein relate to a system, wherein the API layer is configured to provide one or more connections including one or more of a copay verification, a pharmacy lookup, an electronic benefits verification, a payment processing, a prescription transfer, an electronic prior authorization, or a partner pharmacy integration.

[0017] In some aspects, the techniques described herein relate to a system, wherein the analytics layer is configured to identify one or more new patients and provide tracking information associated with each of the one or more new patients throughout a patient journey.

[0018] In some aspects, the techniques described herein relate to a system, further including: one or more memories storing instructions associated with the patient experience layer, the components layer, the Al layer, and the analytics layer; and one or more processors configured to execute the instructions.

[0019] In some aspects, the techniques described herein relate to a non- transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations including: receiving patient information; generating identifiable patient information and de-identifiable patient information, using the patient information; aggregating the identifiable patient information and the de-identifiable patient information; transmitting the de-identifiable patient information to a direct-to-patient platform; determining one or more of a status or an association for the de-identifiable patient information; and displaying one or more prescription services, based on the one orAttorney Docket No.: 00401-0002-00304 more of the status or the association.

[0020] Additional objects and advantages of the disclosed embodiments will be set forth in part in the description that follows, and in part will be apparent from the description, or may be learned by practice of the disclosed embodiments. The objects and advantages of the disclosed embodiments will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.

[0021] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosed embodiments, as claimed.BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and together with the description, serve to explain the principles of the disclosed embodiments.

[0023] FIG. 1 depicts an exemplary network computing environment, according to one or more embodiments.

[0024] FIG. 2 depicts exemplary system components, according to one or more embodiments.

[0025] FIG. 3 depicts exemplary system connections, according to one or more embodiments.

[0026] FIG. 4 depicts an exemplary system architecture, according to one or more embodiments.

[0027] FIG. 5 depicts an exemplary system overview, according to one or more embodiments.

[0028] FIG. 6 depicts an exemplary patient prescription flowchart, according to one or more embodiments.

[0029] FIG. 7 depicts an exemplary patient intake flowchart, according to one or more embodiments.

[0030] FIG. 8A and FIG. 8B depict exemplary user interfaces, according to one or more embodiments.

[0031] FIG. 9 depicts a flow diagram for training a machine-learning model, according to one or more embodiments.Attorney Docket No.: 00401-0002-00304

[0032] FIG. 10 depicts an exemplary computing device, according to one or more embodiments.

[0033] Notably, for simplicity and clarity of illustration, certain aspects of the figures depict the general configuration of the various embodiments. Descriptions and details of well-known features and techniques may be omitted to avoid unnecessarily obscuring other features. Elements in the figures are not necessarily drawn to scale; the dimensions of some features may be exaggerated relative to other elements to improve understanding of the example embodiments.DETAILED DESCRIPTION

[0034] Both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the features, as claimed. As used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” “including,” or other variations thereof, are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such a process, method, article, or apparatus. In this disclosure, unless stated otherwise, relative terms, such as, for example, “about,” “substantially,” and “approximately” are used to indicate a possible variation of ±10% in the stated value. In this disclosure, unless stated otherwise, any numeric value may include a possible variation of ±10% in the stated value.

[0035] The terminology used below may be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the present disclosure. Indeed, certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.

[0036] Various embodiments of the present disclosure relate generally to a direct-to-patient platform, and, more particularly, to a direct-to-patient platform that provides an integrated patient experience.

[0037] A patient may experience long wait times along various phases of a health care journey. Long wait times may include the need to find and / or book an appointment with a primary care physician (PCP), wait for the date of theAttorney Docket No.: 00401-0002-00304 appointment, and travel time to and from the appointment and pharmacy, for example. In addition, health care professionals (HCP) may be limited by the amount of time and / or the information available with respect to the current state of a disease, which requires the patient to follow-up with another HCP, resulting in delaying the treatment and causing frustration to the patient. Patients who are provided with a prescription may encounter challenges related to insurance coverage, copays, and / or other billing-related issues, resulting in delays and confusion.

[0038] Depending on the pharmacy selected by the patient, the pharmacy may face shortages of certain medications, which may lead to delays or the need to visit multiple pharmacies to find a prescribed drug. Complex prescription processes, such as obtaining prior authorization or dealing with specialty medications may be overwhelming for the patient. Some patients may feel the services provided by the retail pharmacies are not personalized enough to address their specific needs or health concerns. Limited operating hours of retail pharmacies may be inconvenient for patients who may need medication outside regular business hours. Additionally, there may be communication gaps between HCPs, patients, and pharmacies, which may lead to misunderstandings or errors in medication management.

[0039] One or more embodiments may provide a direct-to-patient (DTP) care platform to streamline the patient experience. The DTP care platform may include identification and engagement components to predict, find, and research HCP and patients to provide optimized solutions. The DTP care platform may include identification tools, telehealth screenings, and virtual visit capabilities for HCPs. One or more embodiments may ensure that prior authorizations are in place and benefits are optimized to reduce prices for the patient, in addition to providing multiple payment and prescription distribution options. One or more embodiments may provide patient support to maintain the adherence with the patient’s drug regimen, including refill and broader integrated programs.

[0040] One or more embodiments may provide end-to-end modular direct patient engagement solution to support the launch and market success of life science products, including disease awareness, diagnosis, fulfillment, and on-going treatment across digital and human touchpoints. One or more embodiments may provide seamless integration of the digital patient experience across one or more of patient education and awareness, virtual and physical care visits, or digitized fulfillment, with fail-over human coaching / support at each stage.Attorney Docket No.: 00401-0002-00304

[0041] One or more embodiments may provide integration with one or more physical clinicians, medical practices, health systems via clinician finder, automated patient on-boarding and fulfillment, or on-going patient messaging. One or more embodiments may track, measure, and / or optimize the end-to-end patient journey using one or both of identifiable (PHI) and de-identified data as needed to comply with local regulations and privacy laws. One or more embodiments may provide end- to-end analytics and optimization of a patient journey powered by machine-learning (ML) and Artificial Intelligence (Al) to increase conversions at each stage and reduce time to treatment.

[0042] One or more embodiments may provide capabilities and workflow with APIs that are configurable for different patient journeys, product scenarios, and / or regions. One or more embodiments may provide optimization of field resources via insights gathered from the direct patient engagement solution by estimating the flow of patients through virtual and physical care channels and promotion of automated on-boarding and fulfillment and messaging solutions to clinicians. One or more embodiments may provide the ability for patients to receive direct shipments at home, including making payments directly, by integrating with modem payment gateways.

[0043] One or more embodiments may provide an ability of a digital pharmacy to dispense free goods to patients who are uninsured, underinsured, or require bridge programs while formal coverage is established. One or more embodiments may notify patients during the process of pharmacy selection to understand which pharmacies may have the product inventory available in an effort to reduce time to fill. One or more embodiments may provide an ability of a pharmacy to offer 24 hour support through “follow the sun” model by leveraging offshore support to expedite backlog management at the pharmacy.

[0044] FIG. 1 depicts an exemplary network computing environment, according to one or more embodiments. Environment 100 may include one or more user device(s) 105, one or more external system(s) 110, and one or more server system(s) 115 may communicate across a network 101 . As will be discussed in further detail below, one or more server system(s) 115 may communicate with one or more of the other components of the environment 100 across network 101. The one or more user device(s) 105 may be associated with a user, e.g., a user associated with one or more of generating, training, or tuning a machine-learning model.Attorney Docket No.: 00401-0002-00304

[0045] The user device 105 may be configured to enable the user to access and / or interact with other systems in the environment 100. For example, the user device 105 may be a computer system such as, for example, a desktop computer, a mobile device, a tablet, etc. In some embodiments, the user device 105 may include one or more electronic application(s), e.g., a program, plugin, browser extension, etc., installed on a memory of the user device 105. The user device 105 may include a display / user interface (III) 105A, a processor 105B, a memory 105C, and / or a network interface 105D. The user device 105 may execute, by the processor 105B, an operating system (O / S) and at least one electronic application (each stored in memory 105C). The electronic application may be a desktop program, a browser program, a web client, or a mobile application program (which may also be a browser program in a mobile O / S), an applicant specific program, system control software, system monitoring software, software development tools, or the like. For example, environment 100 may extend information on a web client that may be accessed through a web browser.

[0046] In some embodiments, the electronic application(s) may be associated with one or more of the other components in the environment 100. The application may manage the memory 105C, such as a database, to transmit streaming data to network 101. The display / UI 105A may be a touch screen or a display with other input systems (e.g., mouse, keyboard, etc.) so that the user(s) may interact with the application and / or the O / S. The network interface 105D may be a TCP / IP network interface for, e.g., Ethernet or wireless communications with the network 101. The processor 105B, while executing the application, may generate data and / or receive user inputs from the display / UI 105A and / or receive / transmit messages to the server system 115, and may further perform one or more operations prior to providing an output to the network 101 .

[0047] External systems 110 may be, for example, one or more third party and / or auxiliary systems that integrate and / or communicate with the server system 115 in performing various natural language instruction tasks. External systems 110 may be in communication with other device(s) or system(s) in the environment 100 over the one or more networks 101 . For example, external systems 110 may communicate with the server system 115 via API (application programming interface) access over the one or more networks 101 , and also communicate with the user device(s) 105 via web browser access over the one or more networks 101. In variousAttorney Docket No.: 00401-0002-00304 embodiments, the network 101 may be a wide area network (“WAN”), a local area network (“LAN”), a personal area network (“PAN”), or the like. In some embodiments, network 101 includes the Internet, and information and data provided between various systems occurs online.

[0048] The server system 115 may include an electronic data system, e.g., a computer-readable memory such as a hard drive, flash drive, disk, etc. In some embodiments, the server system 115 includes and / or interacts with an application programming interface for exchanging data to other systems, e.g., one or more of the other components of the environment. The server system 115 may include a database 115A and at least one server 115B. The server system 115 may be a computer, system of computers (e.g., rack server(s)), and / or or a cloud service computer system. The server system may store or have access to database 115A (e.g., hosted on a third party server or in memory 115E). The server(s) may include a display / UI 115C, a processor 115D, a memory 115E, and / or a network interface 115F. The display / UI 115C may be a touch screen or a display with other input systems (e.g., mouse, keyboard, etc.) for an operator of the server 115B to control the functions of the server 115B. The server system 115 may execute, by the processor 115D, an operating system (O / S) and at least one instance of a servlet program (each stored in memory 115E).

[0049] Although depicted as separate components in FIG. 1 , it should be understood that a component or portion of a component in the environment 100 may, in some embodiments, be integrated with or incorporated into one or more other components. For example, a portion of the display / UI 115C may be integrated into the user device 105 or the like. In some embodiments, operations or aspects of one or more of the components discussed above may be distributed amongst one or more other components. Any suitable arrangement and / or integration of the various systems and devices of the environment 100 may be used.

[0050] FIG. 2 depicts exemplary system components, according to one or more embodiments. Direct to patient (DTP) platform architecture 200 may include a patient and health care professional (HCP) omni-channel 210, an ACTICS patient relationship management 220, an eBV and ePA 230, a pharmacy management system 240, HCP and FAM portals 250, patient self-services 260, a patient services contact center 270, an application programming interface (API) 280, and a business rules engine 290.Attorney Docket No.: 00401-0002-00304

[0051] Patient and HCP omni-channel 210 may aggregate and synthesize pivotal datasets from marketing campaigns, patient services programs, and field deployment activities to analyze and predict trends and behaviors that better inform promotional and support strategies. Patient and HCP omni-channel 210 may serve as a seamless router of actionable data and deep insights from all channels. Patient and HCP omni-channel 210 may provide coordination of customized touch points to create a seamless brand experience for healthcare providers, patients, payers, and other key stakeholders.

[0052] ACTICS patient relationship management 220 may leverage a combination of proprietary Al and machine-learning (ML) technologies to deliver end- to-end commercial success for life science companies. ACTICS patient relationship management 220 may address critical challenges throughout the product life cycle and improve patient outcomes. ACTICS patient relationship management 220 may create single informed strategies from early in development to launch with speed and certainty. ACTICS patient relationship management 220 may inform healthcare and clinical decision-making at launch and accelerate access for patients. ACTICS patient relationship management 220 may improve patient outcomes and identify opportunities to lower total cost of care. ACTICS patient relationship management 220 may generate regulatory-grade evidence to quantify the economic and clinical value of healthcare interventions to payers, provider, and patients.

[0053] eBV and ePA 230 may communicate with ACTICS patient relationship management 220 to provide electronic benefits (eBV) and electronic prior authorization (ePA) tools. eBV and ePA 230 may provide electronic verification results more accurately, improving patient access and accelerating speed to therapy. eBV and ePA 230 may verify a patient’s insurance eligibility in a simple and straightforward process. eBV and ePA 230 may limit the painstaking process that consumes HCP staff time, causing confusion and frustration due to inaccurate information, among other delays initiating treatment for patients in need. eBV and ePA 230 may elevate the benefits verification process beyond prior, traditional models by leveraging over 1 ,400 digital connections to payers rather than algorithms, providing highly accurate coverage for both pharmacy and major medical benefits being confirmed in minutes rather than days.

[0054] Pharmacy management system 240 may allow pharmacists with the ability to do more than just dispense medication by providing one or more of accessAttorney Docket No.: 00401-0002-00304 to pharmacies, workflows, and patient care in an effort to fuel business growth allowing pharmacists to focus on improving the health of each patient. Pharmacy management system 240 may provide customizable workflows to assist pharmacists in saving time to focus on providing patient care and clinical services. Pharmacy management system 240 may include additional features, such as, med sync, patient risk scores, reporting and improvement, automatic refill, patient labs, patient engagement, and outcomes.

[0055] HCP and FAM portals 250 may provide a 360 degree view of a patient’s medical information using at least one of a community cloud and health cloud information systems. HCP and FAM portals 250 may maintain a list of patients, receive alerts, update care plans, and refer patients to specialists. HCP and FAM portals 250 may provide a deep understanding of individual patient’s profiles, including demographics, communications, clinical and non-clinical data, and pertinent information from an emergency health record (EHR), membership and claims systems, medical devices, and wearables in a single central location. HCP and FAM portals 250 may empower patients and member to access and track progress towards their respective health goals and care plans. HCP and FAM portals 250 may provide connections in real-time for quickly addressing any questions from family members and patients. HCP and FAM portals 250 may monitor cases and prioritize tasks based on immediate needs and level of importance, in addition segment populations by at least condition, demographics, or risk.

[0056] Patient self-services 260 may provide several options for a user to review documents relating to their user profile and contact assistance through one or more communication systems (e.g., SMS messaging system, toll free numbers, email, etc.).

[0057] Patient services contact center 270 may provide innovative solutions to lay the foundation for a more connected, secure, and sustainable future in healthcare. Patient services contact center 270 may securely connect providers, patients, and staff with transformative technologies that power inclusive care for all. Patient services contact center 270 may transform the workplace, deliver care anywhere, heighten security and compliance, and make data-driven care decisions.

[0058] API 280 and Business rules engine 290 may receive and transmit information between components of the DTP platform architecture 200. API 280 and Business rules engine 290 may increase productivity by managing all APIs andAttorney Docket No.: 00401-0002-00304 microservices from a single place. API 280 and Business rules engine 290 may provide secure API policies, manage client access, group APIs as products, and gain critical insights into API programs. API 280 and Business rules engine 290 may provide access to APIs and control API traffic by automatically enforcing pre-built or custom policies, by adding or removing policies for API security, throttling, rate limiting, caching, and identity management at runtime with minimal downtime. API 280 and Business rules engine 290 may apply policies across all APIs with a consistent management experience, regardless of the architectural style or specification language used. API 280 and Business rules engine 290 may connect one or more hosted identity management providers to secure access for app developers, partners, and internal business groups by leveraging SAML integration to manage SSO and authorize API consumption through policies.

[0059] FIG. 3 depicts exemplary system connections, according to one or more embodiments. DTP platform architecture 200, as described with respect to FIG. 2 above, may interact with or integrate one or more external systems 300. The one or more external systems 300 may include Customer S&M Automation system 310, Partner specialty Pharmacies 320, Telehealth Partners 330, Patient Community 340, EzButton 350, Specialist Finder 360, and Customer Data Environment 370.

[0060] FIG. 4 depicts an exemplary system architecture, according to one or more embodiments. DTP platform architecture 400 may include some or all of the components as described in FIG. 2 and FIG. 3. DTP platform architecture 400 may include a process flow layer 410, an experience layer 420, an API layer 430, a systems layer 440, an Al layer 450, and a data and analysis layer 460. Process flow layer 410 may include an ignite interest module, an active patients module, a simplify fulfillment module, and a deliver support module. Experience layer 420 may include a patient and HCP omni-channel module, a patients and HCP self service module, and a contact center. API layer 430 may include one or more connections including, but not limited to, copay, pharmacy look up, eBV, payment, transfer, ePA, partner pharmacies. Systems layer 440 may include an audience, journey and campaign management module, a patient CRM module, a digital intake pharmacy module, a telehealth module, an Ez button, digital front door, self-assessment module, a specialist finder module, a patient community module, and an eBV and ePV module. Al layer 450 may include an Al optimization layer and an Al personalization layer. Data and analysis layer 460 may include access one or more data repositoriesAttorney Docket No.: 00401-0002-00304 including, but not limited to, new patient identification and end-to-end funnel tracking and dashboards.

[0061] FIG. 5 depicts an exemplary system overview, according to one or more embodiments. DTP platform architecture 500 may include identification and engagement 510, HCP visit and prescription 520, prescription coverage and dispensing 530, patient support and adherence 540, digital concierge 550, and engagement and optimization 560. Identification and engagement 510 may include one or more components, including but not limited to, patient communities, new- patient finding, self-diagnosis tools, agency omni-channel marketing, targeted media campaign, reporting and analytics, digital assets and modular content, and deployment.

[0062] HCP visit and prescription 520 may include one or more components, including but not limited to, telehealth screening, telehealth visit to prescription, HCP and specialist finder, and medical affairs. Prescription coverage and dispensing 530 may include one or more components, including but not limited to, benefits and verification, prior authorization, copay support, deployment, specialty pharmacy, retail pharmacy integration, payment collection, gross-to-net optimization, dispensing, ship to patient, HCP or facility, nurse and home dispensing, and compliance. Patient support and adherence 540 may include one or more components, including but not limited to, patient onboarding, patient services support, refills and adherence, and continuous coaching.

[0063] FIG. 6 depicts an exemplary patient prescription flowchart, according to one or more embodiments. Digital intake pharmacy flowchart 600 may include HCP and patient consult 610, prescription information 620, pharmacy workflow 630, patient application and engagement 640, patient options 650, and delivery and payment 660.

[0064] FIG. 7 depicts an exemplary patient intake flowchart, according to one or more embodiments. Digital intake and patient engagement flowchart 700 may include awareness 710, e-prescriptions 720, intake 730, verification 740, engage 750, triage 760, dispense 770, and therapy 780. Awareness 710 may include access to product hub infused within the HCP workflow to encourage e-prescriptions 720. Awareness may include patients having access to telehealth prescribers. E- prescription 720 may include an HCP writing an e-prescription to connect the patient with one or more pharmacies. Intake 730 may include a digital intake process toAttorney Docket No.: 00401-0002-00304 automatically capture patient information from the e-prescription as written in e- prescription 720.

[0065] Verification 740 may include an automated system to complete eBV in real-time or substantially real-time. eBV may be completed within minutes and with a high accuracy (e.g., approximately 90%). Engage 750 may include a digital concierge that engages with a patient via one or more communication services (e.g., SMS, email, telecommunications, etc.). Engage 750 may provide one or more of consent, enroll in copay or PAP, select a preferred pharmacy, or enter payments. Triage 760 may prioritize prescriptions for the next best action. Dispense 770 may ensure fulfillment of the prescription to the appropriate pharmacy in response to the prioritization of the prescription. Therapy 780 may include a faster starting date for a patient to enroll in therapy to support each patient through their respective journey.

[0066] FIG. 8A and FIG. 8B depict exemplary user interfaces, according to one or more embodiments. Interface 810 may include the initial interface for a new patient to register and / or opt-in to one or more resources within the DTP platform. The patient may be presented with a series of interfaces to create a patient profile and select user settings for the associated patient profile. Interface 820 may include one or more benefits verification interface. Interface 820 may include a series of interfaces displaying benefit information relating to the patient profile and associated insurance coverage. Interface 830 may include one or more pharmacies available for selection and use by the DTP platform in fulfilling each prescription for the patient. The patient may select one or more based on the services and compounds provided by each pharmacy. Interface 840 may include a copay offer and wallet display. Interface 850 may include an Al and / or live messaging feature. For example, a patient may wish to discuss certain details of a prescription or benefit with customer support. The customer support may be a combination of Al and live personnel with the ability to assist each patient and respective needs. Interface 860 may include one or more reminder and / or notifications to be displayed to the patient. For example, a user may be notified via email or SMS when a prescription is available for pickup or when a prescription has been approved.

[0067] FIG. 9 depicts a flow diagram for training a machine-learning model, according to one or more embodiments. As shown in flow diagram 900, training data 912 may include one or more of stage inputs 914 and known outcomes 918 related to a machine learning model to be trained. The stage inputs 914 may be from anyAttorney Docket No.: 00401-0002-00304 applicable source including a component or set shown in the figures provided herein. The known outcomes 918 may be included for machine learning models generated based on supervised or semi-supervised training. An unsupervised machine learning model might not be trained using known outcomes 918. Known outcomes 918 may include known or desired outputs for future inputs similar to or in the same category as stage inputs 914 that do not have corresponding known outputs.

[0068] The training data 912 and a training algorithm 920 may be provided to a training component 930 that may apply the training data 912 to the training algorithm 920 to generate a trained machine learning model 950. According to an implementation, the training component 930 may be provided comparison results 916 that compare a previous output of the corresponding machine learning model to apply the previous result to re-train the machine learning model. The comparison results 916 may be used by the training component 930 to update the corresponding machine learning model. The training algorithm 920 may utilize machine learning networks and / or models including, but not limited to a deep learning network such as Deep Neural Networks (DNN), Convolutional Neural Networks (CNN), Fully Convolutional Networks (FCN) and Recurrent Neural Networks (RCN), probabilistic models such as Bayesian Networks and Graphical Models, and / or discriminative models such as Decision Forests and maximum margin methods, or the like. The output of the flow diagram 900 may be a trained machine learning model 950.

[0069] A machine learning model disclosed herein may be trained by adjusting one or more weights, layers, and / or biases during a training phase. During the training phase, historical or simulated data may be provided as inputs to the model. The model may adjust one or more of its weights, layers, and / or biases based on such historical or simulated information. The adjusted weights, layers, and / or biases may be configured in a production version of the machine learning model (e.g., a trained model) based on the training. Once trained, the machine learning model may output machine learning model outputs in accordance with the subject matter disclosed herein. According to an implementation, one or more machine learning models disclosed herein may continuously update based on feedback associated with use or implementation of the machine learning model outputs.

[0070] It should be understood that aspects in this disclosure are exemplary only, and that other aspects may include various combinations of features from other aspects, as well as additional or fewer features.Attorney Docket No.: 00401-0002-00304

[0071] In general, any process or operation discussed in this disclosure that is understood to be computer-implementable, such as the processes illustrated in the flowcharts disclosed herein, may be performed by one or more processors of a computer system, such as any of the systems or devices in the exemplary environments disclosed herein, as described above. A process or process step performed by one or more processors may also be referred to as an operation. The one or more processors may be configured to perform such processes by having access to instructions (e.g., software or computer-readable code) that, when executed by the one or more processors, cause the one or more processors to perform the processes. The instructions may be stored in a memory of the computer system. A processor may be a central processing unit (CPU), a graphics processing unit (GPU), or any suitable types of processing unit.

[0072] A computer system, such as a system or device implementing a process or operation in the examples above, may include one or more computing devices, such as one or more of the systems or devices disclosed herein. One or more processors of a computer system may be included in a single computing device or distributed among a plurality of computing devices. A memory of the computer system may include the respective memory of each computing device of the plurality of computing devices.

[0073] FIG. 10 depicts an exemplary computing device, according to one or more embodiments. FIG. 10 is a simplified functional block diagram of a computer 1000 that may be configured as a device for executing the methods disclosed here, according to exemplary aspects of the present disclosure. For example, the computer 1000 may be configured as a system according to exemplary aspects of this disclosure. In various aspects, any of the systems herein may be a computer 1000 including, for example, a data communication interface 1020 for packet data communication. The computer 1000 also may include a central processing unit (“CPU”) 1002, in the form of one or more processors, for executing program instructions. The computer 1000 may include an internal communication bus 1008, and a storage unit 1006 (such as ROM, HDD, SDD, etc.) that may store data on a computer readable medium 1022, although the computer 1000 may receive programming and data via network communications 1025.

[0074] The computer 1000 may also have a memory 1004 (such as RAM) storing instructions 1024 for executing techniques presented herein, for example theAttorney Docket No.: 00401-0002-00304 flowcharts described with respect to FIGS. 4-6, although the instructions 1024 may be stored temporarily or permanently within other modules of computer 1000 (e.g., processor 1002 and / or computer readable medium 1022). The computer 1000 also may include input and output ports 1012 and / or a display 1010 to connect with input and output devices such as keyboards, mice, touchscreens, monitors, displays, etc. The various system functions may be implemented in a distributed fashion on a number of similar platforms, to distribute the processing load. Alternatively, the systems may be implemented by appropriate programming of one computer hardware platform.

[0075] Program aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of executable code and / or associated data that is carried on or embodied in a type of machine-readable medium. “Storage” type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives, and the like, which may provide non-transitory storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer or processor into another, for example, from a management server or host computer of the mobile communication network into the computer platform of a server and / or from a server to the mobile device. Thus, another type of media that may bear the software elements includes optical, electrical, and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links. The physical elements that carry such waves, such as wired or wireless links, optical links, or the like, also may be considered as media bearing the software. As used herein, unless restricted to non-transitory, tangible “storage” media, terms such as computer or machine “readable medium” refer to any medium that participates in providing instructions to a processor for execution.

[0076] While the disclosed methods, devices, and systems are described with exemplary reference to transmitting data, it should be appreciated that the disclosed aspects may be applicable to any environment, such as a desktop or laptop computer, an automobile entertainment system, a home entertainment system, etc. Also, the disclosed aspects may be applicable to any type of Internet protocol.Attorney Docket No.: 00401-0002-00304

[0077] It should be appreciated that in the above description of exemplary aspects of the invention, various features of the invention are sometimes grouped together in a single aspect, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed aspect. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate aspect of this invention.

[0078] Furthermore, while some aspects described herein include some but not other features included in other aspects, combinations of features of different aspects are meant to be within the scope of the invention, and form different aspects, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed aspects can be used in any combination.

[0079] Thus, while certain aspects have been described, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Operations may be added or deleted to methods described within the scope of the present invention.

[0080] The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other implementations, which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. While various implementations of the disclosure have been described, it will be apparent to those of ordinary skill in the art that many more implementations are possible within the scope of the disclosure. Accordingly, the disclosure is not to be restricted except in light of the attached claims and their equivalents.

Claims

Attorney Docket No.: 00401-0002-00304CLAIMSWhat is claimed is:1 . A method comprising: receiving, by one or more computing devices, patient information; generating, by the one or more computing devices, identifiable patient information and de-identifiable patient information, using the patient information; aggregating, by the one or more computing devices, the identifiable patient information and the de-identifiable patient information; transmitting, by the one or more computing devices, the de-identifiable patient information to a direct-to-patient platform; determining, by the one or more computing devices, one or more of a status or an association for the de-identifiable patient information; and displaying, by the one or more computing devices, one or more prescription services, based on the one or more of the status or the association.

2. The method of claim 1 , wherein the patient information include one or more of a patient profile, a patient insurance coverage, or a prescription.

3. The method of claim 1 , further comprising: verifying, by the one or more computing devices, prescription benefits, in response to receiving the patient information.

4. The method of claim 1 , further comprising: prioritizing, by the one or more computing devices, a pharmacy selection in response to determining one or more of the status and the association for the patient information.

5. The method of claim 1 , further comprising: tracking, by the one or more computing devices, an end-to-end patient journey using one or more of the status, the identifiable patient information, or the de-identifiable patient information.

6. The method of claim 5, further comprising:Attorney Docket No.: 00401-0002-00304 generating, by the one or more computing devices, a dashboard displaying the end-to-end patient journey, wherein the end-to-end patient journey includes one or more status indicators associated with one or more operations in the end-to-end patient journey.

7. The method of claim 1 , further comprising: notifying, by the one or more computing devices, a patient during a pharmacy selection indicating product inventory availability at one or more pharmacies.

8. The method of claim 1 , wherein displaying the one or more prescription services includes providing a plurality of pharmacy options to a patient device, the plurality of pharmacy options including one or more of a specialty pharmacy, a retail pharmacy, or a digital pharmacy.

9. A system comprising: a patient experience layer configured to receive information via an application programming interface (API) layer; a components layer configured to interact with the patient experience layer via the API layer; an artificial intelligence (Al) layer configured to optimize and personalize a patient experience in response to the received information in the patient experience layer; and an analytics layer configured to track and store the received information and display a dashboard to a patient via a patient device.

10. The system of claim 9, wherein the patient experience layer includes one or more of a patient omni-channel, a patient self-service channel, or a contact center channel.

11. The system of claim 9, wherein the components layer includes a plurality of sub-components, wherein the plurality of sub-components include one or more of an audience management module, a journey management module, a campaign management module, a patient customer relationship management module, a digital intake pharmacy module, a telehealth module, a self-assessmentAttorney Docket No.: 00401-0002-00304 module, a specialist finder module, a patient community module, an electronic benefits verification module, or an electronic prior authorization module.

12. The system of claim 9, wherein the API layer is configured to provide one or more connections including one or more of a copay verification, a pharmacy lookup, an electronic benefits verification, a payment processing, a prescription transfer, an electronic prior authorization, or a partner pharmacy integration.

13. The system of claim 9, wherein the analytics layer is configured to identify one or more new patients and provide tracking information associated with each of the one or more new patients throughout a patient journey.

14. The system of claim 9, further comprising: one or more memories storing instructions associated with the patient experience layer, the components layer, the Al layer, and the analytics layer; and one or more processors configured to execute the instructions.

15. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving patient information; generating identifiable patient information and de-identifiable patient information, using the patient information; aggregating the identifiable patient information and the de-identifiable patient information; transmitting the de-identifiable patient information to a direct-to-patient platform; determining one or more of a status or an association for the de-identifiable patient information; and displaying one or more prescription services, based on the one or more of the status or the association.

Images