US20140313053A1 - System, method, and device for monitoring orthopaedic implant data over a cellular network - Google Patents
System, method, and device for monitoring orthopaedic implant data over a cellular network Download PDFInfo
- Publication number
- US20140313053A1 US20140313053A1 US14/189,712 US201414189712A US2014313053A1 US 20140313053 A1 US20140313053 A1 US 20140313053A1 US 201414189712 A US201414189712 A US 201414189712A US 2014313053 A1 US2014313053 A1 US 2014313053A1
- Authority
- US
- United States
- Prior art keywords
- implant
- controller
- data
- sensor data
- orthopaedic prosthesis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/0002—Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network
- A61B5/0031—Implanted circuitry
-
- G—PHYSICS
- G08—SIGNALLING
- G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
- G08C17/00—Arrangements for transmitting signals characterised by the use of a wireless electrical link
- G08C17/02—Arrangements for transmitting signals characterised by the use of a wireless electrical link using a radio link
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/32—Joints for the hip
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/38—Joints for elbows or knees
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/40—Joints for shoulders
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/82—Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/3094—Designing or manufacturing processes
- A61F2/30942—Designing or manufacturing processes for designing or making customized prostheses, e.g. using templates, CT or NMR scans, finite-element analysis or CAD-CAM techniques
- A61F2002/30953—Designing or manufacturing processes for designing or making customized prostheses, e.g. using templates, CT or NMR scans, finite-element analysis or CAD-CAM techniques using a remote computer network, e.g. Internet
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/46—Special tools or methods for implanting or extracting artificial joints, accessories, bone grafts or substitutes, or particular adaptations therefor
- A61F2/4657—Measuring instruments used for implanting artificial joints
- A61F2002/4658—Measuring instruments used for implanting artificial joints for measuring dimensions, e.g. length
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/46—Special tools or methods for implanting or extracting artificial joints, accessories, bone grafts or substitutes, or particular adaptations therefor
- A61F2/4657—Measuring instruments used for implanting artificial joints
- A61F2002/4666—Measuring instruments used for implanting artificial joints for measuring force, pressure or mechanical tension
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61F—FILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
- A61F2/00—Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
- A61F2/02—Prostheses implantable into the body
- A61F2/30—Joints
- A61F2/46—Special tools or methods for implanting or extracting artificial joints, accessories, bone grafts or substitutes, or particular adaptations therefor
- A61F2/4657—Measuring instruments used for implanting artificial joints
- A61F2002/4672—Measuring instruments used for implanting artificial joints for measuring temperature
-
- G—PHYSICS
- G08—SIGNALLING
- G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
- G08C2201/00—Transmission systems of control signals via wireless link
- G08C2201/40—Remote control systems using repeaters, converters, gateways
- G08C2201/42—Transmitting or receiving remote control signals via a network
-
- G—PHYSICS
- G08—SIGNALLING
- G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
- G08C2201/00—Transmission systems of control signals via wireless link
- G08C2201/60—Security, fault tolerance
- G08C2201/61—Password, biometric
Definitions
- the present disclosure relates generally to systems and methods for transmitting, receiving, and/or monitoring orthopaedic implant sensor data.
- Orthopaedic implants or prostheses are implanted into patients by orthopaedic surgeons to, for example, correct or otherwise alleviate bone and/or soft tissue loss, trauma damage, and/or deformation of the bone(s) of the patients.
- Some orthopaedic prostheses include one or more sensors for detecting or measuring various effects or forces acting on the orthopaedic prostheses and/or the surrounding environment. After initial implantation, it is often desirable to periodically monitor the implant sensor data particularly when the patient is experiencing problems with the orthopaedic prosthesis. However, even when the patient is experiencing an ongoing problem with an orthopaedic prosthesis, the patient must typically schedule an appointment for examination by the orthopaedic surgeon or other healthcare provider in their office or hospital.
- the problem may be intermittent and may not be observable at the time of the appointment and/or may change over time.
- the patient may be experiencing discomfort during the delay making prompt medical analysis of the orthopaedic prosthesis desirable.
- a medical device includes an orthopaedic prosthesis having a circuit secured thereto.
- the circuit may include a sensor, a cellular transmitter, and a processor.
- the sensor may be configured to generate implant sensor data and the cellular transmitter may be configured to transmit data over a cellular network.
- the processor may be electrically coupled to the sensor and/or the cellular transmitter.
- the processor may be configured to receive the implant sensor data from the sensor and transmit the implant sensor data over the cellular network using the cellular transmitter.
- the cellular transmitter may form a portion of a cellular transceiver in some embodiments.
- the cellular transceiver may be configured to receive data, such as programming data, over the cellular network.
- the processor may be configured to transmit the implant sensor data in response to a signal received from a controller over the cellular network via the cellular transceiver. Additionally, wherein the data is embodied as programming data, the processor may be configured to update a program of the orthopaedic prosthesis using the programming data.
- the orthopaedic prosthesis may also include a memory device.
- the memory device may have stored therein a first implant serial number associated with the orthopaedic prosthesis.
- the processor may be configured to retrieve the first implant serial number from the memory device and compare the first implant serial number to a second implant serial number received over the cellular network via the cellular transceiver. Additionally, the processor may be configured to transmit the implant sensor data if the first implant serial number is equal to the second implant serial number.
- the processor may be configured to store the implant sensor data in the memory device, retrieve the stored implant sensor data, and transmit the retrieved implant sensor data over the cellular network via the cellular transmitter.
- the processor may be configured to compare the implant sensor data to a predetermined threshold value and initiate communication with the controller over the cellular network using the cellular transmitter based on such comparison. Once cellular communication is established, the processor may be configured to transmit the implant sensor data to the controller over the cellular network using the cellular transmitter. In addition, the processor may be configured to retrieve implant sensor data from the memory device and transmit the retrieved implant sensor data to the controller over the cellular network using the cellular transmitter once cellular communication is established. Further, in some embodiments, the processor may be configured to retrieve an implant serial number from the memory device and transmit the implant serial number to the controller over the cellular network using the cellular transmitter.
- a system for monitoring implant data over a cellular network may include a controller and an orthopaedic prosthesis.
- the orthopaedic prosthesis may include a cellular transceiver configured to communicate with the controller over the cellular network.
- the orthopaedic prosthesis may also include a sensor configured to generate implant sensor data.
- the cellular transceiver of the orthopaedic prosthesis may be configured to transmit the implant sensor data to the controller over the cellular network.
- the system may also include portable computing device.
- the portable computing device may be embodied as, for example, a computer, a laptop computer, a personal digital assistant (PDA), a cellular phone, or the like.
- the portable computing device may be configured to communicate with the controller over a network such as a local area network (LAN), a wide area network, the Internet, a cellular network, and/or the like.
- the controller may be configured to transmit the implant sensor data to the portable computing device.
- the portable computing device may be configured to display the implant sensor data, or indicia thereof, to a user of the portable computing device.
- the portable computing device may be configured to transmit an implant serial number and a passcode to the controller over the network.
- the implant serial number and/or passcode may be supplied or entered by a user of the portable computing device.
- the system may also include a database communicatively coupled to the controller.
- the controller may be configured to verify an association or relation between the implant serial number and the passcode using data stored in the database. For example, the controller may be configured to verify that the user identified by the supplied passcode is authorized to communicate with the orthopaedic prosthesis identified by the implant serial number. Additionally, in some embodiments, the controller may be configured to retrieve contact data associated with the orthopaedic prosthesis from the database based on the implant serial number. The controller may be configured to subsequently initiate cellular communication with the orthopaedic prosthesis using the contact data. The controller may also be configured to transmit programming data to the orthopaedic prosthesis over the cellular network. In such embodiments, the orthopaedic prosthesis may be configured to update a program of a processor of the orthopaedic prosthesis using the programming data.
- a method of monitoring implant sensor data over a cellular network may include receiving the implant sensor data from an orthopaedic prosthesis over the cellular network.
- the method may also include receiving an implant serial number and a passcode from a portable computing device.
- the method may further include verifying an association between the implant serial number and the passcode.
- the association between the implant serial number and the passcode may be verified by retrieving data from a database and comparing the data to the implant serial number and the passcode.
- the method may also include retrieving contact data associated with the orthopaedic prosthesis from a database based on the implant serial number and initiating cellular communication with the orthopaedic prosthesis using the contact data.
- the method may include retrieving implant sensor data from a memory device of the orthopaedic prosthesis. In such embodiments, the method may further include transmitting the retrieved implant sensor data over the cellular network. The method may also include receiving a first implant serial number over a cellular network and retrieving a second implant serial number from a memory device of the orthopaedic prosthesis. The method may additionally include comparing the first implant serial number and the second implant serial number and transmitting the implant sensor data over the cellular network based on such comparison. In some embodiments, the method may further include transmitting the implant sensor data to a portable computing device. In such embodiments, the implant sensor data, or indicia thereof, may be displayed on the portable computing device.
- the method may include receiving the implant sensor data from an implant sensor of the orthopaedic prosthesis, comparing the implant sensor data to a predetermined threshold, and transmitting the implant sensor data over the cellular network using a cellular transmitter of the orthopaedic prosthesis based on the comparing step. Additionally, the method may include transmitting programming data to the orthopaedic prosthesis over the cellular network and updating a program of the orthopaedic prosthesis using the programming data.
- FIG. 1 is a simplified block diagram of a system for monitoring implant sensor data over a cellular network
- FIG. 2 is a simplified block diagram of one embodiment of an orthopaedic prosthesis of the system of FIG. 1 ;
- FIG. 3 is a simplified flowchart of one embodiment of an algorithm for monitoring orthopaedic prosthesis data over a cellular network that may be executed by a portable computing device of the system of FIG. 1 ;
- FIGS. 4A-B include a simplified flowchart of one embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by a controller of the system of FIG. 1 ;
- FIG. 5 is a simplified flowchart of one embodiment of an algorithm for communicating with a controller over a cellular network that may be executed by an orthopaedic prosthesis of the system of FIG. 1 ;
- FIG. 6 is a simplified flowchart of another embodiment of an algorithm for communicating with a controller over a cellular network that may be executed by the orthopaedic prosthesis of the system of FIG. 1 ;
- FIG. 7 is a simplified flowchart of another embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by the controller of the system of FIG. 1 ;
- FIG. 8 is a simplified flowchart of another embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by the portable computing device of the system of FIG. 1 .
- a system 10 for monitoring implant sensor data over a cellular network 18 includes an orthopaedic implant or prosthesis 12 , a controller 14 , and a portable computing device 16 .
- the orthopaedic prosthesis 12 is configured to communicate with the controller 14 over the cellular network 18 .
- the orthopaedic prosthesis 12 may be embodied as any type of orthopaedic prosthesis such as, for example, a knee implant, a hip implant, a shoulder implant, or the like configured to be implanted in a patient 50 .
- the orthopaedic prosthesis 12 includes a number of electrical devices such as a cellular transmitter/transceiver and one or more implant sensors.
- the orthopaedic prosthesis 12 is communicatively coupled to the cellular network 18 via a wireless cellular communication link 20 .
- the communication link 20 is established only while cellular communication between the orthopaedic prosthesis 12 and the controller 14 is desired.
- cellular communication is intended to refer to any transmission or reception of data over a cellular network.
- the cellular network 18 may be embodied as any type of cellular wireless network and may include any number of devices configured to facilitate cellular communication between the orthopaedic prosthesis 12 and the controller 14 .
- the cellular network 18 may include one or more cellular carrier networks electrically coupled to any number of carrier towers having any number of cellular antennas coupled thereto.
- the cellular carrier network(s) may include such elements as Mobile Telephone or Telecommunications Switch Offices (hereinafter sometimes MTSO), carrier base stations, interconnections operable to couple the various elements of the cellular carrier network, additional towers, antennas, and other communication devices useful in propagating data across the cellular network 18 .
- the cellular network 18 may include portions of the local Public Switch Telephone Network (hereinafter sometimes PSTN).
- PSTN Public Switch Telephone Network
- the cellular network 18 may use any cellular transmission protocol to facility the cellular communication between the orthopaedic prosthesis 12 and the controller 16 .
- the cellular network 18 or portion thereof, is embodied as an analog wireless network such as an Advanced Mobile Phone Service (hereinafter sometimes AMPS) network, a Narrowband Advanced Mobile Phone Service (hereinafter sometimes NAMPS) network, or other analog wireless network.
- the orthopaedic prosthesis 12 and the controller 14 are configured to communicate with each other over the cellular network 18 using an analog wireless transmission protocol or technology such as, for example, a Frequency Division Multiple Access (hereinafter sometimes FDMA) transmission protocol.
- FDMA Frequency Division Multiple Access
- the cellular network 18 may be embodied as a digital wireless network such as a Global System for Mobile Communications (hereinafter sometimes GSM) network, a Personal Communications Systems (hereinafter sometimes PCS) network, a Digital Advanced Mobile Phone Service (hereinafter sometimes DAMPS) network, or other digital wireless network which, in some implementations, may use, communicate with, or rely on portions of an analog wireless network such as an AMPS network.
- GSM Global System for Mobile Communications
- PCS Personal Communications Systems
- DAMPS Digital Advanced Mobile Phone Service
- the cellular network 18 may be embodied as a circuit switched digital wireless network, a packet switched wireless network, or other type of digital wireless network including proprietary digital networks such as the Integrated Digital Enhanced Network (hereinafter sometimes iDEN).
- iDEN Integrated Digital Enhanced Network
- the orthopaedic prosthesis 12 and the controller 14 are configured to communicate with each other over the cellular network 18 using a digital wireless transmission protocol or technology such as, for example, a Time Division Multiple Access (hereinafter sometimes TDMA) transmission protocol, a Code Division Multiple Access (hereinafter sometimes CDMA) transmission protocol, a Code Division Multiple Access 2000 (hereinafter sometimes CDMA2000) transmission protocol, a Wideband Code Division Multiple Access (hereinafter sometimes WCDMA) transmission protocol, and/or a Time Division-Synchronous Code Division Multiple Access (hereinafter sometimes TD-SCDMA) transmission protocol.
- TDMA Time Division Multiple Access
- CDMA2000 Code Division Multiple Access 2000
- WCDMA Wideband Code Division Multiple Access
- TD-SCDMA Time Division-Synchronous Code Division Multiple Access
- the controller 14 is coupled to the cellular network 18 via a communication link 22 .
- the communication link 22 may be embodied as any type and number of communication links capable of facilitating communication between the controller 14 and the cellular network 18 .
- the communication link 22 may be embodied as a wired communication link, a wireless communication link, or a combination thereof.
- the communication link 22 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the controller 14 includes a processor 26 and a memory device 28 .
- the processor 26 may be embodied as any type of processor including, for example, discrete circuitry (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs).
- the memory device 28 may be embodied as any type of memory device and may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM).
- the controller 14 may include other devices and circuitry typically found in a computer for performing the functions described herein such as, for example, a hard drive, input/output circuitry, and the like.
- the controller 14 forms a portion of a call center 30 .
- the call center 30 may include any number of controllers 14 configured to communicate with the portable computing device 16 and the orthopaedic prosthesis 12 .
- the call center 30 may form a portion of a hospital network.
- the call center 30 includes a database 32 , which may be embodied as any type of database capable of storing orthopaedic prosthesis-related data. Although illustrated in FIG. 1 as a single database, it should be appreciated that the database 32 may be embodied as any number of separate databases, file folders, flat files, or other storage locations.
- the orthopaedic prosthesis-related data may include, for example, orthopaedic prosthesis serial numbers, passcodes assigned to individual surgeons, cellular telephone numbers and other contact data, implant sensor data, and/or the like.
- the orthopaedic prosthesis-related data may be stored in the database 32 in association with, indexed by, or otherwise retrievable based on each data type.
- implant serial numbers are stored in association with passcodes assigned to the orthopaedic surgeons or other healthcare providers authorized to monitor the orthopaedic prosthesis identified by the particular implant serial number as discussed in more detail below.
- the patient database 32 may be located at the same location as the controller 14 (e.g., within the same hospital) or may be located remotely therefrom.
- the controller 14 is communicatively coupled to the database 32 via a number of communication links 34 .
- the communication links 34 may be embodied as any type of communications links such as a wired communication link, a wireless communication link, or a combination thereof.
- the communication link 34 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the controller 14 is also configured to communicate with the portable computing device 16 via a network 24 .
- the network 24 may be embodied as any type of network capable of facilitating communication between the portable computing device 16 and the controller 14 .
- the network 24 may be embodied as or include a local area network (LAN), a wide area network (WAN), or may form a portion of a publicly-accessible, global network such as the Internet.
- the network 24 may be embodied as a wired network, a wireless network, or a combination thereof.
- the controller 14 is coupled to the network 24 via a communication link 36 .
- the controller 14 is also coupled to the cellular network 18 via a communication link 22 .
- the communication links 22 , 36 may be embodied as any type of communication links capable of facilitating communication between the controller 14 and the cellular network 18 and the network 24 , respectively.
- the communication links 22 , 36 may be embodied as any type of communications links such as wired communication links, a wireless communication links, or a combination thereof.
- the communication link 22 , 36 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the portable computing device 16 is configured to communicate with the controller 14 over the network 24 .
- the portable computing device 16 is also communicatively coupled to the network 24 via a number of communication links 38 .
- the communication links 38 may be embodied as any type of communications links such as a wired communication link, a wireless communication link, or a combination thereof.
- the communication link 38 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the portable computing device 16 may be embodied as any type of computing device usable by an orthopaedic surgeon or other orthopaedic healthcare provider 60 to transmit data to and receive data from the controller 14 over the network 24 .
- the portable computing device 16 may be embodied as a Personal Digital Assistant (hereinafter sometimes PDA), a laptop or desktop computer, a PDA mobile phone, and/or similar computing devices suitable for communicating with the controller 14 over the network 24 and displaying data to the orthopaedic healthcare provider 60 .
- PDA Personal Digital Assistant
- the illustrative portable computing device 16 includes a processor 40 and a memory device 42 .
- the processor 40 may be embodied as any type of processor including, for example, discrete circuitry (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs).
- the memory device 42 may be embodied as any type of memory device and may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM).
- the portable computing device 16 may include other devices and circuitry typically found in a computer for performing the functions described herein such as, for example, a hard drive, input/output circuitry, and the like.
- the portable computing device 16 may include a transmitter/receiver, network card, modem, and/or the like for communicating with the controller 14 over the network 24 .
- the orthopaedic healthcare provider 60 may operate the portable computing device 16 to monitor implant sensor data generated by the orthopaedic prosthesis 12 and/or update programming of the orthopaedic prosthesis 12 as described in more detail below in regard to FIGS. 3-5 .
- the orthopaedic healthcare provider may enter an implant serial number and a passcode into the portable computing device 16 , which is subsequently transmitted to the controller 14 via the network 24 .
- the implant serial number may be embodied as any type of data that uniquely identifies the orthopaedic prosthesis 12 from other orthopaedic prostheses used in the system 10 .
- the implant serial number may include any number and type of characters including numeric characters and alphabetic characters.
- the implant serial number is identical to, based on, or otherwise derived from a cellular telephone or access number associated with the orthopaedic prosthesis device 12 .
- the passcode may be embodied as any type of data that identifies the orthopaedic healthcare provider 60 .
- the passcode may be unique to the orthopaedic healthcare provider 60 or to some other entity such as a hospital, a group of orthopaedic healthcare providers, or the like.
- the controller 14 verifies that the orthopaedic surgeon or healthcare provider associated with the passcode is authorized to communicate with the orthopaedic prosthesis 12 identified by the implant serial number. To do so, the controller 14 may retrieve data, such as a look-up table, from the database 32 and compare the passcode and implant serial number to the retrieved data. If the user identified by the passcode is authorized to communicate with the orthopaedic prosthesis sensor, the controller 14 initiates cellular communication with the orthopaedic prosthesis 12 and receives implant sensor data transmitted from the orthopaedic prosthesis 12 over the cellular network 18 .
- data such as a look-up table
- the controller 14 subsequently transmits the implant sensor data to the portable computing device 16 via the network 24 .
- the implant sensor data, or indicia thereof such as a graph, chart, or the like, is displayed to the orthopaedic healthcare provider 60 via a display device or the like of the portable computing device 16 .
- the orthopaedic healthcare provider 60 may operate the portable computing device 16 to supply programming data to the orthopaedic prosthesis 12 via the cellular network 18 .
- the programming data is used by the orthopaedic prosthesis 12 to update a program executed by electronic circuitry of the orthopaedic prosthesis 12 .
- the orthopaedic prosthesis 12 may be configured to initiate cellular communication with the controller 14 based on a predetermined condition such as the value(s) of the implant sensor data.
- the orthopaedic prosthesis 12 includes electronic circuitry 100 coupled to or otherwise housed therein.
- the electronic circuitry 100 includes a processor 102 , one or more implant sensors 104 , and a cellular transmitter and/or receiver (e.g., a cellular transceiver) 106 .
- the processor 102 is coupled to the sensor(s) 104 via a number of communication links 108 and to the cellular transmitter/transceiver 106 via a number of communication links 110 .
- the communication links 108 , 110 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the processor 102 may be embodied as any type of processor capable of receiving implant sensor data from the implant sensor(s) 104 and transmitting the implant sensor data over the cellular network 18 using the cellular transmitter/transceiver 106 .
- the processor 102 may be embodied as, or otherwise include discrete processing circuits (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs).
- the electronic circuitry 100 may include any number of implant sensors 104 .
- the implant sensor(s) 104 may be embodied as any type of implant sensor configured to generate implant sensor data of a parameter of interest.
- the implant sensor(s) 104 may be embodied as a pressure sensor, a load sensor, a temperature sensor, a hall-effect sensor, or the like.
- the implant sensor data is transmitted to the processor 102 via the communication links 108 .
- the cellular transmitter 106 may be embodied as any transmitter or transceiver configured to transmit and/or receive data over the cellular network 18 . That is, the cellular transmitter 106 is configured to transmit and/or receive data using a wireless carrier frequency and communication protocol/technology supported or otherwise used by the cellular network 18 . As such, the cellular transmitter 106 may include any number of circuits and electronic devices (e.g., a cellular antenna) and, in some embodiments, may be similar to the cellular transmitters/transceivers used in typical cellular telephones and other cellular communication devices.
- the electronic circuitry 100 also includes a memory device 112 .
- the memory device 112 is communicatively coupled to the processor 102 via a number of communication links 114 . Similar to communication links 108 , 110 , the communication links 114 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like.
- the memory device 12 may be embodied as any type of memory device capable of storing implant sensor data and, in some embodiments, programming or software code.
- the memory device 12 may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM).
- the processor 102 and other devices of the electronic circuitry 100 receive power from a power source 116 .
- the power source 116 may be embodied as any type of power source capable of supplying power to the other devices of the electronic circuitry 100 sufficient to perform the functions described herein.
- the power source 116 may be a rechargeable power source or may be a permanent, continuous power source.
- the power source 116 may be embodied as an implant battery, an inductively charged battery, a radio frequency (RF) charged battery, a vibration charged power source, a piezoelectric power source, a thin-film, battery, a thermal power source, an acoustic power source, and/or the like.
- RF radio frequency
- the processor 102 may be configured to receive implant sensor data from the implant sensor(s) 104 and transmit the implant sensor data to the controller 14 over the cellular network 18 in response to a signal received from the controller 14 . Additionally or alternatively, the processor 102 may be configured to store the implant sensor data in the memory device 112 and subsequently retrieve the stored implant sensor data for transmission to the controller 14 via the cellular network 18 . Additionally, in some embodiments, the processor 102 is configured to execute a program stored in or otherwise defined by data stored in the memory device 112 . The program or data may be embodied as software/firmware code executed by the processor and/or other data such as variable data used by a program executed by the processor 102 . In such embodiments, the processor 102 may be configured to update the program stored in the memory device 112 with, based on, or using programming data received from the controller 106 via the cellular network 18 .
- the portable computing device 16 i.e., the processor 40 of the system 10 may execute an algorithm 200 for monitoring orthopaedic prosthesis data as illustrated in FIG. 3 .
- the algorithm 200 begins with a process step 202 in which the orthopaedic healthcare provider 60 (e.g., an orthopaedic surgeon) supplies the implant serial number associated with the orthopaedic prosthesis 12 of interest and the passcode associated with the orthopaedic healthcare provider 60 .
- the orthopaedic healthcare provider 60 e.g., an orthopaedic surgeon
- the implant serial number may be embodied as any type of data that uniquely identifies the orthopaedic prosthesis 12 from other orthopaedic prostheses and the passcode may be embodied as any type of data that identifies the orthopaedic healthcare provider 60 .
- the surgeon may supply the implant serial number and passcode via manually typing in the data or otherwise operating the portable computing device 16 such that the implant serial number and passcode are transmitted to the controller 14 .
- the orthopaedic healthcare provider 60 is prompted for the implant serial number and passcode (e.g., via a data field) once the orthopaedic healthcare provider 60 has initiated communication with the controller 14 over the network 24 .
- the implant serial number and passcode are transmitted from the portable computing device 16 to the controller 14 via the network 24 and communication links 36 , 38 in process step 204 .
- the processor 40 of the portable computing device 16 determines if the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 in process steps 206 , 208 , respectively. To do so, the orthopaedic healthcare provider 60 may be prompted to choose which function the orthopaedic healthcare provider 60 would like to perform. Alternatively, both functions may be accessible by the orthopaedic healthcare provider 60 at any time. As such, it should be appreciated that the process steps 206 , 208 may be executed in a sequential order or contemporaneously with each other.
- the algorithm 200 advances to process step 210 .
- the portable computing device 16 receives implant sensor data from the orthopaedic prosthesis 12 via the cellular network 18 , the controller 14 , and the network 24 .
- the implant sensor data may be current implant sensor data and/or historical implant sensor data generated over a period of time.
- the received implant sensor data or indicia thereof is displayed to the orthopaedic healthcare provider 60 on a display screen, monitor, or other display device of the portable computing device 16 .
- the implant sensor data may be displayed in numerical form, in a graph, in a chart, or the like.
- the orthopaedic healthcare provider 60 may monitor any parameter of interest that is measured by one or more of the implant sensors 104 in near-real time and/or monitor historic implant sensor data generated therefrom.
- the processor 40 determines that the orthopaedic healthcare provider 60 desires to update the programming of the orthopaedic prosthesis 12
- programming data is received from the orthopaedic healthcare provider 60 in process step 214 .
- the orthopaedic healthcare provider 60 may supply the programming data by manually typing in the data into the portable computing device 16 and/or by supplying the data on a readable media such as a diskette, a compact disc read only memory (CD ROM) media, digital video disk (DVD) media, universal serial bus (USB) flashdrive, or the like.
- the portable computing device 16 includes a suitable media player such as a “floppy” disk drive, a CD ROM drive, a DVD drive, or the like.
- the programming data may be embodied as any type of programming data usable by the electronic circuitry 100 of the orthopaedic prosthesis 12 .
- the programming data may be embodied as software/firmware code that is configured to be executed by the processor 102 of the orthopaedic prosthesis 12 .
- the programming data may be embodied as variable data configured to be used by a program executed by the processor 102 .
- the programming data may be used by the electronic circuitry 100 to alter, change, or affect any function of the electronic circuitry 100 .
- the program data may alter the sampling rate used by the processor 102 to sample the implant sensor data generated by the implant sensor(s) 104 , to alter threshold values or tolerance ranges, to alter communication protocols used by the cellular transmitter/transceiver 106 , and/or any other device or function of the electronic circuitry 100 .
- the programming data is transmitted to the controller 14 in process step 216 .
- the programming data is transmitted to the controller 14 via the communication links 36 , 38 and the network 24 .
- the controller 14 of the call center 30 is configured to execute an algorithm 300 for communicating with an orthopaedic prosthesis 12 over the cellular network 18 during the operation of the system 10 .
- the algorithm 300 beings with a process step 302 in which the implant serial number and the passcode are received from the portable computing device 16 via the network 24 .
- the controller 14 determines if the implant serial number and passcode are valid. To do so, the controller 14 may retrieve data from the database and compare the retrieved data to the implant serial number and/or the passcode. Such a comparison may include any number of comparison steps.
- the controller 14 may compare the received implant serial number to a list of implant serial numbers to verify that the received implant serial number is a valid implant serial number. Additionally, the controller 14 may compare the received passcode to a list of passcodes to verify that the received passcode is a valid passcode. Yet further, the controller 14 may retrieve a “look-up” table or the like, which relates passcodes to authorized implant serial numbers, from the database 32 . If so, the controller 14 may compare the received implant serial number and passcode to the “look-up” table to verify that the orthopaedic healthcare provider identified by the received passcode is authorized to communicate with the orthopaedic prosthesis identified by the received implant serial number. Additionally, the controller 14 may use other algorithms and security measures to ensure the identity of the orthopaedic healthcare provider 60 and appropriate authorization.
- the algorithm 300 loops back to process step 302 wherein the controller 14 waits to receive a new implant serial number and/or passcode. However, if the controller 14 determines that the implant serial number and passcode are valid in process step 304 , the algorithm 300 advances to process step 306 in which the controller 14 retrieves contact data associated with the orthopaedic prosthesis 12 identified by the implant serial number from the database 32 .
- the contact data may be embodied as any type of data with which the controller 14 may initiate cellular communication with the orthopaedic prosthesis 12 .
- the contact data may be embodied as or may be based on a cellular telephone number or cellular access number of the orthopaedic prosthesis 12 .
- the controller 14 may retrieve the contact data by, for example, retrieving a “look-up” table from the database 32 that indexes implant serial numbers to associated contact data. The controller 14 may then determine the appropriate contact data based on the received implant serial number.
- the implant serial number is embodied as the contact data.
- the implant serial number may be embodied as the cellular telephone or access number of the orthopaedic prosthesis 12 . In such embodiments, the process step 306 may be skipped.
- the controller 14 initiates cellular communication with the orthopaedic prosthesis 12 in process step 308 .
- the controller 14 is configured to establish a cellular connection with the orthopaedic prosthesis 12 (via the cellular transmitter/transceiver 106 ) over the cellular network 18 using the contact data.
- the controller 14 may transmit the appropriate data to the cellular network 18 to facilitate the cellular connection.
- the controller 14 and the orthopaedic prosthesis 12 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween.
- the controller 14 is configured to transmit the received implant serial number to the orthopaedic prosthesis 12 . To do so, the controller 14 transmits the received implant serial number over the cellular network 18 via the communication links 20 , 22 . Subsequently, the controller 14 determines if the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 in process steps 312 , 314 , respectively.
- the controller 14 may determine if the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 based on, for example, data or signals received from the portable computing device 16 and/or from the orthopaedic prosthesis 12 . For example, the controller 14 may determine that the orthopaedic healthcare provider 60 desires to monitor implant sensor data if implant sensor data is received from the orthopaedic prosthesis 12 . Alternatively, the controller 14 may determine that the orthopaedic healthcare provider 60 desires to update the programming of the orthopaedic prosthesis if programming data is received form the portable computing device 16 .
- the portable computing device 16 may be configured to transmit a signal or data to the controller 14 to inform the controller 14 that the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 .
- the controller 14 may use any one or more of a number of methods to determine which one or more functions to perform.
- the algorithm 300 advances to process step 313 in which the controller 14 transmits a signal to the orthopaedic prosthesis 12 instructing the prosthesis to begin transmitting the implant sensor data.
- the controller 14 receives implant sensor data from the orthopaedic prosthesis 12 via the cellular network 18 .
- the controller 14 is configured to transmit the implant sensor data to the portable computing device 16 via the network 24 .
- the algorithm advances to process step 315 in which the controller 14 transmits a signal to the orthopaedic prosthesis 12 to prepare for a programming update.
- the controller 14 transmits the programming data to the orthopaedic prosthesis 12 .
- the controller 14 transmits the programming data over the cellular network 18 via the communication links 20 , 22 .
- the algorithm 300 loops back to process step 302 wherein the controller 14 waits to receive a new implant serial number and/or passcode.
- the orthopaedic prosthesis 12 of the system 10 is configured to execute an algorithm 400 for communicating with the controller 14 over the cellular network 18 .
- the algorithm 400 begins with a process step 402 in which the orthopaedic prosthesis 12 initializes cellular communication with the controller 14 of the call center 30 .
- the controller 14 is configured to initiate cellular communication with the orthopaedic prosthesis 12 in the illustrative embodiment.
- the orthopaedic prosthesis 12 i.e., the electronic circuitry 100
- the orthopaedic prosthesis 12 may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication with the controller 14 in process step 402 .
- the orthopaedic prosthesis 12 receives the implant serial number from the controller 14 in process step 404 .
- the processor 102 is configured to determine if the received implant serial number is valid. To do so, in one embodiment, the processor 102 is configured to retrieve an implant serial number associated with the implant 12 from the memory device 112 . The processor 102 compares the retrieved implant serial number with the implant serial number received from the controller 14 to determine if the implant serial numbers are equal or otherwise match within some predetermined amount of tolerance. In this way, the processor 102 ensures that the controller 14 has initiated cellular communication with the correct orthopaedic prosthesis 12 .
- the algorithm 400 loops back to process step 402 wherein the electronic circuitry 100 of the orthopaedic prosthesis 12 waits for the initiation of a new cellular communication from the controller 14 .
- the algorithm 400 advances to process steps 408 and 410 .
- the processor 102 determines if the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the electronic circuitry 100 , respectively.
- the processor 102 may determine if the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 based on, for example, data or signals received from the controller 14 .
- the processor 102 may determine that the orthopaedic healthcare provider 60 desires to update the programming of the orthopaedic prosthesis 12 if programming data is received from the controller 14 .
- the controller 14 may be configured to transmit a signal or data to the orthopaedic prosthesis 12 to inform the processor 102 that the orthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of the orthopaedic prosthesis 12 .
- the orthopaedic prosthesis 12 may use any one or more of a number of methods to determine which one or more functions to perform.
- the algorithm 400 advances to process step 412 .
- the processor 102 is configured to transmit the current implant sensor data received from the implant sensor(s) 104 to the controller 14 .
- the processor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the implant sensor data over the cellular network 18 .
- the implant sensor data may be transmitted in any suitable form.
- the implant sensor data may be transmitted in compressed or non-compressed form to the controller 14 .
- the processor 102 determines if any stored implant sensor data should be transmitted to the controller 14 .
- the processor 102 may be programmed or otherwise configured to transmit or not transmit the stored implant sensor data. Additionally or alternatively, the processor 102 may be configured to access or otherwise retrieve data from the memory device 112 and determine if the stored implant sensor data should be transmitted based on such data (e.g., based on the value of the retrieved data).
- the orthopaedic prosthesis 12 may be programmed to transmit stored data or not to transmit stored data depending on the particular application and/or implementation of the system 10 and/or the orthopaedic prosthesis 12 .
- the algorithm 400 loops back to process step 402 wherein the electronic circuitry 100 of the orthopaedic prosthesis 12 waits for the initiation of a new cellular communication from the controller 14 . If, however, the processor 102 determines that the implant sensor data stored in the memory device 112 should also be transmitted, the algorithm 400 advances to process step 418 . In process step 418 , the implant sensor data stored in the memory device 112 is retrieved. The retrieved implant sensor data is subsequently transmitted to the controller 14 in process step 420 . To do so, the processor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the retrieved implant sensor data over the cellular network 18 .
- the implant sensor data retrieved from the memory device 112 may be transmitted to the controller 14 in any suitable form including, for example, compressed or non-compressed form.
- the algorithm 400 loops back to process step 402 wherein the electronic circuitry 100 of the orthopaedic prosthesis 12 waits for the initiation of a new cellular communication from the controller 14 .
- processor 102 receives programming data from the controller 14 over the cellular network 18 using the cellular transmitter/transceiver 106 .
- the processor 102 is configured to update one or more programs or programming data used by the electronic circuitry 100 using the received programming data depending on, for example, the type of programming data received.
- the programming data is embodied as software/firmware code
- the processor 102 may be configured to store the programming data in the memory device 112 and subsequently begin executing the software/firmware code.
- the electronic circuitry 100 may require a “reboot” or otherwise re-initialization to begin executing the new programming code.
- the programming data is embodied as variable data
- the processor 102 may be configured to store the programming data in the memory device 112 such that the programming data overwrites existing data stored therein. In this way, the programming data may alter, change, or update old variable data used by the software and/or firmware executed by the electronic circuitry 100 .
- a data variable indicating if the processor 102 should transmit stored implant sensor data may be stored in the memory device 112 in a known memory location.
- the processor 102 is configured to analyze the stored data variable to determine whether to transmit stored implant data.
- the programming of the orthopaedic prosthesis 12 may be altered, changed, or updated by transmitting a new data value to replace the data variable stored in the memory device 112 .
- the orthopaedic prosthesis 12 transmits a confirmation signal to the call center 30 to confirm that the programming of the orthopedic prosthesis 12 is complete in process step 426 .
- the algorithm 400 loops back to process step 402 wherein the electronic circuitry 100 of the orthopaedic prosthesis 12 waits for the initiation of a new cellular communication from the controller 14 .
- the orthopaedic prosthesis 12 may be configured to initiate cellular communication with the controller 14 if one or more predetermined conditions occur.
- the processor 102 of the orthopaedic prosthesis 12 may be configured to execute an algorithm 500 for communicating with the controller 14 over the cellular network 18 as illustrated in FIG. 6 .
- the algorithm 500 beings with a process step 502 in which the processor 102 determines if the value of the implant sensor data received from any one or more of the implant sensors 104 is out of a tolerance range and/or above or below a predetermined threshold level.
- the processor 102 may be configured to determine if the pressure data is above some predetermined maximum allowable pressure value and/or below some predetermined minimum allowable pressure value. To do so, the processor 102 may compare the pressure data received from the implant sensor 104 to a value or values stored in the memory device 112 . In such embodiments, the value or values stored in the memory device 112 form a portion of the programming data of the orthopaedic device 12 and, as such, may be changed, altered, or otherwise updated as discussed in detail above in regard to FIGS. 3-5 .
- the algorithm 500 advances to process step 504 .
- the orthopaedic prosthesis 12 initiates cellular communication with the controller 14 .
- the orthopaedic prosthesis 12 is configured to establish a cellular connection with the controller 14 via use of the cellular transmitter/transceiver 106 .
- the orthopaedic prosthesis 12 may transmit the appropriate data to the cellular network 18 to facilitate the cellular connection.
- the orthopaedic prosthesis 12 and the controller 14 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween.
- the orthopaedic prosthesis 12 is configured to transmit the implant serial number associated with the orthopaedic prosthesis 12 in process step 506 .
- the processor 102 may be configured to retrieve the implant serial number from the memory device 112 and transmit the implant serial number over the cellular network 18 via the communication links 20 , 22 .
- the processor 102 is configured to transmit the implant sensor data received from the implant sensor(s) 104 to the controller 14 .
- the processor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the implant sensor data over the cellular network 18 .
- the implant sensor data may be transmitted in any suitable form.
- the implant sensor data may be transmitted in compressed or non-compressed form to the controller 14 .
- the processor 102 determines if the orthopaedic prosthesis 12 should continue to send current implant data to the controller 14 . If so, the algorithm 500 loops back process step 508 in which the current implant sensor data is transmitted to the controller 14 as described above. In this way, the processor 102 may transmit a stream of current implant data to the controller 14 .
- the orthopaedic prosthesis 12 may be instructed to continue sending the current implant data by a signal received from the controller 14 , based on a predetermined transmission time, or a programmable flag or data value. If the processor 102 determines that the orthopaedic prosthesis 12 should continue sending the orthopaedic implant sensor data in process step 509 , the algorithm 500 advances to process step 510 .
- the processor 102 determines if any stored implant sensor data should be transmitted to the controller 14 .
- the processor 102 may be programmed or otherwise configured to transmit or not transmit the stored implant sensor data. Additionally or alternatively, the processor 102 may be configured to access or otherwise retrieve data from the memory device 112 and determine if the stored implant sensor data should be transmitted based on such data (e.g., based on the value of the retrieved data).
- the algorithm 500 loops back to process step 502 wherein the processor 102 of the orthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 is within the predetermined tolerance range. If, however, the processor 102 determines that the implant sensor data stored in the memory device 112 should also be transmitted, the algorithm 500 advances to process step 512 . In process step 512 , the processor 102 retrieves the implant sensor data from the memory device 112 . The retrieved implant sensor data is subsequently transmitted to the controller 14 in process step 514 .
- the processor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the retrieved implant sensor data over the cellular network 18 .
- the implant sensor data retrieved from the memory device 112 may be transmitted to the controller 14 in any suitable form including, for example, compressed or non-compressed form.
- the algorithm 500 loops back to process step 502 wherein the processor 102 of the orthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 are within the predetermined tolerance range.
- the algorithm 500 advances to process step 516 .
- the processor 102 determines if there is any incoming cellular communication from the controller 104 . To do so, the processor 102 may monitor the data output of the cellular transmitter/transceiver 106 . If the processor 102 determines that there is no incoming cellular communication, the algorithm 500 loops back to process step 502 wherein the processor 102 of the orthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 are within the predetermined tolerance range.
- the algorithm 500 advances to process step 518 .
- the processor is configured to communicate with the controller 14 of the call center 30 over the cellular network 18 .
- the processor may transmit implant sensor data, including stored implant sensor data in some embodiments, to the controller 14 over the cellular network 18 and/or receive programming data from the controller 14 over the cellular network 18 .
- the processor may execute an algorithm similar to the algorithm 400 illustrated in and discussed above in regard to FIG. 5 in process step 518 .
- the processor 102 may be configured to receive an implant serial number from controller 14 , determine the validity of the implant serial number, transmit current and stored implant sensor data to the controller 14 , receive programming data from the controller 14 , and/or update the programming of the orthopaedic device 12 using the programming data in process step 518 .
- the algorithm 500 loops back to process step 502 wherein the processor 102 of the orthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 is within the predetermined tolerance range.
- the controller 14 may execute an algorithm 600 for communicating with an orthopaedic prosthesis 12 over the cellular network 18 .
- the algorithm 600 beings with a process step 602 in which the controller 14 determines if there is incoming cellular communication from the orthopaedic prosthesis 12 . If so, the algorithm 600 advances to process step 604 wherein the controller 14 is configured to initialize cellular communication with the orthopaedic prosthesis 12 . To do so, the controller 14 may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication with the orthopaedic prosthesis 12 .
- the controller 14 is configured to receive an implant serial number from the orthopaedic prosthesis 12 over the cellular network 18 in process step 606 .
- the controller 14 receives implant sensor data from the orthopaedic prosthesis 12 via the cellular network 18 .
- the controller 14 may be configured to store the implant serial number and/or the implant sensor data in the memory device 28 and/or the database 32 .
- the controller 14 is configured to retrieve contact information associated with the portable computing device 16 based on the received implant serial number in process step 610 .
- the contact information may be embodied as any type of data with which the controller 14 may initiate communication with the portable computing device 16 over the network 24 .
- the contact information may be embodied as or be based on an internet protocol (IP) address or a cellular telephone or access number of the portable computing device 16 .
- IP internet protocol
- the contact information may be embodied as or include an e-mail address or the like.
- the controller 14 may retrieve the contact information by, for example, retrieving a “look-up” table from the database 32 that indexes implant serial numbers to associated contact information. The controller 14 may then determine the appropriate contact information based on the received implant serial number.
- the controller 14 initiates network communication with the portable computing device 16 in process step 612 .
- the controller 14 is configured to establish a network connection with the portable computing device 16 over the network 24 using the contact information.
- the controller 14 may transmit the appropriate data to the network 24 to facilitate the network connection.
- the controller 14 and the portable computing device 16 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween.
- the controller 14 is configured to transmit the received implant sensor data to the portable computing device 16 in process step 614 . To do so, the controller 14 transmits the received implant sensor data over the network 24 via the communication links 36 , 38 .
- the algorithm 600 loops back to the process step 602 wherein the controller 14 is configured to determine if there is any new cellular communication incoming from the orthopaedic prosthesis 12 .
- the algorithm 600 advances to process step 616 .
- the controller 14 determines if there is any incoming communication from the portable computing device 16 . If the controller 14 determines that there is no incoming communication, the algorithm 600 loops back to the process step 602 wherein the controller 14 is configured to determine if there is any new cellular communication incoming from the orthopaedic prosthesis 12 .
- the algorithm 600 advances to process step 618 .
- the controller 14 is configured to communicate with the portable computing device 16 over the network 24 and/or the orthopaedic prosthesis 12 over the cellular network 24 .
- the controller 14 receives implant serial numbers and passcodes from the portable computing device 16 , receives implant sensor data from the orthopaedic prosthesis 12 , and/or transmits implant sensor data to the portable computing device 16 over the network 24 .
- the controller 14 may execute a sub-algorithm similar to the algorithm 300 illustrated in and discussed above in regard to FIGS.
- the controller 14 may be configured to receive an implant serial number and passcode from the portable computing device 16 , validate the implant serial number and passcode, receive programming data from the portable computing device 16 , initiate cellular communication with the orthopaedic prosthesis 12 , receive implant sensor data from the orthopaedic prosthesis 12 , transmit the implant sensor data to the portable computing device 16 , and/or transmit the programming data to the orthopaedic prosthesis 12 in process step 618 .
- the algorithm 600 loops back to process step 602 wherein the controller 14 is configured to determine if there is any new cellular communication incoming from the orthopaedic prosthesis 12 .
- the portable computing device 16 may execute an algorithm 700 for monitoring orthopaedic prosthesis data.
- the algorithm 700 beings with a process step 702 in which the controller 14 determines if there is incoming communication from the controller 14 . If so, the algorithm 700 advances to process step 704 wherein the portable computing device 16 is configured to initialize network communication with the controller 14 . To do so, the portable computing device 16 may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the network communication with the controller 14 .
- the portable computing device 16 receives implant sensor data from the controller 14 in process step 706 .
- the implant sensor data may be current implant sensor data and/or historical implant sensor data generated over a period of time.
- the received implant sensor data or indicia thereof is displayed to the orthopaedic healthcare provider 60 on a display screen, monitor, or other display device of the portable computing device 16 .
- the implant sensor data may be displayed in numerical form, in a graph, in a chart, or the like.
- the orthopaedic healthcare provider 60 may be automatically and/or promptly notified if a problem has occurred with the orthopaedic prosthesis 12 as defined by the implant sensor data.
- the orthopaedic healthcare provider 60 may then subsequently monitor the performance of the orthopaedic prosthesis 12 via the implant sensor data received from the controller 14 and displayed on the portable computing device 16 .
- the portable computing deice 16 determines if the orthopaedic healthcare provider 60 desires to disconnect from the call center 30 (i.e., stop receiving implant sensor data). If so, the algorithm 700 loops back to process step 702 in which the portable communication device 16 again monitors for any incoming communication from the call center 30 . However, if the orthopaedic healthcare provider 60 desires to continue receiving orthopaedic prosthesis data, the algorithm 700 loops back to process step 706 and 708 in which additional current orthopaedic prosthesis data is received and displayed to the orthopedic healthcare provider 60 .
- the algorithm 700 advances to process step 710 .
- the portable computing device 16 determines if the orthopaedic healthcare provider 60 desires to interact with the orthopaedic prosthesis 12 (e.g., monitor implant sensor data and/or update the programming of the implant 12 ). If the portable computing device 16 determines that orthopaedic healthcare provider 60 does not desire to interact with the orthopaedic prosthesis 12 , the algorithm 700 loops back to the process step 702 wherein the portable computing device 16 is configured to determine if there is any new network communication incoming from the controller 14 .
- the algorithm 700 advances to process step 712 .
- the portable computing device 16 is configured to communicate with the controller 14 of the call center 30 over the network 24 .
- the portable computing device 16 is configured to transmit an implant serial number, passcode, and/or programming data to the controller 14 , receive implant sensor data from the controller 14 , and display the implant sensor data to the orthopaedic healthcare provider 60 .
- the portable computing device 16 may execute a sub-algorithm similar to the algorithm 200 illustrated in and discussed above in regard to FIG. 3 in process step 712 .
- the portable computing device 16 may be configured to receive an implant serial number and passcode from the orthopaedic healthcare provider 60 , receive programming data from the orthopaedic healthcare provider 60 , transmit the implant serial number, the passcode, and the programming data to the controller 14 , receive implant sensor data form the controller 14 , and display the implant sensor data to the orthopaedic healthcare provider 60 in process step 712 .
- the algorithm 700 loops back to process step 702 wherein the portable computing device 16 is configured to determine if there is any new network communication incoming from the controller 14 .
Landscapes
- Health & Medical Sciences (AREA)
- Life Sciences & Earth Sciences (AREA)
- Engineering & Computer Science (AREA)
- Animal Behavior & Ethology (AREA)
- Veterinary Medicine (AREA)
- Biomedical Technology (AREA)
- Heart & Thoracic Surgery (AREA)
- Public Health (AREA)
- General Health & Medical Sciences (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- Pathology (AREA)
- Surgery (AREA)
- Molecular Biology (AREA)
- Medical Informatics (AREA)
- Biophysics (AREA)
- Orthopedic Medicine & Surgery (AREA)
- Cardiology (AREA)
- Oral & Maxillofacial Surgery (AREA)
- Transplantation (AREA)
- Vascular Medicine (AREA)
- General Physics & Mathematics (AREA)
- Prostheses (AREA)
- Measuring And Recording Apparatus For Diagnosis (AREA)
Abstract
Description
- This application is a divisional application of U.S. patent application Ser. No. 11/537,338, now U.S. Pat. No. 8,685,091, which was filed on Sep. 29, 2006, issued on Apr. 1, 2014, and is expressly incorporated herein by reference.
- The present disclosure relates generally to systems and methods for transmitting, receiving, and/or monitoring orthopaedic implant sensor data.
- Orthopaedic implants or prostheses are implanted into patients by orthopaedic surgeons to, for example, correct or otherwise alleviate bone and/or soft tissue loss, trauma damage, and/or deformation of the bone(s) of the patients. Some orthopaedic prostheses include one or more sensors for detecting or measuring various effects or forces acting on the orthopaedic prostheses and/or the surrounding environment. After initial implantation, it is often desirable to periodically monitor the implant sensor data particularly when the patient is experiencing problems with the orthopaedic prosthesis. However, even when the patient is experiencing an ongoing problem with an orthopaedic prosthesis, the patient must typically schedule an appointment for examination by the orthopaedic surgeon or other healthcare provider in their office or hospital. As such, there is often a delay between the time that the patient is first aware of the problem and the scheduled appointment. Such a delay may reduce the effectiveness of the medical analysis of the orthopaedic prosthesis. For example, the problem may be intermittent and may not be observable at the time of the appointment and/or may change over time. In addition, the patient may be experiencing discomfort during the delay making prompt medical analysis of the orthopaedic prosthesis desirable.
- According to one aspect, a medical device includes an orthopaedic prosthesis having a circuit secured thereto. The circuit may include a sensor, a cellular transmitter, and a processor. The sensor may be configured to generate implant sensor data and the cellular transmitter may be configured to transmit data over a cellular network. The processor may be electrically coupled to the sensor and/or the cellular transmitter. The processor may be configured to receive the implant sensor data from the sensor and transmit the implant sensor data over the cellular network using the cellular transmitter. The cellular transmitter may form a portion of a cellular transceiver in some embodiments. The cellular transceiver may be configured to receive data, such as programming data, over the cellular network. In such embodiments, the processor may be configured to transmit the implant sensor data in response to a signal received from a controller over the cellular network via the cellular transceiver. Additionally, wherein the data is embodied as programming data, the processor may be configured to update a program of the orthopaedic prosthesis using the programming data.
- The orthopaedic prosthesis may also include a memory device. The memory device may have stored therein a first implant serial number associated with the orthopaedic prosthesis. In such embodiments, the processor may be configured to retrieve the first implant serial number from the memory device and compare the first implant serial number to a second implant serial number received over the cellular network via the cellular transceiver. Additionally, the processor may be configured to transmit the implant sensor data if the first implant serial number is equal to the second implant serial number. In some embodiments, the processor may be configured to store the implant sensor data in the memory device, retrieve the stored implant sensor data, and transmit the retrieved implant sensor data over the cellular network via the cellular transmitter.
- Additionally, in some embodiments, the processor may be configured to compare the implant sensor data to a predetermined threshold value and initiate communication with the controller over the cellular network using the cellular transmitter based on such comparison. Once cellular communication is established, the processor may be configured to transmit the implant sensor data to the controller over the cellular network using the cellular transmitter. In addition, the processor may be configured to retrieve implant sensor data from the memory device and transmit the retrieved implant sensor data to the controller over the cellular network using the cellular transmitter once cellular communication is established. Further, in some embodiments, the processor may be configured to retrieve an implant serial number from the memory device and transmit the implant serial number to the controller over the cellular network using the cellular transmitter.
- According to another aspect, a system for monitoring implant data over a cellular network may include a controller and an orthopaedic prosthesis. The orthopaedic prosthesis may include a cellular transceiver configured to communicate with the controller over the cellular network. The orthopaedic prosthesis may also include a sensor configured to generate implant sensor data. In such embodiments, the cellular transceiver of the orthopaedic prosthesis may be configured to transmit the implant sensor data to the controller over the cellular network. The system may also include portable computing device. The portable computing device may be embodied as, for example, a computer, a laptop computer, a personal digital assistant (PDA), a cellular phone, or the like. The portable computing device may be configured to communicate with the controller over a network such as a local area network (LAN), a wide area network, the Internet, a cellular network, and/or the like. The controller may be configured to transmit the implant sensor data to the portable computing device. In response, the portable computing device may be configured to display the implant sensor data, or indicia thereof, to a user of the portable computing device. In some embodiments, the portable computing device may be configured to transmit an implant serial number and a passcode to the controller over the network. The implant serial number and/or passcode may be supplied or entered by a user of the portable computing device.
- The system may also include a database communicatively coupled to the controller. In such embodiments, the controller may be configured to verify an association or relation between the implant serial number and the passcode using data stored in the database. For example, the controller may be configured to verify that the user identified by the supplied passcode is authorized to communicate with the orthopaedic prosthesis identified by the implant serial number. Additionally, in some embodiments, the controller may be configured to retrieve contact data associated with the orthopaedic prosthesis from the database based on the implant serial number. The controller may be configured to subsequently initiate cellular communication with the orthopaedic prosthesis using the contact data. The controller may also be configured to transmit programming data to the orthopaedic prosthesis over the cellular network. In such embodiments, the orthopaedic prosthesis may be configured to update a program of a processor of the orthopaedic prosthesis using the programming data.
- According to yet another aspect, a method of monitoring implant sensor data over a cellular network may include receiving the implant sensor data from an orthopaedic prosthesis over the cellular network. The method may also include receiving an implant serial number and a passcode from a portable computing device. In such embodiments, the method may further include verifying an association between the implant serial number and the passcode. The association between the implant serial number and the passcode may be verified by retrieving data from a database and comparing the data to the implant serial number and the passcode. The method may also include retrieving contact data associated with the orthopaedic prosthesis from a database based on the implant serial number and initiating cellular communication with the orthopaedic prosthesis using the contact data.
- In some embodiments, the method may include retrieving implant sensor data from a memory device of the orthopaedic prosthesis. In such embodiments, the method may further include transmitting the retrieved implant sensor data over the cellular network. The method may also include receiving a first implant serial number over a cellular network and retrieving a second implant serial number from a memory device of the orthopaedic prosthesis. The method may additionally include comparing the first implant serial number and the second implant serial number and transmitting the implant sensor data over the cellular network based on such comparison. In some embodiments, the method may further include transmitting the implant sensor data to a portable computing device. In such embodiments, the implant sensor data, or indicia thereof, may be displayed on the portable computing device. Yet further, in some embodiments, the method may include receiving the implant sensor data from an implant sensor of the orthopaedic prosthesis, comparing the implant sensor data to a predetermined threshold, and transmitting the implant sensor data over the cellular network using a cellular transmitter of the orthopaedic prosthesis based on the comparing step. Additionally, the method may include transmitting programming data to the orthopaedic prosthesis over the cellular network and updating a program of the orthopaedic prosthesis using the programming data.
- The detailed description particularly refers to the following figures, in which:
-
FIG. 1 is a simplified block diagram of a system for monitoring implant sensor data over a cellular network; -
FIG. 2 is a simplified block diagram of one embodiment of an orthopaedic prosthesis of the system ofFIG. 1 ; -
FIG. 3 is a simplified flowchart of one embodiment of an algorithm for monitoring orthopaedic prosthesis data over a cellular network that may be executed by a portable computing device of the system ofFIG. 1 ; -
FIGS. 4A-B include a simplified flowchart of one embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by a controller of the system ofFIG. 1 ; -
FIG. 5 is a simplified flowchart of one embodiment of an algorithm for communicating with a controller over a cellular network that may be executed by an orthopaedic prosthesis of the system ofFIG. 1 ; -
FIG. 6 is a simplified flowchart of another embodiment of an algorithm for communicating with a controller over a cellular network that may be executed by the orthopaedic prosthesis of the system ofFIG. 1 ; -
FIG. 7 is a simplified flowchart of another embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by the controller of the system ofFIG. 1 ; and -
FIG. 8 is a simplified flowchart of another embodiment of an algorithm for communicating with an orthopaedic prosthesis over a cellular network that may be executed by the portable computing device of the system ofFIG. 1 . - While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific exemplary embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
- Referring to
FIG. 1 , asystem 10 for monitoring implant sensor data over acellular network 18 includes an orthopaedic implant orprosthesis 12, acontroller 14, and aportable computing device 16. Theorthopaedic prosthesis 12 is configured to communicate with thecontroller 14 over thecellular network 18. Theorthopaedic prosthesis 12 may be embodied as any type of orthopaedic prosthesis such as, for example, a knee implant, a hip implant, a shoulder implant, or the like configured to be implanted in apatient 50. As discussed below in regard toFIG. 2 , theorthopaedic prosthesis 12 includes a number of electrical devices such as a cellular transmitter/transceiver and one or more implant sensors. Theorthopaedic prosthesis 12 is communicatively coupled to thecellular network 18 via a wirelesscellular communication link 20. In some embodiments, thecommunication link 20 is established only while cellular communication between theorthopaedic prosthesis 12 and thecontroller 14 is desired. As used herein, the term “cellular communication” is intended to refer to any transmission or reception of data over a cellular network. - The
cellular network 18 may be embodied as any type of cellular wireless network and may include any number of devices configured to facilitate cellular communication between theorthopaedic prosthesis 12 and thecontroller 14. For example, thecellular network 18 may include one or more cellular carrier networks electrically coupled to any number of carrier towers having any number of cellular antennas coupled thereto. The cellular carrier network(s) may include such elements as Mobile Telephone or Telecommunications Switch Offices (hereinafter sometimes MTSO), carrier base stations, interconnections operable to couple the various elements of the cellular carrier network, additional towers, antennas, and other communication devices useful in propagating data across thecellular network 18. Additionally, in some embodiments, thecellular network 18 may include portions of the local Public Switch Telephone Network (hereinafter sometimes PSTN). - The
cellular network 18 may use any cellular transmission protocol to facility the cellular communication between theorthopaedic prosthesis 12 and thecontroller 16. For example, in some embodiments, thecellular network 18, or portion thereof, is embodied as an analog wireless network such as an Advanced Mobile Phone Service (hereinafter sometimes AMPS) network, a Narrowband Advanced Mobile Phone Service (hereinafter sometimes NAMPS) network, or other analog wireless network. In such embodiments, theorthopaedic prosthesis 12 and thecontroller 14 are configured to communicate with each other over thecellular network 18 using an analog wireless transmission protocol or technology such as, for example, a Frequency Division Multiple Access (hereinafter sometimes FDMA) transmission protocol. - In other embodiments, the
cellular network 18, or portion thereof, may be embodied as a digital wireless network such as a Global System for Mobile Communications (hereinafter sometimes GSM) network, a Personal Communications Systems (hereinafter sometimes PCS) network, a Digital Advanced Mobile Phone Service (hereinafter sometimes DAMPS) network, or other digital wireless network which, in some implementations, may use, communicate with, or rely on portions of an analog wireless network such as an AMPS network. In the case of a digital network, thecellular network 18 may be embodied as a circuit switched digital wireless network, a packet switched wireless network, or other type of digital wireless network including proprietary digital networks such as the Integrated Digital Enhanced Network (hereinafter sometimes iDEN). In embodiments wherein thecellular network 18 is embodied as or includes such digital wireless networks, theorthopaedic prosthesis 12 and thecontroller 14 are configured to communicate with each other over thecellular network 18 using a digital wireless transmission protocol or technology such as, for example, a Time Division Multiple Access (hereinafter sometimes TDMA) transmission protocol, a Code Division Multiple Access (hereinafter sometimes CDMA) transmission protocol, a Code Division Multiple Access 2000 (hereinafter sometimes CDMA2000) transmission protocol, a Wideband Code Division Multiple Access (hereinafter sometimes WCDMA) transmission protocol, and/or a Time Division-Synchronous Code Division Multiple Access (hereinafter sometimes TD-SCDMA) transmission protocol. - The
controller 14 is coupled to thecellular network 18 via acommunication link 22. Thecommunication link 22 may be embodied as any type and number of communication links capable of facilitating communication between thecontroller 14 and thecellular network 18. Thecommunication link 22 may be embodied as a wired communication link, a wireless communication link, or a combination thereof. For example, thecommunication link 22 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like. - The
controller 14 includes aprocessor 26 and amemory device 28. Theprocessor 26 may be embodied as any type of processor including, for example, discrete circuitry (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs). Thememory device 28 may be embodied as any type of memory device and may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM). In addition, thecontroller 14 may include other devices and circuitry typically found in a computer for performing the functions described herein such as, for example, a hard drive, input/output circuitry, and the like. - The
controller 14 forms a portion of acall center 30. Thecall center 30 may include any number ofcontrollers 14 configured to communicate with theportable computing device 16 and theorthopaedic prosthesis 12. In some embodiments, thecall center 30 may form a portion of a hospital network. Thecall center 30 includes adatabase 32, which may be embodied as any type of database capable of storing orthopaedic prosthesis-related data. Although illustrated inFIG. 1 as a single database, it should be appreciated that thedatabase 32 may be embodied as any number of separate databases, file folders, flat files, or other storage locations. - The orthopaedic prosthesis-related data may include, for example, orthopaedic prosthesis serial numbers, passcodes assigned to individual surgeons, cellular telephone numbers and other contact data, implant sensor data, and/or the like. The orthopaedic prosthesis-related data may be stored in the
database 32 in association with, indexed by, or otherwise retrievable based on each data type. For example, in one particular embodiment, implant serial numbers are stored in association with passcodes assigned to the orthopaedic surgeons or other healthcare providers authorized to monitor the orthopaedic prosthesis identified by the particular implant serial number as discussed in more detail below. Thepatient database 32 may be located at the same location as the controller 14 (e.g., within the same hospital) or may be located remotely therefrom. - The
controller 14 is communicatively coupled to thedatabase 32 via a number of communication links 34. The communication links 34 may be embodied as any type of communications links such as a wired communication link, a wireless communication link, or a combination thereof. For example, thecommunication link 34 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like. - The
controller 14 is also configured to communicate with theportable computing device 16 via anetwork 24. Thenetwork 24 may be embodied as any type of network capable of facilitating communication between theportable computing device 16 and thecontroller 14. For example, thenetwork 24 may be embodied as or include a local area network (LAN), a wide area network (WAN), or may form a portion of a publicly-accessible, global network such as the Internet. In addition, thenetwork 24 may be embodied as a wired network, a wireless network, or a combination thereof. - The
controller 14 is coupled to thenetwork 24 via acommunication link 36. Thecontroller 14 is also coupled to thecellular network 18 via acommunication link 22. The communication links 22, 36 may be embodied as any type of communication links capable of facilitating communication between thecontroller 14 and thecellular network 18 and thenetwork 24, respectively. As such, the communication links 22, 36 may be embodied as any type of communications links such as wired communication links, a wireless communication links, or a combination thereof. For example, thecommunication link - The
portable computing device 16 is configured to communicate with thecontroller 14 over thenetwork 24. Theportable computing device 16 is also communicatively coupled to thenetwork 24 via a number of communication links 38. Similar to the communication links 22, 36, the communication links 38 may be embodied as any type of communications links such as a wired communication link, a wireless communication link, or a combination thereof. For example, thecommunication link 38 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like. - The
portable computing device 16 may be embodied as any type of computing device usable by an orthopaedic surgeon or otherorthopaedic healthcare provider 60 to transmit data to and receive data from thecontroller 14 over thenetwork 24. For example, theportable computing device 16 may be embodied as a Personal Digital Assistant (hereinafter sometimes PDA), a laptop or desktop computer, a PDA mobile phone, and/or similar computing devices suitable for communicating with thecontroller 14 over thenetwork 24 and displaying data to theorthopaedic healthcare provider 60. - The illustrative
portable computing device 16 includes aprocessor 40 and amemory device 42. Theprocessor 40 may be embodied as any type of processor including, for example, discrete circuitry (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs). Thememory device 42 may be embodied as any type of memory device and may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM). In addition, theportable computing device 16 may include other devices and circuitry typically found in a computer for performing the functions described herein such as, for example, a hard drive, input/output circuitry, and the like. For example, theportable computing device 16 may include a transmitter/receiver, network card, modem, and/or the like for communicating with thecontroller 14 over thenetwork 24. - In use, the
orthopaedic healthcare provider 60 may operate theportable computing device 16 to monitor implant sensor data generated by theorthopaedic prosthesis 12 and/or update programming of theorthopaedic prosthesis 12 as described in more detail below in regard toFIGS. 3-5 . To do so, the orthopaedic healthcare provider may enter an implant serial number and a passcode into theportable computing device 16, which is subsequently transmitted to thecontroller 14 via thenetwork 24. The implant serial number may be embodied as any type of data that uniquely identifies theorthopaedic prosthesis 12 from other orthopaedic prostheses used in thesystem 10. As such, the implant serial number may include any number and type of characters including numeric characters and alphabetic characters. In one particular embodiment, the implant serial number is identical to, based on, or otherwise derived from a cellular telephone or access number associated with theorthopaedic prosthesis device 12. Similarly, the passcode may be embodied as any type of data that identifies theorthopaedic healthcare provider 60. The passcode may be unique to theorthopaedic healthcare provider 60 or to some other entity such as a hospital, a group of orthopaedic healthcare providers, or the like. - Once the
controller 14 receives the implant serial number and passcode from theportable computing device 16, thecontroller 14 verifies that the orthopaedic surgeon or healthcare provider associated with the passcode is authorized to communicate with theorthopaedic prosthesis 12 identified by the implant serial number. To do so, thecontroller 14 may retrieve data, such as a look-up table, from thedatabase 32 and compare the passcode and implant serial number to the retrieved data. If the user identified by the passcode is authorized to communicate with the orthopaedic prosthesis sensor, thecontroller 14 initiates cellular communication with theorthopaedic prosthesis 12 and receives implant sensor data transmitted from theorthopaedic prosthesis 12 over thecellular network 18. - The
controller 14 subsequently transmits the implant sensor data to theportable computing device 16 via thenetwork 24. The implant sensor data, or indicia thereof such as a graph, chart, or the like, is displayed to theorthopaedic healthcare provider 60 via a display device or the like of theportable computing device 16. In addition, theorthopaedic healthcare provider 60 may operate theportable computing device 16 to supply programming data to theorthopaedic prosthesis 12 via thecellular network 18. The programming data is used by theorthopaedic prosthesis 12 to update a program executed by electronic circuitry of theorthopaedic prosthesis 12. Additionally or alternatively, in some embodiments as discussed in more detail below in regard toFIGS. 6-8 , theorthopaedic prosthesis 12 may be configured to initiate cellular communication with thecontroller 14 based on a predetermined condition such as the value(s) of the implant sensor data. - Referring now to
FIG. 2 , theorthopaedic prosthesis 12 includeselectronic circuitry 100 coupled to or otherwise housed therein. Theelectronic circuitry 100 includes aprocessor 102, one ormore implant sensors 104, and a cellular transmitter and/or receiver (e.g., a cellular transceiver) 106. Theprocessor 102 is coupled to the sensor(s) 104 via a number ofcommunication links 108 and to the cellular transmitter/transceiver 106 via a number of communication links 110. The communication links 108, 110 may be embodied as or otherwise include any number of wires, cables, printed circuit board traces, vias, and/or the like. - The
processor 102 may be embodied as any type of processor capable of receiving implant sensor data from the implant sensor(s) 104 and transmitting the implant sensor data over thecellular network 18 using the cellular transmitter/transceiver 106. For example, theprocessor 102 may be embodied as, or otherwise include discrete processing circuits (e.g., a collection of logic devices), general purpose integrated circuit(s), and/or application specific integrated circuit(s) (i.e., ASICs). - The
electronic circuitry 100 may include any number ofimplant sensors 104. The implant sensor(s) 104 may be embodied as any type of implant sensor configured to generate implant sensor data of a parameter of interest. For example, the implant sensor(s) 104 may be embodied as a pressure sensor, a load sensor, a temperature sensor, a hall-effect sensor, or the like. The implant sensor data is transmitted to theprocessor 102 via the communication links 108. - As discussed above, the
cellular transmitter 106 may be embodied as any transmitter or transceiver configured to transmit and/or receive data over thecellular network 18. That is, thecellular transmitter 106 is configured to transmit and/or receive data using a wireless carrier frequency and communication protocol/technology supported or otherwise used by thecellular network 18. As such, thecellular transmitter 106 may include any number of circuits and electronic devices (e.g., a cellular antenna) and, in some embodiments, may be similar to the cellular transmitters/transceivers used in typical cellular telephones and other cellular communication devices. - The
electronic circuitry 100 also includes amemory device 112. Thememory device 112 is communicatively coupled to theprocessor 102 via a number of communication links 114. Similar tocommunication links memory device 12 may be embodied as any type of memory device capable of storing implant sensor data and, in some embodiments, programming or software code. Thememory device 12 may include one or more memory types, such as, random access memory (i.e., RAM) and/or read-only memory (i.e., ROM). - The
processor 102 and other devices of theelectronic circuitry 100 receive power from apower source 116. Thepower source 116 may be embodied as any type of power source capable of supplying power to the other devices of theelectronic circuitry 100 sufficient to perform the functions described herein. Thepower source 116 may be a rechargeable power source or may be a permanent, continuous power source. For example, thepower source 116 may be embodied as an implant battery, an inductively charged battery, a radio frequency (RF) charged battery, a vibration charged power source, a piezoelectric power source, a thin-film, battery, a thermal power source, an acoustic power source, and/or the like. - In use, the
processor 102 may be configured to receive implant sensor data from the implant sensor(s) 104 and transmit the implant sensor data to thecontroller 14 over thecellular network 18 in response to a signal received from thecontroller 14. Additionally or alternatively, theprocessor 102 may be configured to store the implant sensor data in thememory device 112 and subsequently retrieve the stored implant sensor data for transmission to thecontroller 14 via thecellular network 18. Additionally, in some embodiments, theprocessor 102 is configured to execute a program stored in or otherwise defined by data stored in thememory device 112. The program or data may be embodied as software/firmware code executed by the processor and/or other data such as variable data used by a program executed by theprocessor 102. In such embodiments, theprocessor 102 may be configured to update the program stored in thememory device 112 with, based on, or using programming data received from thecontroller 106 via thecellular network 18. - In operation, the portable computing device 16 (i.e., the processor 40) of the
system 10 may execute analgorithm 200 for monitoring orthopaedic prosthesis data as illustrated inFIG. 3 . Thealgorithm 200 begins with aprocess step 202 in which the orthopaedic healthcare provider 60 (e.g., an orthopaedic surgeon) supplies the implant serial number associated with theorthopaedic prosthesis 12 of interest and the passcode associated with theorthopaedic healthcare provider 60. As discussed above in regard toFIG. 1 , the implant serial number may be embodied as any type of data that uniquely identifies theorthopaedic prosthesis 12 from other orthopaedic prostheses and the passcode may be embodied as any type of data that identifies theorthopaedic healthcare provider 60. - The surgeon may supply the implant serial number and passcode via manually typing in the data or otherwise operating the
portable computing device 16 such that the implant serial number and passcode are transmitted to thecontroller 14. In one particular embodiment, theorthopaedic healthcare provider 60 is prompted for the implant serial number and passcode (e.g., via a data field) once theorthopaedic healthcare provider 60 has initiated communication with thecontroller 14 over thenetwork 24. Once the user has entered or otherwise supplied the implant serial number and passcode via theportable computing device 16, the implant serial number and passcode are transmitted from theportable computing device 16 to thecontroller 14 via thenetwork 24 andcommunication links process step 204. - Subsequently, the
processor 40 of theportable computing device 16 determines if theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12 in process steps 206, 208, respectively. To do so, theorthopaedic healthcare provider 60 may be prompted to choose which function theorthopaedic healthcare provider 60 would like to perform. Alternatively, both functions may be accessible by theorthopaedic healthcare provider 60 at any time. As such, it should be appreciated that the process steps 206, 208 may be executed in a sequential order or contemporaneously with each other. - If the
processor 40 determines that theorthopaedic healthcare provider 60 desires to monitor implant sensor data inprocess step 206, thealgorithm 200 advances to processstep 210. Inprocess step 210, theportable computing device 16 receives implant sensor data from theorthopaedic prosthesis 12 via thecellular network 18, thecontroller 14, and thenetwork 24. The implant sensor data may be current implant sensor data and/or historical implant sensor data generated over a period of time. Subsequently, inprocess step 212, the received implant sensor data or indicia thereof is displayed to theorthopaedic healthcare provider 60 on a display screen, monitor, or other display device of theportable computing device 16. For example, the implant sensor data may be displayed in numerical form, in a graph, in a chart, or the like. As such, theorthopaedic healthcare provider 60 may monitor any parameter of interest that is measured by one or more of theimplant sensors 104 in near-real time and/or monitor historic implant sensor data generated therefrom. - Referring back to
process step 208, if theprocessor 40 determines that theorthopaedic healthcare provider 60 desires to update the programming of theorthopaedic prosthesis 12, programming data is received from theorthopaedic healthcare provider 60 inprocess step 214. Theorthopaedic healthcare provider 60 may supply the programming data by manually typing in the data into theportable computing device 16 and/or by supplying the data on a readable media such as a diskette, a compact disc read only memory (CD ROM) media, digital video disk (DVD) media, universal serial bus (USB) flashdrive, or the like. In such embodiments, theportable computing device 16 includes a suitable media player such as a “floppy” disk drive, a CD ROM drive, a DVD drive, or the like. - The programming data may be embodied as any type of programming data usable by the
electronic circuitry 100 of theorthopaedic prosthesis 12. For example, the programming data may be embodied as software/firmware code that is configured to be executed by theprocessor 102 of theorthopaedic prosthesis 12. Additionally, or alternatively, the programming data may be embodied as variable data configured to be used by a program executed by theprocessor 102. In addition, the programming data may be used by theelectronic circuitry 100 to alter, change, or affect any function of theelectronic circuitry 100. For example, the program data may alter the sampling rate used by theprocessor 102 to sample the implant sensor data generated by the implant sensor(s) 104, to alter threshold values or tolerance ranges, to alter communication protocols used by the cellular transmitter/transceiver 106, and/or any other device or function of theelectronic circuitry 100. - Once the
orthopaedic healthcare provider 60 has provided the programming data inprocess step 214, the programming data is transmitted to thecontroller 14 inprocess step 216. The programming data is transmitted to thecontroller 14 via the communication links 36, 38 and thenetwork 24. - Referring now to
FIGS. 4A-B , thecontroller 14 of thecall center 30 is configured to execute analgorithm 300 for communicating with anorthopaedic prosthesis 12 over thecellular network 18 during the operation of thesystem 10. Thealgorithm 300 beings with aprocess step 302 in which the implant serial number and the passcode are received from theportable computing device 16 via thenetwork 24. Next, inprocess step 304, thecontroller 14 determines if the implant serial number and passcode are valid. To do so, thecontroller 14 may retrieve data from the database and compare the retrieved data to the implant serial number and/or the passcode. Such a comparison may include any number of comparison steps. For example, thecontroller 14 may compare the received implant serial number to a list of implant serial numbers to verify that the received implant serial number is a valid implant serial number. Additionally, thecontroller 14 may compare the received passcode to a list of passcodes to verify that the received passcode is a valid passcode. Yet further, thecontroller 14 may retrieve a “look-up” table or the like, which relates passcodes to authorized implant serial numbers, from thedatabase 32. If so, thecontroller 14 may compare the received implant serial number and passcode to the “look-up” table to verify that the orthopaedic healthcare provider identified by the received passcode is authorized to communicate with the orthopaedic prosthesis identified by the received implant serial number. Additionally, thecontroller 14 may use other algorithms and security measures to ensure the identity of theorthopaedic healthcare provider 60 and appropriate authorization. - If the implant serial number and/or passcode are not valid, the
algorithm 300 loops back to process step 302 wherein thecontroller 14 waits to receive a new implant serial number and/or passcode. However, if thecontroller 14 determines that the implant serial number and passcode are valid inprocess step 304, thealgorithm 300 advances to processstep 306 in which thecontroller 14 retrieves contact data associated with theorthopaedic prosthesis 12 identified by the implant serial number from thedatabase 32. The contact data may be embodied as any type of data with which thecontroller 14 may initiate cellular communication with theorthopaedic prosthesis 12. For example, in one embodiment, the contact data may be embodied as or may be based on a cellular telephone number or cellular access number of theorthopaedic prosthesis 12. Thecontroller 14 may retrieve the contact data by, for example, retrieving a “look-up” table from thedatabase 32 that indexes implant serial numbers to associated contact data. Thecontroller 14 may then determine the appropriate contact data based on the received implant serial number. Alternatively, in some embodiments the implant serial number is embodied as the contact data. For example, the implant serial number may be embodied as the cellular telephone or access number of theorthopaedic prosthesis 12. In such embodiments, theprocess step 306 may be skipped. - Once the
controller 14 has retrieved the contact data for the appropriateorthopaedic prosthesis 12 from thedatabase 32, thecontroller 14 initiates cellular communication with theorthopaedic prosthesis 12 inprocess step 308. To do so, thecontroller 14 is configured to establish a cellular connection with the orthopaedic prosthesis 12 (via the cellular transmitter/transceiver 106) over thecellular network 18 using the contact data. For example, thecontroller 14 may transmit the appropriate data to thecellular network 18 to facilitate the cellular connection. In addition, thecontroller 14 and theorthopaedic prosthesis 12 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween. - Once the
controller 14 has initiated cellular communication with theorthopaedic prosthesis 12, thecontroller 14 is configured to transmit the received implant serial number to theorthopaedic prosthesis 12. To do so, thecontroller 14 transmits the received implant serial number over thecellular network 18 via the communication links 20, 22. Subsequently, thecontroller 14 determines if theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12 in process steps 312, 314, respectively. - The
controller 14 may determine if theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12 based on, for example, data or signals received from theportable computing device 16 and/or from theorthopaedic prosthesis 12. For example, thecontroller 14 may determine that theorthopaedic healthcare provider 60 desires to monitor implant sensor data if implant sensor data is received from theorthopaedic prosthesis 12. Alternatively, thecontroller 14 may determine that theorthopaedic healthcare provider 60 desires to update the programming of the orthopaedic prosthesis if programming data is received form theportable computing device 16. Additionally or alternatively, theportable computing device 16 may be configured to transmit a signal or data to thecontroller 14 to inform thecontroller 14 that theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12. As such, thecontroller 14 may use any one or more of a number of methods to determine which one or more functions to perform. - If the
controller 14 determines that theorthopaedic healthcare provider 60 desires to monitor the implant sensor data inprocess step 312, thealgorithm 300 advances to processstep 313 in which thecontroller 14 transmits a signal to theorthopaedic prosthesis 12 instructing the prosthesis to begin transmitting the implant sensor data. Subsequently, inprocess step 316, thecontroller 14 receives implant sensor data from theorthopaedic prosthesis 12 via thecellular network 18. In response to receipt of the implant sensor data, thecontroller 14 is configured to transmit the implant sensor data to theportable computing device 16 via thenetwork 24. - Referring back to
process step 314, if thecontroller 14 determines that theorthopaedic healthcare provider 60 desires to update the programming of theorthopaedic prosthesis 12 inprocess step 314, the algorithm advances to processstep 315 in which thecontroller 14 transmits a signal to theorthopaedic prosthesis 12 to prepare for a programming update. Subsequently, inprocess step 320, thecontroller 14 transmits the programming data to theorthopaedic prosthesis 12. To do so, thecontroller 14 transmits the programming data over thecellular network 18 via the communication links 20, 22. Once thecontroller 14 has transmitted the implant sensor data to theportable computing device 16 and/or transmitted the programming data to theorthopaedic prosthesis 12, thealgorithm 300 loops back to process step 302 wherein thecontroller 14 waits to receive a new implant serial number and/or passcode. - Referring now to
FIG. 5 , theorthopaedic prosthesis 12 of thesystem 10 is configured to execute analgorithm 400 for communicating with thecontroller 14 over thecellular network 18. Thealgorithm 400 begins with aprocess step 402 in which theorthopaedic prosthesis 12 initializes cellular communication with thecontroller 14 of thecall center 30. As discussed above in regard to process step 308 ofalgorithm 300, thecontroller 14 is configured to initiate cellular communication with theorthopaedic prosthesis 12 in the illustrative embodiment. As such, inprocess step 402, the orthopaedic prosthesis 12 (i.e., the electronic circuitry 100) may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication with thecontroller 14 inprocess step 402. - Once the cellular communication with the
controller 14 has been initialized or otherwise established inprocess step 402, theorthopaedic prosthesis 12 receives the implant serial number from thecontroller 14 inprocess step 404. Inprocess step 406, theprocessor 102 is configured to determine if the received implant serial number is valid. To do so, in one embodiment, theprocessor 102 is configured to retrieve an implant serial number associated with theimplant 12 from thememory device 112. Theprocessor 102 compares the retrieved implant serial number with the implant serial number received from thecontroller 14 to determine if the implant serial numbers are equal or otherwise match within some predetermined amount of tolerance. In this way, theprocessor 102 ensures that thecontroller 14 has initiated cellular communication with the correctorthopaedic prosthesis 12. If theprocessor 102 determines that the received implant serial number is not valid, thealgorithm 400 loops back to process step 402 wherein theelectronic circuitry 100 of theorthopaedic prosthesis 12 waits for the initiation of a new cellular communication from thecontroller 14. - If, however, the
processor 102 determines that the received implant serial number is valid inprocess step 406, thealgorithm 400 advances to processsteps processor 102 determines if theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theelectronic circuitry 100, respectively. Theprocessor 102 may determine if theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12 based on, for example, data or signals received from thecontroller 14. For example, theprocessor 102 may determine that theorthopaedic healthcare provider 60 desires to update the programming of theorthopaedic prosthesis 12 if programming data is received from thecontroller 14. Additionally or alternatively, thecontroller 14 may be configured to transmit a signal or data to theorthopaedic prosthesis 12 to inform theprocessor 102 that theorthopaedic healthcare provider 60 desires to monitor implant sensor data and/or update the programming of theorthopaedic prosthesis 12. As such, theorthopaedic prosthesis 12 may use any one or more of a number of methods to determine which one or more functions to perform. - If the
processor 102 determines that the orthopaedic healthcare provider desires to monitor implant sensor data instep 408, thealgorithm 400 advances to processstep 412. Inprocess step 412, theprocessor 102 is configured to transmit the current implant sensor data received from the implant sensor(s) 104 to thecontroller 14. To do so, theprocessor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the implant sensor data over thecellular network 18. The implant sensor data may be transmitted in any suitable form. For example, the implant sensor data may be transmitted in compressed or non-compressed form to thecontroller 14. - Subsequently, in
process step 416, theprocessor 102 determines if any stored implant sensor data should be transmitted to thecontroller 14. To do so, theprocessor 102 may be programmed or otherwise configured to transmit or not transmit the stored implant sensor data. Additionally or alternatively, theprocessor 102 may be configured to access or otherwise retrieve data from thememory device 112 and determine if the stored implant sensor data should be transmitted based on such data (e.g., based on the value of the retrieved data). In this way, theorthopaedic prosthesis 12 may be programmed to transmit stored data or not to transmit stored data depending on the particular application and/or implementation of thesystem 10 and/or theorthopaedic prosthesis 12. - If the
processor 102 determines that any stored implant sensor data should not be transmitted inprocess step 416, thealgorithm 400 loops back to process step 402 wherein theelectronic circuitry 100 of theorthopaedic prosthesis 12 waits for the initiation of a new cellular communication from thecontroller 14. If, however, theprocessor 102 determines that the implant sensor data stored in thememory device 112 should also be transmitted, thealgorithm 400 advances to processstep 418. Inprocess step 418, the implant sensor data stored in thememory device 112 is retrieved. The retrieved implant sensor data is subsequently transmitted to thecontroller 14 inprocess step 420. To do so, theprocessor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the retrieved implant sensor data over thecellular network 18. Again, the implant sensor data retrieved from thememory device 112 may be transmitted to thecontroller 14 in any suitable form including, for example, compressed or non-compressed form. Once the retrieved implant sensor data has been transmitted to thecontroller 14 inprocess step 420, thealgorithm 400 loops back to process step 402 wherein theelectronic circuitry 100 of theorthopaedic prosthesis 12 waits for the initiation of a new cellular communication from thecontroller 14. - Referring back to
process step 410, if theprocessor 410 determines that orthopaedic healthcare provider desires to update the programming of theelectronic circuitry 100, thealgorithm 400 advances to processstep 422. Inprocess step 422,processor 102 receives programming data from thecontroller 14 over thecellular network 18 using the cellular transmitter/transceiver 106. Subsequently, inprocess step 424, theprocessor 102 is configured to update one or more programs or programming data used by theelectronic circuitry 100 using the received programming data depending on, for example, the type of programming data received. For example, in embodiments wherein the programming data is embodied as software/firmware code, theprocessor 102 may be configured to store the programming data in thememory device 112 and subsequently begin executing the software/firmware code. - In such embodiments, the
electronic circuitry 100 may require a “reboot” or otherwise re-initialization to begin executing the new programming code. In other embodiments wherein the programming data is embodied as variable data, theprocessor 102 may be configured to store the programming data in thememory device 112 such that the programming data overwrites existing data stored therein. In this way, the programming data may alter, change, or update old variable data used by the software and/or firmware executed by theelectronic circuitry 100. For example, a data variable indicating if theprocessor 102 should transmit stored implant sensor data may be stored in thememory device 112 in a known memory location. In such embodiments, theprocessor 102 is configured to analyze the stored data variable to determine whether to transmit stored implant data. As such, the programming of theorthopaedic prosthesis 12 may be altered, changed, or updated by transmitting a new data value to replace the data variable stored in thememory device 112. Regardless, once theprocessor 102 has updated the programming of theorthopaedic device 12 with the programming data received from thecontroller 14, theorthopaedic prosthesis 12 transmits a confirmation signal to thecall center 30 to confirm that the programming of theorthopedic prosthesis 12 is complete inprocess step 426. Subsequently, thealgorithm 400 loops back to process step 402 wherein theelectronic circuitry 100 of theorthopaedic prosthesis 12 waits for the initiation of a new cellular communication from thecontroller 14. - Referring now to
FIGS. 6-8 , in some embodiments, theorthopaedic prosthesis 12 may be configured to initiate cellular communication with thecontroller 14 if one or more predetermined conditions occur. In such embodiments, theprocessor 102 of theorthopaedic prosthesis 12 may be configured to execute analgorithm 500 for communicating with thecontroller 14 over thecellular network 18 as illustrated inFIG. 6 . Thealgorithm 500 beings with aprocess step 502 in which theprocessor 102 determines if the value of the implant sensor data received from any one or more of theimplant sensors 104 is out of a tolerance range and/or above or below a predetermined threshold level. For example, if therelevant implant sensor 104 is a pressure sensor configured to generate pressure data, theprocessor 102 may be configured to determine if the pressure data is above some predetermined maximum allowable pressure value and/or below some predetermined minimum allowable pressure value. To do so, theprocessor 102 may compare the pressure data received from theimplant sensor 104 to a value or values stored in thememory device 112. In such embodiments, the value or values stored in thememory device 112 form a portion of the programming data of theorthopaedic device 12 and, as such, may be changed, altered, or otherwise updated as discussed in detail above in regard toFIGS. 3-5 . - If the
processor 102 determines that the implant sensor data received from the implant sensor(s) 104 is out of the predetermined tolerance range and/or above or below a predetermined threshold value inprocess step 502, thealgorithm 500 advances to processstep 504. Inprocess step 504, theorthopaedic prosthesis 12 initiates cellular communication with thecontroller 14. To do so, theorthopaedic prosthesis 12 is configured to establish a cellular connection with thecontroller 14 via use of the cellular transmitter/transceiver 106. For example, theorthopaedic prosthesis 12 may transmit the appropriate data to thecellular network 18 to facilitate the cellular connection. In addition, theorthopaedic prosthesis 12 and thecontroller 14 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween. - Once the
orthopaedic prosthesis 12 has initiated cellular communication with thecontroller 14, theorthopaedic prosthesis 12 is configured to transmit the implant serial number associated with theorthopaedic prosthesis 12 inprocess step 506. To do so, theprocessor 102 may be configured to retrieve the implant serial number from thememory device 112 and transmit the implant serial number over thecellular network 18 via the communication links 20, 22. Subsequently, inprocess step 508, theprocessor 102 is configured to transmit the implant sensor data received from the implant sensor(s) 104 to thecontroller 14. To do so, theprocessor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the implant sensor data over thecellular network 18. As discussed above, the implant sensor data may be transmitted in any suitable form. For example, the implant sensor data may be transmitted in compressed or non-compressed form to thecontroller 14. Subsequently, inprocess step 509, theprocessor 102 determines if theorthopaedic prosthesis 12 should continue to send current implant data to thecontroller 14. If so, thealgorithm 500 loops backprocess step 508 in which the current implant sensor data is transmitted to thecontroller 14 as described above. In this way, theprocessor 102 may transmit a stream of current implant data to thecontroller 14. Theorthopaedic prosthesis 12 may be instructed to continue sending the current implant data by a signal received from thecontroller 14, based on a predetermined transmission time, or a programmable flag or data value. If theprocessor 102 determines that theorthopaedic prosthesis 12 should continue sending the orthopaedic implant sensor data inprocess step 509, thealgorithm 500 advances to processstep 510. - In
process step 510, theprocessor 102 determines if any stored implant sensor data should be transmitted to thecontroller 14. To do so, theprocessor 102 may be programmed or otherwise configured to transmit or not transmit the stored implant sensor data. Additionally or alternatively, theprocessor 102 may be configured to access or otherwise retrieve data from thememory device 112 and determine if the stored implant sensor data should be transmitted based on such data (e.g., based on the value of the retrieved data). - If the
processor 102 determines that any stored implant sensor data should not be transmitted inprocess step 510, thealgorithm 500 loops back to process step 502 wherein theprocessor 102 of theorthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 is within the predetermined tolerance range. If, however, theprocessor 102 determines that the implant sensor data stored in thememory device 112 should also be transmitted, thealgorithm 500 advances to processstep 512. Inprocess step 512, theprocessor 102 retrieves the implant sensor data from thememory device 112. The retrieved implant sensor data is subsequently transmitted to thecontroller 14 inprocess step 514. To do so, theprocessor 102 is configured to control the cellular transmitter/transceiver 106 to transmit the retrieved implant sensor data over thecellular network 18. Again, the implant sensor data retrieved from thememory device 112 may be transmitted to thecontroller 14 in any suitable form including, for example, compressed or non-compressed form. Once the retrieved implant sensor data has been transmitted to thecontroller 14 inprocess step 514, thealgorithm 500 loops back to process step 502 wherein theprocessor 102 of theorthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 are within the predetermined tolerance range. - Referring back to
process step 502, if the processor determines that the implant sensor data received from implant sensor(s) 104 is within the predetermined tolerance range, thealgorithm 500 advances to processstep 516. Inprocess step 516, theprocessor 102 determines if there is any incoming cellular communication from thecontroller 104. To do so, theprocessor 102 may monitor the data output of the cellular transmitter/transceiver 106. If theprocessor 102 determines that there is no incoming cellular communication, thealgorithm 500 loops back to process step 502 wherein theprocessor 102 of theorthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 are within the predetermined tolerance range. - However, if the
processor 102 determines that there is incoming cellular communication from thecontroller 14 inprocess step 516, thealgorithm 500 advances to processstep 518. Inprocess step 518, the processor is configured to communicate with thecontroller 14 of thecall center 30 over thecellular network 18. Inprocess step 516, the processor may transmit implant sensor data, including stored implant sensor data in some embodiments, to thecontroller 14 over thecellular network 18 and/or receive programming data from thecontroller 14 over thecellular network 18. As such, it should be appreciated that the processor may execute an algorithm similar to thealgorithm 400 illustrated in and discussed above in regard toFIG. 5 inprocess step 518. For example, theprocessor 102 may be configured to receive an implant serial number fromcontroller 14, determine the validity of the implant serial number, transmit current and stored implant sensor data to thecontroller 14, receive programming data from thecontroller 14, and/or update the programming of theorthopaedic device 12 using the programming data inprocess step 518. Once theprocessor 102 has communicated with thecontroller 14 inprocess step 518, thealgorithm 500 loops back to process step 502 wherein theprocessor 102 of theorthopaedic prosthesis 12 determines if the implant sensor data received from the implant sensor(s) 104 is within the predetermined tolerance range. - Referring now to
FIG. 7 , in embodiments wherein theorthopaedic prosthesis 12 is also configured to initiate cellular communication with thecontroller 14, thecontroller 14 may execute analgorithm 600 for communicating with anorthopaedic prosthesis 12 over thecellular network 18. Thealgorithm 600 beings with aprocess step 602 in which thecontroller 14 determines if there is incoming cellular communication from theorthopaedic prosthesis 12. If so, thealgorithm 600 advances to processstep 604 wherein thecontroller 14 is configured to initialize cellular communication with theorthopaedic prosthesis 12. To do so, thecontroller 14 may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication with theorthopaedic prosthesis 12. - Once the
controller 14 has initialized cellular communication with theorthopaedic prosthesis 12 inprocess step 604, thecontroller 14 is configured to receive an implant serial number from theorthopaedic prosthesis 12 over thecellular network 18 inprocess step 606. In addition, inprocess step 608, thecontroller 14 receives implant sensor data from theorthopaedic prosthesis 12 via thecellular network 18. In some embodiments, thecontroller 14 may be configured to store the implant serial number and/or the implant sensor data in thememory device 28 and/or thedatabase 32. - Once the
controller 14 has received the implant serial number and sensor data, thecontroller 14 is configured to retrieve contact information associated with theportable computing device 16 based on the received implant serial number inprocess step 610. The contact information may be embodied as any type of data with which thecontroller 14 may initiate communication with theportable computing device 16 over thenetwork 24. For example, in one embodiment, the contact information may be embodied as or be based on an internet protocol (IP) address or a cellular telephone or access number of theportable computing device 16. Additionally, in some embodiments, the contact information may be embodied as or include an e-mail address or the like. Thecontroller 14 may retrieve the contact information by, for example, retrieving a “look-up” table from thedatabase 32 that indexes implant serial numbers to associated contact information. Thecontroller 14 may then determine the appropriate contact information based on the received implant serial number. - Once the
controller 14 has retrieved the contact information for the appropriateportable computing device 16 from thedatabase 32, thecontroller 14 initiates network communication with theportable computing device 16 inprocess step 612. To do so, thecontroller 14 is configured to establish a network connection with theportable computing device 16 over thenetwork 24 using the contact information. For example, thecontroller 14 may transmit the appropriate data to thenetwork 24 to facilitate the network connection. In addition, thecontroller 14 and theportable computing device 16 may perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the cellular communication therebetween. - Once the
controller 14 has initiated communication with theportable computing device 16, thecontroller 14 is configured to transmit the received implant sensor data to theportable computing device 16 inprocess step 614. To do so, thecontroller 14 transmits the received implant sensor data over thenetwork 24 via the communication links 36, 38. Once thecontroller 14 has transmitted the implant sensor data to theportable computing device 16, thealgorithm 600 loops back to theprocess step 602 wherein thecontroller 14 is configured to determine if there is any new cellular communication incoming from theorthopaedic prosthesis 12. - Referring back to
process step 602, if thecontroller 14 determines that there is no incoming cellular communication from theorthopaedic prosthesis 12, thealgorithm 600 advances to processstep 616. Inprocess step 616, thecontroller 14 determines if there is any incoming communication from theportable computing device 16. If thecontroller 14 determines that there is no incoming communication, thealgorithm 600 loops back to theprocess step 602 wherein thecontroller 14 is configured to determine if there is any new cellular communication incoming from theorthopaedic prosthesis 12. - However, if the
controller 14 determines that there is incoming communication from theportable computing device 16 inprocess step 616, thealgorithm 600 advances to processstep 618. Inprocess step 618, thecontroller 14 is configured to communicate with theportable computing device 16 over thenetwork 24 and/or theorthopaedic prosthesis 12 over thecellular network 24. Inprocess step 618, thecontroller 14 receives implant serial numbers and passcodes from theportable computing device 16, receives implant sensor data from theorthopaedic prosthesis 12, and/or transmits implant sensor data to theportable computing device 16 over thenetwork 24. As such, it should be appreciated that thecontroller 14 may execute a sub-algorithm similar to thealgorithm 300 illustrated in and discussed above in regard toFIGS. 4A-B inprocess step 618. For example, thecontroller 14 may be configured to receive an implant serial number and passcode from theportable computing device 16, validate the implant serial number and passcode, receive programming data from theportable computing device 16, initiate cellular communication with theorthopaedic prosthesis 12, receive implant sensor data from theorthopaedic prosthesis 12, transmit the implant sensor data to theportable computing device 16, and/or transmit the programming data to theorthopaedic prosthesis 12 inprocess step 618. Once thecontroller 14 has communicated with theportable computing device 16 and/ororthopaedic prosthesis 12 inprocess step 618, thealgorithm 600 loops back to process step 602 wherein thecontroller 14 is configured to determine if there is any new cellular communication incoming from theorthopaedic prosthesis 12. - Referring now to
FIG. 8 , in embodiments wherein theorthopaedic prosthesis 12 is also configured to initiate cellular communication with thecontroller 14, theportable computing device 16 may execute analgorithm 700 for monitoring orthopaedic prosthesis data. Thealgorithm 700 beings with aprocess step 702 in which thecontroller 14 determines if there is incoming communication from thecontroller 14. If so, thealgorithm 700 advances to processstep 704 wherein theportable computing device 16 is configured to initialize network communication with thecontroller 14. To do so, theportable computing device 16 may be configured to perform any number of initialization steps, “handshaking” steps, or the like to initialize or otherwise establish the network communication with thecontroller 14. - Once the communication has been established with the
controller 14, theportable computing device 16 receives implant sensor data from thecontroller 14 inprocess step 706. As discussed above, the implant sensor data may be current implant sensor data and/or historical implant sensor data generated over a period of time. Subsequently, inprocess step 708, the received implant sensor data or indicia thereof is displayed to theorthopaedic healthcare provider 60 on a display screen, monitor, or other display device of theportable computing device 16. For example, the implant sensor data may be displayed in numerical form, in a graph, in a chart, or the like. As such, theorthopaedic healthcare provider 60 may be automatically and/or promptly notified if a problem has occurred with theorthopaedic prosthesis 12 as defined by the implant sensor data. Theorthopaedic healthcare provider 60 may then subsequently monitor the performance of theorthopaedic prosthesis 12 via the implant sensor data received from thecontroller 14 and displayed on theportable computing device 16. - In
process step 709, theportable computing deice 16 determines if theorthopaedic healthcare provider 60 desires to disconnect from the call center 30 (i.e., stop receiving implant sensor data). If so, thealgorithm 700 loops back toprocess step 702 in which theportable communication device 16 again monitors for any incoming communication from thecall center 30. However, if theorthopaedic healthcare provider 60 desires to continue receiving orthopaedic prosthesis data, thealgorithm 700 loops back toprocess step orthopedic healthcare provider 60. - Referring back to
process step 702, if theportable computing device 16 determines that there is no incoming network communication from thecontroller 14, thealgorithm 700 advances to processstep 710. Inprocess step 710, theportable computing device 16 determines if theorthopaedic healthcare provider 60 desires to interact with the orthopaedic prosthesis 12 (e.g., monitor implant sensor data and/or update the programming of the implant 12). If theportable computing device 16 determines thatorthopaedic healthcare provider 60 does not desire to interact with theorthopaedic prosthesis 12, thealgorithm 700 loops back to theprocess step 702 wherein theportable computing device 16 is configured to determine if there is any new network communication incoming from thecontroller 14. - However, if the
portable computing device 16 determines that theorthopaedic healthcare provider 60 desires to interact with theorthopaedic prosthesis 12 inprocess step 710, thealgorithm 700 advances to processstep 712. Inprocess step 712, theportable computing device 16 is configured to communicate with thecontroller 14 of thecall center 30 over thenetwork 24. Inprocess step 712, theportable computing device 16 is configured to transmit an implant serial number, passcode, and/or programming data to thecontroller 14, receive implant sensor data from thecontroller 14, and display the implant sensor data to theorthopaedic healthcare provider 60. As such, it should be appreciated that theportable computing device 16 may execute a sub-algorithm similar to thealgorithm 200 illustrated in and discussed above in regard toFIG. 3 inprocess step 712. For example, theportable computing device 16 may be configured to receive an implant serial number and passcode from theorthopaedic healthcare provider 60, receive programming data from theorthopaedic healthcare provider 60, transmit the implant serial number, the passcode, and the programming data to thecontroller 14, receive implant sensor data form thecontroller 14, and display the implant sensor data to theorthopaedic healthcare provider 60 inprocess step 712. Once theportable computing device 16 has communicated with thecontroller 14 inprocess step 712, thealgorithm 700 loops back to process step 702 wherein theportable computing device 16 is configured to determine if there is any new network communication incoming from thecontroller 14. - While the disclosure has been illustrated and described in detail in the drawings and foregoing description, such an illustration and description is to be considered as exemplary and not restrictive in character, it being understood that only illustrative embodiments have been shown and described and that all changes and modifications that come within the spirit of the disclosure are desired to be protected.
- There are a plurality of advantages of the present disclosure arising from the various features of the systems and methods described herein. It will be noted that alternative embodiments of the systems and methods of the present disclosure may not include all of the features described yet still benefit from at least some of the advantages of such features. Those of ordinary skill in the art may readily devise their own implementations of the systems and methods that incorporate one or more of the features of the present invention and fall within the spirit and scope of the present disclosure as defined by the appended claims.
Claims (19)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/189,712 US20140313053A1 (en) | 2006-09-29 | 2014-02-25 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/537,338 US8685091B2 (en) | 2006-09-29 | 2006-09-29 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
US14/189,712 US20140313053A1 (en) | 2006-09-29 | 2014-02-25 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/537,338 Division US8685091B2 (en) | 2006-09-29 | 2006-09-29 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140313053A1 true US20140313053A1 (en) | 2014-10-23 |
Family
ID=38896858
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/537,338 Active 2030-07-20 US8685091B2 (en) | 2006-09-29 | 2006-09-29 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
US14/189,712 Abandoned US20140313053A1 (en) | 2006-09-29 | 2014-02-25 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/537,338 Active 2030-07-20 US8685091B2 (en) | 2006-09-29 | 2006-09-29 | System, method, and device for monitoring orthopaedic implant data over a cellular network |
Country Status (5)
Country | Link |
---|---|
US (2) | US8685091B2 (en) |
EP (1) | EP1905388B1 (en) |
AT (1) | ATE540642T1 (en) |
DK (1) | DK1905388T3 (en) |
ES (1) | ES2377737T3 (en) |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7955357B2 (en) | 2004-07-02 | 2011-06-07 | Ellipse Technologies, Inc. | Expandable rod system to treat scoliosis and method of using the same |
US7862502B2 (en) | 2006-10-20 | 2011-01-04 | Ellipse Technologies, Inc. | Method and apparatus for adjusting a gastrointestinal restriction device |
US8057472B2 (en) | 2007-10-30 | 2011-11-15 | Ellipse Technologies, Inc. | Skeletal manipulation method |
US11241257B2 (en) | 2008-10-13 | 2022-02-08 | Nuvasive Specialized Orthopedics, Inc. | Spinal distraction system |
US8382756B2 (en) | 2008-11-10 | 2013-02-26 | Ellipse Technologies, Inc. | External adjustment device for distraction device |
US8197490B2 (en) | 2009-02-23 | 2012-06-12 | Ellipse Technologies, Inc. | Non-invasive adjustable distraction system |
US9622792B2 (en) | 2009-04-29 | 2017-04-18 | Nuvasive Specialized Orthopedics, Inc. | Interspinous process device and method |
US9462964B2 (en) | 2011-09-23 | 2016-10-11 | Orthosensor Inc | Small form factor muscular-skeletal parameter measurement system |
EP3636176B1 (en) | 2009-09-04 | 2024-04-10 | NuVasive Specialized Orthopedics, Inc. | Bone growth device |
DE102009050727B4 (en) * | 2009-10-26 | 2016-09-29 | Orthopädie-Technik Scharpenberg e.K. | Method for identifying prosthetic body parts and their components, and prosthetic body part for carrying out the method |
US9332943B2 (en) | 2011-09-23 | 2016-05-10 | Orthosensor Inc | Flexible surface parameter measurement system for the muscular-skeletal system |
US8926530B2 (en) | 2011-09-23 | 2015-01-06 | Orthosensor Inc | Orthopedic insert measuring system for having a sterilized cavity |
US9248043B2 (en) | 2010-06-30 | 2016-02-02 | Ellipse Technologies, Inc. | External adjustment device for distraction device |
WO2012021378A2 (en) | 2010-08-09 | 2012-02-16 | Ellipse Technologies, Inc. | Maintenance feature in magnetic implant |
US8715282B2 (en) | 2011-02-14 | 2014-05-06 | Ellipse Technologies, Inc. | System and method for altering rotational alignment of bone sections |
US10743794B2 (en) | 2011-10-04 | 2020-08-18 | Nuvasive Specialized Orthopedics, Inc. | Devices and methods for non-invasive implant length sensing |
US10016220B2 (en) | 2011-11-01 | 2018-07-10 | Nuvasive Specialized Orthopedics, Inc. | Adjustable magnetic devices and methods of using same |
US20130338714A1 (en) | 2012-06-15 | 2013-12-19 | Arvin Chang | Magnetic implants with improved anatomical compatibility |
US9044281B2 (en) | 2012-10-18 | 2015-06-02 | Ellipse Technologies, Inc. | Intramedullary implants for replacing lost bone |
BR112015009446B1 (en) | 2012-10-29 | 2021-07-20 | Nuvasive Specialized Orthopedics, Inc. | SYSTEM FOR CHANGING AN ANGLE OF A SUBJECT'S BONE |
US9179938B2 (en) | 2013-03-08 | 2015-11-10 | Ellipse Technologies, Inc. | Distraction devices and method of assembling the same |
US10226242B2 (en) | 2013-07-31 | 2019-03-12 | Nuvasive Specialized Orthopedics, Inc. | Noninvasively adjustable suture anchors |
US9801734B1 (en) | 2013-08-09 | 2017-10-31 | Nuvasive, Inc. | Lordotic expandable interbody implant |
GB201316263D0 (en) | 2013-09-12 | 2013-10-30 | Metaphysis Llp | Medical device with diagnostics |
US10751094B2 (en) | 2013-10-10 | 2020-08-25 | Nuvasive Specialized Orthopedics, Inc. | Adjustable spinal implant |
EP3137000B1 (en) | 2014-04-28 | 2023-08-23 | NuVasive Specialized Orthopedics, Inc. | System for informational magnetic feedback in adjustable implants |
CN107106209B (en) | 2014-10-23 | 2020-07-14 | 诺威适骨科专科公司 | Bone growth device and external remote control for the same |
EP3236867B1 (en) | 2014-12-26 | 2022-02-23 | NuVasive Specialized Orthopedics, Inc. | Systems for distraction |
US10238427B2 (en) | 2015-02-19 | 2019-03-26 | Nuvasive Specialized Orthopedics, Inc. | Systems and methods for vertebral adjustment |
CN108135589B (en) | 2015-10-16 | 2021-07-23 | 诺威适骨科专科公司 | Adjustable device for treating gonitis |
EP3386405B1 (en) | 2015-12-10 | 2023-11-01 | NuVasive Specialized Orthopedics, Inc. | External adjustment device for distraction device |
JP6888015B2 (en) | 2016-01-28 | 2021-06-16 | ニューベイシブ スペシャライズド オーソペディックス,インコーポレイテッド | System for bone movement |
WO2017139548A1 (en) | 2016-02-10 | 2017-08-17 | Nuvasive Specialized Orthopedics, Inc. | Systems and methods for controlling multiple surgical variables |
DE102017131323A1 (en) * | 2017-12-27 | 2019-06-27 | Mecuris GmbH | Computer-implemented method and system for producing an orthopedic restoration |
JP2022519380A (en) | 2019-02-07 | 2022-03-23 | ニューベイシブ スペシャライズド オーソペディックス,インコーポレイテッド | Ultrasonic communication in medical devices |
US11589901B2 (en) | 2019-02-08 | 2023-02-28 | Nuvasive Specialized Orthopedics, Inc. | External adjustment device |
US11252560B1 (en) | 2020-11-25 | 2022-02-15 | Manicka Institute Llc | Secure communications between an implantable biomedical device and authorized parties over the internet |
US11904174B2 (en) | 2020-11-25 | 2024-02-20 | Manicka Institute Llc | Secure communications between an implantable biomedical device and authorized parties over the internet |
US20220265324A1 (en) | 2021-02-23 | 2022-08-25 | Nuvasive Specialized Orthopedics, Inc. | Adjustable implant, system and methods |
US11737787B1 (en) | 2021-05-27 | 2023-08-29 | Nuvasive, Inc. | Bone elongating devices and methods of use |
AU2022325024A1 (en) | 2021-08-03 | 2024-02-22 | Nuvasive Specialized Orthopedics, Inc. | Adjustable implant |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5752976A (en) * | 1995-06-23 | 1998-05-19 | Medtronic, Inc. | World wide patient location and data telemetry system for implantable medical devices |
US5912883A (en) * | 1996-11-01 | 1999-06-15 | Worldcomm Systems, Inc. | System for remote access to computer network |
US6083248A (en) * | 1995-06-23 | 2000-07-04 | Medtronic, Inc. | World wide patient location and data telemetry system for implantable medical devices |
US20010056359A1 (en) * | 2000-02-11 | 2001-12-27 | Abreu Marcio Marc | System and method for communicating product recall information, product warnings or other product-related information to users of products |
US20020010390A1 (en) * | 2000-05-10 | 2002-01-24 | Guice David Lehmann | Method and system for monitoring the health and status of livestock and other animals |
US20020024450A1 (en) * | 1999-12-06 | 2002-02-28 | Townsend Christopher P. | Data collection and storage device |
US20020026224A1 (en) * | 2000-08-26 | 2002-02-28 | Medtronic, Inc. | Implantable medical device incorporating integrated circuit notch filters |
US20030151524A1 (en) * | 2002-02-06 | 2003-08-14 | Clark Ronald Scott | Locator system with an implanted transponder having an organically-rechargeable battery |
US20030195015A1 (en) * | 2002-04-12 | 2003-10-16 | Fox Brian L. | Remote access unit for wireless wide-area data networking |
US20040032882A1 (en) * | 2002-08-19 | 2004-02-19 | Kane John Richard | Method and apparatus for data transfer |
US20040111042A1 (en) * | 2002-12-09 | 2004-06-10 | Imre Szabo | Bioelectric telemetering system and method |
US20040171935A1 (en) * | 2004-03-12 | 2004-09-02 | Siemens Medical Solutions Usa, Inc. | Ultrasound transducer probe identification for security and other purposes |
US20040229661A1 (en) * | 2003-05-12 | 2004-11-18 | Yuan-Yao Shen | Cellular phone combined physiological condition examination and processing device |
US20050134452A1 (en) * | 2001-11-30 | 2005-06-23 | Smith R. S. | Implantable tracking and monitoring system |
US20060224326A1 (en) * | 2005-03-31 | 2006-10-05 | St Ores John W | Integrated data collection and analysis for clinical study |
US20060287693A1 (en) * | 2005-06-08 | 2006-12-21 | Clifford Kraft | Implanted telephone system |
US20090124917A1 (en) * | 2002-12-18 | 2009-05-14 | John Hatlestad | Advanced patient management with environmental data |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5252102A (en) * | 1989-01-24 | 1993-10-12 | Electrobionics Corporation | Electronic range of motion apparatus, for orthosis, prosthesis, and CPM machine |
US6285897B1 (en) * | 1999-04-07 | 2001-09-04 | Endonetics, Inc. | Remote physiological monitoring system |
US6804558B2 (en) * | 1999-07-07 | 2004-10-12 | Medtronic, Inc. | System and method of communicating between an implantable medical device and a remote computer system or health care provider |
US6497655B1 (en) * | 1999-12-17 | 2002-12-24 | Medtronic, Inc. | Virtual remote monitor, alert, diagnostics and programming for implantable medical device systems |
US7256695B2 (en) * | 2002-09-23 | 2007-08-14 | Microstrain, Inc. | Remotely powered and remotely interrogated wireless digital sensor telemetry system |
US20060178583A1 (en) * | 2003-03-28 | 2006-08-10 | Valentino Montegrande | Blood pressure sensor apparatus |
US7801611B2 (en) * | 2004-06-03 | 2010-09-21 | Cardiac Pacemakers, Inc. | System and method for providing communications between a physically secure programmer and an external device using a cellular network |
AU2005286840B2 (en) | 2004-09-21 | 2012-01-12 | Shalon Ventures, Inc. | Tissue expansion devices |
EP1819278A4 (en) | 2004-11-15 | 2009-04-08 | Izex Technologies Inc | Instrumented orthopedic and other medical implants |
EP1843823B1 (en) * | 2005-02-02 | 2016-10-26 | Össur hf | Prosthetic and orthotic systems usable for rehabilitation |
-
2006
- 2006-09-29 US US11/537,338 patent/US8685091B2/en active Active
-
2007
- 2007-09-27 DK DK07253853.1T patent/DK1905388T3/en active
- 2007-09-27 AT AT07253853T patent/ATE540642T1/en active
- 2007-09-27 ES ES07253853T patent/ES2377737T3/en active Active
- 2007-09-27 EP EP07253853A patent/EP1905388B1/en active Active
-
2014
- 2014-02-25 US US14/189,712 patent/US20140313053A1/en not_active Abandoned
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6083248A (en) * | 1995-06-23 | 2000-07-04 | Medtronic, Inc. | World wide patient location and data telemetry system for implantable medical devices |
US5752976A (en) * | 1995-06-23 | 1998-05-19 | Medtronic, Inc. | World wide patient location and data telemetry system for implantable medical devices |
US5912883A (en) * | 1996-11-01 | 1999-06-15 | Worldcomm Systems, Inc. | System for remote access to computer network |
US20020024450A1 (en) * | 1999-12-06 | 2002-02-28 | Townsend Christopher P. | Data collection and storage device |
US20010056359A1 (en) * | 2000-02-11 | 2001-12-27 | Abreu Marcio Marc | System and method for communicating product recall information, product warnings or other product-related information to users of products |
US20020010390A1 (en) * | 2000-05-10 | 2002-01-24 | Guice David Lehmann | Method and system for monitoring the health and status of livestock and other animals |
US20020026224A1 (en) * | 2000-08-26 | 2002-02-28 | Medtronic, Inc. | Implantable medical device incorporating integrated circuit notch filters |
US20050134452A1 (en) * | 2001-11-30 | 2005-06-23 | Smith R. S. | Implantable tracking and monitoring system |
US20030151524A1 (en) * | 2002-02-06 | 2003-08-14 | Clark Ronald Scott | Locator system with an implanted transponder having an organically-rechargeable battery |
US20030195015A1 (en) * | 2002-04-12 | 2003-10-16 | Fox Brian L. | Remote access unit for wireless wide-area data networking |
US20040032882A1 (en) * | 2002-08-19 | 2004-02-19 | Kane John Richard | Method and apparatus for data transfer |
US20040111042A1 (en) * | 2002-12-09 | 2004-06-10 | Imre Szabo | Bioelectric telemetering system and method |
US20090124917A1 (en) * | 2002-12-18 | 2009-05-14 | John Hatlestad | Advanced patient management with environmental data |
US20040229661A1 (en) * | 2003-05-12 | 2004-11-18 | Yuan-Yao Shen | Cellular phone combined physiological condition examination and processing device |
US20040171935A1 (en) * | 2004-03-12 | 2004-09-02 | Siemens Medical Solutions Usa, Inc. | Ultrasound transducer probe identification for security and other purposes |
US20060224326A1 (en) * | 2005-03-31 | 2006-10-05 | St Ores John W | Integrated data collection and analysis for clinical study |
US20060287693A1 (en) * | 2005-06-08 | 2006-12-21 | Clifford Kraft | Implanted telephone system |
Non-Patent Citations (2)
Title |
---|
Ottobock. The electronic C-leg knee joint system instructions for use. Date verified by the Wayback machine 9/16/2005. * |
Rheo. Technical Manual. Date verified by the Wayback machine 8/30/2005. * |
Also Published As
Publication number | Publication date |
---|---|
US8685091B2 (en) | 2014-04-01 |
ATE540642T1 (en) | 2012-01-15 |
EP1905388B1 (en) | 2012-01-11 |
ES2377737T3 (en) | 2012-03-30 |
US20080133009A1 (en) | 2008-06-05 |
DK1905388T3 (en) | 2012-04-10 |
EP1905388A1 (en) | 2008-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8685091B2 (en) | System, method, and device for monitoring orthopaedic implant data over a cellular network | |
US11896391B2 (en) | Implantable reporting processor for an alert implant | |
US20190239802A1 (en) | System and method for transmitting orthopaedic implant data | |
EP0883371B2 (en) | A method and equipment for monitoring the health of a patient by measuring and predicting the glucose level of the patient's blood sample | |
US8942689B2 (en) | Method and technology for remote administration of wireless devices | |
EP2102775B1 (en) | Intelligent discovery of medical devices by a programming system | |
US11191479B2 (en) | Implantable reporting processor for an alert implant | |
EP1843271A2 (en) | System and method for managing patient-related data | |
CN103608817A (en) | Mapping of health data | |
EP3767923A1 (en) | Program control system and method for implantable electronic device | |
WO2003072192A1 (en) | Management of implantable devices | |
CN111630607B (en) | System, device, method, and program for treatment of diseases treatable by behavioral modification | |
US20180344198A1 (en) | Method and imaging system for optimizing a magnetic resonance examination to be performed on a patient | |
JP2002330930A (en) | Biological information measurement system, measurement instrument and communication equipment | |
CN105099582B (en) | A kind of load setting method and system | |
CN110795122A (en) | Medical software updating method based on medical data safety | |
CN116931786A (en) | Interface switching method, system, equipment and storage medium of hospital terminal | |
JP6615074B2 (en) | Switching timing adjustment method, communication apparatus, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DEPUY SYNTHES PRODUCTS, INC., MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:DEPUY SYNTHES PRODUCTS, LLC;REEL/FRAME:037542/0692 Effective date: 20141219 Owner name: DEPUY SYNTHES PRODUCTS, LLC, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:HAND INNOVATIONS LLC;REEL/FRAME:037542/0777 Effective date: 20121231 Owner name: DEPUY SPINE, LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DEPUY PRODUCTS, INC.;REEL/FRAME:037498/0328 Effective date: 20121230 Owner name: DEPUY PRODUCTS, INC., INDIANA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CAYLOR, EDWARD J., III;REEL/FRAME:037498/0067 Effective date: 20060929 Owner name: HAND INNOVATIONS LLC, FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DEPUY SPINE, LLC;REEL/FRAME:037498/0534 Effective date: 20121230 |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |