System and method for using RFID tags to determine sterilization of devices

Abstract

Methods and systems for controlling the usage of devices with embedded RFID tags including connecting a device to an energy source and reading data from a memory device incorporated in the device. The data may include a unique identifier (UID), a usage value, an activation value, a reprocessing value, and/or a sterilization indicator. The usage value is incremented when the device is connected to the energy source and the activation value is incremented when the device is activated permitting energy to flow from the energy source to the device. Usage of the device is prevented if the UID is on a list of prohibited UIDs, the usage value is not lower than a usage limitation value, the reprocessing value equals a reprocessing limitation value, the activation value equals an activation limitation value, and/or the sterilization indicator does not indicate that the device has been sterilized since its previous usage.

Description

BACKGROUND

1. Technical Field

The present disclosure relates to medical devices. More particularly, the present disclosure is directed to limited-use medical devices that must be sterilized between uses, and to systems and methods for controlling the usage of such devices by using embedded radio-frequency identification (RFID) tags.

2. Discussion of Related Art

Certain medical devices are capable of being used multiple times, and are thus referred to as reusable devices, while other medical devices are configured for single use, and are thus referred to as disposable devices. Many such reusable and disposable medical devices are designed for a pre-determined number of uses and/or for a pre-determined usage time between sterilization. Use of these devices beyond their prescribed usage time or number of uses may result in failure of the device and/or damage to the device or surrounds. On the other hand, given the rising costs of performing medical procedures, clinicians have an incentive to maximize the reuse of medical devices.

SUMMARY

Systems and methods for controlling usage of devices by using RFID tags embedded in the devices are provided.

According to an embodiment of the present disclosure, a method for controlling the usage of a device may include connecting the device to an energy source. The method may further include reading data from a memory device incorporated in the device, wherein the data may include a unique identifier (UID), a usage value, an activation value, a reprocessing value, and/or a sterilization indicator. The method may further include incrementing the usage value when the device is connected to the energy source, and incrementing the activation value when the device is activated permitting energy to flow from the energy source to an energy consuming component of the device. The method may further include preventing usage of the device if the UID is on a list of prohibited UIDs, the usage value is not lower than a usage limitation value, the reprocessing value is equal to a reprocessing limitation value, the activation value is equal to an activation limitation value, and/or the sterilization indicator does not indicate that the device has been sterilized since its previous usage.

According to another embodiment of the present disclosure, a reprocessing system may include a medical device having a memory storing data including a UID, a usage value, a reprocessing value, and a total use time value. The reprocessing system may further include a reprocessing device which may include a data reader/writer configured to read the data stored in the memory incorporated in the medical device, authenticate the data, and update the reprocessing value in the memory of the medical device after the medical device has been reprocessed. The reprocessing system may further include a sterilizer configured to sterilize the device and set a sterilization indicator to “ON” after the device has been sterilized. Authenticating the data stored in the memory of the medical device may include verifying that the UID is not on a list of prohibited UIDs, the usage value does not exceed a usage limitation value, the reprocessing value is lower than the reprocessing limitation value, and the total use time value does not exceed a total use time limitation value.

According to another embodiment of the present disclosure, an apparatus for providing power to a device incorporating a memory may include a processor, a reader, a display, and/or a data port. The apparatus may be configured to connect to the device incorporating the memory and read data from the memory incorporated in the device, wherein the data may include a UID, a usage value, an activation value, a reprocessing value, and/or a sterilization indicator. The apparatus may be further configured to increment the usage value when the device is connected to the energy source, and increment the activation value when the device is activated permitting energy to flow from the energy source to an energy consuming component of the device. The apparatus may be further configured to prevent usage of the device if the UID is on a list of prohibited UIDs, the usage value is not lower than a usage limitation value, the reprocessing value is equal to a reprocessing limitation value, the activation value is equal to an activation limitation value, and/or the sterilization indicator does not indicate that the device has been sterilized since a previous usage.

Any of the above aspects and embodiments of the present disclosure may be combined without departing from the scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Objects and features of the presently disclosed system and method will become apparent to those of ordinary skill in the art when descriptions of various embodiments thereof are read with reference to the accompanying drawings, of which:

FIG. 1 is a diagram of a system for controlling usage of devices with embedded memory devices, in accordance with an embodiment of the present disclosure;

