KR101298548B1 - System for managing individual dental history and method thereof - Google Patents

Abstract

PURPOSE: A personal dental medical history management system and a dental medical history management method are provided to manage a dental medical history of individuals by managing a personal dental medical treatment history and identifying material and manufacture applied to dental treatment. CONSTITUTION: An image recognition unit (210) captures a user authentication image by displaying in a user terminal. An authentication data transmission unit (240) transmits the authentication data determined by the authentication image to a dental management server. A first authentication and connection configuration unit authenticates the user terminal through a network. The first authentication and connection configuration unit configures channel connection of the user terminal to the network. A second authentication and connection configuration unit decides permission of access to the dental management server of a medical record system based on the authentication data received from the medical record system. The second authentication and connection configuration unit configures channel connection of the medical treatment information for the user authenticated through the authentication data. An authentication data storage unit (230) stores the authentication data temporarily or for a specific period. [Reference numerals] (210) Image recognition unit; (220) Authentication data determination unit; (230) Authentication data storage unit; (240) Authentication data transmission unit; (250) Channel connection configuration unit; (260) Request receiving unit; (270) Request transmitting and receiving unit; (280) Request display unit

Description

Personal dental history management system and dental history management method {SYSTEM FOR MANAGING INDIVIDUAL DENTAL HISTORY AND METHOD THEREOF}

The present invention relates to a personal dental history management system and a dental history management method, and in particular, to manage the history of the past dental treatment of the individual and to query the treatment history by date by tooth, personal dental history management system and teeth It is about a troop management method.

Teeth are replaced around 12 years of age from primary to permanent teeth and are not replaced afterwards. As a result, individuals need to manage their teeth for life after they are replaced with permanent teeth and receive various treatments related to their teeth.

These treatments are also not permanent and require retreatment or management. If you are receiving retreatment and are receiving treatment at the same dentist, you can use the history history recorded locally at this dentist to determine what treatments you had previously and what treatment you need more. It can be easily determined, but if there is no previous treatment history information, it may be difficult for a doctor to make an accurate diagnosis or plan for treatment.

In particular, treatments applied to teeth include treatment using various metal materials such as gold or silver, or implants provided by a specific manufacturer. For example, in the past, when an implant procedure was performed at another dentist, the treatment may be denied because there is no information about the implant.

Therefore, for the individual, there is a need for a personal dental history management system and a dental history management method to manage the personal history of the dental treatment and to identify the material or manufacturer applied to the dental treatment. In particular, there is a need for a personal dental history management system and a dental history management method to systematically know the treatment history of each tooth by individual tooth and / or date.

On the other hand, such a personal dental history management system and dental history management method may be made using a remote server. Such a server may authenticate an individual and store various treatment related information for the authenticated individual.

And such treatment-related information about the individual needs to be accessible not only to the individual but also to the dentist. Inquiring about the past treatment history of an individual at the dentist will also allow the doctor to make an accurate treatment or procedure.

Inquiries about past treatment histories for specific individuals at the dentist may require an individual's ID or password to log in to the server, which may include someone else's sensitive information (in this case, the dentist). Means exposure to people.

Therefore, in the dentist, it is possible to inquire about the past treatment history of the individual so that accurate dental treatment can be performed, and also prevent limited access to the past treatment history corresponding to the personal information of the individual and unauthorized exposure of ID or password. There is a need for a personal dental history management system and a dental history management method to enable this.

The present invention has been made to solve the above-described problems, and provides a personal dental history management system and a dental history management method for managing the history of dental treatment of individuals and to identify the material or manufacturer applied to the dental treatment Its purpose is to.

In another aspect, the present invention provides a personal dental history management system and a dental history management method that makes it possible to easily manage the teeth by systematically knowing the treatment history of each tooth by individual teeth and / or date. There is a purpose.

In addition, an object of the present invention is to provide a personal dental history management system and a dental history management method for enabling accurate treatment or treatment by allowing the dentist to automatically search the past treatment history of the individual.

It is also an object of the present invention to provide a personal dental history management system and a dental history management method that allows limited access to past treatment histories and prevents unauthorized exposure of authentication information.

Another object of the present invention is to provide a personal dental history management system and a dental history management method for providing various information related to dental treatment.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, unless further departing from the spirit and scope of the invention as defined by the appended claims. It will be possible.

In order to achieve the above object, a personal dental history management method, from the user of the user terminal through a channel connected to the step of authenticating the user terminal over the network and the channel connection on the authenticated user terminal and the network; Receiving an inquiry about the input tooth from the user terminal, processing the received query and transmitting the processed result to the user terminal.

In addition, to achieve the above object, a personal dental history management system includes a dental management server, the dental management server, authentication and connection setting unit for authenticating a user terminal through a network and establishing a channel connection on the network; It includes a query receiving unit for receiving a query about the teeth input from the user of the user terminal through the connected channel from the user terminal, a query processing unit for processing the received query and a result transmission unit for transmitting the processed results to the user terminal.

In addition, to achieve the above object, a personal dental history management method, comprising: authenticating a user terminal through a network; Establishing a channel connection on the network with an authenticated user terminal; Receiving a query from a user terminal about a tooth input from a user of the user terminal through a connected channel; processing the received query; And transmitting the processed result to the user terminal.

