System and method for relaying various saas-based medical services by using service URL

Abstract

The present invention relates to a medical service relay system and method, by which a medical institution provides a medical service constructed on the basis of SaaS, in connection with diagnosis and prescription for a patient, in order to provide various medical services to the patient. The system comprises: a medical service registration unit for registering information on a medical service to be used in a medical institution; a prescription / medical service mapping unit for providing a list of registered medical services, and receiving and managing information in which a prescription code of each medical institution and at least one medical service are mapped; a prescription data processing unit for receiving prescription information issued to a patient to generate a prescription identifier, and storing the prescription information as prescription data mapped to the prescription identifier; and a service relay unit for retrieving the stored prescription data according to a configured scheduling condition and providing access information of the medical service mapped to the prescription data to a patient terminal, wherein the medical service is a medical service application provided on the basis of SaaS.

Description

A SAAS-based, diverse medical service relay system and method utilizing service URLs.

[0001] The present invention relates to a SaaS-based various medical service relay system and method that utilizes a service URL to relay data between a medical institution system and a SaaS-based medical service so that a medical institution can provide various medical services to patients by linking the medical services built on SaaS with the patient's treatment and prescription, and to enable the patient to access and use the SaaS-based medical service according to the treatment and prescription issued by the medical institution.

[0002]

[0003] Recent advancements in digital technology have significantly increased the spread and acceptance of digital healthcare services. The evolution toward patient-centered healthcare services has necessitated the provision of customized services tailored to individual needs. To this end, medical institutions are continuously striving to introduce new healthcare services.

[0004] However, establishing systems and infrastructure to provide various medical services requires significant time and cost, and there are problems that may arise during the integration process with existing systems and the burden of ongoing operating costs.

[0005] For example, in order to provide a new medical service to a medical institution, a medical service provider must supply separate H / W and S / W. In addition, although the same service is provided to various medical institutions, each medical institution must operate and manage it, which incurs costs. In addition, in order to provide a new service, the medical institution must configure a system or interface for linking to the existing hospital system, making it difficult to update or improve new content for the service and incurring separate costs.

[0006] Therefore, technological solutions that can facilitate the introduction of various medical services in medical institutions are required.

[0007]

[0008] The purpose of the present invention is to solve the above problems by enabling medical service providers to provide services based on SaaS, and for medical institutions to connect various SaaS services provided by medical service providers with patient prescriptions through a medical service relay system, thereby enabling patients to utilize medical services.

[0009]

[0010] A SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention may include: a medical service registration unit for registering information on medical services to be used in medical institutions; a prescription / medical service mapping unit for providing a list of registered medical services and receiving and managing information mapping a prescription code of each medical institution with at least one medical service; a prescription data processing unit for receiving prescription information issued to a patient, generating a prescription identifier, and storing the information as prescription data mapped with the prescription identifier; and a service relay unit for searching stored prescription data according to set scheduling conditions and providing access information of a medical service mapped with the prescription data to a patient terminal; wherein the medical service is a medical service application provided based on SaaS.

[0011] In addition, the medical service registration unit can receive medical service information and SaaS information and store them as medical service targets so that SaaS-based medical services can be used in conjunction with at least one medical institution.

[0012] In addition, the prescription / medical service mapping unit receives and manages prescription codes for at least one medical institution, provides an interface to map at least one registered medical service to the prescription code for each medical institution, and stores and manages mapping data between the prescription code for each medical institution and the medical service mapped through the interface.

[0013] In addition, the prescription data processing unit receives patient prescription information from at least one medical institution system, generates a unique prescription identifier that does not include patient information, maps the prescription identifier and prescription information to store it as prescription data, and processes access, status management, and result updates of the prescription data through the prescription identifier.

[0014] In addition, the patient's prescription information received from the medical institution system is characterized by including the medical institution's prescription code, reservation information, medical staff information, patient information, and guardian information.

[0015] In addition, the service relay unit can schedule a medical service provision time set in advance based on the reservation date and / or prescription date included in the prescription data and transmit a medical service access URL to the patient terminal.

