Hospital information processing system and method

Abstract

Provided is a computer-implemented method for hospital information processing, which assists a patient with a medical treatment registration process at a hospital. The method, according to one embodiment, may comprise the steps of: in response to a unique identifier of a hospital being identified on a terminal of a patient visiting the hospital, starting a medical treatment registration interface for the hospital on the patient terminal; and providing information of the patient corresponding to at least one item required by the hospital to a hospital client associated with the hospital.

Description

Hospital information processing system and method

[0001] The description below relates to a hospital information processing system and method.

[0002] Patients visiting a hospital for treatment for the first time are required to complete a customer registration process called a "first-time visit application form." This form typically includes demographic information such as name, resident registration number (e.g., Social Security number or date of birth), and address. It also asks for information about current ailments, symptoms, past medical history, and medications taken. Furthermore, each hospital may collect additional customer information necessary for its operational purposes.

[0003] In most cases, patients fill out the forms themselves on printed paper, which hospital staff then enters into the hospital's EMR. Some hospitals offer alternative data entry methods, such as tablets or laptops. However, these can be inconvenient, requiring patients to touch a tablet already in use or wait if someone else is using it. Furthermore, each hospital handles the receipt, processing, and storage of medical treatment requests differently, so unless you're returning to your current hospital, you'll always have to re-enter all the basic information.

[0004] (Patent Document 1) Republic of Korea Patent No. 10-2433466 (announcement date: August 18, 2022) proposes a method for assisting the reception of patients visiting a hospital by linking with EMR.

[0005] (Patent Document 2) Republic of Korea Patent No. 10-2028692 (publication date October 4, 2019) suggests a method for collecting patient information and compiling statistics to assist hospital operations.

[0006] We manage patient-based personal information, medical records, and other information the hospital may require in a single place. We minimize the hassle of the admission process, even for first-time patients. Furthermore, we minimize patient inconvenience.

[0007] Hospitals are also improving operational convenience, and especially in hospitals with a large number of inpatients, work efficiency is improved even if the number of personnel required for treatment registration is minimized.

[0008] Patient information obtained with the patient's consent is useful for patient treatment and hospital management, and also helps with customer relationship management (CRM) for hospitals and patients.

[0009] Hospitals should prevent potential vulnerabilities in personal information protection due to improper handling of documents containing personal information, such as initial consultation forms. This also minimizes potential violations of the Personal Information Protection Act and reduces risks throughout the security, handling, and disposal of patient information.

[0010] Furthermore, the information required for first-time application is templated and shared and traded through Mobidac, contributing to the overall improvement of the level of medical services.

[0011] According to one aspect, a computer-implemented method for processing hospital information is provided to assist a patient in registering for treatment at a hospital. The method may include: in response to a patient visiting the hospital identifying a unique identifier of the hospital on the patient's terminal, initiating a registration interface for the hospital on the patient's terminal; and providing patient information corresponding to at least one item requested by the hospital to a hospital client associated with the hospital.

[0012] According to one embodiment, at least one item requested by the hospital, including patient information stored in the database, is extracted and provided to the hospital client even without input from the patient terminal. This embodiment allows the patient to enter only information not previously entered during membership registration and / or information that the patient wishes to change.

[0013] In one embodiment, if the patient terminal is an unidentified terminal in the pre-stored subscriber information, the medical reception interface is initiated based on a temporarily generated web page, and information entered on the web page is reused in the patient's registration process. In other words, information directly entered by the patient during the medical reception process can be reused in some of the service membership registration information fields. This simplifies the membership registration process.

[0014] According to one embodiment, a plurality of questionnaire templates are provided to the hospital client, and a first template selected by the hospital client is used as at least one item required by the hospital.

[0015] Here, an editing interface may be provided that allows the hospital client to edit at least one of the questionnaire items, arrangement order, and design layout included in the first template.

[0016] Additionally, in this embodiment, at least one item of the first template is provided with a question code matched to the electronic chart of the hospital's electronic medical record (EMR). By way of example, but not limitation, the method further includes the step of copying response information for the at least one item into the electronic medical record by associating it with the question code.

[0017] According to one embodiment, information entered into the disclosed medical reception interface is updated by reflecting it in the patient information stored in the database. Furthermore, in some embodiments, the results of this update are also provided to a second hospital client at a different hospital than the aforementioned hospital.

[0018] Meanwhile, in one embodiment, if there is a request to delete information in the hospital client of the hospital from the terminal of the patient, the method may further include a step of transmitting the deletion request to the hospital client.

[0019] According to the examples, the initial consultation process is greatly simplified and patient convenience is enhanced by centrally managing patient-based personal information, medical records, and other information the hospital may require. This process eliminates the need for patients to wait in line at the reception desk or interact closely with others, which also contributes to infectious disease management.

