System and methods for recording medical evaluations and dispensing on-site incentives

The system integrates health record connectivity and automated incentives to address underutilization and education gaps in perinatal care, enhancing patient engagement and health outcomes through gamified rewards and personalized timelines.

WO2026236334A1PCT designated stage Publication Date: 2026-11-12TEMPLE UNIVERSITY HEALTH SYSTEM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/026863
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing digital health applications fail to integrate electronic health record connectivity and automated incentive-based reward systems, leading to underutilization of perinatal medical services and lack of education, which contributes to poor health outcomes for birthing parents and their infants.

Method used

A system that integrates a client device, provider device, health record server, timeline analysis server, and distribution server to record medical evaluations, dispense incentives, and provide personalized health education, using gamification principles to encourage timely medical appointments and education through a unified, automated system.

Benefits of technology

Enhances patient engagement and adherence to medical appointments and education, reducing preventable health complications and improving health outcomes by leveraging behavioral reinforcement principles and dynamic reward adjustments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026026863_12112026_PF_FP_ABST
    Figure US2026026863_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A system includes a provider device, a health record server, a timeline analysis server, and a distribution server. The system receives at the health record server a patient appointment report from the provider device, the patient appointment report including a health outcome of a patient. The system determines a patient appointment code based upon the patient appointment report. The system retrieves a timeline code from a patient timeline associated with the patient. The timeline code is associated with the patient appointment code and the patient timeline. The system selects a reward from a reward list. The reward is selected based upon the timeline code and the health outcome. The system dispenses the reward to the patient.
Need to check novelty before this filing date? Find Prior Art

Description

Attorney Docket No. H5776-00070SYSTEM AND METHODS FOR RECORDING MEDICAL EVALUATIONS AND DISPENSING ON-SITE INCENTIVESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 801,532, filed May 7, 2025, the entire contents of which are incorporated herein by reference.TECHNICAL FIELD

[0002] The present disclosure relates to recording medical evaluations, including biometric measurements during pregnancy and the perinatal period of a patient and the neonatal period of their child, and automatically determining and transferring or dispensing incentives or rewards to that patient based upon medical evaluation-related data.BACKGROUND

[0003] Perinatal healthcare systems are designed to provide critical care to birthing patients, with hospitals serving as the primary institutions for delivering these services. In many regions, the majority of births occur in hospitals, and healthcare providers, policymakers, and communities work together to improve access to high-quality, equitable perinatal care. However, significant challenges persist that undermine the effectiveness of these systems, particularly the underutilization of medical services and a lack of pregnancy-specific knowledge in pregnant patients. These two issues, while distinct, both contribute to the same overarching consequences: poor health outcomes for birthing parents and their infants.

[0004] One of the key barriers to optimal perinatal care is the underutilization of standard medical services. Some pregnant patients fail to attend their perinatal medical appointments, delaying critical screenings, tests, and treatments. There are several factors that contribute to this issue, such as socioeconomic challenges, limited access to healthcare facilities, lack of transportation, cultural or language barriers, and mental health concerns. These factors can prevent pregnant patients from seeking care at the recommended intervals, which, in turn, exacerbates health risks during pregnancy and the postpartum period.

[0005] Social Determinants of Health (SDoH) challenges compound these barriers. In theAttorney Docket No. H5776-00070United States, twenty-nine percent of pregnant women experience pre-pregnancy obesity, hypertensive disorders in pregnancy affect one in seven hospital deliveries, and cases of gestational diabetes rose by thirty percent from 2016 to 2020. Additionally, one in five women are affected by maternal mental health conditions, and people with mental health disorders experience fifty percent higher rates of Severe Maternal Morbidity (SMM). Mental health conditions are identified as a leading driver of increased costs related to maternal health complications. These overlapping risk factors — when coupled with housing instability, food insecurity, transportation access limitations, and chronic stress — contribute to difficulty accessing and attending critical care appointments and increase the risk of adverse outcomes for both the birthing parent and the child.

[0006] Alongside underutilization of medical services, there is a significant gap in education about both pregnancy and neonatal care. Many pregnant people lack the necessary knowledge to manage their own health and understand the needs of their newborns. This lack of education regarding prenatal care, potential complications, and neonatal needs can lead to preventable delays in seeking medical attention or neglecting necessary health behaviors. Inadequate education also means that many pregnant people are ill-equipped to make informed decisions about lifestyle choices, early warning signs of complications, or the importance of postnatal care for both themselves and their child.

[0007] Although these issues — underutilization of services and lack of information — can be distinct, they are ultimately linked and feed into the same negative outcomes. The failure to attend medical appointments often stems from a lack of understanding about their importance or the risks of not following medical advice. Similarly, the lack of education about pregnancy and neonatal care can contribute to the underutilization of available services, as women may not be aware of what care is needed or how to access it. Both factors significantly increase the risk of child and parental morbidity and mortality, with many complications remaining undetected or untreated.

[0008] Existing digital health applications directed to pregnancy tracking and support — including consumer-facing mobile applications offering week-by-week pregnancy milestones, appointment tracking, baby size comparison visuals, and rotating educational articles — do not provide integrated electronic health record connectivity or automated incentive-based reward systems tied to clinical engagement behaviors. These applications generally operate as standalone informational tools, available for direct download by consumers, that areAttorney Docket No. H5776-00070disconnected from the patient’s actual clinical care pathway and do not address the underlying motivation gap that contributes to underutilization of perinatal medical services.

[0009] The consequences of underutilizing medical services and lacking information are far-reaching. Health complications such as hypertension, diabetes, and infections can worsen without proper prenatal care, leading to more severe outcomes for both the birthing parent and the child. Mental health issues, including substance use disorder, are increasingly identified as leading causes of pregnancy-associated deaths, which are especially prevalent during the postpartum period. In certain regions, over 60% of pregnancy-associated deaths occur more than 43 days after delivery. This underutilization of care, combined with the lack of education on the long-term health needs of birthing parents and their children, directly contributes to preventable death and illness.

[0010] In certain regions, the rate of Severe Maternal Morbidity (SMM) has increased an average of seven percent annually, underscoring the urgency of continuous monitoring and targeted interventions. Mental health conditions — including perinatal depression, anxiety, and substance use disorder — are increasingly identified as leading causes of pregnancy-associated mortality. In some populations, people with mental health disorders experience fifty percent higher rates of SMM compared to the general perinatal population. These trends confirm that systems which encourage timely prenatal attendance, facilitate ongoing education, and monitor patient engagement may reduce the incidence of preventable complications during and after pregnancy.

[0011] These issues also carry significant financial costs. When pregnant patients do not fully utilize available services or lack proper education about their health, they tend to experience complications that require emergency care, hospitalization, and long-term treatment. The increased incidence of perinatal morbidity and mortality places a strain on healthcare systems, raises medical costs, and burdens communities.

[0012] Addressing these challenges requires a multi-faceted approach that tackles both the underutilization of services and the lack of education. It is essential to improve not only hospital-based care but also the coordination between obstetricians, primary care providers, and behavioral health specialists.

[0013] Therefore, there is a long-felt but unsolved need for systems and methods of promoting better utilization of perinatal and neonatal health care. Encouraging personal healthAttorney Docket No. H5776-00070education and incentivizing prudent health decision-making is needed to ensure that pregnant patients understand the importance of attending medical appointments and the impact of their health behaviors on their pregnancy and neonatal outcomes.

[0014] The background description provided here is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.SUMMARY

[0015] A system for recording medical evaluations and dispensing incentives includes a client device associated with a patient, a provider device, a health record server, a timeline analysis server, a distribution server, and programming. Execution of the programming by one or more processors of the system can configure the system to perform the following functions. The system receives at the health record server via the provider device a patient appointment report. The patient appointment report includes a health outcome of the patient. The system determines a patient appointment code based upon the patient appointment report. The system retrieves a timeline code from a patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient. The system selects a reward from a reward list. The reward is selected based upon the timeline code and the health outcome. The system dispenses the reward from the distribution server to the patient.

[0016] In some embodiments, the reward includes a numerical point value. The system increments a point total associated with the patient by the numerical point value. The system selects a tiered reward from a tiered reward list, the tiered reward selected based upon the point total. The system dispenses the tiered reward from the distribution server to the patient.

[0017] In some embodiments, the system receives via the provider device an onboarding report. The system modifies the patient timeline based upon the onboarding report.

[0018] In some embodiments, the system receives, via the provider device, a major event report. The system, based on the major event report, produces a parent timeline and a child timeline. The system receives, via the provider device, a child appointment report. The child appointment report includes a child health outcome of a child of the patient. The systemAttorney Docket No. H5776-00070determines a child appointment code based upon the child appointment report. The system retrieves a child timeline code from the child timeline. The child timeline code is associated with the child appointment code, and the child timeline associated with the patient. The system selects a child reward from the reward list. The child reward is selected based upon the child timeline code and the child health outcome. The system dispenses the child reward from the distribution server to the patient.

[0019] In a subset of those embodiments, the system retrieves a parent timeline code from the parent timeline. The parent timeline code is associated with the appointment code, and the parent timeline associated with the patient. The system selects a parent reward from the reward list, the parent reward selected based upon the parent timeline code and the health outcome. The system dispenses the parent reward from the distribution server to the patient.

[0020] In a different or overlapping subset of those embodiments, based on receiving the major event report, the system starts a redemption countdown. Based on an expiration of the redemption countdown, the system retracts the reward.

[0021] In some embodiments, the health outcome is obtained by a biometric sensor of the provider device. The patient appointment report is transmitted in response to the health outcome being obtained by the biometric sensor.

[0022] In some embodiments, the distribution server includes a product dispenser. The reward is dispensed when the product dispenser is proximate to the client device.

[0023] In some embodiments, after selecting the reward from the reward list, the system sends a reward notification to the client device. The system sends a reward confirmation from the client device to the distribution server. In response to receiving the reward confirmation, the system dispenses the reward from the distribution server to the patient.

[0024] In some embodiments, the system transmits a patient educational lesson to the client device. The system presents the patient educational lesson on the client device. The system presents a patient educational assessment on the client device. The system transmits a patient educational assessment outcome based on the patient educational assessment. The system selects an educational reward from the reward list, the educational reward selected based upon the patient educational assessment outcome. The system dispenses the educational reward from the distribution server to the patient.Attorney Docket No. H5776-00070

[0025] In some embodiments, the system transmits a scheduling request from the client device. The scheduling request is associated with a scheduling code from the patient timeline. The system selects a scheduling reward from the reward list. The scheduling reward is selected based upon the scheduling request. The system dispenses the scheduling reward from the distribution server to the patient.

[0026] In a subset of those embodiments, the system receives from the provider device an absence report. The absence report is associated with the scheduling request. Based on the absence report, the system retracts the scheduling reward.

[0027] In some embodiments, the system generates the patient timeline based on the patient appointment report via a machine learning model. The system trains the machine learning model based upon the patient timeline, the patient appointment report, and the reward, thereby producing a revised machine learning model. The system generates an additional patient timeline based on an additional patient appointment report via the revised machine learning model. The additional patient timeline is unequal to the patient timeline.

[0028] A method can include receiving, at a health record server, a patient appointment report, the patient appointment report including a health outcome of a patient. The method can include determining a patient appointment code based upon the patient appointment report. The method can include retrieving a timeline code from a patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient. The method can include selecting a reward from a reward list, the reward selected based upon the timeline code and the health outcome. The method can include dispensing the reward to the patient.

[0029] In some embodiments, the method can include receiving, at the health record server, a major event report. The method can include, based on the major event report, producing a parent timeline and a child timeline. The method can include receiving a child appointment report, the child appointment report including a child health outcome of a child of the patient. The method can include determining a child appointment code based upon the child appointment report. The method can include retrieving a child timeline code from the child timeline, the child timeline code associated with the child appointment code and the child timeline associated with the patient. The method can include selecting a child reward from the reward list, the child reward selected based upon the child timeline code and the child healthAttorney Docket No. H5776-00070outcome. The method can include dispensing the child reward to the patient.

