Software application that supports patient-driven healthcare

Abstract

Implementations of a healthcare software system interact with user(s) and / or healthcare provider(s) to permit secure access to patient healthcare data and support user-driven functionality. A user (patient) can interact with the healthcare software system via an application implemented at a user system. The healthcare software system can aggregate the user's health data from a variety of sources. The healthcare application can interact with the user to support user-driven healthcare, such as prompting care plan actions and / or medication actions, triggering health metric monitoring, generating user notes related to the user's healthcare, integrating questionnaires, defining and enforcing health data access permissions and restrictions, and the like.

Description

ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01PCT PATENT APPLICATION FORSOFTWARE APPLICATION THAT SUPPORTS PATIENT-DRIVEN HEALTHCAREPREPARED BY:POTOMAC LAW GROUP, PLLCASSIGNEE: ORACLE INTERNATIONAL CORORATION500 ORACLE PARKWAY REDWOOD SHORES, CA 94065ORC25139524-WO-PCT - 1 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01SOFTWARE APPLICATION THAT SUPPORTS PATIENT-DRIVEN HEALTHCAREFIELD

[0001] The embodiments of the present disclosure generally relate to a patient healthcare application for interacting with patients and healthcare providers.BACKGROUND

[0002] Electronic health records have digitized patient healthcare, but have also generated volumes of health data. As data grows in size, the technological challenges related to efficiently managing secure data has become increasingly complex. For example, implementing privacy and security protocols for health data and sharing health data among multiple parties continues to pose technological challenges. It is particularly important for patients to access, interact, and generally manage their health data, yet the software that accomplishes these patient functions continues to suffer from friction points. Healthcare systems that permit efficient and practical mechanisms for users to interact with their health data can substantially improve the healthcare industry.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Further embodiments, details, advantages, and modifications will become apparent from the following detailed description of the preferred embodiments, which is to be taken in conjunction with the accompanying drawings.

[0004] Fig. 1 illustrates a conceptual framework for implementation of a healthcare application according to an example embodiment.ORC25139524-WO-PCT - 2 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0005] Fig. 2 illustrates a block diagram of a computing device operatively coupled to a healthcare application according to an example embodiment.

[0006] Fig. 3 illustrates a system that implements a patient healthcare application for interacting with user(s) and health service provider(s) according to an example embodiment.

[0007] Fig. 4 illustrates a system that implements a patient record and interactions with health system(s) according to an example embodiment.

[0008] Fig. 5 illustrates system components that support interactions between a patient health record and provider system(s) according to an example embodiment.

[0009] Figs. 6A-6F illustrate example user interface visualizations for a healthcare application that support patient input for tracking health data according to an example embodiment.

[0010] Figs. 7A and 7B illustrate example user interface visualizations for a healthcare application that support input for tracking dependent’s health data according to an example embodiment.

[0011] Figs. 8A-8F illustrate example user interface visualizations for a healthcare application that support care plan execution according to an example embodiment.

[0012] Fig. 9 illustrates a flow diagram for interacting with a user via a patient healthcare application according to an example embodiment.

[0013] Fig. 10 illustrates a flow diagram for updating electronic health record(s) with care plan data from a user’s personal health record according to an example embodiment.ORC25139524-WO-PCT - 3 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01DETAILED DESCRIPTION:

[0014] Implementations of a healthcare software system interact with user(s) and / or healthcare provider(s) to permit secure access to patient healthcare data and support user-driven functionality. A user (patient) can be registered with a healthcare software system such that the user’s health data is managed by the system. The user can interact with the healthcare software system via an application implemented at a user system (e.g., smartphone, laptop, tablet, personal device, etc.). The healthcare software system can aggregate the user’s health data from a variety of sources, such as from user-provided notes, user health metrics monitored via the healthcare application, electronic health records, third-party healthcare provider systems, or any other suitable source of patient health data. In some implementations, the healthcare application can store this aggregated user health data as a personal health record.

[0015] A personal health record can store health data about the user that is accessible by the user. In this example, because the user has unlimited authority to view their own health data, the personal health record can aggregate different types of health data from different sources. In some implementations, aspects of health data from the personal health record can be selectively shared with other systems and / or health records. For example, data from the personal health record can be selectively shared to electronic health record(s), provider system(s), or any other suitable system or record.

[0016] The health data aggregated at the personal health record can include care plan(s), such as a plan generated by a user’s clinician and / or care team that supports the user’s healthcare. The care plan can include actions and guidance for thoseORC25139524-WO-PCT - 4 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 actions, such as taking medications, performing physical therapy, tracking health metric(s), and the like. In some implementations, the healthcare application can interact with the user to support care plan implementation and other user-driven healthcare, such as prompting care plan actions and / or medication actions, guiding health metric monitoring, generating user notes related to the user’s healthcare, integrating questionnaires, defining and enforcing health data access permissions and restrictions, and the like.

[0017] Reference will now be made in detail to the embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments. Wherever possible, like reference numbers will be used for like elements.

[0018] Fig. 1 illustrates a conceptual framework for implementation of a healthcare application according to an example embodiment. Diagram 100 includes healthcare software 102, user 104, service provider 106, patient note(s) 108, electronic health record information 110, and health metric information 112. Healthcare software 102 can include an interface with user 104, such as a healthcare application loaded to a user system, and an interface with service provider 106, such as an interface with external health systems, electronic health record systems, and the like.ORC25139524-WO-PCT - 5 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0019] User 104 can be a patient, a representative for a patient (e.g., guardian, proxy, legal representative, identified representative, etc.), and the like. User 104 can interact with healthcare software 102 via the user-facing healthcare application to actively manage the user’s healthcare. For example, user 104 can generate patient note(s) 108 that provide the user’s input and / or experiences related to healthcare (e.g., natural language notes). For example, patient note(s) 108 can comprise part of a patient journal for the user.

[0020] Health metric information 112 can be measured, monitored, and / or input health metric values from user 104. For example, user 104 can measure a health metric (e.g., blood pressure, heart rate, glucose level, weight, etc.) and manually enter health metric information 112. In another example, a monitoring device can monitor health metric(s) user 104, and health metric information 112 can be obtained from the monitoring device. Electronic health record information 110 can be health data aggregated from electronic health records. For example, service provider 106 can represent a system of a healthcare provider (e.g., hospital system) and / or an electronic health record system. Healthcare software 102 can aggregate electronic health record information 110 from a variety of health data sources.

[0021] In some implementations, data aggregated for the user-facing application of healthcare software 102 (e.g., patient note(s) 108, electronic health record information 110, and health metric information 112, etc.) can comprise a personal health record for user 104. For example, user 104 can be permitted access to any of the user’s own health data, and thus user 104 can readily view the health data aggregated for the user’s personal health record.ORC25139524-WO-PCT - 6 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0022] The user-facing application of healthcare software 102 can support user- driven healthcare. For example, the healthcare application can base used to document notes or questions about the patient’s health or healthcare, track the patient’s health metrics / vitals (e.g., track existing health metrics defined for the patient and add new health metrics), monitor the patient’s care plans, prompt patient action for defined healthcare plans and / or medications, integrate questionnaires about patient care, and the like.

[0023] In some implementations, the healthcare application can be a portal for the patient’s healthcare. Consumers and patients of care often have questions about their health and receive information about their health in a variety of settings. These consumers / patients can benefit from a central location to document their health questions and information. While in a clinic, urgent care, or hospital, a doctor may share health information with the patient and the patient may want to document the information so they can review it at a later date and / or use it to manage their health. The consumers / patients can edit or remove an existing patient note. In some implementations, additional context about their current health history (e.g., health conditions, allergies, medications, immunizations, procedures), test results, vitals, and documents can be integrated into the patient notes.