FIG. 2 is a diagram illustrating a schema according to which data may be written to a memory device embedded in a device, in accordance with an embodiment of the present disclosure; and

FIGS. 3A-3B depict a flowchart illustrating a method by which data stored in the device may be authenticated, in accordance with an embodiment of the present disclosure.

FIG. 4 depicts a flowchart illustrating a method controlling the usage of devices with memory devices embedded in the devices during ordinary use of the devices, in accordance with an embodiment of the present disclosure.

FIGS. 5A-5B depict a flowchart illustrating a method by which devices with embedded memory devices may be reprocessed, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

The present disclosure provides a system and method for controlling usage of devices. Specifically the present disclosure is directed to devices, systems and methods employing memory devices, including for example radio frequency identification devices (RFID) defining one or more use parameters.

Although the present disclosure will be described in terms of a specific embodiment, it will be readily apparent to those skilled in this art that various modifications, rearrangements and substitutions may be made without departing from the spirit of the present disclosure. The scope of the present disclosure is defined by the claims appended hereto.

FIG. 1 depicts a diagram of an exemplary system for controlling usage of a device by using a memory device embedded in the device. A system 100 may include a device 110, a generator 120, a reprocessing facility 130, and a central server 140. Generator 120 and reprocessing facility 130 may be connected to central server 140 via a network 150. Network 150 may include a local area network (LAN), a wide area network (WAN), a wireless network (WiFi), and/or the Internet.

Device 110 may include, among other things, a memory device 111. Memory device 111 may be, for example, a radio frequency identification (RFID) tag, a programmable read-only memory (PROM), or the like, and in turn may include a storage 112 and a communication device 113. Storage 112 may include data 114, cyclic redundancy check (CRC) value 117, and sterilization indicator 118. Data 114 may include locked data 115 and unlocked data 116. Communication device 113 may be, for example, a radio frequency (RF) communication system, a WiFi communication system, a Bluetooth (BT) communication system, or the like. Device 110 may be connectable to generator 120. Generator 120 may act as a power source for device 110, and device 110 may at times be connected to generator 120 to allow power to flow to device 110. Generator 120 may also connect wirelessly to device 110, such as via an electromagnetic field, to read and/or write data from or to memory device 111. Generator 120 may include, among other things, a reader 121, a processor 122, a display 123, and a data port 124. Reprocessing facility 130 may include, among other things, a reprocessing data reader/writer 131 and a sterilizing device 132. Central server 140 may include, among other things, a central database 141. Generator 120 and/or reprocessing facility 130 may also include a database either separate from or linked to central database 141.

FIG. 2 depicts a schema according to which data 114 may be stored in the storage 112 on the device 110. The schema may include data which is locked, meaning that it cannot be overwritten, as well as data that is unlocked and may be updated or changed during the use of the device 110. Locked data 115 is typically read-only data that is written to the storage 112 during the manufacture of the device 110.

Locked data typically cannot be overwritten by the generator 120 or even by the reprocessing facility 130. Unlocked data 116 includes data fields that, even if written to the storage 112 during manufacture of the device 110, may be overwritten or updated by the generator 120 or the reprocessing facility 130 during use or reprocessing of the device 110.

Locked data 115 may include, for example, a device universal identification (UID), a single use time limitation value, a total use time limitation value, a reprocessing limitation value, a usage limitation value, and an activation limitation value. The unlocked data 116 may include, for example, a reprocessing value, a data version value, a usage value, an activation value, a total use time value, and a number of slots wherein timestamps may be written.

As explained in more detail below, the device UID is a unique code assigned to the device 110 to identify it from other devices. The single use limitation value is the maximum amount of time that the device 110 may be used during a single usage before it must be reprocessed by reprocessing facility 130. The total use time limitation is the maximum amount of time that the device 110 may be used over its lifetime. The reprocessing limitation value is the maximum number of times that the device 110 may be reprocessed over its lifetime. The usage limitation value is the maximum number of times that the device 110 may be used over its lifetime. The activation limitation value is the maximum number of times that the device 110 may be activated during a single usage. The reprocessing value indicates the number of times that the device 110 has already been reprocessed during its lifetime. The data version value indicates the version of the data 114 that is written to the storage 112. The usage value indicates the number of times that the device 110 has been used during its lifetime. The activation value indicates the number of times that the device 110 has been activated since it was last reprocessed. The sterilization indicator 118 indicates whether the device has been reprocessed since its last usage. The total use time indicates the total amount of time that the device has been used over its lifetime. The use and interaction of these values will be further explained with reference to FIGS. 3-5 below.