[0030] In a subset of those embodiments, the method can include retrieving a parent timeline code from the parent timeline. The parent timeline code is associated with the appointment code, and the parent timeline associated with the patient. The method can include selecting a parent reward from the reward list. The parent reward is selected based upon the parent timeline code and the health outcome. The method can include dispensing the parent reward to the patient.

[0031] In some embodiments, the health outcome is obtained by a biometric sensor of a provider device. Additionally, the patient appointment report is transmitted in response to the health outcome being obtained by the biometric sensor.

[0032] In some embodiments, the method can include transmitting a patient educational lesson to the patient. The method can include transmitting a patient educational assessment to the patient. The method can include receiving a patient educational assessment outcome based on the patient educational assessment. The method can include selecting an educational reward from the reward list. The educational reward is selected based upon the patient educational assessment outcome. The method can include dispensing the educational reward to the patient.

[0033] In some embodiments, the method can include incrementing a point total associated with the patient by a numerical point value associated with the reward. The method can include selecting a tiered reward from a tiered reward list, the tiered reward selected based upon the point total. The method can include dispensing the tiered reward to the patient.

[0034] A non-transitory computer-readable medium can store instructions. The instructions are executable by a processor to perform a method. The method can include receiving, at a health record server, a patient appointment report, the patient appointment report including a health outcome of a patient. The method can include determining a patient appointment code based upon the patient appointment report. The method can include retrieving a timeline code from a patient timeline. The timeline code is associated with the patient appointment code, and the patient timeline associated with the patient. The method can include selecting a reward from a reward list, the reward selected based upon the timeline code and the health outcome. The method can include dispensing the reward to the patient.Attorney Docket No. H5776-00070BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The present disclosure will become more fully understood from the detailed description and the accompanying drawings.

[0036] FIG. 1 illustrates an example networked computer system in which various embodiments may be practiced.

[0037] FIGS. 2A-2C illustrate example screens of a points tracker associated with earned rewards for medical initiatives.

[0038] FIGS. 3 A-3B illustrate example screens of an alternative points tracker dispensing tiered rewards, and a scheduled task activity tracker dispensing points rewards.

[0039] FIG. 4 illustrates an example screen of a scheduled educational content library dispensing points rewards.

[0040] FIG. 5 illustrates an example process performed by a computer application server in accordance with disclosed embodiments.

[0041] FIG. 6 illustrates a computer system upon which various embodiments may be implemented.DETAILED DESCRIPTION OF THE DRAWINGS

[0042] This description of the exemplary embodiments is intended to be read in connection with the accompanying drawings, which are to be considered part of the entire written description. The use of the singular includes the plural unless specifically stated otherwise. The use of “or” means “and / or” unless stated otherwise. Furthermore, the use of the term “including,” as well as other forms such as “includes” and “included,” is not limiting. In addition, terms such as “element” or “component” encompass both elements and components comprising one unit, and elements and components that comprise more than one subunit, unless specifically stated otherwise. Additionally, the section headings used herein are for organizational purposes only, and are not to be construed as limiting the subject matter described. Numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In otherAttorney Docket No. H5776-00070instances, well known methods, procedures, components, and / or circuitry have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.

[0043] The following description is provided as an enabling teaching of a representative set of examples. Many changes can be made to the embodiments described herein while still obtaining beneficial results. Some of the desired benefits discussed below can be obtained by selecting some of the features discussed herein without utilizing other features. Accordingly, many modifications and adaptations, as well as subsets of the features described herein are possible and can even be desirable in certain circumstances. Thus, the following description is provided as illustrative and is not limiting.

[0044] The term “coupled” as used herein refers to any logical, optical, RF, physical, or electrical connection, link or the like by which signals produced or supplied by one system element are imparted to another coupled element. Unless described otherwise, coupled elements or devices are not necessarily directly connected to one another and may be separated by intermediate components, elements or communication media that may modify, manipulate, or carry the signals.

[0045] Reference now is made in detail to the examples illustrated in the accompanying drawings and discussed below.

[0046] A system for recording medical evaluations and dispensing on-site incentives is disclosed. The system may be programmed to receive medical evaluations regarding medical patients. The medical evaluations may be collected at medical appointments, such as checkups, meetings, scheduled lab work, or imaging tests. The patient may be onboarded to the system, and provided a recommended itinerary of medical evaluations in order to improve their medical outcomes, as well as the medical outcomes of their children. The system can, in some cases, schedule medical evaluations for the patient, and in other cases encourages the patient to schedule the recommended medical evaluations on their itinerary.

[0047] An electronic health record (EHR) server may be configured to receive the medical evaluation information, as well as data regarding whether the patient attended their scheduled medical evaluation as health outcomes of the intended subject of the medical evaluation. The EHR server can also receive the content and notes from the medical evaluation itself. The medical evaluation, scheduling, and attendance information is transmitted to anAttorney Docket No. H5776-00070analysis server, which determines associations between the recommended itinerary of medical evaluations, and the actual scheduling and attendance of medical evaluations. Health outcomes for a patient can include their medical evaluation, scheduling, and attendance information. When a recommended medical evaluation is scheduled, a reward can be determined and provided to the patient. Later, when the recommended evaluation actually occurs, an additional reward can be provided to the patient. The rewards can gamify the process of scheduling and attending recommended medical evaluations for the patient. Gamification has been identified as a highly effective method of encouraging engagement, motivation, and participation. Gamification can also make tasks, such as attending doctor’s appointments, more enjoyable and can drive improved behavior going forward.

[0048] The reward mechanisms disclosed herein may implement established behavioral reinforcement principles recognized in the fields of behavioral economics and health psychology. The tiered reward structure may leverage the goal gradient effect, wherein individuals increase effort expenditure as they perceive proximity to a goal — as reflected in the tier proximity messaging described herein (e.g., ‘You’re only 200 points away from reaching the next tier’). The redemption countdown and reward retraction mechanism may leverage loss aversion, a well-documented cognitive bias wherein the psychological impact of losing an earned benefit exceeds the impact of gaining an equivalent benefit, thereby motivating timely reward redemption and continued engagement. The dynamic reward adjustment — wherein reward values are increased for tasks the patient is recalcitrant in performing — may implement principles of variable ratio reinforcement, which behavioral research has established as producing the highest and most consistent response rates among reinforcement schedules. The combination of these behavioral principles within a unified, automated system distinguishes the disclosed gamification architecture from conventional static incentive programs that do not adapt to individual patient behavior.

[0049] The gamification strategy can be extended into other areas of patient health. A recommended library of educational materials regarding the patient’s health can be provided to the patient, and as the patient reviews the materials, additional rewards can be provided to the patient. The release of educational materials can be timed with the itinerary of medical evaluations, in order to supplement or prepare the patient for their evaluation. Alternatively, if a patient misses a medical examination, remedial educational materials can be provided to bolster the patient’s overall health outcomes in light of missing recommended medicalAttorney Docket No. H5776-00070evaluations.

[0050] The rewards in some cases can be abstract, such as “points” or numerical values stored in a database and presented to the patient in an attractive format, in order to energize the patient through their health journey. In certain embodiments, however, the rewards can be functional rewards, such as money or goods. For certain types of patients, for example pregnant patients managing their pregnancy, the functional rewards can be useful rewards with respect to their pregnancy or postpartum lives, such as diapers (both infant and adult), baby wipes, or prenatal vitamins. These functional rewards may be goods which patients typically need after their immediate clinical care concludes.

[0051] The system can particularly address the medical journey of pregnancy, postpartum, and neonatal care. The system can prepare a pregnancy and perinatal itinerary of medical evaluations, directed to helping the pregnant patient stay on-time and informed. The system, upon being notified of a live birth of a child from the patient, can generate both an itinerary of medical evaluations for the new infant child, as well as an itinerary of medical evaluations for the post-partum parent. The new generated timelines can help new patients navigate the medical care of their new child, while being supported in their own personal postpartum medical experiences.

[0052] In embodiments directed to pediatric care following a major event such as a live birth, the child timeline may include timeline codes associated with well-child visits recommended by applicable clinical guidelines, including visits scheduled at regular intervals through the first eighteen months of life. The child timeline may further include timeline codes associated with recommended vaccinations, enabling the system 100 to track and incentivize timely vaccine adherence. The client device 140 may present an interactive growth and development chart that integrates the child’ s health outcome data received via the health record server 120 — such as weight, length, and head circumference measurements — with age-appropriate developmental milestone education. The system 100 may further support neonatal intensive care unit (NICU) discharge preparation by providing educational materials and task records specific to post-NICU transitional care. The rewards associated with the child timeline may be designed to support Healthcare Effectiveness Data and Information Set (HEDIS) measures related to well-child visit frequency and vaccination timeliness.

[0053] The postpartum parent timeline may include timeline codes directed to mentalAttorney Docket No. H5776-00070health screening, postpartum physical recovery milestones, and lactation support, extending incentivized engagement through the fourth trimester and beyond. The system 100 may provide educational materials and task records addressing postpartum-specific health concerns, such as postpartum depression screening, pelvic floor recovery, and breastfeeding support, with associated rewards calibrated to encourage completion of these postpartum milestones.

[0054] In some embodiments, the system is configured to alternatively or additionally address different or non-pregnancy-related medical journeys for patients. For example, in some embodiments the system is configured to track timelines, medical evaluations, and present awards to patients suffering from cancer during their oncological care, including tracking chemotherapy infusion schedules, radiation therapy sessions, imaging follow-ups, and post-remission surveillance appointments. The oncological embodiment may include timeline codes associated with oncological CPT codes, and rewards calibrated to the intensity and duration of the treatment regimen. In some embodiments, the system is configured to track timelines, appointments, appointment attendance, and drug usage and records of patients suffering from addiction during addiction therapy and rehabilitation, including tracking counseling sessions, medication-assisted treatment (MAT) administration (e.g., methadone, buprenorphine, or naltrexone dosing), urinalysis schedules, and peer support group attendance. In some embodiments, the system is configured to track timelines, appointments, and appointment attendance for post-injury or post-surgery patients engaging in longitudinal physical therapy, including tracking physical therapy sessions, range-of-motion benchmarks, home exercise compliance, and post-operative imaging follow-ups. The system can be configured to address any multi-step medical issue, particularly those with patient-driven elements (e.g., non-state-compelled appointment attendance, off-site prescription drug administration, scheduled exercise, dietary compliance monitoring, etc.)

[0055] The system can be automated. The medical evaluations, after being documented at a medical care facility, can be sent to an EHR server. The medical evaluations can include data directly collected by medical imaging or scanning sensors and tools. The EHR server can transmit the relevant medical evaluation data to an analysis server, which then determines whether the patient is eligible for a reward. If the patient is eligible for a reward, particularly a physical or monetary reward, the patient may be granted a voucher, credit, or a permission to be dispensed the reward. A distribution server may manage the dispensation of the reward, and can either automatically order the reward to be delivered to the patient, using logisticsAttorney Docket No. H5776-00070software and equipment, or instruct an automated self-service dispensing machine or point-of-sale (POS) device to release or permit the release of the identified reward to the patient. System automation can improve the cost-effectiveness and general efficiency of the system, and can lead to higher patient conformance and reward redemption.

[0056] The technical architecture of the system 100 provides specific improvements to the functioning of the computer system itself and to the field of healthcare informatics. The system 100 addresses the technical problem of coordinating real-time data flows between heterogeneous healthcare computing systems, including EHR databases, biometric sensor arrays, machine learning inference engines, and automated dispensing hardware, to produce a unified, patient-specific timeline that dynamically adapts based on incoming clinical data. Unlike conventional reminder or loyalty systems that merely store and retrieve static schedules, the system 100 may be configured to implement a closed-loop feedback architecture in which biometric sensor data captured at the provider device 110 triggers automated appointment code classification (including via LLM inference), dynamic timeline recalculation at the timeline analysis server 102, real-time reward selection, and proximity -based physical dispensation at the distribution server 130 — all without manual intervention. This integrated pipeline reduces network round-trips, eliminates manual data re-entry across systems, and enables sub-second reward determination that would not be achievable through manual or semi-automated processes. The system 100 further provides the technical improvement of adaptively retraining its machine learning model based on multivariate feedback signals (appointment attendance, reward redemption, health outcomes) to generate personalized timelines that demonstrably differ from default timelines, thereby improving both computational efficiency (by focusing system resources on high-impact interventions) and clinical data integrity (by reducing data staleness in the patient timeline).

