Modular medical station with access control and expandability capabilities

Abstract

The embodiment relates to a medical station deployable in various locations with expandable plug-in software and hardware components. The medical station includes access control features that limit persons to enter for use and restrict the software or hardware components that persons can use. Actuators of the medical station are operated to ensure that persons can use the components in a timely and sufficient manner. Some of the actuators are located in drawer assemblies that operate to provide access to medical supplies or instruments to a person or human assistant.

Description

Technical Field

[0001] Embodiments relate to modular medical stations and systems for rapid and efficient deployment at various locations, including such modular medical stations.

Background Art

[0002] To receive medical diagnosis, treatment, or examination, patients generally visit a medical facility such as a hospital. Such medical facilities may be located away from the patient's home or workplace. Visits to medical facilities may sometimes involve long travel times to the facilities. Therefore, it would be desirable to have medical facilities deployed across various locations. However, building medical facilities at different locations involves significant investment due to the use of large spaces and substantial construction costs, as well as hiring medical staff at each location.

Summary of the Invention

Problems to be Solved by the Invention

[0003] To reduce costs and facilitate medical treatment for a large number of patients, virtual sessions with medical staff via video conferencing or email are becoming more common. However, such virtual sessions are often limited in that medical devices cannot be used or their use is restricted at the patient's location. Therefore, only a limited type of medical services can be provided to patients via virtual sessions.

Means for Solving the Problems

[0004] The embodiment relates to a medical station that selectively allows a person to enter and activates one or more applications selected by the person receiving medical services. Input is received regarding whether the person has the authority to access the medical station. When it is determined that the person has the authority to access the medical station, the medical station selectively allows the person to enter the medical station. After entering the medical station, the person may select an application to be activated within the medical station. After activating the selected application, the application may grant the person access to use the medical equipment or components of the medical station.

[0005] In one or more embodiments, a control signal is received after the application is launched. Upon receiving the control signal, one or more actuators of the medical station are activated to allow a person to access a medical device or component.

[0006] In one or more embodiments, when a control signal is received, one or more actuators operate the drawer or tray.

[0007] In one or more embodiments, when a control signal is received, a visual indicator associated with the activated drawer or tray is turned on.

[0008] In one or more embodiments, multiple applications are stored in the medical station. Depending on the access permissions of the person, a subset of applications that the person can access is determined, and that subset of applications is presented to the person for selection.

[0009] In one or more embodiments, another medical device or component is stored in the medical station. Access to the other medical device or component is restricted to the operation of another application.

[0010] In one or more embodiments, the application is associated with different healthcare providers.

[0011] In one or more embodiments, the application is received via a communication network from a computing device located remotely from the medical station.

[0012] In one or more embodiments, it is determined whether the received application meets predetermined requirements related to the medical station. One or more of the received applications that meet the predetermined requirements are installed in the medical station.

[0013] In one or more embodiments, a predetermined requirement refers to the installation of a corresponding medical device or corresponding component in a medical station.

[0014] In one or more embodiments, a person is made able to enter the medical station by opening or unlocking a door to enter the medical station.

[0015] In one or more embodiments, measurements of a person are performed using sensors at a medical station.

[0016] In one or more embodiments, the application presents a series of questions to a person. The application performs a series of actions, which include the use of medical devices or components within a medical station.

[0017] In one or more embodiments, information related to a person or treatment performed on a person is collected using a medical device or component. The collected information is transmitted via a communication network to a computing device located remotely from the medical station for analysis and processing.

[0018] In one or more embodiments, the person's medical records on a computing device are updated according to the collected information.

[0019] Embodiments also relate to a medical station having a restricted entrance that selectively allows a person to enter its interior. The medical station includes an interface device for receiving input associated with the authority to access the medical station. A computing device within the medical station receives input from the interface device and, when it determines that the person has the authority to access the medical station, allows the person to enter the restricted entrance by granting access to the interior of the medical station. The computing device also receives from the person a selection of a first application to be launched in the medical station, and after launching the selected application, grants the person access to use the medical equipment or components of the medical station. [Brief explanation of the drawing]

[0020] [Figure 1] This is a block diagram illustrating an overall network environment, including a medical station, according to one embodiment. [Figure 2] This is a block diagram of a medical station according to one embodiment. [Figure 3] This is a block diagram illustrating a software module in memory according to one embodiment. [Figure 4] This is a block diagram illustrating the components of a backend server according to one embodiment. [Figure 5]Perspective view of a medical station according to one embodiment. [Figure 6A] It is a figure which shows the pop-up type drawer which has a medical instrument by one Embodiment. [Figure 6B] It is a figure which shows the pop-up type drawer which has a medical instrument by one Embodiment. [Figure 7A] It is a figure which shows the exemplary user interface screen of a medical station by one Embodiment. [Figure 7B] It is a figure which shows the exemplary user interface screen of a medical station by one Embodiment. [Figure 8A] It is a figure which shows the exemplary external structure of a medical station by one Embodiment. [Figure 8B] It is a figure which shows the exemplary external structure of a medical station by one Embodiment. [Figure 9] It is a figure which shows the exemplary internal structure of a medical station by one Embodiment. [Figure 10] It is a flowchart which shows the operation of a medical station by one Embodiment.

Mode for Carrying Out the Invention

[0021] Embodiments are described herein with reference to the accompanying drawings. However, the principles disclosed herein may be embodied in many different forms and should not be construed as limited to the embodiments described herein. In this specification, details of well-known features and techniques may be omitted in order to avoid unnecessarily obscuring the features of the embodiments. In the drawings, the same reference numerals in the drawings represent the same elements. The shapes, sizes, and regions, etc. in the drawings may be exaggerated for clarity.