[0016] In addition, the service relay unit requests a service URL for a prescription identifier of the prescription data through SaaS information of a medical service mapped to a prescription code of the prescription data, and transmits the received service URL to a patient terminal, and the service URL includes a prescription identifier and is generated differently for each prescription data.

[0017] In addition, it further includes a usage result receiving unit that receives and stores the service usage result for the medical service provided to the patient, wherein the service usage result includes a prescription identifier, and the medical service usage result is stored by identifying the prescription data through the prescription identifier.

[0018] Meanwhile, a method for relaying various medical services based on SaaS using a service URL according to one embodiment of the present invention may include a step of receiving and registering information on a medical service to be used in a medical institution system in a medical service relay system; a step of receiving and storing mapping information on a prescription code of a medical institution and at least one medical service from the medical institution system; a step of receiving prescription information issued to a patient from the medical institution system and configuring and storing prescription data; a step of providing access information of a medical service mapped with prescription data to a patient terminal according to set scheduling conditions; and a step of receiving a service usage result transmitted by the medical service after the patient uses the medical service through the access information of the medical service transmitted to the patient terminal and storing the result by linking it with prescription data.

[0019] In addition, the step of providing access information of the medical service to the patient terminal may include a step of searching prescription data received and stored from the medical institution system according to the processing order; a step of searching medical services mapped to the prescription code of the searched prescription data; a step of obtaining a service URL according to the linkage information of the medical service; and a step of scheduling and transmitting to the patient terminal according to a medical service provision time set in advance based on the reservation date and / or prescription date of the prescription data.

[0020]

[0021] Through the medical service relay system, multiple medical service providers can register their medical services, and medical institutions can provide patients with registered SaaS-based medical services by linking them to prescriptions. This reduces the cost of building a separate system for providing medical services and reduces the burden of introducing new services and maintaining ongoing service operations.

[0022] Additionally, the medical service relay system allows medical institutions to provide medical services without transmitting sensitive medical information to medical service providers, thereby ensuring data security and personal information protection.

[0023]

[0024] Figure 1 is an overall relationship diagram of a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0025] FIG. 2 is a block diagram of the functions of a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0026] FIG. 3 is a flowchart illustrating a process of mapping medical services by prescription code at a medical institution in a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0027] FIG. 4 is a flowchart illustrating a method for providing medical services to patients according to a prescription from a medical institution in a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0028] Figure 5 is a flowchart of a SaaS-based method for relaying various medical services using a service URL according to one embodiment of the present invention.

[0029] FIG. 6 is a flowchart showing in detail the steps of providing medical service access information to a patient terminal in a SaaS-based various medical service relay method using a service URL according to one embodiment of the present invention.

[0030]

[0031] Hereinafter, specific embodiments of the present invention will be described in detail with reference to the drawings. However, the spirit of the present invention is not limited to the presented embodiments, and those skilled in the art who understand the spirit of the present invention will be able to easily propose other inventions that are retrograde or other embodiments included within the scope of the spirit of the present invention by adding, modifying, or deleting other components within the scope of the same spirit. However, this will also be considered to be included within the scope of the spirit of the present invention.

[0032] In addition, the terms described below are terms established in consideration of their functions in the present invention, and may vary depending on the inventor's intention or custom, so their definitions should be based on the contents throughout this specification, and if it is determined that a specific description of a known structure or function related to the present invention in this specification may obscure the gist of the present invention, a detailed description thereof will be omitted.

[0033]

[0034] Hereinafter, with reference to the drawings, a SaaS-based various medical service relay systems utilizing the service URL according to the present invention are described.

[0035]

[0036] FIG. 1 is an overall relationship diagram of a SaaS-based various medical service relay system (hereinafter referred to as a medical service relay system (100)) utilizing a service URL according to one embodiment of the present invention.

[0037] Referring to FIG. 1, a medical service relay system (100) is connected to at least one medical institution system (200), at least one SaaS medical service server (300), and at least one patient terminal (400) via a network.