FIGS. 3A-3B depict an exemplary method of authenticating the data 114 stored in the storage 112 of the device 110. The data 114 may be authenticated before use of the device 110 is permitted. Processing may begin at step S302 when the device 110 is connected to an energy source, such as generator 120, allowing power to flow to the device 110. The power flowing to device 110 may include electromagnetic power, such as an electromagnetic field, to activate memory device 111 but not the other components of device 110. The power flowing to device 110 may further include electrosurgical power which may power all of device 110 and may be restricted from flowing to device 110 until the data is marked as authenticated at step S326. At step S304, the data 114 is read from the storage 112 of device 110 and copied to the generator 120. All, or only a select portion, of the data 114 may be copied to generator 120.

At step S306, the usage value is compared with the usage limitation value stored on the generator 120. If the usage value is equal to or higher than the usage limitation value, processing proceeds to step S324 where usage of the device is prevented. If the usage value is lower than the usage limitation value, processing proceeds to step S308. By comparing the usage value to the usage limitation value, the device may be limited to a predetermined number of uses.

At step S308, the device's UID is compared with a list of prohibited UIDs. The list of prohibited UIDs may include the UIDs of devices that may no longer be used. If the device's UID is on the list of prohibited UIDs, processing proceeds to step S324. If the device's UID is not on the list of prohibited UIDs, processing proceeds to step S310. The list of prohibited UIDs is compiled and maintained by the reprocessing facility 130 or the manufacturer (not shown), and may include the UIDs of devices that have previously been discarded and/or UIDs that are known to have been duplicated or otherwise tampered with. The list of prohibited UIDs may be updated every time a device, while undergoing reprocessing, is determined to no longer be usable by adding that device's UID to the list of prohibited UIDs. By comparing the device's UID to the list of prohibited UIDs, the manufacturer may ensure that devices with prohibited UIDs are not returned to the market.

At step S310, the version value of the data 114 is compared with a predetermined version value. The predetermined version value may be stored in the generator 120, in the database 141, or elsewhere external to the device. If the version value of the data 114 does not match the predetermined version value, processing proceeds to step S324. If the version value of the data 114 matches the predetermined version value, processing proceeds to step S312. By comparing the version value of the data 114 with the predetermined version value, the generator 120 may ensure that it reads the correct portion of the data 114 from the storage 112, and writes back the data 114 in the correct format so as to be readable by device 110. The integrity of the data 114 in the storage 112 may also be verified.

At step S312, the schema according to which the data 114 is written to the storage 112 is compared to a predetermined schema. If the schema does not match the predetermined schema, processing proceeds to step S324. If the schema matches the predetermined schema, processing proceeds to step S314. By comparing the schema to which the data 114 is written to the device storage 112 to a predetermined schema, the generator 120 may ensure that it reads the correct portion of the data 114 from the device storage 112, and writes back the data 114 in the correct format so as to be readable by device 110. The integrity of the data 114 in the storage 112 may also be verified.

At step S314, a cyclic redundancy check (CRC) value of the data 114 is calculated. At step S316, the calculated CRC value and the CRC value included in the storage 112 is compared. If the calculated CRC value does not match the CRC value included in the storage 112, processing proceeds to step S324. If the calculated CRC value matches the CRC value included in the storage 112, processing proceeds to step S318. By comparing the calculated CRC value and the CRC value included in the storage 112, the data integrity may be verified. A mismatch between the calculated CRC value and the CRC value included in the storage 112 may indicate that data corruption or data tampering has occurred.

The calculated CRC value may also be compared to a previously calculated CRC value of the data 114 stored in the database 141 and associated with the device's UID. If these CRC values do not match, processing proceeds to step S324. If these CRC values match, processing proceeds to step S318. By comparing the calculated CRC value to a previously calculated CRC value stored in the database 141 and associated with the device's UID, it may be determined whether the data has been tampered with or that the device 110 may have been duplicated and loaded with data from another device. As desired, the CRC calculation can be of the locked data 115, the unlocked data 116, or both.