In addition, a personal dental history management method for achieving the above object, the dental management server, the step of authenticating the user terminal via a network and establishing a channel connection to the user terminal on the network; Capturing, by the medical recorder, an authentication image for authenticating a user of the authenticated user terminal; Transmitting, by the medical record device, authentication data determined from the captured authentication image to the dental care server; Determining, by the dental care server, whether to allow the medical record device to access the dental care server based on the received authentication data; And setting up a channel connection with the medical recorder so that the medical recorder can access the treatment information for the user, if the dental care server has allowed access.

According to the present invention as described above, the personal dental history management system and the dental history management method, there is an effect to manage the dental treatment history of the individual and easily identify the material or manufacturer applied to the dental treatment.

In addition, the personal dental history management system and the dental history management method according to the present invention as described above, so that you can know the treatment history of each tooth systematically by individual teeth and / or date to easily manage the teeth It is effective.

In addition, the personal dental history management system and the dental history management method according to the present invention as described above, it is possible to automatically search the past treatment history for the individual in the dentist, it is effective to enable accurate treatment or procedures.

In addition, the personal dental history management system and the dental history management method according to the present invention as described above, there is an effect to allow only limited access to the past treatment history and to prevent unauthorized exposure of authentication information.

In addition, the personal dental history management system and the dental history management method according to the present invention as described above, there is an effect to provide a variety of information related to the dental treatment.

The effects obtained by the present invention are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those skilled in the art from the following description will be.

1 is a system block diagram of a personal dental history management system capable of managing teeth of multiple users.
2 is a diagram illustrating an exemplary hardware block diagram of a dental care server and / or a medical recorder.
3 illustrates an exemplary functional block diagram of a dental care server.
4 is a diagram illustrating an exemplary functional block diagram of a medical recorder.
5 is a control flowchart showing a control flow occurring between the user terminal, the medical recorder, and the dental management server.

The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: It can be easily carried out. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a system block diagram of a personal dental history management system capable of managing teeth of multiple users. According to FIG. 1, the personal dental history management system includes one or more user terminals 100, one or more medical recording devices 200, and a dental management server 300. Certain system blocks may be omitted, for example, one or more of the medical recorder 200 may be omitted from the dental medical history management system according to the application thereof to configure the system.

Referring to each system block of FIG. 1 in turn, the user terminal 100 is a portable terminal possessed by an individual who wishes to use the dental history management system. The user terminal 100 may be, for example, a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet PC, or the like. In the following description, the terms "personal" or "user" are used interchangeably as necessary.

The user terminal 100 may access a display, such as an LCD, a mobile phone network and / or a wireless network, such as a touch panel or a keypad, an input interface capable of receiving a user input, and a user interface. It can include a network interface and memory for storing programs.