[0038] The network referred to in the present invention may be a core network integrated with a wired public network, a wireless mobile communication network, or a mobile Internet, or may mean a global open computer network structure that provides various services existing in the TCP / IP protocol and its upper layer, such as HTTP (Hyper Text Transfer Protocol), HTTPS (Hyper Text Transfer Protocol Secure), Telnet, FTP (File Transfer Protocol), etc., and is not limited to these examples, but comprehensively means a data communication network that can transmit and receive data in various forms.

[0039] The terminal referred to in the present invention should be interpreted as including various communication means such as desktops, tablets, laptops, smartphones, wearable smart devices, etc., and can execute various functions provided by a server or system through web-based or separate software / applications, etc.

[0040] The medical service relay system (100) relays data between the medical institution system (200) and the SaaS-based medical service so that the medical institution can provide various medical services to patients by linking the medical service built on SaaS with the patient's treatment and prescription, and the patient can access and use the SaaS-based medical service according to the treatment and prescription.

[0041] Examples of medical services here include chatbot-based virtual examination room services, online caregiver participation services, experiential medical digital curation services, and smart surgical consent forms, and can be provided to patients in various ways in connection with treatment and prescriptions.

[0042] In addition, the above medical service can be implemented as a SaaS model in a cloud environment and distributed to a SaaS medical service server (300) to provide the service.

[0043] In the present invention, the medical institution system (200) may include systems of medical institutions that create, manage, and use EMR (electronic medical records), and the medical institution mentioned in the present invention may be used with the same meaning as the medical institution system (200).

[0044] The medical service relay system (100) provides medical services linked to prescriptions through relay between a medical institution system (200), a SaaS medical service server (300), and a patient terminal (400).

[0045] A medical service provider distributes a medical service to a SaaS medical service server (300) and registers service information and linkage information in a medical service relay system (100) so that the medical institution can use the medical service. The medical institution can map the prescription items (prescription codes) of each medical institution and at least one medical service registered in the medical service relay system (100) through an interface provided by the medical service relay system (100), and the medical service relay system (100) receives and manages mapping information for medical services by prescription item (prescription code), thereby receiving prescription information issued by the medical institution to the patient from the medical institution system (200), confirming the medical service mapped to the prescription item of the prescription information, and transmitting a service URL so that the medical service can be accessed and used with a patient terminal (400).

[0046] This allows medical institutions to reduce the costs and maintenance burden that arise each time they introduce a new medical service, and to reduce the risk of integration with existing systems due to each new medical service introduction.

[0047] In addition, the medical service relay system (100) manages the minimum patient information and medical information required to provide medical services to patients by applying a data security policy, and connects with an external SaaS medical service server (300) through a prescription identifier that can identify the above information, thereby protecting the patient's personal information. In addition, the SaaS medical service server (300) can effectively perform security management for sensitive medical information by applying authentication and data access rights to requests for access to medical information required when providing medical services to patients.

[0048] Meanwhile, the prescription information referred to in the present invention includes prescriptions and reservations including treatment and medication, examination, and surgery, and may include records of all medical acts issued by a doctor.

[0049]

[0050] FIG. 2 is a block diagram of the functions of a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0051] The function of the medical service relay system (100) is described with reference to FIG. 2.

[0052] The medical service relay system (100) may be equipped with a medical service registration unit (110), a prescription / medical service mapping unit (120), a prescription data processing unit (130), a service relay unit (140), and a usage result receiving unit (150).

[0053] The medical service registration unit (110) receives information about medical services operating in the SaaS medical service server (300) and performs a process of registering the medical services so that they can be used in at least one medical institution system (200).

[0054] The medical service registration unit (110) can receive new medical service information or change information for existing registered medical services from the SaaS medical service server (300) according to a predefined interface.

[0055] Medical service information may include service specification information including a service identifier, service description, etc., SaaS information for service linkage, and authentication information for linkage between a medical service relay system (100) and a medical service.

[0056]

[0057] The prescription / medical service mapping unit (120) receives prescription codes for at least one medical institution, manages prescription codes for each medical institution, and provides an interface to map at least one medical service to the prescription code.

[0058] Prescription codes mapped to medical services here may include surgeries, hospitalizations / discharges, prescriptions, and tests. These items may be defined in detail by disease or by specific disease groups. However, this is not limited to this, and prescription codes mapped to medical services may be defined differently by medical institution.