[0022] The embodiment relates to a medical station deployable in various locations with expandable plug-in software and hardware components. The medical station includes access control features that limit persons to enter for use and restrict the software or hardware components that persons can use. Actuators of the medical station are operated to ensure that persons can use the components in a timely and sufficient manner. Some of the actuators are located in drawer assemblies that operate to provide access to medical supplies or instruments to a person or human assistant.

[0023] Figure 1 is a block diagram illustrating the overall network environment 100 of a medical station 140 according to one embodiment. The network environment includes a backend server 120, a service developer device 130, and the medical station 140, which communicate over network 110. Although the service developer device 130 is shown in Figure 1 as communicating directly with the backend server 120, the service developer device 130 may communicate with the backend server 120 and / or the medical station 140 via network 110.

[0024] The medical station described herein is a prefabricated modular structure equipped with sensors and medical devices for providing medical services to patients. The medical station 140 may have predetermined dimensions, such as 10 feet x 15 feet or any other preferred dimensions, and can be installed inside or outside a building. An exemplary structure of the medical station 140 is described in detail below with reference to Figure 2. The medical station 140 communicates with the backend server 120 to send and receive login information of patients accessing the medical station 140, to send and receive information related to applications launched at the medical station 140, and to send information on the inventory of medical devices at the medical station 140.

[0025] Due to its relatively small size and ease of installation, the medical station 140 can be beneficially deployed in a variety of geographical locations at a relatively low cost. The medical station 140 may be mass-produced in a factory and may have a form and structure adapted for deployment at low construction costs. Patients may visit one of several locations where the medical station is installed to receive medical services.

[0026] In one or more embodiments, the medical station 140 may become operational immediately after being plugged into a power outlet and wireless or wired communication is established. Thus, compared to the weeks or months required for building and configuring equipment in a medical facility, the medical station 140 may be deployed and operational within a day or even a few hours. Furthermore, the medical station 140 can be easily relocated to another location, for example, in response to changing needs at different locations. It should be noted that in some embodiments, the medical station 140 may have an independent power source such as solar panels, generators, or fuel cells. Similarly, the medical station 140 may have a built-in self-contained wireless communication system, eliminating the need to connect to a separate communication interface before the medical station is deployed and operational. In some embodiments, the medical station 140 may be deployed outdoors, may be mobile (e.g. via built-in wheels or other transport infrastructure), may be self-leveling (e.g. via one or more position or orientation adjustment mechanisms), and / or may be pre-assembled or pre-manufactured for on-site assembly.

[0027] To expand the capacity or service capacity at a location, two or more medical stations 140 may be located at the same site. For example, two or more medical stations 140 with the same configuration may be located at the same site (e.g., a shopping mall) so that multiple patients can receive medical services simultaneously. Alternatively, medical stations with different configurations may be located at the same site so that patients can receive different types of medical services at the same site. For example, one medical station may be customized to diagnose or treat cardiovascular diseases, while another medical station may be customized to diagnose or treat mental health problems. For each customization, each medical station may have different medical instruments and / or plug-in components available for use by patients. Such plug-in components may be hardware components or software components.

[0028] The backend server 120 is a computing device that assists or supports the medical station 140 in providing medical services to patients. The backend server 120 can store various applications from the service developer device 130 and send applications to the medical station 140 for deployment. The backend server 120 can also evaluate the performance of various services provided through the medical station 140 by collecting information received from the medical station 140 and take action to manage the medical station 140. The components and functions of the backend server 120 are described in detail below with reference to Figure 4.

[0029] The service developer device 130 is a computing device for developing and / or researching medical services provided using the medical station 140. For this purpose, the service developer device 130 can receive information about the health status of current and past patients, treatments received by patients, and other sources, and can execute specialized algorithms. By receiving and processing such information, the service developer device 130 can update the parameters of applications that can be executed at the medical station and develop or assess treatment protocols.

[0030] The service developer device 130 may be operated by the same entity that operates the medical station 140. Alternatively, each service developer device 130 may be managed and operated by a different entity than the one that operates the medical station 140. In such a case, the entity that manages or operates the service developer device may pay a fee to the entity that operates the medical station 140 for deploying its application and enabling patients to use its services at the medical station 140. Alternatively, these entities may enter into fee-sharing agreements to distribute fees collected from patients or their health insurance companies. Different entities may also purchase, license, or lease medical stations and pay a fee to access and use the service developer device 130, or they may develop their own platform and implement the service developer device 130 to operate in a manner consistent with their own business model. Various types of agreements may be made between the medical station manufacturer, service developers, insurance companies, and other payers and patients accessing the medical station 140.

[0031] Network 110 is a set of devices that enable computing devices to communicate with each other. Various communication protocols, including but not limited to wireless network protocols such as Internet Protocol, Ethernet, and cellular standards, may be used by Network 110.

[0032] Figure 2 is a block diagram of a medical station 140 according to one embodiment. The medical station 140 may include, among other components, a computing device 220, one or more display devices 230, an input device 232 for receiving user input, a drawer assembly 240, a sensor 250, a network interface 260, and a plug-in component 270. The medical station 140 may also include other components not shown in Figure 2, such as a turntable on which the patient stands for scanning the patient's body with a body scanner, an interface that allows third-party or modular equipment or sensors to connect to the equipment and provide data / power to and from the equipment, and any other suitable equipment that expands the functionality of the medical station 140.

