Patent Description:
During the data acquisition procedure, a guide catheter is inserted into a patient to an area of interest in the patient's intravascular system. Once the guide catheter is in place, other catheters can be inserted concentrically to perform diagnostic and treatment procedures. For example, an intravascular imaging system can use an optical or ultrasonic catheter to map the region of interest and determine the level of narrowing and tissue composition of an artery using OCT or IVUS.

In order to perform a procedure, the catheter must be connected to a series of peripherals and processing engines. These peripherals and processing engines tend to be complex and expensive. Moreover, in the catheter lab and especially at the patient bed, space is extremely limited, but the high data rate requirements drive the design where the data acquisition system is directly connected to the high-speed internal computer bus. For example, in the application of OCT to intravascular imaging, the time available for data acquisition is limited by the blood clearance requirements. This limited time, combined with large amounts of data collected at once to create a 3D image results in extremely high data acquisition rates.

<CIT> describes a patient communication system having a medical sensing device operable to collect medical data, a network communication module operable to transmit the medical data onto a data network, a controller operable to route the first medical sensing data to the network communication module, and a power source to provide power to the other elements.

The invention provides a portable digital imager for processing intravascular diagnostic data as set out in claim <NUM>. However, the disclosure generally relates to the field of devices suitable for use in the fields of medical treatment and diagnostics and more specifically the architecture of systems in a catheter laboratory. The present disclosure relates to an intravascular modular imaging acquisition and processing system where the high-speed data acquisition system and the processing unit are in different enclosures and connected by a high-speed digital network. Additionally, the present disclosure relates to a modular configuration to reduce clutter in the patient procedure environment and provide for interchangeability of imaging systems.

One aspect of the disclosure includes a portable digital imager for processing intravascular diagnostic data, the engine comprising a first interface coupling the digital imager to a set of imaging peripherals, an analog imager configured to receive analog image data from the imaging peripherals, a digitizer in communication with the analog imager to convert the analog image data into digital image data, a controller in communication with the digitizer, the controller in communication with the digitizer, the controller adapted to convert the digital image signal to serial communication data, and a second interface coupling the digital imager to a communication link configured to transmit the serial communication data to a remote processing engine.

The portable digital imager further may further include a housing, wherein, the analog imager, the digitizer and the controller are within the housing. At least some of the set of imaging peripherals may reside outside of the housing. The imaging peripherals are further connected to an imaging tool. The portable digital imager may be removably connected to the processing engine. The second interface coupling the portable digital imager to the remote processing engine provides high-speed, serial communications.

Another aspect of the disclosure relates to a modular image acquisition and processing system comprising a remote processing engine positioned outside of a patient procedure environment, a user interface positioned within the patient procedure environment and adapted to receive operational commands from a user, a hub positioned within the patient procedure environment. The hub may comprise a first connection port configured to maintain a persistent connection to the remote processing engine positioned outside of the patient procedure environment, and a further connection port configured for connection to a portable digital imager in the patient procedure environment. The system further comprises a set of imaging peripherals and a portable digital imager, comprising a first interface coupling the digital imager to a set of imaging peripherals, an analog imager configured to receive analog image data from the imaging peripherals, a digitizer in communication with the analog imager to convert the analog image data into digital image data, a controller in communication with the digitizer, the controller adapted to convert the digital image signal to serial communication data, and a second interface coupling the digital imager to a communication link configured to transmit the serial communication data to a remote processing engine.

The hub may further comprise at least one second connection port configured to maintain a persistent coupling to one or more monitors and controls in the patient procedure environment. The system may further comprise at least one light indicator on at least the remote processing engine, the hub, the portable digital imager, or the set of imaging peripherals. The light indicators may provide at least the connectivity or power status of at least the remote processing engine, the hub, the portable digital imager, or the set of imaging peripherals. The user interface comprises a monitor on a mobile cart, wherein the monitor is adapted to display at least intravascular image data, and wherein said monitor communicated with the processing engine via the same controller that interfaces with the digitizer. The user interface further comprises a keyboard and a mouse coupled to the monitor. The monitor may be a touch screen. The set of imaging peripherals may be positioned on a mobile cart. The set of imaging peripherals and the digital imager may be positioned on the mobile cart. The set of imaging peripherals, the digital imager and the monitor may be positioned on the mobile cart. The set of imaging peripherals may be positioned on a support. The set of imaging peripherals and the digital imager may be positioned on a support.

The hub may be positioned on a support. The hub may be positioned underneath the support. The second interface of the digital imager connects to the further connection port of the hub. The hub may receive power from the processing engine through the first connection port.

The set of imaging peripherals may comprise at least one of an imaging system engine, or a light source or an interferometer. The set of imaging peripherals may comprise at least one of an ultrasound imaging system, an ultrasound source, or an ultrasound transducer. The set of imaging peripherals may comprise at least one blood pressure sensor, a blood temperature sensor, or a blood flow sensor.

The hub may further comprise a power control, wherein the power control can detect a connection at the further connection port. The system may further comprise a hub extender. The hub extender may further comprise a power control, wherein the power control can detect a connection at the further connection port.

Another aspect of the disclosure includes a hub positioned within a patient procedure environment, comprising a first connection port configured to maintain a persistent connection to a remote processing engine positioned outside of the patient procedure environment, at least one second connection port configured to maintain a persistent coupling to one or more monitors or controls in the patient procedure environment, a third connection port configured for connection to a portable digital imager in the patient procedure environment, wherein the third connection port may contain a power control that is configured to detect a connection at the third connection port. The hub may further comprise a communications control.

The hub may receive power from the remote processing engine through the first connection port. The hub may be positioned on a support in the patient procedure environment. The hub may be removably attached to a hub mount on the support. The hub may be positioned under the procedure table in the patient procedure environment. The hub may further comprise a hub extender. The third connection port is configured for fixed connection to the hub extender, wherein the hub extender may comprise a removable connection to the portable digital imager. The hub extender may be positioned on a support in the patient procedure environment. The hub may be removably attached to a hub mount on the support. The hub may be positioned under a support in the patient procedure environment.

The disclosure relates to various systems and components thereof for use in a catheter lab or other lab environment to facilitate collection of vascular data from a patient. The vascular data may be related to the patient's cardiovascular or peripheral vascular system and can include image data, pressure data, and/or other types of data as described herein. The disclosure provides for a modular system, where some components may be persistently coupled while other are temporarily coupled during a procedure. The modularity of the system allows for ease of movement of the components and interchangeability of components. It further allows for multiple types of data acquisition to be performed by the system, such as by exchanging some components of the system while other components remain. For example, to accommodate different types of data acquisition, such as different types of imaging, processing components may remain while data acquisition components of a first type are exchanged with data acquisition components of a second type.

<FIG> illustrates the components and connections of a modular imaging acquisition and processing system <NUM>. The modular imaging acquisition and processing system <NUM> may include a user interface <NUM>, a processing engine <NUM>, a digital imager <NUM>, a hub <NUM>, a hub extender <NUM> including a plug <NUM> and a socket <NUM>, and imaging peripherals <NUM> a holster <NUM> for the imaging peripherals <NUM>.

The system <NUM> can be used to collect vascular data from a patient. For example, the system <NUM> may be part of an intravascular imaging system that further includes an image collection apparatus, such as an optical coherence tomography (OCT) probe, intravascular ultrasound (IVUS) probe, micro-OCT probe, near-infrared spectroscopy (NIRS) apparatus, or any of a variety of other intravascular data collection devices. Various elements of the system <NUM> may be located in a patient procedure environment, such as a catheter lab, in the vicinity of the patient or proximal to the patient. In some examples, certain components of the system <NUM> can be positioned remotely from the patient, such as in remote portions of the patient procedure environment that are not near the patient, or in a different room relative to the patient. For example, the processing engine <NUM> may reside in a remote room, such as a control room, equipment closet, or other another location, while the other components of the system are positioned in the patient procedure environment. The ability to place the processing engine <NUM> in a separate location from the other components of the system <NUM> allows for convenience and flexibility in fitting complex data acquisition equipment into limited spaces around a patient table or bed in the patient procedure environment.

The user interface <NUM> may be used to receive operator commands, such as for controlling the data acquisition system, and to display information, such as information related to the acquired vascular data. As such, the user interface <NUM> may include an input/output interface, such as a touchscreen, display, microphone, keyboard, mouse, a joystick, a control panel, etc. According to some examples, the user interface <NUM> may include one or more gesture recognition devices, such as a camera for recognizing hand gestures by the operator, an accelerometer, gyroscope, or the like. While <FIG> illustrates the user interface <NUM> as a display, it should be understood that the user interface <NUM> also includes input devices, such as - without limitation - keyboards, mice, touch screens, and joysticks, multiple displays or other input/output devices. There may be multiple user interfaces supporting one system. The user interface <NUM> may be directly or indirectly coupled with the processing engine <NUM> and the digital imager <NUM>. The user interface <NUM> may be positioned in the vicinity of or proximal to a patient or a patient support. When configured as a system, the user interface <NUM> may be located within the sterile field of the patient procedure environment. Alternatively, the user interface <NUM> may be located outside of the sterile field of the patient procedure environment. In some embodiments, the user interface <NUM> may be docked on a mobile apparatus, such as a wheeled cart, that also includes other components, such as the imaging peripherals <NUM> and digital imager <NUM>.