The data 114 may further be verified by using a secure authentication key stored by the central server 140 in database 141. The authentication key may be in the form of a public/private asymmetrical key combination. The generator 120 may further authenticate the device 110 by calculating a signature of the device 110 based on the device's UID, the CRC value of the locked data 115, and the authentication key. This calculated signature may then be compared with a signature stored in storage 112 or in central database 141 to verify the authenticity of device 110.

At step S318, the usage time is compared to the usage time limitation. If the usage time exceeds the usage time limitation, processing proceeds to step S324. If the usage time does not exceed the usage time limitation, processing proceeds to step S320. By comparing the usage time with the usage time limitation, the total length of time that the device is used during the lifetime of the device may be controlled to not exceed a predetermined limit.

At step S320, the number of timestamps written to the storage 112 is compared to a predetermined number. If the number of timestamps exceeds a predetermined number, processing proceeds to step S324 and usage of the device is prevented. If the number of timestamps does not exceed the predetermined number, processing proceeds to step S322. By comparing the number of timestamps written to the storage 112 to the predetermined number, the number of uses of the device may be controlled. The number of timestamps written to the storage 112 and the usage value may further be compared to verify accuracy, since these values should be the same. Variation between the number of timestamps written to the storage 112 and the usage value may indicate tampering with the data 114.

At step S322, the number of timestamps is compared with the reprocessing value. The reprocessing value is updated by the reprocessing facility 130 when the device is reprocessed. By comparing the number of timestamps with the reprocessing value, it may be ensured that the device 110 has been reprocessed since its last usage. If the number of timestamps does not match the reprocessing value, processing proceeds to step S324. If the number of timestamps matches the reprocessing value, processing proceeds to step S326.

If, as a result of any of the preceding inquiries, the determination is made to execute step S324, usage of the device is prevented and processing ends. The display 123 of generator 120 may indicate to the user that usage of the device 110 is prevented. The display 123 may also include the reason why usage of the device 110 is prevented.

If step S324 is never executed, at step S326, the data 114 is marked as authenticated, the usage value is incremented, and the device is allowed to become operational. Accordingly, the generator is signaled that it may close the necessary circuitry to allow electrosurgical energy to flow from the generator 120 to the device 110 as requested by the user.

FIG. 4 depicts a flowchart illustrating a method for controlling the usage of device 110 with storage 112 embedded therein during ordinary use of the device 110. Authentication, as explained above with reference to FIG. 3, may be required before use of device 110 is permitted. Processing may begin at step S402, when a timestamp is written to device 110 by generator 120 when the device is used. At step S404, the generator 120 verifies that the sterilization indicator 118 is set to “ON.” If the sterilization indicator 118 is not set to “ON,” processing proceeds to step S420 where activation of the device 110 is prevented and the user may be notified that the device 110 is not sterile. If the sterilization indicator is set to “ON,” the device is determined to be authentic, and the generator 120 is signaled to allow the flow of electrosurgical energy to the device enabling the user to depresses an activation switch on device 110 and execute step S406.

At step S408, the activation value is compared with the activation limitation value which has been read from the storage 112. If the activation value is lower than the activation limitation value, processing proceeds to step S410. If the activation value is not lower than the activation limitation value, processing proceeds to step S420, where activation of the device 110 is prevented. By comparing the activation value to the activation limitation value, the device 110 may be limited to a predetermined number of activations.

At step S410, the current time is compared with the time indicated by the most recent timestamp. By comparing the current time to the time indicated by the most recent timestamp, the length of time that the device has been in use during a single usage may be controlled. If the current time is later than a predetermined time from the most recent timestamp (e.g., exceeds a predetermined usage time limit), processing proceeds to step S420 where activation of the device 110 is prevented. If the current time is not later than a predetermined time from the most recent timestamp, processing proceeds to step S412. By comparing the current time to the time indicated by the most recent timestamp, the length of time of a single usage may be controlled to not exceed a predetermined amount of time.

At step S412, the single use time is compared with the single use time limitation. If the single use time is within a predetermined time of the single use time limitation, processing proceeds to step S414. If the single use time is not within a predetermined time of the single use time limitation, processing proceeds to step S416. At step S414, the single use time limitation is extended by a predetermined time, and processing proceeds to step S416. For example, the single use time limitation may be extended by one hour. By comparing the single use time with the single use time limitation, and extending the single use time limitation if the single use time is within a predetermined time of the single use time limitation, it may be ensured that the device will have enough use-time left to complete its operation up to some maximum time period as set by the manufacturer.

