Systems and methods for managing healthcare services and networks
The system integrates telemedicine services across healthcare provider networks, addressing inefficiencies in appointment scheduling and fee distribution, ensuring compliance with data privacy laws, and facilitating seamless healthcare service delivery.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- SEEYOUDOC CORP
- Filing Date
- 2024-04-26
- Publication Date
- 2026-04-27
Smart Images
Figure 2026513434000001_ABST
Abstract
Description
Technical Field
[0001] The present invention generally relates to healthcare information communication technology, and more particularly to a system for managing healthcare services and networks, as well as a method executed by a computer.
Background Art
[0002] Telemedicine has become increasingly well-known as an alternative to traditional in-person consultations. Generally, a telemedicine platform typically provides a means for patients to conveniently request healthcare professionals and receive remote consultations in real time via video conferencing.
[0003] One such platform is disclosed in U.S. Patent No. 11482326 ('326), which aims to provide a web-based application for conducting remote counseling sessions by various mobile devices. In the application according to '326, a client can access a website, log in, search a database of online experts, and select an appropriate expert for a counseling session. The selected healthcare provider can also refer a patient to another healthcare provider within the platform. Subsequently, a two-way audio-visual communication session is initiated between the patient's computing device and the healthcare provider's computing device. This referral process can automatically transfer the user's files, documents, history, and / or data to the referred expert and enable the referred expert to request user authentication to access the files.
[0004] Another related technology is presented in U.S. Patent Application Publication 2018 / 0096483 ('483), which similarly provides a means for patients to make appointments with healthcare practitioners (HCPs) via computer. In particular, the technology by '483 is directed toward enhancing the method of information presentation during referral-based appointments. This is achieved by the steps of creating patient health data for a patient, storing the patient health data on a server, accessing the patient health data by either the patient or the healthcare provider on a corresponding computer connected via the Internet, and presenting the accessed patient health data in a graphical form, with an icon-searchable portion and an editable portion.
[0005] However, the technologies described in '326' and '483' are limited to clinical tasks such as diagnosis, prescription issuance, and patient-healthcare provider interactions, and do not address more complex management issues regarding the types of medical practices performed by healthcare providers, particularly their affiliation with networks such as clinics, hospitals, and healthcare provider networks (HCPNs).
[0006] Healthcare professionals may be self-employed, work in a clinic with other healthcare professionals, work in a hospital, or a combination of these. For example, a healthcare professional may belong to multiple clinics, hospitals, or HCPNs. The technologies cited and existing systems in the market do not provide integrated healthcare services with telemedicine at the hospital level. Therefore, this broad range of healthcare practices needs to be considered in order to properly manage the availability of doctors or services that patients can choose from to avoid appointment problems (e.g., double bookings), and to provide a means for professional fees and other medical costs to be properly distributed among the necessary networks that depend on healthcare professionals' affiliations with various levels of organizations.
[0007] Furthermore, healthcare professionals and patients may have preferences regarding the method of consultation, whether it be in-person or online. Therefore, to manage healthcare services and networks more efficiently, it is also necessary to incorporate mechanisms for monitoring transactions regardless of the chosen consultation format.
[0008] On the other hand, HCPNs can be classified as public, private, or a combination of public and private healthcare providers. Public HCPNs can be further classified at the province level and include provincial, municipal, and town health centers (CHOs), hospitals, health centers, health stations, and other health facilities and services under local government entities (LGUs). They can also be considered at the town level, in which case they include CHOs, hospitals, health centers, barangay health units (BHUs), and other town-level health facilities and services.
[0009] HCPN-level information provides data that can be used in epidemiology, biostatistics, and other related fields that promote public health. Population health monitoring plays a crucial role in public health, particularly in quantifying disease severity and identifying patterns of change and associated risk factors (Tulchinsky and Varavikova, 2014), enabling the identification and diagnosis of health problems and risks in communities.
[0010] Data for mass health monitoring can be extracted from tools that appropriately incorporate HCPN-level information without compromising user privacy.
[0011] As disclosed in U.S. Patent No. 1,0839,964 ('964), one technology provides a means of monitoring healthcare information through a cloud-based clinical information system, where credentials and / or rules for accessing and sharing the information (e.g., viewing, receiving, downloading, uploading, transmitting, etc.) are managed according to a hierarchical organizational scheme. Entity types in the hierarchical organizational scheme according to '964 may include communities (e.g., multiple research collaborators), integrated delivery networks (IDNs) (e.g., multiple facilities and / or providers with business and / or legal relationships), sites (e.g., hospitals, diagnostic imaging centers, etc.), groups (e.g., multiple clinicians), clinicians, and patients.
[0012] However, the technology described by '964 is not particularly relevant to the methods of conducting and managing virtual consultations or virtual facilities across different levels of networks. For example, an HCPN, like in the case of a LGU, needs a system that can manage integrated telemedicine services and issue referrals within the town or barangay level, and a CHO needs a system to monitor the performance of healthcare workers.
[0013] Furthermore, there is a need to facilitate the transfer of funds from insurance companies to HCPNs certified by those companies, and to implement medical consultations that are seamlessly integrated into a system that takes into account the various medical practices of healthcare providers.
[0014] Therefore, healthcare provider networks need to build patient-centered integrated systems to deliver telemedicine services online and in the field, track service performance, provide regulatory reports, manage the seamless integration of healthcare services within networks of physicians, clinics, and medical facilities, facilitate funding transfers from insurance companies to accredited HCPNs, and monitor related impacts. [Overview of the Initiative]
[0015] Therefore, the present invention aims to build a complete universal healthcare supply chain from healthcare provider networks (HCPNs), medical facilities, clinics, physicians, and patients, while complying with the HL7 (Health Level 7) FHIR (Fast Healthcare Interoperability Resource) standards and HIPAA (Health Insurance Portability and Accountability Act) requirements, by providing an integrated online platform on which HCPNs can manage the network, publish healthcare services, provide seamless healthcare services within the network via a referral system, and monitor the performance of all service providers within the network.
[0016] In one aspect of the present invention, a system is provided for managing multiple healthcare services and networks, comprising multiple devices configured to receive input from multiple user groups, and an application cluster deployed on a private network configured to execute multiple computer implementation instructions for interacting with the multiple user groups through multiple user interfaces, wherein the multiple user groups include multiple patients, physicians, clinic administrators, hospital administrators, and HCPN administrators, each with a different degree of relevance to one another.
[0017] Another aspect of the present invention provides a method for managing multiple healthcare services and networks, which is performed by a computer, by obtaining and processing appointment requests from patients, transmitting such appointment requests to physicians, obtaining and processing responses from physicians, establishing virtual consultations between patients and physicians, obtaining further administrative actions, and distributing fees according to predetermined rules between physicians and any of the relevant user groups to which the physicians belong (e.g., clinic administrators, hospital administrators, HCPN administrators).
[0018] In yet another aspect of the present invention, a computer method is provided which includes means for managing both online and in-person consultations, and both scheduled and walk-in appointments, for different network levels. [Brief explanation of the drawing]
[0019] [Figure 1] Figure 1 shows the system configuration of the present invention. [Figure 2] Figure 2 shows one embodiment of the interaction between the system of the present invention and a user group. [Figure 3] Figure 3 shows an embodiment of possible user associations between preferred user groups. [Figure 4] Figure 4 shows another embodiment of the interaction between the system of the present invention and a user group. [Figure 5] Figure 5 shows the interaction between a patient user group and a healthcare professional user group using the present invention. [Figure 6] Figure 6 shows the user flow on the day of the reservation. [Modes for carrying out the invention]
[0020] The present invention relates to a system and method for managing multiple healthcare services and networks, and can be implemented in the form of a web-based application or a mobile application.
[0021] As shown in Figure 1, one embodiment of the present invention deployed on a private network 300 may be accessed by multiple user groups 100 using a device that includes a module for connecting to an external network via the internet. The external network is publicly accessible and uses a Domain Name System (DNS) 200 to identify IP addresses requested by the multiple user groups 100.
[0022] The DNS 200 further includes a plurality of subdomains. In a preferred embodiment, the first user group 101 uses the first subdomain 201, the second user group 102 uses the second subdomain 202, the third user group 103 uses the third subdomain 203, the fourth user group 104 uses the fourth subdomain 204, and the fifth user group 105 uses the fifth subdomain 205 to request access to the private cloud.
[0023] Furthermore, the sixth user group 1001 may include a plurality of third - party applications, or a plurality of users associated with third - party applications, configured to connect to the API 2001 of the present invention for access requests. And the communication protocol 211 is configured to send the access request to the private network 300. The communication protocol 211 may be in the form of Hypertext Transfer Protocol Secure (HTTPS) or WebSocket Secure (WSS).
[0024] The API (Application Programming Interface) object 301, which is a reverse proxy Web server, communicates via the communication protocol 211 and receives access requests from a plurality of user groups 100. Then, the API object 301 sends the request to a destination node within the private network 300 according to a predetermined rule.
[0025] The system according to the present invention deployed in the private network 300 includes an application cluster 302, and this application cluster is configured to utilize a plurality of shared libraries 303 as needed based on its instruction set. The application cluster 302 is stored in a non-transitory computer-readable medium and includes an instruction set executable by at least one processor. In particular, the application cluster 302 includes a first service 3021 configured to execute a first set 30211, 30212, 30213,..., 3021n of Docker containers for managing online processes, and a second service 3022 configured to execute a second set 30221, 30222, 30223,..., 3022n of Docker containers for managing background processes.
[0026] The application cluster 302 communicates with a plurality of shared libraries 303 via a plurality of communication protocols. In particular, the application cluster communicates with a first service 3031 via a first communication protocol, communicates with a second service 3032 via a second communication protocol 322, and communicates with a third service 3033 via a third communication protocol 323. Preferably, the communication protocols 321, 322, 323 are all in the form of TCP (Transmission Control Protocol).
[0027] The plurality of shared libraries 303 are accessible to the application cluster 302. The first service 3031 is a database pool including a first shared library 303111, a second shared library 303121, and a third shared library 303131.
[0028] The first shared library 303111 is a dedicated library for processing a plurality of authentication and authorization functions, is configured to record a plurality of information using a first master database 303112, and is further configured to connect to a first backup database 303113.
[0029] The second shared library 303121 is a dedicated library for handling multiple core business functions, configured to record multiple pieces of information using the second master database 303122, and further configured to connect to the second backup database 303123.
[0030] The third shared library 303131 is dedicated to handling multiple additional functions, is configured to record multiple pieces of information using a third master database 303132, and is further configured to connect to a third backup database 303133. In a preferred embodiment, the multiple additional functions are functionalities added to comply with the requirements of the HL7 (Health Level Seven) FHIR (Fast Healthcare Interoperability Resource) standard.
[0031] The second service 3032 includes at least one shared library containing a dedicated search module 303211 for handling search functions, the search module 303211 being configured to record multiple pieces of information using the search master database 303212, and further configured to connect to the search backup database 303213.
[0032] The third service 3033 includes at least one shared library, which includes a dedicated queuing module 303311 for handling virtual waiting rooms, is configured to record multiple pieces of information using a queuing master database 303312, and is further configured to connect to a queuing backup database 303313.
[0033] In a preferred embodiment, the application cluster 302 is further configured to communicate with a fourth service for storing static files and a fifth service for generating and recording real-time communications, such as video calls (not shown).
[0034] Users in multiple user groups (100 users) can create individual accounts and access their accounts using multiple devices. These multiple devices are configured to receive input from multiple user groups and connect to external networks via the internet.
[0035] In the preferred embodiment shown in Figure 2, there are five user groups, each containing at least one user who can access the system deployed on the private network 300. At least one user in the first user group 101 interacts with the system and other users via the first user interface 2011, at least one user in the second user group 102 interacts via the second user interface 2021, at least one user in the third user group 103 interacts via the third user interface 2031, at least one user in the fourth user group 104 interacts via the fourth user interface 2041, and at least one user in the fifth user group 105 interacts via the fifth user interface 2051.
[0036] In this preferred embodiment, the first user group 101 includes multiple patients, the second user group 102 includes multiple healthcare workers or physicians, the third user group 103 includes multiple clinic administrators, the fourth user group 104 includes multiple hospital administrators, and the fifth user group 105 includes multiple HCPN administrators.
[0037] In this book, "healthcare worker" and "physician" are used as synonymous terms. The term "clinic administrator" may refer to a user who assists a physician with treatment planning or manages patient triage. On the other hand, the term "hospital administrator" may refer to a representative of a hospital or other medical facility. Finally, the term "HCPN administrator" may refer to a representative of an agency under the Department of Health, a LGU, a private medical group, or a health maintenance organization (HMO).
[0038] A user in one user group may be associated with one or more other users in another user group. As shown in the embodiment of Figure 3, patients 101a, 101b, 101c, 101d, and 101e can directly or indirectly (i.e., by selecting relevant healthcare services) select any of the healthcare providers 102a, 102b, 102c, 102d, and 102e of the second user group 102.
[0039] If at least one user in the second user group 102 belongs to at least one clinic, that user may be associated with at least one user in the third user group 103. For example, healthcare worker 102a may be associated with clinic administrator 103a, healthcare worker 102b may be associated with clinic administrator 103b, and healthcare workers 102c and 102d may be associated with clinic administrator 103c.
[0040] Alternatively, one of the healthcare professionals in the second user group 102 may be associated with multiple users in the third user group 103.
[0041] With this invention, healthcare professionals in the second user group 102 and clinic administrators in the third user group 103 can provide and implement healthcare services online and on-site.
[0042] The application cluster 302 is also configured to provide users of the third user group 103 (i.e., clinic administrators) with a means to manage the virtual clinic by adding or removing relevant users from the second user group (i.e., relevant physicians). There are two types of virtual clinics: the first is a general clinic where the clinic administrator 103 assists physician 102 in running the clinic, and the second is a triage clinic where the clinic administrator 102 collects preliminary information and assesses patient needs through chat.
[0043] If at least one user in the third user group 103 belongs to a hospital, that user is associated with at least one user in the fourth user group 104. For example, clinic administrators 103b and 103c are associated with hospital administrator 104a.
[0044] The application cluster 302 is further configured to provide users of the fourth user group (i.e., hospital administrators) 104 with means to add or remove related users from the third user group (i.e., clinic administrators) 103 and related users from the second user group (i.e., physicians) 102.
[0045] A private hospital can take advantage of the benefits of the present invention by assigning one user to the fourth user group 104 to function as a hospital administrator. The hospital administrator can set up virtual clinics for each medical department via the fourth user interface and assign affiliated physicians to provide healthcare services both online and on-site. Furthermore, the hospital administrator can further set up accounts for each clinic or medical department by assigning a user from the third user group 103 to function as a clinic administrator via the third user interface 2031.
[0046] If at least one user in the third user group 103 belongs to HCPN, that user may be associated with at least one user in the fifth user group 105. For example, hospital administrator 103a may be associated with HCPN administrator 105a.
[0047] If at least one user in the fourth user group 104 belongs to HCPN, that user may be associated with at least one user in the fifth user group 105. For example, hospital administrators 104a and 104b may be associated with HCPN administrator 105a.
[0048] For example, LGU can assign users from the fifth user group 105 to act as HCPN administrators, and assign the administrator of that BHU to act as a partner user in the third user group 103, allowing them to act as clinic administrators.
[0049] In this embodiment, the application cluster 302 is further configured to provide users of the fifth user group (i.e., HCPN administrators) 105 with means to manage multiple users and multiple pieces of information from the fourth user group (i.e., hospital administrators) 104 and the third user group (i.e., clinic administrators) 103 in the form of service orders.
[0050] The application cluster 302 is further configured to display an analysis dashboard in the second user interface 2021 using any information associated with at least one user in the second user group 102, to display an analysis dashboard in the third user interface 2031 using any information associated with at least one user in the third user group 103, to display an analysis dashboard in the fourth user interface 2041 using any information associated with at least one user in the fourth user group 104, and to display an analysis dashboard in the fifth user interface 2051 using any information associated with at least one user in the fifth user group 105.
[0051] The application cluster 302 is configured to monitor the behavior of multiple user groups 100, extract data from said behavior according to a predetermined set of instructions, and present that data in the form of visual elements such as charts, graphs, maps, and other data visualization tools. The analytics dashboard can be useful to users in that it monitors bookings, patient demographic data, revenue, and patient feedback.
[0052] For example, a fifth user group 105, such as an LGU administrator, can use the analytics dashboard to monitor the performance of physicians in the CHO and BHU.
[0053] The analytics dashboard may reside in a separate subdomain and may function as an add-on subscription for a second user group 102 (i.e., physicians), a third user group 103 (i.e., clinic administrators), a fourth user group 104 (hospital administrators), and a fifth user group 105 (i.e., HCPN administrators).
[0054] Other possible user associations, not exceeding the scope of the present invention, may be included in the actual implementation of the present invention.
[0055] In another preferred embodiment, as shown in Figure 4, the user groups 100 further include a sixth user group 106 communicating via a sixth user interface 2061, a seventh user group 107 communicating via a seventh user interface 2071, and an eighth user group 108 communicating via an eighth user interface 2081. In this preferred embodiment, the sixth user group 106 includes multiple medical association administrators, the seventh user group 107 includes multiple medical partners, and the eighth user group 108 includes multiple virtual facility administrators.
[0056] Furthermore, if at least one user in the second user group 102 belongs to a medical association, that user may be associated with at least one user in the sixth user group 106. For example, application cluster 302 provides at least one user in the sixth user group (i.e., a medical association user) with a means to track the physician's membership, collect membership fees, create events, and issue Continuing Professional Development (CPI) credits via a unique Quick Response Code (QR Code®).
[0057] If at least one user in the fourth user group 104 has a medical partner that is part of the seventh user group 107, then the user in the fourth user group 104 may be associated with the user in the seventh user group 107. For example, when a user in the fourth user group 104 (e.g., a hospital administrator) is queried, the application cluster 302 provides at least one user in the seventh user group 107 (e.g., a medical partner) to obtain a fee.
[0058] At least one user from the eighth user group 108 can access the medical analytics of the virtual facility using the eighth user interface 2081. The application cluster 302 may be further configured to monitor the behavior of multiple user groups 100, extract data from the behavior according to a predetermined set of instructions, and present the data to at least one user from the eighth user group 108 to provide real-time reports, patient and physician demographic data, booking heatmaps, revenue reports, ratings and complaint information, etc.
[0059] All user groups must follow an onboarding process before they can use the present invention. In particular, physicians and healthcare providers must first register their occupation and office services, preferably using the first subdomain 201.
[0060] Figure 5 shows a preferred embodiment of the process flow for an approved appointment request and interaction between at least one user 1021 from the patient user group and at least one user 1021 from the healthcare professional or physician user group. Once a patient user 1011 creates an account, they can set up, view, and update multiple subprofiles (e.g., a profile for family members) registered under the account. Patient user 1011 can also upload or delete medical records associated with any of the multiple profiles.
[0061] Patient user 1011 can also view, cancel, or reschedule any appointments associated with their user account. To create an appointment, the patient may view a displayed list of available doctors, clinics, and / or services, and preferably search for a desired doctor, clinic, or service. The application cluster then uses the search module 303211 to retrieve the query and display information related to the query. Patient user 1011 then creates a new appointment request 20, which is retrieved for approval and sent to the relevant doctor 1021. The relevant doctor 1021 receives the appointment request and enters a response.
[0062] The relevant physician 1021 can change, cancel, or approve the appointment. In any of these cases, the patient user 1011 receives a notification. If the relevant physician 1021 reschedules the appointment by setting a new schedule proposal, the application cluster 302 provides the patient user 1011 with a means to accept or reject the new schedule proposal. In another embodiment, the physician can query other physician users for appointments.
[0063] The application cluster 302 receives a response once the relevant physician approves, notifies the patient of the approved appointment request 22, and generates a series of payment instructions. The patient user 1011 then settles the payment for the approved appointment request. In one embodiment, if another patient user approves and pays for the same appointment request, the patient user 1011 is notified that the appointment request failed, and the patient user 1011 may then request a new schedule. Once the payment is successful, the application cluster 302 notifies the relevant physician 1021 of the paid appointment request 24. The application cluster 302 processes multiple appointment details based on the paid appointment request 24 and establishes real-time communication 26 (e.g., video conferencing) between the patient user 1011 and the relevant physician 1021. Once completed, the application cluster 302 marks the appointment as complete.
[0064] Alternatively, the patient may choose a walk-in remote consultation session. Figure 6 shows one embodiment of the user flow on an appointment day. Patient user 1001 enters the waiting room 30. If patient user 1001 has a paid appointment request 24, they are placed in a queue under the priority list 32. However, if the prior appointment request has not been paid, patient user 1001 can settle the consultation fee and enter the walk-in queue 34. Patient user 1001 may choose to abandon the queue and receive a refund 36 for their payment.
[0065] The application cluster 302 may also be configured to provide means for playing videos or displaying any form of multimedia on the user's screen while they are in the waiting room 30.
[0066] The virtual consultation begins when the relevant physician 1021 accepts the next patient in the queue. In a preferred embodiment, the application cluster is further configured to provide a real-time communication platform, such as chat, between the relevant physician 1021 and the patient and / or other visitors in the waiting room 30.
[0067] Real-time communication is preferably in the form of video conferencing or chat.
[0068] Patient user 1011 can add medical files, record sessions for personal use, use add-on services, or end appointments early at any time during a consultation.
[0069] On the other hand, the associated physician 1021 can also record the session, create a medical case for an appointment, use medical templates for medical documents, view the medical files of the inpatient user 1011, refer patient user 1011 to another appointment, and end the virtual consultation.
[0070] The patient user 1011 and the associated physician 1021 may perform other actions related to the functions of video conferencing and chat platforms known in the art, such as turning audio and video on and off, which are not described above.
[0071] In a preferred embodiment, once the consultation is complete, the application cluster 302 may be configured to perform tasks such as obtaining customer feedback from the patient user 1011, paying for any additional services used, receiving relevant notifications related to actions initiated by the relevant physician 1021, and providing a platform for tasks such as sending medical documents or referring the patient to another physician or specialist.
[0072] In another preferred embodiment, the application cluster 302 may further be configured to provide a platform for obtaining feedback from the relevant physician 1021, sending official medical records such as electronic prescriptions and clinical test requests to the patient user 1011, and reviewing and adding / modifying the patient user 1101's medical notes or medical cases.
[0073] In another preferred embodiment, the application cluster 302 is further configured to provide the associated physician 1021 with means to manually mark the appointment as complete when an on-site consultation takes place instead of a virtual consultation.
[0074] In a preferred embodiment, the application cluster 302 is further configured to generate an email summary of the relevant physician's (1021) consultation history, including completed appointments, referrals, and revenue, and to display it via a second user interface 2021 for the relevant physician to view.
[0075] In yet another preferred embodiment, the application cluster 302 is further configured to collect fees from patient users 1011 and send them to the relevant physician 1021. In yet another embodiment, the application cluster 302 is further configured to allow the relevant physician 1021 to waive or apply discounts on fees according to predetermined rules.
[0076] If the relevant physician is affiliated with the relevant clinic administrator 1031, the application cluster is further configured to distribute fees between the relevant physician 1021 and the relevant clinic administrator 1031 according to predetermined rules.
[0077] The application cluster 302 is further configured to retrieve multiple user information and multiple pieces of information related to actions performed by the associated clinic administrator 1031 via a third user interface 2031. In a preferred embodiment, these actions may refer to multiple service orders such as adding or removing physicians from the list of physicians associated with the clinic administrator account, viewing, reviewing, and approving appointments on behalf of the associated physician 1021, receiving appointment referrals and assigning them to any physician belonging to the clinic, collecting fees distributed according to predetermined rules, viewing total revenue, adjusting clinic settings, and tracking performance via a dashboard module. Furthermore, clinic administrators in the third user group 103 can act as intermediaries between physicians and hospitals and receive service orders from the associated hospital administrator 1041.
[0078] In a preferred embodiment, as shown in Figure 7, the application cluster is further configured to provide a platform for establishing real-time communication, such as chat, between the clinic administrator 1031 and the patient in the waiting room 30.
[0079] In a preferred embodiment, if the relevant physician is affiliated with a further relevant hospital administrator 1041, the application cluster 302 is further configured to distribute fees among the relevant physician 1021, the relevant clinic administrator 1031, and the relevant hospital administrator 1041 according to predetermined rules.
[0080] Upon activation, at least one user within the fourth user group 104 can begin accessing their user account via the fourth subdomain 204. The account of at least one user within the fourth user group 104 may contain multiple subprofiles for facility users. The application cluster 302 is configured to retrieve multiple user information and other information related to actions performed by at least one user within the fourth user group 104 via the fourth user interface 2041. These actions may relate to managing multiple facility users, multiple associated clinics, and multiple service requests for referrals. In particular, at least one user within the fourth user group can create service orders to be issued to associated users within the third user group 103.
[0081] The fourth user interface 2041 may further include a front desk system that allows patients from the first user group 101 to contact a front desk receptionist, which is one of the subprofiles in the account of at least one user from the fourth user group 104. The front desk receptionist can refer the patient to at least one user from the second user group 102 or the third user group 103 using an intuitive referral system.
[0082] Finally, at least one user within the fifth user group 105 can initiate access to their user account via the fifth subdomain 205. The application cluster 302 is configured to retrieve multiple user information and multiple pieces of information related to actions taken by at least one user within the fifth user group 105 via the fourth user interface 2051. These actions may include multiple service orders in the form of announcements (e.g., important announcements and written memoranda) or time-sensitive action items (e.g., physician referrals, removal or addition of affiliated users).
[0083] The application cluster 302 is configured to identify which users in the second user group 102, third user group 103, fourth user group 104, and fifth user group 105 are associated with the transaction of at least one user in the first user group 101 during the transaction of that user. The application cluster 302 is then configured to determine which of the multiple user information and multiple pieces of information related to the actions taken by the users in the first user group 101 are sent to or accessible by the relevant users in the second user group 102 (i.e., the first set of information), the relevant users in the third user group 103 (i.e., the second set of information), the relevant users in the fourth user group 104 (i.e., the third set of information), and the relevant users in the fifth user group 105 (i.e., the fourth set of information). This is done to comply with standards for the exchange, integration, sharing, and retrieval of electronic health information in accordance with HL7 (Health Level Seven), FHIR (Fast Healthcare Interoperability Resource), and HIPAA (Health Insurance Portability and Accountability Act).
[0084] The present invention incorporates a hierarchical level of access from a second user group 102 to a fifth user group 105 by using service orders. The application cluster 302 is configured to receive service orders from user groups with higher levels, transmit them to the intended users or users within the network, and provide the recipient with a means to fulfill the service order.
[0085] For example, a user in the fifth user group 105 can issue a service order to a first set of associated users, which includes a user in the fourth user group 104, the third user group 103, or the second user group 102. Thus, users in the fourth user group 104, the third user group 103, and the second user group 102 can receive and respond to service orders from associated users in the fifth user group 105. A user in the fourth user group 104 can then issue a service order to a second set of associated users, which includes a user in the third user group 103 and a user in the second user group 102. Users in the third user group 103 and the second user group 102 can then receive and respond to service orders from associated users in the fourth user group. Finally, a user in the third user group can issue a service order to a third set of associated users, which includes a user in the second user group 102.
[0086] Thus, by using the present invention, healthcare management can be seamlessly integrated with clinical operations. Ultimately, the present invention enables healthcare networks to maintain a health information system incorporating electronic medical records, electronic prescription logs, etc., while complying with data privacy laws and universal health insurance laws, and ensuring patient privacy and confidentiality.
[0087] Preferred embodiments of the present invention are described in the detailed description above. Those skilled in the art will understand that modifications and / or variations of the embodiments shown and described herein can be conceived. Such modifications or variations that fall within the scope of this specification are also intended to be included within the scope of this specification. Unless otherwise noted, it is the inventors' intention that the terms in this specification and the claims are to have the usual idiomatic meaning to those ordinary skilled in the art in which they apply. The above description of preferred embodiments and best modes of the present invention, known to the applicant at the time of filing of this application, is presented and intended for illustrative and explanatory purposes. It is not intended to be exhaustive or to limit the invention to the exact forms disclosed, and many modifications and variations are possible in light of the above teachings.
Claims
1. A system for managing multiple healthcare services and networks, Multiple devices configured to receive input from multiple user groups, wherein each of the multiple devices includes a module for connecting to an external network via the Internet. An application cluster located on a private network, comprising an application cluster containing multiple instructions that are stored on a non-transient computer-readable medium and are executable by at least one processor, An Application Programming Interface (API) object configured to receive input from an external network and send requests to a destination node within a private network, A first user interface for receiving reservation requests from at least one user within a first user group, A second user interface for receiving responses to a reservation request from at least one user in a second user group associated with the reservation request, Means for facilitating real-time communication between at least one user in a first user group and at least one related user in a second user group, in accordance with prescribed rules, Includes, The aforementioned application cluster is Communicate with at least one user of the third user group via a third user interface. Communicate with at least one user within the fourth user group via the fourth user interface. Communicating with at least one user within a fifth user group via a fifth user interface. It is configured in such a way, The aforementioned application cluster further, The system includes means for at least one user in the fifth user group to issue multiple service orders to a first set of affiliated users, which includes multiple users from the fourth user group, multiple users from the third user group, and / or multiple users from the second user group. The system includes means for at least one user in the fourth user group to issue multiple service orders to a second set of affiliated users, which includes multiple users from the third user group and / or multiple users from the second user group. The system includes means for at least one user within the third user group to issue multiple service orders to a third group of affiliated users, which includes multiple users from the second user group. The first group of partner users, the second group of partner users, and the third group of partner users are provided with means for responding to received service orders. system.
2. The system according to claim 1, wherein the application cluster is further configured to collect charges from at least one user in the first user group upon completion of the real-time communication and to distribute the collected charges to at least one relevant user in the second user group.
3. The system according to claim 2, wherein if at least one user in the second user group also belongs to at least one related user in the third user group, at least one related user in the fourth user group, and / or at least one related user in the fifth user group, the application cluster is further configured to distribute the collected fees among the at least one related user in the second user group, at least one related user in the third user group, at least one related user in the fourth user group, and at least one related user in the fifth user group, according to predetermined rules.
4. The system according to any one of claims 1 to 3, wherein the application cluster is further configured to display an analytics dashboard in the second user interface using any information associated with at least one user in the second user group; to display an analytics dashboard in the third user interface using any information associated with at least one user in the third user group and the third pair of partner users; to display an analytics dashboard in the fourth user interface using any information associated with at least one user in the fourth user group and the second pair of partner users; and to display an analytics dashboard in the fifth user interface using any information associated with at least one user in the fifth user group and the first pair of partner users.
5. The system according to any one of claims 1 to 4, characterized in that the application cluster is configured to communicate with the first user group, the second user group, the third user group, the fourth user group, and the fifth user group via a web-based application.
6. The system according to claim 1, wherein the application cluster is configured to communicate with the first user group and the second user group via a mobile application.
7. The system further includes a queuing module, the queuing module is: A virtual waiting room is displayed via a first user interface, a second user interface, and / or a third user interface. Allow at least one user within the first user group to enter the virtual waiting room, Determine whether at least one user in the first user group has a paid reservation request. If at least one of the users has a paid reservation request, add the at least one user in the first user group to the priority list. For at least one user of the first user group, if the at least one user does not have a paid reservation request, a means for settling the payment is provided, and at the time of payment, the at least one user is added to the queue without a reservation. According to the established rules, based on the priority list and the no-reservation queue, the first person in the queue is identified. The first person in the queue is to participate in a virtual consultation with a related user within the second user group. The system according to claim 1, characterized in that it is configured as follows.
8. The system according to claim 7, wherein the application cluster is further configured to provide a real-time communication platform between at least one user in the second user group and at least one user in the first user group while in a queue.
9. The system according to claim 8, wherein the application cluster is further configured to provide a real-time communication platform between at least one user in the third user group and at least one user in the first user group while in a queue.
10. The system according to claim 1, characterized in that the first user group includes multiple patients, the second user group includes multiple healthcare professionals, the third user group includes multiple clinic administrators, the fourth user group includes multiple hospital administrators, and the fifth user group includes multiple healthcare networks.
11. The system according to claim 1, characterized in that the first user interface is accessible via a first subdomain, the second user interface via a second subdomain, the third user interface via a third subdomain, the fourth user interface via a fourth subdomain, and the fifth user interface via a fifth subdomain.
12. The system according to claim 1, characterized in that the means for facilitating real-time communication is in the form of a video conference.
13. The system according to claim 10, further comprising means for at least one relevant user within the second user group to manually mark an appointment as complete if a medical consultation is conducted instead of the video conference.
14. The system according to claim 1, wherein the application cluster is further configured to provide means for at least one relevant user in the second user group to send a plurality of medical documents to at least one user in the first user group.
15. The system according to claim 14, characterized in that the plurality of medical documents include electronic prescriptions, clinical test requests, and medical notes.
16. The system according to claim 1, characterized in that the multiple service orders issued to the first group of affiliated users include the issuance of multiple announcements or written memoranda and the assignment of multiple action items.
17. The system according to claim 16, characterized in that the aforementioned multiple action items are time-constrained action items, including referring a doctor and deleting or adding a partner user.
18. The system according to claim 1, characterized in that the multiple service orders issued to the second set of affiliated users include actions for managing the second set of affiliated users and multiple service orders for referrals.
19. The system according to claim 1, further comprising a front system that is accessible to users of the fourth user group via the fourth user interface and accessible to users of the first user group via the first user interface.
20. The system according to claim 1, wherein the multiple service orders issued to the third set of affiliated users include actions for managing the affiliated users, actions for managing multiple reservation requests, and actions for receiving and assigning reservation referrals.
21. The system according to claim 1, wherein the application cluster is configured to allow API connections to at least one third-party application.
22. The system according to claim 1, wherein the application cluster is further configured to communicate with at least one user in a sixth user group via a sixth user interface.
23. The system according to claim 22, characterized in that at least one user in the sixth user group is linked to at least one user in the second user group, the sixth user group includes multiple medical associations, and the second user group includes multiple healthcare professionals.
24. The system according to claim 1, wherein the application cluster is further configured to communicate with at least one user in a seventh user group via a seventh user interface.
25. The system according to claim 24, characterized in that at least one user in the seventh user group is linked to at least one user in the fourth user group, the seventh user group includes a plurality of medical partners, and the fourth user group includes a plurality of hospital administrators.
26. The system according to claim 1, wherein the application cluster is further configured to communicate with at least one user in an eighth user group via an eighth user interface.
27. The system according to claim 26, wherein the application cluster is further configured to monitor the activity of a plurality of pieces of information linked to the eighth user group, to extract data from the activity according to a predetermined set of instructions, and to visually present the data to at least one user of the eighth user group.
28. The system according to claim 27, characterized in that the data is presented in the form of real-time reports, patient and physician demographic data, heatmaps, revenue reports, and rating information.
29. The system according to claim 1, wherein the application cluster communicates with at least one user in a sixth user group via a sixth user interface, and is further configured to provide means for at least one user in the sixth user group to interact with at least one user in the second user group, wherein the at least one user in the sixth user group is a medical association administrator, and the at least one user in the second user group is a healthcare professional.
30. The system according to claim 1, wherein the application cluster communicates with at least one user of a seventh user group via a sixth user interface, and is further configured to provide means for at least one user of the seventh user group to interact with at least one user of the fourth user group, wherein the at least one user of the seventh user group is a medical partner, and the at least one user of the fourth user group is a hospital administrator.
31. The system according to claim 1, further characterized in that the application cluster communicates with at least one user in an eighth user group via an eighth user interface, and provides means for at least one user in the eighth user group to generate an analysis from a plurality of pieces of information related to the at least one user in the eighth user group.
32. A method performed by a computer for managing multiple healthcare services and networks, a. The step of displaying multiple pieces of information to a first user group via a first user interface, b. The step of obtaining multiple reservation request information and multiple user information from at least one user within the first user group, c. The step of sending multiple reservation request information to the relevant users within the second user group, d. A step of obtaining a response to the reservation request from the relevant user within the second user group, e. A step of facilitating real-time communication between at least one user in the first user group and a related user in the second user group, f. The steps of identifying a first set of information, a second set of information, a third set of information, and a fourth set of information from multiple user information using a predetermined rule, g. The step of sending the first set of information to relevant users in the second user group, h. A step of determining whether a relevant user in the second user group is affiliated with at least one user in the third user group and / or at least one user in the fourth user group and / or at least one user in the fifth user group, i. The step of transmitting the second set of information to at least one related user within a third user group via a third user interface, j. The step of transmitting the third information set to at least one relevant user within the fourth user group via a fourth user interface, k. The step of transmitting the fourth information set to at least one relevant user within the fifth user group via a fifth user interface, A method that includes this.
33. The method according to 32, further comprising the steps of obtaining a plurality of service orders from at least one user in the fifth user group via the fifth user interface, and transmitting the service orders to a first set of affiliated users, including a plurality of users from the fourth user group, a plurality of users from the third user group, and / or a plurality of users from the second user group.
34. The method according to 32 or 33, further comprising the steps of obtaining a plurality of service orders from at least one user in the fourth user group via the fourth user interface, and transmitting the service orders to a second set of affiliated users, which include a plurality of users from the third user group and / or a plurality of users from the second user group.
35. The method according to any one of claims 32 to 34, further comprising the steps of obtaining a plurality of service orders from at least one user in the third user group via the third user interface, and transmitting the service orders to a third set of affiliated users, including a plurality of users from the second user group.
36. The method according to 32, further comprising the step of collecting charges from at least one user in the first user group and distributing the collected charges to at least one relevant user in the second user group upon completion of the real-time communication.
37. The method according to 36, further comprising the step of distributing the collected fees among the at least one related user in the second user group, the at least one related user in the third user group, the at least one related user in the fourth user group, and / or the at least one related user in the fifth user group, in accordance with predetermined rules, if at least one user in the second user group is further affiliated with at least one related user in the third user group, the at least one related user in the fourth user group, and / or the at least one related user in the fifth user group.
38. The further step of displaying an analytics dashboard in the second user interface using any information associated with at least one user in the second user group; in the third user interface using any information associated with at least one user in the third user group and the third associated user set; in the fourth user interface using any information associated with at least one user in the fourth user group and the second pair of affiliated users; and in the fifth user interface using any information associated with at least one user in the fifth user group and the first pair of affiliated users. The method according to any one of claims 32 to 35.
39. a. A step of allowing at least one user within a first user group to enter a virtual waiting room, wherein the virtual waiting room is accessible via a first user interface, a second user interface, and / or a third user interface. b. A step of determining whether at least one user in the first user group has a paid reservation request, c. If at least one user has a paid reservation request, the step of adding at least one user in the first user group to the priority list, d. Step (d), if there are no paid reservation requests, the step of providing a means for the at least one user to settle payment for a reservation request, e. The step of adding at least one user from step (d) to the unreserved queue, f. The step of identifying the first person in the queue based on the priority list and the unreserved queue, according to the prescribed rules, g. The step of having the first person in the queue participate in a virtual consultation with relevant users in the second user group, The method of claim 32, further including the method described in claim 32.
40. The method according to claim 39, further comprising the step of providing a real-time communication platform between at least one user in the second user group and at least one user in the first user group while they are in the queue.
41. The method according to claim 39, further comprising the step of providing a real-time communication platform between at least one user in the third user group and at least one user in the first user group while they are in the queue.