[0033] The computing device 220 executes logic for interfaces and controls other components of the medical station 140. For this purpose, the computing device 220 may include, among other components, a processor 222, a component interface 224, and memory 226. The processor 222 is hardware circuitry, or hardware circuitry combined with firmware that executes instructions stored in memory to perform various functions in the computing device 220. Memory 226 is a non-temporary storage medium for storing software modules executable by the processor 222. Details of the software modules in memory 226 are described below in detail with reference to Figure 3. The component interface 224 is hardware, or hardware combined with software that enables it to interface with medical instruments 248 (if applicable), sensors 250, and / or plug-in components 270. The component interface 224 may include multiple subunits that enable the computing device 220 to communicate with different components of the medical station 140 via different protocols.

[0034] The display device 230 receives display signals from the computing device 220 to display various images to the patient or a human assistant. In one embodiment, one of the display devices 230 may be a touch screen embedded in the wall of the medical station 140. Multiple display devices may also be included in the medical station 140. For example, a display device may be installed at the entrance of the medical station 140 to display information about access to the medical station 140 and / or the types of medical services provided by the medical station 140, while another device installed inside the medical station 140 may display a graphical user interface for selecting and receiving specific medical services.

[0035] The input device 232 is a device for receiving user input. The input device 232 may be embodied as part of a display device (e.g., a touch sensor) or as part of a separate component (e.g., a microphone, mouse, or keyboard). Two or more input devices may be included in the medical station 140 to assist different types of user input.

[0036] The drawer assembly 240 is a mechanically operated drawer that allows a patient or human assistant to selectively access medical instruments or supplies. The drawer assembly may be locked or unlocked by the operation of an actuator 244 that operates according to a control signal from a computing device 220. Some of the drawer assemblies may have different sizes (e.g., height and width) to facilitate the user in identifying the correct drawer assembly to use and accommodating instruments of different dimensions. In addition, or alternatively, some or all of the drawer assemblies may include a visual indicator (e.g., a lighting element) that is turned on when selected for use by an application running on the computing device 220. By turning on the visual indicator, the user can easily identify the drawer assembly containing medical instruments or supplies related to an action to be performed by the user. The computing device 220 may also track previously opened drawer assemblies to prevent the reuse of the same used medical instrument on another patient for hygienic reasons.

[0037] In one or more embodiments, the inventory of medical instruments in the medical station 140 may be tracked and managed by a backend server 120, as described in detail below with reference to Figure 4. Examples of working drawer assemblies and their configurations are described in detail below with reference to Figures 6A and 6B. The medical instruments 248 may include, among other things, a wireless heart rate monitor, a digital stethoscope, a non-contact thermometer, a pap smear kit, a blood collection kit, vaccine supplies, an ear cleaning kit, a dermatoscope, or any other suitable device or equipment for self-administration or administration by a healthcare provider. At least some of these medical instruments 248 communicate via the component interface 224 to enable the collection of patient information in real time, while other medical instruments 248 are collected for further examination and analysis. In some embodiments, the drawer assembly 240 functions as an API, enabling a third-party entity to interface with the medical station 140 by specifying the requirements for the drawer (size requirements, temperature control requirements, power requirements, etc.) for providing, for example, pharmaceuticals, therapeutic or diagnostic equipment, or other medical or health equipment to an individual.

[0038] Sensors 250 are provided in the medical station 140 to detect the patient's physical characteristics or position. In one embodiment, sensor 250 may be embodied as a body scanner that detects the dimensions of various parts of the patient's body. The body scanner may be used in cooperation with a turntable (not shown) that rotates the patient and measures the patient's weight while the scan is being performed. A glucose meter may also be provided in the medical station 140 as one of the sensors 250 for detecting the patient's blood glucose level by or without taking a blood sample from the patient. The chairs in the medical station 140 may include one or more sensors for detecting the presence or posture of a patient sitting in the chair. Additional sensors 250 may include a thermographic sensor, a blood pressure measurement system, a blood oxygenation detection system, a heart rate monitor, a body position sensor, a glucose meter, or any other suitable sensor or measurement / detection system.

[0039] The network interface 260 is hardware, or hardware combined with firmware that enables the medical station 140 to communicate with the backend server 120 or service development device 130 via the network 110. The network interface 260 may include, for example, antennas and circuits for communication over the Internet via wireless communication, and / or network cards for communication over wired communication (e.g., Ethernet), or over a private network or peer-to-peer.

[0040] Plug-in components 270 are physical components added to the medical station 140 to extend its functionality. Plug-in components 270 may include digital stethoscopes, digital dermatoscopes, pap smear kits, electrocardiogram machines (e.g., EKG machines), ultrasound devices, spirometers, radiographers, blood sampling kits, treatment kits (e.g., cryo-guns, ear cleaning kits, surgical kits, etc.), exercise equipment (e.g., resistance bands), food and beverages, merchandise, prescription drugs, over-the-counter drugs, educational materials, or informational materials. The functionality of the medical station 140, which can utilize the plug-in component 270, includes, but is not limited to, generating a three-dimensional body model, measuring blood oxygenation, measuring / listening to heart sounds, performing venipuncture or other blood sampling, measuring weight or height, administering vaccines or other injections, performing nasal swabs, collecting urine samples or other specimens, measuring blood pressure, observing the inside of a patient's ears / nose / mouth / throat, taking images of a patient's skin, performing ultrasound / X-ray / MRI on a patient, observing a patient's eyes (e.g., using an ophthalmoscope), performing EKG, performing CT scans, performing vital capacity measurement, analyzing a patient's posture, performing electrocardiogram telemetry, performing intraocular pressure measurement, taking retinal or other images of a patient's eyes or other organs / body parts, taking thermal or hyperspectral images of a patient, and analyzing a patient for chemicals or other compositions.