[0024] The consumers / patients can also track health metrics (e.g. blood pressure, blood glucose, steps, sleep, etc.), and the tracked health metric(s) can be integrated into patient notes. Patient notes can also be viewed in chronological order (filtered in ascending or descending order), queried, filtered based on health history information or health metric(s) added, and the like. Within a given patient note, a consumer / patientORC25139524-WO-PCT - 7 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 can add a title, manage font (e.g., bold, italic, underline, size, etc.), input free text, create a list with checkboxes, upload images, apply informational tags, and more. The consumer / patient can also associate a note with a particular health visit. Notes can be printed, downloaded, saved to a local device, and / or shared. For example, the consumer / patient can share the note through secure messaging to their doctor, clinician, family, and the like. Patient notes can also be applied to patients participating in a clinical trial, where patient notes can be shared with a clinical research organization as part of the clinical trial.

[0025] In some implementations, consumers / patients can, via the healthcare application, opt into a care plan that has been prescribed by their doctor or clinician, such as care plan imported / aggregated from an electronic health record. The clinician can assign the care plan, design it to allow the consumer / patient to interact with the care plan, allow a patient to voluntarily subscribe to a care plan where they can measure their steps / weight / vitals to improve their general health, and the like. An example care plan can define health activities and frequency for these activities, such as measure your weight everyday when you wake up for your CHF condition. The healthcare application can prompt a care plan action based on a frequence (e.g., daily) that reminds the user to perform this health activity at the defined frequency. In some implementations, a user can be prompted to enroll in a healthcare service that provides such care plan functionality when it is detected that the user is not already enrolled.

[0026] The doctor or clinician can also set thresholds to which if a monitored health metric exceeds a certain range, the patient / consumer can be alerted within their healthcare application, such as an alert to take action (e.g., eat food, sit down, seekORC25139524-WO-PCT - 8 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 medical attention, etc.) or schedule a healthcare appointment. The alert message can be customizable by the doctor or clinician.

[0027] A patient / consumer can integrate their medications (e.g., imported or aggregated from electronic health records and / or systems) with the healthcare application. The integrated medications can include medication facts (e.g., name, active ingredient, etc.), directions for use, schedule for taking the medication, time to stop the medication, risks and / or thresholds to not exceed, and the like. A medication action, such as a prompt to take a medication, can be surfaced through an activity log for upcoming activity or next best actions. The medication reminders can be consistent with regulatory and compliance regulations.

[0028] In addition, to engage in care that a doctor has prescribed (e.g., following a care plan, exercise or diet plan, physical therapy, etc.), patients can benefit from a central location to document their health metric(s) and an application that prompts actions related to their care plans. Within a prescribed or subscribed care plan, the consumer / patient can input health metric information (e.g. blood pressure, blood glucose, steps, sleep, etc.) to contribute to the care plan. The consumer / patient can manually identify the vital, add a free text value, click + or - to identify the value, and the like. The consumer / patient can also connect a device (e.g., via Oauth 2.0, Bluetooth, etc.), such as a fitness wearable device, approved medical device, smartwatch, blood monitor, etc., and the healthcare application can obtain user health metric(s) monitored via the device. In another example, the healthcare application can access a third-party application (e.g., fitness application, health application, etc.) that tracks user metric(s) to obtain these metric(s). In some implementations, a user can opt to delete and / orORC25139524-WO-PCT - 9 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 disable sharing with a previously approved device or health application. The health data associated with the removed device / application can be retained, deleted, or a combination thereof.

[0029] The healthcare application can also provide an efficient mechanism for interacting with a care team and / or health system. For example, health systems, at times, expose questionnaires to a patient based on their care and compliance to their care plan. Questionnaires can be created by a healthcare organization and exposed to the consumer. The questionnaires can be part of the care plan or integrated into the patient notes / patient journal. In one example, a care plan can include questions related to the user’s mental health, and the care team of the patient / consumer can review the answers to the questionnaire as part of the care plan. In another example, a campaign questionnaire can be posed to a patient base, such as patients that have been diagnosed with a similar condition. Such a questionnaire can address issues related to specific conditions and / or gauge care for these conditions. In some implementations, a questionnaire can determine if a patient / consumer has received a recent wellness visit, and if not can schedule this visit.

[0030] In some implementations, a patient / consumer can add context to a patient note related to a doctor visit, such as context related to the care team, billing issues, and other suitable visit details. The patient / consumer can also view information about their care team via the healthcare application. For example, the care team can be assigned based on recent visits or attribution configured by a healthcare organization, and specific information about the care team can be imported / aggregated from the healthcare organization’s systems.ORC25139524-WO-PCT - 10 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0031] Fig. 2 is a block diagram of a computer server / system 210 in accordance with embodiments. As shown in Fig. 2, system 210 may include a bus device 212 and / or other communication mechanism(s) configured to communicate information between the various components of system 210, such as processor 222 and memory 214. In addition, communication device 220 may enable connectivity between processor 222 and other devices by encoding data to be sent from processor 222 to another device over a network (not shown) and decoding data received from another system over the network for processor 222.

[0032] For example, communication device 220 may include a network interface card that is configured to provide wireless network communications. A variety of wireless communication techniques may be used including infrared, radio, Bluetooth®, Wi-Fi, and / or cellular communications. Alternatively, communication device 220 may be configured to provide wired network connection(s), such as an Ethernet connection.

[0033] Processor 222 may include one or more general or specific purpose processors to perform computation and control functions of system 210. Processor 222 may include a single integrated circuit, such as a micro-processing device, or may include multiple integrated circuit devices and / or circuit boards working in cooperation to accomplish the functions of processor 222. In addition, processor 222 may execute computer programs, such as operating system 215, healthcare application 216, and other applications 218, stored within memory 214.

[0034] System 210 may include memory 214 for storing information and instructions for execution by processor 222. Memory 214 may contain various components for retrieving, presenting, modifying, and storing data. For example, memory 214 mayORC25139524-WO-PCT - 11 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 store software modules that provide functionality when executed by processor 222. The modules can include an operating system 215, healthcare application 216, as well as other applications modules 218. Operating system 215 provides operating system functionality for system 210. Healthcare application 216 may provide healthcare functionality for a user and / or a provider, or may further provide any other functionality of this disclosure. In some instances, healthcare application 216 may be implemented as an in-memory configuration.

[0035] Non-transitory memory 214 may include a variety of computer-readable medium that may be accessed by processor 222. For example, memory 214 may include any combination of random access memory (“RAM”), dynamic RAM (“DRAM”), static RAM (“SRAM”), read only memory (“ROM”), flash memory, cache memory, and / or any other type of non-transitory computer-readable medium.

[0036] Processor 222 is further coupled via bus 212 to a display 224, such as a Liquid Crystal Display (“LCD”). A keyboard 226 and a cursor control device 228, such as a computer mouse, are further coupled to communication device 212 to enable a user to interface with system 210. In some embodiments, system 210 can be part of a larger system. Therefore, system 210 can include one or more additional functional modules 218 to include the additional functionality. Other applications modules 218 may include the various modules of Oracle® Health, Oracle® Data Integrator, Oracle® Cloud Infrastructure, Oracle® Autonomous Database, Oracle® Cerner®, Oracle® Cerner® Millennium, Oracle® Cerner® Healthelntent, Oracle® Cerner® Seamless Exchange, Oracle® Cerner® HealtheCare, Oracle® Blockchain and Oracle® Cerner®HealtheLife, Oracle® Health Patient Portal, Oracle® Health Patient Portal (cloudORC25139524-WO-PCT - 12 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 service), Oracle® Health Patient Administration (cloud service), Oracle® Health EHR, and representative products across the Oracle® Health & Artificial Intelligence platform, for example.

[0037] A database 217 is coupled to bus 212 to provide centralized storage for modules 216 and 218 and to store, for example, wireless device activity, and in some embodiments, user profiles, transactions history, etc. Database 217 can store data in an integrated collection of logically-related records or files. Database 217 can be an operational database, an analytical database, a data warehouse, a distributed database, an end-user database, an external database, a navigational database, an inmemory database, a document-oriented database, a real-time database, a relational database, an object-oriented database, Hadoop Distributed File System (“HFDS”), or any other database known in the art.

