CLAIM OF PRIORITY

This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62053064, entitled FACILITATING SMART MEDICAL DEVICES, by Amina Hamirani Sultan, filed September 19, 2014, and the entire contents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD

Embodiments described herein generally relate to computers. More particularly, embodiments relate to a mechanism for facilitating integration of medical devices into computing devices for generating and operating smart medical devices.

BACKGROUND

Most medical devices (e.g., stethoscopes, otoscope, thermometers, ear guns, surgical equipment, etc.) include instruments that are used for diagnosis and treatment of various medicals conditions of humans and animals. For example, stethoscopes have long been used by professionals, such as medical professions (e.g., doctors, nurses, veterinarians, technicians, researchers, etc.), to detect and monitor sounds produced by various human and animal body parts, such as heart, lungs, intestine, abdomen, etc., for diagnosing illnesses, irregularities, etc. However, other than being able to perform their basic functionalities, conventional medical devices are not regarded as smart devices.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

Figure 1 illustrates a computing device hosting a smart medical device integration mechanism according to one embodiment. Figure 2 illustrates a smart medical device integration mechanism according to one embodiment.

Figure 3A, 3B, 3C, 3D, 3E, 3F, 3G, 3H and 31 illustrate one or more architectural placements according to one embodiment. Figure 4 illustrates a method 400 for facilitating smart medical devices according to one embodiment.

Figure 5 illustrates computer system suitable for implementing embodiments of the present disclosure according to one embodiment.

SUMMARY A mechanism is described for facilitating smart medical devices according to one embodiment. A method of embodiments, as described herein, includes detecting a medical device being integrated with a computing device, and facilitating the medical device to serve and operate as a smart medical device based and anchored on the computing device, where facilitating further includes facilitating the smart medical device to smartly perform medical device-related tasks. The method may further include presenting results of the tasks at the computing device or one or more other computing devices.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth. However, embodiments, as described herein, may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in details in order not to obscure the understanding of this description.

Embodiments provide for a novel mechanism for generating smart medical devices, where, for example, a medical device (e.g., stethoscope, otoscope, thermometer, surgical equipment, etc.) and/or one or more components of the medical device may be coupled to or integrated with one or more computing devices (e.g., smartphone, tablet computer, laptop computers, etc.) or one or more components (e.g., display device, microphone, camera, etc.) of a computing device such that the medical device (and/or one or more of its components) may serve or perform as a smart medical device. This integration of the medical and computing devices may facilitates additional capabilities and features, such as better acoustic, visuals, animations, interactivity, wireless uses, and automation, etc., allowing the medical device to perform more efficiently and precisely in obtaining relevant results. In one embodiment, a single medical device (e.g., thermometer, stethoscope, otoscope, etc.) may be integrated with a single computing device (e.g., smartphone, tablet computer, etc.) to generate, form, and operate as a single smart medical device. In another embodiment, multiple medical devices may be integrated with a single computing device to generate, form, and operate as multiple smart medical devices based on and connected with the single computing device. In yet another embodiment, multiple medical devices may be integrated with multiple computing devices to generate, form, and operate as multiple smart medical devices. In yet another embodiment, a single medical device may be integrated with multiple computing devices to generate, form, and operate as a single smart medical device.