[0057] The system can include a notification element. Notifications can be sent to the patient or the personal computing device of the patient to inform the patient of their itinerary of medical evaluations, recommended library of educational materials, scheduled appointments, and non-clinical medical tasks, such as exercise, stretching, and consumption of supplements, vitamins, or prescription drugs. Notifications can also be sent to encourage, uplift, or otherwise improve the mental health of the patient, for the purpose of improving mental health, or the purpose of inducing improved conformance with the medical evaluation itinerary or reading the recommended library.Attorney Docket No. H5776-00070

[0058] In some embodiments, the notifications may be delivered to the client device 140 via platform-specific push notification services, such as Apple Push Notification service (APNs) for iOS devices or Firebase Cloud Messaging (FCM) for Android devices. The system 100 may maintain a device token or registration identifier for each client device 140, and the timeline analysis server 102 may transmit notification payloads to the appropriate push notification service for delivery to the patient’s registered device. Notification frequency and categories (e.g., appointment reminders, educational content availability, reward eligibility, motivational messaging) may be independently configurable by the patient via settings accessible on the client device 140, allowing the patient to opt in or opt out of specific notification categories while maintaining receipt of clinically significant notifications as determined by the system administrator or healthcare provider.

[0059] The system can adjust rewards. Rewards can be adjusted on an individual or group level. For example, rewards can be increased for tasks which the patient is relatively recalcitrant in performing, or for tasks which will have an outsized impact on the patient’s health. Rewards can also be adjusted based upon acceptance of rewards at a group level, and a managing organization’s reward budget. Rewards can also be adjusted based on a patient missing a task, and either reallocate points to or from the missed task to a make-up task, or increasing the total number of points to a subsequent or make-up task, to encourage the patient to make up the missed task. The individual rewards can be adjusted based on the attendance of the patient, or based on the health report of the patient. For example, a patient who is diagnosed with hypertension may have their rewards adjusted to encourage additional prenatal visits, or to encourage measuring and recording blood pressure in a non-clinical setting. Relatedly, the system can adjust the itinerary of medical evaluations, as well as the contents of the library of educational materials, based on similar incoming data.

[0060] In embodiments directed to patients with identified high-risk conditions, such as gestational hypertension or gestational diabetes, the system 100 may generate a modified patient timeline that includes additional timeline codes for more frequent prenatal visits, blood pressure monitoring tasks, glucose monitoring tasks, and targeted educational materials addressing the management of these conditions. The reward values associated with the additional timeline codes may be calibrated to reflect the heightened clinical importance of adherence for high-risk patients, and the educational library may be supplemented with condition-specific content, such as dietary guidance for gestational diabetes management orAttorney Docket No. H5776-00070blood pressure self-monitoring instructions for hypertensive patients. Early identification and monitoring of these conditions through the system 100 may reduce the risk of preterm delivery, prolonged labor and delivery, and neonatal intensive care unit admissions.

[0061] In some embodiments, the system 100 implements a dynamic rewards engine that adjusts reward selection and reward values based on the individual patient’s care goals, risk profile, and historical engagement data. For example, the dynamic rewards engine may analyze the patient’s appointment attendance history, educational lesson completion rates, and health outcome trajectory to identify specific areas of non-compliance or elevated clinical risk, and may increase the reward values associated with timeline codes targeting those identified areas. The dynamic rewards engine may operate in conjunction with the machine learning model described herein, using the model’s predictive output to prioritize reward allocation toward interventions with the highest predicted impact on the individual patient’s health outcomes and engagement trajectory.

[0062] The system can utilize machine learning to improve itineraries, libraries, and rewards, and to improve adjusting of itineraries, libraries, and rewards. In particular, because the system receives feedback in the form of appointment attendance data, educational material assessment data, and reward earning and redemption data, the system can retrain based on what rewards, and which notifications improved scheduling and attendance, and can retrain based on health reports what itineraries and libraries improved health outcomes.

[0063] FIG. 1 illustrates an example networked computer system 100 in which various embodiments may be practiced. It is shown in a simplified, schematic format for the purpose of illustrating a clear example. Other embodiments may include more, fewer, or different elements.

[0064] In some embodiments, the networked computer system 100 comprises a timeline analysis server (“server”) 102, a provider device 110, a health record server 120, a distribution server 130, and a client device 140, which are communicatively coupled through direct physical contact or via a network 118.

[0065] In some embodiments, the provider device 110 hosts and executes various computer applications, such as an electronic health record (EHR) practitioner portal for creating and updating medical records and medical scheduling records of medical patients serviced by the medical practice operating the provider device 110. The provider device 110Attorney Docket No. H5776-00070can be configured to communicate with the health record server 120 in storing EHR records created and updated by the provider device 110 in the health record server 120. The provider device 110 can also be configured to communicate with the client device 140 to receive appointment requests, medical-related messages and conversations, and to receive inpatient data and post-clinical updates. The provider device 110 can comprise a desktop computer, laptop computer, tablet computer, smartphone, server, or virtual server hosted on one or more physical servers. The provider device 110 can also be coupled to medical sensing or imaging equipment, including biometric sensors, and can include information, including derived or calculated information, from the medical sensing or imaging equipment in the medical records of the patient.

[0066] In some embodiments, the health record server 120 hosts and executes various computer applications, such as an EHR database for storing medical records and medical scheduling records of medical patients, including practitioners notes, test results, and biometric data. The provider device 110 can be configured to communicate with the timeline analysis server 102 to transmit EHR records, or portions of EHR records to the timeline analysis server 102 for processing. In some cases, the transmittal is first confirmed or authorized by the patient or the client device 140. The health record server 120 can comprise any computing facility with sufficient computing power in data processing, data storage, and network communication for performing the above-mentioned functions. In some embodiments, the health record server 120 is at least two servers, one which maintains particularly identified medical data, and a second which maintains supplementary medical data, such as medical imaging from an ultrasound machine or another diagnostic device.

[0067] In some embodiments, the health record server 120 may store supplementary patient data including medical imaging data, such as ultrasound images captured during prenatal appointments. The client device 140 may present to the patient the medical imaging data stored on the health record server 120, such as by retrieving and displaying ultrasound images associated with the patient’s record, sorted chronologically by the date the imaging data was received. The patient may browse the stored imaging data via the client device 140 to review prior diagnostic images.

[0068] In some embodiments, the health record server 120 comprises or is communicatively coupled to a commercially available electronic health record platform, such as Epic Systems’ MyChart patient portal or a similar EHR platform providing patient-facingAttorney Docket No. H5776-00070data access and clinical data exchange. In such embodiments, the health record server 120 may exchange patient appointment reports, health outcomes, and scheduling data with the timeline analysis server 102 via the EHR platform’s standard data exchange interfaces, such as Health Level Seven (HL7) or Fast Healthcare Interoperability Resources (FHIR) protocols.

[0069] In some embodiments, the timeline analysis server (“server”) 102 hosts and executes various computer applications, such as medical evaluation analysis, medical scheduling analysis, reward calculation and generation, and notification transmission to the client device 140. The server 102 can request or receive medical evaluations, including patient appointment and health record data. The server 102 in certain embodiments can also include a machine learning module for the purpose of preparing medical evaluation itineraries and medical education libraries, as well as improving and revising medical evaluation itineraries, medical education libraries, and rewards lists. The server 102 can comprise any computing facility with sufficient computing power in data processing, data storage, and network communication for performing the above-mentioned functions.

[0070] In some embodiments, the distribution server 130 hosts and executes various computer applications, such as reward redemption and dispensation applications. The distribution server 130 can receive commands to distribute rewards from the server 102, or can receive codes or key pairs, which upon subsequent presentation at the distribution server 130 or transmitted by the client device 140, results in the distribution of rewards. The distribution server 130 can also track reward tiers or budgets, for example tracking a certain number of credits or points required to obtain a particular tangible or monetary reward, as well as the number of credits or points associated with a patient. The distribution server 130 can be coupled to a self-service kiosk or dispensing machine, a POS system, including either a self-service or clerk assisted POS terminal, or an automated teller machine (ATM). The distribution server 130 can also be configured to interact with a blockchain implementation for the purpose of transferring associations of fungible or non-fungible tokens between token wallets. In such blockchain embodiments, the distribution server 130 may deploy or interact with one or more smart contracts on a distributed ledger (e.g., Ethereum, Polygon, or a permissioned enterprise blockchain such as Hyperledger Fabric), where each reward or tier achievement is recorded as an on-chain transaction. Fungible token rewards may be implemented as ERC-20-compatible tokens representing redeemable point balances, while non-fungible token rewards may be implemented as ERC-721 -compatible tokens representing unique achievement badges,Attorney Docket No. H5776-00070milestone certificates, or limited-edition reward vouchers. The distribution server 130 may manage a custodial wallet on behalf of the patient, or may interact with a non-custodial wallet application on the client device 140 via wallet-connect protocols. Token transfers may be triggered automatically upon reward selection by the timeline analysis server 102, with the distribution server 130 signing and broadcasting the transfer transaction to the blockchain network. The distribution server 130 can also be coupled to a financial institution, for the purpose of transferring funds between deposit accounts, or for funding or provisioning credit for transactions at the above listed terminals or machines. The distribution server 130 can also be coupled to an inventory system, and authorize or direct the logistical movement or transfer of reward inventory, which may additionally be facilitated by a transaction at a POS terminal. The inventory system can include non-generic inventory management tools, including inventory scanners, radio frequency identification (RFID) tags, or shelf sensors. The distribution can also be coupled to a radio receiver, such as Bluetooth, Wi-Fi, or Near-field communications (NFC) receiver, configured to communicate with or detect the client device 140 for reward distribution purposes.

[0071] In some embodiments, the client device 140 hosts and executes various computer applications, such as a web browser or compiled software directed to interact with the other elements of system 100. The client device 140 can be configured to communicate with the server 102 to communicate and prepare medical evaluation scheduling, receive educational material and return educational assessments, receive and respond to notifications, view and redeem rewards, and view data such as the medical evaluation itinerary or other screens as illustrated below. The client device 140 can comprise a desktop computer, laptop computer, tablet computer, smartphone, wearable device for performing interactions with the system 100 generally. In addition, the client device 140 can comprise a key, magnetic stripe card, RFID tag, NFC tag, integrated circuit card, or bank routing identifiers.

[0072] The network 118 may be implemented by any medium or mechanism that provides for the exchange of data between the various elements of FIG. 1. Examples of the network 118 include, without limitation, one or more of a cellular network, communicatively coupled with a data connection to the computing devices over a cellular antenna, a near-field communication (NFC) network, a Local Area Network (LAN), a Wide Area Network (WAN), or the Internet, a terrestrial or satellite link.

[0073] In some embodiments, the server 102, the provider device 110, the health recordAttorney Docket No. H5776-00070server 120, the distribution server 130, and the client device 140 can each be programmed to perform specific functions, as discussed in various embodiments herein. These functions can be implemented as software components, general or special-purpose hardware components, firmware components, or any combination thereof.

[0074] In some embodiments, the communications between the server 102, the provider device 110, the health record server 120, the distribution server 130, and the client device 140 are secured using industry-standard encryption protocols. Data in transit between the elements of system 100 may be encrypted using Transport Layer Security (TLS) version 1.2 or higher, and data at rest within the health record server 120 and the timeline analysis server 102 may be encrypted using Advanced Encryption Standard (AES) with a key length of at least 256 bits. Other protocols also may be used to encrypt data. Access to patient health information within the system 100 may be governed by role-based access control (RBAC), wherein each user account (e.g., patient, clinician, administrator) is assigned a role with a defined set of permissions, and access to protected health information (PHI) is restricted to the minimum necessary for the user’s role. The system 100 may maintain an audit log recording all access events, modifications, and transmissions involving PHI, including timestamps, user identifiers, and the nature of the access. For analytics and machine learning model training purposes, patient data may be de-identified in accordance with applicable regulations (e.g., the Health Insurance Portability and Accountability Act (HIPAA) Safe Harbor or Expert Determination methods) prior to inclusion in training datasets. The system 100 may further implement patient consent management functionality, wherein the patient may grant or revoke consent to specific data uses via the client device 140, and the system 100 enforces the patient’s consent preferences across all data processing operations.