[0038] Although shown as a single system, the functionality of system 210 may be implemented as a distributed system. For example, memory 214 and processor 222 may be distributed across multiple different computers that collectively represent system 210. In one embodiment, system 210 may be part of a device (e.g., smartphone, tablet, computer, etc.).

[0039] In an embodiment, system 210 may be separate from the device, and may remotely provide the described functionality for the device. Further, one or more components of system 210 may not be included. For example, for functionality as a user or consumer device, system 210 may be a smartphone or other wireless device that includes a processor, memory, and a display, does not include one or more of theORC25139524-WO-PCT - 13 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 other components shown in Fig. 2, and includes additional components not shown in Fig. 2.

[0040] Fig. 3 illustrates a system that implements a patient healthcare application for interacting with user(s) and health service provider(s) according to an example embodiment. System 300 illustrates cloud system 302, user system 304, provider system 306, monitoring device 308, and healthcare application data 310. A user, such as user 104 of Fig. 1 , can, via user system 304, interact with a healthcare application hosted by cloud system 302, such as a healthcare application implemented by healthcare software 102 of Fig. 1 . Cloud system 302 can interact with external computing systems, such as provider system 306, to connect the implemented healthcare software to third-party computing systems (e.g., hospital systems,), electronic health record systems, and any other suitable computing systems related to health data. Monitoring device 308 can be any suitable device (e.g., wearable device, patch, smartwatch, smart ring, blood pressure cuff, glucose monitor, food and drug administration approved device, etc.) configured to monitor health metrics for a user.For example, the monitoring device can monitor user metric(s) at any suitable frequency and communicate with the healthcare application (e.g., executing at the user’s mobile device) to securely share data for the monitored health metric(s). In some implementations, the data for the monitored health metric(s) can comprise any suitable granularity and / or the healthcare application can analyze the data and alter the data to meet a granularity defined via a care plan. The monitoring device and healthcare application can communicate via any suitable secure communication protocol (e.g., via device and / or user authentication).ORC25139524-WO-PCT - 14 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0041] Cloud system 302 can aggregate healthcare application data 310, including: patient notes generated by a user (e.g., via interactions with user system 304); medication information accessed from a third-party healthcare system and / or electronic health record (e.g., accessed from provider system 306); healthcare plan information accessed from a third-party healthcare system and / or electronic health record (e.g., accessed from provider system 306); health metric(s) monitored via user system 304 and / or monitoring device 308, or accessed from a third-party healthcare system and / or electronic health record (e.g., accessed from provider system 306); and any other suitable electronic health record data. One or more patient identifiers (e.g., global identifier, master-patient index identifier, etc.) can be used to aggregate health data for a given patient from different sources. Cloud system 302 can apply deduplication techniques to deduplicate healthcare application data 310 aggregated from different sources, such as merge data and / or select an instance of the duplicate data for storage.

[0042] Healthcare application data 310, such as data aggregated from disparate sources (e.g., electronic health records, patient notes, monitored health metrics, etc.) can be organized according to a data schema. For example, data aggregated from electronic health records can include segments of health data, such as: originating or attributed physician and / or medical organization (e.g., entity names or identifier(s)), type of information (e.g., medications, tests and results, medical history, family history, biometrics, physician and patient communications, physician notes, patient notes, vaccine information, allergies, etc.), relevant health practice (e.g., cardiology, primary care, neurology, oncology, etc.), images (e.g., radiology scans, x-rays, ultrasound images, MRI images, and the like), date of information origination, electronic healthORC25139524-WO-PCT - 15 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 record format, other Health Level Seven (HL7), Fast Healthcare Interoperability Resource (FHIR), and / or Substitute Medial Applications and Reusable Technologies (SMART) on FHIR data parameters, or any other suitable health data parameters. In some embodiments, segments can include structured and unstructured data.

[0043] The user (e.g., via a healthcare application implemented by user system 304) and / or a provider (e.g., via provider system 306) can query the healthcare software implemented by cloud system 302 (e.g., healthcare application data 310) by issuing a query request comprising query parameters. For example, the query parameters can specify segment dimensions / dimension values, such as: originating physician and / or medical organization - ALL; types - medications, tests and results, medical history, family history, biometrics, vaccine information, and allergies; relevant health practices - cardiology, primary care physician, and neurology; date of information origination - ALL; and electronic health record format - ALL. Other example segment dimension values for date of information include past two years, past year, since the age of 18, custom time range (e.g., Jan. 1 - 31 , 2023), etc. Healthcare application data 310 comprising segment dimension / dimension values from the query parameters can be returned in response to the query.

[0044] In some implementations, patient notes can comprise informational tags, such as tags that indicate health data parameters related to the note. Example informational tags include segment dimensions and / or dimension values, health condition identifier(s), healthcare visit identifier(s), doctor identifier(s), date and / or time, medications, monitored health metric(s), and the like. A query can match a given patient note when its parameters match one or more of the patient note’s informational tags.ORC25139524-WO-PCT - 16 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0045] In some implementations, healthcare application data 310 can be secured.For example, user system 304 and the implemented healthcare application can perform user authentication (e.g., biometric scanning, two-factor authentication, etc.) to authenticate the identity of the user. Authenticated users can be permitted scope limited access to healthcare application data 310. A given user / patient can also define sharing permissions for sharing healthcare application data 310 of the user / patient with others. For example, a user / patient can define limited portions of the healthcare application data 310 to share with a guardian, legal representative, or other identity. In another example, the user / patient can mark portions of the healthcare application data 310 to restrict from sharing with the guardian, legal representative, or other identity.

[0046] In an example, a user registered with healthcare software can comprise a care plan that the user is prescribed and / or to which the user subscribes. For example, a doctor can define the care plan, such as in response to one or more visits, via an electronic health record, and the healthcare software can receive / retrieve the care plan for the user from a computing system associated with the doctor’s office and / or affiliated hospital, or from a computing system that implements the electronic health record that comprises the defined care plan.

[0047] In an example, the care plan can comprise: one or more prescribed health metric(s) for monitoring, one or more prescribed medications, one or more prescribed user actions, and any other suitable care plan information. The user can subscribe to the care plan and view the care plan via a healthcare application that is part of (or interacts with) implementations of the healthcare software. Subscribing to a care plan can be optional for the user. In some implementations, the healthcare application canORC25139524-WO-PCT - 17 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 prompt the user to monitor the prescribed health metric(s) according to a schedule defined in the care plan (e.g., 8:00 am every morning, etc.), and the user can log / enter this health metric(s) data via the healthcare application. In another example, the healthcare application can cause a monitoring device to monitor the health metric(s) and / or can retrieve the user’s health metric(s) stored at the device, where the monitored health metric(s) received / retrieved from the device are in accordance with the schedule defined in the care plan. The user and / or healthcare application can save / store this information (e.g., health metric information) in association with the particular prescribed / subscribed care plan related to the information.

[0048] The healthcare application can also prompt the user to perform medication actions, such as take one or more prescribed medications according to the dosage and schedule defined in the care plan. The healthcare application can also prompt the user to perform defined actions from the care plan, such as physical therapy, exercise, rest, and the like, in accordance with a schedule defined in the care plan. In an example, the care plan may relate to recovery from a surgery, the one or more prescribed health metric(s) for monitoring may relate to risks post-surgery (e.g., weight, blood pressure, blood glucose level, blood oxygen, heartrate, etc.), the one or more prescribed medications may relate to post-surgery conditions (e.g., pain medication, blood medications, etc.), and the one or more prescribed user actions may relate to postsurgery recommended actions (e.g., rest, physical therapy, exercise, diet, etc.). The user can generate patient notes that represent the user’s experience post-surgery, such as the user’s mental state, pain level, appetite, etc. The user and / or healthcareORC25139524-WO-PCT - 18 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 application can save / store these patient notes in association with the particular prescribed / subscribed care plan related to the patient notes.

