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 .
Request for Continued Examination
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 06/25/2026 has been entered.
Applicant Argument Response:
Examiner consider all applicant arguments regarding 35 U.S.C 101 Subject Matter Eligibility in the remark 06/25/2026, pages 9 to 15 and were not persuasive for the reasons below:
Applicant argues that claims 1, 13, and 16 do not recite a certain method of organizing human activity because the claimed communications occur between computer components rather than people.
Examiner respectfully disagrees that automated communications remove the claimed exception. Under BRI, claim 1 organizes the patient-specific decision transaction: identifying the patient data and algorithm, presenting the input values, receiving an instruction to execute the algorithm, applying the identified algorithm, and returning its result. The specification confirms that the clinician ... can then approve the application of the algorithm, or submit any change or update requests. Specification paragraph [0061]. That clinician-directed approval and execution content is managing interactions by following rules or instructions under MPEP 2106.04(a)(2)(II). The host device, database, algorithm service, secure channels, GUI, storage, and transmissions carry that content as additional elements; they do not remove it. The rejection is maintained.
Applicant argues that the first GUI-returning transmission and the later execution transmission integrate the alleged exception into a practical application by securely improving medical-algorithm devices and healthcare-provider networks.
Examiner respectfully disagrees. Under MPEP §§ 2111 and 2106.04(d)(1), the asserted improvement must be reflected in the claim itself, not supplied from a narrower specification embodiment. Under BRI, claim 1 requires two secure channels, transmission of healthcare data and an algorithm identifier, GUI instructions, user-responsive execution, and return of a result; however, it does not require the disclosed local-host-only algorithm architecture, absence of algorithm-device security, equivalent local-host security, data validation, or any particular authentication, encryption, key-exchange, TLS, or GUI implementation. Those features appear in the specification, but are not limitations of claim 1. Accordingly, the claimed channels and two transmissions recite the desired secure communication and execution results, but not the technical mechanism that produces the asserted improvement. The GUI-returning transmission and later execution transmission organize when data is displayed, confirmed, and processed; they do not change how the network, security protocol, GUI, database, or algorithm service technically operates. The required nexus between the claim language and the disclosed technological improvement is therefore absent, and claim 1 does not satisfy Step 2A, Prong Two.
Applicant argues that the ordered combination provides the nonconventional and non-generic arrangement required by BASCOM and therefore amounts to significantly more.
Examiner respectfully disagrees that the ordered combination adds an inventive concept. Claim 1 uses the host, database, service, network, storage, and GUI to receive, transmit, store, apply, and return information. The specification identifies the host and service as computer, smartphone, tablet, computer, server, or cloud computing environment. Specification paragraph [0010]. It identifies TLS and an X.509 certificate commonly being implemented. Specification paragraphs [0071]-[0072]. Those are ordinary computing, network transmission, storage, and security functions. The two transmissions sequence clinician approval before execution, but do not place a technical component in a nonconventional location or change its ordinary operation as in BASCOM. The rejection of claims 1-2, 4-11, 13, and 15-22 is maintained.
Applicant’s arguments filed June 25, 2026, at pages 16–21 of the Remarks, regarding the final obviousness rejection under 35 U.S.C. § 103 of independent claims 1, 13, and 16 and their dependent claims, have been fully considered and are found persuasive. Accordingly, the rejection is withdrawn for the reasons set forth below.
Independent claims 1, 13, and 16 each require, in method, system, or host-device form, the host device to transmit to the database both "an identification of a patient and one or more data field identifiers" and then receive patient-specific healthcare data "associated with each" transmitted field identifier. The cited art does not teach this request-and-corresponding-return relationship.
Reference A - Ott (US 2005/0108055 A1) - Ott enters a patient identification number, uploads patient data and patient information to the central server/database, and later returns a medical report (paragraphs 32, 39, 52, and 56-57). Ott does not send selected data-field identifiers to the database or receive the patient values corresponding to each identifier.
Reference B - Warrier (US 2019/0005115 A1) - Warrier's analysis-server input module accesses the database and receives an ID-field identifier and data-field identifiers (paragraphs 117-129). The ID-field identifier selects a schema or primary-key column; although that column may contain patient IDs (paragraph 239), Warrier does not show the host sending a particular patient ID to the database or receiving the corresponding values.
Reference C - Yuan (US 2019/0303219 A1) - Yuan teaches parameterized interface data and a later operation request (paragraphs 102-109 and 132-140), but no patient-specific database request or corresponding return.
Accordingly, Ott, Warrier, and Yuan do not provide sufficient support to render independent claims 1, 13, and 16 obvious. The prior-art rejection of those claims, and of their dependent claims on this ground, is withdrawn.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(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.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
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 of carrying out his invention.
Claim(s) 1-2, 4-11, 13, 15, and 16-22 rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) 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, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claims 1, 13, and 16 recite an identification of an algorithm to be applied by the host device. Under BRI, this requires the host device to apply the identified algorithm. Even the closest disclosure describes the host device identifying or requesting the algorithm and the algorithm service applying it to the healthcare data see para. 0010,0012, 0015, 0061, 0063, 0076. The original disclosure therefore does not reasonably convey possession of applying the identified algorithm by the host device. Claims 2, 4-11, 15, and 17-22 depend from rejected independent claims and are rejected on the same ground.
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claim 1, 2, 4-11, 13, 15, and 16-22 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 1 and 16 recites an identification of an algorithm to be applied by the host device, but later recites applying, by the algorithm service … the identified algorithm to arrive at the result. Under MPEP 2173.02, after applying the broadest reasonable interpretation consistent with the specification, the claim is indefinite when a person of ordinary skill would read the claim with more than one reasonable interpretation or cannot determine the metes and bounds. Because the same identified algorithm is assigned to both the host device and algorithm service, a person of ordinary skill cannot determine whether the applying step must be performed by the host device, the algorithm service, or both. Claims 2 and 4-11 depend from claim 1 and are rejected on the same ground.
Claim 13 recites the host device transmitting an instruction to the algorithm service to execute the algorithm, but then places apply … the identified algorithm and transmit, to the host device within the host-device configuration. Claims 15 depend from claim 13 and is rejected on the same ground.
Claim 16 is directed to a host device whose memory causes host processors to perform the recited operations, but those operations include acts performed at, by, and from the separate algorithm service. The claim therefore does not make clear whether the host device performs, controls, includes, or merely communicates with the algorithm service. Claims 17-22 depend from claim 16 and are rejected on the same ground unless separately amended to cure the ambiguity.
Claim Rejections - 35 U.S.C. § 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-11, 13, and 15-22 are rejected under 35 U.S.C. § 101 because the claims recite judicial exceptions and do not integrate those exceptions into a practical application or add significantly more.
Step 1
Step 1 evaluates whether the claimed subject matter falls within one of the four statutory categories of invention.
Claims 1-2 and 4-11 recite a process because claim 1 is a computer-implemented method comprising establishing, transmitting, receiving, applying, and result-return operational steps.
Claims 13 and 15 recite a machine because claim 13 is a system comprising a host device and an algorithm service.
Claims 16-22 recite a machine because claim 16 is a host device comprising one or more processors, a network interface, and a non-transitory memory.
Step 1 is satisfied under MPEP § 2106.03. The eligibility determination proceeds to Step 2A.
Prong One
Under Step 2A, Prong One, claims 1-2, 4-11, 13, and 15-22 recite judicial exceptions falling within certain methods of organizing human activity and mental processes under MPEP § 2106.04(a)(2).
Independent Claims Analysis
Claim 1 represents independent claims 13 and 16 because all three cover the same fundamental workflow: identifying the patient and the fields, retrieving the patient's data, identifying the algorithm, providing instructions for execution, applying the algorithm, and returning the result.
In claim 1 below, non-bold text represents the judicial exception and bold text represents the additional elements:
[1] A computer-implemented method of transferring healthcare data between a host device and an algorithm service, the host device residing within a first computer-network and the algorithm service residing within a second computer-network different to the first computer-network, the method including:
[2] establishing, between the host device and a database, a first secure channel of communication;
[3] transmitting, from the host device to the database through the first secure channel, an identification of a patient and one or more data field identifiers;
[4] receiving, from the database and via the first secure channel, patient-specific healthcare data associated with each of the one or more data field identifiers;
[5] establishing, between the host device and the algorithm service, a second secure channel of communication;
[6] transmitting, as a first transmission from the host device to the algorithm service via the second secure channel of communication: an identification of an algorithm to be applied by the host device, and the patient-specific healthcare data; receiving and storing, at the algorithm service, the patient-specific healthcare data; receiving, by the host device and responsive to the first transmission, instructions for rendering a graphical user interface on the host device including algorithm input values;
[7] transmitting, responsive to input received at the host device via the graphical user interface, a second transmission from the host device to the algorithm service including an instruction to execute the algorithm on the patient-specific healthcare data;
[8] applying, by the algorithm service and responsive to the second transmission, the identified algorithm to the patient-specific healthcare data to arrive at a result;
and
[9] transmitting, from the algorithm service to the host device via the second secure channel of communication, the result of applying the identified algorithm to the patient-specific healthcare data.
Under the broadest reasonable interpretation (BRI), the non-bold limitations numbered [1] to [9] involve identifying patient information and a decision rule, applying that rule to the patient information, carrying out the application of the rule, and then obtaining the patient-specific information that results.
Independent claims 1, 13, and 16 recite managing personal behavior or person-computer interaction through following rules or instructions as stated in MPEP § 2106.04(a)(2)(II). The limitations specified in [3], [4], and [6] to [9] include content that identifies a patient and relevant data fields, the corresponding patient-specific information, an algorithm, an instruction to carry out that algorithm, the application of the algorithm, and the resulting information. Under the (BRI), the instruction for execution in response to a graphical user interface (GUI) involves a user deciding whether to apply the selected medical rule to the selected patient information. This sequence of user-controlled decisions falls within the scope of following rules or instructions, even though the computer components communicate and carry out the decision. As noted in MPEP § 2106.04(a)(2)(II), this sub-grouping includes both interpersonal and person-computer interactions. See paragraph 0011
The non-bold language additionally recites a mental process under MPEP § 2106.04(a)(2)(III). Limitations [3], [4], and [6] to [9] require identifying a patient and relevant data fields, recognizing patient-specific data associated with those fields, identifying an algorithm, issuing an instruction to apply that rule, applying the rule, and obtaining the patient-specific result. Under BRI, the claims do not limit the algorithm to an operation so complex that a human could not practically perform it. Paragraph [0011] defines an algorithm broadly as a finite sequence of unambiguous instructions. A clinician can mirror this evaluation mentally or with pen and paper by selecting patient records, choosing a calculation rule, evaluating input values on an intake form, authorizing the calculation, computing the result, and recording the conclusion.
Dependent Claims Analysis
Dependent claims 2, 4-11, 15, and 17-22 recite the same judicial exceptions under MPEP § 2106.04(a)(2).
Claims 5-7, 17, 19, and 20-22 recite confirmation, correction, and execution-control content (identifying which algorithm is applied to what data, presenting pre-populated inputs, receiving change requests, separating transmission timing, and modifying values), which fall within mental processes and managing human interactions through rules.
Claims 2 and 18 recite selecting display instructions based on the algorithm and providing supported-algorithm catalog lists, which recite selection and catalog content for the same administrative transaction.
Claim 8 recites transforming data before or after calculation at a broad functional level, which falls within mental data manipulation.
Claims 4, 9-11, and 15 recite authentication, encryption, and interface labels, adding no separate judicial exception and inheriting claim 1.
Because all pending claims recite judicial exceptions, the determination proceeds to Prong Two of Step 2A.
Prong Two
Under Step 2A, Prong Two, the additional elements of claims 1-2, 4-11, 13, and 15-22 do not integrate the judicial exception into a practical application under MPEP § 2106.04(d) because they do not improve computer or network functioning and do not impose meaningful technical limitations on the abstract concept.
Independent Claims Analysis
The additional elements in representative independent claim 1 (and mirror claims 13 and 16) are: a computer-implemented method, a host device, an algorithm service, a first computer-network, a second computer-network, a database, a first secure channel of communication, a second secure channel of communication, storing at the algorithm service, a graphical user interface on the host device, one or more processors, a network interface, and a non-transitory memory.
Individual Additional Elements Evaluation
Under MPEP § 2106.04(d)(1) and § 2106.05(a), the additional elements do not demonstrate an improvement in the functioning of a computer or other technology. Because there is an insufficient nexus between the claimed limitations and the alleged improvements. The core improvement is making data handling across networks secure when integrating local-host algorithms into a cloud environment. However, the claim language fails to reflect that improvement because it lacks the specific technical details of how that security is accomplished (Intellectual Ventures I LLC v. Symantec Corp., 838 F.3d 1307, 1316).
Under BRI, a first secure channel of communication and a second secure channel of communication require confidentiality and authenticity consistent with specification paragraph [0068]. However, claim 1 does not recite how those security properties are technologically achieved or how the claimed channels modify or improve network-security operation. The disclosed TLS handshake, certificates, key exchange, and cryptographic mechanisms are embodiments described in paragraphs [0071]-[0072], not limitations of claim 1. Thus, the claim invokes secure network communication to implement the underlying workflow but does not itself reflect the asserted technological improvement under MPEP §§ 2106.04(d)(1), 2106.05(a), and 2106.05(f).
Furthermore, assigning operations between a host device in a first computer-network and an algorithm service in a second computer-network merely recites the concept of distributed computing, which uses remote computers merely as tools to carry out data processing under MPEP § 2106.05(f). Paragraph [0010] states that the host device may be a computer, smartphone, or tablet, and the algorithm service may be a computer, server, or cloud environment; paragraph [0082] identifies standard computer systems with CPU, input, output, and data storage. Rendering a graphical user interface on the host device merely invokes a generic interface to display data and receive user input under MPEP § 2106.05(h). Paragraph [0015] describes GUI instructions as an HTML document for browser rendering, paragraph [0059] describes a request to pre-populate a GUI, and paragraph [0063] describes returning results for display. These elements do not improve GUI, database, network routing, or host operation MPEP § 2106.05(a).
Combination Additional Elements Evaluation
Claim 1 recites only a functional sequence for retrieving patient data, transmitting an algorithm identification, presenting GUI input values, separately requesting execution, and returning the result. It does not recite the disclosed protective architecture, containerization, access controls, audit functions, or a specific security mechanism. As an ordered combination, the additional elements implement the abstract decision-support transaction across two networks without improving computer, network, GUI, or security technology, using a machine integral to the exception, transforming an article, or applying a particular medical treatment. Prong Two is not satisfied.
Dependent Claims Analysis
Dependent claims 2, 4-11, 15, and 17-22 do not integrate the judicial exception into a practical application:
Claims 2, 5-7, 17, and 20-21 recite GUI instructions, pre-populated graphical user interfaces, and input fields for receiving change requests. These limitations do not improve how a computer or graphical user interface operates; rather, they use the GUI to present information, receive user input, and communicate that input within the claimed healthcare-data workflow. The claims do not recite a particular rendering technique, interface architecture, data-processing mechanism, or other technological implementation that changes or improves computer functionality. Accordingly, the GUI limitations merely apply the judicial exception using generic computer-interface functionality and do not integrate the exception into a practical application under MPEP §§ 2106.04(d) and 2106.05(a).
Claims 4, 10-11, 15: Recite authenticating an identity and encrypting messages, which recite generic functional results without any improved authentication protocol, encryption technique, or key-exchange mechanism under MPEP § 2106.05(a) and (g).
Claims 9, 19: Recite an API, an edge module, and transmitting an execution request in a separate transmission, which are software labels and transmission sequences that do not alter network functionality under MPEP § 2106.05(a).
Claims 8, 18, 22: Recite transforming data, a list of algorithms, and modifying patient-specific values, which recite data formatting and database storage tools under MPEP § 2106.05(f).
Because the additional elements do not integrate the judicial exception into a practical application under Step 2A, the claims are directed to an abstract idea and require evaluation under Step 2B.
Step 2B
Under Step 2B, claims 1-2, 4-11, 13, and 15-22 do not recite an inventive concept amounting to significantly more than the judicial exception under MPEP § 2106.05.
The additional elements evaluated under Step 2B are identical to those evaluated under Step 2A: a host device, an algorithm service, a first computer-network, a second computer-network, a database, first and second secure channels of communication, storing at the algorithm service, a graphical user interface, one or more processors, a network interface, and a non-transitory memory.
Independent Claims Analysis
Individual Additional Elements Evaluation
Considered individually, each additional element fails to provide an inventive concept under MPEP § 2106.05(d). The recitation of processors, memory, network interface, host device, database, and algorithm service represents generic computer hardware performing routine data transfer, storage, and processing. As the Supreme Court held in Alice Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. 208, 225, "the mere recitation of a generic computer cannot transform a patent-ineligible abstract idea into a patent-eligible invention." Under MPEP § 2106.05(d)(II), Electric Power Group, LLC v. Alstom S.A., 830 F.3d 1350, 1355, the court held that using off-the-shelf computer, network, and display technology for gathering, sending, and presenting information lacks an inventive concept. See buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, a computer receiving and sending information over a network with no further specification is not inventive.
The recitation of first and second secure channels of communication recites no protocol modification. Paragraph [0071] identifies TLS version 1.3 or 1.2, and paragraph [0072] states that server authentication is commonly implemented using an X.509 server certificate. RFC 8446 identifies TLS 1.3 as an established Internet Standards Track protocol allowing client/server applications to communicate over the Internet. TLI Communications LLC v. AV Auto. LLC, 823 F.3d 607, 612, explain that elements performing basic functions such as sending and receiving data over channels do not add significantly more. The claimed secure channels use known confidentiality tools and do not modify TLS, certificates, encryption, or key exchange.
The graphical user interface, service-side storage, and transmission elements do not add significantly more. Paragraph [0015] describes GUI instructions as an HTML document for browser rendering, paragraph [0060] describes message 6 as an HTML document denoting values and algorithm, paragraph [0062] states that the algorithm service may store initially transmitted values, and paragraph [0063] returns results as GUI instructions to display UI(res). Trading Techs. v. IBG LLC, 921 F.3d 1084, 1093, and Electric Power Group, 830 F.3d at 1355, confirm that displaying inputs and receiving user execution commands through generic interfaces is well-understood, routine, and conventional computer activity.
Combination Additional Elements Evaluation
Considered as an ordered combination, the additional elements do not add an inventive concept. The elements do no more than what they are generally used to do: computer components transmit, receive, store, process, and return data; secure channels provide standard confidentiality; and the GUI presents values, receives input, and displays results. The independent claims do not change how the computer, network, secure channel, browser, database, or algorithm service operates, nor do they place those components in an unconventional technical arrangement. Assigning separate tasks across a network to different computing components constitutes routine distributed computing (TLI Communications, 823 F.3d at 612). Thus, the ordered combination merely uses generic computer, network, security, storage, and interface functions to execute the abstract decision-support sequence, and does not amount to significantly more.
Dependent Claims Analysis
Dependent claims 2, 4-11, 15, and 17-22 fail to recite an inventive concept because:
Dependent claims 2, 4-11, 15, and 17-22 likewise do not supply an inventive concept. Under Step 2B, the conclusions reached under MPEP §§ 2106.05(a), (f), and (h) in Prong Two are carried forward, and the claims are evaluated separately under their BRI to determine whether their added limitations provide a particular technological solution rather than merely invoking technology to perform the judicial exception.
Claims 2, 5-7, 17, and 19-21 add GUI instructions, confirmatory or pre-populated interfaces, input/change requests, and separate execution requests. Under BRI, these limitations specify presentation, receipt of input, and transmission of instructions within the claimed data-processing workflow; they do not recite an improved rendering mechanism, interface architecture, communication protocol, or computer operation. Thus, they merely use computer-interface and messaging technology to carry out the exception and do not provide the technological improvement or particular technical solution contemplated by MPEP §§ 2106.05(a) and (f).
Claims 4, 10-11, and 15 add authenticating an identity and/or encrypting messages. These limitations require the desired security functions, but do not recite a particular authentication protocol, encryption technique, key-management mechanism, or modification to network-security operation by which improved security is achieved. Accordingly, they invoke security technology to perform the claimed communications rather than claim a technological improvement or inventive technical implementation under MPEP §§ 2106.05(a) and (f).
Claims 8, 9, 18, and 22 respectively add transforming data, an API and edge module, a list of algorithms, and storing or modifying patient-specific values. Under BRI, these limitations identify data-processing operations or software components used to implement the underlying workflow, but do not prescribe a particular transformation technique, API/edge architecture, service-selection mechanism, or storage operation that improves the functioning of the computer, network, database, or other technology. They therefore do not add an inventive concept under MPEP §§ 2106.05(a) and (f).
Viewed individually and as ordered combinations with their respective parent claims, the dependent limitations further implement or specify the technological environment for the judicial exception without claiming a particular technological solution that changes how the underlying computer, network, GUI, database, or security technology functions. Accordingly, claims 2, 4-11, 15, and 17-22 do not amount to significantly more than the judicial exception under Step 2B.
Accordingly, claims 1-2, 4-11, 13, and 15-22 are rejected under 35 U.S.C. § 101 as failing to claim patent-eligible subject matter.
Conclusion
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, Shahid Merchant can be reached at (571) 270-1360. 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.
/J.D.R./Examiner, Art Unit 3684
/Shahid Merchant/Supervisory Patent Examiner, Art Unit 3684