[0075] FIGS. 2A-C illustrate example screens of a points tracker associated with earned rewards for medical initiatives. FIGS. 3A-B illustrate example screens of an alternative points tracker dispensing tiered rewards, and a scheduled task activity tracker dispensing points rewards. FIG. 4 illustrates an example screen of a scheduled educational content library dispensing points rewards.

[0076] In some embodiments disclosed herein, a patient account is onboarded into a clinical progression facilitation system, or system 100. In some embodiments, the clinical progression facilitation system facilitates successful pregnancies and postpartum care. The patient account can be created at the client device 140, at the provider device 110, and / or at anAttorney Docket No. H5776-00070administrative device (not shown). The patient account can be created in response to the patient discovering their pregnancy, or by a clinician diagnosing a pregnancy. The patient account can be associated with milestone tasks, or a patient timeline.

[0077] In some embodiments, the system 100 may award the patient an onboarding bonus upon creation of the patient account. For example, the patient may be awarded a predetermined number of bonus points (e.g., 500 points) upon completing the onboarding process, which are credited to the patient’s point total. The onboarding bonus may serve to establish initial engagement with the reward system and provide the patient with an immediate incentive to explore the system’s features, including the educational library, the care plan timeline, and the reward catalog. The onboarding bonus may be configurable by a system administrator or healthcare provider via the provider device 110.

[0078] The patient timeline includes timeline codes, which identify medical events, prescribed orders, or recommended tasks such as medical evaluations and education. The patient timeline can be a version of a default patient timeline, provided by the system 100 as a baseline patient timeline to each new patient account. The patient timeline can be measured in ordinal terms, such as days or weeks of pregnancy, or cardinal terms, such as calendar dates. The patient timeline can be updated or synced to measured medical data regarding the pregnancy of the patient, for example by determining a last recorded menstrual period for the patient and comparing to an expected last menstrual period based on the patient timeline, and shifting the patient timeline. The syncing of the patient timeline can also be performed based on physical measurements, such as dimensional measurements, of a fetus in the pregnancy of the patient. The patient timeline can also be personalized or customized. For example, the provider device 110 can upload to the system 100 a specific sequence of timeline codes, associated with specific pregnancy days or dates upon which the patient should perform the task associated with the timeline code. The patient timeline can be modified or added to, for example by the provider device 110, after the patient timeline is created. The patient timeline can include clinical events, which can be included among the medical events which are identified by timeline codes, as well as educational events or activities, which may or may not be associated with a timeline code, and may or may not be associated with a reward. Educational events can be tracked directly via the timeline analysis server 102 and the client device 140, and do not necessarily require interacting with the provider device 110 or the health record server 120 elements.Attorney Docket No. H5776-00070

[0079] In some embodiments, the syncing of the patient timeline based on a last recorded menstrual period may be performed using Naegele’s rule, wherein the estimated date of delivery is calculated by adding two hundred eighty days (forty weeks) to the first day of the patient’s last menstrual period. The timeline shift may be calculated as the difference between the previously estimated gestational age (based on the default patient timeline) and the revised gestational age (based on the confirmed last menstrual period), and all timeline codes may be shifted by that difference. When the syncing is based on physical measurements of the fetus, the system 100 or the provider device 110 may correlate first-trimester crown-rump length measurements to established gestational age reference tables (e.g., the Hadlock or Robinson growth curves) to determine a revised estimated gestational age, and the patient timeline may be adjusted accordingly. In some embodiments, the system 100 may reconcile conflicting gestational age estimates (e.g., when the last menstrual period date and the ultrasound measurements suggest different gestational ages) by selecting the estimate derived from the earliest ultrasound measurement, consistent with standard obstetric practice.

[0080] The timeline codes are codes, keys, or identifiers associated with known clinical tasks, such as medical evaluations, appointments, or classes. The timeline codes can include medical coding codes, such as the Healthcare Common Procedure Coding System (HCPCS) including the Current Procedural Terminology (CPT) codes, or the International Classification of Diseases (ICD) codes, or any code system which can be used as an index with the health record server 120. The educational events or activities can be associated with rewards in a similar manner to the clinical events or medical events, but may not require a specific timeline code, and can instead be tracked by an educational code. An educational code can be interchangeable with or indistinguishable from a timeline code, or an educational code can be tracked within the patient timeline, but not be associated with known clinical tasks, but rather educational tasks.

[0081] Once the patient timeline is created or uploaded to the system 100, the timeline analysis server 102 may associate rewards from a reward list with the timeline codes in the patient timeline. The association can be a default association, for example associating a specific reward with a specific timeline code. The association can also be personalized or customized, as well as modified or added to, by similar methods as the timeline codes.

[0082] As discussed above, rewards can be tangible or intangible, and virtual, monetary, or physical. The rewards are identified by a reward identifier, which can be associated with aAttorney Docket No. H5776-00070dispensation method or process at the distribution server 130. A single patient can be associated with multiple reward lists, which can function separately or in concert.

[0083] In some embodiments, a first reward list includes a list of points, which may be associated with particular timeline codes. A second, tiered reward list may include a list of tangible or useful rewards, such as reward identifiers associated with redemption of a box of infant diapers. In FIG. 2A, one example of a progress bar chart 205A is shown in an interface of the client device 140. The progress bar chart 205A depicts a total number of earned rewards from the first reward list. As the first reward list includes reward points as rewards, the reward points are depicted in the progress bar chart 205 A as a completed portion 210. The completed portion 210 includes rewards that have already been earned by the patient from the first reward list. The progress bar chart 205A includes a remaining portion 220. The remaining portion 220 can depict the remaining amount of rewards in the first reward list, can depict the remaining amount of rewards obtainable in the second, tiered reward list, or can depict an amount of rewards greater than the patient has earned, for example to motivate the patient to pursue additional rewards. The division between the completed portion 210 and the remaining portion 220 can be emphasized by a divider arrow 215.

[0084] The progress bar chart 205A-C also may include tier markers 225A-C. Tier markers 225A-C may indicate the amount of rewards from the first reward list required to earn a reward in the second, tiered reward list. In this example, tiers of the tiered reward list begin at zero, one thousand, two thousand, and three thousand points earned from the first reward list. It should be understood that the shape, content, and orientation of the progress bar chart 205A-C may be varied

[0085] By way of a non-limiting example, the tiers of the tiered reward list may be assigned descriptive names, such as ‘Jade,’ ‘Pearl,’ ‘Emerald,’ and ‘Diamond,’ with each tier associated with a respective point threshold (e.g., five hundred, one thousand seven hundred fifty, two thousand seven hundred fifty, and three thousand five hundred points). The descriptive tier names and associated point thresholds are configurable parameters of the system 100, and the specific names and values may be selected by a system administrator or managing organization to align with the engagement goals and reward budget of a particular clinical program. As a patient accrues points across the tiers, the client device 140 may display tier-specific congratulatory messaging (e.g., ‘Congratulations on completing the Jade tier. You are now a Pearl!’) and unlock access to progressively higher-value redemption options withinAttorney Docket No. H5776-00070the tiered reward list.

[0086] FIG. 2A also may include a descriptor box 255A. Descriptor box 255A may have a written description of some or all elements of the progress bar chart 205A (e.g., “Total Earned 800 Points”) and can also include additional text, such as explanatory text (“You’re only 200 points away from reaching the next tier”) or encouraging text (e.g., “Congratulations on successfully reaching Tier 2!”).

[0087] In FIG. 2B, the patient has earned more rewards in the first reward list, and the progress bar chart 205B has been updated. The divider arrow 215 has advanced past the first tier marker 225 A, indicating that the patient has earned enough points in the first reward list to move to the second level of the tiered reward list. The descriptor box 255A has updated, reflecting the current quantity of rewards earned from the first reward list (“Total earned 1100 Points”) and displays updated encouraging text.

[0088] In FIG. 2C, the patient has earned yet more rewards in the first reward list, and the progress bar chart 205C has been updated. Likewise, the descriptor box 255C has been updated with the current quantity of first reward list rewards (“Total earned 1700 Points”) and displays new encouraging text (e.g., “You’re doing great! Keep going and enjoy the journey.”).

[0089] In some embodiments the tiered reward list may not be ordered, even if the first reward list is ordered by an association with timeline codes. Patients may be able to earn or select one or more rewards from a pool of rewards, and the rewards in a pool of rewards can change in each tier of the tiered reward list. Further, delaying acceptance of a reward in a lower tier can, in some embodiments, change or enhance the pool of rewards in a higher tier.

[0090] In FIG. 3A, a progress bar chart 305 is shown in an interface of the client device 140. This progress bar chart 305 is depicting the same underlying rewards data as the progress bar chart 205A-C in FIG 2B. Here, the progress bar chart 305 is depicted in an arc, with tier markers 325A-D. It should be understood that the shape, content, and orientation of the progress bar chart 305 may be varied. The “1100 Points Earned” text from the descriptor box 255B is included within the arc of the progress bar chart 305. Below the progress bar chart 305, tier boxes 330A-D are shown. Each tier box 330A-D includes a title of the tier, and a written description of the current relationship between the tier and the patient (e.g., “You have reached Tier 2 by earning 1100 points”, “You can reach tier 3 by earning 900 points”).Attorney Docket No. H5776-00070

[0091] FIG. 3A also includes a task activity list 355. The task activity list 355 may be populated by the client timeline for the client associated with the client device 140 viewing the task activity list 355. Tasks in the task activity list 355 may be grouped by trimester, and then specifically by weeks of pregnancy, or by some atemporal category into task groups 360A-I (e.g., “Administrative Activity” in task group 360A). Each task group 360A-I includes one or more task records, each task record associated with one or more timeline codes. For example, task group 360C is expanded for viewing, showing task records 365A-E.

[0092] In some embodiments, the task groups 360A-I are organized into discrete care plan phases corresponding to gestational trimester periods, such as a first trimester phase, a second trimester phase, a third trimester phase, and a postpartum phase. Each care plan phase may include multiple time-bounded task groups (e.g., weeks six through eight, weeks ten through twelve), and each task group may include a defined maximum point value representing the total points available for completing all task records within that group. For example, a task group associated with weeks six through eight of the first trimester may include task records for booking an initial appointment, attending the appointment, and completing associated educational activities, with each task record assigned a specific point value (e.g., fifty points for booking, one hundred points for attending). The care plan phases and their constituent task groups provide the patient with a structured, time-sequenced view of their clinical and educational obligations across the full duration of their care journey.

[0093] Task records 365A-E can be associated with several types of timeline codes, and consequently with several types of medical evaluations or events. For example, Task record 365A is associated with “Book Appointment”, and the patient has earned fifty points for booking their appointment. For the reward earning to be registered, the patient books their appointment with a medical provider. The medical provider, using provider device 110, may record the appointment booking as a patient appointment report, which may be stored in the health record server 120. The timeline analysis server 102 may receive, from the health record server 120, the patient appointment report. Either the provider device 110, health record server 120, and / or timeline analysis server 102 may assign an appointment code to the patient appointment report, which may be written in human-readable language. It is contemplated that a large language model (LLM) can be used to receive the patient appointment report, coupled with an LLM prompt, and return an LLM response including the appointment code. In such embodiments, the timeline analysis server 102 may host or communicate with an LLMAttorney Docket No. H5776-00070inference engine (e.g., a Generative Pre-trained Transformer model or similar transformerbased architecture) via an application programming interface (API). The LLM prompt may include structured or unstructured text from the patient appointment report, together with a system prompt instructing the LLM to extract and classify the clinical event described in the report according to a predefined taxonomy of appointment codes (e.g., CPT codes, ICD codes, or proprietary timeline codes maintained by the system 100). The LLM response may include the identified appointment code, a confidence score, and optionally a natural -language rationale for the classification. In some embodiments, when the confidence score falls below a threshold, which may be configurable, the system 100 may flag the appointment report for manual review by a provider via the provider device 110. In some embodiments, a fine-tuned or domain-adapted language model, trained on a corpus of historical patient appointment reports and their associated appointment codes, may be used in place of or in conjunction with a general-purpose LLM to improve classification accuracy and reduce latency.