[0049] In some scenarios, doctors or other clinicians that are part of the user’s care team can review the patient notes, monitored health metric(s), and other health data managed by the healthcare software related to the care plan to support the user’s care. For example, selection portion(s) of the user’s patient notes and / or monitored health metric(s) can be shared with provider system(s) such that these portions can be reviewed by doctors or other clinicians. Descriptions with respect to Fig. 5 further describe sharing selection portions of a patient’s personal health record. Health metric(s) outside a range or that fail to meet a criteria can be flagged by the care team. The user can be issued changes to medications (e.g., higher dose, new medications, different medications, etc.), changes to prescribed health metric(s) for monitoring (e.g., increased frequence, additional health metric(s) for monitoring, etc.), changes to prescribed user actions (e.g., less strenuous physical therapy schedule, more rest, etc.), and the like.

[0050] In this example, the changes to the user’s care plan can be communicated to the user via the healthcare application. For example, the care plan for the patient can be adjusted, such as via a provider system and / or electronic health record. This adjust care plan can be pushed to healthcare application data 310 (e.g., a personal health record) and / or pulled from the provider system and / or electronic health record. The user can be offered a consultation with the care team to review the changes.

[0051] In some implementations, a user’s care team can interact with the user via the healthcare application to implement changes to the user’s prescribed medication.ORC25139524-WO-PCT - 19 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01For example, secure messages between the user and the care team can confirm the user’s pharmacy, confirm the user’s understanding of the new medication(s) and / or changes to the existing medications(s), and / or schedule a consultation with the user to review the changes. A doctor from the user’s care team can then trigger a new medication and / or changes to existing medication(s) via updates to the user’s electronic health record(s), which can cause prescription information to be pushed to the user’s preferred pharmacy.

[0052] In some scenarios, a user can provide feedback related to a care plan via the healthcare application. For example, the user can indicate, via the healthcare application, a reduced dosage for a medication or elimination of a medication. The user’s care team (e.g., a doctor) can review this user feedback and implement changes to the care plan or maintain the care plan. For example, the doctor can adopt the user’s changed behavior and reduce the dosage of a medication or eliminate the medication. In another example, the doctor can oppose the user’s changed behavior and instruct the user to resume the medication according to the care plan. Medication changes adopted by the doctor can be pushed to the user’s preferred pharmacy via updates to the user’s electronic health records.

[0053] Implementations can utilize one or more machine learning model(s) to analyze health data, such as data stored via a user’s personal health record. A "machine learning model," as used herein, refers to a construct that is configured (e.g., trained using training data) to make predictions, provide probabilities, augment data, and / or generate data. For example, training data for supervised learning can include items with various parameters and an assigned classification. A new data item canORC25139524-WO-PCT - 20 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 have parameters that a model can use to assign a classification to the new data item. Machine learning models can be configured for various situations, data types, sources, and output formats.

[0054] Training data can be any set of data capable of training machine learning model(s), such as a set of features with corresponding labels for supervised learning. Training data can be used to train machine learning model(s) to generate trained machine learning model(s). For example, any suitable training technique (e.g., supervised training via gradient descent, unsupervised training, etc.) can be used to update a configuration of machine learning model(s) (e.g., train the weights of a machine learning model) using training data.

[0055] The architecture of implemented machine learning model(s) can include any suitable machine learning model components. For example, a neural network can be implemented along with a given cost function (e.g., for training / gradient calculation). The neural network can include any number of hidden layers (e.g., 0, 1 , 2, 3, or many more), and can include feed forward neural networks, recurrent neural networks, convolution neural networks, transformer networks, encoder-decoder architectures, large language model(s), and any other suitable type. In some implementations, the neural network can be configured for deep learning, for example based on the number of hidden layers implemented.

[0056] In some implementations, machine learning model(s) can be an ensemble learning model. Multiple models can be stacked, for example with the output of a first model feeding into the input of a second model. Some implementations can include a number of layers of prediction models. In some implementations, features utilized byORC25139524-WO-PCT - 21 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 machine learning model(s) can also be determined, for example via any suitable feature engineering techniques.

[0057] In some implementations, the design of machine learning model(s) can be tuned during training, retraining, and / or updated training. For example, tuning can include adjusting a number of hidden layers in a neural network, adjusting a kernel calculation used to implement a support vector machine, and the like. This tuning can also include adjusting / selecting features used by the machine learning model(s).Various tuning configurations (e.g., different versions of the machine learning model and features) can be implemented while training in order to arrive at a configuration for machine learning model(s) that, when trained, achieves desired performance (e.g., performs predictions at a desired level of accuracy, run according to desired resource utilization / time metrics, and the like). Retraining and updating the training can include training with updated training data. For example, the training data can be updated to incorporate observed data, or data that has otherwise been labeled (e.g., for use with supervised learning).

[0058] Implementations can fine-tune large language model(s) with domain specific language data. For example, historical health data can be aggregated to generate a set of training data specific to healthcare. A pre-trained large language model can be finetuned with the set of training data to generate a large language model configured for health data. For example, one or more layers, nodes, weights, etc. of the pre-trained large language model can be updated and / or added via the fine-tuning to configure the large language model for health data. In some implementations, the fine-tuned largeORC25139524-WO-PCT - 22 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 language model can be prompted to analyze health data and return results (e.g., data visualizations, tables of data, answers to queries, etc.).

[0059] In some examples, the healthcare software can automatically flag conditions and / or suggest changes to the user’s care plan based on the data being generated related to the care plan. For example, natural language processing models can process the user’s patient notes, and certain sentiment can be mapped to predefined recommendations, such as reducing the intensity of physical therapy when the patient’s reported pain is high, recommending a patient consultation when the patient notes indicate confusion with the care plan, triggering an alert that schedules a patient consultation when monitored health metric(s) fail to meet a criteria, and the like.

[0060] Machine learning models and / or artificial intelligence can be implemented to process the user’s health data and / or the data being generated related to a care plan to flag conditions and / or suggest changes. For example, monitored metric(s) can be processed by the model(s), patient notes can be processed by the model(s), data generated via a user visit to a hospital / doctor’s office can be processed by the model(s), and any other suitable user health data can be processed by the model(s). The model(s), based on the processing, can generate recommended changes to the care plan and / or raise flags for care team review.

[0061] Fig. 4 illustrates a system that implements a patient record and interactions with health system(s) according to an example embodiment. Diagram 400 includes personal health record 402, health system 404, health system 406, and patient data 408. In some implementations, health system 404 can be computing system(s) associated with a first health care service provider and health systems 406 can beORC25139524-WO-PCT - 23 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 computing system(s) associated with a second health care service provider. Personal health record 402 can be implemented by a cloud system (e.g., cloud system 302 of Fig. 3, or any other suitable cloud system), and a user-facing healthcare application can permit a user to manage personal health record 402.

[0062] Personal health record 402 can comprise patient data 408, such as data input via a patient (e.g., patient notes, manually entered health metric(s), questions, etc.), health metric(s) or other health data obtained via monitoring devices (e.g., consumer device, medical devices, etc.), health data aggregated via various sources (e.g., electronic health record(s), etc.), or any other suitable health data for a patient.

[0063] Health systems 404 and / or 406 can interact with personal health record 402 such that selective health data for the patient can be shared among the system(s). For example, the user can select certain data elements from personal health record 402 (e.g., monitored health metric(s), question, etc.) to share with health systems 404 and / or 406. For example, because personal health record 402 is scoped to be accessed by the user, the record can contain a variety of health data for the user aggregated from many different sources. However, health systems 404 and / or 406 can be accessed by many individuals, such as different healthcare teams for the user, and thus the user can opt to share select portions of personal health record 402 with either or both of health systems 404 and / or 406.