Similarly, the total usage time limitation of the device may be extended by a predetermined time if the total usage time is within a predetermined time of the total usage time limitation. By extending the total usage time limitation when the total usage time is within a predetermined time of the total usage time limitation, it may be ensured that the device will have enough time to complete its operation.

At step S416, the device is activated after having successfully completed all the startup checks, and power is allowed to flow to the device 110 from the generator 120. At step S418 the activation value is incremented, the sterilization value is set to “OFF,” and processing returns to step S406 when the user again depresses the activation switch.

FIGS. 5A-5B depict an exemplary method by which device 110 with embedded storage 112 may be reprocessed. Reprocessing may occur at reprocessing facility 130 and may include, among other things, inspection of the device 110; removal and/or replacement of parts of device 110; retrieval, verification, and updating of data 114; sterilization of device 110; and/or repackaging of device 110. Inspection of device 110 may include, for example, visual inspection, x-ray inspection, electrical inspection, testing of device 110, and various other tasks that may be performed as part of quality control.

Processing may include step S502, where the device 110 is connected to a reprocessing data reader/writer 131. Thereafter, at step S504, the data 114 is read from the storage 112 of device 110 and copied to the reprocessing data reader/writer 131. All, or only a select portion, of the data 114 may be copied to reprocessing data reader/writer 131 and stored at least temporarily either in a database at the reprocessing facility or transmitted to central database 141 for analysis.

At step S506, the device's UID is compared with the list of prohibited UIDs, similar to step S308 discussed above with reference to FIG. 3. If the device's UID is on the list of prohibited UIDs, processing proceeds to step S528, where the device 110 is discarded. The reprocessing facility and/or the manufacturer may be alerted that the facility which sent device 110 for reprocessing had a device 110 that is on the prohibited list. If the device's UID is not on the list of prohibited UIDs, processing proceeds to step S508.

At step S508, the usage value is compared with the usage limitation value. If the usage value exceeds the usage limitation value, processing proceeds to step S526. If the usage value does not exceed the usage limitation value, processing proceeds to step S510.

At step S510, the total use time of the device 110 is compared with the total use time limitation. If the total use time exceeds the total use time limitation, processing proceeds to step S526. If the total use time does not exceed the total use time limitation, processing proceeds to step S512. By comparing the total use time to the total use time limitation, the total amount of time that the device 110 may be used during its lifetime may be controlled.

At step S512, the reprocessing value is compared to the reprocessing limitation value. If the reprocessing value is lower than the reprocessing limitation value, processing proceeds to step S514. If the reprocessing value is not lower than the reprocessing limitation value, processing proceeds to step S526. By comparing the reprocessing value to the reprocessing limitation value, the number of times that a device can be reprocessed during its lifetime may be controlled.

At step S514, the data 114 read from the storage 112 is compared with data previously stored in the database 141 and associated with the device's UID. If the data 114 matches the data stored in the database 141, processing proceeds to step S516. If the data 114 does not match the data stored in the database 141, processing proceeds to step S526. By comparing the data 114 read from the storage 112 with data previously stored in the database 141, the integrity of data 114 may be verified. As will be appreciated, this data comparison will be of the locked data 115 as the unlocked data 116 is available for update by the generator.

At step S516, a CRC value of the data is calculated. There may be multiple CRC values calculated for all, or just specific portions of the data 114. For example, CRC values for the locked data 115 and unlocked data 116 may be calculated separately. Thereafter, at step S518, the calculated CRC value is compared with the CRC value stored in the storage 112. If the calculated CRC value does not match the CRC value included in the storage 112, processing proceeds to step S526. If the calculated CRC value matches the CRC value included in the storage 112, processing proceeds to step S520. By comparing the calculated CRC value and the CRC value included in the storage 112, the data integrity may be verified. A mismatch between the calculated CRC value and the CRC value included in the storage 112 may indicate that data corruption or data tampering has occurred.