In one embodiment, multiple medical devices may be coupled to a single smart computing device to form a merged smart device such that user may pick and choose, alternate, etc., between multiple medical devices, where multiple medical devices may be connected to the smart computing device directly or through another medium, such as a skin or a case of the smart computing device. Further, a smart medical device may be in communication with one or more server computers (e.g., cloud servers), one or more datasets or databases, one or more third-party computers (e.g., hospital computers, emergency services, doctors' computers, pharmacy computer, research organizations, educational institutions, government agencies, etc.) over one or more networks (e.g., cloud network, Internet, etc.).

Further, a medical device and/or one or more of its components may be placed in communication with a computing device in any number and type of ways, such as wirelessly over a network (e.g., Internet, Internet of Things ("IoT"), Cloud, Cloud of Things ("CoT"), proximity network, WiFi, MyFi, local area network ("LAN"), etc.), wired using a cable, transformation by directly connecting one or more components of the medical device with the computing device (e.g., smartphone, tablet computer, laptop computer, etc.). For example, one or more components of a medical device may be connected with a computing device to perform its tasks or functionalities using the computing device, where the one or more components may be installed on the computing device, connected with computing device via a wire or cable, and/or wirelessly placed in communication with the computing device over one or more networks.

Embodiments further provide for engaging or sharing the medical device (e.g., the results obtained by the medical device) with various software applications hosted by the computing device, such as social networking media outlets/websites (e.g., Facebook®, Twitter®,

Pinterest®, Google® Analytics®, email applications, short message service ("SMS") or text applications, etc.) for participation in numerous capacities and at different levels, such as displaying a patient' s heart rate at a display device via one or more aforementioned software applications. For example, Facebook® may be engaged through images, photos, videos, events, etc., while Pinterest® may be engaged through pins & boards for promotions. Such social networking websites may be used to track patient's medical history (e.g., blood pressure levels for the last 6 months, etc.), data (e.g., blood type, etc.), behavior (e.g., eating habits, etc.), etc.

Throughout this document, terms like "logic", "component", "module", "framework", "engine", "mechanism", "technique", and/or the like, may be referenced interchangeably and include, by way of example, software, hardware, and/or any combination of software and hardware, such as firmware. Further, any use of a particular brand, word, term, phrase, name, acronym, or the like, such as "user", "patient", "consumer", "wired", "wireless", "medical device", "smart medical device", "combined or merged smart medical device", "server computer", "third-party computer", "stethoscope", "otoscope", "thermometer", "surgical equipment or instruments", "computing device", "smartphone", "tablet computer", "software application", "social/business networking site", "website", "site", and/or the like, should not be read to limit embodiments to software or devices that carry that label in products or in literature external to this document.

Further, it is to be noted that throughout this document, terms like "user" may be referenced to and used interchangeably as "medical personnel", "professional user", "doctor", "nurse", "technician", "researcher", "academic", "customer", "consumer", "client", "patient", "end-user", etc. For example and in some embodiments, medical personnel, such as a doctor, may use a smart medical device and a "patient" or "end-user" may be the individual upon whom the smart medical device is used. However, it is to be noted that in some other embodiments, these smart medical devices (e.g., smart thermometer, smart stethoscope, smart otoscope, etc.) may be available for the patients to use upon themselves or on friends or other members of their family without having the need for a medical expert, such as a doctor or a nurse. Accordingly, in some embodiments, an "end-user" is also referred to as the "user" in that there is no intervening medical personnel.

It is contemplated and to be noted that embodiments are not related to a particular medical device or computing device; however, for the sake of brevity, clarity, and ease of understanding, a particular medical device, such as a stethoscope, otoscope, and a particular computing device, such as a smartphone and/or a tablet computer, are used as examples throughout this document even though, as aforementioned, embodiments are not limited as such. It is further contemplated and to be noted that embodiments may not be merely limited to medical devices and that other non-medical devices may also be used with one or more embodiments, such as any number and type of non-medical devices (e.g., household equipment, office equipment, etc.) may be converted into smart devices using one or more embodiments and over a network, such as IoT.

Figure 1 illustrates a computing device 100 hosting a smart medical device integration mechanism 110 according to one embodiment. Computing device 100 serves as a host machine for employing smart medical device integration mechanism ("smart integration mechanism") 110. Computing device 100 may include large computing systems, such as server computers, desktop computers, etc., and may further include set-top boxes (e.g., Internet-based cable television set-top boxes, etc.), global positioning system (GPS)-based devices, etc. Computing device 100 may include mobile computing devices, such as cellular phones including smartphones, personal digital assistants (PDAs), tablet computers, laptop computers, e-readers, smart televisions, television platforms, wearable devices (e.g., smart glasses, smart watches, smart bracelets, smartcard, smartcards, smart jewelry, smart clothing items, etc.), Internet of Things (IoT) devices, media players, Media Internet Devices (MIDs), head-mounted displays (HMDs) (e.g., optical HMDs, binoculars, gaming HMDs, military HMDs, medical HMDs, etc.), etc. For example, computing device 100 may include a mobile computing device employing an integrated circuit ("IC"), such as system on a chip ("SoC" or "SOC"), integrating various hardware and/or software components of computing device 100 on a single chip, etc.

Computing device 100 includes an operating system ("OS") 106 serving as an interface between any hardware or physical resources of the computer device 100 and a user. Computing device 100 further includes one or more processor(s) 102, memory devices 104, network devices, drivers, or the like, as well as input/output ("I/O") mechanisml08 including (without limitations) touchscreens, touch panels, touch pads, virtual or regular keyboards, virtual or regular mice, ports, connectors, etc. Computing device may include a central processing unit ("CPU") (including one or more processors, such as processors 102), a graphics processing unit ("GPU") (including one or more graphics processors), etc.

It is to be noted that terms like "node", "computing node", "server", "server device", "cloud computer", "cloud server", "cloud server computer", "machine", "host machine", "device", "computing device", "computer", "computing system", and the like, may be used interchangeably throughout this document. It is to be further noted that terms like "application", "software application", "website", "site", "program", "software program", "code", "software code", "package", and "software package" may be used interchangeably throughout this document. Similarly, terms like "job", "input", "request" and "message" may be used interchangeably throughout this document. Figure 2 illustrates a smart medical device integration mechanism 110 according to one embodiment. In one embodiment, smart integration mechanism 110 may include any number and type of components, such as (without limitation): reception/detection logic 201,

authentication/verification logic 203, connection/compatibility logic 205, processing logic 207, presentation logic 209, interface logic 211, and communication logic 213. Computing device 100 may host I/O mechanism 108 including input elements 221, output elements 223, user interface 225 as facilitated by interface logic 209, and one or more connectors 227 as facilitated by connection logic 205. Input elements 211 may include any number and type of receiving, capturing, sensing, and/or detecting components, such as camera 231, sensor array 233, microphone 235, etc., while output elements 223 may include any number and type of projection and/or display components, such as display (projection) device 241, speaker 243, etc.

For example, input elements 221 may include one or more of two-dimensional (2D) cameras, three-dimensional (3D) cameras, depth-sensing cameras, sensor arrays (such as context/context-aware sensors and environmental sensors, such as camera sensors, ambient light sensors, Red Green Blue (RGB) sensors, movement sensors, etc.), image sources,

audio/video/signal detectors, microphones, eye/gaze-tracking systems, head-tracking systems, etc.), etc. Input elements 221 may further include one or more of vibration components, tactile components, conductance elements, biometric sensors, chemical detectors, signal detectors, electroencephalography, functional near- infrared spectroscopy, wave detectors, force sensors (e.g., accelerometers), illuminators, eye-tracking or gaze-tracking system, head-tracking system, etc., that may be used for capturing any amount and type of visual data, such as images (e.g., photos, videos, movies, audio/video streams, etc.), and non-visual data, such as audio streams or signals (e.g., sound, noise, vibration, ultrasound, etc.), radio waves (e.g., wireless signals, such as wireless signals having data, metadata, signs, etc.), chemical changes or properties (e.g., humidity, body temperature, etc.), biometric readings (e.g., figure prints, etc.), brainwaves, brain circulation, environmental/weather conditions, maps, illuminators (e.g., infrared (IR) illuminator), light fixtures, generators, sound blockers, etc.