The modular system may be set up with multiple user interfaces for use by one or multiple users. For example, while one user interface <NUM> is illustrated in <FIG>, the modular system may be set up with two or three or more user interfaces. By way of example, a first user interface may include a sterile environment user interface within the sterile field of the patient procedure room. Such sterile environment user interface may be operated by a physician within the sterile field of the patient procedure room, such as to control an intravascular imaging tool or other data acquisition equipment. A second user interface may include a remote user interface. The remote user interface may reside within a separate area from the patient procedure environment, such as in a remote room. In some examples, the remote user interface may reside in a same remote area as the processing engine and/or an angiography system. The remote user interface may be operated by, for example, a technician. In some examples, the system may feature a single power control button within the remote area. The power button may be on the processing engine. A third user interface may include for example, a cart user interface in the patient procedure room. The cart user interface may be connected to the digital imager and/or imaging peripherals. The cart user interface may be docked on a mobile cart, as depicted in <FIG> to be described more fully in turn below. The user interfaces may each include any one or more of a variety of types of input/output devices adapted to receive user input and provide output, such as a monitor, a mouse, a keyboard, a touchscreen, a joystick, etc. The user interfaces may be communicatively coupled with each other. The user interfaces may display the same images and information to the different users, or each user interface may display different information, such as different images, different input options, etc. While a few examples of different types of user interfaces are described herein, it should be understood that other types of user interfaces, to be operated by different types of users or to facilitate different types of input/output, may additionally or alternatively be included in the modular system.

The processing engine <NUM> may include one or more processors in communication with memory, buses, controllers, and other components suitable for processing data. The processing engine <NUM> may be equipped with software implementations, computer program instructions or instructions configured to process and calculate physical, anatomical and physiological data. For example, the processing engine may receive raw data from the data acquisition system and convert the raw data into images, graphs, measurements, tissue characteristics or other output. The raw data may include, for example, signals received from the data acquisition system, such as optical signals, ultrasound signals, etc. According to some examples, the processing engine may be connected to a hospital network and receive data from other systems, such as angiography data from an angiography system.

The processing engine <NUM> may be coupled to the user interface <NUM> and/or other components of the system <NUM> via one or more communication links. The one or more communication links may be configured to transmit data, commands, or other types of signals. According to some examples, the one or more communication links may include an optical communication link. The communication links may be configured to transmit data at high bandwidth, such as <NUM> Gbps (gigabits per second) to <NUM> Gbps or more. This high speed allows data to be transmitted from the imager to the processing engine in real-time as it is acquired, without the need of compression or preprocessing at the patient end. As the processing engine <NUM> may be located in a separate control room remote from a catheter patient procedure environment in which the other components of the system are positioned, the communication links may extend over significant distances, such as tens or hundreds of feet, where ten feet is about <NUM> metres and a hundred feet is about <NUM> metres.

The processing engine <NUM> may be persistently coupled to one or more components, such as the hub <NUM>, in the patient procedure environment. In this regard, the communication link may be permanently fixed underground, under flooring, along beams or other structures between the remote room in which the processing engine <NUM> is stored and the patient procedure environment. In this regard, the communication link is less likely to become damaged by movement, touch, or other interaction that may otherwise occur if the communication link were mostly exposed, and therefore preserves a quality of signals transmitted over the communication link. Similarly, by maintaining a persistent coupling between the processing engine <NUM> and the hub <NUM>, a possibility of interrupted signal or improper coupling is reduced in comparison to a system where the communication link is connected before each procedure and disconnected afterward. Furthermore, significant time may be saved by maintaining the connection between the processing engine <NUM> and the other system <NUM> components in the patient procedure environment, as opposed to reconnecting all components before each procedure. In addition to communicating with the hub <NUM> and peripherals as described, the processing engine <NUM> can also supply power to the peripherals eliminating the need for a separate power supply in the patient procedure area.

While the processing engine <NUM> is illustrated in <FIG> in connection with a single system <NUM>, in some examples the processing engine <NUM> may be used with multiple data acquisition systems at a different or a same time. For example, the processing engine <NUM> may be positioned in a remote room in communication with a first hub in a first patient procedure environment and also in communication with a second hub in a second patient procedure environment. According to some examples, each patient procedure environment may be used for different types of procedures. For example, each of the first and second procedure environments may be adapted to obtain vascular data using IVUS, OCT, angiography, or other types of data acquisition. As such, the processing engine <NUM> may be configured to process various types of signals, including optical signals, ultrasound signals, etc..

According to some examples, the system may be used in connection with pressure measurements, such as to compute fractional flow reserve (FFR) measurements using a pressure measurement device, such as guidewire having one or more pressure and/or temperature sensors thereon. The pressure and/or temperature measurement device may be wired or wirelessly coupled to the processing engine <NUM> through one or more other components of the system <NUM>.

According to some examples, the processing engine <NUM> may be configured to perform comparison and co-registration of multiple different data acquisition types, such as OCT and/or IVUS images with angiographic images. For example, the data collection system can be configured to interface with an angiography device or with a hospital data network wherein angiographic data is stored.

The digital imager <NUM> may be a modular component that receives analog image data from the image catheter through the imaging peripherals <NUM>. The digital imager transmits image data between the imaging system and the processing engine <NUM>. The contents and functionality of the digital imager is described in more detail below in connection with <FIG>. In some configurations there may be multiple digital imagers to receive data from various imaging modalitie. For example, one digital imager may be congifured to receive data from OCT modalities and a second digital imager may be configured to receive data from IVUS modalities. The first OCT digital imager may be replaced with a second digital imager in the modular system. In some examples, the first and second digital imagers may be used simeultaneously.

The imaging peripherals <NUM> may include any of a variety of electronic components, which may vary based on a type of imaging being performed. The imaging peripherals <NUM> may be systems configured to route the signals to the catheter to control the catheter movement. In the case of the OCT system, these systems may be the fiber optic rotary join, motor controllers and catheter loading mechanisms. In the case of IVUS system, these systems may be a rotating catheter head. Typically, the imaging peripherals are in a separate housing from the digital imager allowing the imaging peripherals to be moved into the sterile field in order to perform the procedure. In some examples, the imaging peripherals may include various elements such as an electro-optic rotary coupler, rotational motor, linear travel stage, ultrasound controller, and motion controller. The imaging peripherals may include at least one blood pressure sensor or blood temperature sensor or a blood flow sensor. The imaging peripherals may be connected to an imaging catheter and its controls in the patient procedure environment. In some examples, the imaging peripherals may be anchored to a holster <NUM> within the patient procedure environment, as described in more detail below. The imaging peripherals <NUM> are shown in <FIG> as being within a housing adapted to fit within holster <NUM>. Such housing may also include other mechanisms, such as a coupling for an imaging probe, controls for operating the imaging probe, etc. In other examples, not shown, the imaging peripherals <NUM> may be housed within a same housing as other components, such as the digital imager <NUM>.

The system may be suitable for handling multiple imaging modalities. For OCT, which uses interferometry to determine distances and other related measurements, the imaging peripherals may include a light source such as a laser, and an optical interferometer in communication with an opto-electrical (O/E) converter. In some example systems, imaging peripherals may include a reference arm optical path, a sample arm switch path. In some examples, the system may further comprise a set of catheter controls, such as a series of motors to rotate the catheter and translate it back across the region of interest. In some examples, the system may include a computer to recreate the artery geometry and tissue characteristics using special algorithms and transform routines.

For IVUS, that uses ultrasound to determine distances and other related measurements, the peripherals may be piezoelectric or capacitive micromachined transducers and associated signal processing elements, and motors to rotate and translate the catheter in some instances, or electrical drivers to engage transducers at different angles within the catheter.

The hub <NUM> may be a connection device adapted to communicatively couple multiple modular components. The hub <NUM> may be located within the patient procedure environment to facilitate connections to modules, such as the processing engine <NUM>, that are outside of the patient procedure environment. In some examples, the hub <NUM> connects the processing engine <NUM> and the digital imager <NUM>. The hub <NUM> may transmit power and data signals between the processing engine <NUM> and the digital imager <NUM>. The hub <NUM> is described in more detail below in connection with <FIG>. The plug <NUM> and the socket <NUM> are components of a hub connection system. The hub connection system may facilitate a connection between the hub <NUM> and the digital imager <NUM>. The plug <NUM> may be coupled to the digital imager <NUM>, while the socket <NUM> extends from the hub <NUM>. The plug <NUM> and socket <NUM> may each include a mating surface, such that a mating surface of the plug <NUM> is adapted to engage the mating surface of the socket <NUM>. The hub connection system is described in more detail below in connection with <FIG>.

The hub <NUM> may be connected to a hub extender <NUM>. The hub extender <NUM> may serve to facilitate a connection further away from the hub <NUM>. The hub extender may include the socket <NUM> configured to couple with the plug <NUM>, as described above. The hub extender <NUM> is described in more detail below in connection with <FIG>.

<FIG> illustrates details of the digital imager, here referenced as digital imager <NUM>. The digital imager <NUM> may include an analog imager <NUM>, a digitizer <NUM>, a controller <NUM>, an analog and/or digital link <NUM> coupling to imaging peripherals <NUM>, and a digital communication link <NUM> that may carry power coupling to remote processing engine <NUM>. In some embodiments, the analog imager <NUM>, the digitizer <NUM>, and the controller <NUM> may be contained in a single housing. The analog imager <NUM> may be the system that converts the images retrieved from the catheter into analog electrical signals. The analog imager <NUM> may include one or more of a tunable laser, fiber-optic interferometers, polarization controllers, opto-electrical converters, electro-optical converters, optical switches, electrical receivers and signal conditioners, and/or control systems for controlling these components. The imaging peripherals <NUM> may be systems configured to route the signals to the catheter to control the catheter movement. In the case of the OCT system, these systems may be the fiber optic rotary join, motor controllers and catheter loading mechanisms. In the case of IVUS system, these systems may be a rotating catheter head. The imaging peripherals may be in a separate housing from the digital imager allowing the imaging peripherals to be moved into the sterile field in order to perform the procedure. In another example, the imaging peripherals may be split wherein some of the imaging peripherals may be within the same housing as the digital imager and the rest are not within the same housing. In another example, the imaging peripherals may be in a housing outside of the digital imager. When the digital imager <NUM> is linked to the processing engine <NUM>, where the processing engine <NUM> may be located in a separate control room.