[0094] Once the appointment code is determined and the timeline analysis server 102 has the patient appointment report and the appointment code, the timeline analysis server 102 can determine whether the appointment code matches a timeline code from the patient timeline. If a match is identified, the timeline analysis server 102 can further analyze the patient appointment report to determine whether a reward is merited. For example, for task record 365D, “Attend Appointment”, the reward is only merited if the patient is marked as having attended the appointment in the patient appointment report. If the patient is marked as cancelling or not showing to the appointment, then no reward would be merited. Once the reward is determined to be merited, the reward information is transmitted to the distribution server 130 for processing. In this example, because the reward is simply additional points associated with the patient, the distribution server 130 increments a point total associated with the patient.

[0095] Each task group 360A-I is depicted with the current quantity of points earned in that group. The task group 360F associated with the present time can be highlighted or emphasized. Task groups 360G-I associated with future periods of time can be faded or deemphasized.

[0096] In FIG. 3B, the client device 140 has selected and expanded the Tier 2 tier box 330B. A tier reward may have been processed by the distribution server 130. The distribution server 130 can determine the number of points or first reward list rewards a patient has earnedAttorney Docket No. H5776-00070or redeemed to further determine an appropriate reward for the patient. In some embodiments, the distribution server 130 can debit the number of points or first reward list rewards a patient has earned or redeemed in order to present the appropriate reward to the patient. In certain of those embodiments, a total number of points can be maintained, which may include all of the points or first reward list rewards a patient has earned or redeemed, including debited points or rewards, and a current number of points can be maintained, which would include all of the points or first reward list rewards still eligible for redemption to receive a tiered list reward.

[0097] The tier reward is depicted in a tier reward box 335. In this example, the tier reward is identified with a redemption code. If the redemption code is presented to a specific device coupled to the distribution server 130, for example a POS terminal, the presenter of the redemption code can receive a physical reward, such as a box of infant diapers or baby wipes, to provide only a couple of non-limiting examples. In some embodiments, the tier reward box 355 may include an interface element, such as a button on the client device 140 interface. Interacting with that button can automatically contact the distribution server 130, which places and approves an order for a physical reward, such as the box of infant diapers or baby wipes. The reward can be delivered to a reception address of the client associated with the client device 140, and can be non-exhaustively a mailing address or a hospital room number.

[0098] As discussed above, the tier reward box 335 can empower the patient to receive their reward in multiple ways. For example, the tier reward box 335 can use radio communication with a POS terminal or a self-service kiosk to facilitate the completion of a transaction exchanging the tiered reward for the physical reward. In some embodiments, the distribution server 130 performs an intermediary transaction, debiting a deposit account associated with system 100 to facilitate a transaction with a POS terminal coupled to distribution server 130. It should be noted that the POS terminal can include transactions beyond “sales” transactions, and can include transaction which do not include the exchange of currency for goods or services, such as transactions at inventory tracking terminals, such as pharmacy management systems, or other logistical or supply management systems.

[0099] The tier reward box 355 can be updated as time passes and the scope of the pregnancy changes. For example, if a patient books and attends an appointment in week 20 with their obstetrician with provider device 110, the patient can earn rewards for their week 20 appointment, or their most recent obstetrics appointment before week 20. However, the rewards associated with a week 6-8 visit to the obstetrician can be foreclosed from the patient,Attorney Docket No. H5776-00070as there is no value in additional obstetrics visits to inspect pre-week 20 issues after a week 20 obstetrician appointment. Alternatively, if a patient has missed one or more obstetrician appointments pre-week 20, but ultimately attends their week 20 obstetrician appointment, in some embodiments the patient can receive all of the rewards associated with the pre-week 20 obstetrician appointments, as the patient is up-to-date with their obstetrician, and the system 100 operators do not believe that “punishing” the patient by foreclosing the pre-week 20 obstetrician appointments benefits patient health outcomes. In some embodiments, the tier reward box 355 can condense or recalculate the rewards for multiple task records 365 where some are missed but some are attended, as discussed above. In some embodiments, the condensing or recalculation is presented in the tier reward box 355, in order to encourage completing a later task record 365 in a series of task records 365; in some embodiments, the condensed or recalculated reward is only presented when earned by completing a later task record 365 in a series of task records 365.

[0100] In some embodiments, the condensing or recalculation of rewards for missed task records may employ one or more of the following algorithms: (a) additive aggregation, wherein the full point values of all missed task records in a chronological series are awarded to the patient upon completion of a subsequent task record in that series; (b) proportional aggregation, wherein a configurable percentage (e.g., fifty percent to one hundred percent, as set by a system administrator) of the point values associated with the missed task records is awarded upon completion of the subsequent task record; or (c) threshold-based aggregation, wherein the missed point values are awarded only if the patient completes the subsequent task record within a configurable time window (e.g., within two weeks of the most recent missed appointment date). The selection among these algorithms may be configurable on a per-program, per-provider, or per-patient basis via the provider device 110 or an administrative interface. The system 100 may additionally cap the total catch-up reward at a configurable maximum value to manage the reward budget of the managing organization.

[0101] The task activity list 355 can be made up of multiple patient timelines, streamlined into a single list, or kept separately as multiple lists. For example, when the patient has a major event (e.g., gives birth to an infant) and a major event report is received by the timeline analysis server 102, a timeline for the infant can be produced, and the timeline for the patient can be updated with post-partum timeline codes, or a new post-partum timeline can be added, and the pre-partum patient timeline can be closed, deleted, or made read-only on the client device 140.Attorney Docket No. H5776-00070Rewards from the multiple timelines, even if associated with separate patient activities and outcomes (i.e., parent and child) the rewards can still be associated with a single patient user for redemption purposes (i.e., the parent patient). The rewards can be kept separate, for separate redemptions (e.g., infant diaper box redemptions for points earned from timeline codes on the child timeline; adult diaper box redemptions for points earned from timeline codes on the parent timeline). The rewards can also be combined, and can be redeemed in a shared reward pool or pools.

[0102] In FIG. 4, the progress bar chart 205B is shown in an interface of the client device 140. The descriptor box 255B is also shown. The interface also includes timeline status boxes 405A-K, which present the periods of the current timeline. The timeline status box 405D associated with the present time can be highlighted or emphasized. Timeline status boxes 405E-K associated with future periods of time can be faded or deemphasized.

[0103] FIG. 4 also includes an educational library 410. The educational library 410 is populated based on the client timeline for the client associated with the client device 140 viewing the educational library 410. Educational materials in the educational library 410 are grouped by trimester, and then specifically by weeks of pregnancy, or by some atemporal category into educational groups 420A-D (e.g., the educational lesson 425A under “General Modules”). Each educational group 420A-D includes one or more educational lessons 425A-C. Educational lessons 425A-C can be associated with rewards, or they can be presented for the patient’s personal edification. Educational lessons 425 A-C can be associated with certain timeline codes, patient appointment codes, or health report notes, and can be presented on the client device 140 when certain timeline codes have been completed, certain appointment types have been scheduled or have occurred, or based on notes a practitioner made regarding a medical evaluation at an appointment. As discusses above, the educational lessons 425A-C can be included in the patient timeline, and may or may not be associated with timeline codes. The educational lessons 425A-C can be associated with educational codes, which function similarly to timeline codes, and can be associated with rewards, but may not be associated with specific medical or clinical events.

[0104] In some embodiments, the educational lessons 425A-C may comprise various media formats, including video content, audio podcast content, and written articles. The educational content may be authored or curated by clinicians associated with the healthcare provider operating the provider device 110, and may incorporate the clinical voice andAttorney Docket No. H5776-00070experience of the patient’s care team. For example, a clinician may record a video lesson addressing a specific prenatal topic, such as nutrition during pregnancy, gestational diabetes management, or labor preparation, and the recorded video lesson may be associated with a timeline code corresponding to the gestational period in which the educational content is most relevant. The use of clinician-authored multimedia educational content may improve patient trust in and engagement with the educational library 410.

[0105] FIG. 5 illustrates one example of a process of managing a web application performed by a user device in accordance with some embodiments described herein. FIG. 5 is shown in simplified, schematic format for purposes of illustrating a clear example and other embodiments may include more, fewer, or different elements connected in various manners. FIG. 5 is intended to disclose an algorithm, plan or outline that can be used to implement one or more computer programs or other software elements which when executed cause performing the functional improvements and technical advances that are described herein. Furthermore, the flow diagrams herein are described at the same level of detail that persons of ordinary skill in the art ordinarily use to communicate with one another about algorithms, plans, or specifications forming a basis of software programs that they plan to code or implement using their accumulated skill and knowledge.

[0106] In some embodiments, the system 100 receives, via a provider device 110, an onboarding report. The system 100 modifies a patient timeline based upon the onboarding report.

[0107] In some embodiments, the system 100 may generate the patient timeline based on the patient appointment report via a machine learning model.

[0108] In some embodiments, the system 100 receives, via the provider device 110, a major event report. The system 100, based on the major event report, produces a parent timeline and a child timeline.

[0109] In some embodiments, at block 505, the system 100 receives at the health record server 120 via the provider device 110 a patient appointment report. The patient appointment report may include a health outcome of the patient. In certain embodiments, the system 100 receives, via the provider device 110, a child appointment report. The child appointment report may include a child health outcome of a child of the patient. In some embodiments, the health outcome may be obtained by a biometric sensor of the provider device 110. The patientAttorney Docket No. H5776-00070appointment report can be transmitted in response to the health outcome being obtained by the biometric sensor.

[0110] In some embodiments, at block 510, the system 100 determines a patient appointment code based upon the patient appointment report. In certain embodiments, the system 100 may determine a child appointment code based upon the child appointment report. In specific embodiments, the system 100 may retrieve a parent timeline code from the parent timeline. The parent timeline code may be associated with the appointment code, and the parent timeline may be associated with the patient.[OHl] In some embodiments, at block 515, the system 100 retrieves a timeline code from the patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient. In certain embodiments, the system may retrieve a child timeline code from the child timeline. The child timeline code may be associated with the child appointment code, and the child timeline may be associated with the patient.

[0112] In some embodiments, at block 520, the system 100 selects a reward from a reward list. The reward may be selected based upon the timeline code and the health outcome. In certain embodiments, the reward may include a numerical point value. The system 100 may increment a point total associated with the patient by the numerical point value. The system 100 may select a tiered reward from a tiered reward list, and the tiered reward may be selected based upon the point total.

[0113] In specific embodiments, the system 100 may select a child reward from the reward list. The child reward may be selected based upon the child timeline code and the child health outcome. In a subset of those embodiments, the system 100 may select a parent reward from the reward list, and the parent reward may be selected based upon the parent timeline code and the health outcome.

[0114] In some embodiments, the system 100 may transmit a patient educational lesson to the client device 140. The system 100 may present the patient educational lesson on the client device 140. The system 100 may present a patient educational assessment on the client device 140. The system 100 may transmit a patient educational assessment outcome based on the patient educational assessment. The system 100 may select an educational reward from the reward list, the educational reward selected based upon the patient educational assessment outcome. The system 100 may dispense the educational reward from the distribution serverAttorney Docket No. H5776-00070130 to the patient.

