KR102636838B1 - DTx PLATFORM SYSTEM AND METHOD SUPPORTING CONTINUOUS PRESCRIPTION AND MULTI-HOSPITAL CONTINUOUS PRESCRIPTION - Google Patents

Abstract

The present invention provides an interface module that provides an interface for providing at least one service among digital therapeutic prescription information exchange, digital therapeutic information exchange, digital therapeutic use result information exchange, and authentication to a medical institution system and a digital therapeutic agent server; An authentication module that performs at least one of authentication for the medical institution system and the digital treatment server, identity authentication for the patient's consent to provide information, and digital treatment user authentication; And at least one of patient information, digital treatment prescription information, and prescribed digital treatment use result information received from the medical institution system and the digital treatment server is processed and stored as digital treatment prescription data, and the digital treatment is stored according to the service request. A data management module that provides prescription data, wherein the data management module processes digital treatment prescription data according to the type of prescription prescribed by the medical institution system and provides prescription history data. It concerns a digital treatment platform system that supports continuous prescription and a method of providing digital treatment.

Description

Digital therapeutic platform system and method of providing digital therapeutics that support continuous prescription and multi-center continuous prescription {DTx PLATFORM SYSTEM AND METHOD SUPPORTING CONTINUOUS PRESCRIPTION AND MULTI-HOSPITAL CONTINUOUS PRESCRIPTION}

The present invention provides an environment in which digital treatment prescription linkage and mutual data exchange according to standard protocols are possible for smooth prescription and medical data linkage between medical institutions and medical service companies following various regulations, and digital treatment prescriptions between medical institutions and digital treatment companies. and digital therapeutics that safely exchange treatment data using minimal patient information with patient consent, manage prescription history for single prescription/serial prescription/multi-center continuous prescription, and support continuous prescription and multi-center continuous prescription. It is about a platform system and a method of providing digital therapeutics.

Digital therapeutics are software or digital devices that have the same clinical effectiveness as drugs for the prevention and treatment of medical disorders or diseases. As technology advances, new efficient medical services become possible, and as digital healthcare becomes more prominent, it goes beyond simple health care and diseases. Evidence-based digital treatments that prevent, manage, and treat are attracting attention. Due to the COVID-19 pandemic, interest in non-face-to-face treatment is increasing significantly, difficulties in treating patients with chronic diseases are occurring, and the number of patients with mental health problems such as depression is increasing rapidly, leading to interest in digital therapeutics to solve these problems. It is increasing.

In response to such demands, the number of companies developing various digital therapeutics is increasing, but it is difficult to exchange digital therapeutic prescription information and prescription use result information between medical institutions and medical service companies that follow various regulations, and prescribed digital therapeutic agents are difficult to exchange. There is a problem in that patient personal information must be passed on to digital treatment companies for use, and each digital treatment company must manage patient personal information.

In addition, patient personal information management must be accompanied by data security devices or systems such as access control, encryption, and access record management of patient personal information and prescription data in accordance with the provisions of the Personal Information Protection Act/Information and Communications Network Act, so various digital treatments must be provided. It requires a lot of cost and management resources for companies to equip such data security devices or systems.

Therefore, there is a need for an integrated platform that links prescription information and delivers digital treatments by providing a standardized data model and linkage method between medical institutions and medical service companies.

In addition, since digital therapeutics often aim to mediate (correct) psychological, behavioral, and lifestyle factors, they often require a long period of use of more than 6 weeks for treatment, and are divided into several stages. It has characteristics.

Therefore, digital therapeutics need to be managed separately according to a certain period of time or stage of progress for collaboration between doctors and confirmation and review of effectiveness.

Korean Patent Publication No. 10-2023-0169751 (2023.12.18)

In order to solve the above problems, the present invention provides an environment in which digital treatment prescription linkage and mutual data exchange according to standard protocols are possible for smooth prescription and medical data linkage between medical institutions and medical service companies, and provides digital treatment exchange between medical institutions and digital treatment companies. Continuous prescription and multi-center continuous prescription that safely exchange treatment prescriptions and treatment data using minimal patient information with patient consent, and enable the same disease for the same patient to be prescribed through collaboration between digital treatments and medical staff within various medical institutions. The purpose is to provide a digital therapeutic platform system that supports and a method of providing digital therapeutics.

The digital treatment platform system that supports continuous prescription and multi-center continuous prescription according to an embodiment of the present invention exchanges prescription information of digital treatment, exchanges digital treatment information, and exchanges and authenticates digital treatment use result information with the medical institution system and digital treatment server. an interface module that provides an interface for providing at least one service; An authentication module that performs at least one of authentication for the medical institution system and the digital treatment server, identity authentication for the patient's consent to provide information, and digital treatment user authentication; And at least one of patient information, digital treatment prescription information, and prescribed digital treatment use result information received from the medical institution system and the digital treatment server is processed and stored as digital treatment prescription data, and the digital treatment is stored according to the service request. and a data management module that provides prescription data, wherein the data management module processes digital treatment prescription data according to the type of prescription prescribed by the medical institution system and provides prescription history data.

In addition, the patient information and digital treatment prescription information received from the medical institution system may not include the patient's unique identification information, and the digital treatment prescription data transmitted to the digital treatment server may not include patient personal information. there is.

In addition, the data management module includes an information provision consent processing module that requests information provision consent from the patient terminal to manage patient personal information/prescription information and provide third party information, and receives and stores the result; a prescription data processing module that verifies the digital treatment prescription information received from the medical institution system, processes it, stores it as digital treatment prescription data, and activates the digital treatment prescription data according to the consent to provide information obtained from the patient terminal; and a prescription history module that provides prescription history data for previously prescribed digital therapeutic agents.

