Collision resolution in x-ray imaging systems

[0001] This application claims priority from U.S. Provisional Application Ser. No. 60/781,151 filed on Mar. 10, 2006, the entire contents of which is incorporated herein by reference.

[0002] The invention relates to new and useful improvements in medical systems. More particularly, the invention relates to a collision resolution system and method for use in an x-ray imaging system.

[0003] Presently, angiographic x-ray systems are equipped with an automated collision protection function to avoid collisions of the various hardware components of the system with each other and, more importantly, with the patient. However, in some cases where the collision situation is not obvious to a system operator, collision events can still occur since the operator is allowed to override the warning until a physical collision occurs. One type of collision event that occurs with a fairly high degree of regularity is collisions of the tube underneath the patient table. These collisions occur fairly frequently because this area is not visible to the operator.

[0004] To resolve a collision event in present day angiographic x-ray systems, an override function is required to be activated by the operator. This is a necessary precaution because all motorized movements are blocked when a physical collision is detected. In those cases where an override is activated, the system allows the operator to move the system components in a very slow mode to resolve the collision event. In many cases the collision event is not obvious (e.g. the tube underneath the patient table) and it takes a significant amount of time and experience to move the system out of the collision situation. This is particularly true where a given position may be apparently reached with more than one set of axes motions but where motion limits on one or more axes produces a “dead end” requiring a time consuming backtracking in order to reach the desired position. In some cases, the patient must be removed from the system to avoid injury to quickly resolve a potentially dangerous and harmful situation.

[0005] From the foregoing it will be understood that there is a need for providing a collision detection system and method to maintain operational safety while providing the system operator with means for quickly and easily resolving a collision state.

[0006] A collision detection and resolution system and method of the invention addresses the afore-mentioned and other deficiencies of the prior art by detecting a collision state between various elements of an x-ray imaging apparatus and/or a patient when they occur and resolving the collision state by reversing the movement of the x-ray imaging apparatus along the same path traveled which led to the collision state in the first instance.

[0007] A collision detection and resolution system, according to one embodiment, comprises a control computer having at least one processor for acquiring position data of the most recent movements of an x-ray imaging apparatus, a memory for storing the acquired position data and a user interface for transmitting control signals to the at least one processor for instructing the processor to resolve a collision state, when it occurs, by using the acquired position data to move the x-ray imaging apparatus, by means of motorized drives, in the reverse direction of the apparatuses' most recent movement.

[0008] One of several advantages of the collision detection and resolution system of the invention is that collision resolution is easily implemented by a system operator using a standard interface device, such as a joystick, to initiate and control the resolution process. Another advantage of the present invention is that it provides a straightforward solution for resolving collision situations by using existing system information (i.e., the stored trajectory of the most recent movement of the x-ray imaging apparatus) together with the pre-existing motorized drives of the x-ray imaging system.

[0015] In the following description, various operating parameters and components are described for one constructed embodiment. These specific parameters and components are included as examples and are not meant to be limiting.

[0016] It is to be understood that the systems and methods described herein may be implemented in various forms of hardware, software, firmware, special purpose processors, or a combination thereof. In particular, at least a portion of the present invention is preferably implemented as an application comprising program instructions that are tangibly embodied on one or more program storage devices (e.g., hard disk, magnetic floppy disk, RAM, ROM, CD ROM, etc.) and executable by any device or machine comprising suitable architecture, such as a general purpose digital computer having a processor, memory, and input/output interfaces. It is to be further understood that, because some of the constituent system components and process steps depicted in the accompanying Figures are preferably implemented in software, the connections between the various modules (or the logic flow of method steps) may differ depending upon the manner in which the present invention is programmed. Given the teachings herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations of the present invention.

[0017] Turning now to the drawings and, with particular attention to FIG. 1, an external view of a C-arm structure included in an X-ray diagnostic imaging system 10 is shown.

[0018] In the X-ray diagnostic imaging system 10, the X-ray tube 21 held by the C-arm structure is an under table X-ray tube type. Alternatively, the structure may be an over table X-ray tube type. There is also shown a patient (P) lying on a patient table 24.

[0019] As shown in FIG. 1, the X-ray tube 21 is disposed at one end of a C-arm 28, and the X-ray detecting unit 22 is disposed on the other end of the C-arm 28 such that the X-ray tube 21 and the X-ray detecting unit 22 oppose each other.