[0059] In order to map prescription codes and medical services, the prescription / medical service mapping department (120) provides a web or app screen that can connect the prescription codes of each medical institution with registered medical services, and medical professionals can access the web or app screen through a medical terminal (200) or medical institution system (200) to map prescription codes and medical services.

[0060] As another example, the prescription / medical service mapping unit (120) transmits a list of registered medical services upon request from the medical institution system (200), and when a medical practitioner accesses the medical institution system (200) through a medical terminal (500) to map the prescription code and medical service and then transmits the information to the medical service relay system (100), the prescription / medical service mapping unit (120) can store this in a database.

[0061] That is, the prescription / medical service mapping unit (120) provides an interface that can add, change, and delete mapping information for prescription codes and medical services by medical institution, and reflects the mapping information received through the interface in the database.

[0062]

[0063] The prescription data processing unit (130) receives prescription information issued to a patient from at least one medical institution system (200), generates a prescription identifier, processes the received prescription information to form prescription data, and then stores the information by linking it to the prescription identifier.

[0064] Here, the prescription information received from the medical institution system (200) may include patient information, guardian information, treatment information, examination information, examination prescription information, drug prescription information, admission / discharge information, and surgery information, but is not limited thereto, and it is preferable to include various information related to treatment and prescription.

[0065] Additionally, the prescription information received may include a medical institution number that can identify the medical institution and a prescription number for each medical institution that can identify the prescription issued within the medical institution.

[0066] The prescription data processing unit (130) may include a prescription identifier management unit (131) and a prescription data storage unit (132).

[0067] The prescription identifier management unit (131) creates a prescription identifier to manage prescription information received from multiple medical institutions. The prescription identifier is a unique value for identifying prescription information without including patient information.

[0068] For example, a prescription identifier can be created by combining the medical institution number (medical institution identifier), the prescription number for each medical institution, the patient name, and the patient phone number and applying a hash.

[0069] The prescription data storage unit (132) processes the prescription information received from the medical institution system (200) to create prescription data including patient information, guardian information, reservation information, and medical staff information, and stores the data in a database by mapping it with the prescription identifier created by the prescription identifier management unit (131).

[0070] This enables access, status management, and update of the patient's prescription data through the SaaS medical service server (300), patient terminal (400), and prescription identifier.

[0071]

[0072] The service relay unit (140) searches for prescription data stored from the medical institution system (200) according to set scheduling conditions, checks the medical service mapped to the prescription data, and performs scheduling work to provide the medical service to the patient.

[0073] At this time, the service relay unit (140) schedules the medical service provision time set in advance based on the reservation date and / or prescription date for treatment, examination, surgery, and prescription included in the prescription data, and transmits access information for the medical service to the patient terminal (400).

[0074] Here, the connection information is a service URL for connecting to an individual medical service operating on the SaaS medical service server (300), and may be generated differently for each prescription data.

[0075] The service relay unit (140) searches for SaaS information of a medical service mapped to the prescription code of the prescription data and requests a service URL from the SaaS medical service server (300) where the corresponding medical service operates. However, by transmitting a prescription identifier together, a different service URL can be obtained for each prescription data. In other words, the SaaS-based medical service can provide medical services to a specific patient in a separate service execution space for each prescription identifier and generate usage results.

[0076] As an example of service relay, if a chatbot-based virtual pre-examination medical service is mapped to an outpatient treatment reservation and the medical service is set to be provided to the patient 3 days prior to the reservation date, when an outpatient treatment reservation is made for a specific patient in the medical institution system (200), the prescription information for the outpatient treatment is transmitted to the medical service relay system (100) and stored as prescription data, and the service relay unit (140) checks the provision time (3 days prior to the reservation date) of the virtual pre-examination medical service mapped to the outpatient treatment prescription code of the prescription data, requests and obtains a service URL through SaaS linkage information according to the schedule, and then transmits it to the patient terminal (400).

[0077] At this time, the service URL transmitted to the patient terminal (400) also includes a prescription identifier and is transmitted. When the patient terminal (400) accesses the service URL, the SaaS medical service goes through a pre-determined authentication process such as OAuth authentication, and then requests the medical service relay server (100) to provide medical service for which prescription data through the prescription identifier, obtains the prescription data, and then provides the medical service.