The user terminal 100 downloads a user dental management program for use in the dental history management system viewed from a specific remote server, stores the program in a memory, and drives the stored user dental management program to operate the dental management server ( 300, the query for the individual (user) of the user terminal 100 may be transmitted to the dental care server 300, and the response of the query may be received.

The user terminal 100 may transmit authentication information for logging into the dental care server 300, such as an ID and a password, to the dental care server 300 to establish a channel with the dental care server 300.

In addition, the user terminal 100 may generate an authentication image using the tooth care program and display the generated authentication image on a display. The authentication image may be, for example, an image code having a standardized form such as a two-dimensional barcode (Quick Response) code or a three-dimensional barcode such as MS-Tag and Wi-Mo.

The authentication image may include authentication information for logging in to the dental care server 300 by an individual using the user terminal 100 and may include, for example, an ID and a password. Of course, it does not need to be an ID and password, but may be, for example, data in a promised format for authenticating the user terminal 100 between the dental care server 300 and the user terminal 100. In addition, the authentication image may further include period data indicating, for example, a period during which the dental care record apparatus 200 that recognizes the authentication image as the authentication image is accessible to the dental care server 300.

Such an authentication image may be configured in an encrypted format encrypted between the user terminal 100 (user dental management program) and the dental management server 300, for example, public key based or data encryption standard (DES), etc. It may be the same encryption format.

The authentication image or the text extracted from the authentication image may be accessed by the dental care server 300 to record the treatment information and access to treatment information about the individual of the medical record apparatus 200 that recognizes the authentication image. It may be decided to allow access for the purpose and if it further contains period data, then such access is allowed only during this period.

In addition, the user terminal 100 transmits an inquiry about an individual's tooth to the dental management server 300 and displays the processing result received from the dental management server 300 on the display of the user terminal 100. Such an indication may include a form displayed by overlapping processing results received on the tooth image (background image).

A control flow and a description thereof related to the user terminal 100 will be described with reference to FIG. 5.

The medical record device 200 is a device managed by a doctor, a nurse, or the like at the dentist. The medical recorder 200 may be, for example, a stationary personal PC, a notebook, or a tablet PC.

The medical recorder 200 may store treatment information about a specific individual and transmit the treatment information to the dental care server 300 along with the identification information (eg, ID) of the individual.

In addition, the medical recorder 200 includes an image sensor 460, which captures the authentication image and extracts the text extracted from the captured authentication image itself or the captured authentication image. 300 may be transmitted to the dental care server 300 to query past treatment information on the individual in the dental management server 300 or to record the treatment information for the individual as a treatment history for the individual.

The extracted text may be a string that can be recognized by a general person or a string that cannot be recognized. For example, the extracted text can be encrypted so that the encrypted text will not be recognized by the user as a word or a sentence, even if it is displayed in the form of an ASCII code or the like.

This encrypted form will not allow the medical recorder 200 to obtain authentication information for a particular individual. The authentication image may further include period data, and allows the medical recorder 200 that recognizes the authentication image only to access the dental care server 300 within the period data. The authentication image may be temporarily stored in the medical recorder 200.

More detailed description of the medical recorder 200 will be described with reference to FIGS. 2, 4, and 5.

The dental care server 300 is connected to the internet and is connected to at least one user terminal 100 and at least one medical recorder 200. The dental management server 300 may receive a query about a tooth for a specific individual from the user terminal 100, process the received query, and transmit the processing result to the user terminal 100.

In addition, the dental management server 300 is connected to one or more medical recorder 200 to receive treatment information for a specific individual from the medical recorder 200 to record in the dental management server 300 to record the past history for a specific individual It stores the treatment information to make the query available.

In addition, the dental care server 300 may be implemented as a web server, such that the medical recorder 200 connected by using a markup language (eg, HTML, XML, etc.) may be connected to the past for a specific individual. It can be configured to search the history.

Through the dental management server 300, the management of the history of the past treatment information for each individual and what treatment for a particular individual, what treatment occurred for each tooth metal material or manufacturer applied to each tooth Make sure you know where it is so that you can help with future dental care.

More detailed description of the dental care server 300 will be described with reference to FIGS. 2, 3 and 5.

2 is a diagram illustrating an exemplary hardware block diagram of the dental care server 300 and / or the medical recorder 200. The dental care server 300 and / or the medical recorder 200 may include a network interface 410, a memory 420, an input interface 430, an output interface 440, a mass storage medium 450, and an image sensor. 460 and a control processor 470, the system bus / control bus 480 connects other hardware blocks around the control processor 470.

The dental care server 300 and / or the medical recorder 200 may omit the inclusion of a specific hardware block. For example, the dental care server 300 may omit the image sensor 460 as a hardware block, and may further omit the input interface 430 or the output interface 440.

In this manner, the hardware configuration of each device may be different. Looking briefly at each hardware block, the network interface 410 includes a wired LAN module or a wireless LAN module for connecting the Internet. The network interface 410 may be connected to the Internet to transmit and receive data between the user terminal 100 or the medical recorder 200 and the dental care server 300.

The memory 420 may permanently store or temporarily store data, including volatile memory and / or nonvolatile memory. The memory 420 may permanently store or temporarily store a program driven by the device so that the program can be driven under the control of the control processor 470.

The input interface 430 receives an input by a user of this device. For example, the input interface 430 may receive input from a keyboard, mouse, or touch panel and transfer the received input to the control processor 470.

The output interface 440 outputs the result by the input by the user of the apparatus or outputs the result performed by the control processor 470. For example, the output interface 440 may output an image or a video to a display such as a monitor, a liquid crystal display (LCD), an LED, and the like, and output an audio signal through a speaker.

The mass storage medium 450 stores various data. The mass storage medium 450 may be, for example, a hard disk. The mass storage medium 450 stores a program executed in the apparatus or various data required for execution in the apparatus.

The image sensor 460, which may be included in the medical recorder 200, may include a charge-coupled device (CCD) sensor or the like to sense an external image exposed to the lens. The image sensor 460 provides image data to the medical recorder 200, in particular to the control processor 470, to extract specific data (eg authentication data) therefrom. The image sensor 460 may be fixedly installed in the medical recorder 200 or may be configured to be moved under the control of a user such as a dentist or a nurse.

The control processor 470 controls each block of the device and preferably controls each block using a program stored in the mass storage medium 450 or the memory 420. Control performed by the control processor 470 will be described with reference to FIGS. 3 to 5.

The system bus / control bus 480 is a bus that can transmit and receive data and control data between hardware blocks of the apparatus, and includes, for example, a parallel bus or a serial bus.

3 is a diagram illustrating an exemplary functional block diagram of a dental care server 300. Such a functional block diagram of FIG. 3 may be implemented, for example, on the hardware block diagram of FIG. 2, and preferably may be configured by loading a program by the control processor 470 to control each hardware block.

The dental care server 300 of FIG. 3 queries the database 310, the first authentication and connection setting unit 320, the second authentication and connection setting unit 330, and the treatment information receiving and recording unit 340. The receiver 350 includes a query processor 360 and a result transmitter 370. Some of these functional blocks may be omitted as necessary, and may further include functional blocks not included in this block diagram.

Referring to each functional block according to FIG. 3, the database 310 uses a mass storage medium 450 or a memory 420 to store information related to a plurality of individuals, treatment information generated from a plurality of dentists, It stores information such as related information and dental news.

Such database 310 may be structured. For example, the database 310 may authenticate a plurality of individuals, authenticate a plurality of dentists, or a user DB 311 storing treatment history information about each individual, or specific information (for example, each dentist). Location, dentist, opening date, etc.) may include a dental DB (313) for storing information, such as dental information DB (315). Such a DB may be configured in the form of a table, and an entry (or record) included in each table is allocated and stored for a specific user, a dentist, or a specific news in the table.