In some embodiments, the digital imager <NUM> may be configured to be connected to the imaging peripherals <NUM> via an analog and/or digital link <NUM>. The imaging peripherals <NUM> may be further connected to an imaging catheter and separate catheter controls. The imaging catheter may be inserted in the patient during a data acquisition procedure. The imaging catheter may be controlled by the imaging peripherals <NUM> and/ or separate catheter controls. The imaging catheter obtains image data from the vessels of the patient. The image data may be transmitted to the digital imager <NUM> through the imaging peripherals <NUM> via the link <NUM>. The image data may be transmitted from the imaging catheter as an analog signal.

The digital imager <NUM> may contain components for receiving and converting analog image data transmitted from the imaging catheter. The analog signal may be received by the analog imager <NUM>. The analog signal may be transmitted to the digitizer <NUM> within the housing of the digital imager <NUM>.

The digitizer <NUM> may digitize the analog signal within the digital imager. The digitizer <NUM> may sample the analog signal and convert the analog signal into a digital signal. In one example, the digitizer <NUM> may be configured to perform fast Fourier transforms (FFT) on OCT image data and/or ultrasound image data using a field programmable gate array (FPGA), digital signal processing (DSP) chip, application-specific integrated circuit (ASIC), or other digital logic device. Additional signal processing functionality, such as logarithmic scale compression and digital filtering, may also be incorporated onto the digitizer to reduce the burden on the processing engine. In another example, the digitized signals would be transmitted without conversion to the processing engine <NUM>. The digital imager size may range from about <NUM> metres (<NUM> inches) or less in length, about <NUM> metres (<NUM> inches) or less in depth, and about <NUM> metres (<NUM> inches) or less in width. The size of the digitizer allows for the digital imager to be compact. One advantage of the compact size of the digital imager is to allow for portability facilitating easier interchangeability within the patient procedure environment.

The digitized data may be further processed by the controller <NUM>. The controller may be configured to transform the digital image signal into a format compatible with a high-speed communications connection, such as communication link <NUM>. The formatted image data is transmitted over the communications link <NUM> to the communications controller <NUM> of the remote processing engine <NUM>. Due to the high-speed digital communication, the image data does not need to be compressed prior to transmitting to the processing engine <NUM>.

In some examples, the communications link <NUM> may use Ethernet, Universal Serial Bus (USB), or Thunderbolt protocols. In some examples, the communications link <NUM> may allow for high-speed, serial communications between the digital imager <NUM> and the processing engine <NUM>.

The communications controller <NUM> may be housed within the processing engine <NUM>. The communications controller may be configured such that it receives the formatted, digitized data from the communications link <NUM>. The communications controller may be further configured to convert the digitized signal to any of the protocols suitable for transmission. In addition, the communication controller may control the flow of power into the digital imager <NUM> coming from other components of the modular system, such as the hub <NUM> or the hub extender <NUM> (<FIG>) or the processing engine <NUM>. The communication controller may also send and receive other signals to/from the processing engine <NUM> in addition to the output from the digitizer <NUM>, such as controls for the analog imager <NUM>, the imaging peripherals <NUM> and video information, as described further below.

In conventional systems, the processing engine and the imager must reside in the same housing, due to the difficulty of extending a low-level analog signal long distances without losing strength of the signal or distorting the data. An image collection tool generates a large amount of image data, such as at the rate of <NUM> Gbps per second or more. This data rate typically necessitated the analog image data to be sent into the processing engine and digitized within the processing engine. Digitizing within the processing engine forces the processing engine and the digital imager to be co-located. Therefore, the processing engine needs to remain in the patient procedure room, or the analog imager signals need to extend long distances to reach a processing engine placed outside the patient procedure room. In the example described above, the digital imager <NUM> communicates with the processing engine <NUM> through a digital communications link in real-time, wherein the digitization of the image data or image signal occurs within the digital imager prior to transfer to the processing engine. Digitizing the of image data within the digital imager allows for the processing engine to be located remotely, thus reducing clutter in the procedure room.

<FIG> illustrate an example wherein the modular imaging acquisition and processing system <NUM> may include a processing engine <NUM>, a digital imaging engine <NUM>, imaging peripherals <NUM>, and a hub <NUM>. Such modular components may be used in connection with an imaging catheter <NUM>, etc. to obtain data from a patient <NUM>. The modular system may be positioned with respect to other components in the patient procedure environment, such as on a support <NUM>, a first link <NUM> between the imaging peripherals <NUM> and the digital imaging engine <NUM>, a second link <NUM> between the hub <NUM> and the remote processing engine <NUM>, a sterile environment user interface <NUM>, a network system <NUM>, an angiography system <NUM>, light indicators <NUM>-<NUM>. The system <NUM> of <FIG> is configured to allow similar remote and proximal positioning of different system components as otherwise described herein with different embodiments. When configured as a system, the processing engine <NUM>, the angiography system <NUM>, and the network system <NUM> may be located in a separate control room.

As seen in <FIG>, the imaging peripherals <NUM> may be mounted on a patient support <NUM> or other location using a holster <NUM>. The patient support <NUM> can include a bed, an operating table, or other apparatus suitable for positioning a patient during a data collection procedure.

The processing engine <NUM>, digital imaging engine <NUM>, imaging peripherals <NUM>, hub <NUM>, etc. may be compared with the like components described above in connection with <FIG>.

As shown in <FIG>, the system <NUM> has various features relating to the ability to position the various components relative to the patient <NUM> during a data acquisition procedure. Given that the patient <NUM> may be on the support <NUM> during the data collection procedure, the support <NUM> can serve as a frame of reference. In this example, the patient procedure environment may be divided into a sterile field and a non-sterile field. The patient <NUM> may sit or lay on a portion of the support <NUM> in a sterile field of the patient procedure environment. The data collection procedure may take place in large part within the sterile field. Additionally, the imaging catheter <NUM> and the sterile environment user interface <NUM> may also be within the sterile field of the patient procedure environment. In some other examples, the sterile environment user interface 381may be located in the non-sterile field. During the data acquisition procedure, the imaging catheter <NUM> may be inserted into the patient <NUM>. The imaging catheter <NUM> may be connected to the imaging peripherals <NUM> and/or separate catheter controls. During the procedure, as depicted in <FIG>, the imaging peripherals <NUM> may be removed from the holster <NUM> and brought into the sterile environment of the patient procedure environment to connect to the imaging tool.

The processing engine <NUM> and the angiography system <NUM> may be positioned outside of the patient procedure environment. The processing engine <NUM> may be connected to a hospital network <NUM>. The hospital network <NUM> may include one or more data exchange connections that may be wired, optical, wireless, etc. Various network topologies, cable arrangements, and data routing techniques can be used to facilitate the operation of the modular system. The hospital network <NUM> may be configured to interconnect computing systems allowing for the exchange of data between authorized physicians, such as for review of patient files, transmission of patient images for a second opinions, etc..

The processing engine <NUM> may be connected to the angiography system <NUM> and receive data from the angiography system <NUM> without the need for a remote power supply in the vicinity of the angiography system. Though these connections are depicted as a wired connection, the connection may also be wireless. The processing engine <NUM> may remain connected to a power source.

The sterile environment user interface <NUM> may be directly or indirectly coupled to the processing engine <NUM>, such as by way of one or more communication links and other components. In the example shown, the sterile environment user interface <NUM> is directly coupled to hub <NUM>, which is further coupled to the processing engine <NUM>. The communication links may be, for example, high bandwidth connections such as an optical, copper, or any other type of connection. Input/output devices, such as a keyboard, mouse, monitor, etc., may provide an interface for an operator to enter commands for the image acquisition tools, processing engine <NUM>, or other components of the modular system. For example, a physician in the sterile environment can manipulate input controls of the sterile environment user interface <NUM> to adjust data acquisition parameters, adjust patient parameters, perform steps of a workflow, etc. The physician can observe output from the sterile environment user interface <NUM>, such as audible or visible cues guiding an image acquisition workflow, image data, etc. While the sterile environment user interface <NUM> is illustrated as a type of hand-operated manual input device, it may additionally or alternatively include a microphone for receiving voice commands, an image/object recognition unit for recognizing gestures, a display or speakers for outputting information, etc..

While only the sterile environment user interface <NUM> is illustrated in <FIG>, it should be understood that other types of user interfaces may be included in the modular system. For example, the modular system may be set up with two or three user interfaces for use by two or three separate users. In some examples, there may be a physician within the sterile field of the patient procedure room. As illustrated in <FIG>, the physician may control the intravascular imaging tool using the sterile environment user interface <NUM> within the sterile field of the patient procedure room. Additionally, there may be at least one technician that may use at least one remote user interface. For example, there may be a technician using a remote user interface connected to the processing engine or angiography system. The remote user interface may be located with the processing engine and the angiography system in a separate room. As another example, there may be a technician in the patient procedure room using a cart user interface connected to the digital imager and/or imaging peripherals. The cart user interface may be docked on a mobile cart. The user interfaces may each include any one or more of a variety of types of input/output devices, such as a monitor, a mouse, a keyboard, a touchscreen, a joystick, etc. The user interfaces may communicate with each other. Additionally, the user interfaces may display the same images and information to the different users, or each user interface may display different information, such as different images, different input options, etc..