The calculated CRC value may also be compared to a previously calculated CRC value of the data 114 stored in the database 141 and associated with the device's UID. If these CRC values do not match, processing proceeds to step S526. If these CRC values match, processing proceeds to step S520. By comparing the calculated CRC value to a previously calculated CRC value stored in the database 141 and associated with the device's UID, it may be determined whether the data has been tampered with or that the device 110 may have been duplicated and loaded with data from another device.

At step S520, the schema according to which the data 114 is written to the storage 112 is compared to a predetermined schema. If the schema does not match the predetermined schema, processing proceeds to step S524. If the schema matches the predetermined schema, processing proceeds to step S522. By comparing the schema to which the data 114 is written to the device storage 112 to a predetermined schema, the integrity of data 114 may be verified.

At step S522, the version value of the data 114 is compared with a predetermined version value. The predetermined version value may be stored in the reprocessing data reader/writer 131, in the database 141, or elsewhere external to the device. If the version value of the data 114 does not match the predetermined version value, processing proceeds to step S524. If the version value of the data 114 matches the predetermined version value, processing proceeds to step S530. By comparing the version value of the data 114 with the predetermined version value, the integrity of data 114 may be verified.

At step S524, the data 114 on the device 110 is updated after having been determined in steps S520 or S522 that the schema or version value of the data 114 does not match the predetermined schema or predetermined version value. Processing then proceeds to step S530.

At step S526, the UID of device 110 may be added to the list of prohibited UIDs, after it was determined in steps S508, S510, and/or S512 that the device 110 has reached the end of its lifetime, or in steps S514 and/or S518 that the device 110 has been tampered with or duplicated. Step S526 is optional and may be skipped as desired permitting processing to proceed to step S528, where the device is discarded.

At step S530, the reprocessing value is updated to reflect that the device has been reprocessed. Thereafter, at step S532 new CRC values of the data 114 and the unlocked data 116 are calculated. These new CRC values will be different from previous CRC values, because the data 114 has been updated. The CRC value of the locked data 115 is not recalculated and would not have changed, because the locked data 115 cannot be altered. Thereafter, at step S534, the new CRC values are written to the storage 112.

At step S536, the device 110 is sterilized. The sterilization of device 110 may be performed by, for example, sterilization device 132. Methods of sterilization of device 110 may include using ethylene oxide (EtO), steam, gamma, among others. After the device 110 has been sterilized, at step S538, the sterilization indicator 118 is set to “ON” indicating that the device has been sterilized.

Alternatively, the sterilization indicator 118 may only be set when the device 110 has been repackaged and is being shipped out from the reprocessing facility 130. Sterilization indicators of multiple devices may be set as a batch by using a wireless connection, such as by using an electromagnetic field. By delaying the setting of the sterilization indicator 118 until the device 110 is shipped out from the reprocessing facility 130, the device 110 will not be usable if it is stolen after reprocessing and sterilization but prior to the sterilization indicator being set. In another embodiment, device 110 may include multiple sterilization indicators corresponding to the number of times the device 110 may be sterilized over its lifetime, with a new sterilization indicator being set after each sterilization process is completed. In still another embodiment, where the devices are packaged in bulk, a sterilization indicator may be external to the devices and attached to the bulk packaging, and may be used similarly to the method described above to verify that the devices in the bulk packaging has been sterilized.

At step S540, the data 114 read from the storage 112 is stored in the database 141 and associated with the UID of device 110. All of the data 114, or only a portion of the data 114, may be stored in the database 141. Thereafter, at step S542, the device 110 is returned to the market.

Although embodiments have been described in detail with reference to the accompanying drawings for the purpose of illustration and description, it is to be understood that the inventive processes and apparatus are not to be construed as limited thereby. It will be apparent to those of ordinary skill in the art that various modifications to the foregoing embodiments may be made without departing from the scope of the disclosure.

Claims

1. A method for reprocessing usage of a medical apparatus, the method comprising: connecting the medical apparatus to a reprocessing apparatus;reading, by the reprocessing apparatus, locked data and unlocked data from a storage incorporated in the medical apparatus, the locked data including a unique identifier (UID) and limitation values and the unlocked data including a usage value, an activation value, and a reprocessing value;determining whether or not the medical apparatus is able to be reprocessed based on the locked data and the unlocked data;adding the UID of the medical apparatus to a prohibited list stored at a central server when the medical apparatus is determined not to be able to be reprocessed; andwhen the medical apparatus is determined to be able be reprocessed: calculating a cyclic redundancy check (CRC) value based on one or more of the locked data or the unlocked data;reading a CRC value stored in a storage incorporated in the medical apparatus;comparing the CRC value stored in the storage with the calculated CRC value; andadding the UID of the medical apparatus to the prohibited list stored at the central server when the CRC value does not match the calculated CRC value.