Here, look at each DB in more detail, the entry of the user DB 311, including the ID and password for authenticating the individual as a field (field), further connected or not connected to the dental care server 300 Connection status flag, which includes a virtual channel number (e.g., a socket number or a channel number assigned between the user terminal 100 and the dental care server 300) at the time of connection, in addition to this individual. Per tooth may further include type information for each tooth so as to know whether it is permanent or childish.

In addition, the entry of the user DB 311 further includes treatment history information (also may use a pointer), and the treatment history information may be allocated to one table for each individual. Each entry in this treatment history information table may include an identifier of the time of treatment and the treated tooth (to identify among a number of teeth), an identifier of the dentist in charge of the treatment (these identifiers are identifiers on the dental DB 313). Information about the material used in the treatment and / or a material image for identifying the material, and / or a dental image taken at the dentist in charge of the treatment.

Treatment information included in such an entry may be received directly from the user terminal 100 or may be received from the dental medical recorder 200. If the treatment information is received from the medical recorder 200, information for identifying an individual (for example, an ID or a social security number) or an authentication image is received from the medical recorder 200 to identify an individual. The dental care server 300 may know whether the treatment information.

In addition, the entry of the user DB 311 may further include information on the encryption format. This encryption format is information necessary for decrypting authentication data received from the medical recorder 200.

The entry of the dental DB 313 may include, as fields, an ID and password for the dentistry (medical recorder 200), a connection status flag, and a virtual channel number at the time of connection. It may further include a counseling status flag, including the type of treatment that is present, location information of this dentist, personal information about the dentist of this dentist, and status information by date and / or hourly appointment, as well as availability of online consultation. have.

The entry of the dental DB 313 is used so that the medical recorder 200 can be connected to the dental management server 300 to update the individual's treatment information. Of course, the medical recorder 200 which is not present in this entry can also be connected to the dental management server 300, in which case it can be connected preferably using authentication data.

The entry of the material DB 315 stores information related to the dental news, and stores, for example, the identifier of the information provider who provided the dental news, the time when the news was provided, and the period during which the news was valid.

The entry of the data DB 315 enables the user terminal 100 to provide various additional news in the future.

The first authentication and connection setting unit 320 authenticates at least one user terminal 100 requesting authentication through a broadband network constituting the Internet, and establishes a channel connection with the user terminal 100 according to the authentication result. do. Here, the channel connection may be a network connection that distinguishes the user terminal 100 from other user terminals 100, for example, a channel identified by a channel number arbitrarily assigned when the user terminal 100 is connected for authentication. It can be a connection.

To this end, the first authentication and connection setting unit 320 receives data (for example, an ID and a password) necessary for authentication from the user terminal 100 and uses the data to identify a user in the user DB 311. If the password matches, the user is authenticated.

And if authentication succeeds, set the connection status flag of the entry assigned for this user to the connected state and set the channel number assigned for this user to the virtual channel number of the entry. After that, the user can transmit various queries to the dental management server 300 using this channel number, and the dental management server 300 uses the user DB 311 or the like to connect the processed results to this query. It can be transmitted to the user terminal 100 through.

The second authentication and connection setting unit 330 authenticates the medical record device 200 installed in at least one dentist or the like requesting authentication through a broadband network constituting the Internet, and the medical record device 200 according to the authentication result. Set up a channel connection with. The channel connection here may be a channel connection identified by a channel number arbitrarily given by the dental care server 300 when connected.

More specifically, the second authentication and connection setting unit 330 receives data (ID, password, etc.) necessary for authentication from the medical recorder 200 and uses the data for specific treatment in the dental DB 313. After identifying the recording apparatus 200 (or a specific dentist) and authenticating the medical recording apparatus 200, a connection is established by assigning a virtual channel number with the medical recording apparatus 200. Thereafter, the medical recorder 200 may load the treatment information about the individual who is treated through the connected channel, or change a specific field in the entry.

Here, the second authentication and connection setting unit 330 may also be configured to allow access to information about a specific individual. For example, when the dental care server 300 receives authentication data from the medical recorder 200 and determines whether the authentication data is data for authenticating a specific individual, and if the specific individual can be authenticated, the authentication may be performed. The medical recorder 200 having transmitted the data may be configured to access the treatment information of the individual.

Of course, in this case, the authentication process for the medical recorder 200 itself may be omitted, and in this case, the medical record according to whether or not to allow access to the dental care server 300 by the authentication of the authentication data and whether to permit the access. The second authentication and connection setting unit 330 determines whether to establish a channel connection of the device 200 to the dental care server 300.

Here, the authentication data may be encrypted, for example, including data (ID or password) for authenticating an individual. This encryption may be an encryption scheme in a format previously promised between the particular individual and the dental care server 300, thereby making it impossible for the medical recorder 200 to decrypt the authentication data.

In addition, the authentication data may further include period information (data) indicating the accessible period of the medical record apparatus 200 that has transmitted the authentication data, and the period information may cause the second authentication and connection setting unit 330 to transmit. In addition, even if personal authentication is completed, if the period is over, the connection can be configured to prevent the unauthorized information from being stolen or copied.

The treatment information receiving and recording unit 340 receives treatment information about a specific individual through a channel connected from the authenticated medical recorder 200 and stores the received treatment information in the treatment history information table included in the entry of the individual. Write to a new entry.