Input elements 221 may further include one or more of audio/visual devices (e.g., cameras, microphones, speakers, etc.); context-aware sensors (e.g., temperature sensors, facial expression and feature measurement sensors working with one or more cameras of audio/visual devices, environment sensors (such as to sense background colors, lights, etc.); accelerometers; inertial devices; gravity gradiometers; biometric sensors (such as to detect fingerprints, etc.), calendar maintenance and reading device), etc.; global positioning system (GPS) sensors; resource requestor; and trusted execution environment (TEE) logic. Input elements 221 may further include voice recognition devices, photo recognition devices, facial and other body recognition components, voice-to-text conversion components, etc.

Output element 223 may include (without limitation) projectors, display/projection areas, audio/video/signal sources, display planes, display panels, display screens/devices, projectors, display/projection areas, speakers, etc. Output elements 223 may include dynamic tactile touch screens having tactile effectors as an example of presenting visualization of touch, one or more of light sources, display devices and/or screens, audio speakers, tactile components, conductance elements, bone conducting speakers, olfactory or smell visual and/or non/visual presentation devices, haptic or touch visual and/or non- visual presentation devices, animation display devices, biometric display devices, X-ray display devices, high-resolution displays, high-dynamic range displays, multi-view displays, and head-mounted displays (HMDs) for at least one of virtual reality (VR) and augmented reality (AR), etc.

Smart integration mechanism 110 may be hosted by computing device 100, such as a communication/data processing device including a mobile computer (e.g., smartphone, tablet computer, etc.), a wearable computers (e.g., wearable glasses, smart bracelets, smartcards, smart watches, HMDs, etc.), an Internet of Things (IoT) devices, and/or the like. In another embodiment, computing device 100 may be a larger communication machine, such as a server computer, a desktop computer, a laptop computer, etc. In yet another embodiment, computing device 100 may be in communication with a larger computing machine, scuh as server computer 280, hosting a server-based smart device mechanism 281 for performing one or more tasks outsourced to server computer 280 by computing device 100. Further, server-based smart device mechanism 281 may be the same as or similar to smart integration mechanism 110 at computing device 100.

In yet another embodiment, computing device 100 may be in communication with one or more third-party computing devices, such as personal devices 270A-N (e.g., smartphones, tablet computers, wearable device, laptop computers, desktop computers, etc.), such as personal device 27 OA hosting client-based software application 271 (such as a client-based smart device mechanism that is downloadbale or accessible over a network) which may be the same as or similar to smart integration mechanism 110 of computing device 100, where software application 271 further offers user interface 273. Computing device 100 may be in communication with server computer 280 and personal devices 270A-N over a communicaiton medium, such as one or more networks (e.g., cloud network, Internet, proximity network, IoT, etc.). Computing device 100 may be connected with one or more medical devices, such as medical device 290 A- N, via connectors 227 at computing device 100, such as connector 227 at computing device 100 and connectors 297 at medical device 290A. In another embodiment, computing device 100 and one or more medical devices, such as medical device 290A, may be connected over one or more networks, such as network 250.

In one embodiment, medical device 290A may be integrated with computing device 100 as facilitated by connection/compatiblity logic 205 to ensure medical device 290A is properly connected and compatible with computing device 100. In some embodiment,

connection/compatiblity logic 205 may be used to establish compatiblity between medical device 290A and computing device 100 when, for example, medical device 290A may not be fully compatible with communicaiton device 100.

Once the connectivity and compatility is estabished through conneciton/compatiblity logic 205, in one embodiment, reception/detection logic 201 may be triggered to acknolwedge the reciept detection of medical device 290A and collect any relevant information, such as unique identification, tag number, type of medical device 290A, data relating to one or more users having access to medical device 290A, and/or the like, to authentication/verification logic 203 for further processing. Upon receiving the relevant information from reception/detection logic 201, authentication/verification logic 203 may be used to authenticate and/or verify credentials of medical device 290A and/or its one or more users. Such authentication/verification may be made each time medical device 290A is connected or put in communicaiton with computing device 100. In antoehr embodiment, authentication/verificaiton may be made only once when medical device 290A is first connected with computing device 100 or when a new user is associated with medical device 290A.

Upon authenticating/verifying medical device 290A and its one or more users, computing device 100 may then be used to work with medical device 290 A to perform one or more tasks relating to medical device 290A as facilitated by processing logic 207. For example, when medical device 290A being a thermometer is connected or put in communiction with computing device 100, processing logic 207 may facialite computing device 100 to work with medical device 290A (e.g., thermometer) to obtain a patient's body temparature using one or more sensor of sensor array 233, such as a biometric sensor, of input elements 221, present the patient's temparature by visually displaying it via display device 241, audio broadcasting it and/or other alters (e.g., beeps indicating temperature has been taken), etc., via speaker 243, etc.