In addition, the prescription type includes single prescription, continuous prescription, and multi-center continuous prescription. In the case of a continuous prescription, previously prescribed digital treatment prescription history data is provided to the digital treatment server, and in the case of a multi-center continuous prescription, the digital treatment prescription history data is provided to the digital treatment server. It may be characterized by providing previously prescribed digital treatment prescription history data to the medical institution system and the digital treatment server.

In addition, in the case of multi-center continuous prescription, information provision consent is collected so that digital treatment prescription information can be provided to other medical institutions' systems, and digital treatment prescription history data is provided to other medical institutions only if the collected result is consent. It can be characterized.

In addition, the interface module includes an interchange API module that provides an interlocking interface for providing at least one function among prescription history information inquiry for digital therapeutics, prescription information inquiry, prescription and treatment information delivery, and prescription result information inquiry; and an authentication API module that provides an interoperable interface for issuing authentication keys, renewing authentication keys, and discarding authentication keys for authentication of the medical institution system and the digital therapeutics server.

In addition, the authentication module includes an institution authentication module that performs credential authentication for interworking with the medical institution system and the digital therapeutics server; An identity authentication module that requests identity verification in conjunction with an identity authentication system to collect consent to provide information for the use of patient personal information and prescription information, and receives the results; and a DTx user authentication module that performs patient authentication when using a digital therapeutic delivered to the patient terminal.

In addition, an FHRI module that processes data exchanged based on FHIR (Fast Healthcare Interoperability Resources) may be further provided.

Meanwhile, a method of providing a digital treatment that supports continuous prescription and multi-center continuous prescription according to an embodiment of the present invention includes a medical institution prescription history providing step in which the digital treatment platform system provides a digital treatment prescription history upon a request from a medical institution system; A prescription data processing step in which the digital treatment platform system receives patient information and digital treatment prescription information from the medical institution system, processes the information, and stores it as digital treatment prescription data; An information provision consent collection step in which the digital therapeutic platform system requests consent to provide information from a patient terminal and receives a result of the request; A DTx information transmission step in which the digital therapeutic platform system transmits digital therapeutic product access information to the patient terminal; A DTx prescription history providing step in which the digital treatment platform system provides digital treatment prescription history upon request from a digital treatment server; A prescription data provision step in which the digital treatment platform system provides digital treatment prescription data according to a request from the digital treatment server; And a DTx usage result providing step in which the digital therapeutic product platform system receives digital therapeutic product use result information from the digital therapeutic agent server, stores it as usage result data, and transmits the digital therapeutic product use result data to the medical institution system. You can.

In addition, the prescription data processing step may be characterized by generating and managing connection information between previously prescribed digital treatment prescription data and continuously prescribed digital treatment prescription data in the case of continuous prescription or multi-center continuous prescription.

In addition, the medical institution prescription history provision step may be characterized in that digital treatment prescription history data is provided only when third-party information provision consent to other medical institutions is collected from the patient terminal in the case of multi-institution continuous prescription.

Additionally, the DTx prescription history providing step may be characterized by searching the patient's DTx prescription history data using a DTx authentication code that does not include the patient's personal information.

Digital treatment providers can search prescription information through a one-time code provided by the digital treatment platform system and provide digital treatments to the patient without having to manage the patient's personal information.

If the use cycle of a digital treatment is long, continuous prescriptions and multi-center continuous prescriptions that divide prescriptions for the same digital treatment into certain cycles can be supported, allowing medical institutions to determine the effectiveness of the prescription and proceed with additional prescriptions.

Digital treatment providers do not individually link with medical institutions, but can receive prescription information prescribed by multiple medical institutions through linkage with the digital treatment platform system.

Medical institutions can receive digital treatment information provided by various digital treatment companies through the digital treatment platform system and prescribe it to patients.

Medical institutions and digital therapeutics companies can exchange medical data through standardized service linking methods.

Figure 1 is a schematic diagram showing the overall configuration including the DTx platform system supporting continuous prescription and multi-center continuous prescription.
Figure 2 is a main functional configuration diagram of the DTx platform system supporting continuous prescription and multi-center continuous prescription according to an embodiment of the present invention.
Figure 3 is a flowchart of a method for providing digital therapeutics (DTx) supporting continuous prescription and multi-center continuous prescription according to an embodiment of the present invention.
Figure 4 is a flowchart of an interconnection procedure for exchanging digital therapeutic (DTx) prescription information and prescription use results in a digital therapeutic (DTx) provision method that supports continuous prescription and multi-center continuous prescription.
Figure 5 is a flow chart detailing continuous prescription in a digital therapeutics (DTx) provision method that supports continuous prescription and multi-center continuous prescription.
Figure 6 is a flowchart detailing multi-center continuous prescription in a digital therapeutics (DTx) provision method supporting continuous prescription and multi-center continuous prescription.

Hereinafter, specific embodiments of the present invention will be described in detail with reference to the drawings. However, the spirit of the present invention is not limited to the presented embodiments, and those skilled in the art who understand the spirit of the present invention may add, change, or delete other components within the scope of the same spirit, or create other degenerative inventions or this invention. Other embodiments that are included within the scope of the invention can be easily proposed, but this will also be said to be included within the scope of the invention of the present application.

In addition, the terms described below are terms set in consideration of the function in the present invention, and may vary depending on the inventor's intention or custom, so the definition should be made based on the content throughout the specification, and in this specification, the terms related to the present invention In cases where it is determined that detailed descriptions of well-known configurations or functions may obscure the gist of the present invention, detailed descriptions thereof will be omitted.