This treatment information includes field information necessary to form an entry in the treatment history information table.

Also, the treatment information receiving and recording unit 340 may identify from the authentication data about the individual who is the treatment target of the connected medical record apparatus 200 using the authentication data determined from the authentication image, and thus, the user DB 311 of the individual. Write to entries is possible. If the individual cannot be identified, the medical recorder 200 first requests data for authenticating or identifying the specific individual, and identifies the specific individual in the user DB 311 by using the received data. It may be configured to store the treatment information in.

The query receiver 350 receives a query about a tooth that the user (individual) wants to know or is interested in from the user of the user terminal 100 to which the channel is connected through the first authentication and connection setting unit 320. The query is defined as data in a promised format between the user terminal 100 and the dental care server 300 and embedded in a data packet transmitted and received through a connected channel. This query is, for example, a dental history request for knowing a past treatment history for an individual, a dental appointment request for an individual to schedule a visit to a dentist, or the individual's entry of treatment information entered directly by the individual (treatment history information). It may be a request for recording of a dental examination result requesting a record in a table), a request for a dental consultation to solve a question or a question related to a tooth or a dentist, or a request for dental news for knowing dental news.

In addition, the request for dental care history may be a request for medical history for each tooth to be broken down by more teeth to know the medical history for each tooth, or may be a request for medical history by date requesting to provide the treatment information in order by date. .

The query receiving unit 350 that receives such a query, that is, a request, may receive a query for a plurality of individuals, respectively, and receive each query through a connected channel for each individual, and then process each of the queries through the connected channel. Is sent.

In this example, the query receiver 350 has been described as processing a request for an individual. However, the query receiver 350 may be configured to process a request from the medical recorder 200.

The query processor 360 processes a query received from an individual or from the medical recorder 200, that is, each specific request using a database for each individual or medical recorder 200.

For example, the query processing unit 360 that receives the dental care history request generates a treatment result using the treatment history information table included in the individual's entry of the user DB 311. More specifically, in response to receiving a request for medical history for each tooth, the query processor 360 classifies each entry of the treatment history information table by teeth using the identifier of the tooth, and classifies the entry classified for each tooth of the tooth. By mapping to the identifier, all or part of the fields of the mapped entry are extracted and generated as a processing result.

Accordingly, the processing result may include, for example, one or more treatment time points or material information corresponding to the identifier of the tooth, material information, material image, photographed tooth image, dental information, and the like. Overlapping on the displayed tooth image (for example, using a bubble shape or an arrow) may be used to determine what treatment has occurred for each tooth. In addition, the treatment result may further include tooth-specific type information, which may identify whether each tooth is currently permanent or indwelling.

As another example, in response to receiving a request for a medical history by date, the query processing unit 360 orders each entry of the treatment history information table included in the individual's entry of the user DB 311 by date, and among the fields of the ordered entry. Extract all or part of it and generate it as the result of processing. In this process, when the ordered entries have a predetermined number or more, the query processing unit 360 may omit some entries so that only less than a certain number of entry information is included in the processing result.

In another example, in response to the receipt of the dental appointment request, the query processing unit 360 may use the identifier of the dentist included in the appointment request and the designated time, according to the date and / or date of the corresponding entry of the dental DB 313. The reservation status information for each hour may be changed and the reserved information may be transmitted to the medical recorder 200 of the dentist.

In another example, in response to receiving a request for recording a dental examination result, the query processing unit 360 generates and records a new entry in the treatment history information table of the individual's entry of the user DB 311. The treatment information included in the request for recording the result of the dental examination may include information about a field included in an entry of the treatment history information table.

In another example, in response to the reception of the dental consultation request, the query processing unit 360 determines a dentist who can consult using the consultation status flag of the dental DB 313, and transmits the dental consultation request to the determined one or more medical recording apparatus 200. The consultation content included is transmitted, and when a response to the consultation is received from the specific medical record apparatus 200, it is generated as a processing result.

In another example, in response to the reception of the dental news request, the query processing unit 360 searches the data DB 315 and generates the dental news included in the data DB 315 as a processing result.

Of course, some requests may not include specific data or information, and the processing result may include a response (for example, success or failure) indicating whether the processing is normally performed according to a user's request.

In this way, the query processor 360 may use the database 310 to process requests for various users.

The result transmitting unit 370 transmits the generated processing result through a channel connected to each individual, and the user terminal 100 receiving the processing result displays the processing result on the display in the form of an image.

4 is a diagram illustrating an exemplary functional block diagram of the medical recorder 200. The functional block diagram of FIG. 4 may be implemented, for example, on the hardware block diagram of FIG. 2. Preferably, the functional block diagram may be configured by loading a program by the control processor 470 to control each hardware block.

The medical care recording apparatus 200 of FIG. 4 includes an image recognition unit 210, an authentication data determination unit 220, an authentication data storage unit 230, an authentication data transmission unit 240, and a channel connection setting unit 250. And a request receiving unit 260, a request transmitting and receiving unit 270, and a request display unit 280. Some of these functional blocks may be omitted as necessary, and may further include functional blocks not included in this block diagram. These functional blocks can be implemented by, for example, an application driven by the control processor 470 of the medical recorder 200, which can connect to the Internet or a specific server (tooth management server 300). The program may be, for example, a web-based application.