The hub <NUM>, the digital imager <NUM> and the imaging peripherals <NUM> may be outside of the sterile field. The hub <NUM> and the digital imager <NUM> may be positioned underneath the support. The hub <NUM> is connected to the processing engine <NUM> via the communication and power link <NUM>. The link <NUM> may be routed outside of the patient procedure environment though the floor of the procedure room, as shown in <FIG>. The link <NUM> may transmit data and power signals between the processing engine <NUM> and the hub <NUM>. The hub <NUM> is configured to transmit the data and power signals to the other components of the modular imaging acquisition and processing system <NUM>, such that the processing engine <NUM> may transmit power and signals to components within the patient procedure environment between data acquisition procedures. This near constant power signal allows for operators to quickly prepare the system <NUM> for use without having to power up between procedures. As depicted in <FIG>, hub <NUM> may be connected through link <NUM> to a secondary hub <NUM> outside the procedure environment. In some examples, additional processing may happen at secondary hub <NUM>. In some examples, secondary hub <NUM> may be connected to the processing engine through a separate link, not link <NUM>. The secondary hub <NUM> may be used to connect the modular compoentets to the processing engine <NUM>. In some examples, the secondary hub <NUM> may be utilized when the proseccing engine <NUM> is in a remote closet. For example, the secondary hub may be used to connect remote user interfaces, such as a monitor, keyboard, mouse, etc., to the processing engine.

To set up the catheter lab more efficiently, in one embodiment, the digital imager <NUM> may be integrated with the hub <NUM> underneath the support <NUM>. The integrated digital imager <NUM> and hub <NUM> apparatus reduced clutter in the patient procedure environment. Additionally, a single link <NUM> may route analog and digital data and power signals between the digital imager <NUM> and the imaging peripherals <NUM>. In one embodiment, the imaging peripherals <NUM> may be positioned on the support <NUM> by the holster <NUM> when not in use, as shown in <FIG>. In another example, the imaging peripherals <NUM> may be connected to the holster <NUM> while connected to the imaging catheter. The imaging peripherals <NUM> connects to the holster <NUM> by mechanical fit. For example, the holster <NUM> may form a receptacle sized and shaped corresponding to a housing for the imaging peripherals <NUM>, such that the imaging peripherals <NUM> can be inserted into the holster <NUM> and retained therein until it is removed to perform the procedure. Engaging the imaging peripherals with the holster may be assisted through the use of placement mechanisms, such as magnets, interlocking mechanical features, or a sliding rail system. For example, one or more magnets having a first polarity may be fixed on an inner surface of the holster and one or more corresponding magnets having an opposing polarity may be fixed on an outer surface of the imaging peripherals, such that the magnets on the imaging peripherals engage the magnets on the holster to help retain the imaging peripherals in place within the holster. In another example, the holster may have grooves and a housing of the imaging peripherals may have retractable arms that interlock into the grooves when placed into the holster. In yet another example, the holster may have a track and the imaging peripherals may have a rail configured to slide into the rail.

Using a single link <NUM> to couple the imagine peripherals to the digital imager will allow the user to quickly set up the imaging peripherals <NUM> without having to connect multiple, additional cables. As such, this provides for quick and reliable connection, reducing setup time and reducing possibility for communication errors. The holster <NUM> provides for secure and accurate positioning of the imaging peripherals, thereby conserving space in the procedure environment and reducing a possibility of damage to the peripherals.

There may also be light indicators <NUM>-<NUM> on the modular components. The light indicators <NUM>-<NUM> may communicate status of the components to the user, such that the user can quickly and efficiently identify a status of each component and troubleshoot any issues. Though the light indicators <NUM>-<NUM> are depicted on the hub <NUM>, digital imager <NUM> and the imaging peripherals <NUM>, all components of the modular imaging acquisition and processing system <NUM> may be individually equipped with light indicators. Moreover, while light indicators are illustrated in the present example, in other examples other types of indicators may be used. For example, such other indicators may provide audible feedback, haptic feedback such as vibrations or the like, etc..

Referring to <FIG>, the modular imaging acquisition and processing system <NUM> may include a processing engine <NUM>, a digital imaging engine <NUM>, holster <NUM>, imaging peripherals <NUM>, a hub <NUM>. Such modular components may be used in connection with an imaging catheter <NUM>. The imaging peripherals <NUM> would be taken off the holster <NUM> and placed in the sterile field to guide the catheter into the body and obtain data from a patient <NUM>. The modular system may be positioned with respect to other components in the patient procedure environment, such as a support <NUM>, a first link <NUM>, a second link <NUM>, a sterile environment user interface <NUM>, a network system <NUM>, an angiography system <NUM>, light indicators <NUM>-<NUM>. The system <NUM> of <FIG> is configured to allow similar remote and proximal positioning of different system components as otherwise described herein with different embodiments. When configured as a system, the processing engine <NUM>, the angiography system <NUM>, and the network system <NUM> may be located in a separate control room.

As further shown in <FIG>, another depiction of the modular imaging acquisition and processing system <NUM>, similar to that shown in <FIG>. As shown, in some examples, the modular image acquisition and processing system <NUM> may include a sterile environment user interface <NUM>, a digital imaging engine <NUM>, imaging peripherals <NUM>, a hub <NUM>, and a holster <NUM>. The modular system may be positioned with respect to the other components in the patient procedure environment, such as a support <NUM>, a first link <NUM>, a second link <NUM>, and light indicator(s) <NUM>.

As shown in <FIG>, the system <NUM> has various features relating to the ability to position the various components relative to the patient <NUM> during a procedure. Given that the patient <NUM> may be on the support <NUM> during the data collection procedure, the support <NUM> can serve as a frame of reference. In this example, the patient procedure environment may be divided into a sterile field and a non-sterile field. The patient <NUM> may on the portion of the support <NUM> in a sterile field of the patient procedure environment. The data collection procedure may take place in large part within the sterile field. Additionally, the imaging catheter <NUM>, the imaging peripherals <NUM>, the sterile environment user interface <NUM> may also be within the sterile field of the patient procedure environment. Alternatively, the sterile environment user interface <NUM> may be located in the non-sterile field. During the data acquisition procedure, the imaging catheter <NUM> may be inserted into the patient <NUM>. The imaging catheter <NUM> may be connected to the imaging peripherals <NUM>. In this example, the imaging peripherals <NUM> would be removed from the holster <NUM> and brought into the sterile field of the patient procedure environment to be connected to the imaging catheter <NUM>. In another example, the imaging peripherals <NUM> could remain anchored to the holster <NUM> while connected to the imaging catheter <NUM>. The imaging peripherals <NUM> may include, for example, an input interface in communication with a motor, a rotating mechanism, a pullback mechanism, a steering mechanism, or other mechanisms for moving a catheter through a vessel. Such interface may include manual controls and/or digital controls. In some examples, the imaging peripherals may include features for manipulating an imaging probe and/or features for preparing a vessel for imaging. By way of example only, such features may include a beam splitter, a purge port, optical switches, electrical receivers, etc..

The modular system may be set up with multiple user interfaces for use with multiple users. For example, the modular system may be set up with two or three user interfaces for use by two or three separate users. In some examples, there may be a physician within the sterile field of the patient procedure room. As illustrated in <FIG>, the physician may control the intravascular imaging tool using the sterile environment user interface <NUM> within the sterile field of the patient procedure room. Additionally, there may be at least one technician that may use at least one remote user interface <NUM>, as depicted in <FIG>. For example, there may be a technician using a remote user interface <NUM> connected to the processing engine <NUM> or angiography system <NUM>. The remote user interface <NUM> may be located with the processing engine and the angiography system in a separate room. As another example, there may be a technician in the patient procedure room using a cart user interface connected to the digital imager and/or imaging peripherals. The cart user interface may be docked on a mobile cart. The user interfaces may each include any one or more of a variety of types of input/output devices, such as monitors, a mouse, keyboard, touchscreens, joysticks, etc. The user interfaces may be communicatively coupled with each other. The user interfaces may display the same images and information to the different users, or each user interface may display different information, such as different images, different input options, etc..

The processing engine <NUM> and the angiography system <NUM> may be positioned outside of the lab environment. The processing engine <NUM> may be connected to the angiography system and transmit both data and power signals to the angiography system <NUM>. The processing engine <NUM> may be connected to a network system <NUM>. The hospital network <NUM> may include one or more data exchange connections that may be wired, optical, wireless, etc. Various network topologies, cable arrangements, and data routing techniques can be used to facilitate the operation of the modular system. The hospital network <NUM> may be configured to interconnect computing systems allowing for the exchange of data between authorized physicians, such as for review of patient files, transmission of patient images for a second opinions, etc. The processing engine <NUM> may be connected to the angiography system <NUM> and receive data from the angiography system <NUM> without the need for a remote power supply close to the angiograph. Though these connections are depicted as a wired connection, the connection may also be wireless. The processing engine <NUM> may remain connected to a power source.

Control signals from the processing engine may be sent to a remote user interface by way of a communication link <NUM>, such as an optical link. Input/output devices, such as a keyboard, mouse monitor, etc., may provide an interface for an operator to enter commands for the processing engine <NUM>.

The sterile environment user interface <NUM> may be directly or indirectly coupled to the processing engine <NUM>, such as by way of one or more communication links and other components. In the example shown, the sterile environment user interface is directly coupled to hub <NUM>, which is further coupled to the processing engine <NUM>. The communication links may be, for example, high bandwidth connections such as an optical link, or any other type of connection. Input/output devices, such as a keyboard, mouse monitor, etc., may provide an interface for an operator to enter commands for the image acquisition tools, processing engine <NUM>, or other components of the modular system. For example, a physician in the sterile environment can manipulate input controls of the sterile environment user interface <NUM> to adjust data acquisition parameters, adjust patient parameters, perform steps of a workflow, etc. The physician can observe output from the sterile environment user interface <NUM>, such as audible or visible cues guiding an image acquisition workflow, image data, etc. While the sterile environment user interface <NUM> is illustrated as a type of hand-operated manual input device, it may additionally or alternatively include a microphone for receiving voice commands, an image/object recognition unit for recognizing gestures, a display or speakers for outputting information, etc..