[0115] In some embodiments, the patient educational assessment presented on the client device 140 may comprise one or more of: multiple-choice questions, true / false questions, and / or completion-based metrics. For completion-based metrics, the system 100 may determine the patient educational assessment outcome based on whether the patient has viewed at least a configurable percentage (e.g., eighty percent) of a video lesson or has scrolled through an entire written article. For question-based assessments, the patient educational assessment outcome may be determined as a pass / fail result based on whether the patient correctly answers at least a configurable threshold percentage (e.g., seventy percent) of the presented questions. The configurable thresholds may be set by a system administrator via the provider device 110 and may vary by educational topic, gestational period, or clinical significance of the educational content. In some embodiments, a patient who does not achieve a passing score may be presented with the opportunity to retake the assessment, and the educational reward may be withheld until a passing score is achieved.

[0116] In some embodiments, the system 100 may transmit a scheduling request from the client device 140. The scheduling request may be associated with a scheduling code from the patient timeline. The system 100 may select a scheduling reward from the reward list. The scheduling reward may be selected based upon the scheduling request. The system 100 may dispense the scheduling reward from the distribution server 130 to the patient. In a subset of those embodiments, the system 100 may receive, from the provider device 110, an absence report. The absence report may be associated with the scheduling request. Based on the absence report, the system 100 may adjust the timeline and available rewards.

[0117] In some embodiments, after selecting the reward from the reward list, the system 100 may send a reward notification to the client device 140. The system 100 may send a reward confirmation from the client device 140 to the distribution server 130. In response to receiving the reward confirmation, the system 100 may dispense the reward from the distribution server 130 to the patient.

[0118] In some embodiments, at block 525, the system 100 may dispense the reward from the distribution server 130 to the patient. In specific embodiments, the system 100 may dispense the child reward from the distribution server 130 to the patient. In a subset of those embodiments, the system 100 may dispense the parent reward from the distribution server 130Attorney Docket No. H5776-00070to the patient. In certain embodiments, the system 100 may dispense the tiered reward from the distribution server 130 to the patient. In a different and / or overlapping subset of those embodiments, based on receiving the major event report, the system 100 may start a redemption countdown. Based on an expiration of the redemption countdown, the system 100 may retract the reward. In some embodiments, the distribution server 130 may include a product dispenser. The reward may be dispensed when the product dispenser is proximate to the client device 140.

[0119] In some embodiments, when the distribution server 130 includes a product dispenser and the reward is dispensed when the product dispenser is proximate to the client device 140, the dispensation may be authenticated via a challenge-response protocol. For example, the distribution server 130 or the timeline analysis server 102 may transmit a timelimited cryptographic token (e.g., a signed JSON Web Token (JWT) with a configurable expiration period) to the client device 140 upon reward selection. The client device 140 may present the cryptographic token to the product dispenser via a near-field communication (NFC) tap, a Bluetooth Low Energy (BLE) advertisement, or a visually displayed quick-response (QR) code scanned by an optical reader coupled to the product dispenser. The product dispenser may validate the cryptographic token by verifying its digital signature and confirming that the token has not expired, and may additionally confirm the token’s validity with the distribution server 130 via a network query, before releasing the physical reward to the patient. In some embodiments, the proximity-based dispensation may be authenticated via a one-time passcode (OTP) transmitted to the client device 140 and entered by the patient at the product dispenser. The authentication mechanism ensures that rewards are dispensed only to the patient to whom they were allocated, preventing unauthorized redemption.

[0120] In some embodiments, the machine learning model may be trained based upon the patient timeline, the patient appointment report, and the reward, thereby producing a revised machine learning model. The system 100 may generate an additional patient timeline based on an additional patient appointment report via the revised machine learning model. The additional patient timeline may be unequal to the patient timeline.

[0121] In some embodiments, the machine learning model comprises a supervised learning model, such as a gradient-boosted decision tree (e.g., XGBoost or LightGBM), a random forest, or a deep neural network (e.g., a multi-layer perceptron or a recurrent neural network such as a Long Short-Term Memory (LSTM) network). The input features to the machine learning model may include, without limitation: patient demographic data (e.g., age,Attorney Docket No. H5776-00070gestational age, parity, socioeconomic indicators), historical appointment attendance rates, historical reward redemption rates, health outcome severity scores derived from appointment reports, timeline progression metrics (e.g., percentage of timeline codes completed on schedule), and temporal features (e.g., day of week, time since last appointment). The output of the machine learning model may include a predicted optimal patient timeline, comprising a sequence of timeline codes with associated target dates and recommended reward values calibrated to maximize patient engagement and health outcome improvement.

[0122] The training of the machine learning model may employ a loss function that combines a clinical outcome component (e.g., minimizing deviation from recommended clinical guidelines) with an engagement component (e.g., maximizing predicted appointment attendance probability). The training dataset may include records from multiple patients, with each record comprising a patient timeline, associated appointment reports, rewards dispensed, and subsequent patient behaviors (e.g., whether the patient attended the next scheduled appointment after receiving a reward). The model may be retrained periodically (e.g., weekly or monthly) as new patient data accumulates, or may be retrained in response to detecting model drift via monitoring of prediction accuracy metrics. Hyperparameter tuning may be performed via cross-validation, Bayesian optimization, or grid search over a held-out validation set. The revised machine learning model, having been trained on updated data including the patient’s own engagement history, may generate a revised patient timeline that differs from the original timeline in one or more of: the sequencing of timeline codes, the spacing between recommended appointments, the reward values associated with particular timeline codes, or the inclusion of additional recommended evaluations based on detected health risks.

[0123] In some instances, the system 100 may perform operations that train adaptively a machine-learning or artificial-intelligence process, such as a machine learning module to: create a training scenario; generate a generated response based at least in part on an input prompt; and prepare a generated evaluation of an input response, using training datasets associated with a first grouping (e.g., a “training” grouping), and using validation datasets associated with a second, and distinct, grouping (e.g., a “validation” grouping). A predictive output of the trained, machine-learning or artificial-intelligence processes may, in some examples, evaluate the effectiveness of certain rewards in encouraging desired behavior, may prepare a patient timeline based on an inputted onboarding report, or may revise a patient timeline based on an inputted health report. The disclosed embodiments are, however, notAttorney Docket No. H5776-00070limited to these exemplary analyses and suggestions, and in other instances, system 100 may perform operations that train adaptively a machine-learning or artificial-intelligence process to predict a likelihood of an occurrence of any additional, or alternate, event appropriate to consolidated elements of patient data, timeline data, and reward data maintained within health record server 120, timeline analysis server 102, or distribution server 130, and appropriate to the machine-learning or artificial-intelligence processes (e.g., the machine learning module).

[0124] Further, and as described herein, the machine-learning or artificial-intelligence processes may include a deep learning or neural network process, such as a Generative Pretrained Transformer (GPT), and the training and validation datasets may include, but are not limited to, values of adaptively selected features obtained, extracted, or derived from the consolidated data records maintained within health record server 120, timeline analysis server 102, or distribution server 130, e.g., from data elements maintained within the discrete data records within health record server 120, timeline analysis server 102, or distribution server 130, as well as large language models, partially or completely encompassed within the follow-up question database. By way of example, the values of adaptively selected features of the training and validation datasets may be obtained, extracted, or derived from the patient data, timeline data, and reward data that characterize the patients, rewards, and health outcomes within respective ones of the training and validation groups, e.g., as maintained within the patient data, timeline data, and reward data maintained within health record server 120, timeline analysis server 102, or distribution server 130. In some instances, and through a performance of one or more of the adaptive process training and validation operations described herein, system 100 may generate elements of process parameter data, which includes value of one or more process parameters for the trained, machine-learning or artificial-intelligence process, and elements of composition data, which identify each feature of an input dataset for the trained, machinelearning or artificial-intelligence processes and specify a sequential position of each feature within the input dataset.

[0125] Further, and through the performance of one or more of the adaptive process training and validation operations described herein, system 100 may generate elements of explainability data that, among other things, characterize a relationship between a value of each, or a subset of, the features within the input dataset and the predictive output of the trained, machine-learning or artificial-intelligence processes. In some instances, the elements of explainability data may include a Shapley value associated with each of the features of theAttorney Docket No. H5776-00070input dataset, and as described herein, the Shapley values may characterize a relative importance of each of the discrete features within the input dataset (e.g., as specified within the composition data), and further, a relationship between a magnitude of corresponding ones of the feature values and a magnitude of the predictive output.

[0126] By way of example, and for a particular input feature, a Shapley value of large magnitude may imply that a value of the particular input feature is associated with a corresponding, large contribution to the predicted output, and an increase in a magnitude of that particular feature value may drive an increase in the magnitude of that predicted output. Further, for a particular input feature, a Shapley value of small magnitude may imply that a value of the particular input feature is associated with a corresponding, small contribution to the predicted output and to any increase in the magnitude of that predicted output. In some instances, the elements of explainability data generated through the adaptive training of the machine-learning or artificial intelligence processes may represent elements of reference explainability data that characterize, among other things, a baseline relationship between the values of the features within the input dataset and the predictive output of the machine-learning or artificial intelligence, and further, the reference explainability data may facilitate an application of one or more of the exemplary, dynamic explainability monitoring processes within one or more groups subsequent to the adaptive training of the machine-learning or artificial intelligence process, e.g., during a deployment of the trained machine-learning or artificial intelligence process.

[0127] In some embodiments, the system 100 includes an artificial intelligence (Al) knowledgebase module accessible via the client device 140 that functions as a symptom checker for patient questions and health concerns. The Al knowledgebase module may receive natural -language input from the patient describing symptoms, discomfort, or health-related questions, and may generate responsive guidance based on a clinical knowledge corpus maintained at the timeline analysis server 102 or at a separate knowledge server communicatively coupled to the system 100. In some embodiments, the Al knowledgebase module implements escalation logic that evaluates the severity or urgency of the patient’s reported symptoms and, when the reported symptoms exceed a configurable severity threshold, automatically escalates the patient’s inquiry to a nurse triage pathway, such as by transmitting a notification to a clinical staff member via the provider device 110 or by initiating a real-time communication session (e.g., a chat, video call, or telephone call) between the patient and aAttorney Docket No. H5776-00070nurse. The Al knowledgebase module may operate independently of the reward system, or may be integrated with the patient timeline such that completion of a symptom assessment is associated with a timeline code and eligible for reward dispensation.

[0128] In some embodiments, the system 100 is communicatively coupled to a third-party transportation service, such as a ride-share platform (e.g., Uber, Lyft, or a similar on-demand transportation provider), for the purpose of facilitating patient attendance at scheduled medical evaluations. The timeline analysis server 102 may detect an upcoming appointment on the patient timeline and transmit a transportation coordination request to the third-party transportation service via an application programming interface (API), causing the third-party transportation service to arrange a ride for the patient to the location of the scheduled medical evaluation. In some embodiments, the cost of the transportation may be subsidized or fully covered by the managing organization, and the distribution server 130 may process the transportation cost as a reward or incentive associated with the relevant timeline code. The transportation integration addresses social determinants of health barriers, such as lack of reliable transportation, that contribute to underutilization of perinatal and neonatal medical services as discussed in the Background section above.

[0129] According to one embodiment, the techniques described herein are implemented by at least one computing device. The techniques may be implemented in whole or in part using a combination of at least one server computer and / or other computing devices that are coupled using a network, such as a packet data network. The computing devices may be hardwired to perform the techniques, or may include digital electronic devices such as at least one application-specific integrated circuit (ASIC) or field programmable gate array (FPGA) that is persistently programmed to perform the techniques, or may include at least one general purpose hardware processor programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the described techniques. The computing devices may be server computers, workstations, personal computers, portable computer systems, handheld devices, mobile computing devices, wearable devices, body mounted or implantable devices, smartphones, smart appliances, internetworking devices, autonomous or semi-autonomous devices such as robots or unmanned ground or aerial vehicles, any other electronic device that incorporates hard-wired and / or program logic to implement the described techniques, one or more virtual computing machinesAttorney Docket No. H5776-00070or instances in a data center, and / or a network of server computers and / or personal computers.

[0130] FIG. 6 is a block diagram that illustrates an example computer system with which an embodiment may be implemented. In the example of FIG. 6, a computer system 600 and instructions for implementing the disclosed technologies in hardware, software, or a combination of hardware and software, are represented schematically, for example as boxes and circles, at the same level of detail that is commonly used by persons of ordinary skill in the art to which this disclosure pertains for communicating about computer architecture and computer systems implementations.