[0041] The plug-in component 270 communicates with the computing device 220 using any combination of wired and wireless signals, such as WiFi, Bluetooth, radio frequency, cellular network, satellite, infrared, millimeter wave, USB, serial, Ethernet, optical fiber, and direct signal wire, whether directly or via the internet. This may also include manual methods for transmitting information from the plug-in component to the station, such as data input via touch screen, keyboard, controller, and / or voice as input from the patient and / or provider. Furthermore, the plug-in component 270 may have a dedicated power connection for supplying power from the station to the component, such as a combination of a wireless interface for power transmission, a conductor contact interface, and / or a contact insertion interface. These may be used to actively power the plug-in component or even to charge the component for use when it is relocated.

[0042] Figure 3 is a block diagram illustrating software modules in the memory 226 of a medical station 140 according to one embodiment. Memory 226 may store various software modules, including but not limited to the operating system 302, applications 310, application manager module 330, access control module 320, support module 340, treatment information module 350, and training module 360. Memory 226 may also store software modules other than those illustrated in Figure 3, and one or more of the modules in Figure 3 may be combined into a single module or split into further modules.

[0043] Application 310 is a software module for interacting with patients in order to provide them with medical or health-related services. Each application 310 may focus on different aspects of medical / health services (e.g., mental health checkup services and cardiovascular health checkup services). In some embodiments, different sets of applications developed and managed by different healthcare entities may be stored in memory 226. For example, different sets or pairs of applications may be available to different patients depending on the patient's health insurance plan, the patient's age / gender, the patient's membership level, or other criteria.

[0044] Some of the applications 310 may, while operating, make one or more instruments 248 in a drawer assembly 240 available to the patient. For this purpose, while the application 310 is active, the application may cause the component interface 224 of the computing device 220 to send a start signal to the appropriate drawer assembly 240 in a timely manner. If multiple medical instruments 248 are expected to be accessed by the patient, the active application may send a series of start signals to activate the actuators 244 of the relevant drawer assembly 240 so that the relevant medical instruments 248 can be accessed by the patient in sequence. For example, when a patient activates a routine health check application, the application may first provide a thermometer, then a blood collection device and a urine sample bottle, by sequentially operating the drawer assembly 240 having the relevant instruments. Furthermore, in response to input signals from the patient or from previous medical instruments, the application may change the next medical instrument to be accessed by the patient.

[0045] Application 310 may also operate the plug-in component 270 to perform further examinations on the patient. The use of or access to a particular plug-in component 270 may be restricted to a subset of applications. For example, a plug-in component specifically designed for a particular healthcare provider may be accessed or used only by applications developed or affiliated with the same healthcare provider. Such restrictions on access and aggregation of available instruments may be implemented by the access control module 320.

[0046] The Application Manager Module 330 is a software module that manages the deployment and availability of Application 310 at Medical Station 140. For this purpose, the Application Manager Module 330 communicates with the backend server 120 to receive the most recent version of Application 310, deploys only applications that meet the criteria applicable to the current medical station, and may discard or delete applications that are expired or do not comply with rules, agreements, or other standards. Such management operations may be performed periodically by the Application Manager Module 330, initiated by update requests received from the backend server 120 or by maintenance personnel accessing the medical station.

[0047] In one or more embodiments, a particular application may be installed and deployed to a medical station only when certain requirements are met. For example, an application may be installed only when the medical station has a specific installed plug-in component. Alternatively, a particular application may be installed only when the medical station is located in an authorized geographical area or location, or enabled only when an authorized or skilled operator is present. A particular application may also be installed and deployed for use in planning, scheduling, and forecasting patient visits. Such restrictions may be enforced by the application manager module 330. Restrictions such as those defined in the application manager module 330 may be updated by the backend server 120.

[0048] In some embodiments, the medical station 140 and / or backend server 120 coordinate to implement controls over which applications are installed at the medical station based on regulatory controls and requirements related to the jurisdiction in which the medical station is located, personnel allocation and training related to the medical station, components and equipment available at the medical station, or any other preferred factors. In some embodiments, the medical station 140 itself does not host applications locally, but instead accesses applications stored in one or more cloud services. In some embodiments, the applications installed within the medical station 140 are limited by the capabilities provided by the applications, for example, depending on the availability of equipment or personnel required to implement one or more functionalities of the applications.

[0049] The access control module 320 is a software module that controls access to the resources of the medical station. The access control module 320 may communicate with the backend server 120 to ensure that only authorized patients enter and utilize the medical station. The access control module 320 may also receive the patient's electronic medical record (EMR) from the backend server 120 or other sources and provide the information to application 310 in a format compliant with rules and / or contracts. The access control module 320 may also restrict the use of certain medical devices 248 or plug-in components 270 to application 310 depending on whether certain criteria are met (e.g., the patient has a certain membership level) and / or whether there is a provider with the appropriate qualifications.

[0050] The support module 340 is a software module that works in conjunction with a human assistant (live or asynchronous, on-site or remote) to provide services to a patient. Actions initiated by one or more applications 310 may require assistance from a human assistant. Such actions may involve acts that are impractical or impossible to perform automatically and lawfully without human assistance at the medical station 140 and may involve the operation of certain medical instruments 248 or plug-in components 270. The support module 340 may store a list of human assistants and their qualifications and may notify the appropriate human assistant from among several human assistants to assist the patient. In one or more embodiments, the application 310 may instruct the support module 340 to send a request to a human assistant during those actions. In some embodiments, the support module 340 may call or initialize a robotic device instead of, or in addition to, requesting human assistance. Such a robotic device may perform actions such as, for example, drawing a blood sample from a patient or assisting a patient in assuming a specific posture.

