DETAILED ACTION
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 .
Notice to Applicant
The following is a Final Office Action for Application Serial Number: 18/593,363, filed on March 01, 2024. In response to Examiner’s Non-Final Rejection dated February 26, 2026, Applicant on June 25, 2026 amended claims 1, 8 and 15 and cancelled claims 3, 10 and 17. Claims 1, 2, 4-9, 11-16 and 18-20 are pending in this application and have been rejected below.
Response to Amendment
Applicant's amendments are acknowledged.
Regarding the 35 U.S.C. 101 rejection, Applicants arguments and amendments have been considered but are insufficient to overcome the rejection.
The 35 U.S.C. § 102/103 rejections are hereby withdrawn in light of Applicant’s amendments to claims 1, 8 and 15.
Response to Arguments
Applicant's Arguments/Remarks filed June 25, 2026 (hereinafter Applicant Remarks) have been fully considered but are not persuasive. Applicant’s Remarks regarding the pending rejections will be addressed herein below in the order in which they appear in the response filed June 25, 2026.
Regarding the 35 U.S.C. 101 rejection, Applicant states amended independent claims 1, 8, and 15 each recite assigning, receiving, determining, retrieving and routing limitations (see p. 10, Applicant Remarks). Applicant states A person cannot, "as a practical matter," perform these operations in the human mind. For example, a human cannot: " accept an inbound electronic message (a phone call, IP packet, or email) addressed to a role-bound network address (Spec. [0099]); " query a directory database to identify the device on which a particular provider account is currently authenticated- i.e., to determine which fungible user device the on-shift provider has logged into (Spec. [0101]); or " re-route an in-flight communication from one network address to a different, dynamically resolved network address based on a real-time roster lookup (Spec. [0138]).
These are quintessentially computer-network operations performed by a "communication engine" (Spec. ¶¶ [0073], [0102], [0135], [0138]). They cannot be performed by a human "by a combination of the human mind and a human using pen and paper" as the Office Action asserts. See CyberSource Corp. v. Retail Decisions, Inc., 654 F.3d 1366, 1373 (Fed. Cir. 2011) (the mental-process inquiry asks whether the steps can be performed "in the human mind, or by a human using a pen and paper"; they cannot here).
In response, Examiner finds Applicant is arguing limitations that are not considered abstract and therefore have not and will not be analyzed under Step 2A – Prong One. Nonetheless, Examiner finds Applicant’s arguments to be both collecting and delivering data and using computer components as a tool to apply the operations of the abstract idea. Examiner finds Applicant’s arguments are not persuasive in taking the claim out of the mental processes grouping. Claims can recite a mental process even if they are claimed as being performed on a computer; see MPEP 2106.04(a)(2)(III)(C). Examiner notes even in a computer environment, the pending limitations are still considered abstract by reciting limitations that mimic human thought processes of observation, evaluations, judgement and opinion, that can feasibly be performed with pen and paper, where the data interpretation is perceptible in the human mind. Examiner maintains the claim recites an abstract idea of converting roster data from a first configuration into a second configuration.
Regarding the 35 U.S.C. 101 rejection, Applicant states the Office Action's alternative characterization of independent claims 8 and 15 as reciting a "certain method of organizing human activity" (Office Action at 3) is also untenable as applied to the amended claims. The recited operations are not "managing personal behavior or relationships or interactions between people." They are network-routing operations performed by a communication engine on machine-to- machine communications between a user device, a directory database, and a target device. See MPEP § 2106.04(a)(2)(II) (defining the "managing personal behavior" sub- grouping).
Accordingly, the amended claims do not recite a judicial exception under Step 2A Prong One, and the § 101 rejection should be withdrawn on that basis alone.
In response, Examiner respectfully disagrees and finds that the claims recite, in part, roster systems comprising role identifiers identifying a role within the provider system fillable by different provider accounts, where ultimately messages are routed from a user device to a target device on which a target provider account is currently authenticated, which Examiner finds constitutes methods based on managing personal behavior. Examiner finds Applicants abovementioned arguments are not technological in nature and merely limits the abstract idea to a particular environment.
Regarding the 35 U.S.C. 101 rejection, Applicant states Specification expressly identifies a technical problem and a technical solution. The Specification identifies a concrete technical problem in provider-system communications networks: when a particular role (e.g., "charge nurse on floor 9" or "on-call neurosurgeon") is filled by different providers across different shifts, conventional approaches require either (a) callers to look up the role-holder in a roster system and then look up that provider's phone number in a directory (Spec.[0026]), or (b) assigning a particular physical phone to a role and physically passing the phone between providers at each shift change (id.). Both approaches generate substantial network overhead - additional message routing, repeated authentication exchanges (including Diffie-Hellman key exchange), onboarding traffic when new user devices are introduced (such as for travel nurses), and rework caused by misrouted calls (Spec. ¶¶ [0025]-[0027]).
The amended claims solve that technical problem with a specific architecture: a first communication address is bound to the role itself, and the communication engine, upon receiving a message at that role-bound address, performs a real-time lookup against the consolidated converted roster (keyed by role and current time) to identify the currently authenticated target device of the on-shift provider, and routes the message to that target device - the address of which "dynamically changes as the provider account filling the role changes" (claim 1 final clause; Spec. ¶¶ [0102], [0138]).
The Specification expressly recites the resulting technical benefits (see p. 12, Applicant Remarks) and Applicant notes these are precisely the kinds of computing improvements the Federal Circuit has held are eligible (see p. 13-14, Applicant Remarks).
In response, Examiner respectfully disagrees. Examiner finds Applicant has failed to adequately point out what technological process in the claimed invention has improved. Applicants abovementioned arguments are considered improvements a to an existing business (workforce/equipment management) process and not an improvement to the functioning of a computer, other technological field, or computer-related technology. Merely confining the abstract idea to a particular technological environment does not establish a practical application. See Guidance, 84 Fed. Reg. at 54. “A claim does not cease to be abstract for section 101 purposes simply because the claim confines the abstract idea to a particular technological environment in order to effectuate a real-world benefit.” In re Mohapatra, 842 F. App’x 635, 638 (Fed. Cir. 2021). Examiner finds, Applicant is attempting to say the Step 2A-Prong One elements, the abstract idea, is what makes the claim eligible. Examiner finds Applicant has not identified any limitations in the claimed invention that show or submit that the computer technology used is being improved or there was a problem in or with the computer technology that the claimed invention solves. Examiner maintains the claims are directed to an abstract idea.
Regarding the 35 U.S.C. 101 rejection, Applicant states the amended claims are most directly analogous to Example 42 (see p. 14, Applicant Remarks). The present amended claims recite the analogous Example 42 architecture (heterogeneous roster systems associated with different units of a provider system are converted and recorded into a consolidated second roster system), plus an additional, independently eligible improvement - the role-bound dynamic-address resolution and routing mechanism. The claim is at least as eligible as Example 42's claim 1.
In response, Examiner respectfully disagrees. Examiner finds claim 1 of Example 42 as a whole, integrates the method of organizing human activity into a practical application. Specifically, the additional elements recite a specific improvement over prior art systems by allowing remote users to share information in real time in a standardized format regardless of the format in which the information was input by the user. Examiner finds no comparable improvements recited in the present invention. The claim does not reflect any improvement to the computer components, but instead the improvement is directed towards the operating conditions (e.g., workforce/equipment management) of computing devices within a consolidated roster system. Examiner maintains the claims are directed to an abstract idea.
Regarding the 35 U.S.C. 101 rejection, Applicant states amended claims are additionally analogous to Example 35 - Verifying a Bank Customer's Identity to Permit an ATM Transaction, claim 2 of which the USPTO found eligible because it included specific technological steps that solved a problem at a particular point in a computing process. Here, retrieving the second communication address based on which device the target account is currently authenticated on (claim limitation; Spec. [0101]) is a directly analogous specific technological operation.
In response, Examiner respectfully disagrees. Examiner notes Example 35 was found eligible due to the combination of the steps (e.g., the ATM providing a random code, the mobile communication device’s generation of the image having encrypted code data in response to the random code, the ATM’s decryption and analysis of the code data, and the subsequent determination of whether the transaction should proceed based on the analysis of the code data) operates in a non conventional and non‐generic way to ensure that the customer’s identity is verified in a secure manner that is more than the conventional verification process employed by an ATM alone. In combination, these steps do not represent merely gathering data for comparison or security purposes, but instead set up a sequence of events that address unique problems associated with bank cards and ATMs (e.g., the use of stolen or “skimmed” bank cards and/or customer information to perform unauthorized transactions). Examiner finds no similar improvement here. Instead, Examiner finds the pending claims recite additional elements at a high level of generality that perform programmed functions representing conventional operations of the computing devices, including accessing, converting, recording data and assigning communication addresses to role identifiers, receiving messages and determining and retrieving target provider accounts to route said messages. Examiner maintains the additional elements recited in the claim function as intended with no improvement to the technology.
Regarding the 35 U.S.C. 101 rejection, Applicant states the Office Action's Step 2A Prong Two finding rested entirely on the conclusory statement that "computing device" was recited at a "high-level of generality such that it amounts to no more than generic computer components used as a tool to apply the instructions of the abstract idea" (Office Action at 3). That observation, even if it could ever have been made of the original claim, cannot survive the amendment. The amended claims now recite specific computer-network operations - receiving a message at a role-bound first address, querying a directory database for the second address of a device on which the target account is currently authenticated, and routing the message to that dynamically-resolved address - that go far beyond "apply it on a computer." This is "a particular way" of achieving "a specific" technical result - the hallmark of McRO and DDR Holdings. See McRO, Inc. v. Bandai Namco Games Am., Inc., 837 F.3d 1299, 1313-14 (Fed. Cir. 2016).
In response, Examiner respectfully disagrees. Examiner notes McRO, demonstrated improvements to a specific technological process (i.e., lip synchronization and manipulation of character facial expressions), thus improving computer animation without requiring an artist's constant intermediation with significant support in the specification and DDR Holdings, LLC v. Hotels.com, 773 F.3d 1245 (Fed. Cir. 2014) presents an invention that is rooted in computer technology. Specifically, the court found when a third party's advertisement hyperlink was selected by a user on a host's web page, the system would automatically identify the host web page, retrieve corresponding "look and feel" information from storage for the host page and generate a hybrid web page including the merchant information from the third-party web page with the "look and feel" elements of the host's website. This is different from conventional Internet hyperlink operations which would redirect a user to the third-party page away from the host's web page when the hyperlink is activated and therefore added a specific limitation other than what is well-understood, routine and conventional in the field. Again, Examiner finds there are no similar improvements here and maintains Applicant’s abovementioned arguments are not technological in nature but merely confines the abstract idea to a particular technological environment or field of use; see MPEP 2106.05(h). The routing of messages to target devices based on authenticated target provider accounts of a consolidated roster system does not reflect an improvement to a technology, technological field or computer related technology. Examiner finds the claims aim to provide advantages to the operations of an existing business industry (see Specification par. 0018; 0021; 0024; 0027; 0029).
Regarding the 35 U.S.C. 101 rejection, Applicant states the Office Action's Step 2B authorities are inapposite. The Office Action cites Symantec, buySAFE, Ultramercial, Versata, and OIP - all cases involving generic data-gathering, data-transmission, or recordkeeping steps applied to underlying commercial concepts. None of those cases involved a role-bound network address with dynamic resolution to the currently-authenticated device of a dynamically-changing role-holder in a medical facility. The Examiner's reliance on those cases is misplaced.
Furthermore, Applicant states the Examiner has not carried the Berkheimer burden. Under Berkheimer v. HP Inc., 881 F.3d 1360, 1369 (Fed. Cir. 2018), and the Office's April 19, 2018 Memorandum on Berkheimer, an Examiner asserting that additional elements are "well- understood, routine, and conventional" must support that finding with one of four specified evidentiary showings. The Office Action makes no such factual showing. The combination recited in amended claim 1 (assigning a role-bound first address, receiving a message addressed thereto, looking up the current role-holder and the device on which the holder is currently authenticated, and dynamically routing the message accordingly) is not described anywhere in the Office Action's cited art (Tavakol, Loeffen, Detwiler) as conventional. To the contrary, the Specification expressly identifies the role-bound-routing approach as a technical advance over conventional directory-based call routing. Spec. ¶¶[0026]-[0027].
In response, Examiner respectfully disagrees. First, Applicant is respectfully reminded novelty and non-obviousness over the prior art, have no bearing on whether a claim recites an abstract idea. Although the courts often evaluate considerations such as the conventionality of an additional element in the eligibility analysis, the search for an inventive concept should not be confused with a novelty or non-obviousness determination. See Mayo, 566 U.S. at 91, 101 USPQ2d at 1973 (rejecting "the Government’s invitation to substitute §§ 102, 103, and 112 inquiries for the better established inquiry under § 101 "). As made clear by the courts, the "‘novelty’ of any element or steps in a process, or even of the process itself, is of no relevance in determining whether the subject matter of a claim falls within the § 101 categories of possibly patentable subject matter." Intellectual Ventures I v. Symantec Corp., 838 F.3d 1307, 1315, 120 USPQ2d 1353, 1358 (Fed. Cir. 2016) (quoting Diamond v. Diehr, 450 U.S. at 188–89, 209 USPQ at 9). See also Synopsys, Inc. v. Mentor Graphics Corp., 839 F.3d 1138, 1151, 120 USPQ2d 1473, 1483 (Fed. Cir. 2016) ("a claim for a new abstract idea is still an abstract idea. The search for a § 101 inventive concept is thus distinct from demonstrating § 102 novelty."). In addition, the search for an inventive concept is different from an obviousness analysis under 35 U.S.C. 103. See, e.g., BASCOM Global Internet v. AT&T Mobility LLC, 827 F.3d 1341, 1350, 119 USPQ2d 1236, 1242 (Fed. Cir. 2016) ("The inventive concept inquiry requires more than recognizing that each claim element, by itself, was known in the art. . . . [A]n inventive concept can be found in the non-conventional and non-generic arrangement of known, conventional pieces."). Specifically, lack of novelty under 35 U.S.C. 102 or obviousness under 35 U.S.C. 103 of a claimed invention does not necessarily indicate that additional elements are well-understood, routine, conventional elements. Because they are separate and distinct requirements from eligibility, patentability of the claimed invention under 35 U.S.C. 102 and 103 with respect to the prior art is neither required for, nor a guarantee of, patent eligibility under 35 U.S.C. 101; see MPEP 2106.05(I).
Furthermore, Examiner finds the analysis in Step 2B addresses the question on whether an additional element (or combination of additional elements) represents well-understood, routine and/or conventional activities. Examiner maintains Applicant is attempting to say the Step 2A-Prong One elements, the abstract idea, is what makes the claim eligible. Applicant has not identified any disclosure in the claimed invention showing and/or submitting that the technology used is being improved, there was a technical problem in the technology that the claimed invention solves, or the ordered combinations of the known elements is significantly more than identified abstract idea. Examiner maintains the additional elements (e.g., computing device via a network connection comprising one or more processors in communication with one or more memories and non-transitory computer-readable medium storing instructions executed by one or more processors of a computing device) recited in the claims perform generic functions (i.e., such as receiving or transmitting data over a network, electronic recordkeeping, and storing and retrieving information in memory) without reciting any limitations that amount to “significantly more” than the judicial exception. Applicant has not made any persuasive argument that would alter this analysis.
Additionally, Examiner finds Applicants remarks regarding the Berkheimer Memorandum are moot because the Examiner never referred to or described any of the claim elements as “well-understood, routine and conventional”. However, Examiner notes in light of Berkheimer, Examiner did point to citations reciting computer functions outlined in MPEP 2106.05(d)(II) that the courts found to be well-understood, routine, and conventional in nature (e.g. receiving or transmitting data over a network, e.g., using the Internet to gather data, electronic recordkeeping, and storing and retrieving information in memory), therefore satisfying the requirements outlined in the Berkheimer Memo. Examiner finds the pending claims do not disclose any unconventional computer functions that can be considered significantly more than the judicial exception.
Regarding the 35 U.S.C. 101 rejection, Applicant states the Office Action's characterization of message routing as "insignificant extra-solution activity" is wrong as to the amended claims. The Office Action dismisses the routing limitation of cancelled claim 3 (now incorporated into amended claim 1) as "insignificant extra-solution activities of collecting and delivering data" under MPEP § 2106.05(g). That characterization is incorrect even with respect to the original claim language. It is plainly incorrect as applied to the amended claims. The routing limitation in amended claim 1 is not mere data delivery. It is preceded and informed by two distinct database lookups (the converted-roster lookup keyed on role and current time, and the directory lookup keyed on the current-authentication state of the target provider account), and it produces a dynamically changing second communication address - i.e., the routing destination is not predetermined and is not extra-solution to the recited operations; it is an aspect of the claimed network improvement. See MPEP § 2106.05(g) (insignificant extra-solution activity is "incidental" data gathering or output that is "not significant" to the claimed result); cf. Bascom Global Internet Servs., Inc. v. AT&T Mobility LLC, 827 F.3d 1341, 1350 (Fed. Cir. 2016) (the ordered combination of otherwise familiar elements may itself supply the inventive concept).
In response, Examiner finds Applicant arguments are moot in light of the current amendments. Please see the updated 35 U.S.C. 101 for further explanation and rationale.
Regarding the 35 U.S.C. 101 rejection, Applicant states dependent claims 5-7, 12-14, and 18-20 recite further technical specificity (ordered-list sorting and half-interval search). These dependent claims independently confirm eligibility because they recite "a particular way" of organizing the converted roster data and locating entries therein. Cf. MPEP § 2106.05(a) (improvements to the functioning of a computer or to other technology). Claims 2, 9, and 16 (accessing the converted roster data) and claims 4 and 11 (network connection) likewise inherit the eligibility of their independents. For all of the foregoing reasons, the § 101 rejection of claims 1-20 should be withdrawn.
In response, Examiner respectfully disagrees. Examiner does not find Applicants above-mentioned arguments persuasive and finds the dependent claims currently do not include any inventive concepts that would render the claims eligible over 35 U.S.C 101. Examiner maintains the dependent claims recite additional element limitations that amount to no more than generic computer components used as tools to apply the instructions of the abstract idea and limitations that further narrow the abstract idea of routing messages to a target device based on authenticated target provider accounts of a consolidated roster system, which constitutes methods based on certain methods of organizing human activity and mental processes. Applicant has not identified any disclosure that would alter this analysis. For at least these reasons, the claims remain rejected under 35 U.S.C. § 101 as being directed to non-statutory subject matter.
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, 2, 4-9, 11-16 and 18-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Step 1: The claimed subject matter falls within the four statutory categories of patentable subject matter.
Claims 1, 2 and 4-7 are directed towards a computer-implemented method, claims 8, 9 and 11-14 are directed towards a computing device and claims 15, 16 and 18-20 are directed towards a non-transitory computer-readable medium, which are among the statutory categories of invention.
Step 2A – Prong One: The claims recite an abstract idea.
Claims 1, 2, 4-9, 11-16 and 18-20 recite routing messages to a target device based on authenticated target provider accounts of a consolidated roster system.
Claim 1 recites limitations directed to an abstract idea based on certain methods of organizing human activity and mental processes. Specifically, identifying a plurality of first roster systems, each first roster system associated with a unit of a provider system; accessing a roster data of the first roster system, each entry of the roster data comprising at least a time range and an identifier, the identifier comprising a role identifier, the role identifier identifying a role within the provider system that is fillable by different provider accounts at different times; converting the roster data from a first roster configuration into a second roster configuration; and recording the converted roster data in a second roster system, the second roster system being a consolidated roster system common to the plurality of first roster systems constitutes methods based on managing personal behavior, was well as methods based on observations, evaluations, judgements and/or opinion that can be performed mentally by a combination of the human mind and a human using pen and paper. The recitation of a by the computing device via a network connection does not take the claim out of the certain methods of organizing human activity and mental processes groupings. Thus the claim recites an abstract idea. Claims 8 and 15 recite certain method of organizing human activity and mental processes for similar reasons as claim 1.
Step 2A – Prong Two: The judicial exception is not integrated into a practical application.
The judicial exception is not integrated into a practical application. In particular, claim 1 recites assigning, by the computing device, a first communication address to the role identifier, the first communication address being bound to the role identifier rather than to any particular provider account; receiving, by the computing device from a user device, a message addressed to the first communication address; determining, by the computing device based at least in part on the converted roster data in the second roster system and a current time, a target provider account currently filling the role identified by the role identifier; retrieving, by the computing device from a directory database, a second communication address associated with a target device on which the target provider account is currently authenticated: and routing, by the computing device, the message from the user device to the target device using the second communication address, wherein the second communication address dynamically changes as the provider account filling the role changes in such a way that it amounts to no more than generic computer components used as tools to apply the instructions of the abstract idea; see MPEP 2106.05(f), as well as generally linking the use of the judicial exception to a particular technological environment or field of use; see MPEP 2106.05(h). Thus, the additional elements do not integrate the abstract idea into practical application because they do not impose any meaningful limitations on practicing the abstract idea. Claim 1 as a whole, looking at the additional elements individually and in combination, does not integrate the judicial exception into a practical application and therefore is directed to an abstract idea. The computing device comprising one or more processors in communication with one or more memories recited in claim 8 and non-transitory computer-readable medium storing instructions executed by one or more processors of a computing device in claim 15 also amount to no more than mere instructions to apply the exception using a generic computer component; see MPEP 2106.05(f). Thus, the additional elements recited in claims 8 and 15 do not integrate the abstract idea into practical application for similar reasons as claim 1.
Step 2B: The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception.
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. The additional elements in the claims other than the abstract idea per se, the computing device via a network connection comprising one or more processors in communication with one or more memories and non-transitory computer-readable medium storing instructions executed by one or more processors of a computing device amount to no more than a recitation of generic computer elements utilized to perform generic computer functions, such as receiving or transmitting data over a network, e.g., using the Internet to gather data, Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362 (utilizing an intermediary computer to forward information); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network); electronic recordkeeping, Ultramercial, 772 F.3d at 716, 112 USPQ2d at 1755 (updating an activity log) and storing and retrieving information in memory, Versata Dev. Group, Inc. v. SAP Am., Inc., 793 F.3d 1306, 1334, 115 USPQ2d 1681, 1701 (Fed. Cir. 2015); OIP Techs., 788 F.3d at 1363, 115 USPQ2d at 1092-93; see MPEP 2106.05(d)(II). Viewed as a whole, these additional claim elements do not provide meaningful limitations to transform the abstract idea into a patent eligible application of the abstract idea such that the claims amount to significantly more than the abstract idea itself. Therefore, since there are no limitations in the claim that transform the abstract idea into a patent eligible application such that the claim amounts to significantly more than the abstract idea itself, the claims are rejected under 35 U.S.C. § 101 as being directed to non-statutory subject matter.
§ 101 Analysis of the dependent claims.
Regarding the dependent claims, claims 4, 6, 7, 11, 13, 14, 19 and 20 recite additional element limitations that amount to no more than generic computer components used as tools to apply the instructions of the abstract idea; MPEP 2106.05(f). Additionally, claims 2, 5, 7, 9, 12, 14, 16, 18 and 20 recite steps that further narrow the abstract idea. No additional elements are disclosed in the dependent claims that were not considered in the independent claims. Therefore claims 2, 4-7, 9, 11-14, 16, and 18-20 do not provide meaningful limitations to transform the abstract idea into a patent eligible application of the abstract idea such that the claims amount to significantly more than the abstract idea itself.
Distinguishable over the Prior Art of Record
The prior art rejections of the amended claims are removed in light of Applicant’s Amendments and Remarks filed June 25, 2026, in particular pg. 18-21 regarding the Tavakol and Loeffen references. Examiner analyzed amended claim 1 in view of the prior art on record and finds not all claim limitations are explicitly taught nor would one of ordinary skill in the art find it obvious to combine references with a reasonable expectation of success.
McLaren et al. (US 20100305972 A1) teaches managing medical case and chronology information for one or more medical practices (see par. 0002). Specifically, McLaren discloses medical professionals may use mobile devices to access and display the information regarding assigned case roles and may further use the mobile devices to coordinate assumption and handoff of roles (see Abstract). The system hierarchy shows a first display mode having a user login interface that first requires a device authentication. In operation, device authentication may be performed by comparing a practice or user key code (or any other suitable identifier) to values stored in a medical information management system. Once the device itself is authenticated, the graphical user interface may provide an interface for indicating a medical practice and selecting an authorized user corresponding to the medical practice. Once a user is selected, the device may receive a password and PIN from the user. Once the user is properly authenticated with the medical information management system, the graphical user interface may display a list of one or more supported locations for a medical practice (see par. 0103). A medical professional may use features provided in a graphical user interface on mobile device to handoff or take over a medical role. In an anesthesia setting, this may involve a first CRNA who is actively providing care for a patient handing-off this management role to a second CRNA when the first CRNA requires a break. Another example may include an anesthesiologist who is supervising multiple CRNAs handing-off his supervisory role to another anesthesiologist when he can no longer act in that capacity. In particular implementations, the role-handoff process may require that the relieving party initiate the role-handoff process to take-over a case role from another medical professional. Moreover, this role-handoff process may work within constraints established by institutional policies and procedures for a particular facility or collection of facilities (see par. 0047).
Yadav et al. (US 20210160212 A1) teaches assigning the proper internet protocol (IP) address to a client device following authentication of the client device on a network (see par. 0001). Specifically Yadav discloses a client device may be connected at operation directly to the network controller while in other embodiments, the client device may be connected indirectly to the network controller via the network device. In this second embodiment, communications/messages may be forwarded through the network device to the network controller and subsequently to other portions of the network system. Following connection of the client device to the network system, the client device may be assigned a first role at operation. In one embodiment, the first role assigned at operation may indicate that the client device has not been authenticated on the network system and accordingly the client device is not authorized to be connected with or join secure portions of the network system. For example, the first role may restrict the client device to associate with a VLAN X that is utilized during machine authentication procedures for devices that are newly joining the network system (see par. 0036-0037). Since the client device is currently assigned the first role and associated with the VLAN X, the client device may be issued an IP address at operation corresponding to the VLAN X. As described above, this assignment may be based on the binding of the network interface/port of client device to the VLAN X in a VLAN table. In one embodiment, one of the DHCP servers may assign the IP address to the client device at operation. (see par. 0044). The client device 103 may use a ping utility to test the IP address assigned to the client device 103 to ensure that no other device is using the assigned address (see par. 0046).
However, McLaren and Yadav, individually or in combination with the prior art of record, does not explicitly teach the combination of claim limitations as recited in claim 1. Thus, claim 1 is found to be distinguishable over the prior art. Claims 8 and 15 are distinguishable for similar reasons as claim 1 and claims 2, 4-7, 9, 11-14, 16, and 18-20 are distinguishable over the prior art because they depend on claims 1, 8 and 15 respectfully.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Rice (US 20220108790 A1) - A system and method for coordinating physician matching for a user. The system including an interface configured to receive preference data related to the user. The system further includes a physician recommendation module being applied to the preference data and corresponding physician data. The physician recommendation module can track the preference data received by the interface, compare the preference data to the corresponding physician data, and recommend a list of physicians to the user when the physician data is above a threshold value. A display coupled to the recommendation module and configured to display the list of physicians to the user.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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 Crystol Stewart whose telephone number is (571)272-1691. The examiner can normally be reached 9:00am-5:00pm.
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, Patty Munson can be reached at (571)270-5396. 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.
/CRYSTOL STEWART/Primary Examiner, Art Unit 3624