2. The method of claim 1, wherein the medical apparatus is determined not to be able to be reprocessed when the UID is included in the prohibited list stored at the central server.

3. The method of claim 1, wherein the medical apparatus is determined not to be able to be reprocessed when the reprocessing value is greater than or equal to a reprocessing limitation value among the limitation values.

4. The method of claim 1, wherein the medical apparatus is determined not to be able to be reprocessed when the usage value is greater than a total use time limitation value among the limitation values.

5. The method of claim 1, further comprising: comparing schema of the locked data and the unlocked data with a predetermined schema for the medical apparatus.

6. The method of claim 5, further comprising: updating the unlocked data when the schema does not match the predetermined schema.

7. A reprocessing apparatus for reprocessing usage of a medical apparatus, the reprocessing apparatus comprising: a data reader/writer configured to: read locked data and unlocked data from a storage incorporated in the medical apparatus, the locked data including a unique identifier (UID) and limitation values and the unlocked data including a usage value, an activation value, and a reprocessing value;determine whether or not the medical apparatus is able to be reprocessed based on the locked data and the unlocked data update the reprocessing value stored in the storage of the medical apparatus after the medical apparatus has been reprocessed;add the UID of the medical apparatus to a prohibited list stored at a central server when the medical apparatus is determined not to be able to be reprocessed; andwhen the medical apparatus is determined to be able to be reprocessed: calculate a cyclic redundancy check (CRC) value based on one or more of the locked data or the unlocked data;read a CRC value stored in the storage incorporated in the medical apparatus;compare the CRC value stored in the storage with the calculated CRC value; andadd the UID of the medical apparatus to the prohibited list stored at the central server when the CRC value does not match the calculated CRC value; anda sterilizer configured to: sterilize the medical apparatus, when the medical apparatus is determined to be able to be reprocessed.

8. The reprocessing apparatus of claim 7, wherein the data reader/writer is further configured to determine the medical apparatus as not able to be reprocessed when the UID is included in the prohibited list stored at the central server.

9. The reprocessing apparatus of claim 7, wherein the data reader/writer is further configured to determine the medical apparatus as not able to be reprocessed when the reprocessing value is greater than or equal to a reprocessing limitation value among the limitation values.

10. The reprocessing apparatus of claim 7, wherein the data reader/writer is further configured to determine the medical apparatus as not able to be reprocessed when the usage value is greater than a total use time limitation value among the limitation values.

11. The reprocessing apparatus of claim 7, wherein the data reader/writer is further configured to compare schema of the locked data and the unlocked data with a predetermined schema for the medical apparatus.

12. The reprocessing apparatus of claim 11, wherein the data reader/writer is further configured to update the unlocked data when the schema does not match the predetermined schema.

13. A reprocessing system comprising: a medical apparatus having a storage storing locked data and unlocked data, the locked data including a unique identifier (UID) and limitation values and the unlocked data including a usage value, an activation value, and a reprocessing value; anda reprocessing apparatus including: a data reader/writer configured to: read the locked data and the unlocked data in the storage incorporated in the medical apparatus;determine whether or not the medical apparatus is able to be reprocessed based on the locked data and the unlocked data update the reprocessing value stored in the storage of the medical apparatus after the medical apparatus has been reprocessed;add the UID of the medical apparatus to a prohibited list stored at a central server when the medical apparatus is determined not to be able to be reprocessed; andwhen the medical apparatus is determined to be able to be reprocessed: calculate a cyclic redundancy check (CRC) value based on one or more of the locked data or the unlocked data;read a CRC value stored in the storage incorporated in the medical apparatus;compare the CRC value stored in the storage with the calculated CRC value; andadd the UID of the medical apparatus to the prohibited list stored at the central server when the CRC value does not match the calculated CRC value; anda sterilizer configured to: sterilize the medical apparatus, when the medical apparatus is determined to be able to be reprocessed.