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 .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 05/23/2025 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Drawings
The drawings were submitted on 05/05/2025. These drawings are reviewed and accepted by the examiner.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Kumar (US 20110257989 A1).
Regarding claims 1, 8, and 15, Kumar teaches:
“obtaining an indication to provide access to a prescription resource at an electronic computing device associated with a user” (par. 0023; ‘The patient 110 may use the prescription management application 102 to manage his or her prescriptions or other prescription-related health care data.’)
“causing one or more user interfaces to be provided at the electronic computing device to perform an action prerequisite to providing access to the prescription resource, the one or more user interfaces using a communication mode selected based on configuration information associated with the electronic computing device, the configuration information indicating compatibility of the electronic computing device to provide output to the user or receive input from the user in accordance with the selected communication mode” (par. 0045, prescription identifier; ‘The prescription entry prompt 246 may be displayed on the graphical user interface 216 of the mobile communication device 204 in response to the patient's selection of a prescription entry prompt activation button 248. The prescription entry prompt 246 includes a prescription identifier field 250.’; par. 0058, application settings for notifications; ‘In one embodiment, the prescription management application 202 may also have application settings that are customizable or changeable by the patient 210. For example, the patient 210 may change the method by which the patient 210 is notified when his or her prescription is ready for retrieval at the pharmacy 212. Non-limiting examples of the type of notification the patient 210 may receive include a graphical notification, such as the prescription availability notification 214, or an audio notification.’); and
“causing the prescription resource to be provided at the electronic computing device upon completion of the prerequisite action via the one or more user interfaces” (par. 0047; ‘For example, the patient 210 may select the prescription status module activation button 252 to cause the prescription management application 202 to display the prescription status, as shown in FIG. 5.’).
Regarding claims 2 (dep. on claim 1), 9 (dep. on claim 8), and 16 (dep. on claim 15), Kumar further teaches:
“wherein the one or more processors include one or more processors of the electronic computing device” (par. 0075; ‘The computing device 702 includes a communications fabric 703, which provides communications between a processor unit 705, a memory 707,, a persistent storage 709, a communications unit 711, an input/output (I/O) unit 713, and a display 715.’).
Regarding claims 3 (dep. on claim 1) and 10 (dep. on claim 8), Kumar further teaches:
“wherein the one or more processors include one or more processors of one or more servers communicatively connected to the electronic computing device” (par. 0033; ‘In addition to the server on which the health care management hub, 106 may be implemented, additional intervening servers may facilitate data communication or storage within the prescription management system 100.’).
Regarding claims 4 (dep. on claim 1), 11 (dep. on claim 8), and 17 (dep. on claim 15), Kumar further teaches:
“wherein the configuration information indicates capability of the electronic computing device to provide output to the user” (par. 0064; ‘Referring to FIG. 15, an illustrative embodiment of a process for initiating a prescription availability notification on the mobile communication device and presenting a set of selectable modules related to the prescription on a graphical user interface, referred to in steps 307 and 309 in FIG. 13, may include displaying the prescription availability notification on the mobile communication device (step 501).’).
Regarding claims 5 (dep. on claim 1), 12 (dep. on claim 8), and 18 (dep. on claim 15), Kumar further teaches:
“wherein the configuration information indicates capability of the electronic computing device to receive input from the user” (par. 0058; ‘In one embodiment, the prescription management application 202 may also have application settings that are customizable or changeable by the patient 210.’).
Regarding claims 6 (dep. on claim 1), 13 (dep. on claim 8), and 19 (dep. on claim 15), Kumar further teaches:
“wherein the configuration information includes hardware configuration information indicative of hardware included within or otherwise operatively connected to the electronic computing device” (par. 0058; ‘Non-limiting examples of the type of notification the patient 210 may receive include a graphical notification, such as the prescription availability notification 214, or an audio notification.’ Settings for audio notification inherently would require hardware configuration information since it is hardware only that can output an audio notification.).
Regarding claims 7 (dep. on claim 1), 14 (dep. on claim 8), and 20 (dep. on claim 15), Kumar further teaches:
“wherein the configuration information includes application configuration information indicative of hardware access permissions associated with one or more software applications executing via the electronic computing device” (par. 0058; ‘In one embodiment, the prescription management application 202 may also have application settings that are customizable or changeable by the patient 210.’).
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent No. 11,568,865. Although the conflicting claims are not identical, they are not patentably distinct from each other because removing inherent and/or unnecessary limitations/step and rearranging the claims would be within the level of one of ordinary skill in the art. It is well settled that the omission of an element, e.g. identifying, via the one or more processors, a plurality of modes of communication usable to perform the one or more actions;, etc. (see claim 1 of US Patent) and its function is an obvious expedient if the remaining elements perform the same function as before. In re Karlson, 136 USPQ 184 (CCPA 1963). Also note Ex parte Rainu, 168 USPQ 375 (Bd. App. 1969). Omission of a reference element or step whose function is not needed would be obvious to one of ordinary skill in the art.
Conclusion
Other pertinent prior art are cited in the PTO-892 for the applicant's consideration.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MARK VILLENA whose telephone number is (571)270-3191. The examiner can normally be reached 10 am - 6pm EST Monday through Friday.
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, Richemond Dorvil can be reached at (571) 272-7602. 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.
MARK . VILLENA
Examiner
Art Unit 2658
/MARK VILLENA/Examiner, Art Unit 2658