WO2015026872A1 - Interface utilisateur pour dispositif électronique vestimentaire - Google Patents

Interface utilisateur pour dispositif électronique vestimentaire Download PDF

Info

Publication number
WO2015026872A1
WO2015026872A1 PCT/US2014/051760 US2014051760W WO2015026872A1 WO 2015026872 A1 WO2015026872 A1 WO 2015026872A1 US 2014051760 W US2014051760 W US 2014051760W WO 2015026872 A1 WO2015026872 A1 WO 2015026872A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
patient
health status
touchscreen
user interface
Prior art date
Application number
PCT/US2014/051760
Other languages
English (en)
Inventor
Richard S. Gaster
Kristian DAMBOULEV
Original Assignee
Gaster Richard S
Damboulev Kristian
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Gaster Richard S, Damboulev Kristian filed Critical Gaster Richard S
Publication of WO2015026872A1 publication Critical patent/WO2015026872A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus

Definitions

  • the present disclosure relates to systems and methods for interfacing between wireless monitoring electronic devices and a user, for example via interface on a remote device.
  • a tocometer is a non-invasive device that is wrapped around the belly of a pregnant woman like a large elastic belt and measures the frequency of uterine contractions via a strain gauge pressure sensor. Both the strength and duration of a contraction may be indirectly measured based on the change in pressure in the abdomen.
  • the main disadvantage to the tocometer is that must be strapped around the abdomen and the back of the patient, which makes it difficult to put on, maintain in a uniform position, and makes it susceptible to falling off as the patient moves.
  • This device must also be wired to a local computer to monitor the readings, tethering the patient to a confined area. Therefore, the patients are typically restricted to a hospital setting, and home monitoring is not convenient.
  • a method for providing a health status of a patient via a user interface includes receiving, by a handheld computing device via a wireless interface, a signal from a sensor coupled to a patient, the signal indicating a health status of the patient. The method further includes providing an indication of the health status of the patient via a touchscreen of the handheld computing device, based on the signal, and enabling user selection of two or more functions related to the indication of health status via a graphical user interface presented on the touchscreen.
  • the method may include generating, as part of the graphical user interface, a scrolling wheel broken down into sections wherein each section presents a button to access a unique screen of the user interface.
  • Each section of the scrolling wheel may be enabled to be relocated to a user-specified location on the scrolling wheel, in response to user input.
  • the method may include presenting real time data recorded by the sensor coupled to a patient on the touchscreen interface, in response to user input selecting a first defined section of the scrolling wheel.
  • Other aspects of the method may include, for example, presenting an interface for scheduling medical appointments on the touchscreen interface, in response to user input selecting a second defined section of the scrolling wheel, and presenting an interface for recording text or audio notes on the touchscreen interface, in response to user input selecting a third defined section of the scrolling wheel.
  • the method may further include processing the signal using a processor located in the handheld computing device, thereby obtaining the indication of the health status.
  • the handheld computing device may be, or may include, at least one of a smartphone or a tablet computer.
  • FIGs. 1A and 1 B illustrate examples of a home or main screen for a mobile user interface device, at different times.
  • FIG. 2 illustrates an example of a physiologic monitoring screen for a mobile user interface device.
  • Fig. 3 illustrates an example of an appointments and calendar screen for a mobile user interface device.
  • Fig. 4 illustrates an example of a "my notes" screen for a mobile user interface device.
  • FIG. 5 is a block diagram illustrating an example of a wireless device for providing a user interface to health monitoring data from a remote sensor.
  • Figs. 6 and 7 are flow diagrams illustrating operations of a method for providing a health status of a patient via a user interface.
  • the present application describes methods for retrieving data acquired by a wireless wearable electronic device coupling a sensor to a patient, analyzing the data using mathematical algorithms, and presenting the data on a remote device, such as a smart phone or tablet computer, to the end user in a user friendly and easy to interpret application.
  • the disclosure further describes a simple to operate user interface for the consumer remote device that may analyze medical grade wireless sensors and present the data for non-professional consumers and medical professionals alike. Methods for navigating such a user interface are also described.
  • Wireless technologies are the future of medical diagnostics, making remote user interfaces with the wearable electronics a vital component of functionality and convenience of the overall system.
  • a remote consumer device for example a smartphone or tablet computer, may include a processor coupled to a computer memory comprising a non-transitory computer-readable medium, transceiver, touchscreen display and microphone.
  • the device may include other components as known in the art.
  • the memory may hold data and executable files, including one of more application modules collectively referred to herein as an user interface application.
  • the user interface application may include one or more executable files coded in any suitable programming language (for example, C, C++, Objective C, Java, Javascript, or other language) and compiled for operating under the operating system to be installed on the consumer wireless device.
  • the processor may execute the application to cause the consumer wireless device to generate, output, and interact with a user interface as described herein.
  • the user interface application may include, but is not limited to, providing the following features:
  • An initial landing screen also known as a splash screen.
  • This screen may present the company logo and the name of the product, among other things.
  • a sign up/log in screen This screen may contain a "sign in” button and a "create new account” button, among other buttons. If the new account button is created, a new account creation screen may show up, prompting the user to input key data relevant to their current physiological state. This data may be used to customize the user interface of the application by considering various data points such as age, number of prior pregnancies, number of abortions or miscarriages, and other patient health history information.
  • a main dashboard screen 100 may be used to navigate the entire application.
  • This screen may contain a header section 1 10, enabling the user to access their settings, change the profile of their account, integrate with other devices, access the physiologic monitoring screen, access scheduled appointments, access a predictive timeline (such as data about pregnancy which include facts about physiologic changes in the mother and fetus), a glossary of terms relevant to the end user, a note pad, and other features.
  • the navigation of the main dashboard screen 100 may contain a wheel scroll interface 120 (see also, Figs.
  • each section can be enabled for accessing a unique screen by rotating the wheel 120 to a position placing the section in the active position.
  • the segment 126 is in the active center position.
  • This wheel 100 may rotate in response to user input (e.g., touchscreen input), allowing the end user to scroll through all the possible options as many times as they wish, in a continuous fashion.
  • the mechanics of the wheel may feature inertial scrolling, whereby the input of the user may be sensed by the interface.
  • the interface may sense the momentum of the wheel rotation via a touch, scroll and or swipe gesture, and rotate in either direction. Once the user lifts his or her finger off the wheel interface, the wheel may slow down naturally before coming to a stop. Additionally, the machine of the user interface may be able to infer the speed of the swipe, scroll or touch gesture to rotate the wheel based on virtual inertia.
  • Added functionality may include the ability to physically rotate the device and have the accelerometers detect the rotation of the device and cause the wheel to spin.
  • Each section of the wheel may act as a button to take the user into a new screen, in response to user input selecting the section. While only six sections 122, 124, 126, 128, 129 are illustrated, it should be appreciated that other numbers of sections may be useful, without any particular upper limit.
  • each section of the wheel may be moved around and organized relative to other sections of the wheel according to how the end user wishes, with a special toggle setting. The wheel may rotate counterclockwise (as shown) or clockwise, or both. In contrast, scrolling up and down a page, the current standard method for navigating a user interface, has a finite beginning and end. In addition, more sections of the wheel may be added without significantly changing the user interface experience.
  • a physiologic monitoring screen 200 may contain a section 210 to present real time data recorded by the sensor coupled to a patient on the remote device.
  • This data set can be presented in portrait mode, however, the data can also be displayed in landscape mode (not shown). Once in landscape mode, the data may be presented across time to visualize past and present recorded data.
  • This data set can be scrollable through touch gestures.
  • the user interface may automatically interpret screen orientation and adjust the user interface accordingly. Equations and/or algorithms may be integrated into the software of the user interface of the remote device allowing the device to analyze and present data captured by the sensor coupled to a patient.
  • unique algorithms based on the data recorded by the wireless sensors may be interpreted by the user interface to predict the onset of labor.
  • Features measured by the wireless electronic such as the strength of contractions, duration of contractions, and rate of contractions detected by the wearable device all may be sent to the remote device.
  • the data recorded by the sensor coupled to a patient may be interpreted in hardware and/or software and ultimately presented to the end user on the user interface.
  • the data presented may be both diagnostic and prognostic information.
  • the device may include features enabling the end user to select recipients, such as physicians, hospitals, emergency responders, central servers, families and friends, to receive information about the data recorded by the sensor coupled to a patient and presented on the remote device. For example, in the case of a contraction monitor, warnings such as impending labor may be automatically sent to the predefined recipients. If the wearable device detects fetal distress, it may similarly warn the mother as well as the predefined recipients about the event in preparation to triage. The fetal heart rate tracings may similarly be monitored for accelerations and decelerations and interpreted by the user interface to provide mothers with an overall indication of the health of her fetus.
  • recipients such as physicians, hospitals, emergency responders, central servers, families and friends
  • warnings such as impending labor may be automatically sent to the predefined recipients.
  • the wearable device detects fetal distress, it may similarly warn the mother as well as the predefined recipients about the event in preparation to triage.
  • the fetal heart rate tracings may similarly be monitored for acceleration
  • the system may display visual, audible or tactile alerts (e.g., vibration signals), to the user. These alerts may be user-customizable and may be shared with other authorized users of the application. These are just a few examples of how the physiological monitoring portion of the user interface may relay analyzed information generated by the sensor coupled to a patient to not only the initially intended end user, but a selected group of other individuals as well.
  • alerts e.g., vibration signals
  • a separate and custom user interface may be targeted to the treating physician.
  • the physician interface may organize the data in a way that is presentable to a physician and provides more detailed information than what may be provided to the mother in her user interface.
  • This extension may include, but is not limited to, web-based application interfaces that combine multiple data sets of multiple users into easy-to-read widgets across a screen. Each widget may contain customizable data sets based on physician preferences set in a settings area. Physicians also may have the ability to move widgets around and organize patients based on rank, risk factors, appointment times, problems, complications and other user-selectable criteria.
  • the physician user interface may allow patients of the mobile-based application to submit real-time or previously recorded historic data in the form of contraction data, fetal heart rate (FHR) data, core or peripheral temperature data and other forms of sensor data wirelessly detected by the remote device for display.
  • FHR fetal heart rate
  • the physician may have the ability to read data from the users sensor in realtime over a wireless cellular or Ethernet signal.
  • Exchanging physician contact information and application synchronization between the end user remote device and physician remote device may also be done via virtual handshake or the like in a secure, encrypted manner.
  • an appointments screen 300 may also be added to the user interface.
  • the appointments section of the user interface may be configured to integrate with a native calendar on the remote device as well as with emails and text messages, so that appointments may be seamlessly and effortlessly added to the appointments section of the app.
  • others that the user has connected with through the app such as physicians, nurses, family members, and secretaries, may add appointments and visualize appointments scheduled, if the end user chooses.
  • Various views may be toggled through such as a view of today's events, the week's events and events for the month as well as a timeline view, among others.
  • a notes screen 400 may be added to the user interface.
  • a notes section 410 may be configured to enable storing an end user's questions or concerns with regards to the specific application at hand. For example, in the context of a pregnancy monitor, the end user may record any questions she has about her pregnancy so that the next time she is with her physician, she may ask him her questions. In addition, when in a meeting with her physician, she may record important information in her notes screen so that she may remember the information in the future.
  • This section may also be equipped with voice to text dictation technology, so the patient may simply record the physician's own words and save his text (or voice recording) in her notes section.
  • a user may send her notes and questions directly to her physician via a physician chat interface described below.
  • a user may also share her questions, concerns or experience here and elsewhere with an online community.
  • native device camera functionality may be added to the notes app where the user may take and store photographs and/or video directly in the notes section. These photos similarly may be sent via email, text message, shared on an online community or via physician chat.
  • the notes may be searchable according to the date recorded, keyword entered, user defined tags or other method(s).
  • the notes may also be organized into folders determined by the end user. These folders may be organized according to how the user chooses and the names may be custom generated. Additionally, these folders can be tagged by the user for easy searching.
  • a general knowledge component may also be added to the user interface where the user may look up facts that are relevant to them and their sensor coupled to a patient and/or condition or disease state. For example, in the setting of a pregnancy monitor, the mother may look up definitions of various obstetrics and gynecology terms that are often used by physicians but not adequately defined. A glossary of terms such as pre-term labor, chorioamnionitis, gestational age, gestational diabetes, macrosomia, neural tube defect, preeclampsia, still birth as well as many others may be easily accessed by the mother and sorted alphabetically and/or according to category. In addition, detailed facts relevant to the condition that is being looked up may be accessed by the end user.
  • Each fact presented may be based on primary literature studies from prestigious medical journals and may be updated in real time as new information is presented in the literature. Users may also select and tag various risk factors, conditions or predisposed disease states to be sent as an alert or notification if and when each new piece of data regarding a disease state or condition is reported in the literature.
  • details such as the expected weight gain over time, or the amount of folic acid that is required in her diet at a certain time, and need for special testing may all be integrated in the application.
  • Temporally related information may also be auto populated into the appointments application for seamless integration of knowledge at a relevant point in time. This way, not all the data is presented at once, but only as needed.
  • a frequently asked questions section may also be integrated into the general knowledge section of the application.
  • questions such as "what basic nutrients should I include in by diet?" "How much should I eat during pregnancy?" "What is pica?” may all be answered.
  • This data may be updated in real-time as users ask new questions and experts answer them.
  • the application may also feature a ranking mechanism with respect to frequently asked questions, whereby the highest ranked, answered and commented on questions may appear at the top of results using a standard ranking algorithm. Users may also vote using a thumbs / thumbs down manner, or the like, on relevance and accuracy of the answers posted.
  • a prenatal diagnostic tests timeline may be incorporated in an application on the remote device and provide the end user with a set of warnings to indicate when various tests and obstetrics appointments are recommended during her pregnancy. This may be integrated into the calendar and appointments feature or elsewhere. This way, the end user may be made aware of her recommended schedule according to her current gestational age. Additionally, the user may select via gesture each prenatal diagnostic test to learn more about the procedure in another window of the user interface. This learning interface can include brief descriptions, photos, videos, animations, interactive models, etc.
  • the mother may be informed that Alpha fetoprotein may be attained at 15-20 weeks gestation and the purpose of the test, an amniocentesis is recommended at 15-17 weeks if she is more than 35 years old at the time of delivery, in Rh-sensitized pregnancy, they are informed to attain fetal blood type, etc.
  • pregnant mothers may be warned to attend prenatal visits every 4 weeks.
  • mothers may be warned every 2 weeks to attend prenatal visits, and at 36 weeks gestation and beyond, warned to attend prenatal visits weekly.
  • Women may also be provided with calculators to calculate various changes that may take place during pregnancy.
  • expected weight gain is 25-35 lbs for BMI 19.8-26 (less for obese women, and more for thinner women).
  • the end user may be advised to add an additional 100- 300 kcal/day in her diet during pregnancy.
  • a calorie tracker based on food consumption may also be integrated into the device as well as an exercise tracker to aid in calculating net calories in and calories burned each day.
  • a water tracker may also be integrated to ensure adequate hydration. She may be reminded to take 0.4 mg/day of folic acid if no history of neural tube defects, and 4 mg/day if there is a history of neural tube defects.
  • Iron supplementation with 325 mg iron sulfate in latter half of pregnancy may be added to the list of recommended changes during pregnancy.
  • Chat screens may also be integrated into the application. Telemedicine and the ability to ask questions to physicians in real-time through the application may be an integral component of the user interface.
  • This physician chat may be set up either via application to application, or communication via email, text message, voice message, video as well as other methods of communication. Photographs may also be shared as well.
  • an online community chat may be integrated into the application where the end user of the sensor coupled to a patient may be connected with people in the community with the same wearable device or condition, disease state, or disorder. In this way the end user has the ability to also communicate with the general public about their condition. These people in the general public may be very knowledgeable in area or have some experience in the field of interest.
  • Another feature of the application should include wireless transmission of the analyzed data in the application from the remote device back to the wearable electronic sensor apparatus.
  • the remote device may send a signal to the wearable device to display readout of its findings. This may mitigate the need to look at the remote device.
  • the end user may visualize the status of their pregnancy and fetus by looking at the wearable biosensor instead of the remote device. So, if the fetus is doing well and labor contractions have begun, a green light may illuminate, if the baby is doing poorly, a red light may illuminate, for example.
  • an in-application notification or status message that may be sent by a physician, partner, assistant, or the like, for example for appointment scheduling, may be displayed on the wearable device via a flashing light, or by some other signaling method either visual, audio or tactile.
  • a flashing light or by some other signaling method either visual, audio or tactile.
  • Other possibilities would be to illuminate a light to indicate the fetal heart rate or indicate a rate and/or intensity of contractions of the uterus.
  • the foregoing user interface may be implemented in the hardware context of a handheld wireless computing device 500, for example, a smartphone or tablet computer.
  • the device may include a processor 510 coupled to a memory 520, or to a computer-readable storage medium 522.
  • the memory 520 or computer-readable storage medium 522 may hold program instructions 600 for performing any of the operations of the methods described herein, as described, for example, with reference to Figs. 6-7 below, or in the paragraphs above providing examples of user interface functions in connections with Figs. 1A-B and Figs. 2-4.
  • Operations as described herein for performance by the device 500 may be coded as applications using any suitable programming language, for example, C, Objective C, C++, JavaTM, JavaScriptTM, Object Pascal, or Visual BasicTM. Applications may be developed for standard operating environments, for example, AndroidTM, iOSTM, or WindowsTM, or other environments.
  • the device 500 may further include a wireless interface for receiving data from a health monitoring sensor 530 coupled to a body of the patient.
  • the monitoring sensor may, for example, transmit sensor data directly to the device 500.
  • the sensor 530 may transmit to a router and/or modem (not shown), which may transmit the data via a WiFi (e.g., IEEE 802.1 1 ) or cellular communications network (e.g., LTE) to the device 500.
  • the device 500 may further include one or more suitable receivers, such as a WiFi receiver 540 or a cellular wireless receiver 542, coupled to the processor 510 and memory 520.
  • the device may include one or more suitable transmitters, for example a WiFi transmitter 550 or cellular wireless transmitter 552.
  • the device 500 may further include a touchscreen 560, functioning both as a display screen for displaying any one or more of the user interface displays described herein above and as a user input device for accepting user touch input responsive to a user interface display.
  • the device 500 may include additional user input or output devices, for example, a microphone 570 or speaker (audio transducer) 572.
  • a user interface device e.g., device 500
  • examples of operations of a method 600 for performance by a user interface device are illustrated as blocks of a flow diagram. It should be appreciated that additional or alternative operations may also be performed as a method by a user interface device, for example, any of the operations described above in connection with Figs. 1A-B and 2-4.
  • the method 600 for providing a health status of a patient via a user interface may include receiving 602, by a handheld computing device via a wireless interface, a signal from a sensor coupled to a patient, the signal indicating a health status of the patient.
  • the senor may be coupled to a pregnant woman, and the signal may include an electromyography (EMG) signal correlated in time to a fetal heart rate signal.
  • EMG electromyography
  • the health status may be the status of the pregnant woman's labor.
  • the method may include processing the signal using a processor located in the handheld computing device, thereby obtaining the indication of the health status.
  • the handheld computing device may include at least one of a smartphone or a tablet computer.
  • the method 600 may further include, at 604, providing an indication of the health status of the patient via a touchscreen of the handheld computing device, based on the signal.
  • the indication may include, for example, contraction monitoring information such as shown in screen 200, Fig. 2, or any other suitable information.
  • the method 600 may further include, at 606, enabling user selection of two or more functions related to the indication of health status via a graphical user interface presented on the touchscreen.
  • the method may include generating, as part of the graphical user interface, a scrolling wheel broken down into sections wherein each section presents a button to access a unique screen of the user interface.
  • a scroll wheel 120 is shown, with segments 122, 124, 126, 128 and 129 each enabling access to a different function related to health status.
  • the segment 126 enables access to a contraction information screen described elsewhere herein, which can be accessed by selecting the corresponding segment 126 using a touchscreen or other pointing device.
  • each of the other segments enables access to a different information screen that is related in some way to the health status detected by the sensor signal.
  • the method 600 may further include enabling each section of the scrolling wheel to be relocated to a user-specified location on the scrolling wheel, in response to user input. For example, user touch input (e.g., "holding" a touch for longer than a specified time, a double touch, or a movement of two or more fingers) on a segment of interest may be detected and interpreted as a signal to relocate the segment. The device interface may then respond to further touch input to enable the user to "drag" the segment to a different location on the scroll wheel.
  • user touch input e.g., "holding" a touch for longer than a specified time, a double touch, or a movement of two or more fingers
  • the method of 700 may further include, at 702, presenting real time data recorded by the sensor on the touchscreen interface, in response to user input selecting a first defined section of the scrolling wheel.
  • the real time data may include contraction data correlated to fetal heart rate, as shown in Fig. 2, or any other time- related data of interest.
  • the method 600 may further include, at 704, presenting an interface for scheduling medical appointments on the touchscreen interface, in response to user input selecting a second defined section of the scrolling wheel.
  • This may include wireless signaling to a network node, in response to user input via an entry screen like that shown in Fig. 3.
  • the interface may direct a request for a new appointment to a designated network address for a user-selected physician.
  • the method 600 may include, at 706, presenting an interface for recording text, photographic images or audio notes on the touchscreen interface, in response to user input selecting a third defined section of the scrolling wheel. An example screen for this function is shown at 400 in Fig. 4.
  • User text, audio notes, photos or videos entered by this interface may be stored in the device memory for future reference, transmitted to a designated recipient (e.g., the user's physician), or both.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD- ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on as one or more instructions or code on a non-transitory computer-readable medium.
  • Non- transitory computer-readable media includes computer storage or memory media.
  • a storage media or computer memory may be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray. Combinations of the above should also be included within the scope of computer-readable media..
  • an apparatus and method for interfacing between a portable wireless computing device including a user interface and a remote sensor coupled to a patient is disclosed.
  • the apparatus and method may be used for any desired health monitoring purpose, for example, fetal health monitoring before and during labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

L'invention concerne un procédé pour fournir un état de santé d'un patient par l'intermédiaire d'une interface utilisateur, lequel procédé consiste à recevoir, par un dispositif informatique portatif par l'intermédiaire d'une interface sans fil, un signal à partir d'un capteur couplé à un patient, le signal indiquant l'état de santé du patient, à fournir une indication de l'état de santé du patient par l'intermédiaire d'un écran tactile du dispositif informatique portatif, et à permettre une sélection, par l'utilisateur, d'au moins deux fonctions associées à l'indication d'état de santé par l'intermédiaire d'une interface utilisateur graphique présentée sur l'écran tactile. L'interface utilisateur graphique peut comprendre une molette de défilement décomposée en sections, chaque section présentant un bouton pour accéder à un écran unique de l'interface utilisateur. Un appareil, tel qu'un téléphone intelligent ou un autre dispositif sans fil portable, peut être programmé pour réaliser des opérations du procédé.
PCT/US2014/051760 2013-08-20 2014-08-19 Interface utilisateur pour dispositif électronique vestimentaire WO2015026872A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201361868049P 2013-08-20 2013-08-20
US61/868,049 2013-08-20

Publications (1)

Publication Number Publication Date
WO2015026872A1 true WO2015026872A1 (fr) 2015-02-26

Family

ID=52484109

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/051760 WO2015026872A1 (fr) 2013-08-20 2014-08-19 Interface utilisateur pour dispositif électronique vestimentaire

Country Status (1)

Country Link
WO (1) WO2015026872A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105988588A (zh) * 2015-03-19 2016-10-05 三星电子株式会社 包括触摸面板的电子设备和控制电子设备的方法
WO2024064235A1 (fr) * 2022-09-23 2024-03-28 Apple Inc. Élément d'interface utilisateur de molette d'écran tactile

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110004073A1 (en) * 2008-02-28 2011-01-06 Koninklijke Philips Electronics N.V. Wireless patient monitoring using streaming of medical data with body-coupled communication
WO2012036386A2 (fr) * 2010-09-15 2012-03-22 전자부품연구원 Système de surveillance de patient d'un système de communication à distance sans fil pour usage médical
US20120129139A1 (en) * 2010-11-23 2012-05-24 Sanitas, Inc. Disease management system using personalized education, patient support community and telemonitoring
KR20120120817A (ko) * 2011-04-25 2012-11-02 상지대학교산학협력단 센서 노드와 임베디드 기기에 기반한 원격 환자 모니터링 시스템
WO2013119982A2 (fr) * 2012-02-09 2013-08-15 Masimo Corporation Dispositif sans fil pour la surveillance de patients

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110004073A1 (en) * 2008-02-28 2011-01-06 Koninklijke Philips Electronics N.V. Wireless patient monitoring using streaming of medical data with body-coupled communication
WO2012036386A2 (fr) * 2010-09-15 2012-03-22 전자부품연구원 Système de surveillance de patient d'un système de communication à distance sans fil pour usage médical
US20120129139A1 (en) * 2010-11-23 2012-05-24 Sanitas, Inc. Disease management system using personalized education, patient support community and telemonitoring
KR20120120817A (ko) * 2011-04-25 2012-11-02 상지대학교산학협력단 센서 노드와 임베디드 기기에 기반한 원격 환자 모니터링 시스템
WO2013119982A2 (fr) * 2012-02-09 2013-08-15 Masimo Corporation Dispositif sans fil pour la surveillance de patients

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105988588A (zh) * 2015-03-19 2016-10-05 三星电子株式会社 包括触摸面板的电子设备和控制电子设备的方法
WO2024064235A1 (fr) * 2022-09-23 2024-03-28 Apple Inc. Élément d'interface utilisateur de molette d'écran tactile

Similar Documents

Publication Publication Date Title
AU2021218036B2 (en) Wellness data aggregator
US20200357522A1 (en) Wellness aggregator
US20230014290A1 (en) Wellness aggregator
US10313506B2 (en) Wellness aggregator
US10278581B2 (en) Wireless pregnancy monitor
EP2441015B1 (fr) Systèmes et procédés de visualisation de données de patient
US20150238150A1 (en) Smartwatch with a multi-purpose sensor for remote monitoring of a patent
EP3268881B1 (fr) Méthode et dispositif portable pour obtenir des données audio pour le diagnostic
US11830590B2 (en) Maintaining context of clinically relevant information when displayed
EP2405803A1 (fr) Systèmes et procédés de visualisation de données concernant des patients
US20170344715A1 (en) Health managing device and health managing method
WO2020132351A1 (fr) Système d'affichage de données médicales en temps réel indépendant de la plate-forme
US20130158366A1 (en) Handheld device for fetal health monitoring and method thereof
US20140276239A1 (en) Method and apparatus for integrated medical services using a multi-purpose sensor for remote monitoring of a patient
WO2011116314A1 (fr) Procédé et système destinés à des diagnostics de médecine cutanée
US20200113506A1 (en) Health monitoring method, wearable device, health monitoring system, and computer readable storage medium
US20170235905A1 (en) Telemedicine Data and Video Management System
US20150119749A1 (en) Systems and methods for monitoring fertility using a portable electronic device
WO2015026872A1 (fr) Interface utilisateur pour dispositif électronique vestimentaire
Tumpa et al. Smart care: An intelligent assistant for pregnant mothers
Kuo et al. A newborn baby care support app and system for mHealth
KR101075596B1 (ko) 당뇨병 관리 어플리케이션 제공 방법 및 그 장치
US20220165412A1 (en) Apparatus and method for monitoring and assisting pregnant women
CN106663303A (zh) 少儿健康管理系统及少儿健康管理方法
JP6064233B2 (ja) 健康管理システム、端末装置、表示方法及び制御プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14838060

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14838060

Country of ref document: EP

Kind code of ref document: A1