Prosecution Insights
Last updated: October 02, 2026
Application No. 17/806,197

VIRTUAL ASSISTANTS FOR PREEMPTIVE MEDICAL DATA ANALYSIS AND TREATMENT

Final Rejection §101§103§112
Filed
Jun 09, 2022
Examiner
JACKSON, JORDAN L
Art Unit
2857
Tech Center
2800 — Semiconductors & Electrical Systems
Assignee
AT&T Intellectual Property I L.P.
OA Round
4 (Final)
41%
Grant Probability
Moderate
5-6
OA Rounds
0m
Est. Remaining
79%
With Interview

Examiner Intelligence

Grants 41% of resolved cases
41%
Career Allowance Rate
78 granted / 191 resolved
-27.2% vs TC avg
Strong +38% interview lift
Without
With
+38.5%
Interview Lift
resolved cases with interview
Typical timeline
3y 2m
Avg Prosecution
40 currently pending
Career history
231
Total Applications
across all art units

Statute-Specific Performance

§101
38.7%
-1.3% vs TC avg
§103
34.5%
-5.5% vs TC avg
§102
10.5%
-29.5% vs TC avg
§112
12.9%
-27.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 191 resolved cases

Office Action

§101 §103 §112
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Formal Matters Applicant's response, filed 17 April 2026, has been fully considered. The following rejections and/or objections are either reiterated or newly applied. They constitute the complete set presently being applied to the instant application. Status of Claims Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are currently pending and have been examined. Claims 1, 11, 13, and 19 have been amended. Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 have been rejected. Priority Applicant's response, filed 26 December 2025, has been fully considered. The following rejections and/or objections are either reiterated or newly applied. They constitute the complete set presently being applied to the instant application. Claim Rejections – 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. § 112(a): IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are rejected under 35 U.S.C. 112(a) as failing to comply with the written description requirement. The claims contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, at the time the application was filed, had possession of the claimed invention. Claims 9, 13, and 19 have been amended to include performing the proposed action, wherein the proposed action comprises medical testing wherein a computer and corresponding hardware performs the action. Dependent claim 11 has been amended to recite wherein the performing of the proposed action comprises: providing, by the system via the virtual assistant, instructions to a medical testing device, wherein the system comprises the medical testing device; and performing, by the system, the medical testing utilizing the medical testing device, wherein the medical testing comprises one of blood testing, lung testing, blood glucose testing, heart testing, operation, heart-related procedure, biopsy, X-ray, magnetic resonance imaging (MRI), computed tomography (CT scan, dental procedure, eye-related procedure, or combination thereof. Examiner notes Applicant has not pointed out where the new (or amended) claim is supported outside of ¶ 0023 and ¶ 0048 wherein only the embodiment of recommending to a user “for consideration or action” of the follow up actions is supported, nor does there appear to be a written description of the claim limitations in the application as filed (see 2163.04(I) regarding the burden on Examiner with regard to the written description requirement). Claims 4-7, 9-10, 15-16, and 20-27 depend on claims 1, 13, or 19 and do not remedy the written description requirement issues of claim 10. As dependent claims inherit the deficiencies of the claims they depend on, they are also rejected. Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are rejected under 35 U.S.C. § 101 because the claimed invention is directed to a judicial exception (i.e. a law of nature, a natural phenomenon, or an abstract idea) without significantly more. Step 1 – Statutory Categories of Invention: Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are drawn to a method, system, or manufacture, which are statutory categories of invention. Step 2A – Judicial Exception Analysis, Prong 1: Independent claim 1 recites a method, independent claim 13 recites a system, and independent claim 19 recites a non-transitory machine-readable medium each in part performing the steps of obtaining first medical data contained in medical records associated with a user identity; receiving second medical data associated with the user identity, the second medical data comprising data from sensors, medical devices, or user input devices determining a model relating to medical care and medical conditions associated with a plurality of user identities based on a result of an analysis, of the first medical data and the second medical data, and third medical data relating to the medical care and the medical conditions; generating a user-specific model associated with the user identity from the model wherein the user-specific model is generated by weighting or focusing on medical data specific to the user identity; utilizing the user-specific model to process only data relevant to the user identity for determining a proposed action relating to the medical care associated with the user identity, thereby reducing computational requirement and improving data processing efficiency; determining a device interface for communicating action information relating to the proposed action to a user; communicating the action information relating to the proposed action to the user; and performing the proposed action, wherein the proposed action comprises medical testing. These steps amount to methods of organizing human activity which includes functions relating to interpersonal and intrapersonal activities, such as managing relationships or transactions between people, social activities, and human behavior; satisfying or avoiding a legal obligation; advertising, marketing, and sales activities or behaviors; and managing human mental activity (MPEP § 2106.04(a)(2)(II)(C) citing the abstract idea grouping for methods of organizing human activity for managing personal behavior or relationships or interactions between people similar to iii. a mental process that a neurologist should follow when testing a patient for nervous system malfunctions, In re Meyer, 688 F.2d 789, 791-93, 215 USPQ 193, 194-96 (CCPA 1982) – also note MPEP § 2106.04(a)(2)(II) stating certain activity between a person and a computer may fall within the “certain methods of organizing human activity” grouping). Dependent claim 4 recites, in part, wherein the electronic medical records are first electronic medical records, and wherein the method further comprises: receiving updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and modifying, by the system, the user-specific model based on analysis, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity, wherein the historical medical data comprises a portion of the first medical data, the second medical data, or the third medical data, and wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model. Dependent claim 5 recites, in part, wherein the portion is a first portion; wherein the receiving of the updated medical data comprises: prior to, and within a defined amount of time of, a medical care visit with a medical care provider by the user, receiving a second portion of the updated medical data from the user, the sensor, or the medical device and wherein the method further comprises: prior to the medical care visit with the medical care provider by the user, presenting the second portion of the updated medical data to the medical care provider in connection with the medical care visit; or prior to the medical care visit with the medical care provider by the user: communicating the second portion of the updated medical data to the medical care provider, and presenting the second portion of the updated medical data to the medical care provider in connection with the medical care visit. Dependent claim 6 recites, in part, wherein the portion is a first portion, wherein the receiving of the updated medical data comprises: receiving a second portion of the electronic medical records from a first medical care provider; and receiving a third portion of the electronic medical records from a second medical care provider; Dependent claim 7 recites, in part, perceiving a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating medical condition information relating to the medical condition; and communicating the medical condition information to a medical care provider identity located at a second location. Dependent claim 9 recites, in part, communicating a request for information relating to a medical condition associated with the user identity to a second [device] based on determining that the second [device] has access to medical field information relating to a medical field associated with the medical condition; and receiving the information relating to the medical condition, wherein the determining of the proposed action comprises determining the proposed action relating to the medical care based on the model and analysis of the information relating to the medical condition. Dependent claim 10 recites, in part, access first medical treatment information relating to a first type of medical treatment to utilize to treat the medical condition, wherein the information relating to the medical condition comprises second medical treatment information relating to a second type of medical treatment to utilize to treat the medical condition, wherein the determining of the proposed action comprises determining which of the first type of medical treatment, the second type of medical treatment, or a third type of medical treatment is to be utilized or recommended to treat the medical condition based on the model and analysis of the first medical treatment information and the second medical treatment information, and wherein the third type of medical treatment is determined based on the first type of medical treatment and the second type of medical treatment. Dependent claim 11 recites, in part, providing instructions; and performing the medical testing. Dependent claim 15 recites, in part, wherein the operations further comprise: determining that first information relating to a medical condition associated with the user identity is subject to a higher privacy level based on a defined privacy criterion; determining that second information relating to the user identity is subject to a lower privacy level based on the defined privacy criterion; in response to determining that the first information is subject to the higher privacy level, presenting the first information to the user, wherein the first interface is determined to be able to provide privacy of the first information at the higher privacy level for the presenting of the first information to the user, and wherein the first information presented is only able to be perceived by the user; and in response to determining that the second information is subject to the lower privacy level, presenting the second information to the user, wherein the second interface is determined to be able to provide privacy of the second information at the lower privacy level for the presenting of the second information to the user, and wherein the second information presented is able to be perceived by the user and another user other than the user. Dependent claim 16 recites, in part, determining that a user associated with the user identity has a medical condition based on the user specific model; receiving medical treatment information relating to a medical treatment for the medical condition, wherein the second [device] is not associated with a medical care provider that has provided medical care to the user; determining that the medical treatment has not been considered, by the medical care provider or the user, to treat the user for the medical condition based on analysis of the model, the user-specific model, or the first medical information, the second medical information, or the third medical information that pertains to the user; in response to determining that the medical treatment has not been considered by the medical care provider or the user, presenting the medical treatment information relating to the medical treatment for the medical condition to the user or to the medical care provider. Dependent claim 21 recites, in part, receiving updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and modifying the user-specific model based on analysis, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity, wherein the historical medical data comprises a portion of the first medical information, the second medical information, or the third medical information, and wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model. Dependent claim 22 recites, in part, perceiving a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating medical condition information relating to the medical condition; and communicating the medical condition information to a medical care provider identity located at a second location. Dependent claim 23 recites, in part, communicating a request for information relating to a medical condition associated with the user identity based on determining that the second [device] has access to medical field information relating to a medical field associated with the medical condition; and receiving the information relating to the medical condition, wherein the determining of the proposed action comprises determining the proposed action relating to the medical care based on the model and analysis of the information relating to the medical condition. Dependent claim 20 recites, in part, wherein the electronic medical records are first electronic medical records, and wherein the operations further comprise: receiving, by the virtual assistant function, updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and modifying the user-specific model based on analysis, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity, wherein the historical medical data comprises a portion of the first medical data, the second medical data, or the third medical data, and wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model. Dependent claim 24 recites, in part, wherein the virtual assistant function is a first virtual assistant function, wherein the portion is a first portion, wherein the receiving of the updated medical data comprises: prior to, and within a defined amount of time of, a medical care visit with a medical care provider by the user, receiving, by the virtual assistant function, a second portion of the updated medical data from the user, the sensor, or the medical device, and wherein the operations further comprise prior to the medical care visit with the medical care provider by the user, presenting, via the first virtual assistant function, the second portion of the updated medical data to the medical care provider in connection with the medical care visit; or prior to the medical care visit with the medical care provider by the user; communicating, by the first virtual assistant function, the second portion of the updated medical data to a second virtual assistant function associated with the medical care provider, and presenting, via the second virtual assistant function, the second portion of the updated medical data to the medical care provider in connection with the medical care visit. Dependent claim 25 recites, in part, wherein the virtual assistant function is a first virtual assistant function, and wherein the receiving of the updated medical data comprises: receiving a second portion of the electronic medical records from a second virtual assistant function associated with a first medical care provider; and receiving a third portion of the electronic medical records from a third virtual assistant function associated with a second medical care provider. Dependent claim 26 recites, in part, wherein the virtual assistant function is a first virtual assistant function, and wherein the operations further comprise: perceiving a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating medical condition information relating to the medical condition; and communicating the medical condition information to a second virtual assistant function associated with a medical care provider identity, wherein the second virtual assistant function is located at a second location. Dependent claim 27 recites, in part, receiving, from a medical care provider, a request for information relating to a medical or health history associated with the user identity; identifying the information relating to the medical or health history associated with the user identity in the model a portion of the electronic medical records that is determined to be associated with the user identity, or sensor data associated with the user identity; and presenting, via the virtual assistant function to the medical care provider, the information relating to the medical or health history associated with the user identity. Each of these steps of the preceding dependent claims only serve to further limit or specify the features of independent claims 1, 13, or 19 accordingly, and hence are nonetheless directed towards fundamentally the same abstract idea as the independent claim and utilize the additional elements analyzed below in the expected manner. Step 2A – Judicial Exception Analysis, Prong 2: This judicial exception is not integrated into a practical application because the additional elements within the claims only amount to instructions to implement the judicial exception using a computer [MPEP 2106.05(f)]. Claim 1 recites a system with a processor and a virtual assistant device. Claims 1 and 13 recite a user device. Claims 1, 13, and 19 recite a device interface of the user device comprising at least one of a display screen, audio speaker, or haptic device. Claim 13 recites a processor, a memory, and a virtual assistance device. Claim 19 recites non-transitory machine-readable medium. Claim 5, 6, 7, 9, 16, and 22-26 recite a second virtual assistant device (or function which notably includes an embodiment of an algorithm alone). Claims 15, 24, and 27 recite an interface of the virtual assistant device. Claims 6, 16, and 25 recite a third virtual assistant device (or function which notably includes an embodiment of an algorithm alone). The specification provides that these devices are “known by those of skill in the art” (see the Detailed Description in ¶ 00125) and can be practiced on any other computer system configurations with no specific hardware requirements (see the Detailed Description in ¶ 00136-139 and ¶ 00159). The use of the virtual assistant devices, interfaces, and corresponding hardware, in this case to communicate and process patient data, only recites virtual assistant devices, interfaces, and corresponding hardware as a tool to perform an existing process and only amounts to an instruction to implement the abstract idea using a computer (MPEP § 2106.05(f)(2) see case requiring the use of software to tailor information and provide it to the user on a generic computer within the “Other examples.. v.”). Claims 1, 4, 13, and 19-21 recite an artificial intelligence functions. Claims 1, 13, and 19 recite applying the artificial intelligence function, including training of neural networks, Markov chains, or other machine learning algorithms, to historical medical data and updated medical data associated with the user identity. The specification discloses that that artificial intelligence functions may be any embodiment of AI/machine learning listing a plurality of different algorithm embodiments for performing a plurality of diverse tasks (see the Detailed Description in ¶ 0073-75. The use of an artificial intelligence function, in this case to perform any medical data related task, only recites the artificial intelligence function as a tool to apply data to an algorithm and report the results (MPEP § 2106.05(f)(2) see case involving a commonplace business method or mathematical algorithm being applied on a general purpose computer within the “Other examples.. i.”) amounting to instruction to implement the abstract idea using a general purpose computer. Alice Corp. Pty. Ltd. V. CLS Bank Int’l, 134 S. Ct. 2347, 1357 (2014). Claims 1, 13, and 19 recite wherein the action information includes a direction to the user device to use a haptic device to communicate the action information to the user, wherein the haptic device presents the action information in a haptic form to the user. The limitations are only recited as a tool which only serves as display/output of the data determined from the abstract idea (MPEP § 2106.05(g) - insignificant pre/post-solution activity that amounts to post-solution output on a well-known display device) and is therefore not a practical application of the recited judicial exception. Claim 11 recites wherein the performing of the proposed action comprises: providing, by the system via the virtual assistant, instructions to a medical testing device, wherein the system comprises the medical testing device; and performing, by the system, the medical testing utilizing the medical testing device, wherein the medical testing comprises one of blood testing, lung testing, blood glucose testing, heart testing, operation, heart-related procedure, biopsy, X-ray, magnetic resonance imaging (MRI), computed tomography (CT scan, dental procedure, eye-related procedure, or combination thereof. The limitations are only recited as a tool which only serves as output of the data determined from the abstract idea (MPEP § 2106.05(g) - insignificant pre/post-solution activity that amounts to post-solution output on a well-known display device) and is therefore not a practical application of the recited judicial exception. Furthermore, the recitation of providing any instructions to a plurality of unrelated medical testing devices is very broad and therefore amounts to a field of use or technological environment in which to apply a judicial exception do not amount to significantly more than the exception itself (MPEP § 2106.05(h) similar to example vi. Limiting the abstract idea of collecting information, analyzing it, and displaying certain results of the collection and analysis to data related to the electric power grid, because limiting application of the abstract idea to power-grid monitoring is simply an attempt to limit the use of the abstract idea to a particular technological environment, Electric Power Group, LLC v. Alstom S.A., 830 F.3d 1350, 1354, 119 USPQ2d 1739, 1742 (Fed. Cir. 2016) wherein the additional elements do not amount to more than generally linking the use of a judicial exception to a particular technological environment or field of use). The above claims, as a whole, are therefore directed to an abstract idea. Step 2B – Additional Elements that Amount to Significantly More: The present claims do not include additional elements that are sufficient to amount to more than the abstract idea because the additional elements or combination of elements amount to no more than a recitation of instructions to implement the abstract idea on a computer. Claim 1 recites a system with a processor and a virtual assistant device. Claims 1 and 13 recite a user device. Claims 1, 13, and 19 recite a device interface of the user device comprising at least one of a display screen, audio speaker, or haptic device. Claim 13 recites a processor, a memory, and a virtual assistance device. Claim 19 recites non-transitory machine-readable medium. Claim 5, 6, 7, 9, 16, and 22-26 recite a second virtual assistant device (or function which notably includes an embodiment of an algorithm alone). Claims 15, 24, and 27 recite an interface of the virtual assistant device. Claims 6, 16, and 25 recite a third virtual assistant device (or function which notably includes an embodiment of an algorithm alone). Claims 1, 4, 13, and 19-21 recite an artificial intelligence functions. Claims 1, 13, and 19 recite applying the artificial intelligence function, including training of neural networks, Markov chains, or other machine learning algorithms, to historical medical data and updated medical data associated with the user identity. Each of these elements is only recited as a tool for performing steps of the abstract idea, such as the use of the storage mediums to store data, the computer and data processing devices to apply the algorithm, and the display device to display selected results of the algorithm. These additional elements therefore only amount to mere instructions to perform the abstract idea using a computer and are not sufficient to amount to significantly more than the abstract idea (MPEP 2016.05(f) see for additional guidance on the “mere instructions to apply an exception”). Each additional element under Step 2A, Prong 2 is analyzed in light of the specification’s explanation of the additional element’s structure. The claimed invention’s additional elements do not have sufficient structure in the specification to be considered a not well-understood, routine, and conventional use of generic computer components. Note that the specification can support the conventionality of generic computer components if “the additional elements are sufficiently well-known that the specification does not need to describe the particulars of such additional elements to satisfy 35 U.S.C. § 112(a)” (Berkheimer in III. Impact on Examination Procedure, A. Formulating Rejections, 1. on p. 3). Claims 1, 13, and 19 recite wherein the action information includes a direction to the user device to use a haptic device to communicate the action information to the user, wherein the haptic device presents the action information in a haptic form to the user. The use of haptic feedback to communicate information to a user is well understood, routine, and conventional activity. This position is supported by Alur et al., Haptic Technology :- A Comprehensive Review of its Applications and Future Prospects, 5(5) Int J of Computer Science and Information Technologies 6039-6043 (2014) teaching on the state of the art for haptic feedback design and function particularly in under interfaces in § 2. Design History on p. 6039-6040 and § 6.1 Use Of Haptic Feedbacks In Graphical User Interfaces on p. 6041 (treated as a review under MPEP § 2106.07(a)(III)(C) that describes the state of the art and discusses what is well-known and in common use in the relevant industry). Therefore, the use of a haptic device to communicate the action information to the user additional element is not sufficient to amount to significantly more than the recited judicial exception. Claim 11 recites wherein the performing of the proposed action comprises: providing, by the system via the virtual assistant, instructions to a medical testing device, wherein the system comprises the medical testing device; and performing, by the system, the medical testing utilizing the medical testing device, wherein the medical testing comprises one of blood testing, lung testing, blood glucose testing, heart testing, operation, heart-related procedure, biopsy, X-ray, magnetic resonance imaging (MRI), computed tomography (CT scan, dental procedure, eye-related procedure, or combination thereof. The courts have decided that determining the level of a biomarker in blood by any means as well-understood, routine, conventional activity in the life science arts when they are claimed in a merely generic manner (e.g., at a high level of generality) or as insignificant extra-solution activity (MPEP § 2106.05(d)(II)). The use of an image capture device to generate and store images is well-understood, routine, and conventional activity as evidenced by (1) Wirx-Speetjens (US Patent App No 2013/0166256) teaching on digital medical image capturing devices known in the art in the Detailed Description in ¶ 0037 stating “Digital patient-specific image information may be provided by any suitable means known in the art, such as, for example, an X-ray, a computer tomography (CT) scanner, a magnetic resonance imaging (MRI) scanner, an ultrasound scanner, etc.” (treated as a review under MPEP § 2106.07(a)(III)(C) that describes the state of the art and discusses what is well-known and in common use in the relevant industry). Therefore, performing, by the system, the medical testing utilizing the medical testing device is not sufficient to amount to significantly more than the recited judicial exception. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception. Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. Their collective functions merely provide conventional computer implementation. Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are therefore rejected under 35 U.S.C. § 101 as being directed to non-statutory subject matter. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1, 4-7, 9-11, 13, 15-16, and 19-27 are rejected under 35 U.S.C. 103 as being unpatentable over Rusak (US Patent Pub No 2021/0225495)[hereinafter Rusak] in view of Chen et al., FedHealth: A Federated Transfer Learning Framework for Wearable Healthcare, 35(4) IEEE Intelligent Systems 83-93 (April 22, 2020)[hereinafter Chen] in further view of Dirghangi et al. (US Patent Pub No 20180220889)[hereinafter Dirghangi]. As per claim 1, Rusak discloses the following limitations: a method, comprising: obtaining, by a system comprising a processor is taught in the Detailed Description in ¶ 0058 (teaching on a computer with a processor and memory for collecting and analyzing patient data for diagnostic and treatment recommendations via machine learning); obtaining… first medical data contained in electronic medical records associated with a user identity is taught in the Detailed Description in ¶ 0083, ¶ 00149-150, ¶ 0177, ¶ 0181, ¶ 0203, and in the Figures at fig. 1 (teaching on receiving electronic medical record data for the current target patient); receiving, by the system, second medical data associated with the user identity from a user device, the second medical data comprising data from sensors, medical devices, or user input devices of the user device is taught in the Detailed Description in ¶ 0161, ¶ 0181, and ¶ 0203 (teaching on receiving sensor device data for the current target patient from a plurality of patient and provider devices); determining, by the system, a model relating to medical care and medical conditions associated with a plurality of user identities based on a result of an analysis utilizing an artificial intelligence function is taught in the Detailed Description in ¶ 0130, ¶ 0139, and in the Figures at fig. 1 (teaching on a machine learning model (treated as synonymous to a model utilizing an artificial intelligence function) for analyzing general data and current target patient specific data (treated as synonymous to "associated with a plurality of user identities")); of the first medical data is taught in the Detailed Description in ¶ 0083, ¶ 00149-150, ¶ 0177, ¶ 0181, ¶ 0203, and in the Figures at fig. 1 (teaching on the machine learning model receiving electronic medical record data for the current target patient); second medical data, and is taught in the Detailed Description in ¶ 0161, ¶ 0181, and ¶ 0203 (teaching on the machine learning model receiving sensor device data for the current target patient from a plurality of patient and provider devices); third medical data relating to the medical care and the medical conditions is taught in the Detailed Description in ¶ 0162-163, ¶ 0181, and ¶ 0203 (teaching on the machine learning model receiving additional patient parameter data such as prior treatments and diagnosis, for the current target patient); utilizing, by the system, the user-specific model to process only data relevant to the user identity for determining a proposed action relating to the medical care associated with the user identity, thereby reducing computational requirements and improving data processing efficiency is taught in the Detailed Description in ¶ 0194, ¶ 0181, and ¶ 0203 (teaching on the machine learning model determining a user action related to the medical care of the current target patient - Examiner notes that the intended use of reducing computational requirements and processing efficiency does not add meaningful limitations to the claim see MPEP § 2144.07 for more detail regarding art recognized suitability for an intended purpose ); determining, by the system, a device interface of the user device for communicating action information relating to the proposed action to a user of the user device, the device interface comprising at least one of a display screen, audio speaker, or haptic device; and is taught in the Detailed Description in ¶ 0203-205, ¶ 0217, and in the Summary in ¶ 0021 (teaching on determining a user interface for displaying the determined user action to a user device wherein the device comprises a display and speaker); communicating, via a virtual assistant device of the system, the action information relating to the proposed action to the user device is taught in the Detailed Description in ¶ 0181 and ¶ 0203-205 (teaching on outputting the determined user action to a user interface of the one of the devices). Rusak fails to teach the following; Chen, however, does disclose: generating, by the system, a user-specific model associated with the user identity from the model by applying the artificial intelligence function, including training of neural networks, Markov chains, or other machine learning algorithms, to historical medical data and updated medical data associated with the user identity, wherein the user-specific model is generated by weighting or focusing on medical data specific to the user identity is taught in the § Overview of the Framework on p. 85-86, § Federated Learning on p. 86, and in Figure 2 on p. 86 (teaching on further refining a generalized model by training a personalized convolutional neural network model from a trained cloud/generalized model to optimize the cloud model parameters to the patient specific data). One of ordinary skill in the art before the effective filing date would combine the generalized medical action machine learning model of Rusk with a personalized user model via transfer learning of Chen with the motivation of “aggregate[ing] the data from different organizations without compromising privacy security and achiev[ing] relatively personalized model learning through knowledge transfer” (Chen in the § Conclusions and Future Work on p. 91). The combination of Rusak and Chen fails to teach the following; Dirghangi, however, does disclose: wherein the action information includes a direction to the user device to use a haptic device to communicate the action information to the user, wherein the haptic device presents the action information in a haptic form to the user is taught in the Field of the Invention in ¶ 0002 and in the Detailed Description in ¶ 0060 (teaching on providing ambient examination-related feedback to the user to communicate a visual and non-visual notification to the user on a user device); performing the proposed action, wherein the proposed action comprises medical testing is taught in the Detailed Description in ¶ 0056, ¶ 0117, ¶ and in the Figures at fig. 3 (teaching on performing a recommended diagnostic action (treated as synonymous with medical testing) with the diagnostic device in response to the haptic feedback - here the capture of an image when a better capture of a desired feature is detected);. One of ordinary skill in the art before the effective filing date would modify the sound and visual notification of Rusak and Chen with the haptic feedback and the diagnostic testing performance of Dirghangi with the motivation of “allowing the doctor and patient the benefits of clinical photographic documentation and enhancement, while optimizing workflows” (Dirghangi in the Summary of the Invention in in ¶ 0007). Independent claims 13 and 19 are rejected under the same rational. As per claim 4, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 1. Rusak also discloses the following: the method of claim 1, wherein the electronic medical records are first electronic medical records, and wherein the method further comprises: receiving, by the virtual assistant device, updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and is taught in the Detailed Description in ¶ 0195-197 (teaching on receiving current iteration data of the patient parameters for the current target patient from a plurality of patient and provider devices including patient sensor data); modifying, by the system, the user-specific model based on analysis, utilizing the artificial intelligence function, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity wherein the historical medical data comprises a portion of the first medical data, the second medical data, or the third medical data, and is taught in the Detailed Description in ¶ 0137 and ¶ 0195-197 (teaching on updating the machine learning model with the new patient parameter data and the collected first (EHR data), second (historical patient sensor data), and third (additional patient parameter data) data sets); wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model is taught in the Detailed Description in ¶ 0137, ¶ 0197, and ¶ 0209 (teaching on the determined user action generated from the machine learning model being specific to the patient's real-time needs and training data). As per claim 5, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 4. Rusak also discloses the following: the method of claim 4, wherein the virtual assistant device is a first virtual assistant device, wherein the portion is a first portion; wherein the receiving of the updated medical data comprises: prior to, and within a defined amount of time of, a medical care visit with a medical care provider by the user, receiving, by the virtual assistant device, a second portion of the updated medical data from the user, the sensor, or the medical device is taught in the Detailed Description in ¶ 0203 and ¶ 0214 (teaching on collecting the patient parameter data from a patient sensor for a predetermined time interval rate prior to the physician utilizing the machine learning model in a follow up appointment to generate a determined user action); and wherein the method further comprises: prior to the medical care visit with the medical care provider by the user, presenting, via a first interface associated with the first virtual assistant device, the second portion of the updated medical data to the medical care provider in connection with the medical care visit; or prior to the medical care visit with the medical care provider by the user: communicating, by the first virtual assistant device, the second portion of the updated medical data to a second virtual assistant device associated with the medical care provider, and presenting, via a second interface associated with the second virtual assistant device, the second portion of the updated medical data to the medical care provider in connection with the medical care visit is taught in the Detailed Description in ¶ 0065, ¶ 0203, and ¶ 0214-215 (teaching on sending an alert to the healthcare provider's user interface if, during the monitoring period of collecting patient parameter data, the data meets an alert threshold). As per claim 6, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 4. Rusak also discloses the following: the method of claim 4, wherein the virtual assistant device is a first virtual assistant device, wherein the portion is a first portion, wherein the receiving of the updated medical data comprises: receiving, by the first virtual assistant device, a second portion of the electronic medical records from a first device or a second virtual assistant device associated with a first medical care provider; and receiving, by the first virtual assistant device, a third portion of the electronic medical records from a second device or a third virtual assistant device associated with a second medical care provider is taught in the Detailed Description in ¶ 0212-215 (teaching on receiving additional second (historical patient sensor data) data from a secondary/plurality of other providers to be analysed by the machine learning model for generating a determined user action for the current target patient). As per claim 7, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 1. Rusak also discloses the following: the method of claim 1, wherein the virtual assistant device is a first virtual assistant device, and wherein the method further comprises: perceiving, by the first virtual assistant device, a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating, by the first virtual assistant device, medical condition information relating to the medical condition; and is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on collecting a similar patient parameter data and corresponding first provider's interaction with said data related to the patient's condition (here the example is of a G6PD deficiency and diabetic diagnosis)); communicating, by the first virtual assistant device, the medical condition information to a second virtual assistant device associated with a medical care provider identity, wherein the second virtual assistant device is located at a second location is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on alerting on a second provider's user interface regarding a determined user action for the current target patient related to the similar patient's condition wherein the second provider is at a separate medical institute (treated as synonymous to located at a second location)). As per claim 9, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 1. Rusak also discloses the following: the method of claim 1, wherein the virtual assistant device is a first virtual assistant device, and wherein the method further comprises: communicating, by the first virtual assistant device, a request for information relating to a medical condition associated with the user identity to a second virtual assistant device based on determining that the second virtual assistant device has access to medical field information relating to a medical field associated with the medical condition; and is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on the system requesting the collection of similar patient parameter data and corresponding second provider's interaction with said data related to the patient's condition (here the example is of a G6PD deficiency and diabetic diagnosis)); receiving, by the first virtual assistant device, the information relating to the medical condition from the second virtual assistant device, wherein the determining of the proposed action comprises determining the proposed action relating to the medical care based on the model and analysis of the information relating to the medical condition is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on alerting on a first provider's user interface regarding a determined user action for the current target patient related to the similar patient's condition wherein the determined user action is determined via the machine learning model). As per claim 10, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 9. Rusak also discloses the following: the method of claim 9, wherein the first virtual assistant device accesses first medical treatment information relating to a first type of medical treatment to utilize to treat the medical condition, wherein the information relating to the medical condition comprises second medical treatment information relating to a second type of medical treatment to utilize to treat the medical condition, wherein the determining of the proposed action comprises determining which of the first type of medical treatment, the second type of medical treatment, or a third type of medical treatment is to be utilized or recommended to treat the medical condition based on the model and analysis of the first medical treatment information and the second medical treatment information, and wherein the third type of medical treatment is determined based on the first type of medical treatment and the second type of medical treatment is taught in the Detailed Description in ¶ 0211-214 and ¶ 0195-197 (teaching on utilizing the machine learning model to determine if an alternative (second or third) treatment would be better suited to treat the current target patient's condition and outputting the treatment as the determined user action to a user interface of the one of the devices). As per claim 11, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 1. The combination of Rusak and Chen fails to teach the following; Dirghangi, however, does disclose: the method of claim 1, further comprising wherein the performing of the proposed action comprises: providing, by the system via the virtual assistant, instructions to a medical testing device, wherein the system comprises the medical testing device; and performing, by the system, the medical testing utilizing the medical testing device, wherein the medical testing comprises one of blood testing, lung testing, blood glucose testing, heart testing, operation, heart-related procedure, biopsy, X-ray, magnetic resonance imaging (MRI), computed tomography (CT scan, dental procedure, eye-related procedure, or combination thereof is taught in the Detailed Description in ¶ 0056, ¶ 0117, ¶ and in the Figures at fig. 3 (teaching on performing a recommended diagnostic action (treated as synonymous with medical testing) with the diagnostic device in response to the haptic feedback - here the capture of an image when a better capture of a desired feature is detected). One of ordinary skill in the art before the effective filing date would modify the sound and visual notification of Rusak and Chen with the haptic feedback and the diagnostic testing performance of Dirghangi with the motivation of “allowing the doctor and patient the benefits of clinical photographic documentation and enhancement, while optimizing workflows” (Dirghangi in the Summary of the Invention in in ¶ 0007). As per claim 16, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 13. Rusak also discloses the following: the system of claim 13, wherein the virtual assistant device is a first virtual assistant device, and wherein the operations further comprise: determining that a user associated with the user identity has a medical condition based on the user-specific model is taught in the Detailed Description in ¶ 0135, ¶ 0137, and ¶ 0195-197 (teaching on determining via the machine learning model with the new patient parameter data and the collected first (EHR data), second (historical patient sensor data), and third (additional patient parameter data) data sets, a target patient outcome which may be the target has or does not have a particular condition); receiving, by the first virtual assistant device from a second virtual assistant device, medical treatment information relating to a medical treatment for the medical condition, wherein the second virtual assistant device is not associated with a medical care provider that has provided medical care to the user is taught in the Detailed Description in ¶ 0178, ¶ 0211-212, and in the Figures at fig. 12B (teaching on receiving at the first provider's user interface a second provider's treatment for the same condition for a different patient (treated as synonymous to a provider not associated with the user)); determining that the medical treatment has not been considered, by the medical care provider or the user, to treat the user for the medical condition based on analysis of the model, the user-specific model, or the first medical information, the second medical information, or the third medical information that pertains to the user; in response to determining that the medical treatment has not been considered by the medical care provider or the user, presenting, by the first virtual assistant device, the medical treatment information relating to the medical treatment for the medical condition to the user or to the medical care provider via a third virtual assistant device associated with the medical care provider is taught in the Detailed Description in ¶ 0210-212 and in the Figures at fig. 12B (teaching on presenting of the first provider via the user interface the additional treatment option that has not been utilized by the first provider to treat the current patient - Examiner notes that the use of a third virtual assistant device is a duplication of parts as displaying the additional treatment information on device, whether the first or a third device, has no new or unexpected results see MPEP 2144.04(VI)(B)). As per claim 21, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 13. Rusak also discloses the following: the system of claim 13, wherein the operations further comprise: receiving, by the virtual assistant device, updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and is taught in the Detailed Description in ¶ 0195-197 (teaching on receiving current iteration data of the patient parameters for the current target patient from a plurality of patient and provider devices including patient sensor data); modifying the user-specific model based on analysis, utilizing the artificial intelligence function, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity, wherein the historical medical data comprises a portion of the first medical information, the second medical information, or the third medical information, and is taught in the Detailed Description in ¶ 0137 and ¶ 0195-197 (teaching on updating the machine learning model with the new patient parameter data and the collected first (EHR data), second (historical patient sensor data), and third (additional patient parameter data) data sets); wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model is taught in the Detailed Description in ¶ 0137, ¶ 0197, and ¶ 0209 (teaching on the determined user action generated from the machine learning model being specific to the patient's real-time needs and training data). As per claim 22, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 13. Rusak also discloses the following: the system of claim 13, wherein the virtual assistant device is a first virtual assistant device, and wherein the operations further comprise: perceiving, by the first virtual assistant device, a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating, by the first virtual assistant device, medical condition information relating to the medical condition; and is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on collecting a similar patient parameter data and corresponding first provider's interaction with said data related to the patient's condition (here the example is of a G6PD deficiency and diabetic diagnosis)); communicating, by the first virtual assistant device, the medical condition information to a second virtual assistant device associated with a medical care provider identity, wherein the second virtual assistant device is located at a second location is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on alerting on a second provider's user interface regarding a determined user action for the current target patient related to the similar patient's condition wherein the second provider is at a separate medical institute (treated as synonymous to located at a second location)). As per claim 23, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 13. Rusak also discloses the following: the system of claim 13, wherein the virtual assistant device is a first virtual assistant device, and wherein the operations further comprise: communicating, by the first virtual assistant device, a request for information relating to a medical condition associated with the user identity to a second virtual assistant device based on determining that the second virtual assistant device has access to medical field information relating to a medical field associated with the medical condition; and is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on the system requesting the collection of similar patient parameter data and corresponding second provider's interaction with said data related to the patient's condition (here the example is of a G6PD deficiency and diabetic diagnosis)); receiving, by the first virtual assistant device, the information relating to the medical condition from the second virtual assistant device, wherein the determining of the proposed action comprises determining the proposed action relating to the medical care based on the model and analysis of the information relating to the medical condition is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on alerting on a first provider's user interface regarding a determined user action for the current target patient related to the similar patient's condition wherein the determined user action is determined via the machine learning model). As per claim 20, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 19. Rusak also discloses the following: the non-transitory machine-readable medium of claim 19, wherein the electronic medical records are first electronic medical records, and wherein the operations further comprise: receiving, by the virtual assistant function, updated medical data associated with the user identity from a user associated with the user identity, second electronic medical records associated with the user identity, or a sensor or a medical device associated with the user; and is taught in the Detailed Description in ¶ 0195-197 (teaching on receiving current iteration data of the patient parameters for the current target patient from a plurality of patient and provider devices including patient sensor data); modifying the user-specific model based on analysis, utilizing the artificial intelligence function, of the model, the updated medical data associated with the user identity, and historical medical data associated with the user identity, wherein the historical medical data comprises a portion of the first medical data, the second medical data, or the third medical data, and is taught in the Detailed Description in ¶ 0137 and ¶ 0195-197 (teaching on updating the machine learning model with the new patient parameter data and the collected first (EHR data), second (historical patient sensor data), and third (additional patient parameter data) data sets); wherein the determining of the proposed action relating to the medical care associated with the user identity comprises determining the proposed action relating to the medical care associated with the user identity based on the user-specific model is taught in the Detailed Description in ¶ 0137, ¶ 0197, and ¶ 0209 (teaching on the determined user action generated from the machine learning model being specific to the patient's real-time needs and training data). As per claim 24, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 20. Rusak also discloses the following: the non-transitory machine-readable medium of claim 20, wherein the virtual assistant function is a first virtual assistant function, wherein the portion is a first portion, wherein the receiving of the updated medical data comprises: prior to, and within a defined amount of time of, a medical care visit with a medical care provider by the user, receiving, by the virtual assistant function, a second portion of the updated medical data from the user, the sensor, or the medical device, and is taught in the Detailed Description in ¶ 0203 and ¶ 0214 (teaching on collecting the patient parameter data from a patient sensor for a predetermined time interval rate prior to the physician utilizing the machine learning model in a follow up appointment to generate a determined user action); wherein the operations further comprise prior to the medical care visit with the medical care provider by the user, presenting, via a first interface associated with the first virtual assistant function, the second portion of the updated medical data to the medical care provider in connection with the medical care visit; or prior to the medical care visit with the medical care provider by the user; communicating, by the first virtual assistant function, the second portion of the updated medical data to a second virtual assistant function associated with the medical care provider, and presenting, via a second interface associated with the second virtual assistant function, the second portion of the updated medical data to the medical care provider in connection with the medical care visit is taught in the Detailed Description in ¶ 0065, ¶ 0203, and ¶ 0214-215 (teaching on sending an alert to the healthcare provider's user interface if, during the monitoring period of collecting patient parameter data, the data meets an alert threshold). As per claim 25, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 20. Rusak also discloses the following: the non-transitory machine-readable medium of claim 20, wherein the virtual assistant function is a first virtual assistant function, and wherein the receiving of the updated medical data comprises: receiving a second portion of the electronic medical records from a first device or a second virtual assistant function associated with a first medical care provider; and receiving a third portion of the electronic medical records from a second device or a third virtual assistant function associated with a second medical care provider is taught in the Detailed Description in ¶ 0212-215 (teaching on receiving additional second (historical patient sensor data) data from a secondary/plurality of other providers to be analysed by the machine learning model for generating a determined user action for the current target patient). As per claim 26, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 19. Rusak also discloses the following: the non-transitory machine-readable medium of claim 19, wherein the virtual assistant function is a first virtual assistant function, and wherein the operations further comprise: perceiving a medical condition associated with a user associated with the user identity while the user is at a first location; based on the perceiving, generating medical condition information relating to the medical condition; and is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on collecting a similar patient parameter data and corresponding first provider's interaction with said data related to the patient's condition (here the example is of a G6PD deficiency and diabetic diagnosis)); communicating the medical condition information to a second virtual assistant function associated with a medical care provider identity, wherein the second virtual assistant function is located at a second location is taught in the Detailed Description in ¶ 0116, ¶ 0130, and ¶ 0214-215 (teaching on alerting on a second provider's user interface regarding a determined user action for the current target patient related to the similar patient's condition wherein the second provider is at a separate medical institute (treated as synonymous to located at a second location)). As per claim 27, the combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 19. Rusak also discloses the following: the non-transitory machine-readable medium of claim 19, wherein the operations further comprise: receiving, from a medical care provider, a request for information relating to a medical or health history associated with the user identity is taught in the Detailed Description in ¶ 0201 and in the Figures in fig. 5 reference character 212 (teaching on the provider requesting a "battle plan" for a set of proposed determined user actions wherein requesting a plan necessarily requires the use of collecting patient historical and current data for processing by the model); identifying the information relating to the medical or health history associated with the user identity in the model a portion of the electronic medical records that is determined to be associated with the user identity, or sensor data associated with the user identity; and is taught in the Detailed Description in ¶ 0194, ¶ 0181, ¶ 0203, and in the Figures in fig. 5 reference characters 213 and 209 (teaching on processing via the machine learning model the collected historical and current patient data wherein the patient data includes electronic health record data); presenting, via an interface of the virtual assistant function to the medical care provider, the information relating to the medical or health history associated with the user identity is taught in the Detailed Description in ¶ 0200-201 and Figures in fig. 5 reference character 218 (teaching on displaying on the provider's user interface the "battle plan" with corresponding proposed determined user actions and real time current patient information concurrently). Claim 15 is rejected under 35 U.S.C. 103 as being unpatentable over Rusak (US Patent Pub No 2021/0225495)[hereinafter Rusak] in view of Chen et al., FedHealth: A Federated Transfer Learning Framework for Wearable Healthcare, 35(4) IEEE INTELLIGENT SYSTEMS 83-93 (April 22, 2020)[hereinafter Chen] in further view of Dirghangi et al. (US Patent Pub No 20180220889)[hereinafter Dirghangi] in further view of Shan et al. (US Patent No. 11636955)[hereinafter Shan]. As per claim 15, The combination of Rusak, Chen, and Dirghangi discloses the limitations of claim 13. Rusak fails to teach the following; Shan, however, does disclose: the system of claim 13, wherein the operations further comprise: determining, by the virtual assistant device, that first information relating to a medical condition associated with the user identity is subject to a higher privacy level based on a defined privacy criterion is taught in the Detailed Description in col 13 lines 4-13, col 13 lines 27-62, and in the Figures at fig. 7 reference character 704 (teaching on assigning patient data items to an access right level including secure data items (treated as synonymous to a higher privacy level)); determining, by the virtual assistant device, that second information relating to the user identity is subject to a lower privacy level based on the defined privacy criterion is taught in the Detailed Description in col 13 lines 4-13, col 13 lines 27-62, and in the Figures at fig. 7 reference character 704 (teaching on assigning patient data items to an access right level including unsecure data items (treated as synonymous to a lower privacy level)); in response to determining that the first information is subject to the higher privacy level, presenting, via a first interface of the virtual assistant device, the first information to the user, wherein the first interface is determined to be able to provide privacy of the first information at the higher privacy level for the presenting of the first information to the user, and wherein the first information presented via the first interface is only able to be perceived by the user; and is taught in the Detailed Description in col 14 lines 61-67, col 15 lines 44-51, and in the Figures at fig. 7 reference character 710 and 718 (teaching on displaying to a first provider and user the patient data determined to be a secure data item); in response to determining that the second information is subject to the lower privacy level, presenting, via a second interface of the virtual assistant device, the second information to the user, wherein the second interface is determined to be able to provide privacy of the second information at the lower privacy level for the presenting of the second information to the user, and wherein the second information presented via the second interface is able to be perceived by the user and another user other than the user is taught in the Detailed Description in col 15 lines 26-31, col 15 lines 44-51, and in the Figures at fig. 7 reference character 714 and 718 (teaching on displaying to a second provider on a user interface only the data determined to be an unsecure data item). One of ordinary skill in the art before the effective filing date of the invention would combine the machine learning clinical decision support system of Rusak with the data privacy controls for data access on different user interfaces of Shan with the motivation of “keep[ing] other users informed, engaged and participating in the patient’s disease management” (Shan in the Detailed Description in col 4 lines 40-43). Response to Arguments Applicant's arguments filed 04/17/2026 with respect to 35 USC § 101 have been fully considered but they are not persuasive. Applicant asserts that by performing a diagnostic test, the performance of the proposed action amounts to an improvement to technology. Examiner disagrees. Generically performing any medical testing based on a recommendation or alert is not a technical problem nor an unconventional technical solution. An indication that the claimed invention provides an improvement can include a discussion in the specification that identifies a technical problem and explains the details of an unconventional technical solution expressed in the claim, or identifies technical improvements realized by the claim over the prior art (MPEP § 2106.05(a)). Additionally, an important consideration in determining whether a claim improves technology is the extent to which the claim covers a particular solution to a problem or a particular way to achieve a desired outcome, as opposed to merely claiming the idea of a solution or outcome. McRO, 837 F.3d at 1314-15, 120 USPQ2d at 1102-03 (MPEP § 2106.05(a)(II)). The instant claims seem analogous to MPEP § 2106.05(a)(II) examples that the courts have indicated may not be sufficient to show an improvement to technology, example iii. Gathering and analyzing information using conventional techniques and displaying the result, TLI Communications, 823 F.3d at 612-13, 118 USPQ2d at 1747-48. Applicant’s arguments filed 04/17/2026 with respect to 35 USC § 103 have been considered and are persuasive regarding the newly added limitations. Therefore, the rejection has been withdrawn. However, upon further consideration, a new grounds of rejection is made in view of Dirghangi, as per the rejection above. Conclusion THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to JORDAN LYNN JACKSON whose telephone number is (571)272-5389. The examiner can normally be reached Monday-Friday 8:30AM-4:30PM ET. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Arleen M Vazquez can be reached at 571-272-2619. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /JORDAN L JACKSON/Primary Examiner, Art Unit 2857
Read full office action

Prosecution Timeline

Show 6 earlier events
Dec 26, 2025
Request for Continued Examination
Dec 28, 2025
Response after Non-Final Action
Jan 23, 2026
Non-Final Rejection mailed — §101, §103, §112
Apr 17, 2026
Response Filed
May 05, 2026
Final Rejection mailed — §101, §103, §112
Jul 17, 2026
Interview Requested
Jul 23, 2026
Examiner Interview Summary
Jul 23, 2026
Applicant Interview (Telephonic)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12738373
SYSTEM FOR MANAGING PATIENT SUPPORT APPARATUSES AND CLINICAL ROUNDS
1y 10m to grant Granted Sep 15, 2026
Patent 12706204
METHODS AND SYSTEMS FOR MEDICAL DATA PROCESSING
1y 11m to grant Granted Aug 11, 2026
Patent 12683016
MEDICAL IMAGE PROCESSING DEVICE, MEDICAL IMAGE PROCESSING SYSTEM, MEDICAL IMAGE PROCESSING METHOD, AND PROGRAM
2y 10m to grant Granted Jul 14, 2026
Patent 12667323
MEDICAL INFORMATION PROCESSING APPARATUS, MEDICAL INFORMATION PROCESSING METHOD, AND RECORDING MEDIUM
3y 9m to grant Granted Jun 30, 2026
Patent 12658309
METHODS AND SYSTEMS FOR PATIENT DISCHARGE MANAGEMENT
4y 0m to grant Granted Jun 16, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

5-6
Expected OA Rounds
41%
Grant Probability
79%
With Interview (+38.5%)
3y 2m (~0m remaining)
Median Time to Grant
High
PTA Risk
Based on 191 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month