[0064] In some implementations, portions of personal health record 402 can be sourced from health system 404 and shared back with health system 406. For example, a healthcare team affiliated with health system 404 may have provided care for the user, and personal health record 402 may have aggregated health dataORC25139524-WO-PCT - 24 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 generated based on this care (e.g., sourced from an electronic health record associated with health system 404). In this example, the user can select this health data and share it with health system 406, for example to support care being provided by a healthcare team affiliated with health system 406. In some implementations, selectively sharing health data among personal health record 402, health system 404, and health system 406 can involve interactions with one or more electronic health records.

[0065] Fig. 5 illustrates system components that support interactions between a patient health record and provider system(s) according to an example embodiment. Diagram 500 illustrates healthcare software 502, patient provided data 504, device and application data 506, payer data 508, interface for provider 510, electronic health record 512, clinical data 514, interface for provider 516, electronic health record 518, clinical data 520. Communications among the components of diagram 500 can utilize any suitable secure communication and / or authentication protocol to maintain the security of the health data being communicated.

[0066] Healthcare software 502 can be implemented at a cloud system and can host a personal health record for a user. For example, patient provided data 504 (e.g., provided via a user-facing healthcare application) can be stored as part of the personal health record, such as patient notes, patient entered health metric(s), questions, and the like. In addition, device and application data 506 can comprise data monitored via one or more monitoring devices and / or one or more elements of software (e.g., third-party software) configured to monitor a user’s health metric(s), such as user health metrics (e.g., blood pressure, heartrate, blood oxygen level, blood sugar, etc.), nutrition information tracked via third-party applications, activity level tracked via third-partyORC25139524-WO-PCT - 25 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 applications (e.g., steps, exercise, etc.), and the like. Device and application data 506 can be received / obtained by healthcare software 502 and stored as part of the personal health record. Payer data 508 can include user insurance data and / or healthcare account data (e.g., health spending account, flexible spending account, etc.) received / obtained by healthcare software 502 and stored as part of the personal health record.

[0067] In addition, portions of clinical data 514 (associated with a first healthcare provider) and portions of clinical data 520 (associated with a second healthcare provider) can be received / obtained by healthcare provider 502 and stored as part of the personal health record. For examples, the first healthcare provider may have provided historical or ongoing care for the user, and thus clinical data 514 about the user can be stored at electronic health record 512 (e.g., a record associated with the first healthcare provider). Similarly, the second healthcare provider may have also provided historical or ongoing care for the user, and thus clinical data 520 about the user can be stored at electronic health record 518 (e.g., a record associated with the second healthcare provider). Portions of electronic health record 512 can be provided to healthcare software 502 via patient interface for provider 510 (e.g., a patient portal for the first healthcare provider) and portions of electronic health record 518 can be provided to healthcare software 502 via patient interface for provider 516 (e.g., a patient portal for the second healthcare provider).

[0068] While several components of healthcare data can be aggregated via healthcare software 502 for storage at a personal health record for the user, updates from the personal health record back to electronic health record 512 and / or electronicORC25139524-WO-PCT - 26 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 health record 518 can be selective. For example, electronic health records can be managed by associated healthcare provider(s), and thus one or more care team members may review updates for an electronic health record prior to implementing an update. In some implementations, a user can, via a user-facing healthcare application, select elements of a user’s health data stored at a personal health record to share with a given healthcare service provider.

[0069] For example, healthcare software 502 may provide selected elements of a user’s health data from a personal health record to patient interface for provider 510, and one or more care team members associated with the first healthcare provider can review these elements of health data for inclusion at electronic health record 512.Similarly, healthcare software 502 may provide selected elements of a user’s health data from a personal health record to patient interface for provider 516, and one or more care team members associated with the second healthcare provider can review these elements of health data for inclusion at electronic health record 518. In some implementations, selection by the user of which elements of health data to share and review by care team members (of the healthcare providers) prior to updating electronic health records can ensure that a) the user manages what health data is shared, and b) that the care team members of the healthcare providers manage the specific electronic health records associated with each healthcare provider.

[0070] In some implementations, an element of health data that is part of a care plan stored at a given electronic health record and implemented by an associated healthcare provider can be added to the given electronic health record absent such reviews. For example, healthcare software 502 can generate an update for electronic health recordORC25139524-WO-PCT - 27 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01512 that comprises data for monitored health metric(s) subscribed by a care plan stored at electronic health record 512. In this example, because the health metric(s) have been subscribed by a care team of the associated healthcare provider, the data for the health metric(s) has already been approved for inclusion at electronic health record 512. Similarly, because the care team of the associated healthcare provider is implementing a care plan with the user (e.g., voluntarily accepted by the user), the user has provided consent to sharing this health metric(s) data with the healthcare provider. Accordingly, health data can flow from the personal health record to one or more electronic health records as part of a care plan implemented by healthcare provider(s).

[0071] In some implementations, the systems of Figs. 3, 4, and 5 can be implemented in combination with user interface visualizations of Figs 6A-6F, 7A, 7B, and 8A-8F. For example, a healthcare application and / or personal health record can be implemented to support user interactions based on a care plan for the user or based on any other suitable healthcare workflow. Figs. 6A-6F illustrate example user interface visualizations for a healthcare application that support patient input for tracking health data according to an example embodiment.

[0072] User interface 600A of Fig. 6A illustrates a user interface for interactions between a healthcare application and a user (e.g., the patient). User interface 600A is an example of an interface that obtains health data from a user (e.g., based on a subscribed / prescribed care plan) according to a defined frequency (e.g., daily, weekly, etc.). In the illustrated example, a user is prompted to provide the user’s weight and to answer question(s) related to the user’s mental health. For example, the user can select “what do you weight?” and input a weight via the user interface.ORC25139524-WO-PCT - 28 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0073] In some implementations, selection of “how are you feeling today?” can launch a workflow (e.g., according to the defined care plan) that prompts the user to answer a series of questions. User interfaces 600B, 600C, 600D, and 600E of Figs. 6B, 6C, 6D, and 6E illustrate interface components for the user to answer such a prompted question, such as providing: a numeric value for an anxiety level, a timing related to the anxiety level, other suitable parameters related to the anxiety (e.g., an explanation of what caused the anxiety), one or more symptoms related to the anxiety (e.g., shortness of breath, sweating, insomnia, palpitations, etc.), and the like.

[0074] Returning to user interface 600A of Fig. 6A, the user can also select “Add new symptom” to add health data related to a new symptom the user is experiencing. User interface 600F of Fig. 6F illustrates an interface in which a user can select / provide a new symptom (e.g., headache, cough, etc.). In an example, input via user interfaces 600A, 600B, 600C, 600D, 600E, and / or 600F can represent a user’s daily input with respect to a subscribed / prescribed care plan. For example, a healthcare provider (e.g., doctor, care team, etc.) may have defined health data components for the user to monitor (e.g., weight, anxiety related health, etc.), and the healthcare application can display prompts for the user to provide the information relevant to the care plan. The provided health data can be shared with computing systems associated with the healthcare provider such that healthcare team can review the user’s response and take clinical actions (e.g., maintain care plan, schedule an appointment, increase medication dose, etc.). In some implementations, a care plan can relate to an individual other than the user, such as a dependent.ORC25139524-WO-PCT - 29 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0075] For example, an individual can be authorized to access all or a portion of a personal health record for a patient, such as a guardian of a minor or other dependent, a family member, or any other suitable relationship where an individual is authorized to make healthcare decisions for a patient. This individual can, via interactions with a healthcare application, implement a care plan for the patient. Figs. 7A and 7B illustrate example user interface visualizations for a healthcare application that support input for tracking a dependent’s health data according to an example embodiment.

[0076] User interfaces 700A and 700B can be used to input, by a parent, guardian, or other suitable individual, health data for a child. For example, via a selection at user interface 700A, a workflow can be launched that displays user interface 700B. User interface 700B can be used to input feeding data for the child. In another example, via a selection at user interface 700A, a workflow can be launched that displays a user interface used to input details related to a diaper change for the child. In these examples, the input data about the child can be shared with a healthcare provider system, and a clinical team can review the data to make clinical decisions (e.g., schedule a doctor’s appointment, etc.).