The hub <NUM>, the digital imager <NUM> and the imaging peripherals <NUM> may be outside of the sterile field. As described above, the imaging peripherals <NUM> may be moved into the sterile field when performing a procedure. The hub <NUM> and the digital imager <NUM> may be positioned underneath the support. The hub <NUM> is connected to the processing engine <NUM> via the link <NUM>. The link <NUM> may be routed outside of the patient procedure environment though the floor of the procedure room, as shown in <FIG>. The link <NUM> may transmit data and power signals between the processing engine <NUM> and the hub <NUM>. The hub <NUM> is configured to transmit the data and power signals to the other components of the modular imaging acquisition and processing system <NUM>, such that the processing engine <NUM> may transmit the power signals to components within the patient procedure environment between data acquisition procedures. This near constant power signal allows for the user to quickly prepare the system <NUM> for use without having to power up between procedures.

To set up the catheter lab more efficiently, in one embodiment, the digital imager <NUM> may be integrated with the imaging peripherals <NUM> on the support <NUM>. The integrated digital imager <NUM> and imaging peripheral <NUM> apparatus reduces clutter in the patient procedure environment. Additionally, a single link <NUM> may route data and power signals between the digital imager <NUM> and the imaging peripherals <NUM>. In one embodiment, the imaging peripherals <NUM> and digital imager <NUM> may be positioned on the support <NUM> by the holster <NUM>. In another example, the holster <NUM> may be positioned underneath the support <NUM>. In yet another example, the holster <NUM> may be positioned away from the support <NUM>, such as beside the support <NUM>, on an IV pole <NUM>, on a wall of the patient procedure environment, on the boom monitor within the patient procedure environment, or elsewhere in the patient procedure room.

The imaging peripherals <NUM> may engage with the holster <NUM> by mechanical fit. For example, the holster <NUM> may form a receptacle sized and shaped corresponding to a housing for the imaging peripherals <NUM>, such that the imaging peripherals <NUM> can be inserted into the holster <NUM> and retained therein until it is removed. According to some examples, an electronic port within the holster <NUM> may be used to communicatively couple the imaging peripherals <NUM> with other components of the system, such as the digital imager <NUM>, hub <NUM>, etc. For example, a port on the holster <NUM> may engage with a port on a housing of the imaging peripherals <NUM> when the imaging peripherals <NUM> are inserted into the holster <NUM>. The interconnection of such ports may establish an electrical coupling able to transmit power and/or data between components. The holster <NUM> may be coupled to further components, such as through ports, cables, or other electrical connections, and as such may establish a connection between the imaging peripherals <NUM> and such further components. Engaging the imaging peripherals with the holster may be assisted through the use of placement mechanisms, such as magnets, interlocking mechanical features, or a sliding rail system. For example, there may be magnets having one polar charge on the holster and magnets having an opposing polar charge on the imaging peripherals. In another example, the holster may have grooves and the imaging peripherals may have retractable arms that interlock into the grooves when placed into the holster. In yet another example, the holster may have a track and the imaging peripherals may have a rail configured to slide into the rail. This process will allow the user to quickly set up the imaging peripherals <NUM> and digital imager without having to connect multiple, additional cables. Additionally, the user will be able to spend less time orienting the imaging peripherals <NUM> as the holster <NUM> will facilitate correct positioning. In some examples, while not in use, the imaging peripherals <NUM> may be anchored in the holster <NUM>, as depicted in <FIG>. During the procedure, the imaging peripherals <NUM> may be removed from the holster <NUM> to be connected to the imaging tool within the sterile environment, as depicted in <FIG>.

The module components may include one or more indicators, such as light indicators <NUM>-<NUM>. The light indicators <NUM>-<NUM> may communicate status of the components to the user, such that the user can quickly and efficiently identify a status of each component and troubleshoot any issues. Though the light indicators <NUM>-<NUM> are depicted on the hub <NUM>, digital imager <NUM> and the imaging peripherals <NUM>, all components of the modular imaging acquisition and processing system <NUM> may be individually equipped with light indicators. Moreover, while light indicators are illustrated in the present example, in other examples other types of indicators may be used. For example, such other indicators may provide audible feedback, haptic feedback such as vibrations or the like, etc..

Referring to <FIG>, in one example the modular imaging acquisition and processing system <NUM> may include a processing engine <NUM>, a digital imaging engine <NUM>, imaging peripherals <NUM>, and a hub <NUM>. Such modular components may be used in connection with an imaging catheter <NUM> and imaging peripherals <NUM>, to obtain data from a patient <NUM>. The modular system may be positioned with respect to other components in the patient procedure environment, such as a support <NUM>, a first link <NUM>, a second link <NUM>, at least one light indicator <NUM>, a network system <NUM>, an angiography system <NUM>, an imaging catheter <NUM>, imaging peripherals <NUM>, a boom monitor <NUM>, sterile environment user interfaces <NUM> and <NUM>, cart user interface <NUM>, and a patient <NUM>. The system <NUM> of <FIG> is configured to allow similar remote and proximal positioning of different system components as otherwise described herein with different embodiments. When configured as a system, the processing engine <NUM>, the angiography system <NUM>, and the network system <NUM> may be located in a separate control room.

As further shown in <FIG>, another depiction of the modular imaging acquisition and processing system <NUM>, similar to that shown in <FIG>. As shown, in some examples, the modular image acquisition and processing system <NUM> may include a remote user interface unit <NUM>, a digital imaging engine <NUM>, imaging peripherals <NUM>, a hub <NUM>, a hub extender <NUM>, and a holster <NUM>. The modular system may be positioned with respect to the other components in the patient procedure environment, such as a support <NUM>, a first link <NUM>, at least one light indicator <NUM>, a boom monitor <NUM>, sterile environment user interface <NUM>, and a cart user interface <NUM>. The processing engine <NUM> and remote user interface <NUM> may be in a separate room, divided by a structure, such as wall <NUM>.

As shown in <FIG>, the system <NUM> has various features relating to the ability to position the various components relative to the patient <NUM> during a procedure. Given that the patient <NUM> may be on the support <NUM> during the data collection procedure, the support <NUM> can serve as a frame of reference. In this example, the patient procedure environment may be divided into a sterile field and a non-sterile field, by a dividing structure, such as wall <NUM>. The patient <NUM> may on the portion of the support <NUM> in a sterile field of the patient procedure environment. The data collection procedure may take place in large part within the sterile field. The imaging catheter <NUM>, the imaging peripherals <NUM> the user interface modules <NUM> and <NUM>, and the hub <NUM> may also be within the sterile field of the patient procedure environment. Alternatively, the sterile environment user interfaces <NUM> and <NUM> modules and the hub <NUM> may be located in the non-sterile field. During the data acquisition procedure, the imaging catheter <NUM> may be inserted into the patient <NUM>. The imaging catheter <NUM> may be connected to the imaging peripherals <NUM>, which may include catheter controls. During the procedure, the imaging peripherals may remain on the cart <NUM> while connected to the imaging catheter <NUM>. In another example, the imaging peripherals <NUM> may be moved into the sterile field of the patient procedure environment to be connected to the imaging catheter <NUM>. In yet another example, as shown in <FIG> the imaging peripherals <NUM> may be separated into multiple housings, where some of the imaging peripherals may move into the sterile field to be connected to the imaging catheter <NUM>, while the rest of the imaging peripherals remain on the cart <NUM>.

The processing engine <NUM> and the angiography system <NUM> may be positioned outside of the patient procedure environment. The processing engine <NUM> may be connected to the angiography system and receive data signals from the angiography system <NUM> without the need for a remote power supply close to the angiograph. The processing engine <NUM> may be connected to a network system <NUM>. The hospital network <NUM> may include one or more data exchange connections that may be wired, optical, wireless, etc. The hospital network <NUM> may be configured to interconnect computing systems allowing for the exchange of data between authorized physicians, such as for review of patient files, transmission of patient images for a second opinions, etc. The processing engine <NUM> may be electrically and/or communicatively connected to the angiography system <NUM>. According to some examples, the processing engine <NUM> may transmit data and/or power signals to the angiography system <NUM>. Though these connections are depicted as a wired connection, the connection may also be wireless. For example, the connection may be established through a wireless local area network or other type of network using WiFi, Bluetooth, ultra-wideband, or any other type of wireless communication technology. The processing engine <NUM> may remain connected to a power source.

Control signals from the processing engine are sent to the remote user interface <NUM> by way of a communication link, such as an optical link. Input/output devices, such as a keyboard, mouse monitor, etc., may provide an interface for an operator to enter commands for the processing engine <NUM>.

The modular system may be set up with multiple user interfaces for use with multiple users. For example, the modular system may be set up with two or three user interfaces for use by two or three separate users. In some examples, there may be a physician within the sterile field of the patient procedure room. As illustrated in <FIG>, the physician may control the intravascular imaging tool using the sterile environment user interface <NUM> or <NUM> within the sterile field of the patient procedure room. The sterile environment user interface may transmit signals to the boom monitor <NUM> within the sterile field of the patient procedure room. Additionally, there may be at least one technician that may use at least one other user interface. For example, there may be a technician using the remote user interface <NUM> connected to the processing engine <NUM> or angiography system <NUM>. As shown in <FIG>, the remote user interface <NUM> may be located with the processing engine <NUM> and the angiography system <NUM> in a separate room. As another example, there may be a technician in the patient procedure room using a cart user interface <NUM> connected to the digital imager <NUM> and/or imaging peripherals <NUM>. The cart user interface may be docked on a mobile cart <NUM>. Further, the cart user interface <NUM> may share a link transmitting serial communications between the digital engine <NUM> and/or the imaging peripherals <NUM>. The user interface devices may each include any one or more of a variety of types of input/output devices, such as monitors, a mouse, a keyboard, a touchscreen, a joystick, etc. The user interfaces may be communicatively with each other. The user interfaces may display the same images and information to the different users, or each user interface may display different information, such as different images, different input options, etc..