[0078]

[0079] The usage result receiving unit (150) receives the usage result from the SaaS medical service server (300) after the use of the medical service transmitted to the patient terminal (400) is completed.

[0080] More specifically, when the service relay unit (140) requests a service URL according to the SaaS information of a specific medical service, it transmits a prescription identifier, and the SaaS medical service server (300) that receives it creates a medical service instance corresponding to the prescription identifier and transmits a service URL including the prescription identifier for accessing the medical service, and the patient terminal (400) that receives the service URL accesses the service URL to receive the medical service. When the medical service is completed, the medical service instance transmits the medical service usage result together with the prescription identifier to the medical service relay system (100), and the usage result receiving unit (150) stores the medical service usage result by connecting it to the prescription data corresponding to the prescription identifier.

[0081] The results of using medical services saved in this way can be provided upon request from the medical institution system (200).

[0082]

[0083] FIG. 3 is a flowchart illustrating a process of mapping medical services by prescription code at a medical institution in a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0084] Referring to Figure 3, companies providing medical services distribute various medical services to the SaaS medical service server (300) so that the medical institution system (200) can use the services.

[0085] When medical services are distributed to the SaaS medical service server (300), it may include service specification information including service identifiers, service descriptions, SaaS information for service linkage, and authentication information for linkage between the medical service relay system (100) and the medical service.

[0086] Medical services newly registered in the SaaS medical service server (300) can perform a medical service registration process with the medical service relay system (100). When a request for medical service registration is made including medical service information, SaaS information, and linkage information, the medical service relay system (100) that receives the request can register the new medical service, transmit a list of added / changed medical services to the medical institution system (200), or provide a list of medical services upon request from the medical institution system (200).

[0087] The medical institution system (200) can set the medical services to be provided for each prescription by mapping the list of received medical services and the prescription code used by the medical institution.

[0088] The mapped information is stored and managed in the medical service relay system (100).

[0089]

[0090] FIG. 4 is a flowchart illustrating a method for providing medical services to patients according to a prescription from a medical institution in a SaaS-based various medical service relay system utilizing a service URL according to one embodiment of the present invention.

[0091] Referring to Figure 4, the process of providing medical services to patients according to a prescription at a medical institution is described.

[0092] When surgery is prescribed to a patient, the medical institution system (200) issues prescription information for the surgery reservation, and the prescription information is transmitted to the medical service relay system (100).

[0093] The medical service relay system (100) generates a prescription identifier for the received prescription information, configures prescription data, and stores it in a database.

[0094] Through scheduling work, the medical service relay system (100) searches the corresponding prescription data to check the digital curation service and smart consent service mapped to the prescription code, and requests a service URL to be provided to the patient terminal (400) through SaaS linkage information for the medical service.

[0095] The digital curation service and smart consent form service on the SaaS medical service server (300) generate a service URL for the prescription identifier and transmit it in response to the request, and the medical service relay system (100) transmits the service URL to the patient terminal (400) via text message or notification talk according to the medical service provision standards. At this time, the digital curation service URL and smart consent form service URL may be transmitted together, or if there are conditions for the order of progress, they may be transmitted individually according to the transmission standards.

[0096] The patient terminal (400) receives medical services by accessing the received service URL.

[0097] When the medical service provided by the patient terminal (400) is completed, each medical service transmits the usage result to the medical service relay system (200), and the medical service relay system (100) stores the medical service usage result by linking the usage result with the prescription data corresponding to the prescription identifier.

[0098]

[0099] Meanwhile, the hardware structure of the medical service relay system (100) is configured to include a central processing unit (1000), memory (2000), user interface (3000), database interface (4000), network interface (5000), web server (6000), etc.

[0100] The user interface (3000) provides input and output interfaces to the user by using a graphical user interface (GUI).

[0101] The database interface (4000) provides an interface between the database and the hardware structure.

[0102] The network interface (5000) provides network connectivity between devices owned by the user.