[0051] The treatment information module 350 is a software module for collecting patient information related to the treatment being given to the patient. Patient information may include treatments received by the patient and various information about the patient before and after treatment commencement. Such information may include medications taken, physical therapy performed on the patient, patient dimensions / weight, blood test results (e.g., blood glucose levels), blood pressure measurements, and response to treatment. The treatment information module 350 may transmit the collected patient information to the backend server 120 for further analysis and processing, as described in detail below with reference to Figure 4. In some embodiments, the patient's mobile device may interface with the medical station 140 or the backend server 120 to access patient information (treatment information, medical station usage information, etc.) and present such information within an application running on a mobile device, for example.

[0052] The training module 360 ​​is a software module that instructs the patient and / or human assistant to perform specific actions. The patient may be presented with video and / or audio files with instructions on how to operate the medical instrument 248 and / or plug-in components 270. The human assistant may also be presented with instructions to assist the patient during diagnostic or therapeutic actions performed on the patient within the medical station 140. Some training instructions may be provided to the human assistant when the patient is not within the medical station 140. In some embodiments, the qualifications of the human assistant or caregiver are monitored to track individual qualifications, and these qualifications may be measured based on comparison with other human assistants, based on a baseline set of evaluation criteria, based on user feedback, or based on any other preferred criteria. In some embodiments, the training module 360 ​​may provide the human assistant with information detailing the user's preferences (such as arm preferences, aversion to needles, desired user posture during the action being performed) or the user's history (such as past complications, past complaints, previous favorable experiences). The training module 360 ​​can leverage current best practices for specific care scenarios in real time, beneficially enabling medical stations to provide the best / preferred care within any given time. Furthermore, the data collected from medical stations 140 can generally enable the development and deployment of new care procedures, the standardization of care protocols, the consistent application of care, the improvement of training protocols and procedures, and the alignment of care standards with local care-focused rules.

[0053] The operating system 302 is a set of instructions for managing the resources of the computing device 220. Exemplary operating systems include Microsoft Windows, Unix, macOS, Linux, iOS, and Android. In addition, the operating system 302 can control the lighting, sound (music, instructions, prompts, voice selection, etc.), logistics functions (medical station inventory, next patient steps, instructions for human assistants, medical station or user monitoring, etc.) of the medical station 140, as well as automation functions (automated supply / capacity management, automated laboratory processing, etc.).

[0054] Figure 4 is a block diagram illustrating the components of a backend server 120 according to one embodiment. The backend server 120 may also include, among other components, a processor 402, memory 410, a network interface 406, and a bus 450 connecting these components. The backend server 120 may also include other components not shown in Figure 4.

[0055] Processor 402 reads and executes instructions stored in memory 226 to perform various operations on the backend server 120. Although only a single processor 402 is illustrated in Figure 4, the backend server 120 may contain multiple processors.

[0056] The network interface 406 is hardware, or hardware combined with firmware or software for communicating with the medical station 140 and / or the service developer device 130. For this purpose, the network interface 406 may implement various wired or wireless protocols.

[0057] Memory 410 is a non-temporary storage medium for storing software modules. Memory 410 may include, among other software modules, an application repository 412, a patient information module 420, a medical station management module 430, and a treatment assessment module 440. Memory 410 may also store other software modules not shown in Figure 4. Two or more software modules in Figure 4 may be combined into a single module, or one software module in Figure 4 may be split into multiple software modules.

[0058] The application repository 412 stores applications 416 that should be sent to the medical station 140 for installation. The application repository 412 can keep the most recent version of application 416 and can record and store older versions of application 416. Newer applications, or updated versions of application 416, may be automatically received from the service developer device 130 and stored in the application repository 412. In addition, or alternatively, application 416 may be manually transferred to and stored in the application repository 412 by a human operator. The application repository 412 may also store metadata for application 416, including but not limited to the associated application, the stored version of the application, the ID of the developer who created the application, and members who are entitled to access the application.

[0059] In other embodiments, the backend server 120 does not include the application repository 412. Rather, the medical station 140 receives applications directly from developers, either via the network or through manual installation.

[0060] The patient information module 420 is a database containing a list of patients and their membership information (e.g., name, age, gender, membership level, insurance information). The patient information module 420 may also include the patient's EMR, which can be updated based on diagnostic work and treatment performed at the medical station 140. Similarly, the EMR or other patient information may be updated via a mobile device, via a customary visit to a medical facility, via a web interface, via a health app, or via any other preferred means. The patient information module 420 may be accessed by the medical station 140 to determine whether a patient should be granted access to the medical station 140 and / or a specific application 310 that can be run at the medical station 140.

[0061] The medical station management module 430 is a software module that performs various management operations related to the medical station 140. The medical station management module 430 may track the inventory of medical equipment available at the medical station 140 and take action to replenish the inventory if it is running low. For this purpose, the medical station management module 430 may send an order to a warehouse to transport the equipment 248 to the location where the medical station 140 is located. The medical station management module 430 may also instruct maintenance personnel to visit a specific medical station and perform prescribed maintenance work there.