Hereinafter, a digital therapeutic platform system 100 (hereinafter referred to as the DTx platform system) that supports continuous prescription and multi-center continuous prescription according to an embodiment of the present invention will be described with reference to the drawings.

Patient information and prescription information referred to in the present invention refers to medical information received from the medical institution system 200.

In other words, it means data before being processed in the DTx platform system 100.

Patient data and prescription data referred to in the present invention refers to data that is processed and managed by the DTx platform system 100 of patient information and prescription information received from the medical institution system 200.

Figure 1 is a schematic diagram showing the overall configuration including the DTx platform system 100 that supports continuous prescription and multi-center continuous prescription.

The DTx platform system 100 according to an embodiment of the present invention is connected to the medical institution system 200, the digital therapeutic agent server 300 (hereinafter, DTx server), and the patient terminal 400 through an online network and can communicate with each other.

The online network referred to in the present invention may be a core network integrated with a wired public network, wireless mobile communication network, or mobile Internet, etc., and may include TCP/IP protocols and various services existing at the upper layer thereof, such as HTTP (Hyper Text Transfer Protocol). , can refer to a worldwide open computer network structure that provides HTTPS (Hyper Text Transfer Protocol Secure), Telnet, FTP (File Transfer Protocol), DNS (Domain Name System), and SMTP (Simple Mail Transfer Protocol). It is not limited to examples, but comprehensively refers to a data communication network that can transmit and receive data in various forms.

The server referred to in the present invention may be constructed as a server that functions as at least one of a type of web server, database server, and mobile server. For example, it may display processed results on a web page through an online network or provide necessary input data. It can be transmitted through a web page, where a web page should be interpreted as including software for performing specific tasks such as web applications in addition to simple text, images, sounds, videos, etc., and can also be used on desktops, laptops, smartphones, It can also be built to provide applications and interfaces to be installed on tablet PCs, etc. However, it is not limited to this, and the type of server can be changed in various ways at a level that is obvious to a person skilled in the art.

The system referred to in the present invention may be configured to include the server and various communication devices such as desktops, tablets, netbooks, personal digital assistants (PDAs), portable multimedia players (PMPs), smartphones, and wearable smart devices.

The medical institution system 200 in the present invention is a prescription system (OCS, Order Communication System) or an electronic medical record (EMR, Electronic Medical Record) system used in medical institutions such as general/general hospitals, oriental medicine hospitals, and nursing hospitals. It may be a hospital information system (HIS) that includes at least one or more.

The medical institution system 200 converts the patient's prescription information to a standardized interconnection standard and transmits it to the DTx platform system 100, and can then check the results of the digital therapeutics (DTx) used by the patient.

The DTx server 300 in the present invention may be a system that includes at least one server that provides a digital therapeutic agent (DTx), or a server, a hardware device, and an application that operates on the hardware device to provide a digital therapeutic agent.

Here, digital therapeutics (hereinafter referred to as DTx) are software or digital devices that have the same clinical effectiveness as drugs for the prevention and treatment of medical disorders or diseases, and include virtual reality (VR)/augmented reality (AR), digital content, and computers. Technologies such as games, metaverse, and mobile may be applied, or technologies such as big data or artificial intelligence may be applied to maximize treatment effects.

The DTx server 300 can provide DTx information to the DTx platform system 100.

For example, the DTx server 300 may register DTx information in the DTx platform system 100 so that DTx can be used for prescriptions.

At this time, information and reference information necessary for prescription, such as DTx code, DTx connection information, usage information, and precautions, can be provided.

Additionally, the DTx server 300 can provide DTx in the form of an application (App) so that patients can download and use it through access information.

At this time, the DTx server 300 communicates with the App installed on the patient terminal 400 to deliver the prescribed DTx, receives the use results of DTx, and transmits them to the DTx platform system 100, so that the medical institution system 200 responds to the prescription. Allows you to check the usage results.

The patient terminal 400 in the present invention should be interpreted as including various communication means such as desktops, tablets, netbooks, personal digital assistants (PDAs), portable multimedia players (PMPs), smartphones, and wearable smart devices, and DTx By installing web-based or separate software/applications provided by the platform system 100 and the DTx server 300, various functions provided by the servers can be executed.

The DTx platform system 100 in the present invention is a standardized interface for providing digital treatment prescription information exchange, digital treatment information exchange, digital treatment use information exchange, and authentication services to the medical institution system 200 and the DTx server 300. It is possible to provide authentication for the medical institution system 200 and the DTx server 300, identity authentication for the patient's consent to provide information, and digital therapeutic user authentication.

In addition, patient information, digital treatment prescription information, and prescribed digital treatment use information received from the medical institution system 200 and the DTx server 300 are processed and stored/managed as digital treatment prescription data, and are requested by the DTx server 300. Accordingly, the corresponding prescription data can be delivered.

In addition, the usage results of the DTx prescription data used by the patient can be received, connected to the DTx prescription data, stored/managed, and the DTx usage result data can be transmitted to the medical institution system 200.

In addition, single prescription, continuous prescription, and multi-center continuous prescription can be performed at the request of the medical institution system 200.

Figure 2 is a main functional configuration diagram of the DTx platform system 100 that supports continuous prescription and multi-center continuous prescription according to an embodiment of the present invention.

Below, we will look at specific details related to the DTx platform system 100.

The DTx platform system 100 may include an interface module 110, a data management module 120, an authentication module 130, an FHIR module 140, and a database (DB, 150).