[0103] The web server (6000) provides a means for users to access the hardware structure via a network. Most users can access the medical service relay system (100) remotely by accessing the web server.

[0104] Each step of the above-described configuration or method may be implemented as computer-readable code on a computer-readable recording medium or transmitted via a transmission medium. The computer-readable recording medium is a data storage device capable of storing data that can be read by a computer system.

[0105] Examples of computer-readable recording media include, but are not limited to, databases, ROMs, RAMs, CD-ROMs, DVDs, magnetic tapes, floppy disks, and optical data storage devices. Transmission media may include carrier waves transmitted over the Internet or various types of communication channels. Furthermore, computer-readable recording media may be distributed through a network-connected computer system, such that computer-readable code is stored and executed in a distributed manner.

[0106] In addition, at least one component applied to the present invention may include or be implemented by a processor, such as a central processing unit (CPU) or microprocessor, which performs each function, and two or more of the components may be combined into a single component that may perform all operations or functions of the two or more combined components. In addition, a part of at least one component applied to the present invention may be performed by another component among these components. In addition, communication between the components may be performed via a bus (not shown).

[0107]

[0108] FIG. 5 is a flowchart for a SaaS-based method for relaying various medical services using a service URL according to one embodiment of the present invention, and FIG. 6 is a flowchart showing in detail the steps for providing medical service access information to a patient terminal in a SaaS-based method for relaying various medical services using a service URL according to one embodiment of the present invention.

[0109] Referring to FIGS. 5 and 6, a medical service relay method performed in a medical service relay system is described.

[0110] First, a step (S100) is performed in which information about medical services to be used in the medical institution system is received and registered in the medical service relay system.

[0111] Each medical service distributed on the SaaS medical service server (300) can request medical service registration by transmitting medical service information, SaaS information, and linkage information.

[0112] In response to a request for medical services, the medical service relay system (100) registers a new medical service, thereby enabling the medical institution system (200) to use the new medical service by mapping it to a prescription code.

[0113] The medical service registration process can be performed when a new service is deployed or when information for an existing registered service changes.

[0114] Next, a step (S200) is performed to receive and store the prescription code of the medical institution and mapping information for at least one medical service from the medical institution system (200).

[0115] The medical service relay system (100) can transmit a list of added / changed medical services to the medical institution system (200), or provide a list of medical services upon request from the medical institution system (200). Upon receiving this, the medical institution system (200) can map the list of medical services and the prescription codes used by the medical institution to set the medical services to be provided for each prescription, and the mapped information is stored and managed in the medical service relay system (100).

[0116] Steps S100 and S200 may be performed initially before Step S300, and may be performed periodically when new medical services are registered, existing medical service information is changed, or the like.

[0117] Next, a step (S300) is performed to receive prescription information issued to a patient from a medical institution system (200) and configure and store prescription data.

[0118] When a medical practitioner issues a patient prescription, the medical institution system (200) transmits the prescription information to the medical service relay system (100). Upon receiving the prescription information, the medical service relay system (100) creates a prescription identifier for the prescription information, configures prescription data linked to the prescription identifier, and stores the information in a database.

[0119] Afterwards, a step (S400) is performed to retrieve prescription data according to the set scheduling conditions and provide access information for medical services mapped to the prescription data to the patient terminal.

[0120] More specifically, referring to FIG. 6, in step S400, prescription data received and stored from a medical institution system is retrieved in the processing order (S410), a medical service mapped to the prescription code of the retrieved prescription data is retrieved (S420), a service URL is obtained according to the SaaS linkage information of the medical service, and a process of scheduling and transmitting the service to the patient terminal according to a medical service provision time set in advance based on the reservation date and / or prescription date of the prescription data can be performed (S430).

[0121] At this time, the order in which prescription data is processed may be various conditions such as prescription data creation time, prescription type (prescription code), reservation time, etc., or a combination of these conditions.

[0122] After step S400, the patient can use the medical service through the medical service access information transmitted to the patient terminal (400), and when the medical service is completed, the medical service relay system (100) receives the service use result transmitted by the medical service and performs a step (S500) of storing it by linking it with prescription data.

[0123]

