DETAILED ACTION
This is responsive to remarks filed on 07/13/2026 in which claims 1-4 are presented for examination; claims 1 and 4 are amended.
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 .
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are:
a filtration module(101)... claims 1, 2: para 0012 “The filtration module (101) filters the one-dimensional ECG datasets to eliminate the presence of noise and artifacts using a plurality of filtration techniques such as and not limited to
Discrete Wavelet Transformation (DWT) techniques.”
a feature extraction module(102)... claim 1: “[0013] Further, the filtered one-dimensional ECG data is provided to a feature extraction module (102) for extracting a set of pre-defined features from the filtered one-dimensional ECG data using techniques such as fiducial points, adaptive thresholding, lifting based schemes and so on, wherein the extracted features include various combinations of the PQRST complex such as RR, SS, QRS complex, QT, ST segment values present in the one-dimensional ECG data. Multiple combinations of the PQRST complex is extracted based on the disease to be identified. The extracted features from the one-dimensional ECG data is provided to a classification module (103) for the purpose of classifying the
extracted features.
a classification module (103)... in claim 1: [0014] The classification module (103) employs interval and peak detection classification techniques for the purpose of data classification, and claim further clarifies how the similarity is used to perform the classification..
a conversion module (104)... in claims 1, 4: para 0014, “The classified data from the classification module (103) is provided to a conversion module (104) for converting classified features from one-dimensional ECG signal present in serial format into a matrix format representing a two-dimensional spectrogram image,”
a remote server module (105)... in claim 1: para 0014 states that “the two-dimensional spectrogram image is uploaded to a remote server module (105) using a wired or wireless network infrastructure”; an embodiment with wired infrastructure will provide support that server module is well known hardware module.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 112
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.
Claims 1-4 are 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 limitations “a classification module (103), a conversion module (104), and a remote server module (105) ” invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. Regarding a classification module (103)... in claim 1; para 0014 states “the classification module (103) employs interval and peak detection classification techniques for the purpose of data classification.” However, it does not explicitly state which techniques are being applied. Regarding, a conversion module (104); para 0014 states, “the classified data from the classification module (103) is provided to a conversion module (104) for converting classified features from one-dimensional ECG signal present in serial format into a matrix format representing a two-dimensional spectrogram image”, however it does not explicitly disclose what, or how this conversion is performed. Regarding, a remote server module (105); para 0014 states that “the two-dimensional spectrogram image is uploaded to a remote server module (105) using a wired or wireless network infrastructure.” Here, the limitation claims server module, not the server itself, and specification does not disclose what this server modules is, though para 0014 states that this module can use communication via wired or wireless network infrastructure.
Therefore, the claim is indefinite and is rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
Applicant may:
(a) Amend the claim so that the claim limitation will no longer be interpreted as a limitation under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph;
(b) Amend the written description of the specification such that it expressly recites what structure, material, or acts perform the entire claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(c) Amend the written description of the specification such that it clearly links the structure, material, or acts disclosed therein to the function recited in the claim, without introducing any new matter (35 U.S.C. 132(a)).
If applicant is of the opinion that the written description of the specification already implicitly or inherently discloses the corresponding structure, material, or acts and clearly links them to the function so that one of ordinary skill in the art would recognize what structure, material, or acts perform the claimed function, applicant should clarify the record by either:
(a) Amending the written description of the specification such that it expressly recites the corresponding structure, material, or acts for performing the claimed function and clearly links or associates the structure, material, or acts to the claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(b) Stating on the record what the corresponding structure, material, or acts, which are implicitly or inherently set forth in the written description of the specification, perform the claimed function. For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181.
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.
Claims 1-4 are 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. As described above, the disclosure does not provide adequate structure to perform the claimed function of classification, conversion, and server modules. The specification does not demonstrate that applicant has made an invention that achieves the claimed function because the invention is not described with sufficient detail such that one of ordinary skill in the art can reasonably conclude that the inventor had possession of the claimed invention.
Claims 1-4 are 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.
Regarding claim 1, claim 1 states “determines a Euclidean Distance between the extracted features and one or more test data.” It is not clear what does it mean by “determining a Euclidean Distance between the extracted features and one or more test data”? Thew main issue over here is, What is the “test data”? Note, here the extracted features are a set of pre-defined features from EC data, these features can include one or more combination of PQRST complex. The Euclidean distance between these features and test data is being determined; unless, one knows, what is this “test data”, it is impossible to determine the “Euclidean distance”. Under BRI, the test data can be any data, such as patient ECG data, how does one determines Euclidean distance between ECG data, and data that was extracted as point son wave (P, Q, R, S, T). In addition, if the match, and unmatch can detect the presence/absence of disease, who does the test data belong to (patient, or general population, etc...). The distance being determined is not apple to apple, extracted data, and test data, can be two completely different entities.
In addition, with regard to step e in claim 1, it recites “...and for enabling a display of the detected cardiac disease on one or more user interface devices...” Step C, determines absence/presence of disease using Euclidean distance; and in step d, conversion module is used to classify the image among disease (basically identifying the disease). Now, in step e, what is “the detected cardiac disease” that is being displayed.
Also, it is not clear what step c, and step d have anything to do with each other; in fact it seems, in step c, we are detecting presence/absence of the disease using Euclidean distance, and then in step D, all the sudden, we are using different technique that completely ignores the finding/technique of step c, and uses the conversation and hybrid model to identify the disease. What is the link between these steps, or we claiming multiple detection techniques within the same claim? Simply, put, the claim seems, like a piecemeal group of limitations, that is going into multiple directions, leaving the scope of claimed invention indefinite.
Claims 2-4 are rejected based on rejected claim 1.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-4 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Regarding claim 1:
Step 1: Is the claim to a process, machine, manufacture or composition of matter?” Yes, it’s a machine(system).
Step 2a Prong 1 (judicial exception)
Step 2A (1): “Does the claim recite an abstract idea, law of nature, or natural phenomenon? Yes , the claim comes under mental processes.
Claim 1 recites:
“A system for detection and classification of cardiac diseases using deep neural network techniques, the system (100) comprising:
a. a filtration module (101) for filtering one or more datasets pertaining to one-dimensional Electrocardiogram (ECG) data obtained from a plurality of individuals, wherein the filtration module (101) filters the one-dimensional ECG datasets to eliminate the presence of noise and artifacts;
b. a feature extraction module (102) for extracting a set of pre-defined features from the filtered one-dimensional ECG data, wherein the extracted features include one or more combinations of a P, Q, R, S, and T (PQRST) complex present in the one-dimensional ECG data, the one or more combinations comprising at least one of an RR, an SS, a QRS complex, a QT, and an ST segment value;
c. a classification module (103) for determining, using interval and peak detection techniques, a presence or an absence of a cardiac disease based on the extracted features, wherein the classification module (103):
i. determines a Euclidean Distance between the extracted features and one or more test data. wherein:
1. the Euclidean Distance indicating a match between the extracted features and the one or more test data corresponds to the absence of the cardiac disease; and;
2. the Euclidean Distance indicating a mismatch between the extracted features and the one or more test data corresponds to the presence of the cardiac disease;
d. a conversion module (104) for converting the extracted features classified by the classification module (103) from the one-dimensional ECG signal into a two-dimensional spectrogram image for neural network-based classification, wherein the conversion module (104) deploys the two-dimensional spectrogram image into a custom deep neural network comprising a hybrid model of a Convolutional Neural Network (CNN) and a Recurrent Neural Network (RNN) to classify the two-dimensional spectrogram image among a plurality of cardiac diseases;
e. a remote server module (105) for receiving the two-dimensional spectrogram image from the conversion module (104) via a wired or wireless network infrastructure, and for enabling a display of the detected cardiac disease on one or more user interface devices, wherein the one or more user interface devices comprise at least one of a mobile phone, a tablet, and a standalone display device.”
All of the above mentioned limitations with the exception of bold and underlined limitations can be performed mentally or on paper. For example, a user could visually review a plot of ECG signals, filter/remove noisy parts of the signals (e.g., crossing them out or otherwise not considering such portions), extract/identify certain portions of the PSRST complex as interesting features, generate Euclidean distances, and analyze the distances to determine with disease is detected or not (classifying).
Step 2A(2): Prong Two: evaluate whether the claim recites additional elements that integrate the exception into a practical application of the exception. NO
The claim does recite additional elements (all underlined elements); however they don’t integrate the exception into a practical application of the exception, as they are merely presented at apply it level.
The various “modules” are just using computers as tools to carry out the abstract idea (2106.05(f)(2)) while converting the classified 1D ECG features into a 2D spectrogram image for input to the NN is just reciting the “idea of a solution” (2106.05(f)(1)). Similarly a remote server module is being applied in network environment to communicate data. The neural network, and hybrid models are also at apply it level.
Step 2B: evaluate whether the claim recites additional elements that amount to an inventive concept (aka “significantly more”) than the recited judicial exception? NO
As discussed previously with respect to Step 2A Prong Two, the additional element in the claim amounts to no more than mere instructions to apply the exception using a generic computer component.
The same analysis applies here in 2B, i.e., mere instructions to apply an exception using a generic computer component cannot integrate a judicial exception into a practical application at Step 2A or provide an inventive concept in Step 2B.
Claim 2 is a mathematical concept, claim 3 is mentally performable, and claim 4 appears to be just reciting list of different diseases.
Response to Arguments
Applicant's arguments filed on 07/13/2026 have been fully considered but they are not persuasive.
Regarding claim objection, the claim objection has been withdrawn in light of the amendments.
Regarding drawing objections, the drawing objections have been withdrawn in light of the amendments.
Regarding 35 U.S.C 112(a), and 35 U.S.C 112(b) due to 35 USC 112(f) invocation, the rejection with regard to classification module is withdrawn, as it seems, the classification of presence/absence is using the Euclidean distance; however, the 35 U.S.C 112(b) rejection still remains, as it is not clear how distance between extracted features and test data is determined; mainly, it is not clear what is test data. The applicant further contends on pg. 8 , “accordingly, a person of ordinary skill in the art would readily understand the conversion module to correspond to a signal-processing routine that converts classified one-dimensional ECG information into a two-dimensional spectrogram representation and provides the resulting spectrogram to the disclosed hybrid neural-network framework for disease classification.”
The issue here is applicant invoking 35 U.S.C 112(f), based on the invocation the examiner needs to interpret the conversion module in light of the specification, and the broadest reasonable interpretation is limited to the specification. The issue is written description here, not the enablement. The specification is devoid of any structure for the conversion module; assuming, the conversion module is executed on the general processor, then the support would be general processor, plus the algorithm. The claims, or the specification, is completely devoid of any algorithm that outlays step by step, how the function is being performed. In instant case, arguing that conversion is a signal-processing routine, is not sufficient, as the claims or the specification don’t describe such routine. Also, , the claim is mentioning various modules, which under broadest reasonable interpretation could all be software per se, and the claim would be rejected under 35 U.S.C. 101; however, since the applicant have invoked claim interpretation under 35 U.S.C 112(f), now examiner have to treat these modules to be more than software, and determine, the structure based on the instant specification. The instant specification is devoid of any structure for these modules; and if the support is generic computer/processor, then for computer related function, we need to have algorithm that performs the claimed functions, and the specification/claims are devoid of such function.
Applicant contends on pg. 8 : “Remote Server Module (105): The Specification further discloses that the remote server module communicates with the conversion module through a wired or wireless network infrastructure and enables the detected cardiac disease to be displayed on one or more user interface devices. Paragraph [0014] identifies suitable user interface devices including a mobile phone, tablet, and standalone display device.”
The display devices are external to system claim, which are being used to display. The above remarks, have nothing to do with 35 U.S.C 112(f) analysis, neither it lends any structure to remote server module.
Applicant contends on pg. 9 : “A person of ordinary skill in the art would therefore readily understand the corresponding structure for the remote server module to include a conventional network-connected server configured to communicate diagnostic information between the conversion module and one or more remote user interface devices.”
The applicant is providing a conclusory statement without any detail; in addition, the support for the module can’t be merely “conventional server.” If the conventional server was supported by the specification, then specification will need to further provide algorithm to ensure that it is special purpose server. Also, the claim rejections as discussed above with regard to 35 U.S.C 112(a), and 35 U.S.C 112(b) are due to claim interpretation under 35 U.S.C 112(f). The applicant’s remark seems to analyze the rejection, as simple 35 U.S.C 112(a), and 112(b) rejections, the applicant is advised to analyze the rejections in light of claim interpretation that limits the broadest reasonable interpretation to the specification. The same analysis applies with respect remarks under 35 U.S.C 112(a), as 35 U.S.C 112(a) is always applied when the 35 U.S.C 112(b) is applied due to specification being devoid of the structure.
Applicant contends on pg. 11 , “First, Claim 1(c)(i) has been amended to recite that the classification module "determines a Euclidean Distance between the extracted features and one or more test data," replacing the prior "compares to match phrasing that the Examiner found unclear. Read in light of Claim 1(a), which recites that the underlying one-dimensional ECG data is "obtained from a plurality of individuals," the "extracted features" referenced in element (c) are reasonably understood to characterize aggregate or representative feature values derived from this plurality of individuals i.e., a reference data set while the "one or more test data" against which those extracted features are compared corresponds to feature values associated with a single ECG signal under evaluation. As further recited in Claim 1(b), the extracted features comprise diagnostic ECG features derived from the filtered one-dimensional ECG data, including features derived from the P, O, R, S, and T (PORST) complex, such as an RR interval, an SS interval, a QRS complex value, a oT interval, and an ST segment value.”
It is not clear what applicant is stating in underlined remarks; it is clear to examiner what is extracted data; but not “test data”; under broadest reasonable interpretation (BRI), test data can be any data. If test data can be any data, and the extracted data is combination of PQRST, then how is Euclidean distance between these two different types of data being determined? The claim rejection under 35 U.S.C 112(b) have been updated in light of the specification; the claim amendments remove few of the previous issues raised, however they introduce the new issues that needs to be resolved.
Regarding 35 USC 101, Applicant's arguments filed 07/13/2016 have been fully considered but they are not persuasive.
Remarks, Pg. 14, applicant contends “these operations cannot be practically performed in the human mind. In particular, a) generation of a two-dimensional spectrogram from physiological signals requires computational signal processing; b) deployment of a spectrogram into a deep neural network requires execution of trained machine-learning models; c) and neural network inference cannot be replicated mentally. These operations are not performed merely to organize or analyze information. Rather, they define a technical workflow for processing physiological ECG signals and transforming the processed signal into a different technical representation that enables neural-network- based cardiac disease classification. The claimed modules therefore cooperate to improve the operation of an automated cardiac diagnostic system by enabling clear classification of multiple cardiac diseases using the disclosed signal-processing and hybrid model of a Convolutional Neural Network (CNN) and a Recurrent Neural Network (RNN).”
The rejection have identified the additional limitations, however these additional limitations are merely at apply it level; the limitation provide not technical improvement into any of the technical fields being recited. In fact, the applicant has admitted that a person of ordinary skill would understand, the structure of the claimed device to perform the claimed functions. (Please see discussion with regard to 35 U.S.C 112(a), and 35 U.S.C 112(b) in the remarks).
Remarks, Pg. 14, applicant contends “furthermore, the current claim amendments clarify the technical interaction between the claimed modules by reciting determination of the Euclidean Distance, determination of the presence or absence of cardiac disease based upon the determined Euclidean Distance, conversion of the classified extracted features into a two-dimensional spectrogram image, deployment of the spectrogram image into a custom hybrid CNN-RNN model, and communication of the detected cardiac disease through the remote server module for display on user interface devices. These amendments further emphasize the practical technological implementation already disclosed in the originally filed Specification and do not introduce new functionality.”
The examiner agrees that these limitations provide the technological implementation; however the issue is that in Step 2B, we analyze inventive concept (significantly more); and since, in step 2A, the examiner relied on “apply it”, the discussion with regard to step 2B is substantially same. The applicant needs to discuss the technical solution being presented, and what technical problem is being solved, or what technical improvements are being made. For example, when discussing extracting, what in extraction technology is being improved,
Allowable Subject Matter
Claims 1-4 are allowed over the prior art. As previously discussed in the office action mailed on 04/14/2026, the applicant’s arguments are persuasive, and prior art rejection was withdrawn. The applicants’ amendments didn’t change the scope of the claimed invention.
Conclusion
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 extension fee 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 date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HUMA WASEEM whose telephone number is (571)272-1316. The examiner can normally be reached Monday-Friday(9:00am - 5:00 pm) EST.
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, Jason B. Dunham can be reached on (571) 272-8109. 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.
/HUMA WASEEM/Examiner, Art Unit 3686
/JASON B DUNHAM/Supervisory Patent Examiner, Art Unit 3686