[0077] In some implementations, a healthcare application can provide a summary that includes results of an appoint, care plan information for a user, and other suitable health information. Figs. 8A-8F illustrate example user interface visualizations for a healthcare application that support care plan execution according to an example embodiment.

[0078] User interface 800A of Fig. 8A can provide a summary after a doctor’s visit, such as care plan information prescribed by a care team and accepted by a patient,ORC25139524-WO-PCT - 30 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 goals for the care plan, and the like. User interface 800A displays health data for tracking during the care plan and goals for the care plan.

[0079] While implementing a care plan, a user-facing healthcare application can provide ongoing support. User interface 800B of Fig 8B displays a daily summary that implements a care plan for a user. User interface 800B provides prompts for when to track health data for the user (e.g., measure basal body temperature, track ovulation, etc.) and what actions to take (e.g., have intercourse). In addition, user interface 800B can also provide other prompts for the user, such as prompts to take ongoing medication. User interface 800C of Fig. 8C represents a state where the user has entered health data for the implemented care plan over a given day. This entered health data can be reviewed by the healthcare provider implementing the care plan to make additional clinical decisions.

[0080] User interface 800D of Fig. 8D illustrates a graph visualization of a health data monitored over an implemented care plan. This graph visualization can be displayed to a care team member of the healthcare provider and / or the user. The graph visualization can be used to assess compliance and / or effectiveness of an implemented care plan.

[0081] User interface 800E of Fig. 8E illustrates a messaging functionality of a userfacing healthcare application, where a user can message a care team member of a given healthcare provider. For example, the user may be permitted to message a) any care team member that is part of the user’s care plan, b) any care team member that has provided the user healthcare (e.g., across a defined time period), c) any care team member that is part of the clinical division treating the user (e.g., any fertility teamORC25139524-WO-PCT - 31 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 members), or any other suitable care team members for a given healthcare provider. In some implementations, messages can be reviewed by care team member and one or more alterations can be made to the implemented care plan. The example illustrated in user interface 800E indicates a care plan will be adjusted to track additional health data for the user.

[0082] Implementations can also analyze health data for a user (e.g., data stored as part of the user’s personal health record), and display results of the analysis to the user (or to a care team member). User interfaces 800F and 802F of Fig. 8F illustrate a query posed by a user and the health data results that match the query. For example, the user asked “show me my weight after taking [a medication]”. In this example, a care plan can be analyzed to identify a date at which the specific medication was started, and the user’s tracked weight can be displayed (e.g., as a graphical visualization and / or as a table) relative to this start date. User interface 802F also shows a source for each weight entry over the time period (e.g., journal entry vs measured via a clinical visit).

[0083] The example illustrated in user interfaces 800F and 802F also display explanation(s) for any changes in weight since starting the medication. In some implementations, a large language model can be prompted to return the information displayed via user interfaces 800F and 802F. For example, a user query can be converted to a prompt for a large language model, and the model can: analyze the care plan and / or personal health record of the user, and respond to the prompt by providing matching health information and / or additional information related to the matching health information and prompt (e.g., possible causes for weight loss).ORC25139524-WO-PCT - 32 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0084] Fig. 9 illustrates a flow diagram for interacting with a user via a patient healthcare application according to an example embodiment. In one embodiment, the functionality of Figs. 9 and 10 are implemented by software stored in memory or other computer-readable or tangible medium, and executed by a processor. In other embodiments, each functionality may be performed by hardware (e.g., through the use of an application specific integrated circuit (“ASIC”), a programmable gate array (“PGA”), a field programmable gate array (“FPGA”), etc.), or any combination of hardware and software. Process 900, at least in part, can be implemented via a healthcare application.

[0085] At block 902, process 900 can aggregate health data. For example, healthcare software can aggregate health data for a registered patient from a variety of sources, such as electronic health record systems, provider systems, other health software, user systems, monitoring device(s), and any other suitable health data sources. In some implementations, the aggregated health data for a particular patient can be stored as part of the patient’s personal health record. For example, a personal health record can store health data about the patient that is accessible by the patient. In this example, because the patient has unlimited authority to view their own health data, the personal health record can aggregate different types of health data from different sources.

[0086] At block 904, process 900 can store patient notes related to the patient. For example, the patient can generate, via interactions with a healthcare application that is part of or in communication with the healthcare software, notes related to the patient’s health. At least a portion of the patient notes can include metadata that comprises: aORC25139524-WO-PCT - 33 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 date and / or time, and informational tags. For example, the date and / or time can comprise a time stamp, and the information tags can represent the areas of the patient’s health and / or healthcare that are relevant to the patient note.

[0087] At block 906, process 900 can access care plan information for the patient. For example, the healthcare software can access care plan information for a care plan prescribed for the patient, such as a care plan developed by the patient’s clinicians and care team. A care plan can include tasks and / or actions for the patient’s care, such as taking medications, performing physical therapy, monitoring health metric(s), reporting symptoms, and the like. The care plan can also define frequencies for one or more of the tasks / actions (e.g., daily, twice a day, weekly, etc.). In some implementations, the care plan can be aggregated / retrieved from the patient’s electronic health record(s).

[0088] At block 908, process 900 can determine whether a patient action related to a care plan is to be prompted. For example, the care plan can define prescribed actions, such as prompting the user to monitor and record health metric(s) according to a schedule, causing the monitoring of health metric(s) via a monitoring device, prompting the user to perform other care plan actions (e.g., exercise, rest, physical therapy, water consumption, etc.) according to a schedule, and the like.

[0089] In some implementations, a prescribed action can be prompted in response to monitoring health metric(s). For example, health metric data for at least one health metric can be received from a monitoring device (e.g., blood pressure, heart rate, blood sugar level, weight, etc.). A prescribed action trigger can be partially met after health metric data is received from the patient, such as after a daily measurement.

[0090] In some implementations, an action is determined to be prompted when: anORC25139524-WO-PCT - 34 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 action is defined in the care plan, and a trigger criteria for the defined action is met (e.g., a defined schedule for the defined action indicates that action is due for prompting, monitored metric(s) and / or reported symptoms are within a range or characterize a user state such that the defined action is due for prompting, etc.). For example, a care plan can include patient criteria for monitored health metric(s), and a prescribed action can be prompted in response to a comparison between health metric data (e.g., received from at least one monitoring device) and the patient criteria (e.g., monitored health metric(s) falling withing a range). In some implementations, a prescribed action trigger may require receiving health metric data for at least one health metric, for example to ensure that the patient is in a state such that the prescribed action is a healthy action for the patient.

[0091] In some implementations, a patient note is automatically generated for the one or more prescribed actions. For example, a patient note can be automatically generated for a prescribed action that is prompted, and the patient can be further prompted to provide input about the prescribed action to complete the automatically generated patient note.

[0092] When it is determined that a patient action related to the care plan is to be prompted, process 900 progresses to block 910. When it is determined that a patient action related to the care plan is not to be prompted, the process 900 progresses to block 912.

[0093] At block 910, process 900 can prompt a care plan action. For example, the healthcare application can prompt the patient, via the patient’s device (e.g., smartphone) to take a prescribed action. Example prescribed actions includes: takingORC25139524-WO-PCT - 35 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 prescribed medication, performing prescribed physical therapy, eating or drinking a prescribed food or drink, or performing a manual action for monitoring one or more health metrics. In some implementations, the prescribed action can be performing prescribed physical therapy, and the user can be prompted to perform the prescribed physical therapy according to a physical therapy schedule defined in the care plan.

[0094] At bock 912, process 900 can access medication information for the user. For example, the healthcare software can access medication information related to a care plan prescribed for the patient, such as a care plan developed by the patient’s doctors and care team. In some implementations, the care plan and medication information can be aggregated / retrieved from the patient’s electronic health record(s).