Once the relevant data, such as the patient' s body temparature, has been obtained, presentation logic 209 may be used to present the results in any number and types of ways the user (e.g., patient, patient's doctor, nurse, family member, etc.) may choose to receive. For example, the temperature may be presented as merely a number on display device 241 or the audio of the number may be played through speaker 243. Simiarly, in some embodiments, the patient's temperature may be visually displayed as a graph/chart, such as a historical line graph of the patient's temperaturs over a period of time. In some other embodiments, one or more remedies, cures, additional information, etc., may also be displayed along with the patient's temperature to assist the one or more users with any possible subsequent steps or procedures.

Any inputs (e.g., user data, preferences, etc.) may be recived and outputs (e.g., presentations, results, etc.) may be offered through user interface 225 as faciltated by interface logic 211. For example, user interface 225 may be a mobile application-based user interface or a general user interface, such as a web brower, etc. Any communication may be triggered and facilitated by communication logic 213, such as communicaiton between various components of smart integration mechanism 110, computing device 100, medical devices 290A-N, personal devices 270A-N, and/or server computer 280, database(s) 260, and/or one or more network(s) 250. It is contemplated that for brevity, clarity, and ease of understanding, although

thermometer is used as an example for medical device 290A, embodiments are not limited as such and that medical device 290A may include (without limitation) one or more of stethoscope, otoscope, pulse oximeter, blood pressure monitor, blood sugar or glucose monitor, prothrombin time (PT)/internaltional normalized ratio (INR) monitor, dental equipment, surgical equipment, and/or the like.

Continuing with the thermometer example, once the relevant result have been obtained, such as the patient's body temperature is acquired, the results (e.g., body temparature) may the, be automatically, or as desired or necessitated by the user of computing device 100, shared with one or more other users of third-party personal devices 270A, 270B, 270N, such as the patient's doctor having access to personal device 270A where the results may be received over network 260 and via user interface 273 of software application 271 as facilitated by communication components 275. Software application 271 may be the same as or similar to smart integration mechanism 110 or it may be another software application, such as a website, a communication application, and/or the like.

It is contemplated personal devices 270A-N are not limited to any particular number of type of devices (such as mobile computers, laptops, wearable devices, IoT devices, desktops, server computers, etc.) and simialrly, any user having access to personal devices 270A-N may include any number and type of users, such as doctors, nurses, other medical personnel, hospitals, clinics, research centers, family members, friends, other personal devices or accounts of the user of computing device 100, and/or the like. Such communciation between computing device 100 and one or more of personal devices 270 A-N may be performed using any number and type of communication applications, such as email, short message service (SMS), instant messaging, websites (e.g., social or business networking websites, such as Facebook®,

Linkedln®, WebMD®, etc.), and/or the like. Further, any communication between computing device 100 and one or more of personal devices 270 A-N may be confidential, such as using one or more encryption techniques, and in accordance with any application laws and/or policies, such as local laws, state laws, federal laws, insurance policies, user preferences, other statutes and relevant acts, such as Health Insurance Portability and Accountability Act (HIPP A), etc.

As illustrated, computing device 100 may be in communication with server computer 280 such that any number and type of tasks relating to smart integration mechanism 110 may be outsourced to server-based smart device mechanism 281 which may then be responsible for performing such outsourced tasks. For example, it is contemplated that not all mobile devices are the same in terms of their resources, such as memory, processing power, etc., and accordingly, if computing device 100 is occupied or incapable of performing one or more tasks (such as graphical represenation of the patient's body temperature, accessing the patient's body temperature history at one or more database(s) 260, bigger resource-consuming tasks, etc.) may be perfomred at server computer 280 using server-based smart device mechanism 281.

Further, as with communciation with personal devices 270A-N, any communication between computing device 100 and server computer 280 may be confidential, such as using one or more encryption techniques, and in accordance with any application laws and/or policies, such as local laws, state laws, federal laws, insurance policies, user preferences, other statutes and relevant acts, such as Health Insurance Portability and Accountability Act (HIPP A), etc.

Connection/compatiblity logic 205 and communication logic 213 may be used to facilitate dynamic communication and compatibility between computing device 100 and medical devices 290A-N, database(s) 260, network(s) 250, etc., and/or any number and type of other computing devices 280, 270A-270N (such as wearable computing devices, mobile computing devices, desktop computers, server computing devices, etc.), processing devices (e.g., central processing unit (CPU), graphics processing unit (GPU), etc.), capturing/sensing components (e.g., non-visual data sensors/detectors, such as audio sensors, olfactory sensors, haptic sensors, signal sensors, vibration sensors, chemicals detectors, radio wave detectors, force sensors, weather/temperature sensors, body/biometric sensors, scanners, etc., and visual data

sensors/detectors, such as cameras, etc.), user/context-awareness components and/or

identification/verification sensors/devices (such as biometric sensors/detectors, scanners, etc.), memory or storage devices, data sources, and/or database(s) (such as data storage devices, hard drives, solid-state drives, hard disks, memory cards or devices, memory circuits, etc.), network(s) (e.g., Cloud network, the Internet, Internet of Things, intranet, cellular network, proximity networks, such as Bluetooth, Bluetooth low energy (BLE), Bluetooth Smart, Wi-Fi proximity, Radio Frequency Identification (RFID), Near Field Communication (NFC), Body Area Network (BAN), etc.), wireless or wired communications and relevant protocols (e.g., Wi-Fi®, WiMAX, Ethernet, etc.), connectivity and location management techniques, software