[0062] The treatment assessment module 440 performs analysis to determine the effectiveness of treatments given to a patient. For this purpose, the treatment assessment module 440 may receive patient information from one or more medical stations 140. Various statistical analyses may be performed on the patient information to determine the efficacy or performance of treatment options. In some embodiments, the distribution of multiple medical stations 140 as described herein allows users to access care more frequently than they would need to visit a conventional clinic, and enables the collection of a larger volume of patient data. Similarly, the medical stations 140 described herein enable the collection of more different types of patient data. The medical stations 140 can leverage this data to assess loyalty to and effectiveness of specific treatment options, which can then be used to evaluate best course of action or treatment guidelines for recommendations to other users. Patient information may be provided to the treatment assessment module 440 in real time to enable healthcare providers to evaluate, assess, and select treatment options. In addition, patient information (such as demographic or geographical information, health risks, existing conditions, and history) may be used to recommend specific health apps or programs provided by Medical Station 140.

[0063] The backend server 120 can access multiple datasets related to a patient or a medical station 140. For example, the backend server 120 may access patient data from one or more medical data repositories, from applications operated by the medical station 140 with which the patient interacts, from mobile applications used by the patient via one or more mobile devices (such as health applications or fitness applications), from wearable devices worn or used by the patient, or from any other suitable source. Similarly, the backend server 120 may access data describing preferred treatment methods or care standards from medical or scientific literature, from government organizations or agencies, from commercial data sources, or from any other suitable data sources. The data accessed by the backend server 120 may then be used to develop a patient treatment plan for recommendations to the patient, to inform one or more healthcare professionals about the patient, or for any other suitable use. In some embodiments, the accessed data (e.g., from a group of patients) may be used to train one or more machine learning models, which may be used to inform or predict future patient treatment plans. Finally, the accessed data may enable the medical station 140 or the backend server 120 to approve treatment plans prepared by healthcare professionals and to flag any anomalies within such treatment plans (such as treatment plans that do not follow best practices, as identified by the medical station or the backend server).

[0064] Figure 5 is a perspective view of a medical station 140 according to several embodiments. The medical station 140 may include a chassis 524 that forms an outer enclosure as illustrated in Figure 5. The chassis 524 may be in the shape of a cube, with one wall 522 having an entrance 526 with an automatic door 514 and another wall having a display screen 508. The display screen 508 may be a touch screen that allows the patient to provide answers or responses to displayed choices.

[0065] A chair 512 is provided on one side of the medical station 140. The patient may sit in the chair to undergo various examinations and provide feedback via an input device 232. In one or more embodiments, plug-in components 270 may be attached to the chair 512 to extend the functionality of the medical station 140. The chair 512 may include another sensor 520 that detects the presence or posture of a patient on the chair 512.

[0066] The wall 522 also has an interface 504 (e.g., a touchscreen or console) on the side of the entrance 526 that allows the patient to input information and access the medical station 140. The automatic door 514 attached to the wall 522 may be opened only when the computing device 220 determines that the patient has the right or authority to enter the medical station 140.

[0067] A drawer assembly 240 is installed on wall 518. The drawer assembly 240 may be operated by the operation of an application 310 performed by a medical station 140. Figures 6A and 6B illustrate a drawer assembly 240 having a medical instrument 248 according to one embodiment. When the application 310 determines that it is time to give patient 614 access to a particular medical instrument, the actuator of the drawer assembly containing the particular medical instrument operates to transition from a closed state (as illustrated in Figure 6A) to an open state (as illustrated in Figure 6B). To assist patient 614 in identifying the correct drawer, a visual cue may be provided on the corresponding drawer assembly. The visual cue may include, for example, lighting up the entire surface of the drawer (as illustrated in Figure 6A by the hatching pattern of drawer 240A) or a symbol on the surface (as illustrated in Figure 6B). Note that while a drawer assembly is referred to herein, in practice any delivery mechanism, including but not limited to cabinets and pockets, may be substituted for a drawer assembly. The selected drawer may be opened manually after being unlocked, or it may be opened automatically by an actuator. After the drawer is opened, the patient, a human assistant, or a robotic device may take the medical instrument 248 from the drawer to perform further work on the patient.

[0068] Figures 7A and 7B illustrate the external structure of the medical station 140 according to one embodiment. Figures 7A to 9 illustrate exemplary user interface screens, external structures, and internal structures of the medical station 140 according to various embodiments.

[0069] Figure 7A is a user interface diagram illustrating a screen presented on a touch screen near an entrance door according to one embodiment. Figure 7B is a user interface diagram illustrating a screen presented on a display screen 508 on a wall inside a medical station according to one embodiment. In Figures 7A and 7B, each box or icon represents an application that may be run by the medical station 140 for use by a patient. A patient or human assistant may select one of the boxes or icons displayed on the screen to start an application relevant to the patient. The box or icon presented on the display device may be selected and / or updated by the access control module 320. User input for selecting a box or icon may be received via touching the screen, voice commands, gestures, or other forms of user input.

[0070] Figures 8A and 8B illustrate an exemplary external structure of a medical station according to one embodiment. As shown in Figures 8A and 8B, the medical station 140 has an outer frame 524, a door 514, and an adjacent door panel. The door 514 can be used by a patient to access the interior of the medical station 140, and the door panel may include an interface 504 that allows the patient to check in to the medical station, to identify or authenticate themselves, to determine the capabilities of the medical station, to identify the functionality desired by the patient or what the patient needs, etc.

[0071] The medical station 140 may include components to facilitate installation and deployment. Such components may include a power plug-in unit 804 and a communication system 808. The power plug-in unit 804 may be connected to an outlet to receive power. In remote locations, the plug-in unit 804 may be connected to a battery pack or a generator. If access to the power grid is readily available, the plug-in unit 804 may receive power from the power grid. The communication system 808 is connected to a network interface 406 to enable the medical station 140 to communicate with a backend server 120 or other external computing devices. The communication system 808 may be compatible with wireless or wired communication networks.