[0131] Computer system 600 includes an input / output (I / O) subsystem 602 which may include a bus and / or other communication mechanism(s) for communicating information and / or instructions between the components of the computer system 600 over electronic signal paths. The VO subsystem 602 may include an I / O controller, a memory controller and at least one I / O port. The electronic signal paths are represented schematically in the drawings, for example as lines, unidirectional arrows, or bidirectional arrows.

[0132] At least one hardware processor 604 is coupled to I / O subsystem 602 for processing information and instructions. Hardware processor 604 may include, for example, a general-purpose microprocessor or microcontroller and / or a special-purpose microprocessor such as an embedded system or a graphics processing unit (GPU) or a digital signal processor or ARM processor. Processor 604 may comprise an integrated arithmetic logic unit (ALU) or may be coupled to a separate ALU.

[0133] Computer system 600 includes one or more units of memory 606, such as a main memory, which is coupled to I / O subsystem 602 for electronically digitally storing data and instructions to be executed by processor 604. Memory 606 may include volatile memory such as various forms of random-access memory (RAM) or other dynamic storage device. Memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 604. Such instructions, when stored in non-transitory computer-readable storage media accessible to processor 604, can render computer system 600 into a special-purpose machine that is customized to perform the operations specified in the instructions.

[0134] Computer system 600 further includes non-volatile memory such as read only memory (ROM) 608 or other static storage device coupled to I / O subsystem 602 for storingAttorney Docket No. H5776-00070information and instructions for processor 604. The ROM 608 may include various forms of programmable ROM (PROM) such as erasable PROM (EPROM) or electrically erasable PROM (EEPROM). A unit of persistent storage 610 may include various forms of non-volatile RAM (NVRAM), such as FLASH memory, or solid-state storage, magnetic disk, or optical disk such as CD-ROM or DVD-ROM, and may be coupled to I / O subsystem 602 for storing information and instructions. Storage 610 is an example of a non-transitory computer-readable medium that may be used to store instructions and data which when executed by the processor 604 cause performing computer-implemented methods to execute the techniques herein.

[0135] The instructions in memory 606, ROM 608 or storage 610 may comprise one or more sets of instructions that are organized as modules, methods, objects, functions, routines, or calls. The instructions may be organized as one or more computer programs, operating system services, or application programs including mobile apps. The instructions may comprise an operating system and / or system software; one or more libraries to support multimedia, programming or other functions; data protocol instructions or stacks to implement Transmission Control Protocol / Intemet Protocol (TCP / IP), Hypertext Transfer Protocol (HTTP) or other communication protocols; file processing instructions to interpret and render files coded using HTML, Extensible Markup Language (XML), Joint Photographic Experts Group (JPEG), Moving Picture Experts Group (MPEG) or Portable Network Graphics (PNG); user interface instructions to render or interpret commands for a GUI, command-line interface or text user interface; application software such as an office suite, internet access applications, design and manufacturing applications, graphics applications, audio applications, software engineering applications, educational applications, games or miscellaneous applications. The instructions may implement a web server, web application server or web client. The instructions may be organized as a presentation layer, application layer and data storage layer such as a relational database system using structured query language (SQL) or NoSQL, an object store, a graph database, a flat file system or other data storage.

[0136] Computer system 600 may be coupled via I / O subsystem 602 to at least one output device 612. In one embodiment, output device 612 is a digital computer display. Examples of a display that may be used in various embodiments include a touch screen display or a lightemitting diode (LED) display or a liquid crystal display (LCD) or an e-paper display. Computer system 600 may include other type(s) of output devices 612, alternatively or in addition to a display device. Examples of other output devices 612 include printers, ticketAttorney Docket No. H5776-00070printers, plotters, projectors, sound cards or video cards, speakers, buzzers or piezoelectric devices or other audible devices, lamps or LED or LCD indicators, haptic devices, actuators, or servos.

[0137] At least one input device 614 is coupled to I / O subsystem 602 for communicating signals, data, command selections or gestures to processor 604. Examples of input devices 614 include touch screens, microphones, still and video digital cameras, alphanumeric and other keys, keypads, keyboards, graphics tablets, image scanners, joysticks, clocks, switches, buttons, dials, slides, and / or various types of sensors such as force sensors, motion sensors, heat sensors, biometric sensors, pulse sensors, kinematic sensors, accelerometers, gyroscopes, and inertial measurement unit (IMU) sensors and / or various types of transceivers such as wireless, such as cellular or Wi-Fi, radio frequency (RF) or infrared (IR) transceivers and Global Positioning System (GPS) transceivers. Biometric sensors can also include any sensor, device, or component which captures data related to a biological metric, and can communicate it to processor 604: biometric sensors can include hospital equipment which is networked or has communication ports, such as a Magnetic Resonance Imaging (MRI) machine, an ultrasound machine, a computed tomography (CT) scan machine, a positron emission tomography (PET) scan machine, an X-ray machine, an endoscopy machine, a blood and urinalysis machine, a microplate reader, a patient monitor, a blood pressure monitor, a weight scale, a surgical robot, or other diagnostic equipment.

[0138] Another type of input device is a control device 616, which may perform cursor control or other automated control functions such as navigation in a graphical interface on a display screen, alternatively or in addition to input functions. Control device 616 may be a touchpad, a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 604 and for controlling cursor movement on the output device 612. The input device may have at least two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. Another type of input device is a wired, wireless, or optical control device such as a joystick, wand, console, steering wheel, pedal, gearshift mechanism or other type of control device. An input device 614 may include a combination of multiple different input devices, such as a video camera and a depth sensor.

[0139] In some embodiments, computer system 600 may comprise an internet of things (loT) device in which one or more of the output device 612, input device 614, and controlAttorney Docket No. H5776-00070device 616 are omitted. Or, in such an embodiment, the input device 614 may comprise one or more cameras, motion detectors, thermometers, microphones, seismic detectors, other sensors or detectors, measurement devices or encoders and the output device 612 may comprise a special-purpose display such as a single-line LED or LCD display, one or more indicators, a display panel, a meter, a valve, a solenoid, an actuator or a servo.

[0140] When computer system 600 is a mobile computing device, input device 614 may comprise a global positioning system (GPS) receiver coupled to a GPS module that is capable of triangulating to a plurality of GPS satellites, determining and generating geo-location or position data such as latitude-longitude values for a geophysical location of the computer system 600. Output device 612 may include hardware, software, firmware, and interfaces for generating position reporting packets, notifications, pulse or heartbeat signals, or other recurring data transmissions that specify a position of the computer system 600, alone or in combination with other application-specific data, directed toward host computer 624 or server 630.

[0141] Computer system 600 may implement the techniques described herein using customized hard-wired logic, at least one ASIC or FPGA, firmware and / or program instructions or logic which when loaded and used or executed in combination with the computer system causes or programs the computer system to operate as a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 600 in response to processor 604 executing at least one sequence of at least one instruction contained in main memory 606. Such instructions may be read into main memory 606 from another storage medium, such as storage 610. Execution of the sequences of instructions contained in main memory 606 causes processor 604 to perform the process steps described herein. In some embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

[0142] The term “storage media” as used herein refers to any non-transitory media that store data and / or instructions that cause a machine to operate in a specific fashion. Such storage media may comprise non-volatile media and / or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage 610. Volatile media includes dynamic memory, such as memory 606. Common forms of storage media include, for example, a hard disk, solid state drive, flash drive, magnetic data storage medium, any optical or physical data storage medium, memory chip, or the like.Attorney Docket No. H5776-00070

[0143] Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus of I / O subsystem 602. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infrared data communications.

[0144] Various forms of media may be involved in carrying at least one sequence of at least one instruction to processor 604 for execution. For example, the instructions may initially be carried on a magnetic disk or solid-state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a communication link such as a fiber optic or coaxial cable or telephone line using a modem. A modem or router local to computer system 600 can receive the data on the communication link and convert the data to be read by computer system 600. For instance, a receiver such as a radio frequency antenna or an infrared detector can receive the data carried in a wireless or optical signal and appropriate circuitry can provide the data to VO subsystem 602 such as place the data on a bus. I / O subsystem 602 carries the data to memory 606, from which processor 604 retrieves and executes the instructions. The instructions received by memory 606 may optionally be stored on storage 610 either before or after execution by processor 604.

[0145] Computer system 600 also includes a communication interface 618 coupled to I / O subsystem 602. Communication interface 618 provides a two-way data communication coupling to network link(s) 620 that are directly or indirectly connected to at least one communication network, such as a network 622 or a public or private cloud on the Internet. For example, communication interface 618 may be an Ethernet networking interface, integrated-services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of communications line, for example an Ethernet cable or a metal cable of any kind or a fiber-optic line or a telephone line. Network 622 broadly represents a LAN, WAN, campus network, internetwork, or any combination thereof. Communication interface 618 may comprise a LAN card to provide a data communication connection to a compatible LAN, or a cellular radiotelephone interface that is wired to send or receive cellular data according to cellular radiotelephone wireless networking standards, or a satellite radio interface that is wired to send or receive digital data according to satellite wireless networking standards. In any such implementation,Attorney Docket No. H5776-00070communication interface 618 sends and receives electrical, electromagnetic, or optical signals over signal paths that carry digital data streams representing various types of information.

[0146] Network link 620 typically provides electrical, electromagnetic, or optical data communication directly or through at least one network to other data devices, using, for example, satellite, cellular, Wi-Fi, or BLUETOOTH technology. For example, network link 620 may provide a connection through a network 622 to a host computer 624.

[0147] Furthermore, network link 620 may provide a connection through network 622 or to other computing devices via internetworking devices and / or computers that are operated by an Internet Service Provider (ISP) 626. ISP 626 provides data communication services through a world-wide packet data communication network represented as internet 628. A server 630 may be coupled to internet 628. Server 630 broadly represents any computer, data center, virtual machine, or virtual computing instance with or without a hypervisor, or computer executing a containerized program system such as DOCKER or KUBERNETES. Server 630 may represent an electronic digital service that is implemented using more than one computer or instance and that is accessed and used by transmitting web services requests, URL strings with parameters in HTTP payloads, application programming interface (API) calls, app services calls, or other service calls. Computer system 600 and server 630 may form elements of a distributed computing system that includes other computers, a processing cluster, server farm or other organization of computers that cooperate to perform tasks or execute applications or services. Server 630 may comprise one or more sets of instructions that are organized as modules, methods, objects, functions, routines, or calls. The instructions may be organized as one or more computer programs, operating system services, or application programs including mobile apps. The instructions may comprise an operating system and / or system software; one or more libraries to support multimedia, programming or other functions; data protocol instructions or stacks to implement TCP / IP, HTTP or other communication protocols; file format processing instructions to interpret or render files coded using HTML, XML, JPEG, MPEG or PNG; user interface instructions to render or interpret commands for a GUI, command-line interface or text user interface; application software such as an office suite, internet access applications, design and manufacturing applications, graphics applications, audio applications, software engineering applications, educational applications, games or miscellaneous applications. Server 630 may comprise a web application server that hosts a presentation layer, application layer and data storage layer such as a relational database systemAttorney Docket No. H5776-00070using structured query language (SQL) or NoSQL, an object store, a graph database, a flat file system or other data storage.

[0148] Computer system 600 can send messages and receive data and instructions, including program code, through the network(s), network link 620 and communication interface 618. In the Internet example, a server 630 might transmit a requested code for an application program through Internet 628, ISP 626, local network 622 and communication interface 618. The received code may be executed by processor 604 as it is received, and / or stored in storage 610, or other non-volatile storage for later execution.