Referring to each functional block according to FIG. 4, the image recognition unit 210 captures an authentication image displayed on the user terminal 100 using the image sensor 460 or the like. The authentication image may be, for example, a QR code or an MS-Tag or Wi-Mo type image code in a standardized format.

The authentication data determiner 220 determines the authentication data to be used to authenticate the user terminal 100 in the captured authentication image. The determination of the authentication data may be performed by extracting the image code from the authentication image according to the type of the image code and extracting specific text (data) from the image code. Alternatively, the authentication image or the image code itself may be one piece of authentication data without the medical recorder 200 having to perform this process. The authentication data determined as described above may be encrypted so that the medical recorder 200 does not know the method used for encryption and the decryption key, and thus does not know the authentication information necessary to access the personal information of the dental care server 300. Do not let it.

The authentication data storage unit 230 temporarily stores the authentication data determined by using the memory 420 or the mass storage medium 450 or for a predetermined period of time. The stored authentication data may then be utilized for a user who uses a dentist equipped with the medical recorder 200 without being recognized by the image recognition unit 210. In this case, the authentication data may be stored together with the identifier of the user, and the identifier may be, for example, the name of the user or may further include at least a part of the social security number.

The authentication data transmission unit 240 transmits the authentication data stored in the authentication data determination unit 220 or in the authentication data storage unit 230 to the dental care server 300. The transmission of the authentication data enables the dental care server 300 to identify a specific individual and to connect a channel for the specific individual with the medical recorder 200.

The channel connection setting unit 250 establishes a channel connection for the individual through the Internet and the dental care server 300 according to the transmission of the authentication data. Of course, since the medical recorder 200 may be used for a plurality of individuals, when a channel connection for one individual is established, the channel connection for another individual may be set to the dental care server 300 or a channel connection. It may be configured to be broken by the unit 250.

In addition, the channel connection setting unit 250 may further set a channel connection to the dental care server 300 for the medical care recorder 200 itself. Accordingly, modification and / or addition of an entry of the dental DB 313 assigned to the medical care record apparatus 200 may be performed.

The request receiving unit 260 receives an input received through the input interface 430 from a dentist or nurse who uses the medical record apparatus 200, and determines a request corresponding to the received input. Such a request may be controlled by the channel connection setting unit 250 to determine a specific request.

For example, the determined request may be a part of a request that may be transmitted from the user terminal 100, and may be, for example, a request for recording a dental examination result, a request for medical history for each tooth, or a request for medical history for each date.

The determined request may also be a request required for modifying and / or adding entries in the dental DB 313. These two different requests may be made through a control window separated by an application program or may be configured under control by a channel connection setting unit.

The request transmitting and receiving unit 270 transmits the determined request through the connected channel (for the individual or for the dental medical recorder 200) and receives the processing result from the dental management server 300. The request transmission and reception unit 270 is also made through the connected channel of the channel connection setting unit 250.

In addition, the request display unit 280 displays the processing result received through the connected channel of the channel connection setting unit 250 on the display through the output interface 440.

The functional block diagram of FIG. 4 may be configured to allow the medical recorder 200 to inquire and modify treatment history information about an individual, while not exposing important information about the individual.

FIG. 5 is a control flowchart illustrating a control flow generated between the user terminal 100, the medical care recording apparatus 200, and the dental care server 300. Hereinafter, a description will be given focusing on contents that do not overlap with the description of FIGS. 3 and 4.

Prior to this, the dental care program performed in the user terminal 100 may display a layered menu. The dental care program is a menu of the highest level, and includes an image icon for searching an individual's past treatment history, an image icon for reserving a dental treatment, an image icon for an individual to directly input treatment information, and consultation regarding teeth. Image icon for requesting an image, an image icon for receiving a dental news, and the like, and in addition, an image icon for logging in (certifying) the dental care server 300 or an image icon for generating an authentication image or a dental management server ( And an image icon for registering as a member in 300.

The configuration of such image icons may vary depending on the embodiment and the particular icons may be configured to perform two or more functions.

The selection of each image icon by the user may be transferred to a lower level menu or a corresponding query or request may be generated by the selection and transmitted to the dental care server 300. The network address for the dental care server 300 may be stored in the dental care program as well.

For example, the selection of the image icon for the treatment history inquiry is configured to display a lower level menu, and the lower level menu includes at least two image icons for inquiring the treatment history by tooth and date. The selection of the lower level image icon may transmit a corresponding dental history request or a dental history request to the dental management server 300 and display the received processing result in the lower level processing result window.

The treatment results displayed in this Treatment Results window show the individual's treatment history, for example, from the most recent date to the following date, for example, if the request is for a daily medical history (for example, at what dentist and when In the case of a request for medical history for each tooth, the tooth image embedded in or stored in the tooth care program is displayed and the tooth identifier included in the processing result for each tooth of the marked tooth image is used to display the tooth image. Overlap it so that you know what treatment occurred for each tooth.

In this case, the treatment information displayed in the treatment result window may be selected by the user again, and may include detailed information related to the treatment information. Such information may include, for example, what treatments have been performed, such as an X-ray photograph (image of a tooth taken) or the material used for treatment, or an image to identify the material (for example, a bar code on an implant product). Contains information that can be known.

