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 .
Status of the Claims
Claims 1, 3-7, 9-12, and 14-21 are currently pending.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on July 17, 2026 has been entered.
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, 3-7, 9-12, and 14-20 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
Claims 1, 3-7, 9-12, and 14-20 are within the four statutory categories. Claims 1, 3-7, and 9-11 are drawn to a method for matching patients to providers, which is within the four statutory categories (i.e. process). Claims 12 and 14-20 are drawn to a system for matching patients to providers, which is within the four statutory categories (i.e. machine).
Prong 1 of Step 2A
Claim 1, which is representative of the inventive concept, recites: A method for automated entity field correction in an electronic database, the method comprising:
digitally tracking longitudinal engagement of multiple providers by patients, wherein a patient switching between multiple providers in a first period of time and then staying with another provider for a second period of time which is longer than the first period, is indicative of a good match between the provider for the second period of time and the patient;
generating historical feature vector inputs including a sequence of good provider matches and poor provider matches based on the tracked longitudinal engagement, with poor provider matches being different than the good provider match;
training a machine learning model, in circuitry using a long term short term neural network implementing a root mean squared error, with historical feature vector inputs including the sequence of good provider matches and poor provider matches for each patient to generate a provider match prediction output, wherein determining the provider match prediction output includes supplying the at least a portion of stored provider data to the machine learning model to generate the provider match prediction output, and assigning the provider match prediction output as a predicted best provider match for the patient, wherein the long term short term neural network includes inputs nodes that equal a number of the historical vector inputs and a plurality of intermediate nodes connected to the input nodes to receive respective input based, in part, on the historical vector inputs, and wherein the plurality of intermediate nodes are pruned when a weight associated with any individual intermediate node being zero;
receiving one or more target health conditions;
obtaining a set of multiple patient entries, stored patient data, stored claims data and stored prescription data, the set of multiple patient entries, store patient data, stored claims data and stored prescription data each stored in one or more databases;
for each patient entry in the set of multiple patient entries;
accessing at least a portion of the stored patient data, stored claims data and stored prescription data corresponding to the patient entry;
determining an eligibility status for the patient entry according to specified eligibility criteria and the accessed portion of the stored patient data, stored claims data, and stored prescription data, wherein the determined eligibility status is indicative of the patient entry being eligible for targeted outreach regarding the one or more target health conditions; and
in response to the patient entry having an eligible status, assigning the patient entry to an eligible subset of the set of multiple patient entries;
for each patient entry in the eligible subset;
determining an exclusion status for the patient entry according to specified exclusion criteria and the accessed portion of the stored patient data, stored claims data, and stored prescription data, wherein the exclusion status is indicative of the patient entry being excluded from targeted outreach regarding the one or more target health conditions; and
in response to the patient entry having a non-excluded status, assigning the patient entry to a non-excluded subset of the set of multiple patient entries;
accessing stored provider data; and
for each patient entry in the non-excluded subset;
determining a predicted best provider match for the patient entry by supplying at least a portion of the stored provider data and data of the patient entry to the machine learning model to generate the provider match prediction output, wherein the stored provider data supplied to the machine learning model includes different weights applied to different provider factors stored in a table or memory; and
transmitting the predicted best provider match to a computing device associated with the patient entry, to display the predicted best provider match on a user interface for selection by a user;
receiving a selection of the predicted best provider match via the user interface of the computing device; and
in response to receiving the selection of the predicted best provider match, transmitting the selection of the predicted best provider match to a server to update a database entry associated with the patient entry.
The underlined limitations as shown above, given the broadest reasonable interpretation, cover the abstract ideas of a mathematical concept and/or a certain method of organizing human activity because they recite mathematical relationships, formulas, equations, and/or mathematical calculations (in this case, the step of training the machine learning model using the long term short term neural network implementing a root mean squared error, the limitations pertaining to the feature vector inputs and the provider match prediction output, and the limitations pertaining to the nodes of the long short term neural network and the pruning of nodes with zero weights recite mathematical calculations because these terms include optimization algorithms which compute neural network parameters using a series of mathematical calculations), and/or managing personal behavior or relationships or interactions between people (i.e. social activities, teaching, and following rules or instructions – in this case, the steps of tracking longitudinal patient engagement data, generating historical feature vectors, generating a provider match prediction output, receiving target health conditions, accessing patient, claims, and prescription data, and analyzing the accessed data to determine patient eligibility, then further analyzing eligible patients to determine non-excluded patients, accessing provider data, determining a predicted best provider match for each eligible and non-excluded patient, and receiving a selection of the predicted best provider match recite following rules or instructions to determine and/or classify a patient-provider relationship, and/or filtering data), e.g. see MPEP 2106.04(a)(2). Any limitations not identified above as part of the abstract idea are deemed “additional elements,” and will be discussed in further detail below.
Furthermore, the abstract idea for Claim 12 is identical as the abstract ideas for Claim 1, because the only difference between Claims 1 and 12 is that Claim 1 recites a method, whereas Claim 12 recites a system and its associated structural elements.
Dependent Claims 3-7, 9-11 and 14-20 include other limitations, for example Claims 3-4 and 14-15 recite searching for multiple provider data sources, Claims 5-7, 10, 16-18, and 20 recite various types of eligibility criteria, Claim 8 recites receiving a selection of a provider and updating the patient data based on the provider selection, Claims 9 and 19 recite displaying provider subsets based on patient preferences, and Claim 11 recites a type of exclusion criteria, but these only serve to further narrow the abstract idea, and a claim may not preempt abstract ideas, even if the judicial exception is narrow, e.g. see MPEP 2106.04, and/or do not further narrow the abstract idea and instead only recite additional elements, which will be further addressed below. Hence dependent Claims 3-7, 9-11, and 14-20 are nonetheless directed towards fundamentally the same abstract ideas as independent Claims 1 and 12.
Prong 2 of Step 2A
Claims 1 and 12 are not integrated into a practical application because the additional elements (i.e. the non-underlined limitations above – in this case, the one or more databases, the computing device, the memory, and the processor, and the steps of transmitting and displaying the provider match) amount to no more than limitations which:
amount to mere instructions to apply an exception – for example, the recitation of the database, the computing device, the memory, and the processor, which amounts to merely invoking a computer as a tool to perform the abstract idea, e.g. see [0100], [0201], and [0216]-[0217] of the present Specification, see MPEP 2106.05(f);
generally link the abstract idea to a particular technological environment or field of use – for example, the claim language of patient, claims, prescription, and provider data, which amounts to limiting the abstract idea to the field of healthcare, see MPEP 2106.05(h); and/or
add insignificant extra-solution activity to the abstract idea – for example, the recitation of transmitting and displaying provider match data and the selection of the predicted best provider match, which amounts to an insignificant application, see MPEP 2106.05(g).
Additionally, dependent Claims 3-7, 9-11 and 14-20 include other limitations, but these limitations also amount to no more than mere instructions to apply an exception (e.g. the APIs recited in dependent Claims 3-4 and 14-15), generally linking the abstract idea to a particular technological environment or field of use (e.g. the types of data recited in dependent Claims 5-7, 10, 16-18, and 20), and/or do not include any additional elements beyond those already recited in independent Claims 1 and 12, and hence also do not integrate the aforementioned abstract idea into a practical application.
Hence Claims 1-7, 9-12, and 14-20 do not include additional elements that integrate the judicial exception into a practical application.
Step 2B
Claims 1 and 12 do not include additional elements that are sufficient to amount to “significantly more” than the judicial exception because the additional elements (i.e. the non-underlined limitations above – in this case, the one or more databases, the computing device, the memory, and the processor, and the steps of transmitting and displaying the provider match), as stated above, are directed towards no more than limitations that amount to mere instructions to apply the exception, generally link the abstract idea to a particular technological environment or field of use, and/or add insignificant extra-solution activity to the abstract idea, wherein the additional elements comprise limitations which:
amount to elements that have been recognized as well-understood, routine, and conventional activity in particular fields, as demonstrated by:
The present Specification expressly disclosing that the structural additional elements are well-understood, routine, and conventional in nature:
[0100], [0201], and [0216]-[0217] of the Specification discloses that the additional elements (i.e. the recitation of the database, the computing device, the memory, and the processor) comprise a plurality of different types of generic computing systems;
Relevant court decisions: The functional limitations interpreted as additional elements are analogized to the following examples of court decisions demonstrating well-understood, routine and conventional activities, e.g. see MPEP 2106.05(d)(II):
Receiving or transmitting data over a network, e.g. see Intellectual Ventures v. Symantec – similarly, the current invention receives health condition and patient data, performs and analysis to determine provider match data, and transmits the provider match data and the selection of the predicted best provider match over a network to display the best provider match, e.g. see [0047]-[0048] of the present Specification;
Electronic recordkeeping, e.g. see Alice Corp v. CLS Bank – similarly, the current invention merely recites the storing of patient and provider data on a database and/or electronic memory; and/or
Storing and retrieving information in memory, e.g. see Versata Dev. Group, Inc. v. SAP Am., Inc. – similarly, the current invention recites storing patient and provider data in a database and/or electronic memory, and retrieving the patient and provider data from storage in order to determine the provider match data.
Dependent Claims 3-7, 9-11 and 14-20 include other limitations, but none of these limitations are deemed significantly more than the abstract idea because the additional elements recited in the aforementioned dependent claims similarly amount to mere instructions to apply the exception (e.g. the APIs recited in dependent Claims 3-4 and 14-15), generally linking the abstract idea to a particular technological environment or field of use (e.g. the types of data recited in dependent Claims 5-7, 10, 16-18, and 20)and/or the limitations recited by the dependent claims do not recite any additional elements not already recited in independent Claims 1 and 12, and hence do not amount to “significantly more” than the abstract idea.
Hence, Claims 1, 3-7, 9-12, and 14-20 do not include any additional elements that amount to “significantly more” than the judicial exception.
Thus, taken alone, the additional elements do not amount to significantly more than the abstract idea identified above. Furthermore, looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually, and there is no indication that the combination of elements improves the functioning of a computer or improves any other technology, and their collective functions merely provide conventional computer implementation.
Therefore, whether taken individually or as an ordered combination, Claims 1, 3-7, 9-12, and 14-20 are nonetheless rejected under 35 U.S.C. 101 as being directed to non-statutory subject matter.
Allowable Subject Matter
Claims 1, 3-7, 9-12, and 14-20 are not presently rejected under 35 U.S.C. 102 or 103, and hence would be in condition for allowance if amended to overcome the rejections presented under 35 U.S.C. 101. The following represents Examiner’s characterization of the most relevant prior art references and the differences between the present claim language and the prior art references in view of 35 U.S.C. 102 and/or 103, and is reproduced from the Final Rejection mailed on June 4, 2025:
With regards to 35 U.S.C. 102 and/or 103, the following represents the closest prior art to the claimed invention, as well as the differences between the prior art and the limitations of the presently claimed invention.
Olsen (US 2017/0278209) teaches a system for matching patients with care providers, wherein the matching utilizes a plurality of rules, for example a patient being diagnosed with a particular disease or malady, that ultimately determine a ranked list of care providers for the patient. However, Olsen does not teach training a machine learning model utilizing historical feature vector comprising good and poor provider matches, and utilizing the trained machine learning model to generate a provider match prediction output that is assigned as the provider match. Furthermore, Olsen does not teach tracking longitudinal engagement data, wherein the longitudinal engagement data is indicative of a good match between a patient and provider when it shows a patient switching between multiple providers for a first period of time and then staying with another provider for a second period of time that is longer than the first period of time.
Karampourniotis (US 2021/0265063) teaches a machine learning module that utilizes historical data, for example electronic health records and historical treatment plans, as training data in order to determine an appropriate healthcare provider (i.e. a provider match prediction output) for a patient. However, Karampourniotis does not teach that the historical data includes longitudinal engagement data that is indicative of a good match between a patient and provider when it shows a patient switching between multiple providers for a first period of time and then staying with another provider for a second period of time that is longer than the first period of time.
Aunger (US 2018/0211059) teaches tracking a threshold period of time during which the patient has seen an outside medical professional with a same type as an earlier trusted medical professional, indicating that the patient is seeing a new doctor instead of an old doctor. However, Aunger does not teach a plurality of threshold periods of time (i.e. first and second periods of time), or that one threshold period of time is longer than another (i.e. the second period of time being longer than the first period of time). Additionally, Aunger teaches tracking the fact that the patient is seeing a new doctor instead of an old doctor (i.e. engagement data) in order to determine whether or not the doctor should be provided access to a patient data, but does not teach inputting the engagement data into a machine learning model to train the model, and/or utilizing the trained machine learning model to generate a provider match prediction output that is assigned as the provider match.
Schneberk (“Opiod prescription patterns among patients who doctor shop; Implications for providers,” PLOS ONE, May 26, 2020) teaches tracking patient and doctor behaviors during doctor shopping periods, specifically statistics relating to number and type of prescriptions issued during the period and usage data of the drugs prescribed, and further teaches tracking the same data outside of doctor shopping periods, wherein the time outside of doctor shopping periods may be longer than the time for the doctor shopping period. However, Schneberk does not teach that the patient behaviors indicate a good or poor match between the providers and the patient. Additionally, although Schneberk defines doctor shopping as a patient receiving greater than 6 or more prescriptions from at least 6 different prescribers within 6 months of time (i.e. during the first period of time), it does not teach that the patient stays with a single doctor during the non-doctor shopping period (i.e. the second period of time). Additionally, Schneberk does not teach inputting the patient and doctor behavior data, both during and outside the doctor shopping period, into a machine learning model to train the model, and further does not teach generating the provider match prediction output using the trained machine learning model. Furthermore, Schneberk does not teach utilizing the aforementioned data to determine provider matches.
The Health Foundation (“Measurement The various measures of Continuity of Care,” Morecambe Bay Primary Care Collaborative, April 2020) teaches various metrics measuring continuity of care including Usual Provider of Care (UPC), which describes the proportion of visits to the patient’s regular care provider out of all visits, Continuity of Care Index, which describes the frequency of visits to each care provider, and St Leonard’s Index of Continuity of Care, which compares groups of patients and is intended for use within a practice. However, The Health Foundation does not teach calculating the aforementioned metrics using different time periods that vary in length (i.e. the first and second periods of time). Furthermore, The Health Foundation does not teach inputting any of the aforementioned metrics into a machine learning model to train the model, and further does not teach generating the provider match prediction output using the trained machine learning model. Furthermore, The Health Foundation does not teach utilizing the aforementioned data to determine provider matches.
The aforementioned references are understood to be the closest prior art. Various aspects of the present invention are known individually, but for the reasons disclosed above, the particular manner in which the elements are claimed, when considered as an ordered combination, distinguishes from the aforementioned references and hence the invention recited in Claims 1, 3-12, and 14-20 is not considered to be a non-novel and/or obvious variant of the inventions taught by the closest prior art references.
Additionally, regarding Claim 21, Claim 21 is objected to as being dependent upon a rejected base claim (Claim 1), but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. That is, Claim 21 is not presently rejected under 35 U.S.C. 102 or 103 for the reasons disclosed above, and Claim 21 is further not rejected under 35 U.S.C. 101 for reasons that will be discussed in further detail below, e.g. see Response to Arguments section, and would be allowable if incorporated into independent Claim 1, and/or rewritten in independent form including the limitations from independent Claim 1.
Response to Arguments
Applicant’s arguments, see Remarks, filed July 17, 2026, with respect to the rejections of Claims 1, 3-7, 9-12, and 14-21 under 35 U.S.C. 112(b) have been fully considered and, in combination with the amendments, are persuasive. The previous rejections of Claims 1, 3-7, 9-12, and 14-21 under 35 U.S.C. 112(b) have been withdrawn.
Applicant’s arguments, see Remarks, filed July 17, 2026, with respect to the rejections of Claims 1, 3-7, 9-12, and 14-20 under 35 U.S.C. 101 have been fully considered but are not persuasive.
Applicant alleges that the claimed invention is patent eligible because it does not recite an abstract idea, specifically because it recites an ordered, computer-implemented architecture for automated entity field correction in an electronic database and further recites concrete data structures and processing operations as part of a computer-implemented workflow, e.g. see pgs. 9-10 of Remarks – Examiner disagrees.
Examiner initially notes that a claimed invention is not patent eligible merely because it implements an abstract idea on a physical machine, e.g. see MPEP 2106(I). Additionally, the Claims being narrowly claimed is not dispositive in determining the eligibility of the Claims. The Court has held that a claim may not preempt abstract ideas, laws of nature, or natural phenomena, even if the judicial exception is narrow, e.g. see MPEP 2106.04. That is, a claim reciting a narrow abstract idea nonetheless recites an abstract idea and must be evaluated under the remainder of the requirements under 35 U.S.C. 101.
Hence, for the reasons disclosed above, the claimed invention is properly characterized as reciting the abstract idea of a mathematical concept and/or a certain method of organizing human activities.
Applicants further allege that the claimed invention is patent eligible because they integrate any abstract idea into a practical application, specifically because Examiner’s analysis improperly treats the databases, memory, processor, transmitting, displaying, and updating steps as generic computer components or extra-solution activity in isolation, e.g. see pgs. 11-12 of Remarks – Examiner disagrees.
As stated above, the analysis of the aforementioned elements does not change whether they are considered individually or as an ordered combination because none of the hardware elements or functions operate differently in concert with one another as opposed to separately. For example, the databases, memory, and processor are known, off-the-shelf, general purpose hardware elements, e.g. see [0100], [0201], and [0216]-[0217] of the as-filed Specification, and the functional steps of transmitting data, displaying data, and updating data are properly characterized as extra-solution activities, specifically receiving or transmitting data over a network, electronic recordkeeping, and/or storing and retrieving information in memory. Additionally, Applicant alleges that the selection and transmission of best provider matches for display, and the weighting for ranking inputs “impose meaningful limits on any alleged abstract idea, and apply the abstract idea through a concrete, technology-rooted data-processing implementation,” but as stated above, the fact that these limitations are narrowly claimed (i.e. “meaningfully limited” and/or “concrete”) is not dispositive with regards to subject matter eligibility, e.g. see MPEP 2106.04 and MPEP 2106.05(I).
Applicant further alleges that the claimed invention is patent eligible because it recites significantly more than the abstract idea, specifically because it recites a particular implementation of automated database correction and multidimensional provider matching, e.g. see pg. 11 of Remarks – Examiner disagrees.
As stated above, the breadth/narrowness of the Claims is not dispositive of the eligibility of the Claims because the absence of complete preemption does not guarantee that a claim will be eligible, and preemption is not a stand-alone test for patentability, but rather is inherent in the two-part Alice/Mayo framework, e.g. see MPEP 2106.04. That is, even assuming, arguendo, that the claimed invention recites a particular configuration for an abstract idea, a narrow abstract idea nonetheless recites an abstract idea, and the broadness/narrowness of the abstract idea is not, by itself, dispositive of the eligibility of the claim. Furthermore, as shown above, Examiner has provided evidence demonstrating that the present invention is directed towards at least one court-identified abstract idea that is not integrated into a practical application, and further that the additional elements of the present invention (i.e. any elements not identified as part of the abstract idea) do not represent significantly more than the abstract idea, and hence has addressed any concerns arising from preemption.
Furthermore, regarding the “database correction,” the claimed invention claims receiving a selection of the predicted best provider match via the user interface of the computing device, and transmitting the selection of the predicted best provider match to a server to update a database entry. That is, the updating (i.e. correction) of the data in the database is explicitly triggered by a human interacting with the user interface by selecting the predicted best provider. Moreover, even if the “database correction” operation were performed automatically, Examiner asserts that merely updating data stored in a database, whether automatically or manually, does not recite significantly more than an abstract idea but instead recites insignificant extra-solution activity in the form of electronic recordkeeping. Furthermore, regarding the weighting of the provider factors, this recites the mathematical concept of a multiplier for a data element and hence is not significantly more than the abstract idea.
Regarding Claim 21, as stated above, Claim 21 is no longer rejected under 35 U.S.C. 101. As previously stated in the Final Rejection mailed on April 17, 2026, a medication dispenser that performs operations including the dispensing of medication as a result of the data processing steps of the method of Claim 1 (from which Claim 21 depends) recites a particular machine because it recites a medication dispenser configured to implement the steps of the method, e.g. see MPEP 2106.05(b). Furthermore, as presently amended, Claim 21 now recites receiving prescription data corresponding to the selection of the predicted best provider match, controlling movement of a set of containers based on the prescription data, and automatically dispensing the prescription drug into a container of the set of containers. Therefore, the aforementioned dispenser (i.e. a hardware element comprising a particular machine) applies the judicial exception (i.e. the mathematical concept and/or certain method of organizing human activities), and hence Claim 21 is eligible under 35 U.S.C. 101.
For the aforementioned reasons, Claims 1, 3-7, 9-12, and 14-20 are rejected under 35 U.S.C. 101.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure is as follows:
Jonassen (US 2020/0293528) – teaches a system for categorizing clinical data utilizing machine learning.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN P GO whose telephone number is (703)756-1965. The examiner can normally be reached Monday-Friday 9am-6pm Pacific.
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, PETER H CHOI can be reached at (469)295-9171. 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.
/JOHN P GO/Primary Examiner, Art Unit 3681