[0124] Although the configuration and features of the present invention have been described above based on embodiments according to the present invention, the present invention is not limited thereto, and it is obvious to those skilled in the art that various changes or modifications can be made within the spirit and scope of the present invention, and therefore, it is made clear that such changes or modifications fall within the scope of the appended patent claims.

[0125]

[0126] Through the medical service relay system, multiple medical service providers can register their medical services, and medical institutions can provide patients with registered SaaS-based medical services by linking them to prescriptions. This reduces the cost of building a separate system for providing medical services and reduces the burden of introducing new services and maintaining ongoing service operations.

[0127] Additionally, the medical service relay system allows medical institutions to provide medical services without transmitting sensitive medical information to medical service providers, thereby ensuring data security and personal information protection.

Claims

1. Medical service registration book that registers information on medical services to be used at medical institutions; A prescription / medical service mapping department that provides a list of registered medical services and receives and manages information mapping the prescription code of each medical institution to at least one medical service; A prescription data processing unit that receives prescription information issued to a patient, generates a prescription identifier, and stores the prescription data mapped to the prescription identifier; and A service relay unit is provided that searches for stored prescription data according to set scheduling conditions and provides access information for medical services mapped with the prescription data to the patient terminal; The above medical service is a medical service application provided based on SaaS. Medical service relay system.

2. In paragraph 1, The above medical service registration is, Receive medical service information and SaaS information and store them as medical service targets so that SaaS-based medical services can be used in conjunction with at least one medical institution. Medical service relay system.

3. In paragraph 1, The above prescription / medical service mapping department, A system for receiving and managing prescription codes for at least one medical institution, providing an interface to map at least one registered medical service to the prescription code for each medical institution, and storing and managing mapping data between the prescription code for each medical institution and the medical service mapped through the interface. Medical service relay system.

4. In paragraph 1, The above prescription data processing unit, Receives patient prescription information from at least one medical institution system, generates a unique prescription identifier that does not include patient information, maps the prescription identifier and prescription information to store it as prescription data, and processes access, status management, and result updates of prescription data through the prescription identifier. Medical service relay system.

5. In paragraph 4, The patient's prescription information received from the above medical institution system is characterized in that it includes the medical institution's prescription code, reservation information, medical staff information, patient information, and guardian information. Medical service relay system.

6. In paragraph 1, The above service relay unit is, Scheduling medical services according to the pre-set medical service provision time based on the reservation date and / or prescription date included in the prescription data and transmitting the medical service access URL to the patient terminal. Medical service relay system.

7. In paragraph 6, The above service relay unit is, Request a service URL for the prescription identifier of the above prescription data through the SaaS information of the medical service mapped to the prescription code of the above prescription data, and transmit the received service URL to the patient terminal. The above service URL includes a prescription identifier and is characterized in that it is generated differently for each prescription data. Medical service relay system.

8. In paragraph 7, It further includes a usage result receiving unit that receives and stores the service usage results for the medical service provided to the patient; The above service usage result includes a prescription identifier, and is characterized in that the prescription data is identified through the prescription identifier and the medical service usage result is stored. Medical service relay system.

9. In the medical service relay system, a step of receiving and registering information on medical services to be used in the medical institution system; A step of receiving and storing a prescription code of a medical institution and mapping information for at least one medical service from the above medical institution system; A step of receiving prescription information issued to a patient from the above medical institution system, configuring prescription data, and storing the same; A step of providing access information of medical services mapped with prescription data to a patient terminal according to set scheduling conditions; and A step of receiving the service usage result transmitted by the medical service after the patient uses the medical service through the access information of the medical service transmitted to the patient terminal and storing it by linking it with the prescription data; including; Method of relaying medical services.

10. In paragraph 9, The step of providing access information for the above medical service to the patient terminal is: A step of searching prescription data received and stored from the above medical institution system according to the processing order; A step of searching for a medical service mapped to the prescription code of the searched prescription data; A step of obtaining a service URL according to the linkage information of the above medical service; and A step of scheduling and transmitting to a patient terminal according to a pre-set medical service provision time based on the reservation date and / or prescription date of the prescription data; including; Method of relaying medical services.

Images