[0072] Figure 9 illustrates an exemplary internal structure of a medical station according to one embodiment. As shown in Figure 9, the interior of the medical station 140 includes a chair 512 in which a patient can sit, an interface 932 in which the patient can interact (e.g., through one or more applications performed by the medical station), and a tray 938 in which one or more materials, stock, drugs, or other consumables or disposable items (e.g., swabs identified by the medical station as needed by the patient through one or more applications in which the patient interacts). The interface 932 may be embodied as a touch screen that displays images and also receives input from the patient. The tray 738 may be used in cooperation with, or as an alternative to, the drawer assemblies described above with reference to Figures 5 to 6B. The components and their layouts shown in Figure 9 are illustrative only, and various other modifications or additions may be made. For example, a body scanner may be provided in the medical station, and drawer assemblies may also be provided.

[0073] Figure 10 is a flowchart illustrating the operation of a medical station 140 according to one embodiment. A patient may use the interface 504 of the medical station 140 to provide user input for accessing the medical station 140. User input may include a patient ID and password. User input may be transmitted to a backend server 120 via the network 110 in order to determine the patient's access rights or privileges 1002 by comparing the user input with an entry in the patient information module 420. In some embodiments, the patient may carry a radio frequency (RF) tag or other ID card that can be read by the interface 504.

[0074] After the backend server 120 has authorized access to the medical station 140, the entrance door to the medical station 140 may be opened or unlocked to allow the patient to enter the medical station 140.

[0075] Next, applications are presented to the patient for selection.1008 Multiple applications that the patient can select may be displayed on the screen, and the patient's selection may be received via touch, verbal command, or gesture. Instead of displaying the selectable applications, a text-to-speech (TTS) system may provide language prompts to enable the patient to make an application selection.

[0076] Based on the selection of medical / health services, a corresponding application 310 may be launched 1010 by a computing device 220 in the medical station 140. After launch, the application may perform measurements on the patient using sensors 250 (e.g., a body scanner) within the medical station 140. Some of these measurements may be performed by default, while others may be performed only on certain patients under specific conditions. In conjunction with performing measurements, other preliminary actions may be performed at the medical station 140, such as obtaining verbal authorization for the services provided by the medical station 140 and receiving input from the patient regarding the requested medical / health services. In some embodiments, such preliminary actions may be performed by a default application that is launched before or in conjunction with the launch of the application selected by the patient.

[0077] Furthermore, in order to diagnose and / or treat a patient, or to collect and relay information to enable healthcare workers to diagnose and / or treat a patient, application 310 may ask a series of questions and perform one or more actions, which in some embodiments may include or may not include questions asked by a human healthcare worker or actions performed by a human healthcare worker. As part of such a series, one or more drawer assemblies 240 may be activated 1014 to enable the patient to access medical instruments 248 contained within the drawer assemblies 240. To facilitate the patient's use of the medical instruments 248, instructions may be provided by activating a training module 360 ​​in a computing device 220.

[0078] Furthermore, by using a specific plug-in component 816, a specific function or action 1016 may be performed at the medical station 140. Assuming that a patient or selected service has access to the plug-in component, the launched application may cause the computing device 220 to send signals to operate the plug-in component.

[0079] The steps and their sequence as illustrated in Figure 10 are merely illustrative. Additional steps may be performed by the medical station 140, and certain steps may be omitted. For example, if the medical station 140 is not equipped with any plug-in components, the process 1016 for using plug-in components may be omitted. Furthermore, the actions of activating the series of drawer assemblies 1014 and using plug-in components 1016 may be performed in parallel or in reverse order.

[0080] In some embodiments, a medical station 140 may be identified or selected for use by a patient (e.g., via a mobile device application associated with the medical station) based on one or more capabilities of the medical station, the patient's medical needs, characteristics (e.g., the patient's biological, demographic, geographical, or any other characteristics), the qualifications of the operators or personnel associated with the medical station, the availability / occupancy / use of the medical station, the inventory available within the medical station, the sensors or equipment available within the medical station, the applications installed in the medical station, whether the patient has completed any necessary actions in advance (e.g., filling out documents or disclosure forms in advance, fasting, taking medication in advance), or any other preferred criteria. For example, if a patient needs to have their blood pressure checked as part of a health screen, a medical station 140 with blood pressure measurement capabilities may be selected and recommended for that user. If the medical station 140 visited by the patient is unable to meet the patient's needs, an alternative medical station may be recommended to the patient based on the patient's needs.

[0081] The medical station 140 described herein enables personalized care for patients based on patient-related information available to the medical station. By leveraging the scale of the network of medical stations and automating various processes and functionalities, the cost of providing such care is generally reduced compared to conventional access to healthcare (e.g., visits to clinics). As described above, the manufacturing and assembly of such medical stations 140 may be streamlined, beneficially increasing the deployment speed, and lowering the barriers to creating a large-scale distributed network of deployed medical stations. Other functionalities of the medical station 140 that may not be described herein may include self-cleaning functionality, self-notification functionality (for notifying medical station personnel or operators when inventory is low or a particular function of the medical station is not working properly), real-time inventory tracking and management (e.g., automated inventory ordering when certain supplies are low), modular installation (e.g., multiple medical stations can be installed side-by-side to increase throughput capacity), platform-focused software deployment (e.g., applications can be built based on the capabilities of the medical stations and target all or a subset of the network of medical stations), and centralized regulatory compliance (e.g., regulatory requirements for each jurisdiction can be centrally managed and enforced).