[0095] At block 914, process 900 can determine whether a patient action related to medication is to be prompted. For example, the care plan can define medication actions, such as prompting the user to take one or more prescribed medications according to a defined dosage and frequence. A medication action is determined to be prompted when: a medication is defined in the care plan, and a defined schedule (e.g., frequency) for the medication indicates that medication is due for prompting. In some implementations, a medication action trigger may require receiving health metric data for at least one health metric, for example to ensure that the patient is in a state such that the prescribed medication is healthy for the patient.

[0096] When it is determined that a medication action related to the care plan is to be prompted, process 900 progresses to block 916. When it is determined that a medication action related to the care plan is not to be prompted, the process 900 progresses to block 918.ORC25139524-WO-PCT - 36 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01

[0097] At block 916, process 900 can prompt a medication action. For example, the healthcare application can prompt the patient, via the patient’s device (e.g., smartphone) to take medication according to the dosage and frequence defined in the patient’s care plan.

[0098] At block 918, process 900 can continue operating the healthcare application. For example, the healthcare application can, at a patient’s device, execute in the foreground, execute in the background, and / or switch to standby. The patient can interact with the healthcare application to view the patient’s healthcare data, generate patient notes, and / or otherwise manage the patient’s healthcare.

[0099] In some implementations, the patient record maintained by the healthcare application can be analyzed. For example, a request for analyzing the patient record can be received, the request comprising query parameters, lin response to the prompt and based on the query parameters, the patient record can be analyzed including one or more of: patient notes, medication information, care plan information, monitored health metric, or health data aggregated from the one or more electronic health records. In response to the analyzing, results can be returned. For example, the results can be health information that matches the query parameters, such as one or more of: portions of the patient notes, one or more medications defined by the medication information, portions of the care plan information, monitored health metric data, and portions of the aggregated electronic health data.

[0100] In some implementations, a trained machine learning model can perform the analyzing of the patient record. For example, the trained machine learning model can match the query parameters to the health information of the results. In someORC25139524-WO-PCT - 37 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 implementations, trained machine learning model can be a large language model, the query parameters can be a prompt for the large language model, and the matched results can be health information retrieved from the patient record by the large language model in response to the prompt. In some implementations, the query parameters can include a period of time and an identifier for the at least one health metric, and the results can be a graph representation or a chart representation of health metric data (e.g., received from the monitoring device) over the period of time. For example, the period of time can be defined relative to a date of: a prescribed medication (e.g., medication start date or alteration data), a prescribed care plan (e.g., care plan start date or alteration data), a medical procedure defined via the aggregated electronic health data, a health event defined via the aggregated electronic health data, or any combination thereof.

[0101] Fig. 10 illustrates a flow diagram for updating electronic health record(s) with care plan data from a user’s personal health record according to an example embodiment. Process 1000, at least in part, can be implemented via a healthcare application.

[0102] At block 1002, process 1000 can aggregate health data. For example, healthcare software can aggregate health data for registered patient(s) from a variety of sources, such as electronic health record systems, provider systems, other health software, user systems, monitoring device(s), and any other suitable health data sources. In some implementations, the aggregated health data for a particular patient can be stored as part of the patient’s personal health record. For example, a personal health record can store health data about the patient that is accessible by the patient.ORC25139524-WO-PCT - 38 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01In this example, because the patient has unlimited authority to view their own health data, the personal health record can aggregate different types of health data from different sources.

[0103] At block 1004, process 1000 can access a patient’s care plan. For example, the healthcare software can access care plan information for a care plan prescribed for the patient, such as a care plan developed by the patient’s clinicians and care team. A care plan can include tasks and / or actions for the patient’s care, such as taking medications, performing physical therapy, monitoring health metric(s), reporting symptoms, and the like. The care plan can also define frequencies for one or more of the tasks / actions (e.g., daily, twice a day, weekly, etc.). In some implementations, the care plan can be aggregated / retrieved from the patient’s electronic health record(s).

[0104] At block 1006, process 1000 can receive health data via the healthcare application. For example, health metric data for at least one health metric can be received from a monitoring device (e.g., blood pressure, heart rate, blood sugar level, weight, etc.). In some implementations, the received health metric data can be received as part of a care plan implemented for the patient.

[0105] At block 1008, process 1000 can update electronic health record(s) with at least a portion of the received health data. For example, the healthcare software can add, to the electronic health record(s), at least a portion of the health metric data received from the one or more monitoring devices. In some implementations, the updated can be performed by generating update data that matches a care plan (e.g., care plan for the patient stored at the one or more electronic health record(s). For example, the care plan can include an identifier for the health metric, and at least aORC25139524-WO-PCT - 39 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 portion of the health metric data can be included in the generated update data based on the care plan including the identifier for the health metric data.

[0106] In some implementations, an update to the electronic health record(s) can be authorized based on the care plan information stored at the electronic health record(s) identifying the health metric for the patient. For example, a system that implements the one or more electronic health records can permit the update based on validating that the update data matches the care plan information of the one or more electronic health records for the user (e.g., the care plan includes an identifier for the health metric). In this example, a general workflow for updating electronic health record(s) may require one or more layers of approval and / or authorization (e.g., doctor, nurse, or clinician authorization). However, because the care plan explicitly defines that the health metric is part of the patient’s care plan, the health metric data can update the electronic health record(s) without requiring these layers of approval and / or authorization. In some implementations, the system that implements the electronic health record(s) can permit the update based on the health metric data comprising a granularity (e.g., daily, hourly, weekly, etc.) that matches a granularity defined in the stored care plan.

[0107] Implementations of a healthcare software system interact with user(s) and / or healthcare provider(s) to permit secure access to patient healthcare data and support user-driven functionality. A user (patient) can be registered with a healthcare software system such that the user’s health data is managed by the system. The user can interact with the healthcare software system via an application implemented at a user system (e.g., smartphone, laptop, tablet, personal device, etc.). The healthcare software system can aggregate the user’s health data from a variety of sources, such asORC25139524-WO-PCT - 40 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 from user-provided notes, user health metrics monitored via the healthcare application, electronic health records, third-party healthcare provider systems, or any other suitable source of patient health data. In some implementations, the healthcare application can store this aggregated user health data as a personal health record.

[0108] A personal health record can be health data about the user and accessible by the user. In this example, because the user has unlimited authority to view of their own health data, the personal health record can aggregate different types of health data from different sources. In some implementations, aspects of health data from the personal health record can be selectively shared with other systems and / or health records. For example, data from the personal health record can be selectively shared to electronic health record(s), provider system(s), or any other suitable system or record.

[0109] The health data aggregated at the personal health record can include care plan(s), such as a plan generated by a user’s clinician and / or care team that supports the user’s healthcare. The care plan can include actions and guidance for those actions, such as taking medications, performing physical therapy, tracking health metric(s), and the like. In some implementations, the healthcare application can interact with the user to support care plan implementation and other user-driven healthcare, such as prompting care plan actions and / or medication actions, guiding health metric monitoring, generating user notes related to the user’s healthcare, integrating questionnaires, defining and enforcing health data access permissions and restrictions, and the like.

[0110] The features, structures, or characteristics of the disclosure described throughout this specification may be combined in any suitable manner in one or moreORC25139524-WO-PCT - 41 -ORACLE CONFIDENTIALPATENT Docket No.: 201 1 -0712WO01 embodiments. For example, the usage of “one embodiment,” “some embodiments,” “certain embodiment,” “certain embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present disclosure. Thus, appearances of the phrases “one embodiment,” “some embodiments,” “a certain embodiment,” “certain embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0111] One having ordinary skill in the art will readily understand that the embodiments as discussed above may be practiced with steps in a different order, and / or with elements in configurations that are different than those which are disclosed. Therefore, although this disclosure considers the outlined embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of this disclosure. In order to determine the metes and bounds of the disclosure, therefore, reference should be made to the appended claims.ORC25139524-WO-PCT - 42 -