The module is a functional component, and each module may be composed of a plurality of servers such as an application server, database server, web server, and web application server depending on the architectural design.

The interface module 110 may provide an interface defined according to a predefined network protocol to exchange data between the medical institution system 200 and the DTx server 300.

For example, the predefined network protocol may be a RESTful API or HL7 (Health Level 7)-based RESTful API.

Here, HL7 is a standard certified by the American National Standards Institute (ANSI) for the exchange of information between various health and medical information systems. It can unify the interface by standardizing the format of messages sent and received to enable direct information exchange between medical information systems. .

RESTful API and HL7 standards are already known technologies, so detailed information will be omitted.

The interface module 110 is an interchange API module 111 provided to transmit and receive medical information such as patient information, prescription information, and prescription use result information, authentication of the medical institution system 200 or DTx server 300, and patient information. It may include an authentication API module 112 provided for identity authentication.

More specifically, the interchange API module 111 can provide an interchange API for querying DTx prescription information, querying DTx prescription history information, transmitting DTx prescription information, and querying DTx prescription result information.

The authentication API module 112 can provide an authentication API to perform an authentication process for the medical institution system 200 and the DTx server 300 using the interchange API.

For example, the authentication API may include APIs for requesting authentication key issuance, updating authentication key, and deleting authentication key.

However, it is not limited to this and various APIs for interoperability may be defined and provided according to the authentication process.

The authentication module 130 is an institutional authentication module 121 that performs authentication for the medical institution system 200 and the DTx server 300 that exchanges data with the DTx platform system 100, and identity authentication for the patient's consent to provide information. It may include an identity authentication module 122 that requests and receives the results, and a DTx user authentication module 123 that authenticates the prescribed DTx and the patient using it.

The institutional authentication module 121 can provide an OAuth2 authentication process that certifies external systems such as the medical institution system 200 and the DTx server 300 to use services provided by the DTx platform system 100.

For example, the organization authentication module 121 can perform the Client Credentials method of OAuth2.

More specifically, the medical institution system 200 and the DTx server 300 may request credentials through a web service or web portal site interface provided by the DTx platform system 100. At this time, the authentication module 120 After registering credentials and institutional information (medical institution, digital therapeutics company), a Secret Key is issued to store authentication information and authorization information.

Afterwards, the medical institution system 200 and the DTx server 300 can request services provided by the DTx platform system 100 by obtaining an authentication key (Access Token) using the issued Secret Key.

The DTx platform system 100 determines whether a service request is acceptable to the relevant institution through institution authentication and identifies institution information through an access token, so this must be performed before requesting a service.

The identity authentication module 122 can link with an identity authentication service system, which is an external system, to provide an identity authentication screen to the patient terminal 400 and receive the identity authentication results.

For example, the identity authentication service system may be a mobile phone identity authentication system that verifies the identity of the mobile phone holder from the telecommunication company.

The DTx user authentication module 123 does not transmit patient personal information to the DTx server 300, but in order to exchange prescription data with the DTx server 300, it provides a DTx one-time code to identify the DTx prescription data prescribed to the patient. It can be created and managed.

At this time, the DTx one-time code includes the medical institution identifier, prescription identifier, patient name, and patient mobile phone number, and can be one-way encrypted to generate a non-redundant identification code.

In the DTx platform system 100, patient information and DTx prescription information received from the medical institution system 200 do not include the patient's unique identification information, and DTx prescription data transmitted to the DTx server 300 does not include patient personal information. The purpose is to manage and exchange data.

In other words, the DTx platform system 100 manages the minimum amount of patient information.

Patient information may be included in prescription information delivered by the medical institution system 200.

At this time, the patient information included in the prescription information does not include unique identification information such as resident registration number, passport number, driver's license number, alien registration number, etc. that can directly identify the patient in a 1:1 correspondence, We use only the minimum amount of patient personal information necessary to provide services.

This is to prevent personal information leakage in advance by managing only the minimum personal information necessary to identify the patient.

Meanwhile, the DTx one-time code can be used to identify a single prescription.

Additionally, it can be used as an auxiliary authentication key to request or transmit patient-related information from the DTx server 300 to the DTx platform system 100.

Here, the DTx one-time code is not used immediately after creation, but can be used after activation.

Before activation, the DTx one-time code is managed in connection with the patient's name and mobile phone number, but after obtaining consent to provide information from the patient, it is activated and linked to prescription data so that it can be used as an identifier.

Meanwhile, the DTx user authentication module 123 can generate, map, and manage a DTx one-time code and a corresponding DTx authentication code.

Here, the DTx authentication code is transmitted to the patient terminal 400 after the patient agrees to provide information and can be used as a means for authenticating the user and the prescribed DTx when the patient uses the prescribed DTx.

Additionally, the DTx authentication code does not contain the patient's personal information or any information that can be inferred.

For example, to use DTx, the patient runs the DTx application (App), enters the DTx authentication code sent to the patient terminal (400), goes through the user authentication process of the DTx App authentication/linking system (100), and then uses DTx. You can.

At this time, the DTx application (App) installed on the patient terminal 400 can receive the authentication procedure and DTx prescription data through the DTx server 300 without directly communicating with the DTx platform system 100.

The data management module 130 processes patient information, digital treatment prescription information, and prescribed digital treatment use result information received from the medical institution system 200 and the DTx server 300, stores it as DTx prescription data, and sends a service request. DTx prescription data can be provided according to.

The data management module 130 may include an information provision consent processing module 131, a prescription data processing module 132, and a prescription history module 133.

