# US 2021/0241898 A1 · Data handling and prioritization in a cloud analytics network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0241898 A1 - Document ID: US20210241898A1 - Status: Published application - Kind: A1 - Application number: 17/216,997 - Filed: 2021-03-30 - Published: 2021-08-05 - Earliest claimed: 2017-12-28 - Assignees: Ethicon, Inc. - Applicants: Ethicon LLC - Inventors: Frederick E. Shelton, IV; David C. Yates; Jason L. Harris; Gregory J. Bakos - Web page: https://patentgrep.com/patent/US20210241898A1 ## CPC - G16H 40/63: for local operation - G16H 20/40: relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture - G16H 40/40: for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades - G16H 40/67: for remote operation - G16H 50/70: for mining of medical data, e.g. analysing previous cases of other patients - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract A cloud based analytics medical system is disclosed. The system includes a processor, a memory communicatively coupled to the processor, an input/output interface configured for accessing data from a plurality of surgical hubs and a database residing in the memory and configured to store the data. The surgical hub is communicatively coupled to the surgical instrument and the processor. The memory is configured to store instructions executable by the processor to receive critical data from the surgical hub as determined by the surgical hub based on screening criteria, determine a priority status of the critical data, route the critical data to a cloud storage location residing within the memory, and determine a response to the critical data based on an operational characteristic indicated by the critical data. A time component of the response is determined based on the priority status. ## Claims ### Claim 1 A cloud-based central medical server comprising: at least one processor communicatively coupled to at least one memory unit and a transceiver, wherein the processor is configured to: receive a first plurality of data packets from one or more surgical hubs, wherein the first plurality of data packets comprises metadata that is indicative of data criticality, and wherein the first plurality of data packets correspond to a medical event at a first surgical device; analyze the first plurality of data packets to determine a classification status corresponding to the first surgical device, wherein the classification status indicates whether the first plurality of data packets comprises critical data; verify the classification status of the first surgical device; prioritize the first plurality of data packets corresponding to the first surgical device, wherein the classification status of the first surgical device has been verified as corresponding to critical data, and wherein the first surgical device is assigned a priority escalation status; store the plurality of data packets in a separate memory location according to the assigned escalation priority status, and wherein the separate memory location is a separate partition in memory from non-critical data. ### Claim 2 (depends on 1) The cloud based medical server of claim 1, wherein the classification status is determined based on criticality indicators, and wherein the criticality indicators include the severity of a medical event associated with the data, the unexpectedness of the medical event, or the suspiciousness of the data. ### Claim 3 (depends on 1) The cloud based medical server of claim 1, wherein the processor is configured to: request a second plurality of data packets from the first surgical device, wherein the request is triggered based on verifying the classification status of the first surgical device corresponding to critical data. ### Claim 4 (depends on 3) The cloud based medical server of claim 3, wherein the second plurality of data packets corresponds to a second medical event, and wherein the priority escalation status of the first surgical device is reevaluated based on the second plurality of data packets. ### Claim 5 (depends on 1) The cloud based medical server of claim 1, wherein the critical data is further classified according to a binary classification, and wherein the binary classification of the critical data classifies the data as being associated with a bleeding event or a non-bleeding event. ### Claim 6 (depends on 5) The cloud based medical server of claim 5, wherein the priority escalation status comprises watch list, automated response, notification, and urgent action required, and wherein the priority escalation status is determined in part by the binary classification. ### Claim 7 (depends on 1) The cloud based medical server of claim 1, wherein the classification status of the first surgical device is determined as unverified critical data, and wherein the first surgical device is not provided priority escalation status. ### Claim 8 A system for prioritizing critical medical data in a cloud network comprising: a central server communicably coupled to one or more surgical hubs, wherein the central server is remotely located respective to a first surgical hub, and wherein the central server is configured to: receive a first plurality of data from the first surgical hub, wherein the first plurality of data comprises metadata that is indicative of data criticality, and wherein the first plurality of data correspond to a medical event of a first surgical device; analyze the first plurality of data to determine a classification status corresponding to the first surgical device, wherein the classification status indicates whether the first plurality of data comprises critical data; verify the classification status of the first surgical device; prioritize the first plurality of data corresponding the first surgical device, wherein the classification status of the first surgical device has been verified as corresponding to critical data, and wherein the first surgical device is assigned a priority escalation status; store the plurality of data in a separate memory location according to the assigned escalation priority status, and wherein the separate memory location is a separate partition in memory from non-critical data. ### Claim 9 (depends on 8) The system for prioritizing critical medical data in a cloud network of claim 8, wherein the classification status is determined based on criticality indicators, and wherein the criticality indicators include the severity of a medical event associated with the data, the unexpectedness of the medical event, or the suspiciousness of the data. ### Claim 10 (depends on 8) The system for prioritizing critical medical data in a cloud network of claim 8, wherein the central server is configured to: request a second plurality of data from the first surgical device, wherein the request is triggered based on verifying the classification status of the first surgical device corresponding to critical data. ### Claim 11 (depends on 10) The system for prioritizing critical medical data in a cloud network of claim 10, wherein the second plurality of data corresponds to a second medical event, and wherein the priority escalation status of the first surgical device is reevaluated based on the second plurality of data. ### Claim 12 (depends on 8) The system for prioritizing critical medical data in a cloud network of claim 8, wherein the critical data is further classified according to a binary classification, and wherein the binary classification of the critical data classifies the data as being associated with a bleeding event or a non-bleeding event. ### Claim 13 (depends on 12) The system for prioritizing critical medical data in a cloud network of claim 12, wherein the priority escalation status comprises watch list, automated response, notification, and urgent action required, and wherein the priority escalation status is determined in part by the binary classification. ### Claim 14 (depends on 8) The system for prioritizing critical medical data in a cloud network of claim 8, wherein the classification status of the first surgical device is determined as unverified critical data, and wherein the first surgical device is not provided priority escalation status. ### Claim 15 A non-transitory computer readable medium comprising instructions stored thereon, when executed by one or more processors, perform operations comprising: receiving a first plurality of data from a first surgical hubs, wherein the first plurality of data comprises metadata that is indicative of data criticality, and wherein the first plurality of data correspond to a medical event of a first surgical device; analyzing the first plurality of data to determine a classification status corresponding to the first surgical device, wherein the classification status indicates whether the first plurality of data comprises critical data; verifying the classification status of the first surgical device; prioritizing the first plurality of data corresponding the first surgical device, wherein the classification status of the first surgical device has been verified as corresponding to critical data, and wherein the first surgical device is assigned a priority escalation status; storing the plurality of data in a separate memory location according to the assigned escalation priority status, and wherein the separate memory location is a separate partition in memory from non-critical data. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the classification status is determined based on criticality indicators, and wherein the criticality indicators include the severity of a medical event associated with the data, the unexpectedness of the medical event, or the suspiciousness of the data. ### Claim 17 (depends on 15) The non-transitory computer readable medium of claim 15, further comprising: requesting a second plurality of data from the first surgical device, wherein the request is triggered based on verifying the classification status of the first surgical device corresponding to critical data. ### Claim 18 (depends on 17) The non-transitory computer readable medium of claim 17, wherein the second plurality of data corresponds to a second medical event, and wherein the priority escalation status of the first surgical device is reevaluated based on the second plurality of data. ### Claim 19 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the critical data is further classified according to a binary classification, and wherein the binary classification of the critical data classifies the data as being associated with a bleeding event or a non-bleeding event. ### Claim 20 (depends on 19) The non-transitory computer readable medium of claim 19, wherein the priority escalation status comprises watch list, automated response, notification, and urgent action required, and wherein the priority escalation status is determined in part by the binary classification. ### Claim 21 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the classification status of the first surgical device is determined as unverified critical data, and wherein the first surgical device is not provided priority escalation status.