[0020] Hospitals are moving closer to a paperless environment as they no longer need to keep unnecessary registration forms, and patients can use their own devices to register for their first visit, reducing the number of items and facilities that need to be kept on hand, which is helpful for hospital management.

[0021] Patient information obtained with the patient's consent can be used for patient treatment and hospital management, and can be utilized for customer relationship management (CRM) to promote patient health.

[0022] This fundamentally prevents potential vulnerabilities in personal information protection due to improper handling of documents containing personal information, such as initial consultation forms. Hospitals can therefore minimize potential violations of the Personal Information Protection Act and enhance convenience and safety across all procedures, from securing patient information to handling and disposal.

[0023] Furthermore, the information required for first-time application is templated and shared and traded through Mobidac, contributing to the overall improvement of the level of medical services.

[0024] The above description is exemplary, and the effects brought about by the embodiments are also described when describing each embodiment throughout the specification.

[0025] Figure 1 is a drawing for explaining the connection between a hospital information processing device, a patient terminal, and a doctor terminal.

[0026] Figure 2 is a drawing explaining an operation method of a hospital information processing device according to one embodiment.

[0027] Figure 3 is referenced to explain the process of receiving treatment according to an embodiment and the advantages thereof.

[0028] Figure 4 is referenced in relation to the treatment reception procedure and classification processing of first and second visits according to an embodiment.

[0029] Figure 5 illustrates a process of writing down symptoms during a medical reception according to an embodiment.

[0030] Figure 6 illustrates exemplary items of a first-time examination questionnaire provided to a patient receiving a first-time examination according to one embodiment.

[0031] Figure 7 illustrates the process of completing the medical treatment reception.

[0032] Figure 8 is a drawing for explaining a procedure in which a medical treatment reception is linked to an EMR chart according to one embodiment.

[0033] Figure 9 illustrates a screen for providing and editing a first-time reception template according to an embodiment.

[0034] Figure 10 illustrates an exemplary screen of the basic template editing process.

[0035] Figure 11 illustrates a statistical screen of the results of medical treatment reception according to an embodiment.

[0036] Figure 12 illustrates input data output for first-time patients who have registered for treatment according to one embodiment.

[0037] Hereinafter, embodiments are described in detail with reference to the attached drawings. However, the scope of the invention is not limited or restricted by these embodiments. The same reference numerals in each drawing represent the same components.

[0038] The terms used in the following description have been selected as common and universal in the relevant technical fields. However, other terms may be used depending on technological developments and / or changes, customs, and the preferences of technicians. Therefore, the terms used in the following description should not be construed as limiting the technical concepts, but rather as exemplary terms used to describe the embodiments.

[0039] Additionally, in certain cases, the applicant may arbitrarily select terms, in which case their detailed meanings will be described in the relevant description. Therefore, the terms used in the following description should be understood not simply as names, but based on their inherent meaning and the overall context of the specification.

[0040] The hospital information processing system according to one embodiment may be an electronic device. An electronic device may include any general-purpose computing device implemented by hardware in the form of a system-on-chip (SoC) and / or application software, as long as it provides service connection and implementation.

[0041] For example, the electronic device may include at least one of a smartphone, a tablet personal computer, a mobile phone, a video phone, an e-book reader, a desktop personal computer, a laptop personal computer, a netbook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), an MP3 player, a mobile medical device, a camera, or a wearable device (e.g., a head-mounted device (HMD) such as electronic glasses, electronic clothing, electronic bracelet, electronic necklace, electronic appcessory, electronic tattoo, or smart watch).

[0042] According to a further embodiment, the electronic device may include at least one of various medical devices (e.g., magnetic resonance angiography (MRA), magnetic resonance imaging (MRI), computed tomography (CT), a camera, an ultrasound machine, etc.), a navigation device, a global positioning system receiver (GPS receiver), an event data recorder (EDR), a flight data recorder (FDR), an automobile infotainment device, electronic equipment for ships (e.g., a navigation device and a gyrocompass for ships), avionics, a security device, a head unit for cars, an industrial or household robot, an automatic teller's machine (ATM) of a financial institution, or a point of sales (POS) of a hospital.

[0043] In addition, the electronic terminal may include at least one of intelligent furniture or a part of a building / structure for connecting to a remote medical service, an electronic board, an electronic signature receiving device, a projector, or various measuring devices (e.g., water, electricity, gas, or radio wave measuring devices, etc.). An electronic device according to various embodiments of the present invention may be a combination of one or more of the various devices described above. In addition, an electronic device according to various embodiments of the present invention may be a flexible device. As such, it is obvious to those skilled in the art that the form of the electronic device itself is diverse, and the form and main use (other than the function of providing a remote medical service) of the electronic device are not limited to the above-described matters. Hereinafter, specific embodiments will be described with reference to the drawings.