[0082] Although the term “patient” is used herein, in practice, the medical station 140 may provide access to any number of health-focused or wellness-focused services or functionalities (such as physical fitness or meditation), in which case the users of the medical station may not be patients themselves, but rather consumers or participants in the capabilities of the medical station. Similarly, in practice, some versions of the medical station 140 may not provide any medical or wellness services or functionalities at all, and it should be noted that the features and functionalities described herein with respect to the medical station may be equally applicable to any station or system that provides users with access to one or more services or functionalities, such as consumer activities, entertainment services, or banking services.

[0083] A person skilled in the art will understand, by reading this disclosure, that further additional alternative designs of medical stations, medical station interoperability devices, and operating mechanisms may be used. Thus, although specific embodiments and applications have been illustrated and described, the present invention is not limited to the exact construction and components disclosed herein, and it will be understood that various modifications, changes, and variations will be made to the configuration, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope of this disclosure, as will be apparent to a person skilled in the art.

Claims

1. A method for operating a medical station, The system receives input associated with a person and determines the person's authority to access the medical station, In response to the determination that the person has the authority to access the medical station, the ability to selectively allow the person to enter the interior of the medical station, The medical station receives the selection of the first application to be activated from the person, In response to the activation of the selected application, grant the person access to the first medical device or first component of the medical station, Methods that include...

2. In response to the activation of the first application, receive a control signal, In response to receiving the aforementioned control signal, one or more actuators of the medical station are operated to allow the person access to the first medical device or the first component, The method according to claim 1, further comprising:

3. The method according to claim 2, wherein the drawer or tray is operated by one or more actuators in response to receiving the control signal.

4. The method according to claim 3, further comprising turning on a visual indicator associated with the activated drawer or tray in response to receiving the control signal.

5. The medical station stores multiple applications, In accordance with the person's authority to access a subset of applications, including the first application, the subset of applications accessible to the person is determined. Presenting a subset of the aforementioned applications to the person for selection, The method according to claim 1, further comprising:

6. To store a second medical device or second component that is different from the first medical device or first component of the medical station, Restricting access to the second medical device or the second component to the operation of a second application different from the first application, The method according to claim 5, further comprising:

7. The method according to claim 6, wherein the first application and the second application are associated with different healthcare providers.

8. The method according to claim 5, further comprising receiving the plurality of applications from a computing device located remotely from the medical station via a communication network.

9. Determining whether the received plurality of applications meet predetermined requirements related to the medical station, Installing one or more of the received applications that satisfy the aforementioned predetermined requirements into the medical station, The method according to claim 8, further comprising:

10. The method according to claim 9, wherein the predetermined requirement refers to the availability of the corresponding medical device or corresponding component of the medical station.

11. The method according to claim 1, wherein enabling the person to enter the medical station includes opening or unlocking a door to enter the medical station.

12. The method according to claim 1, further comprising performing measurements on the person by using the sensors of the medical station.

13. The first application presents the person with a series of questions, Performing a series of actions by the first application, including the use of the first medical device or the first component within the medical station, The method according to claim 1, further comprising:

14. Using the first medical device or the first component, information is collected about the person or the treatment performed on the person. The collected information is transmitted via a communication network to a computing device located away from the medical station for analysis and processing. The method according to claim 1, further comprising:

15. The method according to claim 14, further comprising updating the person's medical record in the computing device in accordance with the collected information.

16. It is a medical station, An interface device for receiving input associated with the authorization of a person to access the aforementioned medical station, A restricted entrance, configured to selectively allow the person to enter the interior of the medical station, A computing device, Receiving the input from the interface device, In response to determining that the person has the authority to access the medical station, granting access to the interior of the medical station allows the person to enter the restricted entrance, The medical station receives the selection of the first application to be activated from the person, In response to the activation of the selected application, grant the person access to the first medical device or first component of the medical station, A computing device configured to do so, A medical station equipped with these facilities.

17. The medical station according to claim 16, further comprising one or more actuators for granting access to the first medical device or the first component in response to receiving a control signal from the computing device.

18. The medical station according to claim 17, further comprising a drawer or tray operated by one or more actuators.

19. The medical station according to claim 18, wherein the drawer or tray is equipped with a visual indicator that is turned on in response to receiving the control signal from the computing device.

20. The computing device, The medical station stores multiple applications, In accordance with the person's authority to access a subset of applications, including the first application, the subset of applications accessible to the person is determined. Presenting a subset of the aforementioned applications to the person for selection, A medical station according to claim 16, configured to do the following.

21. The medical station according to claim 16, further comprising a second medical device or second component different from the first medical device or first component of the medical station, wherein access to the second medical device or second component is restricted to the operation of a second application different from the first application.

22. The medical station according to claim 16, further comprising a communication system configured to receive a plurality of applications from a computing device located away from the medical station, wherein the computing device is further configured to install at least a subset of the received applications.

23. The medical station according to claim 16, wherein the computing device is further configured to present a series of questions and to perform a series of actions by the first application, including the use of the first medical instrument or the first component within the medical station.

24. A non-temporary computer-readable storage medium for storing instructions, wherein when the instructions are executed by a processor, the processor is provided with The system receives input associated with a person and determines the person's authority to access the medical station, In response to the determination that the person has the authority to access the medical station, the ability to selectively allow the person to enter the interior of the medical station, The medical station receives the selection of the first application to be activated from the person, In response to the activation of the selected application, grant the person access to the medical equipment or components of the medical station, A non-temporary computer-readable storage medium that enables this process.

Images