applications/websites, (e.g., social and/or business networking websites, business applications, games and other entertainment applications, etc.), programming languages, etc., while ensuring compatibility with changing technologies, parameters, protocols, standards, etc.

Throughout this document, terms like "logic", "component", "module", "framework",

"engine", "tool", and the like, may be referenced interchangeably and include, by way of example, software, hardware, and/or any combination of software and hardware, such as firmware. Further, any use of a particular brand, word, term, phrase, name, and/or acronym, such as "medical device", "smart medical device", "combined or merged smart medical device", "user", "user profile", "user preference", "user", "sender", "receiver", "server computer",

"personal device", "smart device", "mobile computer", "wearable device", "IoT devices", etc., should not be read to limit embodiments to software or devices that carry that label in products or in literature external to this document.

It is contemplated that any number and type of components may be added to and/or removed from smart integration mechanism 110 and/or smart device mechanism 281 to facilitate various embodiments including adding, removing, and/or enhancing certain features. For brevity, clarity, and ease of understanding of smart integration mechanism 110 and/or smart device mechanism 281, many of the standard and/or known components, such as those of a computing device, are not shown or discussed here. It is contemplated that embodiments, as described herein, are not limited to any particular technology, topology, system, architecture, and/or standard and are dynamic enough to adopt and adapt to any future changes.

Figure 3A illustrates an achitectural placement 300 according to one embodiment. As an intial matter, it is contemplated that embodiments are not limited to any particular architectural placement or setup, such as architectural placement 300, nor are embodiments limited to any particular number and type of medical devices 290A-290N and/or computing device 100.

Architectural placement 300 may be faclitated by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (such as instructions run on a processing device), or a combination thereof, such as smart integration mechanism 110, server- based smart device mechanism 281, and/or client-based software application 271.

In one embodiment, computing device 100 may offer one or more connectors 227, such as connectors 227 A, 227B, 227N, of Figure 2 that are either provided directly through the housing of computing device 100, such as connector 227 A, or indirectly through an intermediary entity 301, such as a device case or casing, providing additional components, connectors, etc., such as connectors 227B, 227N. It is contempalted that any intermediatery entity, such as intermediary entity 301, may be connected to computing device 100 using one or more internal connections. As illustrated, in one embodiment, medical device 290A, such as a thermometer, may be directly connected to computing device 100 using a primary or direct connector, such as connector 227 A. Similarly, another medical device 290B, such as blood pressure monitor, may be connected to computing device 100 via a secondary or indirect connector, such as connector 290B, provided through intermediary entity 301.

In another embodiment, medical devices 290C (e.g., stethoscope) and 290N ( e.g., otoscope) may be connected and in communication with computing device 100 over one or more network(s) 250. In yet another embodiment, medical devices 290C, 290N may be connected with computing deivce 100 using one or more appropriate connectors 227C, 227N which may be directly provided on the housing of computing device 100, indireclty provided through intermediary entity 301, etc. In some embodiments, connectors 227C, 227N may removable such that connector 227C may be temorarily placed on or attached to computing device 100 while medical device 290C is to be connected. Similarly, another connector 227N may be placed on or attached to computing device 100 to connect medical device 290N to computing device 100. These connectors 227C, 227N may be removed when the corresponding medical devices 290C, 290N are removed from computing device 100. In some embodiments, connectors 227C, 227N may be permanent provided through the housing of computing device 100 and/or an intermediatry entity 301, such as device case.

Fig. 3B-3E illustrates an architectural placement 310 according to one embodiment. As described with reference to Figure 3A, medical device 290C, such as stethoscope, is shown as being connected or in communication with computing device 100 in any number of ways, such as wirelessly, over network 250, or wired through connector 227 A using cable 311. Similarly, as shown Figure 3B, connector 227C may be provided for connecting medical device 290C or one or more of its components, such as diaphragms 303A-303B chest piece 301, etc., as further illustrated in Figure 3C.

As further illustrated with regard to Figure 3B, medical device 290C, such as a stethoscope, may include one or more components, such as (without limitation): a chest piece 302 having a large diaphragm 303A and a small diaphragm 303B, a stem 305, a tubing 307, ear tubes 309A-B, and earpieces 311A-B, etc. As in Figure 3A, medical device 290C may also include communication logic which may be used to communicate with computing device 100 over one or more networks, such as network 250. In yet another embodiment and as illustrated in Figure 3B, medical device 290C may be placed in communication with computing device 100 by connecting one or more components (e.g., via diaphragms 303A-303B chest piece 301) of medical device 290C to computing device 100 using one or more specified slots 321 A, 32 IB of connector 227C. In yet another embodiment and as illustrated in Figure 3E, one or more components (e.g., diaphragms 303A-303B of chest piece 301) of medical device 290C may be placed in communication with computing device 100 over one or more networks, such as network 250.

As further illustrated in Figure 3A, in one embodiment, results of the use of medical device 290C may be observed or obtained in any number or type of ways, such as through ear tips 311A-311B, set of earphones 313, speakers 243 of computing device 100 by simply clicking of speaking icon 315, display device 241, etc. As illustrated in Figure 3B, in one embodiment, slots 312A, 321B of connector 227C may be of any form or type, such as ring, square, rectangular, etc., and may be used to accept diaphragms 303A-303B, such as large diaphragm 303A into a larger or outer slot 321A, small diaphragm 303B into a smaller or inner slot 321B, respectively. Upon having such an insertion, side views of computing device 100 may appear as illustrated in Figure 3C.

