The present disclosure relates to a medical device interface, and more particularly, the present disclosure relates to an interface between a medical monitoring platform and a monitoring module.
A patient monitoring platform interface is provided to communicatively couple a patient monitoring platform device to a monitoring module. The monitoring module may communicate physiological information (e.g., physiological parameter values, sensor signal data) to the platform device. In some embodiments, the patient monitoring platform interface includes a plurality of pins (e.g., an array of 20 pins) configured to electrically and communicatively couple the patient monitoring platform and the monitoring module. The plurality of pins may include at least two pins configured for receiving universal asynchronous receiver/transmitter (UART) communication, at least two pins configured for transmitting UART communication, at least one pin configured for communicating diagnostic information (e.g., whether devices are coupled, whether sufficient power has been provided), at least one pin configured to couple to a ground (e.g., a ground for regulated power, unregulated power, digital data reference), at least one pin configured as a clock, at least one pin configured to receive and transmit serial communications, at least one pin configured as a regulated power supply, and at least two pins configured to a suitable universal serial bus specification.
The above and other features of the present disclosure, its nature and various advantages will be more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings in which:
The present disclosure is directed towards a connection interface between a platform device and a module device that are configured to be communicatively coupled to one another. In some embodiments, the platform device and module device may be part of a physiological monitoring system.
For example,
Platform device 102 may include any suitable hardware, software, or both for implementing a device that may be used as a platform for a physiological monitoring system. For example, platform device 102 may include a display device as well as any other suitable input/output mechanisms for receiving input from a clinician or other user of physiological monitoring system 100 and for providing output to a clinician or other user of physiological monitoring system 100. Platform device 102 may include any suitable processing circuitry for determining physiological information from information provided by monitoring module 110.
In some embodiments, platform device 102 may be a standalone physiological monitor such as a pulse oximeter and may be used without monitoring module 110. In this case, platform device 102 may be directly coupled to sensors for receiving suitable physiological signals.
Monitoring module 110 may be any suitable software, hardware, or both for calculating or otherwise determining physiological information from physiological signals received from, for example, one or more sensors 112. Physiological information may include sensor signal data, physiological parameter data (e.g., values, trends), any other suitable information, or any combination thereof. In some embodiments, monitoring module 110 may condition or otherwise process (e.g., filter, sample, average, amplify, modulate, transform) a signal received from one or more sensors and communicate the conditioned signal to platform device 102. Sensors 112 may include photoplethysmograph (PPG) sensors, respiratory sensors, electrocardiograph (EKG) sensors, electroencephalograph (EEG) sensors, electromyograph (EMG) sensors, temperature sensors, blood pressure sensors, any other suitable type of physiological sensor, or any combination thereof. Monitoring module 110 may communicate sensor signals, calculated physiological parameter values, calculated physiological parameter trend values, alarm data, message data, status data, device identification data, any other suitable information, or any combination thereof to platform device 102. For example, monitoring module 110 may provide one or more physiological parameters to platform 102 by communicating information indicative of the physiological parameters using wired connection 106 and any suitable ports that interface wired connection 106 between platform device 102 and monitoring module 110.
Monitoring module 110 may be configured to calculate one or more physiological parameters of a patient such as blood oxygen saturation, pulse rate, respiration rate or any other suitable respiratory activity, blood pressure (e.g., systolic, diastolic, or both), blood glucose concentration, any other suitable physiological parameter, or any combination thereof. Monitoring module 110 may be configured to calculate physiological parameter trend data such as, for example, statistical parameters (e.g., an average, a moving average, standard deviation, least squares curve-fit parameters), a change (e.g., a deviation, a relative difference), a rate of change (e.g., a slope, a derivative), any other suitable calculated values, or any combination thereof.
In some embodiments, monitoring module 110 may be a standalone physiological monitoring device such as a pulse oximeter. In some embodiments, in order for monitoring module 110 to be functional, it must be coupled to platform device 102. For example, platform device 102 may be configured to power monitoring module 110 using particular terminals of connectors 104 and 108, and particular wires of wired connection 106. In such an arrangement, monitoring module 110 may not be able to obtain power to function unless coupled to platform device 102 (although, if desired, monitoring module 110 may also be able to obtain power from other external power sources). Monitoring module 110 need not have any display interface or otherwise provide an indication of any information to a clinician or user of physiological monitoring system 100. If desired, however, any suitable indicators or information display may be provided on monitoring module 110. In some embodiments, monitoring module 110 may provide functionality that platform device 102 does not provide, any may be thus used to upgrade the functionality of platform device 102.
The arrangement of platform device 102 and monitoring module 110 may be such that they are apart from one another and wired connection 106 may extend from the location of monitoring module 110 to the location of platform device 102. Alternatively, platform device 102 and monitoring module 110 may be arranged such that they are closely spaced relative to one another and may be physically attached to one another. For example, monitoring module 110 may latch onto platform device 102 using any suitable latching mechanism.
In some embodiments, monitoring module 208 may include connector 212 which is used to connect monitoring module 208 to another monitoring module (not shown but with the same or different functionality compared to monitoring module 208) or other suitable external device, or any combination thereof.
In some embodiments, connector 300 includes electrical terminals 304 which are each electrically coupled to corresponding wires 314. Wires 314 may include electrical insulation, which may prevent shorting or electrical contact between different wires. Wires 314 may be bundled, twisted, sheathed or otherwise arranged in a collection (e.g., a ribbon cable, a sheathed 20-conductor cable). In some embodiments, wires 314 may electrically couple to an additional connector (not shown), circuitry of an electronic device (not shown), or any combination thereof. Electrical terminals 304 may be blades, tabs, sockets, pins, any other suitable type electrical terminal which may be included in a connector, or any combination thereof. Electrical terminals (e.g., electrical terminals 304) and wires (e.g., wires 314) may be configured to transmit direct current (DC) power, alternating current (AC) power, analog signals, digital signals, any other suitable electrical activity, or any suitable combination thereof.
In some embodiments, connector 306 includes electrical terminals 310, which may correspond to electrical terminals 304 of connector 300. For example, connectors 300 and 306 may be connected (e.g., connector 300 may be plugged into connector 306), creating contact between electrical terminals 304 and corresponding terminals of electrical terminals 310. Connecting connector 300 to connector 306 may include inserting male connector portion 302 into female connector portion 308 to create the contact between electrical terminals 304 and electrical terminals 310. In some embodiments, electrical terminals 304 may be arranged on male connector portion 302, and electrical terminals 310 may be arranged in female connector portion 308. In some embodiments, electrical terminals 304 may be pins arranged in a suitable array, and may correspond to electrical terminals 310 which may be holes arranged in a corresponding array. Electrical continuity among corresponding terminals may be formed by plugging the male connector into the female connector, allowing communication among devices electrically coupled to the respective connectors. Connector 300, connector 306, or both, may function as input/output ports for suitable devices (e.g., a patient monitoring platform, a monitoring module).
In an illustrative example, connectors 300 and 306 may be a Molex 45985-0433 male connector and a Molex 46133-0203 female receptacle both manufactured by Molex of Lisle, Ill., respectively, in which the male connector is configured to plug into the female connector. One or both connectors may be soldered or otherwise electrically coupled to a printed circuit board or other suitable circuit arrangement.
In an illustrative example, illustrative platform interface 400 may include 20 pins as shown in
Platform interface 400 may include one or more pins for supplying regulated DC power to a monitoring module, as shown by pins 1 and 11 of
Platform interface 400 may include one or more pins for transmitting power, data, or both, using a suitable USB specification (e.g., USB 1.1, 2.0, 3.0). In some embodiments, two pins may be used for digital data transfer, as shown by pins 9 and 19 of
Platform interface 400 may include one or more pins for communicating diagnostic information, as shown by pins 6 and 16 of
Platform interface 400 may include one or more grounding pins, as shown by pins 8, 10, 18, and 20 of
Platform interface 400 may include one or more pins configured for communicating using the I2C interface, as shown by pins 2 and 12 of
Platform interface 400 may include one or more pins configured to receive UART communications, as shown by pins 14 and 15 of
Platform interface 400 may include one or more pins which are not configured, capable of being configured as desired, reserved for future use, or otherwise not functionally assigned, as shown by pins 3 and 13 of
Although illustratively shown as having 20 pins, platform interface 400 may include any suitable number of pins, arranged in any suitable array which may be, but need not be, patterned. Pins may be arranged in any suitable order according to functionality, polarity, signal type, power level, any other suitable designation, or any combination thereof. Although discusses as “pins”, the terminals of platform interface may include any suitable geometry such as, for example, tabs, blades, holes, sockets, any other suitable electrical terminal type, or any combination thereof. In some embodiments, a platform interface may include pins configured according to standards such as, for example, IEEE 1394, parallel small computer system interface (SCSI), serial data interface at 1200 Baud (SDI-12), recommended standard 422 (RS-422), any other suitable standards for data communication, or any combination thereof.
Number | Name | Date | Kind |
---|---|---|---|
5375604 | Kelly et al. | Dec 1994 | A |
5491781 | Gasperina | Feb 1996 | A |
5724025 | Tavori | Mar 1998 | A |
5830150 | Palmer et al. | Nov 1998 | A |
5871451 | Unger et al. | Feb 1999 | A |
5912656 | Tham et al. | Jun 1999 | A |
5957838 | Rantala | Sep 1999 | A |
6093146 | Filangeri | Jul 2000 | A |
6152754 | Gerhardt et al. | Nov 2000 | A |
6221012 | Maschke et al. | Apr 2001 | B1 |
6325540 | Lounsberry et al. | Dec 2001 | B1 |
6352504 | Ise et al. | Mar 2002 | B1 |
6402691 | Peddicord et al. | Jun 2002 | B1 |
6544173 | West et al. | Apr 2003 | B2 |
6544174 | West et al. | Apr 2003 | B2 |
6579231 | Phipps | Jun 2003 | B1 |
6584336 | Ali et al. | Jun 2003 | B1 |
6658276 | Kianl et al. | Dec 2003 | B2 |
6684090 | Ali et al. | Jan 2004 | B2 |
6770028 | Ali et al. | Aug 2004 | B1 |
6792396 | Inda et al. | Sep 2004 | B2 |
6820050 | Simmon et al. | Nov 2004 | B2 |
6850788 | Al-Ali | Feb 2005 | B2 |
6947780 | Scharf | Sep 2005 | B2 |
6996427 | Ali et al. | Feb 2006 | B2 |
7002468 | Eveland et al. | Feb 2006 | B2 |
7249036 | Bayne | Jul 2007 | B2 |
7316648 | Kelly et al. | Jan 2008 | B2 |
7373193 | Al-Ali et al. | May 2008 | B2 |
7383358 | Kennedy | Jun 2008 | B1 |
7530949 | Ali et al. | May 2009 | B2 |
7542878 | Nanikashvili | Jun 2009 | B2 |
7657849 | Chaudhri et al. | Feb 2010 | B2 |
7702382 | Xue et al. | Apr 2010 | B2 |
7887345 | Wong et al. | Feb 2011 | B2 |
8046721 | Chaudhri et al. | Oct 2011 | B2 |
8131564 | Dicks et al. | Mar 2012 | B2 |
8208853 | Lydon et al. | Jun 2012 | B2 |
8238811 | Lydon | Aug 2012 | B2 |
8286103 | Chaudhri et al. | Oct 2012 | B2 |
8315683 | Al-Ali et al. | Nov 2012 | B2 |
20060094936 | Russ | May 2006 | A1 |
20060098666 | Powell et al. | May 2006 | A1 |
20060229503 | Fluegel | Oct 2006 | A1 |
20060235281 | Tuccillo | Oct 2006 | A1 |
20070004971 | Riley et al. | Jan 2007 | A1 |
20070282177 | Pilz | Dec 2007 | A1 |
20080045809 | Hermannsson | Feb 2008 | A1 |
20080081954 | Meyer et al. | Apr 2008 | A1 |
20080097550 | Dicks et al. | Apr 2008 | A1 |
20080097917 | Dicks et al. | Apr 2008 | A1 |
20080103554 | Dicks et al. | May 2008 | A1 |
20080114221 | Tso | May 2008 | A1 |
20080191866 | Falck et al. | Aug 2008 | A1 |
20080221404 | Tso | Sep 2008 | A1 |
20080294462 | Nuhaan et al. | Nov 2008 | A1 |
20090325408 | Wong et al. | Dec 2009 | A1 |
20110077473 | Lisogurski | Mar 2011 | A1 |
20110077487 | Buxton et al. | Mar 2011 | A1 |
20110077488 | Buxton et al. | Mar 2011 | A1 |
20110078596 | Rawlins et al. | Mar 2011 | A1 |
20110125601 | Carpenter et al. | May 2011 | A1 |
20120029304 | Medina et al. | Feb 2012 | A1 |
20120190944 | Thaveeprungsriporn et al. | Jul 2012 | A1 |
20120311219 | Ma et al. | Dec 2012 | A1 |
Number | Date | Country |
---|---|---|
WO 2005114524 | Dec 2005 | WO |
WO 2006006107 | Jan 2006 | WO |
WO 2006064397 | Jun 2006 | WO |
WO 2010027694 | Mar 2010 | WO |
Entry |
---|
Molex—“Part No. 45985-0443—1.27mm Pitch, EXTreme LPHPower Plug with Guides and Pegs”; 2 pages, Dated Oct. 18, 2012. |
“Apple iPod, iPad and iPhone dock Connector Pinout—AllPinouts”; 3 pages, Dated Sep. 27, 2010. |
International Search Report for Application No. PCT/US2012/040084, 4 pages, mailed on Aug. 2, 2012. |
Number | Date | Country | |
---|---|---|---|
20120311219 A1 | Dec 2012 | US |