The information provision consent processing module 131 may request consent to provide information to a third party through the patient terminal 400 for mutual exchange of DTx prescription data and receive the result.

More specifically, the information provision consent processing module 131 may transmit a URL through which information provision consent can be performed to the patient terminal 400 using the patient's mobile phone number.

For example, a method of delivering the information provision consent URL to the patient terminal 400 may be a mobile text message, an SNS message, or a notification from an application linked to a medical institution.

The prescription data processing module 132 may verify the DTx prescription information received from the medical institution system 200, process the information, and store it as DTx prescription data.

More specifically, the prescription data processing module 132 may perform expression and data verification on prescription information received through the FHIR module 140, which will be described later.

Additionally, the prescription data processing module 132 may process the DTx prescription information for which verification work has been completed according to the data structure of the DTx platform system 100 and store it as DTx prescription data.

At this time, a DTx one-time code can be requested through the DTx user authentication module 123, and a process of mapping the DTx one-time code and DTx prescription data can be performed.

Afterwards, through the information provision consent processing module 131, the patient's consent to provide information can be collected and stored, and DTx prescription data for which the patient has agreed to provide information can be activated.

Here, activation of DTx prescription data means that the use and provision of data to a third party is permitted, and may mean that prescription data can be transmitted to the DTx server 300.

Meanwhile, the prescription data processing module 132 can manage connection information between DTx prescription data according to the type of prescription.

Here, the prescription type may include a single prescription, a continuous prescription, and a multi-center continuous prescription, and the prescription type is defined in advance and can be delivered by the medical institution system 200 by including it in the DTx prescription information.

Additionally, if the type of prescription is a continuous prescription or a multi-center continuous prescription, a continuous prescription code that can determine the connection with the continuous prescription may be included.

In other words, DTx prescription information with the same consecutive prescription code can be determined to be connected to consecutive prescriptions.

A single prescription may mean implementing the entire DTx use cycle with one prescription issued by the medical institution system 200.

Continuous prescription may mean issuing multiple prescriptions by dividing the DTx prescription issued by one medical institution system 200 at regular intervals.

Continuous prescription is to prescribe the next drug while judging its effectiveness during use, as the period during which a patient uses one DTx may be prolonged.

Multi-institution continuous prescription may mean issuing continuous prescriptions in a plurality of medical institution systems 200.

The prescription data processing module 132 can query previously prescribed DTx prescription data for continuous prescriptions and multi-center continuous prescriptions to generate and store connection information for continuous prescriptions.

For example, linkage information may include prescription type, continuous prescription code, DTx identification code (DTx prescription code), and DTx one-time code.

Meanwhile, the prescription data processing module 132 verifies the data through the FHIR module 140 on the DTx use result information received from the DTx server 300, processes it, and includes it in the corresponding DTx prescription data. The results of prescription use can be saved.

The prescription history module 133 may provide DTx prescription history data in response to a request for previous prescription history from the medical institution system 200 and the DTx server 300.

More specifically, when the medical institution system 200 makes a continuous prescription or multi-institution continuous prescription, it can request the DTx platform system 100 for the history of prescriptions previously prescribed to the patient.

At this time, the medical institution system 200 can search the DTx prescription history using patient information (name), hospital identifier, and DTx code (DTx identifier).

In other words, prescription history can be searched using only minimal patient personal information (name).

In addition, the DTx server 300 may request previously prescribed prescription history from the DTx platform system 100 when delivering DTx use results for continuous prescriptions or multi-center continuous prescriptions. At this time, the DTx server 300 transmits the history of previously prescribed prescriptions. By using the DTx authentication code, previous identification information can be searched without including the patient's personal information.

The prescription history module 133 can search the corresponding DTx prescription data in response to the DTx prescription history request, check whether there is consent to provide information, and provide a list of DTx prescription data for which the user has agreed to provide information.

As a result, the medical institution system 200 can proceed with the next prescription by referring to the DTx prescription history data, and the DTx server 300 can record the DTx use results for consecutive prescriptions, including the results of previous prescriptions and uses for the same DTx. The entire thing can be created and delivered.

The DTx platform system 100 may further include an FHIR module 140 that processes data exchanged based on FHIR (Fast Healthcare Interoperability Resources).

The FHIR module 140 can perform verification of expressions and required data for FHIR (Fast Healthcare Interoperability Resource) data.

Here, FHIR data refers to a text-based data model that defines medical information in accordance with the HL7 standard, and data verification work can be performed on the premise that DTx prescription information is linked to FHIR data.

FHIR must be defined in advance according to the type of data being linked.

The FHIR module 140 can configure or parse medical information such as prescription information and patient information to be exchanged according to defined FHIR standards.

Figure 3 is a flowchart of a method for providing a digital therapeutic agent (DTx) supporting continuous prescription and multi-center continuous prescription according to an embodiment of the present invention, and Figure 4 is a flow chart of a digital therapeutic agent (DTx) supporting continuous prescription and multi-center continuous prescription according to an embodiment of the present invention. This is a flowchart of the linking process for mutually exchanging digital therapeutics (DTx) prescription information and prescription use results.

With reference to FIGS. 3 and 4 , the method of transmitting prescription data for single prescription, continuous prescription, and multi-center continuous prescription will be described in detail.

First, when a medical professional prescribes, there are three types of prescriptions: single prescription, continuous prescription, and multi-center continuous prescription.

In the case of single prescriptions and consecutive prescriptions, prescriptions made at the same medical institution, the medical institution already manages history information on previous prescriptions, so there is no need to request previous prescription history data from the DTx platform system 200.