In addition, other menus of the upper level also display necessary input windows and output windows according to the functions assigned to each icon to receive necessary information from the user through the input window, and to the dental care server 300 according to a query request by the user. After sending, you can configure the processing results to be displayed in this output window.

The selection of an image icon for generating an authentication image is performed by the medical recorder 200 using the authentication image or information (ID or password) for logging into the dental management server 300 to the user. It may be required to input period data that can be connected to 300. Alternatively, the image icon for generating the authentication image may be displayed to be activated by the user only when the user is already authenticated to the dental care server 300 and connected to the channel. In this case, the request for the user of the information for logging in may of course be omitted.

According to the selection of the icon for the authentication image, the user terminal 100 generates an authentication image and displays it on the display. The displayed authentication image may be captured by the image sensor 460 of the medical recorder 200.

Referring to the main control flow again through FIG. 5 with reference to the tooth management program (user interface) in the user terminal 100, first, at least one user terminal 100 requests authentication to the tooth management server 300 ( 1 of FIG. 5). This authentication request includes authentication information necessary for authenticating the user of the user terminal 100 and includes, for example, an ID and a password.

The dental care server 300 receiving the authentication information authenticates the user terminal 100 using the authentication information (see ② in FIG. 5). In this process, the dental care server 300 determines whether the user is registered as a member by using the user DB 311 of the database 310 and accordingly, an authentication response (accept / deny, etc.) indicating whether to allow access. ) Is transmitted to the user terminal 100 requesting authentication (see 3 in FIG. 5).

According to the authentication response, the dental management server 300 that allows the connection establishes a channel connection with the user terminal 100 (see ④ in FIG. 5). In this process, data required for channel connection may also be transmitted to the user terminal 100 or included in the authentication response in this process.

Thereafter, the user terminal 100 transmits an inquiry about a tooth, which is information that the user is interested in or needs, to the dental care server 300 through a connected channel (see ⑤ in FIG. 5). This query contains one of several requests. Such a request may be, for example, one of a dental care history request (a dental care history request by date, a medical care history request by date), a dental care appointment request, a dental examination result record request, a dental consultation request, and a dental news request.

The dental care server 300 receiving the query from the user terminal 100 processes the received query (see 6 in FIG. 5). Such processing may generate a processing result using the database 310 according to a request included in the query and may be different for each request.

For example, in the case of requesting a dental history request, the dental management server 300 classifies the entries of the treatment history information table of the entry of the individual in the user DB 311 by teeth using the identifier of the tooth and is classified. Is mapped to each tooth (identifier of) and information of the field included in the entry mapped with the identifier of the tooth is generated to generate a treatment result as treatment information.

As another example, in the case of a request for medical care by date, the dental care server 300 orders the entries of the treatment history information table of the entry of the individual of the user DB 311 according to the time of treatment and is included in the ordered entry. The information of the field is extracted to generate a treatment result as treatment information.

Thereafter, the dental management server 300 transmits the processing result to the user terminal 100 that has transmitted the query through the connected channel (see ⑦ of FIG. 5).

Accordingly, the user terminal 100 displays this processing result on the display. The result of this processing can of course be displayed overlapped with the tooth image (as a background image). Thereafter, the user terminal 100 may repeatedly perform a querying process and receive a processing result (see ⑧ of FIG. 5).

The result of such processing may also be transmitted to the medical recorder 200 (for example, only when the user of the corresponding user terminal 100 authenticates and is connected).

Similarly, the at least one medical recorder 200 may include a control flow similar to the control flow generated by the user terminal 100 and the dental care server 300. In brief, the medical recorder 200 requests an authentication to the dental care server 300 (see ①-1 of FIG. 5).

The authentication request is for authenticating the user of the user terminal 100 or for authenticating the medical recorder 200 (dental) itself. If the user terminal 100 authenticates the user, the authentication request includes authentication data. Such authentication data is for authenticating a specific individual.

The authentication data for the individual may be data received through the input interface 430 of the medical recorder 200 or authentication data determined from the authentication image captured by the image sensor 460. Therefore, in this case, the medical recorder 200 may request authentication by capturing the authentication image and then transmitting an authentication request including the authentication data determined by determining authentication data from the authentication image.

The dental care server 300 receiving the authentication data authenticates a specific individual or authenticates the medical record apparatus 200 using the authentication data (see ② in FIG. 5). In this process, the dental care server 300 determines whether the user is registered as a member using the user DB 311 of the database 310 or whether the corresponding dental is registered using the dental DB 313. Accordingly, an authentication response (accept / deny or the like) indicating whether to allow the connection is transmitted to the medical record apparatus 200 that has requested the authentication (see 3-1 in FIG. 5).

According to the authentication response, the dental management server 300 allowing the connection establishes a channel connection with the medical care recording apparatus 200 (see ④ in FIG. 5). In this process, the data required for channel connection may also be transmitted to the medical recorder 200 in this process or may be transmitted in the authentication response. In this process, the channel connection may be a data (user DB 311 or dental DB 313) that can be accessed according to this channel depending on whether the channel is for the medical recorder 200 or for an individual. The type of can vary or can be limited.

Thereafter, the medical recorder 200 transmits a query related to a registered dentist or a specific individual to the dental management server 300 through a connected channel (see ⑤-1 in FIG. 5). This query may include one of several requests and may be, for example, a dental care history request (a dental history request, a dental history request by date) or a dental examination results record request.