[0020] The C-arm 28 can slide such that the X-ray tube 21 moves from the lower position to the upper left position in the drawing, or such that the X-ray detecting unit 22 moves from the upper position to the lower left position in the drawing. Furthermore, the C-arm 28 can rotate around a rotational axis of the rotating mechanism 23.

[0021] The X-ray diagnostic imaging system 10 includes a computer (not shown) functioning as a controlling unit that drives various units to capture the contrast images.

[0022] Referring now to FIG. 2, there is shown a block diagram showing the components of a computer system 106, which can be used to drive the various units of the x-ray system diagnostic imaging system 10 to capture the contrast images. The computer system 106 includes a system memory 108, a motion control module 110, a collision control module 112, first (F1) 114 and second (F2) 116 data interfaces, and a module 118 for performing collision resolution in accordance with embodiments of the invention, referred to hereafter as a “flight recorder” module 118. It is understood that each of the modules 110, 112 and 118 are capable of performing the standard functions of a computer including the ability to perform calculations and logic operations required to execute a program.

[0023] In the exemplary illustrative embodiment, an operator 102 interfaces with the x-ray diagnostic system 10 via a user interface 124, which comprises a joystick and a dead man's switch. The C-arm 28 is controlled externally by the operator 102 using the joystick. Manipulation of the joystick 124 by the operator 102 creates control data (signals) which are sent to the motion control module 110 via interface connector 220. The motion control module 110 uses the control data, received via interface connector 220, to control the various motors M1 122a, M2 122b, M3 122c, M4 122d and M5 122e of the x-ray diagnostic system 10, via the second (F2) data interface 116, to move the C-arm 28.