However, in the case of a multi-center continuous prescription that follows DTx prescribed by another medical institution, it is necessary to check the prescription history previously prescribed by other medical institutions and refer to it when prescribing.

Accordingly, the medical institution system 200 can request the DTx platform system 100 to check the history of prescriptions prescribed to a specific patient.

The DTx platform system 100 performs a medical institution prescription history provision step to provide digital treatment prescription history upon request from the medical institution system 200. (S310)

Step S310 can be performed in case of multi-center continuous prescription.

More specifically, the DTx platform system 100 receives a request to check the DTx prescription history prescribed to a specific patient from the medical institution system 200.

Here, the medical institution system 200 delivers patient information (patient name, mobile phone number) and DTx prescription code upon request, and the DTx platform system 100 can search and provide DTx prescription history corresponding to the above information. there is.

In addition, the DTx server 300 can also request DTx prescription history data for a specific patient from the DTx platform system 100, and transmits the DTx authentication code to obtain the patient's DTx prescription history data without using the patient's personal information. You can search. (Refer to step S350)

Meanwhile, when providing the searched DTx prescription history, consent to provision of information regarding the prescription data is checked and only the consented prescription data is provided.

In particular, in the case of multi-center consecutive prescriptions, that is, when a patient receives an initial prescription from medical institution A and then receives consecutive prescriptions from medical institution B, medical institution B may require the patient to share information about the DTx prescription data prescribed by medical institution A to other medical institutions. It would be advisable to provide previous DTx prescription history data only if consent has been provided.

The medical professional checks the patient's prescription history and issues a DTx prescription.

The DTx platform system 100 performs a prescription data processing step of receiving patient information and DTx prescription information from the medical institution system 200, processing them, and storing them as DTx prescription data. (S320)

More specifically, since the received DTx prescription information can be delivered in a data model format based on a standardized standard (FHIR), it is possible to determine whether data can be extracted (parsed) according to the standard and proceed with the next task.

After the verification work, a step is performed to process and store the extracted data into the data structure of the DTx platform system 100.

Here, the DTx platform system 100 does not transmit patient personal information to the DTx server 300, but generates and manages a DTx one-time code to identify the patient when exchanging prescription data with the DTx server 300.

The DTx one-time code can be used to identify one prescription, and after creation, the DTx one-time code is linked to the patient's name and mobile phone number. After going through the patient medical information consent process, it is activated and used as an identifier for DTx prescription data. You can.

Meanwhile, in the case of a continuous prescription prescribed in connection with previously prescribed digital prescription information for the same patient, link information (continuous prescription information) with previously prescribed digital prescription data is generated and stored.

Continuous prescription information includes prescription type, continuous prescription code, DTx identification code to identify DTx, and DTx one-time code and can be stored and managed separately.

Next, the DTx platform system 100 requests consent to provide information from the patient terminal 400, and performs an information provision consent collection step in which the result of the request is received and stored. (S330)

Here, the DTx platform system 100 transmits a URL through which informed consent can be performed to the patient terminal 400.

The URL can be delivered through text messages, SNS notifications, notifications from dedicated applications, etc.

When the patient performs the information consent process through the received URL, the DTx platform system 100 maps the consent with each DTx prescription data and stores it.

The informed consent process can be performed at each prescription.

If the patient agrees to provide information, the DTx platform system 100 performs a DTx information transmission step in which DTx access information is transmitted to the patient terminal 400. (S340)

DTx provided to the patient is provided in the form of an application and can be installed and used on the patient terminal (400). For this, the DTx platform system (100) sends the installation URL of the DTx App and the DTx authentication code for use of DTx to the patient terminal (400). ) can be transmitted.

The patient installs and runs the DTx App according to the DTx connection information transmitted to the patient terminal 400 and enters the DTx authentication code.

The DTx authentication code is managed by mapping with the DTx one-time code and can be used as an identifier to identify DTx prescription data.

Therefore, the DTx authentication code entered by the patient is transmitted to the DTx server 300 through the DTx App, and the DTx server 300 then sends DTx prescription history data and DTx to the DTx platform system 100 using the DTx authentication code. You can request prescription data.

Next, the DTx server 300 may use the DTx authentication code to perform a DTx prescription history provision step in which DTx prescription history data previously prescribed with the same DTx is searched by the DTx platform system 100. (S350)

The reason for checking the previous prescription history is to deliver the results of continuous use, including all results of DTx used by the patient from the first prescription to consecutive prescriptions.

The reason medical institutions issue continuous prescriptions is to divide the use cycle of the same DTx and issue it as continuous prescriptions in order to determine the effectiveness of DTx with a long use cycle. Therefore, the results of use, including the results of use of previously prescribed DTx, are communicated. It would be desirable to do so.

The DTx authentication code transmitted to search DTx history data can be used as an identifier to identify prescription data for a specific patient.

As a result, previous identification information can be searched without including the patient's personal information.

The DTx platform system 100 searches for the DTx prescription history data requested by the DTx server 300 and transmits it to the DTx server 300.

Thereafter, the DTx server 300 may request DTx prescription data from the DTx platform system 100 using the DTx authentication code.

The DTx platform system 100 performs a prescription data provision step in which the patient's DTx prescription data is searched using the DTx authentication code at the request of the DTx server 300 and the corresponding prescription information is provided. (S360)

The DTx server 300 can check the received DTx prescription data and provide the corresponding DTx to the patient.

Afterwards, when the patient completes the use of DTx, the DTx server 300 transmits the DTx use result information to the DTx platform system 100.