Figures 3F-3I illustrates an architectural placement 350 according to one embodiment. In the illustrated embodiment, another medical device 290N (e.g., otoscope) is shown as being connected or in communication with computing device 100 in any number of ways, such as wirelessly, over network 250, or wired through connector 227N using connection cable 311. Similarly, as shown Figure 3F, in one embodiment, connector 227N may be provided for connecting medical device 290N or one or more of its components, such optical head 351, etc., with computing device 100 as further illustrated in Figure 3G, 3H. Medical device 290N being an otoscope may include any number and type of other components, such as viewing window 353, speculum 355, and handle 357. As in Figure 31, one or more components (e.g., optical head 351) may be placed in communication with computing device 100 over one or more networks, such as network 250.

As in Figure 3E, results of the use of (e.g., optical head 351) may be obtained using viewing window 353, display screen 241 at computing device 100, and/or the like. As with medical device 290C, the one or more components of medical device 290N may be connected with one or more connectors, such as connector 227N, having one or more slots, such as slot 361, such as on back side 363B of the housing of computing device 100 or on or through an intermediary entity (such as a case) covering computing device 100. As in Figure 3G, slots 361 may be shown as a square slot, but embodiments are not limited to any particular shape, such as square, ring, circle, rectangular, etc. Upon having such an insertion of a portion of medical device 290N, a side view of computing device 100 may appear as illustrated in Figure 3H. In one embodiment, slots 321A, 321B of Figure 3C and slot 361 of Figure 3G of connectors 227C, 227N may be uniform or universal to fit any type of component of any type of medical devices 290A-N of Figure 3A, such as stethoscope, otoscope, thermometer, blood pressure monitor, blood sugar monitor, etc. In another embodiment, each slot 321 A, 321B, 361 of connectors 227 C, 227N may be unique in that it may fit a particular component and/or a medical device and thus a separate slot or connector may be offered and used for each type of medical devices 290A-N of Figure 3A. It is contemplated that embodiments are not limited to any particular number or type of medical devices 290A-N. Further, a single medical device or multiple medical devices may be simultaneously or alternatively connected to or placed in communication with computing device 100. It is further contemplated that computing device 100 may be in communication with any number and type of other non-medical devices, such as printer, etc., along with being in communication or connection with one or more medical devices 290A-290N.

Figure 4 illustrates a method 400 for facilitating smart medical devices according to one embodiment. Method 400 may be performed by processing logic that may comprise hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (such as instructions run on a processing device), or a combination thereof, as facilitated by smart integration mechanism 110 and/or server-based smart device mechanism 281 of Figure 2. The processes of method 400 are illustrated in linear sequences for brevity and clarity in presentation; however, it is contemplated that any number of them can be performed in parallel, asynchronously, or in different orders.

Method 400 begins at block 401 with integrating a medical device (e.g., stethoscope, otoscope, thermometer, blood sugar monitor, blood pressure monitor, etc.) with a computing device (e.g., smartphone, tablet computer, laptop computer, wearable device, IoT device, etc.), by intelligently placing the medical device in connection or communication with the computing device. At block 403, as facilitated by smart integration mechanism 110 of Figure 2 and using the computing device, the medical device is converted into and used as a smart medical device to perform any number and type of medical device-related tasks. At block 405, a determination is made as to whether one or more tasks may be outsourced or assigned to one or more server computers, such as a cloud computer, over one or more networks, such as a cloud network, to be performed using server-based smart device mechanism 281 of Figure 2.

If yes, at block 407, one or more tasks may be forwarded on to a server computer over a network such that the tasks may be performed by server-based smart device mechanism 281 of Figure 2. If not, at block 409, the tasks may continue to be performed at the computing device as facilitated by smart integration mechanism 110 of Figure 2. At block 411 , results (e.g., views from inside an ear, body temperature, close up view of the eye, sounds and frequency of heartbeats, etc.) are obtained from performance of the medical device-related tasks.

At block 413, a determination is made as to whether the results are to be shared other users having access to one or more personal computing devices. If yes, some or all of the results are shared with one or more users having access to one or more personal computing devices at block 415, where sharing may be performed using one or more communication applications, such as email, SMS, instant messaging, websites, etc., and the one or more receiving users may include any number and type of individuals (e.g., doctor, nurse, friend, family member, etc.), groups (e.g., family, doctor's clinic, human resources, etc.), institutions (e.g., hospital, employer company, etc.), and/or the like. At block 417, the results are presented via one or more display devices (e.g., high-definition (HD) videos, pictures, graphics, charts, animation, etc.), speakers (e.g., amplified sounds, tones, alerts, etc.), projection areas (e.g., larger projection videos, pictures, etc.), etc.

In one embodiment, the smart medical device may be sustained for any amount of time as desired or necessitated by the user (e.g., doctor, nurse, practitioner, professional, expert, etc.) such that the smart medical device may be used short-term (e.g., for one or more patients, a day or two, etc.), long-term (e.g., for a large number of patients, a couple of weeks or months or longer, etc.), or even permanently, as desired or necessitated.

Figure 5 illustrates a diagrammatic representation of a machine 500 in the exemplary form of a computer system, in accordance with one embodiment, within which a set of instructions, for causing machine 500 to perform any one or more of the methodologies discussed herein, may be executed. Machine 500 may be the same as or similar to or contained within computing device 100 employing reverse shopping mechanism 110 of Figure 1 according to one embodiment. In alternative embodiments, machine 100 may be connected (e.g., networked) to other machines either directly, such as via media slot or over a network, such as a cloud-based network, a Local Area Network (LAN), a Wide Area Network (WAN), a

Metropolitan Area Network (MAN), a Personal Area Network (PAN), an intranet, an extranet, or the Internet. The machine may operate in the capacity of a server or a client machine in a client- server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment or as a server or series of servers within an on-demand service environment, including an on-demand environment providing multi-tenant database storage services. Certain embodiments of the machine may be in the form of a personal computer (PC), a tablet PC, a set- top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, switch or bridge, computing system, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines (e.g., computers) that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The exemplary computer system 500 includes one or more processors 502, a main memory 504 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc., static memory 542, such as flash memory, static random access memory (SRAM), volatile but high- data rate RAM, etc.), and a secondary memory 518 (e.g., a persistent storage device including hard disk drives and persistent multi-tenant data base implementations), which communicate with each other via a bus 530. Main memory 504 includes instructions 524 (such as software 522 on which is stored one or more sets of instructions 524 embodying any one or more of the methodologies or functions of reverse shopping mechanism 110 of computing device 100 of Figure 1 and other figures described herein) which operate in conjunction with processing logic 526 and processor 502 to perform the methodologies discussed herein.