The digital imager <NUM>, the cart user interface <NUM> and the imaging peripherals <NUM> may be outside of the sterile field. The digital imager <NUM>, the cart user interface <NUM> and the imaging peripherals <NUM> may be positioned on a mobile apparatus that may be quickly interchanged between various catheter labs, such as cart <NUM>. The cart user interface may communicate with the processing engine through the same controller that interfaces the digitizer. The cart <NUM> may remain outside of the sterile field of the patient procedure environment and connect to the other components of the modular system <NUM> via a removable connection to the hub <NUM>. The hub <NUM> may be positioned on or underneath the support <NUM>. The hub <NUM> may be permanently affixed to the support <NUM>. In some examples, the hub <NUM> may be removably mounted to support <NUM>, underneath the support <NUM>, or anywhere else in the patient procedure environment. The hub <NUM> may be connected to a hub mount by a mechanical fit. For example, the hub mount may form a receptacle sized and shaped corresponding to a housing for the hub <NUM>, such that the hub <NUM> can be inserted into the hub mount and retained therein until it is removed. Additionally, the docking process may be assisted through the use of placement mechanisms, such as magnets, interlocking mechanical features, or a sliding rail system. For example, there may be magnets having one polar charge on the hub mount and magnets having an opposing polar charge on the hub. In another example, the hub mount may have grooves and the hub may have retractable arms that interlock into the grooves when placed into the hub mount. In yet another example, the hub mount may have a track and the hub may have a rail configured to slide into the rail.

The hub <NUM> may have one or more connection ports, such as a first connection port, a second connection port, and a third connection port. The hub <NUM> is configured to transmit the data and power signals to the other components of the modular imaging acquisition and processing system <NUM>, such that the processing engine <NUM> may transmit the power signals to components within the patient procedure environment between and during data acquisition procedures. This near constant power signal allows for the user to quickly prepare the system <NUM> for use without having to power up between procedures. Additionally, the hub <NUM> may be configured to receive a single link <NUM> from the mobile apparatus, through the third connection port. The link <NUM> may transmit data and power between the hub <NUM> and the digital imager <NUM> and imaging peripherals <NUM>.

The hub <NUM> may be communicatively coupled to the processing engine <NUM> at the first connection port via link <NUM> and <NUM>. The link <NUM> may transmit data signals between the processing engine <NUM> and the hub <NUM>. The link <NUM> may transmit power between the processing engine <NUM> and the hub <NUM>. The hub <NUM> may maintain a persistent connection with the processing engine <NUM> at the first connection port, such that between and during procedures, power signals may be transmitted to the hub <NUM> through a persistent connection of link <NUM>. The hub <NUM> may be communicatively coupled to the sterile environment user interfaces <NUM> and <NUM> through the second connection port. The sterile environment user interfaces <NUM> and <NUM> may transmit data input signals to the other components of the modular system, such as the processing engine <NUM>, digital imager <NUM>, imaging peripherals <NUM>, through the second connection port of the hub <NUM>. The hub may maintain a persistent power connection between the sterile environment user interfaces <NUM> and <NUM> and the hub <NUM> through the second connection port, such that power signals may be transmitted through the hub to the sterile environment user interfaces <NUM> and <NUM> between data acquisition procedures. Alternatively, the links <NUM> and <NUM> may be transmitted over one or more cables between the processing engine <NUM> and the hub. According to other examples, a hub extender may be used to establish the connection between the hub <NUM> and the digital imager <NUM> and imaging peripherals <NUM>. According to further examples, the hub extender may be used in place of the hub <NUM>. For example, the hub extender may have a fixed connection to the processing engine <NUM>, such that when the plug and socket of the hub extender are engaged, the hub extender completes a connection between the processing engine <NUM> and the imaging peripherals <NUM> and digital imager <NUM>.

Alternatively, as shown in <FIG>, the hub <NUM> may be connected to a hub extender <NUM>. In this configuration, the hub <NUM> is connected to the remote processing engine and another connection method links the hub to a separate housing. The separate housing may be a hub extender <NUM>. The hub extender may have a socket configured to receive the plug from the digital imager <NUM> that is inserted into the socket. Both power and data signals are transmitted between the digital imager <NUM> and the hub extender <NUM>, described more fully below regarding <FIG>. The hub extender <NUM> allows for the hub <NUM> to be located further away from the digital imager <NUM> and imaging peripherals <NUM>, allowing for a more organized patient procedure environment. The hub extender <NUM> could also be directly connected to the processing engine <NUM>, without the need for hub <NUM>.

There may also be a light indicator <NUM> on the hub <NUM> and/or hub extender <NUM>. The light indicator <NUM> may communicate status of the components to the user, such that the user can quickly and efficiently identify the status of each component and troubleshoot any issues. Though the light indicator <NUM> is depicted on the hub <NUM>, all components of the modular imaging acquisition and processing system <NUM> may be individually equipped with light indicators.

Conventionally, imaging peripherals and a processing engine may be packaged in the form of a mobile cart that can be transported from one lab into another in the hospital when the need arises. With this conventional configuration, a multitude of connections are made to the cart prior to the imaging procedure. The cart needs to be connected to power source within the procedure room. To import patient specific data, such as the name of the patient, the intervening physician, and other parameters necessary to uniquely identify the procedure, the cart must be connected to the hospital's network. In order to correlate results from the intravascular imaging procedure with simultaneously captured angiographic images, the cart must be connected to the angiography system. Using the current configuration, the mobile cart is not within the sterile field of the procedure room, thus the cart must be attached to user interface devices, such as joysticks and/or touch screens, so the user may control the imaging tools. Thus, when the mobile imaging cart is brought into the procedure room to perform intravascular diagnosis, the technician in charge will have to spend time connecting the cart independently to a power outlet, angiograph video feed, hospital LAN, bed monitor, and any user interface devices in use. This is a time-consuming endeavor which can lead to delays and mistakes. Specifically, after the system is wheeled in, the cart must be plugged into a power outlet, and the technician must wait until the system is powered up before they can start setting up the system for the procedure. This introduces several minutes delay to the start of the procedure. Also, power outlets are often difficult to access in the procedure room and may be located away from the procedure table creating tripping hazards for the procedure room personnel. Additionally, connections to the angiograph, the boom monitor, the hospital network, and the user interface devices all require separate cables and demand attention to detail. Often, given the pressure to speed up the procedure, the technician may neglect to perform a connection, and this introduces further delays while the system attempts to diagnose the problem.

The example modular system described herein is advantageous over conventional mobile cart configurations as it facilitates seamless connections and expedites pre-procedure preparations, thereby reducing the time between entering the procedure room and the system being procedure-ready. For example, the system described in the example of <FIG> would introduce a small, rugged connection system, such as in the hub or hub extender, conveniently stationed within the procedure room. The connection system may be positioned at the edge of the bed, or elsewhere in the procedure environment. In this configuration, the imaging mobile cart may be coupled with the entire modular system by inserting a single cable into the connection system when wheeled into the procedure lab. This connection system carries both power and data communications between components. As such, the coupling of the connection system allows the imaging engine to be ready for use in seconds. Moreover, it allows for reliable coupling of the digital imager and peripherals to the rest of the modular system, reducing the possibility of errors or failures due to improper connections. The hub and/or the hub extender may maintain a persistent connection with a power source through the processing engine, which would reduce the time required to start up the modular system. This persistent connection would be useful in emergency situations when time and space in the patient procedure room is limited. Moreover, it similarly provides a reliable connection, as the persistent coupling can be maintained between procedures, thereby reducing a potential for misconnections or mishandling of the couplings.

Referring to <FIG>, in one example the modular imaging acquisition and processing system <NUM> may include a processing engine <NUM>, a digital imaging engine <NUM>, and imaging peripherals <NUM>. In some configurations, there may be a hub inside the processing engine <NUM>. The modular system may be positioned with respect to other components in the patient procedure environment, such as a support <NUM>, a first link <NUM>, imaging peripherals <NUM>, a boom monitor <NUM>, cart user interface <NUM>, and cart monitor <NUM>. The system <NUM> of <FIG> is configured to allow similar remote and proximal positioning of different system components as otherwise described herein with different embodiments.

As shown in <FIG>, the system <NUM> may include a cart <NUM> equipped with the processing engine <NUM>, a hub, the digital imagine engine <NUM>, cart user interface <NUM>, cart monitor <NUM>, and holster <NUM>. The holster <NUM> may be configured to receive the imaging peripherals <NUM>, similar to the holster described with respect to <FIG>. One benefit of a fully mobile solution, as shown in <FIG>, is that the user can perform an OCT case in a lab with no installed OCT components. In some examples, the cart <NUM> and all components may be communicatively connected to the procedure room via a support interface <NUM>. The support interface may connect the components on cart <NUM>, including the processing engine <NUM>, hub, the digital imaging engine <NUM>, cart user interface <NUM>, cart monitor <NUM>, and the holster <NUM>. The support interface <NUM> may receive and send signals to the connected components and the procedure room. In some examples, additional processing may occur at support interface <NUM>. As depicted in <FIG>, a remote processing room may not be needed in the described modular system where the processing engine may be placed on a cart.

Referring to <FIG>, in yet another example, the modular imaging acquisition and processing system <NUM> may include a processing engine <NUM>, a digital imaging engine <NUM>, a holster <NUM>, and imaging peripherals <NUM>. The modular system may be positioned with respect to other components in the patient procedure environment, such as a support <NUM>, a sterile environment user interface <NUM>, a link <NUM>, and a remote user interface <NUM>. The system <NUM> of <FIG> is configured to allow similar remote and proximal positioning of different system components as otherwise described herein with different embodiments. When configured as a system, the processing engine <NUM>, and the remote user interface <NUM> may be located in a separate control room and connected to the patient procedure environment through link <NUM>.