[0024] Each of the motors M1 122a, M2 122b and M3 122c control various angular rotations of the C-arm structure. For example: Motor M1 122-a controls the left/right angular rotation of the C-arm 28, (RAO/LAO (Right Anterior Oblique/Left Anterior Oblique). Motor M2 122-b controls the top and bottom angular rotations of the C-arm 28, (CRAN/CAUD (cranial/caudal)). Source image distance (SID) movement between the x-ray tube and the image receptor is controlled via motor M3 122-c.

[0025] Linear movement in the x-direction of the patient table 24 is effected via motor M4 122-d (Table-X) and tilting movement of a patient table 24 is effected via motor M5 122-e (Table-Tilt). In other embodiments, motors M4 and M5 may be substituted for mechanical linkage operated via manual means.

[0026] Feedback of the current position of the various axes of the C-arm 28, under motor control is received at the first data interface F1 114 from position sensors 130a through 130g configured to detect a current position of each axis. As various position sensor data is received at the computer 106, it is stored in the system memory 108.

[0027] In an exemplary embodiment, at least a portion of the system memory 108 is configured in a ring buffer configuration. As is well known in the art, in a ring buffer configuration, newly written data overwrites old, previously stored data.

[0028] The collision control unit 112 is configured to monitor the actual positions of the C-arm 28, the patient table 24 and the source-image distance (SID) when a collision state is entered.

[0029] Whenever the x-ray diagnostic system 10 enters a collision zone, the velocity of the axes currently in motion of the x-ray system are reduced. A collision zone is generally defined herein as a zone around an object at a given distance from the object. In other embodiments, a “collision state” may be used in lieu of a collision zone. A collision state may be defined as a state in which a device receptor actually touches another-surface, including the patient, upon which all motion is immediately suspended. In the presently described embodiment, a “collision state” may be detected by one or more system collision sensors 126. It is noted that the embodiments of the invention contemplate the use of both collision zones and collision states in various embodiments.

[0030] The flight recorder module 118 of the invention is configured to operate in one of two modes, normal and resolve.

[0031] The flight recorder module 118 determines which mode it is currently operating in (i.e., normal or resolve) based on a binary input signal received from the collision control module 112 which determines whether or not a collision zone has been entered or a collision state has occurred. For example, a binary input signal value of 0 could indicate that the system 10 is presently in a ‘normal’ mode and a binary input signal value of 1 could indicate that the system is in a ‘resolve’ mode.

[0032] In the normal mode of operation, the flight recorder module 118 formats and stores the most recent movements (e.g., the last 10 seconds) of the C-arm 28 and patient table 24 as a series of time-stamped vectors, received via interface F1 114 in the system memory 108.

[0033] In the resolve mode of operation, the flight recorder module 118 of the invention resolves a detected collision state of the x-ray imaging system 10 as follows.

[0034] When a collision state is detected by the collision control module 112, the time-stamped vectors which are currently stored in the system memory 108 are frozen in the memory. It is noted that the frozen values constitute the most recent movement of the system 10 prior to entering the resolve mode upon detecting a collision state.

[0035] When the operator initiates the process of collision resolution, typically in response to a system message on display 122, the data values, frozen in the system memory 108, are individually read out from the system memory 108 by the flight recorder module 118 in the reverse order in which they were written. In other words, the last vector to be written to the system memory 108 is the first vector to be read out from the system memory 108.

[0036] As the vector values are read out from the system memory 108 in reverse order, they control the various system motors M1-M5 to produce a reverse trajectory of the most recent movements of the C-arm 28 controlled by motors M1-M3 and patient table 24 controlled motors M4-M5 which led to the occurrence of entering the collision state in the first instance. It is noted that in those configurations wherein the patient table 24 is controlled via mechanical means, suitable instructions may be displayed to the operator 102 via display 122, indicating the necessary operations to be performed on the table 24 to resolve the collision state.

[0037] In this embodiment, the operator 102 both initiates the process of collision resolution and controls the speed of the process (i.e., the reverse trajectory movement of the C-arm 28) by manipulating a joystick. In other embodiments, the operator 102 merely initiates the process of collision resolution via a button press without controlling the speed of the reverse trajectory movement. In these embodiments, the speed of the reverse trajectory movement is automatic.

[0038] With reference now to FIG. 3 and certain elements of FIGS. 1 and 2, there is shown a process 300 for resolving a collision state in an x-ray imaging system 10 in accordance with the present invention.

[0039] At step 302, it is determined if the C-arm 28 is moving. Movement is determined by the motion control module 110 receiving changing position sensor inputs 130. If it is determined at this step that the C-arm 28 is moving, the process continues at step 304, otherwise the process remains at step 302 until movement is detected.

[0040] At step 304, position data associated with the movement of the C-arm 28 is recorded in the system memory 108. More particularly, position sensor data is continuously received by the inventive flight recorder module 118 from the various position sensors 130, via the first interface F1 114. The position sensor data is formatted by the inventive flight recorder module 118 and is stored in the system memory 108 in a format described further below.

[0041] At step 306, the collision control module 112 determines whether a collision has occurred. If it is determined that a collision has occurred, the process continues at step 308, otherwise, the process returns to step 302. Collision detection is determined by the collision control unit 112 by processing inputs received from the various position sensors 130 together with an internal software model of the physical x-ray system 10.

[0042] At step 308, a warning is displayed to the operator indicating that a collision zone is entered in an embodiment that employs collision zones or that a collision has occurred in an embodiment that employs collision states.

[0043] At step 310, the system 10 is automatically switched from normal mode to resolve mode in which all of the motor drives M1-M5 are stopped. To switch the system 10 from normal to resolve mode, the collision control module 112 sends a signal to the motion control module 110 to stop all motion. Thereafter, both the motion control module 110 and the flight recorder module 118 are set to ‘resolve’ mode.

[0044] At step 312, in the resolve mode, the system 10 waits for the operator 102 to initiate a collision resolution procedure. In the presently described embodiment, the collision resolution procedure is initiated by the operator holding down a dead man's switch while deflecting the joystick (i.e., user interface 124) a predetermined amount. In this embodiment, the velocity of the reverse motion of the C-arm 28 is controlled by the degree of deflection of the joystick applied by the operator 102. In other embodiments, the velocity of the reverse motion of the C-arm 28 may occur at a fixed rate. In these embodiments, the collision resolution procedure is initiated by a simple button press without further operator intervention.

[0045] At step 314, the collision resolution procedure, initiated at step 312, is performed, a more detailed explanation of which is provided in accordance with the detailed flowchart of FIG. 4, described below.

[0046] At step 316, upon completing the collision resolution procedure, the system 10 is reset to the normal mode and the process returns to step 302.

[0047] In FIG. 4 there is shown a more detailed process of step 312 of the flowchart of FIG. 3. Specifically, FIG. 4 is a detailed flowchart illustrating a process for performing collision resolution, in accordance with an embodiment of the present invention. With reference now to FIG. 4 and certain elements of FIGS. 1 and 2, the process begins at step 402.

[0048] At step 402, the motion control module 110 reads the degree of operator deflection of a user interface device (e.g., joystick deflection). The degree of deflection of the user interface device directly determines the speed (i.e., velocity) of the C-arm 28 moving along a reverse trajectory determined by the most recently stored data values in the system memory 108. More particularly, the deflection is used as a multiplier with an internal constant that controls the actual speed of the motors for moving from one position to another in accordance with the most recently stored data values in the system memory 108. As noted above, in other embodiments, the speed at which the C-arm 28 moves along a reverse trajectory may be set to a fixed value.

[0049] At step 404, the inventive flight recorder module 118 retrieves the last written stored movement (vector) of the C-arm 28 from the system memory 108, as indicated by a memory pointer.

[0050] At step 406, a memory pointer is decremented to point to the N-dimensional vector immediately preceding the N-dimensional time-stamped vector read at step 404.

[0051] At step 408, the N-dimensional time-stamped vector retrieved at step 404 is applied to the system 10 to cause the system 10 to move in a reverse trajectory in accordance with the N values.

[0052] At step 410, it is determined whether the C-arm 28 has been moved a so-called “safe distance” in a reverse direction. If so, the process for moving the C-arm 28 out of the collision state is complete. Otherwise, the process returns to step 402. It is noted that what determines a “safe distance” is configurable parameter which is set prior to system operation.

[0053] Referring now to FIG. 5, there is shown an exemplary illustrative embodiment of a ring buffer memory 500. The ring buffer memory 500 wraps stored data from the end of the memory (vector 17) area to the start of the memory area (vector 0). In the present embodiment, it is contemplated to utilize a portion of the system memory 108 for use as a ring buffer memory 500.

[0054] The ring buffer memory area 500 of FIG. 5 is shown to include 18 write positions (0-13) for ease of explanation. In various embodiments, the number of write positions may depend upon what constitutes the most recent movement of the C-arm 28.

[0055] Each write position of the ring buffer memory 500 (e.g., write positions 0-13 in the example) stores an N-dimensional time-stamped vector. For example, as shown in FIG. 5, vector 0 of the ring buffer memory, labeled 502, is an 8 dimensional vector including a time stamp value of 11:15:41:18 and seven vector values {0, −5, 91, 20, 13, 2, 0).

[0056] In accordance with the method of the invention for performing collision resolution, whenever motion occurs on any axis of the C-arm 28, that motion is detected by one or more of the system position sensors 130 and recorded as an N-dimensional time-stamped vector at a memory position pointed to by a memory pointer 50. For example, FIG. 5 illustrates the pointer 50 pointing to ring buffer position 8 (i.e., vector 8), corresponding to the most recently detected motion at time 11:15:41:34.

[0057] Whenever a collision state is detected, the data contents of the ring buffer memory area 500 are frozen and subsequently read in reverse order from the current pointer position, as determined by the memory pointer 50, to the first write position in the ring buffer memory 500 (i.e., vector 0), thus providing the flight recorder module 118 with the necessary data to move the C-arm 28 in a reverse trajectory of its most recent movement, as described at step 406 of the flowchart of FIG. 4.

[0058] There have thus been provided new and improved methods and systems for detecting and resolving a collision state in a x-ray imaging system. In the described embodiment of the invention, the invention comprises detecting a collision state between various elements of an x-ray imaging apparatus and/or a patient when they occur and resolving the collision state by reversing the movement of the x-ray imaging apparatus along the same path traveled which led to the collision state in the first instance. In accordance with benefits and advantages of the present invention, collision resolution is easily implemented by a system operator using a standard interface device, such as a joystick, to initiate and control the resolution process. Another advantage of the present invention is that it provides a straightforward solution for resolving collision situations by using existing system information (i.e., the stored trajectory of the most recent movement of the x-ray imaging apparatus) together with the pre-existing motorized drives of the x-ray imaging system.

[0059] While particular embodiments of the present invention have been illustrated and described, it would be obvious to those skilled in the art that various other changes and modifications can be made without departing from the spirit and scope of the invention. Any of the aspects of the invention of the present invention found to offer advantages over the state of the art may be used separately or in any suitable combination to achieve some or all of the benefits of the invention disclosed herein.