Processor 502 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor 502 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 502 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processor 502 is configured to execute the processing logic 526 for performing the operations and functionality of reverse shopping mechanism 110 of computing device 100 of Figure 1 and other figures discussed herein.

The computer system 500 may further include a network interface device 508, such as a network interface card (NIC). The computer system 500 also may include a user interface 510 (such as a video display unit, a liquid crystal display (LCD), or a cathode ray tube (CRT)), an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), a signal generation device 540 (e.g., an integrated speaker), and other devices 516 like cameras, microphones, integrated speakers, etc. The computer system 500 may further include peripheral device 536 (e.g., wireless or wired communication devices, memory devices, storage devices, audio processing devices, video processing devices, display devices, etc.). The computer system 500 may further include a hardware-based application programming interface logging framework 534 capable of executing incoming requests for services and emitting execution data responsive to the fulfillment of such incoming requests.

Network interface device 508 may also include, for example, a wired network interface to communicate with remote devices via network cable 523, which may be, for example, an

Ethernet cable, a coaxial cable, a fiber optic cable, a serial cable, a parallel cable, etc. Network interface device 508 may provide access to a LAN, for example, by conforming to IEEE 802.11b and/or IEEE 802. l lg standards, and/or the wireless network interface may provide access to a personal area network, for example, by conforming to Bluetooth standards. Other wireless network interfaces and/or protocols, including previous and subsequent versions of the standards, may also be supported. In addition to, or instead of, communication via the wireless LAN standards, network interface device 508 may provide wireless communication using, for example, Time Division, Multiple Access (TDMA) protocols, Global Systems for Mobile Communications (GSM) protocols, Code Division, Multiple Access (CDMA) protocols, and/or any other type of wireless communications protocols.

The secondary memory 518 may include a machine-readable storage medium (or more specifically a machine- accessible storage medium) 531 on which is stored one or more sets of instructions (e.g., software 522) embodying any one or more of the methodologies or functions of reverse shopping mechanism 110 of Figure 1 and other figures described herein. The software 522 may also reside, completely or at least partially, within the main memory 504, such as instructions 524, and/or within the processor 502 during execution thereof by the computer system 500, the main memory 504 and the processor 502 also constituting machine -readable storage media. The software 522 may further be transmitted or received over network 520 via the network interface card 508. The machine -readable storage medium 531 may include transitory or non-transitory machine-readable storage media.

Portions of various embodiments may be provided as a computer program product, which may include a computer-readable medium having stored thereon computer program instructions, which may be used to program a computer (or other electronic devices) to perform a process according to the embodiments. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, compact disk read-only memory (CD-ROM), and

magneto-optical disks, ROM, RAM, erasable programmable read-only memory (EPROM), electrically EPROM (EEPROM), magnet or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions. Modules 544 relating to and/or include components and other features described herein (for example in relation to reverse shopping mechanism 110 of computing device 100 as described with reference to Figure 1) can be implemented as discrete hardware components or integrated in the functionality of hardware components such as ASICS, FPGAs, DSPs or similar devices. In addition, modules 544 can be implemented as firmware or functional circuitry within hardware devices. Further, modules 544 can be implemented in any combination hardware devices and software components.

The techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer -readable media, such as non-transitory computer - readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer -readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals - such as carrier waves, infrared signals, digital signals). In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device. Of course, one or more parts of an embodiment may be implemented using different combinations of software, firmware, and/or hardware.

Any of the above embodiments may be used alone or together with one another in any combination. Embodiments encompassed within this specification may also include

embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments do not necessarily address any of these deficiencies. In other words, different embodiments may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies. Embodiment 1 includes an apparatus to facilitate smart medical devices, comprising: reception/detection logic to detect a medical device being integrated with the apparatus;

processing logic to facilitate the medical device to serve and operate as a smart medical device based and anchored on the apparatus, wherein the processing logic is further to facilitate the smart medical device to perform medical device-related tasks; and presentation logic to present results of the tasks at the apparatus or one or more other computing devices.

Embodiment 2 includes the subject matter of Embodiment 1, wherein the results are presented via one or more output elements including at least one of a display device and a speaker.