Claims

ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01WE CLAIM:1 . A method for executing a patient healthcare application to interact with healthcare entities, the method comprising: executing, via a computing device, a healthcare application, wherein the healthcare application is configured to store a patient record for the user, the patient record comprising: health metric data monitored from the user via one or more monitoring devices, and health data aggregated, using at least an identifier for the user, from one or more electronic health records, the aggregated health data comprising at least medication information for prescribed medications and care plan information for prescribed care plans; receiving, at the healthcare application from at least one of the one or more monitoring devices, health metric data for at least one health metric; and performing, via the healthcare application, one or more of the following in response to receiving the monitored data: prompting, via the healthcare application, one or more prescribed actions from the user, wherein the prompting is performed according to the care plan information and / or the medication information accessed from the one or more electronic health records; orORC25139524-WO-PCT - 43 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 causing, via the healthcare application, an update to the one or more electronic health records, wherein the update adds at least a portion of the health metric data received from the one or more monitoring devices to the one or more electronic health records.

2. The method of claim 1 , wherein the healthcare application, in response to receiving the monitored data, prompts the one or more prescribed actions, and wherein the one or more prescribed actions comprise taking prescribed medication, performing prescribed physical therapy, eating or drinking a prescribed food or drink, or performing a manual action for monitoring one or more health metrics.

3. The method of claim 2, wherein the care plan information comprises patient criteria for the one or more monitored health metrics, and the one or more prescribed actions are prompted in response to a comparison between the health metric data, received from the at least one monitoring device, and the patient criteria.

4. The method of claim 2, wherein the one or more prescribed actions comprise performing prescribed physical therapy, and the user is prompted to perform the prescribed physical therapy according to a physical therapy schedule defined in the care plan information accessed from the one or more electronic health records, or wherein the one or more prescribed actions comprise taking prescribedORC25139524-WO-PCT - 44 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 medication, and the user is prompted to take the prescribed medication according to a medication schedule defined in the medication information accessed from the one or more electronic health records.

5. The method of claim 1 , wherein the patient record further comprises patient notes based on input provided by a user, metadata for at least a portion of the patient notes comprising: a date and / or time and informational tags.

6. The method of claim 5, wherein the healthcare application, in response to receiving the monitored data, prompts the one or more prescribed actions, and wherein a patient note is automatically generated for the one or more prescribed actions, and wherein the user is prompted to provide input about the prescribed action to complete the automatically generated patient note.

7. The method of claim 5, further comprising: receiving, from a user, a request for analyzing the patient record, the request comprising query parameters; analyzing, in response to the prompt and based on the query parameters, the patient record including one or more of: the patient notes, the medication information, the care plan information, the monitored health metric, or the health data aggregated from the one or more electronic health records; andORC25139524-WO-PCT - 45 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 returning, in response to the analyzing, results comprising health information that matches the query parameters, the results comprising one or more of: portions of the patient notes, one or more medications defined by the medication information, portions of the care plan information, monitored health metric data, and portions of the aggregated electronic health data.

8. The method of claim 7, wherein a trained machine learning model performs the analyzing of the patient record, the trained machine learning model matching the query parameters to the health information of the results.

9. The method of claim 8, wherein the trained machine learning model comprises a large language model, the query parameters comprise a prompt for the large language model, and the matched results comprise health information retrieved from the patient record by the large language model in response to the prompt.

10. The method of claim 9, wherein the query parameters comprise a period of time and an identifier for the at least one health metric, and the results comprise a graph representation or a chart representation of the health metric data received from the monitoring device over the period of time.1 1 . The method of claim 10, wherein the period of time is defined relative to a date of: a prescribed medication, a prescribed care plan, a medical procedure defined via the aggregated electronic health data, a health event defined via the aggregatedORC25139524-WO-PCT - 46 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 electronic health data, or any combination thereof.

12. The method of claim 1 , wherein the healthcare application, in response to receiving the monitored data, causes the update to the one or more electronic health records, wherein the update is performed by: generating update data that matches a care plan from the care plan information, wherein the care plan includes an identifier for the at least one health metric, and wherein at least a portion of the health metric data is included in the generated update data based on the care plan.

13. The method of claim 12, wherein a system that implements the one or more electronic health records permits the update based on validating that the update data matches the care plan information of the one or more electronic health records for the user.

14. A non-transitory computer readable medium having instructions stored thereon that, when executed by a processor, cause the processor to interact with a user via a patient healthcare application, wherein, when executed, the instructions cause the processor to:ORC25139524-WO-PCT - 47 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 execute a healthcare application, wherein the healthcare application is configured to store a patient record for the user, the patient record comprising: health metric data monitored from the user via one or more monitoring devices, and health data aggregated, using at least an identifier for the user, from one or more electronic health records, the aggregated health data comprising at least medication information for prescribed medications and care plan information for prescribed care plans; receive, at the healthcare application from at least one of the one or more monitoring devices, health metric data for at least one health metric; and perform, via the healthcare application, one or more of the following in response to receiving the health metric data: prompt, via the healthcare application, one or more prescribed actions from the user, wherein the prompting is performed according to the care plan information and / or the medication information accessed from the one or more electronic health records; or cause, via the healthcare application, an update to the one or more electronic health records, wherein the update adds at least a portion of the health metric data received from the one or more monitoring devices to the one or more electronic health records.

15. The non-transitory computer readable medium of claim 14,ORC25139524-WO-PCT - 48 -ORACLE CONFIDENTIALPATENT Docket No.: 201 1 -0712WO01 wherein the healthcare application, in response to receiving the monitored data, prompts the one or more prescribed actions, and wherein the one or more prescribed actions comprise taking prescribed medication, performing prescribed physical therapy, eating or drinking a prescribed food or drink, or performing a manual action for monitoring one or more health metrics.

16. The non-transitory computer readable medium of claim 15, wherein the care plan information comprises patient criteria for the one or more monitored health metrics, and the one or more prescribed actions are prompted in response to a comparison between the health metric data, received from the at least one monitoring device, and the patient criteria.

17. The non-transitory computer readable medium of claim 15, wherein the one or more prescribed actions comprise performing prescribed physical therapy, and the user is prompted to perform the prescribed physical therapy according to a physical therapy schedule defined in the care plan information accessed from the one or more electronic health records, or wherein the one or more prescribed actions comprise taking prescribed medication, and the user is prompted to take the prescribed medication according to a medication schedule defined in the medication information accessed from the one or more electronic health records.

18. A system for interacting with a user via a patient healthcare application, theORC25139524-WO-PCT - 49 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 system comprising: a processor; and a memory storing instructions for execution by the processor, the instructions configuring the processor to: execute a healthcare application, wherein the healthcare application is configured to store a patient record for the user, the patient record comprising: health metric data monitored from the user via one or more monitoring devices, and health data aggregated, using at least an identifier for the user, from one or more electronic health records, the aggregated health data comprising at least medication information for prescribed medications and care plan information for prescribed care plans; receive, at the healthcare application from at least one of the one or more monitoring devices, health metric data for at least one health metric; and perform, via the healthcare application, one or more of the following in response to receiving the health metric data: prompt, via the healthcare application, one or more prescribed actions from the user, wherein the prompting is performed according to the care plan information and / or the medication information accessed from the one or more electronic health records; orORC25139524-WO-PCT - 50 -ORACLE CONFIDENTIALPATENTDocket No.: 201 1 -0712WO01 cause, via the healthcare application, an update to the one or more electronic health records, wherein the update adds at least a portion of the health metric data received from the one or more monitoring devices to the one or more electronic health records.

19. The system of claim 18, wherein the healthcare application, in response to receiving the monitored data, causes the update to the one or more electronic health records, wherein the update is performed by: generating update data that matches a care plan from the care plan information, wherein the care plan includes an identifier for the at least one health metric, and wherein at least a portion of the health metric data is included in the generated update data based on the care plan.

20. The system of claim 19, wherein a system that implements the one or more electronic health records permits the update based on validating that the update data matches the care plan information of the one or more electronic health records for the user.ORC25139524-WO-PCT - 51 -

Images