[0044] Medical reception services provided by Mobidoc™ according to embodiments

[0045] MobiDoc TM ) service helps patients visiting hospitals easily register for treatment. Mobidoc, which provides various services that enhance the completeness of medical care, is revolutionizing offline patient registration in a smart way.

[0046] Patients visiting a hospital for treatment typically complete a customer registration process called a "first-time visit application." Since the hospital has no prior records of the patient, this is a necessary step for registering a new patient and creating a customer card. While completing and submitting the first-time visit application not only serves as a treatment request, it can also be understood as the initial registration process, registering the patient in the hospital system, such as the electronic medical record (EMR), unlike a repeat visit application.

[0047] The initial consultation application form primarily includes demographic information such as name, resident registration number (e.g., Social Security number or date of birth), and address. It also asks for information on current ailments and symptoms, past medical history, and medications taken. Furthermore, hospitals may collect additional customer information necessary for hospital operations. Registered patients are required to provide minimal identification for subsequent visits and registration.

[0048] Most of the medical treatment application process is done by patients filling out printed paper sheets, which hospital staff then input into the hospital EMR. Some hospitals provide other information input methods such as tablet PCs and laptops, but basically, each hospital must input from scratch.

[0049] According to the example, Mobidac TM Mobidac securely stores the information (name, date of birth, address, contact information, medications taken, side effects, allergies, medical history, blood pressure, blood sugar, weight, blood type, and other information that medical staff need to know during treatment) of users who have signed up for Mobidac. While storing the patient's information, when the patient checks in for the first visit to the hospital (such as by scanning the QR code provided at a Mobidac affiliated hospital), the information requested by the hospital is exported from the Mobidac storage with the patient's (user's) consent and transmitted to the hospital system. In other words, Mobidac provides a means for patients visiting the hospital for treatment to communicate with the hospital quickly, conveniently, and safely for the first time. Mobidac also provides services from registration to payment (receipt) of medical fees, elevating the level of medical service with the motto, "When going to the hospital, go to Mobidac."

[0050] According to one example, when a patient terminal for first-time registration at a hospital recognizes the hospital QR code, Mobidoc TMIt also helps with initial treatment even when the user is not identified (e.g., cannot run and log in to the Mobidoc app) or is not a member. Unlike when the patient is a Mobidoc member, in this case, the patient is not a member of Mobidoc. TM Since the hospital does not have the patient's information previously, Mobidac assists in entering the information requested by the hospital (via a patient-facing terminal, such as a smartphone, or a temporary information terminal provided by the hospital). Optionally, with the patient's consent, the hospital can encourage Mobidac registration by offering, "Sign up for Mobidac. It will make your next hospital visit much more convenient." The information entered during the initial registration process is used, with the patient's consent, as Mobidac registration information.

[0051] Each drawing is described in more detail below.

[0052] System and service configuration

[0053] Figure 1 is a drawing for explaining the connection between a hospital information processing device (100), a patient terminal (101), and hospital terminals (102 or 103).

[0054] In the schematic diagram shown, the device (100) is implemented by a server-class computer, a workstation, a desktop computer, a laptop computer, a mobile electronic device, etc., and it is also possible to implement it by a plurality of devices among these. The device (100) can provide the Mobidac service.

[0055] The device (100) is connected to a patient terminal (101) via a network, and is also connected to a doctor terminal (or nurse / hospital staff terminal, hereinafter, the term 'doctor terminal' should be understood to include all hospital-side terminals including nurses and administrative staff) (102) and a hospital terminal (103). Each of the terminals (101 to 103) can also correspond to a desktop computer, a laptop computer, a mobile electronic device such as a smartphone or a tablet PC, etc. Each of the terminals (101 to 103) has a software means, which is conveniently referred to as a 'client'.

[0056] A patient client is executed on the patient terminal (101). A doctor client is executed on the doctor terminal (102), and a hospital client is executed on the hospital terminal (103). The doctor client corresponds to a counter part of the patient client and is installed in the hospital. There may also be an online cloud service in the form of SaaS (Software as a Service). In this case, the doctor client refers to a service type in which a cloud service is provided when accessed through the account of a doctor and / or hospital staff. The hospital client is a means for performing treatment assistance tasks such as receiving treatment and collecting hospital fees, rather than a medical professional (doctor) performing the treatment. The doctor client used by the doctor and the hospital client (103) used by hospital staff other than doctors may be provided separately. However, according to one embodiment, the doctor client and the hospital client are integrated into one, and if the log-in account is a doctor user with a medical license, all functions are activated, and if the log-in account is a non-doctor staff member, some functions are deactivated. Some of the functions that are disabled are functions that only doctors should perform, such as 'Start Remote Consultation'. Since the time to start the consultation of the next patient can be most accurately and appropriately selected by the doctor, the 'Start Consultation' function that initiates a video call with the patient client waiting in the consultation room is implemented as a function that only doctors can perform. However, this is an example, and in the following, the 'doctor client' can be understood to include the 'doctor client' installed on the doctor terminal (102) and the hospital terminal (103) and the 'hospital client' used by the hospital staff (or conversely, even if it is called a 'hospital client', it can also include the 'doctor client').

[0057] The client installed on the terminals (101 to 103) may be an original application software installed, a service provided through a page accessed through a web-based browser, or a hybrid app having both app and web characteristics. Furthermore, it may be a cloud-based service provided in the form of SaaS. Since such implementations are feasible for developers with ordinary skill in the art, further detailed descriptions are omitted, and even if the description of the embodiments mentions one example, it does not exclude other implementations. The implementation and operation of the device (100) will be described with reference to FIG. 2.

[0058] System configuration and Mobidac treatment reception processing process

[0059] FIG. 2 is a diagram illustrating an operating method of a hospital information processing device according to an embodiment. The device (100) may be an electronic device including at least one processor (120), a communication interface (110), and a storage unit (130). The device is communicatively connected to a patient terminal (101) and a medical institution (hospital) terminal (103), and processes patient reception into the medical institution terminal (103) and / or the electronic medical record (EMR) (220) of the hospital (200) connected to the terminal (103). The reception process is described in flow.

[0060] The device (100) provides a unique identifier for the hospital (200) via a hospital client installed on the hospital terminal (103). An example of the unique identifier may be, for example, a QR code (211). The QR code (211) is displayed on a display (210) near the hospital entrance or reception desk. In some cases, the QR code may be provided through other means instead of the display (210).

[0061] According to one embodiment, the QR code (211) is not only unique to the hospital (200), but can also dynamically change by including time stamp information. This is because if a fixed identifier is held or spread to outside parties, including patients, confusion may arise during hospital treatment registration. For example, there may be adverse effects such as patients registering for hospital treatment from afar before they even arrive at the hospital, disrupting work, or patients registering for treatment at the wrong hospital. Some other services allow patients to register for hospital treatment by having them scan a hospital barcode reader with their unique QR code or barcode. However, there may be problems such as other people registering for treatment on their behalf with the patient's unique identifier, or patients having no means of controlling the patient if their terminal is excluded from the registration process after the patient identifier has been read by the hospital reader.

[0062] Accordingly, according to one embodiment, the process proceeds as a patient terminal (101) reads a QR code (211), which is a dynamic identifier unique to the hospital (200) and changes periodically through a time stamp or other encryption means, and requests reception and consents to the provision of information through the patient's Mobidoc patient client. Therefore, in terms of security and the patient's right to decide on their own information, there are many advantages over reception through reading the barcode of a conventional medical card.

[0063] In step (201), the device (100) providing the Mobidac service provides a dynamic QR code (211), which is a unique identifier of the hospital, through the hospital terminal (103) controlling the display (210) and the hospital client installed thereon. It is also possible for the device (100) to provide some key values ​​and / or a timestamp, rather than providing an image of the completed code (211), so that the hospital terminal (103) can encode the QR code.

[0064] In step (202), a patient who wishes to register for treatment (including first and second visits) operates the camera of his / her terminal (101) to take a picture of the hospital QR code (211). Then, depending on whether the Mobidoc app is installed on the terminal (101), the patient's treatment registration process for the hospital (200) is initiated through the Mobidoc app or the web-based Mobidoc page. After the photo is taken, the patient does not need to stand in front of the display (211). There is no need to stand in line at the treatment registration desk or stand in front of the desk while filling out the form. The patient can simply sit comfortably on a sofa in any space of his / her choice, such as a hospital waiting room, and proceed with the treatment registration process for the hospital (200) on his / her own using his / her terminal (101).

[0065] In step (203), information entered into the terminal (101) during the process of filling out the medical treatment application form is transmitted to the Mobidac service device (100), and, if necessary, information is exchanged, such as the Mobidac service device (100) receiving the patient's consent or confirmation through the terminal (101). This process is a process of creating an electronic document according to a form requested online.

[0066] In step (204), with the patient's consent and knowledge, the device (100) provides patient information to the hospital client of the hospital terminal (103) regarding items requested by the hospital (200). The information provided includes extraction and sharing of information already entered by the patient when signing up for the Mobidac service, and transmission of information entered by the patient on the terminal (101) regarding items requested by the hospital but not available in the storage (130) of the Mobidac device (100).

[0067] Advantages of Mobidac's medical registration process

[0068] The hospital client inputs the information provided from the Mobidoc device (100) into the linked EMR (220) to process treatment reception and / or patient registration. Information transfer and sharing according to these embodiments has several advantages.

[0069] First, even if a patient does not update their changed information upon arrival at the hospital, their personal information can be updated and registered through information updates between the Mobidoc device (100) and the hospital client. When visiting a hospital after a long time, the address recorded and managed on the patient card may be outdated. The Mobidoc service eliminates the hassle of updating this information.

[0070] Furthermore, hospitals can process patient registrations without providing patients with paper, writing instruments, or tablets. This creates a paperless environment, eliminating the need for hospital staff to input information from paper medical application forms into the hospital's EMR (220), making the process faster and less error-prone.

[0071] Additionally, since patients typically verify their identity using a terminal (101) when signing up for Mobidac (100), and since it is unusual to steal or borrow someone else's cell phone, there is a high probability that receiving treatment under someone else's name by entering someone else's information on the treatment application form can be prevented. In other words, the expected effect is that the person receiving treatment at the hospital can be verified through the verification of a Mobidac member.

[0072] Furthermore, the likelihood of hospital staff or any other third party viewing or obtaining a patient's medical treatment application is low. This is because information is directly entered into the encrypted EMR (220) database via the device (100) terminal (103) and the hospital client. This significantly reduces the risk of personal information leakage.

[0073] In addition, - apart from the preservation of medical records for a certain period of time under the Medical Act - if a patient wants the hospital (200) to delete his / her personal information, there is no need for the patient to call or visit the hospital (200) and request deletion of the personal information. The request to destroy the patient's personal information at the hospital (200) is made to the hospital client of the hospital (200) through Mobidac (100), and since appropriate processing that does not violate relevant laws can be electronically processed between systems, it is advantageous in terms of convenience, security, and guaranteeing the right to self-determination of information.

[0074] Figure 3 is referenced to explain the process of receiving treatment according to an embodiment and the advantages thereof.

[0075] In the waiting room of a hospital (300) depicted in Figure 3, a patient (310) sits comfortably in a chair and registers for treatment using his or her terminal (311). As experienced during the COVID-19 pandemic, hospitals are inherently more susceptible to the spread of infectious diseases than other places. Therefore, face-to-face interactions between hospital staff and patients at the reception desk can be minimized through this Mobidoc service. Close contact with others, such as patients lining up at the reception desk or filling out their individual treatment forms in close proximity to others at a single reception desk, can also be relatively reduced. This provides hygienic advantages and helps with quarantine management. Since the Mobidoc service allows patients to pay hospital bills during or after treatment using a payment method registered with Mobidoc, contact with others, other than face-to-face interaction with the doctor, can be minimized.

[0076] When a patient (310) visits the hospital (300) for the first time and registers for a first visit, he / she takes a picture of the QR code with his / her terminal (311) as described in FIG. 2 (or includes other alternative means such as NFC tag recognition or direct input, hereinafter the same), and then sits comfortably to proceed with the registration process. If he / she is an existing Mobidoc user with the Mobidoc app installed, the Mobidoc app may be called and executed, otherwise, he / she enters the treatment registration menu based on the mobile web. During this process, he / she may be recommended to sign up for Mobidoc and register, or he / she may be recommended to install the Mobidoc app (patient client) and install the app. The process for registering for a first visit will be described in more detail later.

[0077] This allows patients to self-register and (unless there are any issues with the information entered) minimizes staff intervention, thereby improving hospital staff efficiency. Even a single reduction in hospital staff can improve hospital management and allow hospital resources to be more focused on patient care.

[0078] Also, as described above with reference to Figure 2, the first-time visit registration items, which have many items and take relatively long to fill out compared to the re-visit registration, are calmly identified, and only those that are pulled from the Mobidac service and provided to the hospital are agreed upon, and the necessary information (which is not registered in the Mobidac service and therefore needs to be filled out on site) can be entered on the patient's own terminal, making the reception process simpler, faster, and eliminating input errors.

[0079] The re-admission registration process is simpler. Patients who have previously visited the hospital can register for a re-admission through the app or website, by scanning the QR code provided at the hospital, rather than waiting in line. For conditions previously treated at the hospital, registration can be processed simply by confirming that the visit is for that condition. If a patient is registered but receiving treatment for a different symptom, the symptoms can be entered separately. As mentioned earlier, while a re-admission is considered a re-admission to the hospital, both Mobidac members and non-members can register for a re-admission through the above-described method.

[0080] Instead of multiple patients having to register sequentially at the administrative desk, each patient can register in parallel using their individual smartphones. This will improve hospital workflow efficiency and allow Mobidoc to automatically generate patient medical records upon registration. Furthermore, as described below, the input information will be directly linked to electronic charting, enabling the registration details to be confirmed on the physician's terminal, all while being automated.

[0081] Initiation of medical reception and automatic distinction between first and second visits

[0082] Figure 4 provides reference to the medical treatment reception process and the classification processing for first-time and re-visit patients according to an exemplary embodiment. As previously mentioned, when an individual is identified on the application form screen (410) during the medical treatment reception process, whether the patient is requesting a re-visit or a first-time visit is automatically identified at the hospital. If the patient is logged into the Mobidac patient client, the individual may also be automatically identified.

[0083] In some cases, multiple family members may register for treatment together through a single Mobidac patient client. For example, a child and a parent may register separately at the same hospital. The child member is registered as a family member in the parent's Mobidac app, and during this process, the child member or a family member can be selected. In this case, instead of repeatedly scanning the QR code (211) of the hospital (200), the QR code is scanned once and additional patients can be registered through [Add Treatment Subject]. This is another advantage of Mobidac. If the patient identifier was generated on the patient terminal and then scanned by the hospital reader for registration, the patient identifier would have to be changed and the QR code identified multiple times. However, with the Mobidac app, since there is only one hospital (200) and multiple patients, the hospital (200) is identified only once and multiple patients can be registered. Mobidac can manage the Mobidac membership system as a family unit in this way.

[0084] Once the patient is identified on screen (410), the Mobidoc client can determine whether the patient is a repeat visitor or a first-time visitor. If the distinction is inaccurate, the patient and / or hospital staff can correct the distinction. If the patient is a repeat visitor, the patient can simply enter symptoms and skip filling out the first-time questionnaire, and proceed directly to the registration process. If the patient is identified as a first-time visitor, the patient can proceed to the symptom entry process after completing the terms and conditions agreement and personal information handling agreement screen (420).

[0085] Symptom input screen

[0086] Figure 5 illustrates the process of recording symptoms during a medical registration process according to an exemplary embodiment. While this process may be omitted for some repeat visits, both first-time and repeat visits can receive responses to the symptoms that are the cause of the current registration process through screens (e.g., 510, 520, 530) illustrated as examples. These screens may be configured differently depending on the hospital, department, or the intent of the treating physician. As described above, once the symptom entry process in Figure 5 is completed, repeat patients can proceed directly to steps 710 to 730 in Figure 7, thereby completing the registration process.

[0087] For first-time patients, a first-time examination questionnaire is completed.

[0088] Initial examination questionnaire

[0089] FIG. 6 illustrates exemplary items (610, 620, 630, 640, 650) of a first-time visit questionnaire provided to a first-time visit patient according to one embodiment.

[0090] Mobidac TM Mobidoc provides hospitals with templates for initial visit registration and questionnaires. Standard templates can be provided by default, differentiated by each hospital's department. Additionally, additional options for hospital marketing and other necessary aspects of hospital management can be selected / added. If the hospital requires new initial visit registration items that are not included in existing Mobidoc information, these can be tagged as unique information for the hospital and processed separately. Mobidoc will then be able to process these items separately. TM You can verify this information and add it to the standard template items as needed.

[0091] In one embodiment, this can be optionally implemented. If a patient (user) registered with Mobidac changes their personal information (e.g., address, phone number), medication information, etc., Mobidac can provide updated information to other Mobidac-affiliated hospitals that have registered the patient with the patient's consent. Therefore, patients can update their information without having to repeatedly provide or modify information to the hospital where they are receiving treatment. Of course, since this information is shared with the patient's consent, if a hospital requests that the patient retrieve their personal information, Mobidac can assist in its disposal in accordance with relevant laws and hospital policies (making personal information processing easier). This can satisfy both hospitals and patients, and help ensure compliance with the Personal Information Protection Act and other medical laws and regulations.

[0092] Figure 7 illustrates the process of completing a medical treatment application. If you need to upload the image data you brought, you can do so at step (710). Once completed, you can wait for a response from the hospital client through the "Awaiting Completion of Medical Treatment Application" step (720) and / or for confirmation of the completion of information registration in the hospital EMR. Upon completion of this process, you will receive a notification (730) indicating that your medical treatment application has been completed, and the process will proceed as if you had previously completed a hospital treatment application.

[0093] Integration of EMR charts with Mobidac or assistance with chart input

[0094] Figure 8 is a diagram illustrating a procedure for linking medical reception with an EMR chart according to one embodiment. As illustrated, items requested by a hospital for patients visiting the hospital during the medical reception process can be provided as a basic template (800). According to one embodiment, this template may include a hospital chart format. Chart formats are typically managed and processed by physicians using the identifiers below when creating charts.

[0095] CC: Main symptoms

[0096] PI: Troops

[0097] PMHx: Past history

[0098] Drug Hx: medication taken

[0099] FHx: Family history

[0100] If these chart-required items are received electronically from patients via Mobidoc at the time of admission, the physician's charting workload can be reduced. By saving time on charting, physicians can focus more on observing patients and providing treatment, which is expected to improve the quality of care. The chart format codes (811), questions patients can understand (812), and patient responses (813) are all recorded in chart format.

[0101] The chart format at the time of such treatment reception can be directly entered into the EMR chart in some embodiments, but if automatic entry is not desired, in other embodiments, when the doctor checks the contents and selects the 'Copy Chart' button (820) at the bottom, the contents are copied to the clipboard, and can be conveniently pasted with Ctrl+V when charting in the EMR later.

[0102] According to another embodiment, when the 'Copy Chart' button (820) is pressed, the contents of the chart format can be edited in natural language and entered into charting.

[0103] For example, "CC: Visited with back pain since last night. PI: Symptoms since last night. Pain intensity is 5 points. Drug Hx: Taking antihypertensive medication. PMHx: High blood pressure, liver disease" is processed into sentences like this and inserted into the chart.

[0104] Providing and editing a first-time visit template

[0105] Figure 9 illustrates a screen (900) for providing and editing a first-visit reception template according to one embodiment. The provided templates are accessed through the "Questionnaire Template" tab (901). Standard templates may be provided by default, differentiated by each hospital department. Additionally, additional options, such as marketing, may be selected / added for future hospital management.

[0106] If the items required by the hospital for the first visit application are new items not included in the existing Mobidac information, they can be tagged as unique information of the hospital and processed separately, and later, Mobidac TM You can review this information and add it to your advice template items as needed.

[0107] These items may be arranged as a list of codes (911) and questions (910) for the pre-required electronic chart format, as described above with reference to FIG. 8.

[0108] Figure 10 illustrates an exemplary screen (1000) of the basic template editing process.

[0109] In the illustrated exemplary screen, the question (1010) is configured with the type of question and the multiple choice answers that the patient can choose. In the chart format selection section (1011), the editor can select a chart format from an already created questionnaire or select PI, PMHx, Drug Hx, and FHx when adding a question item. Unlike other codes, in the case of CC (chief symptom), it is not entered only in the initial examination questionnaire during the process, but must be entered by all patients regardless of whether they are first-time or second-time patients when receiving treatment, and this may not constitute a separate initial examination questionnaire template. Therefore, CC is omitted from the 'chart format' selection list in the illustrated exemplary configuration.

[0110] When selecting to add a questionnaire (1020) and previewing the initial consultation questionnaire reflecting the editing results (1031), a screen similar to that in Fig. 9 is previewed. After editing is completed, the template can be saved (1032).

[0111] This allows member hospitals to edit their own initial visit registration templates and use their own customized initial visit application forms. This process allows for the addition or deletion of items, changes to specific wording, and even allows for design changes. Once hospitals have edited and saved their templates, they can be managed separately and shared for future use by the hospital or other hospitals.

[0112] Initial Reception Template Trading Ecosystem (Market)

[0113] Mobidac TM While supporting hospital operations and management, it also provides a healthy ecosystem for synergy among hospital members. The aforementioned initial admission questionnaire items are owned by the hospital that created them and, with the hospital's consent, can be shared and traded with other hospitals within the Mobidac platform. The Mobidac Market can be utilized for these transactions.

[0114] Hospitals, especially those based on regional healthcare, may compete with each other based on regional and departmental differences, but fundamentally, they can create healthy synergy. Mobidac provides management and system support to its member hospitals, reducing personnel and external solution adoption costs. Therefore, sharing and trading hospital forms can benefit hospitals' operations.

[0115] Various incentives and benefits can be offered to hospitals that provide quality templates. For example, hospitals that provide the original templates, or hospitals that use the templates with the consent of the hospitals using the templates, can be exposed to their customers.

[0116] Inter-hospital VoC sharing

[0117] Mobidac TM The treatment reception and treatment details through this service may be shared and utilized in cases where the patient transfers to another hospital (transfers) and receives treatment, within the framework of compliance with the Medical Service Act and the Personal Information Protection Act, and with the patient's consent.

[0118] While transfers can be made within the same department or between departments with a less direct connection, they can be shared between identical or similar departments for the sake of patient care. Examples of shared information include factors that contribute to the patient's satisfaction with the hospital's services, factors that contribute to their dissatisfaction, factors that the patient considers important about the hospital, evaluations of the Mobidac user experience, feedback based on the user experience (CX) of the hospital, and information on side effects of medications prescribed during previous visits. This information is shared with the Mobidac affiliated hospital when the patient next registers for treatment, allowing the hospital to obtain useful information for patient care and improve the efficiency and completeness of treatment. Now, Mobidac ensures consistency in patients' lives and enhances the connectivity between patients and medical services.

[0119] Providing statistical information on medical treatment reception

[0120] Figure 11 illustrates a statistical screen (1100) of the results of medical treatment reception according to an embodiment.

[0121] Accessed through the Response Statistics tab (1101). These statistical results can serve as reference data for hospital management. Essentially, the hospital receives statistical information on its admitted patients.

[0122] However, depending on the embodiment, statistical data may be provided to Mobidac affiliated hospitals as long as it does not violate relevant laws, such as anonymization of patient information.

[0123] This information can be processed and provided as data that can be used by government agencies, such as health authorities, the National Health Insurance Service, and the Health Insurance Review & Assessment Service, to establish health information, enabling hospitals to gain insights into improving the quality of care for patients in the future, similar to the use of medical big data.

[0124] Furthermore, since it can be utilized in designing insurance products for private health insurance, the Mobidac initial consultation process can contribute to big data with various uses in the future.

[0125] Individual response lists can also be accessed through the Response List tab (1201). Figure 12 illustrates input data output (1200) for first-time patients who have registered for treatment according to one embodiment. This data is provided only to patients (1211) who have registered at the hospital and can be appropriately anonymized / de-identified as needed. By verifying responses to questions (1212), hospital managers can continuously hear the voices of their patients, thereby improving hospital management and medical quality.

[0126] The devices described above may be implemented as hardware components, software components, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used singly; however, those skilled in the art will appreciate that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors, or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are also possible.

[0127] Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may, independently or collectively, command the processing device. The software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave, for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0128] The method according to the embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc., alone or in combination. The program commands recorded on the medium may be those specially designed and configured for the embodiment or may be those known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program commands, such as ROMs, RAMs, and flash memories. Examples of the program commands include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiment, and vice versa.

