Apparatus and method for providing user-customized medical information
The method and apparatus for hospital CRM systems generate and deliver customized content based on patient-specific information, addressing the uniformity issue in existing systems by providing personalized medical information, enhancing patient engagement and adherence to medical recommendations.
Patent Information
- Application Number
- PCT/KR2024/006438
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-05-10
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
Existing hospital CRM systems provide uniform information to patients, failing to account for individual patient situations, diseases, family history, and specific needs, leading to a lack of personalized communication and reduced patient engagement.
A method and apparatus that utilize a processor to generate, sort, and deliver customized CRM content based on medical information from databases, user terminals, and doctor terminals, matching content with user-specific information such as examination data, family details, location, and medical events to provide timely and relevant information to patients.
This approach ensures that patients receive personalized medical information tailored to their specific needs, improving patient engagement, satisfaction, and adherence to medical recommendations by providing relevant health checkup guidance and disease management advice.
Smart Images

Figure KR2024006438_21112024_PF_FP_ABST
Abstract
Description
Device and method for providing customized medical information
[0001] Hereinafter, a technology for providing customized medical information to users is disclosed.
[0002] CRM (customer relationship management) is the practice of managing customer communication and implementing personalized marketing. Specifically, hospitals actively communicate with patients, collect their inquiries, requests, and complaints, and use this information for patient management. Hospitals also use CRM as a management tool to enhance patient satisfaction through personalized communication, and further increase patient visit and return rates.
[0003] These CRMs can operate on tools or systems that enable hospitals to communicate with each other. In many cases, one-time, one-time CRM services are still provided, with hospital staff calling patients at appropriate times, sending SMS / MMS text messages, app-based instant messaging, or push messages. Therefore, rather than providing CRM to patients uniformly, a technology is needed that automatically provides a more personalized CRM to each patient, taking into account their specific circumstances, medical conditions, family history, and other factors.
[0004] The background technology described above is technology that the inventor possessed or acquired in the process of deriving the disclosure of the present application, and cannot necessarily be said to be publicly known technology disclosed to the general public prior to the present application.
[0005] A method for providing customized hospital customer relationship management (CRM) content performed by a processor according to one embodiment may include: generating a plurality of CRM contents corresponding to medical information received from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal; arranging the generated plurality of CRM contents in chronological order; selecting a target CRM content from the at least one CRM content in response to at least one CRM content among the aligned plurality of CRM contents matching user medical information including at least one of examination information, family information, and location information about the user; and rearranging the plurality of CRM contents so that the selected target CRM content is exposed first, and providing the rearranged CRM contents to the user terminal.
[0006] The step of selecting the target CRM content may include a step of selecting CRM content corresponding to at least one of seasonal disease information and specific period epidemic disease information as the target CRM content in response to matching time information corresponding to the time at which a request for providing CRM content is received from the user terminal and predetermined time information corresponding to the expected time at which a medical event related to the user medical information is expected to occur.
[0007] The step of selecting the target CRM content may include a step of selecting CRM content indicating the user's need to visit the target hospital as the target CRM content in response to matching time information corresponding to the time at which a request for providing CRM content is received from the user terminal and reservation time information corresponding to the user's scheduled time for a checkup at the target hospital.
[0008] The step of selecting the target CRM content may include a step of selecting CRM content corresponding to epidemic disease information within the occurrence area as the target CRM content in response to the location information received from the user terminal and the predetermined area information corresponding to the occurrence area of the medical event being within a predetermined threshold range.
[0009] The step of selecting the target CRM content may include a step of selecting CRM content that guides whether a health checkup is necessary for the user as the target CRM content, based on the health checkup information for the user at the time when a request for providing CRM content is received from the user terminal.
[0010] The step of selecting the target CRM content may include a step of selecting CRM content including necessary examination items for a predetermined age group as the target CRM content in response to at least one of the plurality of CRM contents matching age information of a family member of the user among the family information at the time a request for providing CRM content is received from the user terminal.
[0011] The step of selecting the target CRM content may include a step of selecting the target CRM content based on the number of times the user accesses medical information, including at least one of the number of visits to the target hospital, the number of searches for the target hospital, and the number of searches for a specific disease.
[0012] The step of selecting the target CRM content may include a step of selecting the target CRM content based on a comparison result between the user's body information at the time when a request for providing CRM content is received from the user terminal and the user's initial body information received from the user terminal.
[0013] According to one embodiment, a device for providing customized hospital customer relationship management (CRM) content may include a communication unit that receives medical information from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal; and a processor that generates a plurality of CRM contents corresponding to the medical information, arranges the generated plurality of CRM contents in chronological order, and selects a target CRM content based on a matching result between each of the arranged plurality of CRM contents and user medical information including examination information, family information, and location information about the user, and rearranges the selected target CRM content so that it is first exposed among the plurality of CRM contents, and provides the rearranged CRM contents to the user terminal.
[0014] Figure 1 is a drawing for explaining the connection between a CRM content provision device and a user terminal, a doctor terminal, a hospital terminal, and a medical database.
[0015] FIG. 2 illustrates a CRM content providing device according to one embodiment.
[0016] FIGS. 3A and 3B are drawings for explaining how CRM contents provided to a user terminal by a CRM contents provision device according to one embodiment are displayed on the user terminal.
[0017] FIGS. 4A to 4E are diagrams illustrating a CRM content providing device according to one embodiment providing CRM content to a user terminal based on a relationship with the user or the occurrence of a medical event related to the user.
[0018] Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified and implemented in various forms. Therefore, the actual implementation is not limited to the specific embodiments disclosed, and the scope of this specification includes modifications, equivalents, or alternatives within the technical concepts described in the embodiments.
[0019] Although terms such as "first" or "second" may be used to describe various components, these terms should be interpreted solely to distinguish one component from another. For example, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.
[0020] When it is said that a component is "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but there may also be other components in between.
[0021] Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises" or "has" should be understood to indicate the presence of a described feature, number, step, operation, component, part, or combination thereof, but not to exclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0022] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art. Terms defined in commonly used dictionaries should be interpreted to have a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.
[0023] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are assigned the same reference numerals regardless of the drawing numbers, and redundant descriptions thereof will be omitted.
[0024]
[0025] FIG. 1 is a diagram illustrating the connection between a CRM content provision device (100) (hereinafter, “device”), a user terminal (101), a doctor terminal (102), a hospital terminal (103), and a medical database (104). The user terminal (101) may include a terminal of a patient visiting a hospital, a terminal of a patient examined through non-face-to-face treatment, a terminal of a patient scheduled to visit a hospital, etc. The doctor terminal (102) and the hospital terminal (103) may represent examples of terminals belonging to a medical institution. The medical database (104) may represent, for example, a medical database about users stored in the National Health Insurance Corporation.
[0026] The device (100) may be implemented by a server-class computer, workstation, desktop computer, laptop computer, mobile electronic device, etc., and may also be implemented by multiple devices among these. Each of the terminals (101, 102, 103) may execute software, conveniently referred to as a "client."
[0027] A patient client may be executed on a user terminal (101). A doctor client may be executed on a doctor terminal (102), and a hospital client may be executed on a hospital terminal (103). The doctor client, which corresponds to a count portion of the user client, may represent software installed in a hospital. The client may include an online cloud service in the form of Software as a Service (SaaS). In this case, the doctor client may represent 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 may include software that allows hospital administrative staff or nurses, rather than the medical professional (doctor) performing the treatment, to perform treatment assistance tasks such as receiving treatment and collecting hospital fees. The doctor client used by doctors and the hospital client 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. For example, some disabled functions may represent functions that only doctors should perform, such as "remote consultation." Since the doctor can determine the most accurate and appropriate time to begin consultation with the next patient, the "Start Consultation" function for patient clients waiting in the examination room and those waiting for non-face-to-face consultation via video conferencing can be implemented as a function that only doctors can perform. The examples described above are merely a few examples of doctor clients and hospital clients and are not limiting.
[0028] The client installed on terminals (101, 102, 103) may be an original application software installed, a service provided through a page accessed via a web-based browser, or a hybrid app with both app and web features. Furthermore, it may be a cloud-based service provided in the form of SaaS. The above-described client embodiments do not exclude other implementations.
[0029] The device (100) can receive medical information from terminals (101, 102, 103) and a medical database (104). Based on the received medical information, the device (100) can generate customer relationship management (CRM) content corresponding to the medical information. For example, the CRM content can be information displayed on the displays of the terminals (101, 102, 103) in the form of cards. The device (100) can rearrange the CRM content based on the medical information of the user to be more customized for the user and provide it to the user terminal (101). The implementation and operation of the device (100) are described in detail in FIG. 2.
[0030] Figure 2 illustrates a CRM content providing device (200) (hereinafter, "device") according to one embodiment. The device (200) can generate multiple CRM contents to be provided in card form on a user's terminal based on medical information. The device (200) rearranges the multiple CRM contents based on the relationship with the user so that necessary information is displayed at the top of the user terminal, thereby providing more customized medical information to the user. Note that the medical information required or of interest may vary for each user. For example, a user with a child in the family may require medical information related to the child's vaccination. For another example, a user with cancer may require medical information related to cancer treatment. For yet another example, an obese user may require medical information related to obesity treatment, such as hypertension, diet control, and diabetes. Therefore, a device is needed to provide more customized medical information to each user. Accordingly, based on the device (200), CRM contents corresponding to medical information suitable for the user can be provided to the user terminal.
[0031] A device (200) according to one embodiment may include at least one communication unit (210) and a processor (220). The device (200) may be connected to a user terminal and a medical institution (e.g., a doctor, a hospital, or a National Health Insurance Service) terminal through the communication unit (210), and may provide a service of transmitting CRM content from a client of a medical institution terminal to a patient terminal.
[0032] Specifically, the communication unit (210) can receive medical information from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal.
[0033] The medical database may include the National Health Insurance Service database. For example, the medical database may store data on patient treatment, treatment and medication information, screening subjects, and health checkup results stored in the National Health Insurance Service database. Specifically, treatment details may include patient name, National Health Insurance Service co-payment, out-of-pocket expenses, number of medication days, number of hospital visits (hospitalization) days, number of prescriptions, type of treatment, start date, and hospital (pharmacy) name. Treatment and medication information may include category, medication details array, number of medication (treatment) days, number of prescriptions, number of hospital visits (hospitalization) days, type of treatment, start date, and hospital (pharmacy) name. Screening subjects may include information on cancer screening lists, public health centers, confirmatory tests, general screenings, hepatitis B tests, oral screenings, screening year, patient date of birth, and name. Health checkup results may include information on screening subjects, reference value lists, results lists, and at-a-glance lists.
[0034] Medical information received from a user terminal can correspond to medical information entered by the user into the client application of the user terminal. For example, when signing up for an application installed on the user terminal, the user may enter information such as gender, physical information, family relationships, family history, current symptoms, medication types, and health information of interest. The user can enter relevant medical information by selecting relevant items provided by the application or by entering the information directly.
[0035] Medical information received from a hospital terminal may correspond to medical information entered by staff, excluding doctors, at the hospital where the user was diagnosed or is scheduled to be diagnosed, or at a nearby hospital based on the user's location information. For example, this may include the user's hospital visit history and appointment information.
[0036] Medical information received from the doctor's terminal may correspond to medical information including charts, prescriptions, etc. written by a doctor who performed face-to-face and / or non-face-to-face treatment on the user and completed the treatment for the user.
[0037] In other words, the communication unit (210) can receive the medical information exemplified above from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal. However, the medical information exemplified above is merely an example and is not limited thereto.
[0038] The processor (220) may generate a plurality of CRM contents corresponding to the medical information received via the communication unit (210). For example, the processor (220) may generate card-type CRM contents corresponding to the hospital based on the medical information received from the hospital terminal. For example, the card-type CRM contents corresponding to the hospital may include information indicating the doctor affiliated with the hospital, the doctor's treatment field, whether the doctor is a specialist, whether the patient is receiving treatment, etc. For example, the processor (220) may generate card-type CRM contents including QR code information for registering at the hospital based on the medical information received from the hospital terminal. In another example, if the medical information received from the user terminal includes a child among the user's family, the processor (220) may generate CRM contents related to information related to medical services to be provided to the child. For example, if the medical information received from the user terminal includes information on the child's age, the processor (220) may generate CRM contents corresponding to information related to vaccinations required for the child's age.
[0039] The processor (220) may sort the generated plurality of CRM contents in chronological order. For example, the processor (220) may sort the corresponding plurality of CRM contents in chronological order based on the time at which medical information received from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal was created (or, input, created). For example, if the processor (220) first generates the first hospital CRM contents related to internal medicine treatment and later generates the second hospital CRM contents related to pediatric treatment, the processor (220) may arrange the second hospital CRM contents that were most recently generated to be placed first and the first hospital CRM contents that were previously generated to be placed last.
[0040] The processor (220) may select a target CRM content from at least one CRM content in response to at least one CRM content matching the user's medical information, which includes at least one of examination information, family information, and location information, among a plurality of aligned CRM contents. For example, the examination information for the user may include the results of a health examination for the user. The family information for the user may include information on the age of children in the user's family, the ages of the user's parents, whether there is a family history, whether there is a genetic disease carrier in the family, etc. The location information may indicate information corresponding to the user's current location or current residence. The processor (220) may select a target CRM content in response to the user's medical information, which includes at least one of examination information, family information, and location information, matching the at least one CRM content at the time a request for providing CRM content is received from the user terminal. In other words, the processor (220) may select the CRM content most relevant to the current user as the target content from among the plurality of CRM contents for the user. For example, if the user has a pollen allergy and the current time is a pollen allergy season, the processor (220) may select CRM content including information about hospitals or management methods related to pollen allergy as the target CRM content.
[0041] The processor (220) can rearrange multiple CRM contents so that the selected target CRM content is exposed to the user terminal first among the multiple CRM contents, and provide the rearranged CRM contents to the user terminal via the communication unit (210). In other words, the user terminal can display multiple CRM contents rearranged by the processor (220), and the multiple CRM contents can include medical information most needed by the current user. In other words, the device (200) can provide customized CRM contents to the user.
[0042]
[0043] FIGS. 3A and 3B are drawings for explaining how CRM contents provided to a user terminal by a CRM contents provision device according to one embodiment are displayed on the user terminal.
[0044] In FIG. 3A, a user terminal (300) can receive a plurality of aligned CRM contents (310, 320, 330) from a CRM contents providing device. As illustrated in FIG. 3A, the user terminal (300) can display a plurality of CRM contents (310, 320, 330) in card form provided from the CRM contents providing device. For example, the CRM contents providing device can arrange the plurality of CRM contents (310, 320, 330) in chronological order. For example, the CRM contents (310) can represent a UI including reservation information for a specific hospital of the user. For example, the CRM contents (320) can represent a UI including QR code information for registering for treatment at a specific hospital. For example, the CRM contents (330) can represent a UI including information about a specific hospital related to the user, such as where the user received treatment or made a reservation for treatment. The CRM content providing device can provide a plurality of CRM contents (310, 320, 330) to the user terminal (300) by arranging them based on the creation time and / or update time. For example, FIG. 3A illustrates a case where the CRM content (310) is most recently created (or updated) compared to the remaining contents (320, 330) and the CRM content (330) is most recently created (or updated) compared to the remaining contents (310, 320), and the most recently created CRM content (310) is chronologically arranged at the top. Although not illustrated in FIG. 3A, the CRM content providing device can provide the user terminal (300) with CRM contents including specific hospital information related to the user, such as the CRM content (330). In other words, the user terminal (300) can receive CRM contents including information on each of multiple hospitals related to the user from the CRM content providing device.For example, if a user recently received neurosurgery treatment and has a child among his / her family members, the CRM content providing device can provide CRM content corresponding to the neurosurgery hospital where the user received treatment and CRM content corresponding to the pediatric hospital to the user terminal (300). The user terminal (300) can display CRM contents (310, 320, 330) arranged in chronological order provided as the initial screen by the CRM content providing device as a UI. Thereafter, when the user terminal (300) sends a CRM content providing request to the CRM content providing device, or even if the user terminal (300) does not send a provision request, the CRM content providing device can rearrange the CRM contents (310, 320, 330) so that the user-related CRM contents are arranged at the top at predetermined time intervals. A specific rearrangement method will be described below with reference to FIGS. 4a to 4e.
[0045] In FIG. 3b, the user terminal (300) can display multiple sub-item CRM contents within a specific hospital-related CRM content provided by the CRM content providing device. For example, the CRM content providing device can provide multiple hospital-related CRM contents to the user terminal (300). For example, the CRM content providing device can provide CRM contents for hospitals where the user has visited (or made a non-face-to-face treatment, appointment) within the past six months. For example, if the user has visited a first hospital specializing in surgery, a second hospital specializing in internal medicine, and a third hospital specializing in otolaryngology within the past six months, the CRM content providing device can, based on the information, sequentially provide CRM contents for the most recently visited hospital to the user terminal (300). In other words, the CRM content providing device can provide multiple different hospital-related CRM contents to the user terminal (300).
[0046] Furthermore, the CRM content providing device can display multiple sub-item CRM contents within each hospital-related CRM contents. For example, as illustrated in FIG. 3B, the CRM content providing device can provide CRM contents (350) regarding 'Barun Neurosurgery Clinic' to the user terminal (300), and provide sub-CRM contents (361, 371, 381) corresponding to multiple sub-items (360, 370, 380) within the CRM contents (350). For example, the CRM contents (350) regarding 'Barun Neurosurgery Clinic' can include sub-items (360, 370, 380). For example, the sub-item (360) can include sub-item CRM contents (361) corresponding to information about doctors affiliated with 'Barun Neurosurgery Clinic'. At this time, information about doctors belonging to 'Barun Neurosurgery Clinic' may indicate whether the doctors belonging to the clinic are providing treatment or have gone to work, etc. For another example, the sub-item (370) may include sub-CRM content (371) corresponding to medical information (e.g., posts written / posted by the hospital about fracture management methods) created by 'Barun Neurosurgery Clinic' and provided to the CRM content provision device. For another example, the sub-item (380) may include sub-CRM content (371) corresponding to notification information that notifies notices, etc., from 'Barun Neurosurgery Clinic'. In other words, the CRM content provision device may provide CRM content in the form of a parent-subtree to the user terminal (300) so that card-type sub-CRM contents (361, 371, 381) are included within the CRM content (350) for a specific hospital. The user can change the lower CRM contents (361, 371, 381) displayed on the user terminal (300) by touching the area corresponding to the lower items (360, 370, 380) displayed on the user terminal (300) or by dragging in the left and right directions.
[0047]
[0048] FIGS. 4A to 4E are diagrams illustrating a CRM content providing device according to one embodiment providing CRM content to a user terminal based on a relationship with the user or the occurrence of a medical event related to the user.
[0049] FIG. 4A illustrates a CRM content providing device providing CRM content to a user terminal (400a) based on the relationship between the CRM content and the user and / or the current state of a medical event occurring to the user. For example, the CRM content providing device may select CRM content (430) indicating the user's need to visit the target hospital as the target CRM content in response to matching the time information corresponding to the time at which the CRM content providing request is received from the user terminal (400a) with the reservation time information corresponding to the user's scheduled examination time at the target hospital. For example, assume that the user has made a reservation at 'Barun Neurosurgery Clinic' at 3:00 PM on Wednesday, July 17, 2023. In this case, the CRM content providing device may receive a CRM content providing request from the user terminal (400a) on July 17, 2023 (or the day before the reservation). For reference, a request for CRM content provision may include, but is not limited to, cases where a user directly refreshes the application screen in the application or cases where a user starts the application. The CRM content provision device may receive appointment time information corresponding to the time when the user is scheduled to receive a checkup (or treatment) at the target hospital from a hospital terminal or a doctor terminal. The CRM content provision device may match the CRM content provision request time information received from the user terminal (400a) with appointment time information at the target hospital. In response to the matching, the CRM content provision device may select CRM content (430) indicating the user's need to visit the target hospital (e.g., the user has an appointment on July 17, 2023, so he needs to visit the hospital, or the user has a regular checkup appointment on July 17, 2023, so he needs to visit the hospital) as the target CRM content.For example, if a CRM content providing device receives a request for CRM content provision from a user terminal (400a) on the 'same day of the reservation' at the target hospital, as illustrated in FIG. 4a, the CRM content (430) indicating 'the same day of the reservation' may be selected as the target CRM content and provided so that it is displayed at the top of the user terminal (400a). As another example, if a CRM content providing device receives a request for CRM content provision from a user terminal (400a) on the 'one day before the reservation' at the target hospital, the CRM content indicating 'the one day before the reservation' may be selected as the target CRM content and provided so that it is displayed at the top of the user terminal (400a). That is, when the user's hospital reservation schedule or regular checkup schedule approaches, the CRM content providing device may display the corresponding information at the top of the user terminal (400a) or guide it as a pop-up so that the user does not forget.
[0050] For another example, the CRM content providing device may select target CRM content based on the number of times the user accesses medical information, including at least one of the number of visits to the target hospital, the number of searches for the target hospital, and the number of searches for a specific disease. For example, assume that the user has searched for a disk more than a predetermined number of times. The CRM content providing device may select CRM content (420) containing disk-related information for the current user as the target CRM content based on the number of disk searches by the user. For example, assume that the user has searched for neuralgia (or neurosurgery) more than a predetermined number of times, the CRM content providing device may display CRM content (410) containing neurosurgery-related information at the top of the user terminal (400a) or guide the current user to it through a pop-up based on the number of searches for neuralgia (or neurosurgery) by the user.
[0051] FIG. 4b is a diagram illustrating a CRM content providing device that provides relevant medical information to a user based on the user's family information.
[0052] A CRM content provision device according to one embodiment may select, as the target CRM content, a CRM content including necessary examination items for a predetermined age group in response to at least one of a plurality of CRM contents matching age information of a family member of the user among family information at the time a CRM content provision request is received from a user terminal.
[0053] For example, a user's family may include members of various ages, such as preschoolers, seniors, and adolescents. Therefore, the tests or diagnostic items required for each age group may vary, making it necessary to provide CRM content that reflects medical information appropriate for each age group.
[0054] For example, suppose that one of the user's family members is elderly and is about to undergo a health checkup. When the CRM content provision device receives a CRM content provision request from the user terminal (400b), the CRM content provision device can match the age information of the elderly family member with the CRM content. For example, since osteoporosis tests may be required periodically for those over 60 years of age, the CRM content provision device can select CRM content that includes osteoporosis screening items as a necessary checkup item for those in their 60s as the target CRM content. For another example, health checkups for the elderly, such as elderly physical function tests, may be recommended for those in their 66s, 70s, and 80s. Accordingly, if the user's parents are in an age group that requires elderly physical function tests, the CRM content provision device can select CRM content (440) that includes necessary checkup items for predetermined age groups (e.g., 66, 70, and 80s) as the target content and place it at the top of the user terminal (400b).
[0055] For another example, assume that one of the user's family members is a child. If the CRM content providing device receives a CRM content provision request from the user terminal (400e), and the child is 2 years old, the device may select CRM content (470) containing information on developmental tests as the target content and provide it to the user terminal (400e). The CRM content providing device, based on the family member's age information, may select CRM contents (440, 470) containing necessary examination items for the corresponding age group, but is not limited thereto.
[0056] FIG. 4c is a diagram for explaining a CRM content providing device that provides relevant medical information to a user based on the user's location information.
[0057] Depending on the geographic, climatic, and social factors of a specific region, epidemics can occur within that region. For example, influenza and food poisoning can be prevalent in a specific area. Therefore, technology is needed to provide users with medical information on diseases to watch out for and response measures based on their location.
[0058] According to one embodiment, a CRM content providing device may select CRM content (450) corresponding to epidemic disease information within an outbreak area as target CRM content in response to the location information received from a user terminal (400c) and predetermined area information corresponding to an outbreak area of a medical event being within a predetermined threshold range. For example, the location information received from the user terminal (400c) may include the user's residence, the user's current location, and the user's workplace location. The location information may be directly input by the user into the user terminal (400c) and transmitted to a CRM content storage device, or may be acquired based on the user terminal's (400c) own GPS, etc. For example, if an influenza outbreak caused by an influenza virus has occurred in a specific area, the CRM content providing device may compare the distance between the user's current location information and an outbreak area where the influenza is prevalent. In response to the distance between the user's current location information and the influenza outbreak area being within a predetermined threshold range, the CRM content providing device may select CRM content (450) corresponding to the influenza epidemic as the target CRM content and provide the content to the user terminal (400c). In another example, in response to the distance between the user's current residence information and the influenza outbreak area being within a predetermined threshold range, the CRM content providing device may select CRM content (450) including a preventive method for the influenza epidemic as the target CRM content.
[0059] FIG. 4d is a diagram illustrating a CRM content provision device that provides health check-up-related information so that users do not miss the time to receive a health check-up.
[0060] While users may undergo regular general health checkups, some may opt for personalized screenings based on their underlying medical conditions. For example, individuals with cardiovascular disease or a family history of the condition may undergo regular preventive screenings. In such cases, it's important to provide these users with information about their checkups so they don't miss out.
[0061] According to one embodiment, a CRM content providing device may select, as target CRM content, CRM content (460) that provides guidance on whether a health checkup is necessary for a user based on the health checkup information of the user at the time when a request for providing CRM content is received from a user terminal (400d). For example, if the time when the CRM content providing device receives a request for providing CRM content from the user terminal (400d) corresponds to a time when a user who has been receiving regular cardiovascular disease prevention checkups has not yet received the checkup, the CRM content providing device may select, as target CRM content, CRM content (460) that provides guidance on the need for a cardiovascular disease prevention checkup.
[0062] FIG. 4e is a diagram illustrating a CRM content provision device that provides users with seasonal or epidemic disease information to be aware of depending on the time period.
[0063] Seasonal or epidemic diseases may exist during specific seasons or periods that require attention. For example, norovirus or influenza may be prevalent in January and February, pollen allergies may be prevalent in April during the spring season, and food poisoning may be classified as a seasonal or epidemic disease during the rainy season from May to August. Therefore, it is necessary to provide users with information about specific seasonal or epidemic diseases and to prepare for them.
[0064] According to one embodiment, a CRM content providing device may, in response to matching time information corresponding to a time when a CRM content providing request is received from a user terminal (400f) with predetermined time information corresponding to an expected time of occurrence of a medical event related to user medical information, select CRM content corresponding to at least one of seasonal disease information and specific period epidemic disease information as target CRM content. For example, assume that the time when the CRM content providing device receives a CRM content providing request from the user terminal (400f) is April. In response to matching the time information corresponding to April with predetermined time information (e.g., April) corresponding to an expected time of occurrence of pollen allergy among the user medical information, the CRM content providing device may select CRM content (480) containing instructions to prepare for pollen allergy as target CRM content.
[0065] For another example, assume that a user is diagnosed with tonsillitis consistently in March, corresponding to the yellow dust season. Not all users are diagnosed with tonsillitis in March, but some users may be diagnosed with tonsillitis consistently in March. In this case, it is necessary to warn the user about tonsillitis in March and provide related information. According to one embodiment, a CRM content provision device may, when a request for CRM content provision is received from a user terminal (400f) in March, match the time information with predetermined time information (e.g., March) corresponding to the expected time of tonsillitis diagnosis among the user's medical information, and select CRM content corresponding to user-tailored disease information as the target CRM content.
[0066] Although not illustrated in FIG. 4e, a CRM content providing device according to another embodiment may select target CRM content based on a comparison result between the user's physical information at the time a CRM content providing request is received from the user terminal and the user's initial physical information received from the user terminal. For example, a user may input his / her own physical information during a subscription process to a patient client (e.g., an application) via a user terminal (400f). For example, the user may input his / her own height, weight, BMI, body fat percentage, etc. The CRM content providing device may identify the user's own physical information entered by the user during the subscription process as initial physical information and compare it with the user's physical information at the time a CRM content providing request is received from the user terminal. The user's physical information at the time a CRM content providing request is received may be newly measured or correspond to newly input physical information by the user. The CRM content providing device may select target CRM content based on a comparison result between the initial physical information and the newly measured physical information. For example, if the weight or BMI value of newly measured body information has changed beyond a predetermined threshold range compared to the initial body information, the CRM content providing device can select CRM content related to diet control, joint health, exercise method, etc. as the target CRM content and provide it to the user terminal.
[0067]
[0068] The embodiments described above may be implemented using hardware components, software components, and / or a combination of hardware components and software components. For example, the devices, methods, and components described in the embodiments may be implemented using a general-purpose computer or a special-purpose computer, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), 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 software applications running on the operating system. Furthermore, the processing device may 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 alone; however, one of ordinary skill in the art will recognize that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, a processing unit may include multiple processors, or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.
[0069] Software may include computer programs, codes, 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, or computer storage medium or device 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 a computer-readable recording medium.
[0070] 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, and the program commands recorded on the medium may be those specially designed and configured for the embodiment or may be 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 program commands include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.
[0071] The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.
[0072] In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof.
[0073] Although the embodiments described above have been described with limited drawings, those skilled in the art will appreciate that various technical modifications and variations can be applied based on the described embodiments. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.
[0074] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims described below.
Claims
1. A method for providing customized hospital customer relationship management (CRM) content performed by a processor, A step of generating a plurality of CRM contents corresponding to medical information based on medical information received from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal; A step of arranging the plurality of CRM contents generated above in chronological order; In response to at least one CRM content among the plurality of aligned CRM contents matching user medical information including at least one of examination information, family information, and location information about the user, selecting a target CRM content from the at least one CRM content; and A step of rearranging the selected target CRM content so that it is exposed first among the plurality of CRM contents and providing it to the user terminal. A method of providing CRM content including:
2. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting CRM content corresponding to at least one of seasonal disease information and specific period epidemic disease information as the target CRM content in response to matching time information corresponding to the time at which a request for providing CRM content is received from the user terminal and predetermined time information corresponding to the expected time at which a medical event related to the user medical information is expected to occur. A method of providing CRM content including:
3. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting CRM content indicating the need for the user to visit the target hospital as the target CRM content in response to matching the time information corresponding to the time at which a request for providing CRM content is received from the user terminal and the reservation time information corresponding to the time at which the user is scheduled to have a checkup at the target hospital. A method of providing CRM content including:
4. In paragraph 1, The step of selecting the above target CRM content is: In response to the location information received from the user terminal and the predetermined area information corresponding to the occurrence area of the medical event being within a predetermined threshold range, a step of selecting CRM content corresponding to epidemic disease information within the occurrence area as the target CRM content; A method of providing CRM content including:
5. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting CRM content that guides whether a health checkup is necessary for the user as the target CRM content based on the health checkup information for the user at the time when a request for providing CRM content is received from the user terminal. A method of providing CRM content including:
6. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting CRM content including necessary examination items for a predetermined age group as the target CRM content in response to at least one of the plurality of CRM contents matching the age information of the family member of the user among the family information at the time when a request for providing CRM content is received from the user terminal. A method of providing CRM content including:
7. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting the target CRM content based on the number of medical information accesses including at least one of the number of visits to the target hospital of the user, the number of searches for the target hospital, and the number of searches for a specific disease. A method of providing CRM content including:
8. In paragraph 1, The step of selecting the above target CRM content is: A step of selecting the target CRM content based on a comparison result between the user's body information at the time when a request for providing CRM content is received from the user terminal and the user's initial body information received from the user terminal. A method of providing CRM content including:
9. A computer program stored in a computer-readable recording medium to execute any one of the methods of claims 1 to 8 in combination with hardware.
10. In the device providing customized hospital customer relationship management (CRM) content, A communication unit that receives medical information from at least one of a medical database, a user terminal, a hospital terminal, and a doctor terminal; and A processor that generates a plurality of CRM contents corresponding to the medical information, arranges the generated plurality of CRM contents in chronological order, selects a target CRM content based on a matching result between each of the arranged plurality of CRM contents and user medical information including examination information, family information, and location information for the user, and rearranges the selected target CRM content so that it is exposed first among the plurality of CRM contents, and provides the same to the user terminal. A CRM content delivery device that includes.
Citation Information
Patent Citations
Method And System For Providing Patient Relationship Management Service
KR1020180080863A
Lifetime cash gifts record management and settlement method using blockchain technology
KR1020240155995A
Systems and methods for surgical and interventional planning, support, post-operative follow-up, and functional recovery tracking
US20180344308A1
KR20220071339A
KR20230052616A
