SYSTEMS AND METHODS FOR MANAGING A CARDIAC MONITORING DEVICE WITH A MONITORING INTERVAL TRACKER

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 August 13, 2026 have been fully considered, but they are not persuasive. Applicant’s arguments are primarily directed towards the following: Lack of the claims being considered as a whole. The claimed technological workflow providing system improvement to solve the technological problem of improving system inaccuracies amongst data transmission timing and intervals that can ultimately effect patient care. The claims not being directed to the judicial exception due to being implemented into a practical application (such as being directed to automated processing of medical device telemetry data using control mechanisms within the computer system, as stated by the Applicant). The claims being directed to “significantly more” than an abstract idea. However, the examiner respectfully disagrees with Applicant’s statements. Since the method of the claims states the following: “receive transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations... recording transmission related data associated with the transmission data in a transmissions database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval… automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date… wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later- received transmission data is captured within the monitoring interval for determining the date of service; 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”, the previous claim language (and the claim language when considered as a whole) is still directed to an abstract idea. Furthermore, since the claims do not provide an improvement to the computer itself (but instead modifies the transmitted data), the claims do not provide a direct improvement to the device. Improvements to an abstract idea itself does not equate to a technological improvement. See MPEP 2106.05(a)(II). As a result, the 35 U.S.C. 101 rejection is maintained, which has been further explained and updated below. Claim Objections Claim 3 is objected to because of the following informalities: In claim 3, line 4 the claim states: “...receiving an approval timestamp corresponding to the docket, wherein the approval timestamp corresponding corresponds to an approval date for the docket report.” But should state: “...receiving an approval timestamp corresponding to the docket, wherein the approval timestamp corresponding corresponds to an approval date for the docket report.” (i.e. with “corresponding” deleted). Appropriate correction is required. 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-15 and 18-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-15 and 18-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). Automatically determining a received date for the transmission data. 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 based on the transmission data from the cardiac monitoring interval. Generating a second docket 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. Automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval , the monitoring interval defining an extended end date based on the interval extension rule, which implements an interval extension when the date of service is not generated on or before at least one of the first end date or the second end date. Automatically generating the monitoring interval extension, which includes extending at least one of the first monitoring interval or the second monitoring interval such that later-received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval for determining the date of service. 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: “receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations……automatically determining a received date for transmission data”, And, “automatically generating a date of service for the transmission data when 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 “automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining having an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring for determining the date of service; 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.” This 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 medical device 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, wherein the approval timestamp corresponds to an approval date for the docket.” 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 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.” These steps 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 or a second corresponds to the transmission data; and receiving an approval timestamp after the received date and indicating an approval date corresponding to only one the first or the second” 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” 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 follow the same analysis given above for the independent claims. 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”, 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. Examiner’s Note 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: Receiving transmission data at a medical device platform (see para 0072), the transmission data received over a network and captured from the cardiac monitoring device (see para 0168 and para 0174), 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a monitoring interval using a monitoring interval tracker of a medical device platform, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date; automatically determining a received date for the transmission data, recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval; automatically generating a date of service for the transmission data based when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring interval for determining the date of service; 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: Receiving transmission data at a medical device platform (see para 0072), the transmission data received over a network and captured from the cardiac monitoring device (see para 0168 and para 0174), 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, automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval (see para 0007), 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 all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the 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; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for at least one of the first monitoring interval or the second monitoring interval, and automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval when the date of service is not generated on or before the first end date or the second end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval, 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: Receiving transmission data at a medical device platform (see para 0072), the transmission data received over a network and captured from the cardiac monitoring device (see para 0168 and para 0174), 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, automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval (see para 0007), 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of the medical device platform, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the one or more interrogations and communicated to the medical device platform; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for each of the plurality of monitoring interval; automatically generating a date of service for the transmission data when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to a monitoring interval of the plurality of monitoring intervals when the date of service is not generated on or before an end date of the monitoring interval, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the plurality of monitoring intervals for determining the date of service 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. 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 from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date (abstract), receiving transmission data at a medical device platform over a network (see col. 3, lines 31-39), recording transmission related data associated with the transmission data (see col. 4, lines 58-67 and col. 5, lines 1-4), the transmission related data including at least a received date timestamp (see col. 5, lines 50-64), 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 all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a monitoring interval using a monitoring interval tracker of a medical device platform, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date; automatically determining a received date for the transmission data, recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval; automatically generating a date of service for the transmission data based when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring interval for determining the date of service; 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 from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date (abstract), receiving transmission data at a medical device platform over a network (see col. 3, lines 31-39), recording transmission related data associated with the transmission data (see col. 4, lines 58-67 and col. 5, lines 1-4), the transmission related data including at least a received date timestamp (see col. 5, lines 50-64), 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 all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the 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; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for at least one of the first monitoring interval or the second monitoring interval, and, automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval when the date of service is not generated on or before the first end date or the second end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval, 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 from a group of patients that have a collection date and contains information of a time period that has elapsed since the collection date (abstract), receiving transmission data at a medical device platform over a network (see col. 3, lines 31-39), recording transmission related data associated with the transmission data (see col. 4, lines 58-67 and col. 5, lines 1-4), the transmission related data including at least a received date timestamp (see col. 5, lines 50-64), 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 all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of the medical device platform, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the one or more interrogations and communicated to the medical device platform; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for each of the plurality of monitoring interval; automatically generating a date of service for the transmission data when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to a monitoring interval of the plurality of monitoring intervals when the date of service is not generated on or before an end date of the monitoring interval, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the plurality of monitoring intervals for determining the date of service 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. 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device (see abstract, para 0106, and para 0144), 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), recording transmission related data, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval (see para 0018 and para 0241-0244), 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a monitoring interval using a monitoring interval tracker of a medical device platform, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date; automatically determining a received date for the transmission data, recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval; automatically generating a date of service for the transmission data based when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring interval for determining the date of service; 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device (see abstract, para 0106, and para 0144), 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), recording transmission related data, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval (see para 0018 and para 0241-0244), 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the 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; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for at least one of the first monitoring interval or the second monitoring interval, and automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval when the date of service is not generated on or before the first end date or the second end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval, 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device (see abstract, para 0106, and para 0144), 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), recording transmission related data, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval (see para 0018 and para 0241-0244), 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: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of the medical device platform, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the one or more interrogations and communicated to the medical device platform; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for each of the plurality of monitoring interval; automatically generating a date of service for the transmission data when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to a monitoring interval of the plurality of monitoring intervals when the date of service is not generated on or before an end date of the monitoring interval, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the plurality of monitoring intervals for determining the date of service 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. 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 computer-assisted monitoring device and method (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), And, Receiving transmission data at a medical device (see para 0003), and continuously providing adjustments to the trials conducted (see para 0003), but does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a monitoring interval using a monitoring interval tracker of a medical device platform, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date; automatically determining a received date for the transmission data, recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval; automatically generating a date of service for the transmission data based when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring interval for determining the date of service; 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 computer-assisted monitoring device and method (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), And, Receiving transmission data at a medical device (see para 0003), and continuously providing adjustments to the trials conducted (see para 0003), but does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the 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; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for at least one of the first monitoring interval or the second monitoring interval, and automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval when the date of service is not generated on or before the first end date or the second end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval, 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 computer-assisted monitoring device and method (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), And, Receiving transmission data at a medical device (see para 0003), and continuously providing adjustments to the trials conducted (see para 0003), but does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of the medical device platform, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the one or more interrogations and communicated to the medical device platform; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for each of the plurality of monitoring interval; automatically generating a date of service for the transmission data when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to a monitoring interval of the plurality of monitoring intervals when the date of service is not generated on or before an end date of the monitoring interval, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the plurality of monitoring intervals for determining the date of service 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. 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 system is configured to receive data, having a cloud computing architecture, the transmission data received over a network (see abstract-first four sentences, col. 8, line 1-11) 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 it does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a monitoring interval using a monitoring interval tracker of a medical device platform, the monitoring interval associated with the cardiac monitoring device, the monitoring interval having an end date; automatically determining a received date for the transmission data, recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for the monitoring interval; automatically generating a date of service for the transmission data based when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the monitoring interval when the date of service is not generated on or before the end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending the monitoring interval such that later-received transmission data is captured within the monitoring interval for determining the date of service; 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 system is configured to receive data, having a cloud computing architecture, the transmission data received over a network (see abstract-first four sentences, col. 8, line 1-11) 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 it does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the 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; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for at least one of the first monitoring interval or the second monitoring interval, and automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to the first monitoring interval or the second monitoring interval when the date of service is not generated on or before the first end date or the second end date, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the first monitoring interval or the second monitoring interval, 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 system is configured to receive data, having a cloud computing architecture, the transmission data received over a network (see abstract-first four sentences, col. 8, line 1-11) 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 it does not explicitly disclose all of the following: receiving transmission data at a medical device platform having a cloud computing architecture, the transmission data received over a network and captured from the cardiac monitoring device through one or more interrogations, generating a plurality of monitoring intervals running concurrently using a monitoring interval tracker of the medical device platform, 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 the transmission data, the transmission data captured from the cardiac monitoring device through the one or more interrogations and communicated to the medical device platform; recording transmission related data associated with the transmission data in a transmission database, the transmission related data including at least a received date timestamp corresponding to the received date and a monitoring interval state for each of the plurality of monitoring interval; automatically generating a date of service for the transmission data when 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; automatically generating, using the monitoring interval tracker, a monitoring interval extension corresponding to a monitoring interval of the plurality of monitoring intervals when the date of service is not generated on or before an end date of the monitoring interval, the monitoring interval extension defining an extended end date, wherein automatically generating the monitoring interval extension includes extending at least one of the first monitoring interval or the second monitoring interval such that later – received transmission data is captured within at least one of the plurality of monitoring intervals for determining the date of service 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. 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. 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