Embodiment 3 includes subject matter of Embodiment 1 or 2, further comprising authentication/verification logic to authenticate at least one of the medical device and a user having access to the medical device, wherein authenticating is performed prior to the processing logic facilitating the medical device to serve as a smart medical device; and/or

connection/compatibility logic to integrate the medical device with the apparatus to generate the smart medical device such that the medical device serves and operates as the smart medical device, wherein integrating includes at least one of directly connecting, indirectly connecting, and remotely connecting, wherein the connection/compatibility logic is further to simultaneously integrate multiple medical devices to the apparatus such that each of the multiple medical devices serves and operates as a smart medical device simultaneously with other multiple medical devices serving as other smart medical devices based and anchored on the apparatus, wherein directly connecting comprises connecting the medical device with the apparatus via a direct connector on a housing of the apparatus such that the medical device and the apparatus singularly function as the smart medical device, wherein indirectly connecting comprises connecting the medical device and the apparatus via an indirect connector provided via an intermediary entity coupled with the apparatus, wherein the intermediary entity includes a casing of the apparatus, and wherein remotely connecting comprises connecting the medical device and the apparatus over a network, wherein the network includes a cloud network, the Internet, and a proximity network.

Embodiment 4 includes subject matter of Embodiment 1 or 2 or 3, further comprising communication logic to transmit one or more of the tasks to a server computer such that the one or more tasks are performed at the server computer, wherein the server computer is in communication with the apparatus over the network, wherein the communication logic is further to communicate one or more of the results to one or more client computers, wherein the one or more client computers are accessible by one or more users and in communication with the apparatus over the network, and/or wherein the apparatus comprises a computing device including at least one of a smartphone, a tablet computer, a wearable device, an Internet of Things (IoT)-based device, a laptop computer, and a desktop computer, wherein the medical deice includes at least one of a thermometer, an otoscope, a stethoscope, a blood sugar monitor, blood pressure monitor, a prothrombin time (PT)/international normalized ratio (INR) monitor, an oxygen saturation monitor, an eye magnifying device, a dental device, and a surgical device.

Embodiment 5 includes a method for facilitating smart medical devices, comprising: detecting a medical device being integrated with a computing device; facilitating the medical device to serve and operate as a smart medical device based and anchored on the computing device, wherein facilitating further includes facilitating the smart medical device to perform medical device-related tasks; and presenting results of the tasks at the computing device or one or more other computing devices.

Embodiment 6 includes the subject matter of Embodiment 5, wherein the results are presented via one or more output elements including at least one of a display device and a speaker.

Embodiment 7 incudes subject matter of Embodiment 5 or 6, further comprising authenticating at least one of the medical device and a user having access to the medical device, wherein authenticating is performed prior to facilitating the medical device to serve as a smart medical device; and/or integrating the medical device with the computing device to generate the smart medical device such that the medical device serves and operates as the smart medical device, wherein integrating includes at least one of directly connecting, indirectly connecting, and remotely connecting, wherein integrating further includes simultaneously integrating multiple medical devices to the computing device such that each of the multiple medical devices serves and operates as a smart medical device simultaneously with other multiple medical devices serving as other smart medical devices based and anchored on the computing device, wherein directly connecting comprises connecting the medical device with the computing device via a direct connector on a housing of the computing device such that the medical device and the computing device singularly function as the smart medical device, wherein indirectly connecting comprises connecting the medical device and the computing device via an indirect connector provided via an intermediary entity coupled with the computing device, wherein the intermediary entity includes a casing of the computing device, and/or wherein remotely connecting comprises connecting the medical device and the computing device over a network, wherein the network includes a cloud network, the Internet, and a proximity network. Embodiment 8 includes the subject matter of Embodiment 5 or 6 or 7, further comprising transmitting one or more of the tasks to a server computer such that the one or more tasks are performed at the server computer, wherein the server computer is in communication with the computing device over the network; and/or communicating one or more of the results to one or more client computers, wherein the one or more client computers are accessible by one or more users and in communication with the computing device over the network, wherein the computing device comprises at least one of a smartphone, a tablet computer, a wearable device, an Internet of Things (IoT)-based device, a laptop computer, and a desktop computer, wherein the medical deice includes at least one of a thermometer, an otoscope, a stethoscope, a blood sugar monitor, blood pressure monitor, a prothrombin time (PT)/international normalized ratio (INR) monitor, an oxygen saturation monitor, an eye magnifying device, a dental device, and a surgical device.

Embodiment 9 includes least one machine-readable medium comprising a plurality of instructions, when executed on a computing device, to implement or perform a method or realize an apparatus as claimed in any preceding claims.

Embodiment 10 includes least one machine-readable medium comprising a plurality of instructions, when executed on a computing device, to implement or perform a method or realize an apparatus as claimed in any preceding claims.

Embodiment 11 includes a system comprising a mechanism to implement or perform a method or realize an apparatus as claimed in any preceding claims.

Embodiment 12 includes an apparatus comprising means to perform a method as claimed in any preceding claims.

Embodiment 13 includes a computing device arranged to implement or perform a method or realize an apparatus as claimed in any preceding claims.

Embodiment 14 includes a communications device arranged to implement or perform a method or realize an apparatus as claimed in any preceding claims.

Embodiment 15 includes a medical device including a non-invasive non-piercing blood glucose monitoring device arranged to implement or perform a method or realize an apparatus as claimed in any preceding claims.

While one or more implementations have been described by way of example and in terms of the specific embodiments, it is to be understood that one or more implementations are not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art.

Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. It is to be understood that the above description is intended to be illustrative, and not restrictive.