At this time, in the case of continuous prescription or multi-center continuous prescription, the DTx server 300 may connect and include previously prescribed and used DTx prescription results to generate result information and transmit it to the DTx platform system 100.

The DTx platform system 100 receives the DTx prescription usage result information transmitted by the DTx server 300, stores the usage result information in connection with the DTx prescription data, and transmits the information to the medical institution system 200. Perform the steps to provide usage results. (S370)

Here, in the case of consecutive prescriptions, the medical institution system 200 can receive usage results including all results for previous prescriptions.

For example, if a medical institution initially prescribes DTx for a 3-week period and then prescribes DTx for a 5-week period as the next consecutive prescription, the DTx use outcome data for the first prescription can be delivered as the use results for 1-3 weeks. In addition, DTx use result data for continuous prescriptions can be delivered for 1 to 8 weeks.

In addition, for example, in the case of multi-center continuous prescription, if medical institution A initially prescribed DTx for 3 weeks and medical institution B prescribed DTx for 5 weeks as a continuous prescription, medical institution A would prescribe DTx for 1-3 weeks. The results of use can be delivered, and medical institution B can receive the results of use for 1-8 weeks only if it has collected the consent of other medical institutions to provide information for 1-3 weeks of prescription data.

Figure 5 is a flow chart detailing continuous prescription in a digital therapeutics (DTx) provision method that supports continuous prescription and multi-center continuous prescription.

When a medical professional prescribes the first DTx to a specific patient, the medical institution system 200 transmits the DTx prescription information to the DTx platform system 100. At this time, the DTx prescription information is referred to as the first prescription.

Afterwards, the DTx platform system 100 processes the received DTx prescription information, stores it as DTx prescription data, and provides third-party information provision consent to the patient terminal 400 in order to provide the information to the DTx server 300. request.

If the patient accepts the consent to provide information, the DTx platform system 100 transmits the DTx access information to the patient terminal 400, and the patient installs and runs the DTx App using the received DTx access information.

The DTx App of the patient terminal 400 communicates with the DTx server 300 to deliver a DTx authentication code, and the DTx server 300 requests and receives DTx prescription data from the DTx platform system 100.

The DTx server 300 provides DTx included in the DTx prescription data to the patient.

The patient uses DTx during the first prescription cycle, and when use is completed, the DTx server 300 transmits the results of DTx use during the first prescription cycle to the DTx platform system 100.

The DTx platform system 100 that received this transfers the DTx use result data to the medical institution system 200 that issued the prescription.

This process corresponds to the process of initial prescription.

Next, the same DTx can be prescribed consecutively at the same medical institution.

The process of continuous prescription proceeds in the same way as the process of initial prescription, but after generating DTx prescription data in the DTx platform system 100, the process of generating and storing continuous prescription information linking the initial prescription and continuous prescription can be additionally performed. there is.

In addition, when the DTx server 300 searches DTx prescription data after installing the DTx App on the patient terminal 400, previously prescribed DTx prescription history data can be searched in case of continuous prescriptions. This is to deliver all results of continuously prescribed DTx prescription data to the DTx platform system.

As a result, the medical institution system 200 that continuously prescribes can receive information including all DTx use results for previous prescriptions and observe the effect of the prescribed DTx.

Figure 6 is a flow chart illustrating in detail multi-center continuous prescription in a method of providing digital therapeutics (DTx) that supports continuous prescription and multi-center continuous prescription.

Multi-institutional consecutive prescriptions may apply when the medical institution that first prescribed the medicine and the medical institution that subsequently prescribed sequentially are different.

This multi-center continuous prescription is the same as the flow of continuous prescription described above.

However, at the stage of continuous prescription at a medical institution other than the one that initially prescribed, an additional step of requesting DTx prescription history information first prescribed by another medical institution is performed before prescribing, and then the continuous prescription is made by referring to the information prescribed by the other medical institution. The prescription proceeds.

Additionally, when requesting consent to provide information through the patient terminal 400, it would be desirable to request an additional item for consent to provide information to other medical institutions.

In the above, the configuration and features of the present invention have been described based on the embodiments according to the present invention, but the present invention is not limited thereto, and various changes or modifications may be made within the spirit and scope of the present invention. It is instructed to those skilled in the art, and therefore, it is stated that such changes or modifications fall within the scope of the attached patent claims.

100: DTx platform system
110: Interface module
111: Interchange API module 112: Authentication API module
120: Authentication module
121: Institutional authentication module 122: Personal authentication module
123: DTx user authentication module
130: Data management module
131: Information provision consent processing module 132: Prescription data processing module
133: Prescription history module
140: FHIR module
200: Medical institution system
300: DTxserver
400: Patient terminal

Claims (12)