As depicted in <FIG>, the digital imaging engine <NUM>, holster <NUM> and imaging peripherals <NUM> may be positioned remotely from the patient support <NUM>. In some examples, the digital imaging engine <NUM>, holster <NUM> and imaging peripherals <NUM> may be connected to the rest of the system <NUM> via a ceiling mounted arm <NUM>. In some embodiments the ceiling mounted arm may include wired connections within the arm that facilitate a connection of the imaging engine <NUM> and imaging peripherals <NUM> to the system <NUM>. By concealing the wires and cords that facilitate the connection of the imaging engine <NUM> and imaging peripherals <NUM> to the modular components of system <NUM>, clutter in the patient procedure environment is reduced. In some embodiments, the imagining engine <NUM> and imaging peripherals may be connected to modular components of system <NUM> via wireless connection.

In some examples, there may be a hub mounted on arm <NUM>. The hub may enable connectivity between the mounted components and components inside and outside of the procedure room. For example, the hub may enable a connection between the digital imaging engine <NUM> and imaging perihpherals <NUM> and the components inside the procedure room, such as the sterile enivonment user interface <NUM>. Additionally, the hub may enable a connection between the digital imaging engine <NUM> and imaging perihpherals <NUM> and the components outside the procedure room, such as the processing engine <NUM>.

Referring to <FIG>, in one embodiment a hub <NUM> may include a controller <NUM>, a lighting control module <NUM>, at least one indicator <NUM>, a first input <NUM>, and a second input <NUM>. The hub <NUM> may have a single housing containing the controller <NUM>, lighting control module <NUM>, at least one indicator <NUM>, the first input <NUM>, and a second input <NUM>. The hub may be connected to the digital imager <NUM>. The digital imager <NUM> may be connected to imaging peripherals <NUM>. The digital imager <NUM> may be connected to the imaging peripherals <NUM> by a link <NUM>. Alternatively, the digital imager <NUM> may be connected to the imaging peripherals <NUM> by wired or wireless connection. Further, in some embodiments, hub <NUM> may be connected to user interface modules <NUM> and <NUM>.

The hub <NUM> is configured to facilitate efficient connection of the digital imager <NUM> and the imaging peripherals <NUM>. The hub <NUM> is connected to a remote processing engine via links <NUM> and <NUM>. The link <NUM> may transmit data signals between the processing engine <NUM> and the hub <NUM>. The link <NUM> may transmit power signals between the processing engine <NUM> and the hub <NUM>. Between and during procedures, the link <NUM> may allow power signals to be transmitted to the hub <NUM> between data acquisition procedures. Alternatively, the links <NUM> and <NUM> may be transmitted over one or more cables between the processing engine <NUM> and the hub <NUM>.

The hub <NUM> and the digital imager <NUM> may be connected through the data interface <NUM> and the power switch <NUM>. The data interface <NUM> transmits data signals between the digital imager <NUM> and the hub <NUM>. The power switch <NUM> transmits power signals between the digital imager <NUM> and the hub <NUM>. Alternatively, in some examples, the connection between the digital imager <NUM> and the hub <NUM> may be through one cable.

The hub <NUM> contains a power control <NUM>. The power control <NUM> detects a connection to the digital imager <NUM> and can activate power switch <NUM>, and vice versa. The power control <NUM> may prevent the routing of a power signal to the power switch <NUM> when not in use, such that when no plug is inserted into the power switch <NUM> no electrical current runs to the power switch <NUM>. This feature provides additional safety precautions by preventing power surges and sparks.

The hub <NUM> remains connected to the remote processing engine via the data link <NUM>. For example, link <NUM> may establish a persistent connection between the hub <NUM> and the remote processing engine, such that link <NUM> is not disconnected between procedures. The hub <NUM> contains a communication controller <NUM> that may transfer signals received from the remote processing engine and the digital imager <NUM>.

The hub <NUM> may be connected to user interface modules <NUM> and <NUM> via a wired connection. The wired connection may be USB, Thunderbolt, or other cables for power and data transmission known in the art. The hub <NUM> receives commands and data from the user interface modules <NUM> and <NUM>, then routes the data through the communication controller to other components of the modular system via the processing engine or the digital imager <NUM>. The user interface modules may be any data input devices, such as a touch screen, joystick, control panel, monitor with a keyboard or mouse. Alternatively, in some examples, there may be one or more user interface modules for a user to input commands into the modular system.

In another example there may be a hub extender between the hub <NUM> and the digital imager <NUM>. The hub extender may facilitate serial communications between the digital imager <NUM> and the processing engine.

Alternatively, in some examples there may be no hub <NUM> present and the components of the hub <NUM>, as described in <FIG> may be housed and connected in a hub extender. For example, the hub extender may include a controller <NUM>, a lighting control module <NUM>, at least one indicator <NUM>, a first input <NUM>, and a second input <NUM>. The hub extender may have a single housing containing the controller <NUM>, lighting control module <NUM>, at least one indicator <NUM>, the first input <NUM>, and a second input <NUM>. The hub extender may be connected to the digital imager <NUM>. The digital imager <NUM> may be connected to imaging peripherals <NUM>. The digital imager <NUM> may be connected to the imaging peripherals <NUM> by a link <NUM>. Alternatively, the digital imager <NUM> may be connected to the imaging peripherals <NUM> by wired or wireless connection. Further, in some embodiments, hub extender may be connected to user interface modules <NUM> and <NUM>. The hub extender is configured to facilitate efficient connection of the digital imager <NUM> and the imaging peripherals <NUM>. The hub extender is connected to a remote processing engine via links <NUM> and <NUM>. The link <NUM> may transmit data signals between the processing engine <NUM> and the hub extender. The link <NUM> may transmit power signals between the processing engine <NUM> and the hub extender. The link <NUM> may allow power signals to be transmitted to the hub extender during data acquisition procedures. The link <NUM> may be fixed to the hub extender and also fixed to the remote processing engine <NUM>. As such, the procedure environment may be prepared more expeditiously as compared to a system where such connection would need to be established prior to each procedure.

The hub extender and the digital imager <NUM> may be connected through the data interface <NUM> and the power switch <NUM>. The data interface <NUM> transmits data signals between the digital imager <NUM> and the hub extender. The power switch <NUM> transmits power signals between the digital imager <NUM> and the hub extender. The connection between the digital imager <NUM> and the hub extender may be established through one or multiple cables.

The hub extender may contain a power control <NUM>. The power control <NUM> detects a connection to the digital imager <NUM> and can activate power switch <NUM>, and vice versa. The power control <NUM> may prevent the routing of a power signal to the power switch <NUM> when not in use, such that when no plug is inserted into the power switch <NUM> no electrical current runs to the power switch <NUM>. This feature provides additional safety precautions by preventing power surges and sparks.

The hub extender may remain connected to the remote processing engine via the data link <NUM>. For example, link <NUM> may establish a persistent connection between the hub extender and the remote processing engine, such that link <NUM> is not disconnected between procedures. The hub extender may contain a communication controller <NUM> that may transfer signals received from the remote processing engine and the digital imager <NUM>.

The hub extender may be connected to user interface modules <NUM> and <NUM> via a wired connection. The wired connection may be USB, Thunderbolt or other data transmission cables. The hub extender receives commands and data from the user interface modules <NUM> and <NUM>, then routes the data through the communication controller to other components of the modular system via the processing engine or the digital imager <NUM>. The user interface modules may be any data input devices, such as a touch screen, joystick, control panel, monitor with a keyboard or mouse. Alternatively, in some examples, there may be one or more user interface modules for a user to input commands into the modular system.

Referring to <FIG>, the digital imager may include a plug <NUM>, having a first mating surface including a power interface <NUM> and a data interface <NUM>, and a cable <NUM> to a digital imaging engine. The system may also include a socket <NUM>, having a second mating surface, including a power receptacle <NUM> and a data receptacle <NUM> configured to mate with the power interface <NUM> and data interface <NUM>, and cables <NUM> and <NUM> to a processing engine. Socket <NUM> may be an integral part of the hub. In alternate example, the socket <NUM> may be an integral part of a hub extender. When assembled together, the plug <NUM> and the socket <NUM> create a hub connection system. The hub connection system serves to connect the hub of the modular system to the digital imager and imaging peripherals.

Referring to <FIG>, in some examples, the plug <NUM> may facilitate a connection between the digital imager and the hub of the modular system via the cable <NUM>. The cable <NUM> extends from the digital imager. The cable <NUM> transmits both data and power signals between the digital imager and the hub. Referring to <FIG>, in some examples, the socket <NUM> may facilitate a connection between the digital imager and the hub of the modular system via cables <NUM> and <NUM>. In another example, the socket <NUM> may facilitate a connection between the digital imager and the hub extender. Cables <NUM> and <NUM> may connect the hub to the processing engine. The cables <NUM> and <NUM> may independently transmit data and power signals from a remote processing engine. Alternatively, in some examples, data and power signals between the hub and the remote processing engine may be one or more cables.

In some examples, the hub connection system is configured to transmit a power signal through the power interface <NUM>. The power interface <NUM> connects to the socket at the power receptacle <NUM>. Similarly, the hub connection system is configured to transmit data signals through the data interface <NUM>. The data interface <NUM> connects to the socket at the data receptacle <NUM>. The connection may support the Thunderbolt, Ethernet, USB, or other serial communication protocol.

The plug <NUM> may have a first mating surface that is configured to connect to the second mating surface of the socket <NUM>. The mating surfaces may allow for a robust mechanical fit between the plug <NUM> and the socket <NUM>. For example, the socket <NUM> may form a receptacle sized and shaped corresponding to a plug <NUM>, such that the plug <NUM> can be inserted into the socket <NUM> and retained therein until it is removed. Moreover, the mating surfaces may facilitate proper orientation of the power interface <NUM> to the power receptacle <NUM> and the data interface <NUM> to the data receptacle <NUM>. The mechanical fit between the plug and the socket may be facilitated by magnets, interlocking mechanical features, or a sliding rail system. For example, there may be magnets having one polar charge on the socket and magnets having an opposing polar charge on the plug. In another example, the socket may have grooves and the plug may have retractable arms that interlock into the grooves when placed into the socket. In yet another example, the socket may have a track and the plug may have a rail configured to slide into the rail. While the faces of the plug <NUM> and the socket <NUM> are illustrated as having a particular size, shape and orientation, the connection can be established through the first and second mating surfaces including interfaces not shown.