[0129] Although the embodiments have been described with limited drawings, those skilled in the art will recognize that various modifications and variations can be made based on the above teachings. For example, suitable results can still be achieved if the described techniques are performed in a different order than described, and / or if the components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or if they are replaced or substituted with other components or equivalents.

[0130] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims described below.

Claims

1. In the computer implementation method, In response to the identification of a unique identifier of the hospital on the terminal of a patient visiting the hospital, a step of initiating a treatment reception interface for the hospital on the terminal of the patient; and A step of providing the patient's information corresponding to at least one item required by the hospital to a hospital client associated with the hospital. A computer implemented method comprising:

2. In paragraph 1 A computer-implemented method for extracting at least one item required by the hospital, which is contained in the patient information stored in the database, and providing it to the hospital client even without input from the patient terminal.

3. In paragraph 1, A computer-implemented method for initiating the medical treatment reception interface based on a temporarily generated web page when the patient terminal is an unidentified terminal in the pre-stored subscriber information, and reusing information entered on the web page in the procedure for the patient to register the subscriber information.

4. In paragraph 1, A computer-implemented method for providing a plurality of questionnaire templates to the hospital client, and utilizing a first template selected by the hospital client as the at least one item required by the hospital.

5. In paragraph 4, A computer-implemented method for providing an editing interface that allows the hospital client to edit at least one of the questionnaire items, arrangement order, and design layout included in the first template.

6. In paragraph 4 A computer-implemented method, wherein at least one item of the first template is provided by matching a question code in an electronic chart of an electronic medical record (EMR) of the hospital.

7. In paragraph 6 A computer-implemented method further comprising the step of copying response information for at least one item to the electronic medical record by associating the question code with the response information.

8. In paragraph 1, A computer-implemented method for updating information entered into the disclosed above-mentioned medical reception interface by reflecting it in the patient information stored in the database.

9. In paragraph 8, A computer-implemented method for providing the results of the above update to a second hospital client of a different hospital from the above hospital.

10. In paragraph 1, A computer-implemented method further comprising the step of transmitting a deletion request to the hospital client in response to a request for deletion of information in the hospital client of the hospital from the terminal of the patient.

11. A non-transitory computer-readable storage medium containing instructions for performing the method of any one of claims 1 to 10.

12. One or more processors; A communication interface operatively coupled to the one or more processors to provide communication with the medical institution client and the terminal of the receiver; and Storage unit that stores the above CRM content An electronic device comprising: a processor configured to perform a method according to any one of claims 1 to 10.

Images