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 .
Response to Arguments
Applicant's arguments filed on January 2, 2026 have been fully considered but they are not persuasive. Applicant first presents the argument stating that the present claims are patent-eligible for similar reasons as the claims in McRO, Inc. v. Bandai Namco Games America Inc., 837 F.3d 1299 (Fed. Cir. 2016) ("McRO"), in which the case was found patent-eligible due to the following:
“[b]y incorporating the specific features of the rules as claim limitations, the McRO claims are limited to a specific process for automatically animating characters using particular information and techniques and does not preempt approaches that use rules of a different structure or different techniques." And further proceeds to stating the specific claim 1 limitation: "automatically generating a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date."
The applicant further states that like McRO, the present claims incorporate specific features of the rules as claim limitations, and is therefore integrated into a practical application. The examiner respectfully disagrees. As further explained below, the applicant has amended claims containing the process of "generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture," and "automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform," as well as the "automatically generating a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date" as additionally presented in the applicant’s remarks still equates to a mental process using generic computer technology while containing insignificant pre and post solution activity, which is further explained below. In regards to the previous double patenting rejection, the previous double patenting rejections have been withdrawn in light of the amendments.
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.
The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action.
Claims 1-22 are rejected under 35 U.S.C. 101 because the claims are directed to a mental processes without significantly more.
All of claims 1-22 are directed to a method for managing a cardiac device, which could be performed by the human mind and/or by a human with a physical aid as with pen and paper.
The claims 1, 8, and 14 recite a mental process including the steps such as:
Generating/obtaining a cardiac monitoring interval associated with a cardiac monitoring device using a monitoring interval tracker (containing an end date).
Generating a second monitoring interval associated the cardiac monitoring device using a using a monitoring interval tracker (having a second end date).
Generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker.
Generating automatically a date of service for the transmission data (using the monitoring interval tracker of the medical device platform) based on whether the received date occurs before the end date.
Generating a docket report based on the transmission data from the cardiac monitoring interval.
Generating a second docket report based on the transmission data from the cardiac monitoring interval.
Accessing/obtaining an interval extension rule from a rules database.
Generating a monitoring interval extension having an extended end date based on the interval extension rule, which implements an interval extension if the received date is later than the end date.
Generating a monitoring interval extension having an extended end date based on the interval extension rule, which implements an interval extension when the date of service fails to generate on or before at least one of the first end date or the second end date.
This judicial exception is not integrated into a practical application because the claims merely implement the mental process using generic processing technology and add insignificant extra-solution activity. Specifically: the step of:
“automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform” and “automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform” is considered insignificant pre-solution activity of mere data gathering and processing, since it merely collects the data necessary to carry out the mental process.
Furthermore, merely carrying out mental steps using generic computing technology such as “from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date; automatically generating, according to the interval extension rule, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining having an extended end date, the date of service occurring on or before the extended end date; and causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.” is well established to not amount to an integration into a practical application under the § 101 analysis. See, e.g., MPEP §§ 2106.04(a)(2)(III)(C), 2106.04(d)(I), 2106.05(f), and 2106.05(g).
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the only additional elements recited in the claims are:
The cardiac monitoring device.
The rules database (containing the interval extension rule).
The monitoring interval tracker
Display of a clinic system
The Examiner takes official notice that these are basic, generic components which are well-understood, routine and conventional in the medical diagnostic arts, and the claims here merely use them for their well-understood, routine and conventional functions. As such, those additional elements cannot be considered “significantly more” than the judicial exception in Step 2B of the § 101 analysis.
Regarding claims 2 and 5, the additional steps of “automatically generating the monitoring interval extension includes generating day-by-day extensions to the monitoring interval until the transmission data is received on the extended end date” are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper. Therefore, these claims follow the same analysis given above for the independent claims.
Regarding claims 3-4 and 15 the additional steps of “generating a docket report corresponding to the transmission data:
and receiving an approval timestamp corresponding to the docket report, the approval timestamp corresponding to an approval date for the docket report.”
And “the date of service for the transmission data is further based on whether the approval date occurs prior to the end date.”
And
“wherein the date of service for the transmission data is further based on whether the approval date occurs prior to at least one of the first end date or the second end date, and wherein automatically generating the monitoring interval extension includes generating day-by-day extensions to the first monitoring interval until the approval timestamp occurs on the extended end date.” are considered to be insignificant post-solution activity of mere data gathering since these steps merely gather the data necessary for one or more of the mental steps and carrying out mental steps using generic computing technology. These claims otherwise follow the same analysis given above for the independent claims.
Regarding claims 6-7, the additional steps of “generating, in response to the approval timestamp occurring on the extended end date, a second monitoring interval having a second end date” and “generating a second docket report for the transmission data; receiving a second approval timestamp indicating a second approval date later than the extended end date and prior to the second end date; and determining that the second approval timestamp corresponds to the second docket report” are considered to be insignificant pre-solution activity of mere data gathering since these steps merely gather the data necessary for one or more of the mental steps, and/or are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper. These claims otherwise follow the same analysis given above for the independent claims.
Regarding claims 9-10, the steps of “- generating at least one of a first docket report or a second docket report corresponding to the transmission data; and receiving an approval timestamp after the received date and indicating an approval date corresponding to only one the first docket report or the second docket report” and “wherein the date of service for the transmission data is further based on whether the approval date occurs prior to the first end date or the second end date.” are considered to be insignificant post-solution activity of mere data gathering since these steps merely gather the data necessary for one or more of the mental steps and carrying out mental steps using generic computing technology. These claims otherwise follow the same analysis given above for the independent claims.
Regarding claims 11-12 the steps of “automatically generating the monitoring interval extension includes generating day-by-day extensions to the first monitoring interval until the approval timestamp occurs on the extended end date” and “generating, in response to the approval timestamp occurring on the extended end date, a third monitoring interval running subsequently to the first monitoring interval and having a third end date” are considered to be insignificant pre-solution activity of mere data gathering since these steps merely gather the data necessary for one or more of the mental steps, and/or are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper. These claims otherwise follow the same analysis given above for the independent claims.
Regarding claim 13, the steps of “receiving, prior to the third end date of the third monitoring interval, a second approval timestamp indicating a second approval date; and determining that the second approval date corresponds to the second docket report” are considered to be insignificant pre-solution activity of mere data gathering since these steps merely gather the data necessary for one or more of the mental steps. These claims otherwise Regarding claims 18, the steps of “generating, in response to the approval timestamp occurring on the extended end date, a third monitoring interval having a third end date” are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper. These claims otherwise follow the same analysis given above for the independent claims.
Regarding claims 19, the steps of “generating a graphical representation of the plurality of monitoring intervals as interactive blocks on a plurality of simultaneously presented timelines.” is considered insignificant post-solution activity since it merely outputs the result of the mental process using a generic output modality.
Regarding claim 20, the step of having “a first timeline including the first monitoring interval with a 31-day length; a second timeline including the second monitoring interval with a 91-day length; and a third timeline including a third monitoring interval with a one-year length” are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper, since the claim adds further limitations to the previously presented independent claim 1 above. Therefore, these claims follow the same analysis given above for the independent claims.
Regarding claims 21-22, the steps of “wherein generating the plurality of monitoring intervals is based at least partly on one or more patient care modality rules associated with one or more patient care modalities, wherein the one or more patient care modalities include an in-office care modality, a remote monitoring care modality, or a heart failure care modality.”, and “wherein the one or more patient care modalities include an in- office care modality, a remote monitoring care modality, or a heart failure care modality” are merely additional mental steps that could be performed by the human mind and/or by a human with a physical aid as with pen and paper. These claims otherwise follow the same analysis given above for the independent claims.
Allowable Subject Matter
The claims contain subject matter that would be allowable if the 101 rejections above are overcome. The following is a statement of reasons for the indication of allowable subject matter:
Regarding claims 1, 8, and 14, the closest prior art reference of record is considered in US 20170225001 A1 to Zaidi et al. (hereinafter “Zaidi”).
Regarding claim 1, Zaidi teaches:
A method and system for managing a cardiac monitoring device (abstract), wherein the method comprises:
generating a monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end time (see abstract, para 0165, fig. 3, and para 0078), and extending the time period if the comparison with a gold standard database if a high-accuracy clause is not met. This is used to determine if a patient is in a shockable or non-shockable state (see para 0032-0036), and wherein the system uses a display to display to the rescuer if a shockable rhythm exist and communicate an appropriate message to the rescuer (see para 0067 and para 0070, last sentence), but does not explicitly disclose the following:
generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date; and
causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 8, Zaidi teaches:
A method and system for managing a cardiac monitoring device (abstract), wherein the method comprises:
generating the first monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end time (see abstract, para 0165, fig. 3, and para 0078), and extending the time period if the comparison with a gold standard database if a high-accuracy clause is not met. This is used to determine if a patient is in a shockable or non-shockable state (see para 0032-0036), and wherein the system uses a display to display to the rescuer if a shockable rhythm exist and communicate an appropriate message to the rescuer (see para 0067 and para 0070, last sentence), but does not explicitly disclose the following:
generating a second monitoring interval using the monitoring interval tracker of the medical device platform, the second monitoring interval associated with the cardiac monitoring device, the second monitoring interval having a second end date, the second end date being different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically determining, according to the interval extension rule, whether to generate a monitoring interval extension for at least one of the first monitoring interval or the second monitoring interval according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date,
and
causing a display of a clinic system to present a user interface of a provider portal including the first monitoring interval, the second monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 14, Zaidi teaches:
A method and system for managing a cardiac monitoring device (abstract), wherein the method comprises:
generating a plurality of monitoring intervals associated with the cardiac monitoring device (see para 0004, fourth sentence and para 0047), the monitoring interval having an end time (see abstract, para 0165, fig. 3, and para 0078), and extending the time period if the comparison with a gold standard database if a high-accuracy clause is not met. This is used to determine if a patient is in a shockable or non-shockable state (see para 0032-0036), and wherein the system uses a display to display to the rescuer if a shockable rhythm exist and communicate an appropriate message to the rescuer (see para 0067 and para 0070, last sentence), but does not explicitly disclose the following:
generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture,
and,
each of the plurality of monitoring intervals associated with the cardiac monitoring device, a first monitoring interval of the plurality of monitoring intervals having a first end date and a second monitoring interval of the plurality of monitoring intervals having a second end date that is different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date;
and
causing a display of a clinic system to present a user interface of a provider portal including the plurality of monitoring intervals, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Another close prior art reference of record is considered in US 5,832,448 to Brown.
Regarding claim 1, Brown teaches:
A system and method for a patient monitoring device for multiple patients (abstract), the monitoring system contains collecting patient measurements from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date, and wherein the patient monitoring device contains a display for displaying a group overview chart for each patient (see abstract and col. 12, lines 20-32, and col. 3, lines 15-22), but it does not explicitly disclose the following:
generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date; and
causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 8, Brown teaches:
A system and method for a patient monitoring device for multiple patients (abstract), the monitoring system contains collecting patient measurements from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date, and wherein the patient monitoring device contains a display for displaying a group overview chart for each patient (see abstract and col. 12, lines 20-32, and col. 3, lines 15-22), but it does not explicitly disclose the following:
generating a second monitoring interval using the monitoring interval tracker of the medical device platform, the second monitoring interval associated with the cardiac monitoring device, the second monitoring interval having a second end date, the second end date being different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically determining, according to the interval extension rule, whether to generate a monitoring interval extension for at least one of the first monitoring interval or the second monitoring interval according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date,
and
causing a display of a clinic system to present a user interface of a provider portal including the first monitoring interval, the second monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 14, Brown teaches:
A system and method for a patient monitoring device for multiple patients (abstract), the monitoring system contains collecting patient measurements from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date, and wherein the patient monitoring device contains a display for displaying a group overview chart for each patient (see abstract and col. 12, lines 20-32, and col. 3, lines 15-22), but it does not explicitly disclose the following:
generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture,
and,
each of the plurality of monitoring intervals associated with the cardiac monitoring device, a first monitoring interval of the plurality of monitoring intervals having a first end date and a second monitoring interval of the plurality of monitoring intervals having a second end date that is different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date;
and
causing a display of a clinic system to present a user interface of a provider portal including the plurality of monitoring intervals, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Following Brown, another close prior art reference of record is US 2013/0035871 A1 to Mayou et al. (hereinafter “Mayou”).
Regarding claim 1, Mayou teaches:
A system and method for monitoring a cardiac device, the method comprising:
Generating a monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date (abstract, para 0018, para 0106, and para 0159), generating a report from the transmitted data signal (see para 0185), and changing or modifying the start and end dates and times for the collected data to obtain more accurate pattern data (see para 0321-0329), and wherein the device comprises a display for displaying sensor data (see para 0009), but does not explicitly disclose all the following:
generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date; and
causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 8, Mayou teaches:
A system and method for monitoring a cardiac device, the method comprising:
Generating a first monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date (abstract, para 0018, para 0106, and para 0159), generating a report from the transmitted data signal (see para 0185), and changing or modifying the start and end dates and times for the collected data to obtain more accurate pattern data (see para 0321-0329), and wherein the device comprises a display for displaying sensor data (see para 0009), but does not explicitly disclose all the following:
generating a second monitoring interval using the monitoring interval tracker of the medical device platform, the second monitoring interval associated with the cardiac monitoring device, the second monitoring interval having a second end date, the second end date being different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically determining, according to the interval extension rule, whether to generate a monitoring interval extension for at least one of the first monitoring interval or the second monitoring interval according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date,
and
causing a display of a clinic system to present a user interface of a provider portal including the first monitoring interval, the second monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 14, Mayou teaches:
A system and method for monitoring a cardiac device, the method comprising:
Generating a plurality of monitoring intervals associated with the cardiac monitoring device (), the monitoring interval having an end date (abstract, para 0018, para 0106, and para 0159), generating a report from the transmitted data signal (see para 0185), and changing or modifying the start and end dates and times for the collected data to obtain more accurate pattern data (see para 0321-0329), and wherein the device comprises a display for displaying sensor data (see para 0009), but does not explicitly disclose all the following:
generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture,
and,
each of the plurality of monitoring intervals associated with the cardiac monitoring device, a first monitoring interval of the plurality of monitoring intervals having a first end date and a second monitoring interval of the plurality of monitoring intervals having a second end date that is different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date;
and
causing a display of a clinic system to present a user interface of a provider portal including the plurality of monitoring intervals, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Another close prior art reference of record is considered in US 2014/0324553 A1 to Rosenberg et al. (hereinafter “Rosenberg”).
Regarding claim 1, Rosenberg teaches:
A monitoring device (title and para 0003-0005) used to assess the quality of field data (see abstract), and comparing error rates in order to adjust or address weaknesses in one or more sites (see abstract and para 0020-0027), and contains a display for displaying the performance of a plurality of clinical sites (see para 0113), but does not explicitly disclose all of the following:
generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date; and
causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 8, Rosenberg teaches:
A monitoring device (title and para 0003-0005) used to assess the quality of field data (see abstract), and comparing error rates in order to adjust or address weaknesses in one or more sites (see abstract and para 0020-0027), and contains a display for displaying the performance of a plurality of clinical sites (see para 0113), but does not explicitly disclose all of the following:
generating a second monitoring interval using the monitoring interval tracker of the medical device platform, the second monitoring interval associated with the cardiac monitoring device, the second monitoring interval having a second end date, the second end date being different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically determining, according to the interval extension rule, whether to generate a monitoring interval extension for at least one of the first monitoring interval or the second monitoring interval according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date,
and
causing a display of a clinic system to present a user interface of a provider portal including the first monitoring interval, the second monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 14, Rosenberg teaches:
A monitoring device (title and para 0003-0005) used to assess the quality of field data (see abstract), and comparing error rates in order to adjust or address weaknesses in one or more sites (see abstract and para 0020-0027), and contains a display for displaying the performance of a plurality of clinical sites (see para 0113), but does not explicitly disclose all of the following:
generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture,
and,
each of the plurality of monitoring intervals associated with the cardiac monitoring device, a first monitoring interval of the plurality of monitoring intervals having a first end date and a second monitoring interval of the plurality of monitoring intervals having a second end date that is different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date;
and
causing a display of a clinic system to present a user interface of a provider portal including the plurality of monitoring intervals, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Another relevant prior art reference of record is US 10,839,352 to Mitchell et al. (hereinafter “Mitchell”).
Regarding claim 1, Mitchell teaches:
An Intelligent file-level validation system, where the system contains an administrator/service provider determines rules based on a received data file/specified data. The service provider determines modification data that indicates the amount change according previously stored modification data. Furthermore, threshold(s) can indicate an amount of changed that will occur to a data file based off of a set of rules from a rules database. The data file is determined to be valid based off of the service provider, and if valid, the file is stored in a database and is representative of a source of truth, while invalid data files can be routed to error handling (abstract, col. 4, lines 35-54, col. 6, lines 58-67, col. 23-24, lines 43-67 and lines 1-3 (of col. 24) , col. 10, lines 39-67, col. 11, lines 1-3, 48-52), but does not explicitly disclose all of the following:
A method for managing a cardiac monitoring device, the method comprising:
generating a monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to the end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to the monitoring interval when the date of service fails to generate on or before the end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date; and
causing a display of a clinic system to present a user interface of a provider portal including the monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 8, Mitchell teaches:
An Intelligent file-level validation system, where the system contains an administrator/service provider determines rules based on a received data file/specified data. The service provider determines modification data that indicates the amount change according previously stored modification data. Furthermore, threshold(s) can indicate an amount of changed that will occur to a data file based off of a set of rules from a rules database. The data file is determined to be valid based off of the service provider, and if valid, the file is stored in a database and is representative of a source of truth, while invalid data files can be routed to error handling (abstract, col. 4, lines 35-54, col. 6, lines 58-67, col. 23-24, lines 43-67 and lines 1-3 (of col. 24) , col. 10, lines 39-67, col. 11, lines 1-3, 48-52), but does not explicitly disclose all of the following:
A method for managing a cardiac monitoring device, the method comprising:
generating a first monitoring interval using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture, the first monitoring interval associated with the cardiac monitoring device, the first monitoring interval having a first end date;
generating a second monitoring interval using the monitoring interval tracker of the medical device platform, the second monitoring interval associated with the cardiac monitoring device, the second monitoring interval having a second end date, the second end date being different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically determining, according to the interval extension rule, whether to generate a monitoring interval extension for at least one of the first monitoring interval or the second monitoring interval according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date,
and
causing a display of a clinic system to present a user interface of a provider portal including the first monitoring interval, the second monitoring interval, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
Regarding claim 14, Mitchell teaches:
An Intelligent file-level validation system, where the system contains an administrator/service provider determines rules based on a received data file/specified data. The service provider determines modification data that indicates the amount change according previously stored modification data. Furthermore, threshold(s) can indicate an amount of changed that will occur to a data file based off of a set of rules from a rules database. The data file is determined to be valid based off of the service provider, and if valid, the file is stored in a database and is representative of a source of truth, while invalid data files can be routed to error handling (abstract, col. 4, lines 35-54, col. 6, lines 58-67, col. 23-24, lines 43-67 and lines 1-3 (of col. 24) , col. 10, lines 39-67, col. 11, lines 1-3, 48-52), but does not explicitly disclose all of the following:
A method for managing a cardiac monitoring device, the method comprising:
generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of a medical device platform, the medical device platform having a cloud computing architecture,
and,
each of the plurality of monitoring intervals associated with the cardiac monitoring device, a first monitoring interval of the plurality of monitoring intervals having a first end date and a second monitoring interval of the plurality of monitoring intervals having a second end date that is different than the first end date;
automatically determining a received date for transmission data, the transmission data captured from the cardiac monitoring device through one or more interrogations and communicated to the medical device platform;
automatically generating a date of service for the transmission data based on whether the received date occurs prior to at least one of the first end date or the second end date, the date of service automatically generated using the monitoring interval tracker of the medical device platform;
accessing, from a rules database, an interval extension rule corresponding to at least one of the first monitoring interval or the second monitoring interval when the date of service fails to generate on or before at least one of the first end date or the second end date;
and
automatically generating, a monitoring interval extension according to the interval extension rule, the monitoring interval extension automatically generated using the monitoring interval tracker and defining an extended end date, the date of service occurring on or before the extended end date;
and
causing a display of a clinic system to present a user interface of a provider portal including the plurality of monitoring intervals, the date of service, and the extended end date, the clinic system in communication with the medical device platform.
After further search and consideration, no single reference or combination of references could be found which could properly reject any of the pending claims.
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 10,055,547 B2 to Chari et al. teaches a medical care system used for identifying and addressing unsatisfactory characteristics.
THIS ACTION IS MADE FINAL. 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 KARMEL J WEBSTER whose telephone number is (703)756-5960. The examiner can normally be reached Monday-Friday 7:30am-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, NIKETA PATEL can be reached at 571-272-4156. 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.
/K.J.W./Examiner, Art Unit 3792
/NIKETA PATEL/Supervisory Patent Examiner, Art Unit 3792