In another example, the hub may be removable. The hub may be anchored into a hub mount. The hub may be removably docked to a support, underneath the support, or anywhere else in the patient procedure environment. The hub may be connected to the hub mount by a mechanical fit. For example, the hub mount may form a receptacle sized and shaped corresponding to the hub, such that the hub can be inserted into the hub mount and retained therein until it is removed. Engaging the hub with the hub mount be assisted through the use of placement mechanisms, such as magnets, interlocking mechanical features, or a sliding rail system. For example, there may be magnets having one polar charge on the hub mount and magnets having an opposing polar charge on the hub. In another example, the hub mount may have grooves and the hub may have retractable arms that interlock into the grooves when placed into the hub mount. In yet another example, the hub mount may have a track and the hub may have a rail configured to slide into the rail.

In some examples, the hub connection system may be connected to a hub extender where the hub is separate from the plug and socket described above. In this configuration, the hub is connected to the remote processing engine and another connection method links the hub to a separate housing. The separate housing may be a hub extender that has the socket. The plug from the digital imager is inserted into the socket. As described above, power and data signals are transmitted between the digital imager and the hub through the power interface <NUM> and data interface <NUM>, respectively. The hub extender allows for the hub to be located further away from the digital imager and imaging peripherals. This configuration allows for a more organized patient procedure environment.

In another example, the hub extender may be removable. The hub extender may be anchored into a hub mount. The hub extender may be removably mounted to a support, underneath the support, or anywhere else in the patient procedure environment. The hub extender may be connected to the hub mount by a mechanical fit. For example, the hub mount may form a receptacle sized and shaped corresponding to the hub, such that the hub can be inserted into the hub mount and retained therein until it is removed. Engaging the hub extender with the hub mount may be assisted using placement mechanisms, such as magnets, interlocking mechanical features, or a sliding rail system. For example, there may be magnets having one polarity on the hub mount and magnets having the opposing polarity on the hub extender. In another example, the hub mount may have grooves and the hub extender may have retractable arms that interlock into the grooves when placed into the hub mount. In yet another example, the hub mount may have a track and the hub extender may have a rail configured to slide into the rail.

While a number of example configurations are described above, numerous other configurations of the modular system are possible. By way of example, the digital imager may be within the sterile field of the patient procedure environment. The digital imager may include a digitizer. The digital imager may be coupled to a remote processing engine residing outside the patient procedure environment. The digital imager may be outside of the patient procedure room. The digital imager may be positioned on a mobile cart. The digital imager may be positioned on the support. The digital imager may be positioned on the bed. The digital imager may be positioned under the support. The digital imager may be positioned under the bed. The digital imager may be attached to the boom monitor. The digital imager may be within the same housing as the imaging peripherals. The digital imager may be within the same housing as at least some of the set of imaging peripherals. The digital imager may be in a housing separate from the imaging peripherals. The digital imager may be docked in a holster with the imaging peripherals. The digital imager may be docked separately from the imaging peripherals. The digital imager may be communicatively coupled to a user interface. The digital imager may be communicatively coupled to a monitor. The digital imager may be communicatively coupled to a touch screen. The digital imager may be communicatively coupled to a user interface on a mobile cart. The digital imager may be communicatively coupled to a user interface at the patient side. The digital imager may be communicatively coupled to a remote user interface. The digital imager may connect to the modular system with or without a hub.

The digital imager may connect to the modular system via a hub. The digital imager may connect to the hub through a single plug. The digital imager may connect the hub through multiple plugs. The digital imager may connect to the hub via a removable connection. The digital imager may connect to the hub via a fixed connection. The hub may be positioned on the support. The hub may be positioned on a bed. The hub may be positioned under the support. The hub may be positioned under the bed. The hub may be within the sterile field of the patient procedure environment. The hub may be outside of the sterile field of the patient procedure environment. The digital imager may connect to the modular system via a hub extender, which may be used in addition to or in place of the hub. The digital imager may connect to the hub extender through a single plug. The digital imager may connect to the hub extender through multiple plugs. The digital imager may connect to the hub extender via a removeable connection. The digital imager may connect to the hub extender via a fixed connection. The hub extender may be positioned on a support. The hub extender may be positioned on a bed. The hub extender may be positioned underneath a support. The hub extender may be positioned on a bed. The hub extender may be positioned underneath a bed. The hub extender may be positioned within the sterile field of the patient procedure environment. The hub extender may be outside of the sterile environment of the patient procedure environment. In any of these examples, the digital imager may include a digitizer. The digital imager may be coupled to a remote processing engine residing outside the patient procedure environment. The digital imager may be outside of the patient procedure room. The digital imager may be positioned on a mobile cart. The digital imager may be positioned on the support. The digital imager may be positioned on the bed. The digital imager may be positioned under the support. The digital imager may be positioned under the bed. The digital imager may be attached to the boom monitor. The digital imager may be within the same housing as the imaging peripherals. The digital imager may be within the same housing as at least some of the set of imaging peripherals. The digital imager may be in a housing separate from the imaging peripherals. The digital imager may be docked in a holster with the imaging peripherals. The digital imager may be docked separately from the imaging peripherals. The digital imager may be communicatively coupled to a user interface. The digital imager may be communicatively coupled to a monitor. The digital imager may be communicatively coupled to a touch screen. The digital imager may be communicatively coupled to a user interface on a mobile cart. The digital imager may be communicatively coupled to a user interface at the patient side. The digital imager may be communicatively coupled to a remote user interface. The digital imager may connect to the modular system with or without a hub.

In some configurations, a hub may be used for interconnection of components of the modular system, such that some components maintained a fixed connection to the hub while other components are quickly connected to the hub prior to a procedure. The hub may be on a cart. The hub may be on a support. The hub may be a bed. The hub may be under a support. The hub may be under a bed. The hub may be within the sterile field of the patient procedure environment. The hub may be outside the sterile field of the patient procedure environment. The hub may be attached to a boom monitor. The hub may have one connection port. The hub may have two connection ports. The hub may have three connection ports. The hub may have four connection ports. The hub may have multiple connection ports. The hub may be connected to a processing engine. The hub may be connected to the processing engine by a removeable connection. The hub may be connected to the processing engine by a fixed connection. The processing engine may be outside of the patient procedure environment. The hub may be connected to the processing engine by a removeable connection. The hub may be connected to the processing engine by a fixed connection. The processing engine may be connected to the hub via one cable. The processing engine may be connected to the hub via two cables. The processing engine may be connected to the hub via multiple plugs. The hub may be connected to the user interfaces within the sterile field of the patient procedure environment. The hub may be connected to the user interfaces by a removable connection. The hub may be connected to the user interfaces by a fixed connection. The hub may be connected to user interfaces via one cable. The hub may be connected to the user interfaces via two cables. The hub may be connected to user interfaces via multiple cables. The hub may be connected to a digital imager via a single plug. The hub may be connected to a digital imager and imaging peripherals. The hub may be connected to a digital imager, imaging peripherals, and a user interface.

The hub may be connected to a hub extender. The hub extender may include a plug and socket configuration, or other configuration with mating connections. The hub may be connected to a digital imager via the hub extender. The hub may be connected to a hub extender through a fixed connection. The hub may be connected to a hub extender through a removable connection. The hub extender may be connected to the modular system through a hub. The hub extender may be connected to the modular system without connection to a hub. The hub extender may be on a mobile cart. The hub extender may be positioned on a support. The hub extender may be positioned on a bed. The hub extender may be positioned under the support. The hub extender may be positioned under a bed. The hub extender may be within the sterile field of the patient procedure environment. The hub extender may be outside of the sterile field of the patient procedure environment. The hub extender may be attached to the boom monitor. The hub extender may have one connection port. The hub extender may have two connection ports. The hub extender may have multiple connection port. The hub extender may connect the digital imager to the rest of the modular system. The hub extender may connect the digital imager and the imaging peripherals to the rest of the modular system. The hub extender may connect the digital imager, imaging peripherals, and a user interface to the rest of the modular system.

The hub extender may be used without the hub. The hub extender may include a plug and socket configuration, or other configuration with mating connections. One end of the mating connection may couple with the remote processor while another end of the mating connection couples with the digital imager. The hub extender may be on a mobile cart. The hub extender may be positioned on a support. The hub extender may be positioned on a bed. The hub extender may be positioned under the support. The hub extender may be positioned under a bed. The hub extender may be within the sterile field of the patient procedure environment. The hub extender may be outside of the sterile field of the patient procedure environment. The hub extender may be attached to the boom monitor. The hub extender may have one connection port. The hub extender may have two connection ports. The hub extender may have multiple connection port. The hub extender may connect the digital imager to the rest of the modular system. The hub extender may connect the digital imager and the imaging peripherals to the rest of the modular system. The hub extender may connect the digital imager, imaging peripherals, and a user interface to the rest of the modular system.

Claim 1:
A portable digital imager for processing intravascular diagnostic data, the portable digital imager (<NUM>, <NUM>) comprising:
a first interface arranged to couple the digital imager to a set of imaging peripherals (<NUM>, <NUM>, <NUM>);
an analog imager (<NUM>, <NUM>, <NUM>) configured to receive analog image data from the imaging peripherals and convert the analog image data into analog electrical signals;
a digitizer (<NUM>) arranged to communicate with the analog imager to convert the analog electrical signals into digital image data;
a controller (<NUM>) arranged to communicate with the digitizer, the controller adapted to convert the digital image data to serial communication data; and
a second interface arranged to couple the digital imager to a communication link configured to transmit the serial communication data to a remote processing engine (<NUM>, <NUM>, <NUM>).