An interface module that provides an interface to the medical institution system and the digital treatment server to provide at least one service among digital treatment prescription information exchange, digital treatment information exchange, and digital treatment use result information exchange and authentication;
At least one of patient information, digital treatment prescription information, and prescribed digital treatment use result information received from the medical institution system and the digital treatment server is processed and stored as digital treatment prescription data, and the digital treatment prescription data is stored according to a service request. A data management module that provides; and
Authentication of the medical institution system and the digital treatment server, identity authentication for the patient's consent to provide information, and digital treatment user authentication are performed, and a DTx one-time code that does not contain patient personal information is used to identify the digital treatment prescription data. Provided with an authentication module that is created and managed,
Patient information and digital treatment prescription information received from the medical institution system do not include the patient's unique identification information, and digital treatment prescription data transmitted to the digital treatment server does not contain patient personal information.
The digital treatment prescription information received from the medical institution system includes one prescription type among single prescription, continuous prescription, and multi-center continuous prescription,
The continuous prescription is issued as a plurality of prescriptions in a medical institution system for one digital therapeutic agent divided into specific cycles,
The multi-center continuous prescription is issued by a plurality of medical institution systems,
The data management module is,
Exchange digital treatment prescription data with the digital treatment server using the DTx one-time code,
An information provision consent processing module that requests information provision consent from the patient terminal to manage patient personal information/prescription information and provide third party information, and receives and stores the result;
Verifies the digital treatment prescription information received from the medical institution system, processes it, stores it as digital treatment prescription data, maps the DTx one-time code with the patient information and the digital treatment prescription data, and provides consent to provide information obtained from the patient terminal. a prescription data processing module that activates the digital treatment prescription data according to availability, provides it upon request from the digital treatment server, and receives and stores results of use of the digital treatment from the digital treatment server; and
It includes a prescription history module that provides a history of previous prescription data linked to continuous prescriptions or multi-center continuous prescriptions at the request of the medical institution system or the digital treatment server,
The prescription data processing module,
Retrieving previously issued continuous prescription data for continuous prescriptions or multi-center continuous prescription data to create and store linkage information to provide a history of issued continuous prescriptions for a specific digital therapeutic product;
Digital therapeutic platform system.
delete delete delete According to clause 1,
If the prescription type of the digital treatment prescription information received from the medical institution system is a multi-center continuous prescription, informed consent is collected so that the digital treatment prescription information can be provided to other medical institution systems, and only if the collected result is consent, Characterized by providing digital treatment prescription history data to medical institutions,
Digital therapeutic platform system.
According to clause 1,
The interface module is,
An interchange API module that provides an interoperable interface for providing at least one of the following functions: inquiry of prescription history information for digital therapeutics, inquiry of prescription information, delivery of prescription and treatment information, and inquiry of prescription result information; and
An authentication API module that provides an interoperable interface for issuing authentication keys, renewing authentication keys, and discarding authentication keys for authentication of the medical institution system and the digital therapeutics server. Including,
Digital therapeutic platform system.
According to clause 1,
The authentication module is,
An institutional authentication module that performs credential authentication for linking with the medical institution system and the digital therapeutics server;
An identity authentication module that requests identity verification in conjunction with an identity authentication system to collect consent to provide information for the use of patient personal information and prescription information, and receives the results; and
Containing a DTx user authentication module that performs patient authentication when using a digital therapeutic delivered to the patient terminal;
Digital therapeutic platform system.
According to clause 1,
Further comprising a FHRI module that processes data exchanged based on FHIR (Fast Healthcare Interoperability Resources),
Digital therapeutic platform system.
A medical institution prescription history provision step in which the digital treatment platform system provides digital treatment prescription history upon request from the medical institution system;
A prescription data processing step in which the digital treatment platform system receives patient information and digital treatment prescription information from the medical institution system, verifies and processes them, and stores them as digital treatment prescription data;
An information provision consent collection step in which the digital therapeutic platform system requests consent to provide information from a patient terminal and receives a result of the request;
A DTx information transmission step in which the digital therapeutic platform system transmits digital therapeutic product access information to the patient terminal;
A DTx prescription history providing step in which the digital treatment platform system provides digital treatment prescription history upon request from a digital treatment server;
A prescription data provision step in which the digital treatment platform system provides digital treatment prescription data according to a request from the digital treatment server; and
A DTx usage result providing step in which the digital therapeutic product platform system receives digital therapeutic product use result information from the digital therapeutic agent server, stores it as usage result data, and transmits the digital therapeutic product use result data to the medical institution system,
Patient information and digital treatment prescription information received from the medical institution system do not include the patient's unique identification information, and digital treatment prescription data transmitted to the digital treatment server does not contain patient personal information.
The digital treatment prescription information received from the medical institution system includes one prescription type among single prescription, continuous prescription, and multi-center continuous prescription,
The continuous prescription is issued as a plurality of prescriptions in a medical institution system for one digital therapeutic agent divided into specific cycles,
The multi-center continuous prescription is issued by a plurality of medical institution systems,
The step of providing the medical institution prescription history is,
Receiving a request for the prescription history of a specific digital therapeutic agent prescribed to a specific patient from the medical institution system, providing the prescription history of previous digital therapeutic agents issued as a continuous prescription or multi-center continuous prescription,
The prescription data processing step is,
In order to identify digital treatment prescription data, a DTx one-time code that does not contain patient personal information is generated and mapped with the patient information received from the medical institution system and the digital treatment prescription data, and previously used for continuous prescription or multi-center continuous prescription data. Search issued continuous prescription data to create and store connection information to provide a history of issued continuous prescriptions for a specific digital treatment,
The above information provision consent collection step is,
Activating the digital treatment prescription data so that the digital treatment server can query the prescription data according to the consent to provide information obtained from the patient terminal,
The DTx prescription history provision step is,
Receiving a request for prescription history of a specific digital treatment prescribed to a specific patient from the digital treatment server, providing a list of previous prescription data linked to continuous prescription or multi-center continuous prescription,
The DTx prescription history providing step, the prescription data providing step, and the DTx usage result providing step are characterized in that digital therapeutic drug prescription data is exchanged using the DTx one-time code,
How to deliver digital therapeutics.
delete According to clause 9,
The step of providing the medical institution prescription history is,
In the case of multi-center continuous prescription, digital treatment prescription history data is provided only when consent to provide third-party information to other medical institutions is collected from the patient terminal.
How to deliver digital therapeutics.
delete