The dental care history request may be performed in the same manner as the procedure according to the dental care history request received from the user terminal 100.

Upon receiving the request for recording the dental examination result, the dental management server 300 receives the treatment information for the user included in the request and records the new information in the treatment history information table of the entry of the user DB 311 for the corresponding user. do. Such treatment information may include, for example, the time of treatment, the identifier of the treated tooth, the identifier of the dentist in charge of treatment (which may also be the identifier of the medical recorder 200), information about the material used in the treatment and / or Or a material image to identify this material, and / or a tooth image taken at the dentist in charge of the treatment. The one or more entries recorded as described above may be used to query the medical recorder 200 or the user terminal 100 to generate a processing result.

The dental care server 300 receiving the query from the medical recorder 200 processes the received query (see 6 in FIG. 5). Such processing may generate a processing result using the database 310 according to a request included in the query and may be different for each request.

Thereafter, the dental management server 300 transmits the processing result to the medical recorder 200 that has transmitted the query through the connected channel or to the user terminal 100 of the individual used by the medical recorder 200 for authentication (FIG. See ⑦-1 of 5).

Accordingly, the medical recorder 200 displays the processing result on the display through the output interface 440. Then, the medical recorder 200 may repeatedly perform the inquiry process and receive the processing result (see ⑧-1 of FIG. 5).

By using such a control flow, it is possible to provide the dental history information and the like related to the tooth to the user terminal 100 and to protect the important information of the individual while allowing the medical recorder 200 to access the specific information.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. The present invention is not limited to the drawings.

100: user terminal 200: medical record device
210: image recognition unit 220: authentication data determination unit
230: authentication data storage unit 240: authentication data transmission unit
250: channel connection setting unit 260: request receiving unit
270: request transmission and reception unit 280: request display unit
300: tooth care server 310: database
311: User DB 313: Dental DB
315 Source DB 320: First Authentication and Connection Setup
330: second authentication and connection setting unit 340: treatment information receiving and recording unit
350: query receiver 360: query processor
370: result transmission unit 410: network interface
420: memory 430: input interface
440: output interface 450: mass storage media
460: image sensor 470: control processor
480: System Bus / Control Bus

Claims (10)

A personal dental history management method using a dental care management device managed by a dentist and a dental management server connected to at least one medical care device and at least one user terminal through a network,
Authenticating, by the dental care server, a user terminal to access using authentication information;
Capturing, by the medical recorder, an authentication image displayed on a display of the authenticated user terminal using an image sensor;
Transmitting, by the medical record device, authentication data determined from the captured authentication image to a dental care server;
Determining, by the dental care server, whether to permit access of the medical recorder based on the received authentication data; And
And setting the channel connection with the medical recorder so that the medical recorder can access the treatment information for the authenticated user using the authentication data when the access is permitted.
The determined authentication data is the captured authentication image itself or text extracted from the captured authentication image,
The extracted text is encrypted in an encryption format promised between the user terminal and the dental care server,
The determined authentication data includes information of a period of time allowing the medical recorder to access treatment information for the authenticated user,
How to manage your personal dental history. The method of claim 1,
Receiving, by the tooth management server, a query about a tooth input from the authenticated user terminal from the user terminal; And
And transmitting, by the dental care server, the received query to the user terminal by processing the received query.
How to manage your personal dental history. The method of claim 2,
Receiving, by the dental care server, treatment information for the authenticated user from at least one medical record device; And
And recording, by the dental care server, the received treatment information together with an identifier of the medical recorder.
How to manage your personal dental history. delete delete The method of claim 3,
The dental care server, the processing of the received query and transmitting the processed result to the user terminal,
Classifying the recorded one or more treatment information using an identifier of the tooth;
Mapping the classified treatment information for each identifier of the tooth; And
Generating treatment information mapped to identifiers of teeth as the processed result;
And transmitting the treatment information mapped to the identifier of the generated tooth to the user terminal.
How to manage your personal dental history. The method of claim 3,
The dental care server, the processing of the received query and transmitting the processed result to the user terminal,
Ordering the recorded one or more treatment information in order of treatment time; And
Generating ordered treatment information as the processed result;
And transmitting the generated ordered treatment information to the user terminal.
How to manage your personal dental history. A personal dental history management system comprising a dental care recorder managed by a dentist and a dental care server connected to one or more of the medical care recorder and one or more user terminals via a network,
The medical record device,
An image recognition unit displayed on the user terminal to capture an authentication image for authenticating the user; And
And an authentication data transmitter for transmitting the authentication data determined from the captured authentication image to the dental care server.
The dental care server,
A first authentication and connection setting unit for authenticating the user terminal through the network and establishing a channel connection to the user terminal on the network; And
On the basis of the authentication data received from the medical recorder, it is determined whether the medical recorder is allowed to access the dental care server, and when the access is permitted, the treatment information for the authenticated user is obtained using the authentication data. And a second authentication and connection setting unit for establishing a channel connection with the medical recorder so that the medical recorder is accessible.
The determined authentication data is the captured authentication image itself or text extracted from the captured authentication image,
The extracted text is encrypted in an encryption format promised between the user terminal and the dental care server,
The determined authentication data includes information of a period of time allowing the medical recorder to access treatment information for the authenticated user,
Personal dental history management system. delete delete

Images