[0149] The execution of instructions as described in this section may implement a process in the form of an instance of a computer program that is being executed, and consisting of program code and its current activity. Depending on the operating system (OS), a process may be made up of multiple threads of execution that execute instructions concurrently. In this context, a computer program is a passive collection of instructions, while a process may be the actual execution of those instructions. Several processes may be associated with the same program; for example, opening up several instances of the same program often means more than one process is being executed. Multitasking may be implemented to allow multiple processes to share processor 604. While each processor 604 or core of the processor executes a single task at a time, computer system 600 may be programmed to implement multitasking to allow each processor to switch between tasks that are being executed without having to wait for each task to finish. In an embodiment, switches may be performed when tasks perform input / output operations, when a task indicates that it can be switched, or on hardware interrupts. Time-sharing may be implemented to allow fast response for interactive user applications by rapidly performing context switches to provide the appearance of concurrent execution of multiple processes simultaneously. In an embodiment, for security and reliability, an operating system may prevent direct communication between independent processes, providing strictly mediated and controlled inter-process communication functionality.

[0150] In the foregoing specification, embodiments of the disclosure have been described with reference to numerous specific details that may vary from implementation to implementation. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the disclosure, and what is intended by the applicants to be the scope of the disclosure, is the literal and equivalent scope of the set of claims that issue from this application, in the specific formAttorney Docket No. H5776-00070in which such claims issue, including any subsequent correction.

[0151] Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Exemplary embodiments of the subject matter described in this specification, such as, but not limited to protocol 500 can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, a data processing apparatus (or a computer system). According to some embodiments, “function,” “functions,” “application,” “applications,” “instruction,” “instructions,” or “programming” are program(s) that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++), procedural programming languages (e.g., C or assembly language), or firmware. In a specific example, a third-party application (e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the third-party application can invoke API calls provided by the operating system to facilitate functionality described herein.

[0152] Additionally, or alternatively, the program instructions can be encoded on an artificially generated propagated signal, such as a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0153] Hence, a machine-readable medium may take many forms of tangible storage medium. Non-volatile storage media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s) or the like, such as may be used to implement the client device, media gateway, transcoder, etc. shown in the drawings. Volatile storage media include dynamic memory, such as main memory of such a computer platform. Tangible transmission media include coaxial cables; copper wire and fiber optics, including the wiresAttorney Docket No. H5776-00070that comprise a bus within a computer system. Carrier-wave transmission media may take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media therefore include for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any other optical medium, punch cards paper tape, any other physical storage medium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM, any other memory chip or cartridge including flash or semiconductor memory devices, special purpose logic circuitry, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer may read programming code and / or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution.

[0154] The terms “apparatus,” “device,” and “system” refer to data processing hardware and encompass all kinds of apparatus, devices, and machines for processing data, including, by way of example, a programmable processor such as a graphical processing unit (GPU) or central processing unit (CPU), a computer, or multiple processors or computers. The apparatus, device, or system can also be or further include special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). The apparatus, device, or system can optionally include, in addition to hardware, code that creates an execution environment for computer programs, such as code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

[0155] A computer program, which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, such as one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, such as files that store one or more modules, sub programs, or portions of code. A computer program can be deployed to beAttorney Docket No. H5776-00070executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

[0156] The processes, protocols, and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes, protocols, and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array), an ASIC (application specific integrated circuit), one or more processors, or any other suitable logic.

[0157] Computers suitable for the execution of a computer program include, by way of example, general or special purpose microprocessors or both, or any other kind of central processing unit (e.g., processor 604). Generally, a CPU will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data (e.g., memory 606). Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, such as magnetic, magneto optical disks, or optical disks (e.g., secondary memory 608, 610). However, a computer need not have such devices. Moreover, a computer can be embedded in another device, such as a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, such as a universal serial bus (USB) flash drive, to name just a few.

[0158] To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display unit, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, such as a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user’ s device in response to requests received from the web browser.Attorney Docket No. H5776-00070

[0159] Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back end component, such as a data server, or that includes a middleware component, such as an application server, or that includes a front end component, such as a computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), such as the Internet.

[0160] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some implementations, a server transmits data, such as an HTML page, to a user device, such as for purposes of displaying data to and receiving user input from a user interacting with the user device, which acts as a client. Data generated at the user device, such as a result of the user interaction, can be received from the user device at the server.

[0161] While this specification includes many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[0162] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous.Attorney Docket No. H5776-00070Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0163] Various embodiments have been described herein with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the disclosed embodiments as set forth in the claims that follow.

[0164] Further, other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of one or more embodiments of the present disclosure. It is intended, therefore, that this disclosure and the examples herein be considered as exemplary only, with a true scope and spirit of the disclosed embodiments being indicated by the following listing of exemplary claims.

[0165] The scope of protection is limited solely by the claims that now follow. That scope is intended and should be interpreted to be as broad as is consistent with the ordinary meaning of the language that is used in the claims when interpreted in light of this specification and the prosecution history that follows and to encompass all structural and functional equivalents. Notwithstanding, none of the claims are intended to embrace subject matter that fails to satisfy the requirement of Sections 101, 102, or 103 of the Patent Act, nor should they be interpreted in such a way. Any unintended embracement of such subject matter is hereby disclaimed.

[0166] Except as stated immediately above, nothing that has been stated or illustrated is intended or should be interpreted to cause a dedication of any component, element, block, step, feature, object, benefit, advantage, or equivalent to the public, regardless of whether it is or is not recited in the claims. It will be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein. Relational terms such as first and second and the like may be used solely to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “includes,” “including,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatusAttorney Docket No. H5776-00070that comprises or includes a list of elements, blocks, or steps does not include only those elements, blocks, or steps but may include other elements, blocks, or steps not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by “a” or “an” does not, without further constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element unless the context clearly and unambiguously dictates otherwise.

[0167] Unless otherwise stated, any and all measurements, values, ratings, positions, magnitudes, sizes, and other specifications that are set forth in this specification, including in the claims that follow, are approximate, not exact. Such amounts are intended to have a reasonable range that is consistent with the functions to which they relate and with what is customary in the art to which they pertain. For example, unless expressly stated otherwise, a parameter value or the like may vary by as much as ±10% from the stated amount.

[0168] In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various examples for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, the subject matter to be protected lies in less than all features of any single disclosed example. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

[0169] While the foregoing has described what are considered to be the best mode and / or other examples, it is understood that various modifications may be made therein and that the subject matter disclosed herein may be implemented in various forms and examples, and that they may be applied in numerous applications, only some of which have been described herein. It is intended by the following claims to claim any and all modifications and variations that fall within the true scope of the present concepts.

Claims

Attorney Docket No. H5776-00070CLAIMSWhat is claimed is:

1. A system comprising:a client device associated with a patient;a provider device;a health record server;a timeline analysis server;a distribution server; andprogramming, wherein execution of the programming by one or more processors of the system configures the system to perform the following functions:receive at the health record server via the provider device a patient appointment report, the patient appointment report including a health outcome of the patient;determine a patient appointment code based upon the patient appointment report;retrieve a timeline code from a patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient;select a reward from a reward list, the reward selected based upon the timeline code and the health outcome; anddispense the reward from the distribution server to the patient.

2. The system of claim 1, wherein:the reward includes a numerical point value; andexecution of the programming by one or more processors of the system further configures the system to perform the following functions:increment a point total associated with the patient by the numerical point value;select a tiered reward from a tiered reward list, the tiered reward selected based upon the point total; anddispense the tiered reward from the distribution server to the patient.

3. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions: receive via the provider device an onboarding report; andAttorney Docket No. H5776-00070modify the patient timeline based upon the onboarding report.

4. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:receive, via the provider device, a major event report;based on the major event report, produce a parent timeline and a child timeline; receive via the provider device a child appointment report, the child appointment report including a child health outcome of a child of the patient;determine a child appointment code based upon the child appointment report; retrieve a child timeline code from the child timeline, the child timeline code associated with the child appointment code and the child timeline associated with the patient;select a child reward from the reward list, the child reward selected based upon the child timeline code and the child health outcome; anddispense the child reward from the distribution server to the patient.

5. The system of claim 4, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:retrieve a parent timeline code from the parent timeline, the parent timeline code associated with the patient appointment code and the parent timeline associated with the patient;select a parent reward from the reward list, the parent reward selected based upon the parent timeline code and the health outcome; anddispense the parent reward from the distribution server to the patient.

6. The system of claim 4, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:based on receiving the major event report, start a redemption countdown; and based on an expiration of the redemption countdown, retract the reward.

7. The system of claim 1, wherein:the health outcome is obtained by a biometric sensor of the provider device; and the patient appointment report is transmitted in response to the health outcome being obtained by the biometric sensor.Attorney Docket No. H5776-000708. The system of claim 1, wherein:the distribution server includes a product dispenser; andthe reward is dispensed when the product dispenser is proximate to the client device.

9. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:after selecting the reward from the reward list, send a reward notification to the client device;send a reward confirmation from the client device to the distribution server; and in response to receiving the reward confirmation, dispense the reward from the distribution server to the patient.

10. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:transmit a patient educational lesson to the client device;present the patient educational lesson on the client device;present a patient educational assessment on the client device;transmit a patient educational assessment outcome based on the patient educational assessment;select an educational reward from the reward list, the educational reward selected based upon the patient educational assessment outcome; anddispense the educational reward from the distribution server to the patient.

11. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:transmit a scheduling request, the scheduling request associated with a scheduling code from the patient timeline;select a scheduling reward from the reward list, the scheduling reward selected based upon the scheduling request; anddispense the scheduling reward from the distribution server to the patient.

12. The system of claim 1, wherein execution of the programming by one or more processors of the system further configures the system to perform the following functions:modify the patient timeline based upon the health outcome; andAttorney Docket No. H5776-00070modify the reward list based upon the health outcome.

13. The system of claim 1, wherein:execution of the programming by one or more processors of the system further configures the system to perform the following functions:generate the patient timeline based on the patient appointment report via a machine learning model;train the machine learning model based upon the patient timeline, the patient appointment report, and the reward, producing a revised machine learning model; generate an additional patient timeline based on an additional patient appointment report via the revised machine learning model; andthe additional patient timeline is unequal to the patient timeline.

14. A method, compri sing :receiving, at a health record server, a patient appointment report, the patient appointment report including a health outcome of a patient;determining a patient appointment code based upon the patient appointment report; retrieving a timeline code from a patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient;selecting a reward from a reward list, the reward selected based upon the timeline code and the health outcome; anddispensing the reward to the patient.

15. The method of claim 14, further comprising:receiving, at the health record server, a major event report;based on the major event report, producing a parent timeline and a child timeline; receiving a child appointment report, the child appointment report including a child health outcome of a child of the patient;determining a child appointment code based upon the child appointment report; retrieving a child timeline code from the child timeline, the child timeline code associated with the child appointment code and the child timeline associated with the patient;selecting a child reward from the reward list, the child reward selected based upon the child timeline code and the child health outcome; anddispensing the child reward to the patient.Attorney Docket No. H5776-0007016. The method of claim 15, further comprising:retrieving a parent timeline code from the parent timeline, the parent timeline code associated with the patient appointment code and the parent timeline associated with the patient;selecting a parent reward from the reward list, the parent reward selected based upon the parent timeline code and the health outcome; anddispensing the parent reward to the patient.

17. The method of claim 14, wherein:the health outcome is obtained by a biometric sensor of a provider device; and the patient appointment report is transmitted in response to the health outcome being obtained by the biometric sensor.

18. The method of claim 14, further comprising:transmitting a patient educational lesson to the patient;transmitting a patient educational assessment to the patient;receiving a patient educational assessment outcome based on the patient educational assessment;selecting an educational reward from the reward list, the educational reward selected based upon the patient educational assessment outcome; anddispensing the educational reward to the patient.

19. The method of claim 14, further comprising:incrementing a point total associated with the patient by a numerical point value associated with the reward;selecting a tiered reward from a tiered reward list, the tiered reward selected based upon the point total; anddispensing the tiered reward to the patient.

20. A non-transitory computer-readable medium storing instructions executable by a processor to perform a method comprising:receiving, at a health record server, a patient appointment report, the patient appointment report including a health outcome of a patient;Attorney Docket No. H5776-00070determining a patient appointment code based upon the patient appointment report; retrieving a timeline code from a patient timeline, the timeline code associated with the patient appointment code and the patient timeline associated with the patient;selecting a reward from a reward list, the reward selected based upon the timeline code and the health outcome; anddispensing the reward to the patient.