KR101087272B1 - An apparatus for editing a clinical contents model and computer readable recording medium with program therefor - Google Patents

Abstract

An apparatus for editing a clinical content model according to the present invention includes an entity representing a disease name, symptom, disease, treatment or prescription, a qualifier constituting detailed components of the entity, and the qualifier. A memory for storing user interface data constituting a user interface screen for inputting / outputting edit information of a set value corresponding to the memory; An input unit to receive the edit information; A central processing unit which controls the editing of the entity, the quality and the setting value by using the editing information input through the input unit; An output unit for outputting the editing information according to the control of the central processing unit; A clinical content model database for storing editing information of the clinical content model under control of the central processing unit; A qualifier database for storing editing information of the qualifier under the control of the central processing unit; And a setting value database for storing the edited information of the setting values according to the control of the central processing unit, wherein the central processing unit includes any one or more of registration, search, modification, storage, and deletion of the quality and the setting values. By performing the edit control, a tool for authoring a clinical content model does not directly edit XML, but automatically generates and edits a clinical content model in XML format with a simple screen manipulation.

Description

An apparatus for editing a clinical contents model and computer readable recording medium with program therefor}

The present invention relates to an authoring tool of a clinical content model, and more particularly, to an apparatus for editing an XML-based clinical content model, so that a user who cannot write XML can easily create and edit a clinical content model in XML format. It is a technique to do.

The present invention is derived from a study conducted as part of a health technology R & D project of the Ministry of Health, Welfare and Family Affairs and Seoul National University Industry-Academic Cooperation Foundation. [Task Management No .: A050909, Title: Electronic Health Record Architecture, Integrated Medical Terminology System, Clinical Decision Support System]

The Clinical Content Model (CCM) logically organizes clinical data, making it easier and more accurate to support patient data entry, as well as recycling input data (clinical decision support, research analysis, clinical document authoring, etc.). Means the model to In recent years, the medical community has been increasing interest in clinical content models that are useful for combination and disassembly and are highly recyclable for obtaining and utilizing rich and accurate patient information.

By the way, there is no application program for authoring a reusable clinical information model of clinical information unit, and the reality is that the author writes with the help of a computer programmer at the request of a medical staff. Although there are tools for authoring a clinical element model in the Intermountain healthcare center in the US and achetype for openEHR in Australia, authoring tools that require professional authors by analyzing XML tags. Is nothing. Therefore, a general user who does not have the knowledge to parse the XML tag has a problem that can not author the clinical content model.

The technical problem to be solved by the present invention is to edit the clinical content model and the computer for recording the program for the clinical content model that can create and edit the clinical content model in XML format by simple screen manipulation, without directly editing XML. To a recording medium.

In order to achieve the above object, the apparatus for editing a clinical content model according to the present invention is an entity representing a disease name, symptom, disease, treatment or prescription, and a qualifier constituting detailed components of the entity. A memory for storing user interface data constituting a user interface screen for inputting and outputting edit information of a Qualifier and a set value corresponding to the Qualifier; An input unit to receive the edit information; A central processing unit which controls the editing of the entity, the quality and the setting value by using the editing information input through the input unit; An output unit for outputting the editing information according to the control of the central processing unit; A clinical content model database for storing editing information of the clinical content model under control of the central processing unit; A qualifier database for storing editing information of the qualifier under the control of the central processing unit; And a setting value database for storing the edited information of the setting values according to the control of the central processing unit, wherein the central processing unit includes any one or more of registration, search, modification, storage, and deletion of the quality and the setting values. The editing control is performed.

In order to achieve the above object, a computer-readable recording medium recording a program according to the present invention is an entity for editing the entity representing the name, symptoms, diseases, treatment or prescription of the clinical content model Editing module; And a qualifier constituting a detailed component of the entity and a qualifier and a set value editing module for editing a set value corresponding to the qualifier, and the qualifier and the set value. It is characterized by performing one or more edit control of registration, search, modification, storage and deletion.

According to the present invention, a user who cannot write XML can easily create and edit a clinical content model in XML format.

In addition, it is free and easy to set up a hierarchy between models with simple operation, and there is no need to limit the number of steps when setting up a lower hierarchy.

In addition, the clinical content model can be used in the field of standard development such as an electronic medical record system, medical information system, clinical information model.

Hereinafter, an apparatus for editing a clinical content model according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an exemplary embodiment for explaining an apparatus 100 for editing a clinical content model according to the present invention. The memory 110, the input unit 112, the output unit 114, the central processing unit 120, and the clinical unit are described. It is composed of the content model database 130, the quality database 140 and the setting value database 150.

The memory 110 may include an entity representing a disease name, a symptom, a disease, a treatment or a prescription, a qualifier constituting detailed elements of the entity, and a setting value corresponding to the qualifier. ) Stores user interface data constituting a user interface screen for inputting and outputting edit information.

An entity refers to a clinical concept that is intended to be expressed as a disease name, symptoms, disease, treatment or prescription. For example, an entity refers to clinical concepts such as "cold", "flu", "cough", "headache", "abdominal pain", and the like. Qualifier means a modifier to describe an entity in detail. For example, if an entity is called "abdominal pain," the quality of the entity corresponding to the entity is "subject", "occurrence", "pain site", "severity", and "pain characteristics". do. The set value represents the corresponding value of the qualifier to clearly modify this entity. For example, if the entity is "abdominal pain" and the quality is "severe", the setting value is divided into "mile", "moderate", and "severe", and the item can be selected in duplicate. The memory 110 stores data constituting a user interface screen for inputting or outputting such edited information, and outputs the data according to an access request of the central processing unit 120.

The input unit 112 receives edit information of an entity, a qualifier, and a set value. When the central processing unit 120 displays a user interface screen for inputting edit information through the output unit 114, the user refers to the user interface screen, and displays an entity, a qualifier, and a set value. ), And the input unit 112 receives the edit information selected by the user. An example of the input unit 112 for receiving the edit information includes a keyboard, a mouse, and a touch screen.

The output unit 114 displays a user interface screen for inputting editing information under the control of the central processing unit 120. When the user inputs the information for editing the clinical content model through the input unit 112 described above, the output unit 114 displays the edited information under the control of the central processing unit 120. An example of such an output unit 114 may include a liquid crystal display (LCD), and may be configured to work with the touch screen function of the input unit 112 described above.

The central processing unit 120 controls the editing of entities, qualifiers, and setting values using the edit information input through the input unit 112. Edit control of entities, qualifiers, and set values is described below.

The central processing unit 120 performs one or more edit control of registering, searching, modifying, storing, and deleting an entity. 2 illustrates a user interface screen for explaining entity editing control of the central processing unit 120. As shown in FIG. 2, the central processing unit 120 accesses data of a user interface screen for editing an entity stored in the memory 110 to control editing of an entity, and thus outputs a user interface screen to the output unit 114. Control to display. Accordingly, a new entity may be generated through a user interface screen displayed on the output unit 114, or may be read and checked for the existence of an existing entity when searching for existing entity information and registering a new entity, and storing and storing the entity. You can also delete it.

3 illustrates a user interface screen for explaining an entity registration function. As shown in FIG. 3, the central processing unit 120 registers information on an entity name, model name, synonyms, model type, entity definition, entity code, database code, creation date, etc. as information for registering an entity. For controlling the display of the user interface screen. The entity name is expressed as a representative term corresponding to the entity. The Model name defines the name in the form of “Entity name + Value Representation Type.” Synonym means a synonym for the name of the entity. The Model Type indicates the type of clinical content model. Model types can be distinguished by a panel, a simple statement, etc. A panel means a clinical content model composed of two or more entities, and a simple statement means a clinical content model composed of a single entity. An entity definition is a definition and description of an entity, which is an entity unique identifier (ID), an entity mapping code (a standard term code that maps to a concept corresponding to an entity). And entity mapping system (a standard terminology that maps to concepts that correspond to an entity). Refers to the code of the Data Dictionary (DD) that maps to the concept corresponding to the tee.Write Date refers to the date of automatic system creation.

4 illustrates a user interface screen for explaining a search function of an entity. As shown in FIG. 4, an existing entity may be read or may be read after checking an existing entity stored in a clinical content model database (CCM Repository 130).

Meanwhile, the central processing unit 120 may perform any one or more edit control of registering, searching, modifying, storing, and deleting a qualifier and a value set.

Data constituting a user interface screen that enables the quality and setting values to be edited in one screen is stored in the memory 110. Accordingly, the central processing unit 120 controls the output unit 114 to output a user interface screen that allows the quality and setting values to be edited on one screen. To this end, the central processing unit 120 controls the interworking of the quality database 140 and the setting value database 150, which will be described later.

FIG. 5 illustrates a user interface screen for explaining the quality control and setting value editing control of the central processing unit 120. As shown in FIG. 5, the central processing unit 120 accesses data of a user interface screen for editing the quality and setting values stored in the memory 110 to control the editing of the quality and setting values. Control to display the user interface screen on the output unit 114. Accordingly, new quality and setting values may be generated through the user interface screen displayed on the output unit 114, and existing quality and information may be generated when retrieving existing quality information and setting values and registering new quality and setting values. You can check the existence of the settings and read them. You can also save and delete the quality and settings.

The central processing unit 120 may display information on a user interface screen for registering information on a quality name, a label, a quality definition, a quality code, a database code, a quality weight, and a creation date. To control. The Qualifier name is expressed as a representative term corresponding to the Qualifier. Label is an alias of Qualifier and can be set in terms that are easy to understand. Qualifier definition includes the definition and description of the Qualifier in English or Korean. Qualifier codes include Qualifier IDs, Qualifier Mapping Codes (standard term codes that map to Qualifier concepts), and Mapping Code System (Qualifier) concepts. Standard terminology to be mapped). Database code refers to code of a data dictionary (DD) mapped to a concept corresponding to a quality. The quality weight means the weight of the value that the quality can have. In addition, the HL7 Data Type refers to the HL7 datatype of the Value of the corresponding Qualifier.

In addition, the central processing unit 120 is a user interface screen for registering information on a setting value name, basic setting value, setting value unit, setting value definition, setting value code, data type, etc. as information for registering the setting value. To control the display. 6 shows an example of a user interface screen for registration of basic setting values.

The set value name is represented by a representative term corresponding to the set value. The default value refers to a default value that the corresponding qualityifier may have, and the default value UI refers to a basic user expression that the corresponding value may have. In addition, the set value unit means a unit that the set value can have, and the set value count means the total number of set values that the set value can have. The value code includes a standard term code mapped to a concept corresponding to a set value and a value code system which is a standard term system mapped to a concept corresponding to a set value. The label can be set as an alias of the setting value or a term easily understood by the user. A check box indicates a setting value selected by a user from a setting value obtained from the setting value database 150.

As shown in FIG. 5, the central processing unit 120 controls whether existing quality is present when retrieving existing quality information or registering a new quality. That is, the central processing unit 120 displays a list of qualifiers stored in the qualifier database 140, and if the user selects the control unit, the central processing unit 120 displays the information of the selected qualifier on the output unit 114. In addition, the central processing unit 120 modifies the contents of the existing qualifier or generates and stores a new qualifier. The modified and generated qualifiers are stored in the qualifier database 140. In addition, the central processing unit 120 controls the change of information, such as the deletion of the existing quality fire.

Meanwhile, the central processing unit 120 controls whether the existing setting value exists when searching for the existing setting value or registering the new setting value. That is, the central processing unit 120 displays a list of setting values stored in the value set database 150, and when the user selects the control unit, the central processing unit 120 controls to display information on the selected setting value. In addition, the central processing unit 120 modifies the contents of the existing setting values, or generates and stores new setting values. The modified and generated setting values are stored in the setting database 150. In addition, the central processing unit 120 controls change of information such as deletion of existing setting values.

The central processing unit 120 provides a user interface screen so that the quality and setting values can be edited on one screen, and controls the interworking of the quality database 140 and the setting value database 150. The central processing unit 120 selects a desired setting value from the setting value database 150 and controls the connection to the corresponding quality fire. In this case, the central processing unit 120 may selectively configure the set value. FIG. 7 illustrates a user interface screen for explaining the interworking of the quality database 140 and the set value database 150. As shown in FIG. 7, it can be seen that the setting value selected from the setting value database 150 is connected to the corresponding quality fire.

Meanwhile, the central processing unit 120 may control editing of hierarchies among entities, qualifiers, and setting values. 8 illustrates an example of a UI screen for editing a hierarchy between entities, qualifiers, and setting values. The central processing unit 120 accesses data of a user interface screen for hierarchical editing between entities, qualifiers, and setting values stored in the memory 110 for hierarchical editing control between entities, qualifiers, and setting values. Accordingly, the control is performed to display the user interface screen on the output unit 114. As shown in FIG. 8, the central processing unit 120 may select and edit various combinations of entities, qualifiers, and setting values through a hierarchical structure editing screen. This user interface screen has various menu bars for editing the hierarchical structure.

The central processing unit 120 controls the interworking of the quality database 140 when modifying the quality required for the hierarchical structure editing between entities, the qualifier, and the setting value, and the setting value database 150 when the setting value is modified.

Meanwhile, the central processing unit 120 may control the hierarchical structure editing for each entity. It is a function for editing the hierarchical structure of each entity in the same manner as the hierarchical structure editing between the above-described entities, qualifiers, and setting values. The central processing unit 120 is in charge of editing control for forming a panel structure, a section for supporting a template, and managing a hierarchy when generating a template. Panels are another form of clinical model that consists of two or more entities. In other words, when one entity is an atom, the panel is the concept of a molecule composed of several atoms. New panels can be created by querying existing entities. A template can consist of several entities and multiple panels, and a template means a formalized, electronically-processable (ie computer-enabled) clinical form. The section means each item that forms the template corresponding to the clinical form. A template consists of several sections, which are logical units of this. After querying the previously created template, you can create and save it as another template after making some changes, and create and save a new template by querying and selecting the previously created entities and panels. Each of these inquiries and creation can be done by simple clicking and dragging the mouse.

On the other hand, the central processing unit 120 may control the classification editing by any one of the clinical region, model structure and set value expression type of the clinical content model. 9 illustrates an example of a user interface screen for classification editing according to a type of clinical content model. The central processing unit 120 may be configured by clinical area, model structure (for example, panel, simple statement, etc.) or set value expression type (for example, Assert, Measurement, Evaluation, Administration, Procedure, etc.) through a user interface screen. You can control editing.

Clinical areas can be classified into Observation (Order or diagnosis) and Order (Prescription). Examples of clinical areas include clincal observation, medication, laboratory, assessement, measurement, and procedure. A panel refers to a clinical content model consisting of two or more entities, and a simple statement refers to a clinical content model consisting of a single entity. Assert means the value indicating the patient's condition, Measurement indicates the measurement of the test performed on the patient and has a numeric value, and Evaluation evaluates the patient's condition. Administration represents the medicine prescribed to the patient, and the drug code is the value. Procedure represents the treatment received by the patient, and the treatment name is the value. When the user selects the desired item after searching the hierarchy, edited contents of the hierarchy are displayed as shown in FIG. 9.

The central processing unit 120 controls to store the clinical content model in a template format of XML (Extensible Markup Language). 10 illustrates an example of a user interface screen for generating a template of a clinical content model. The central processing unit 120 controls to generate a clinical format template in XML format through a combination of clinical content models through interworking with the clinical content model database 130. The central processing unit 120 allows a user to conveniently adjust and configure a hierarchical structure such as a section in a template through a hierarchical editing menu or dragging a mouse. Save the template in this XML format. 11 shows an example of a template in XML format. By saving the clinical content model as a template form of XML, it is possible to automatically generate a webform for input of the doctor information based on the template generated through the combination of the clinical content model. 12 illustrates an example of a web form for a pseudo information input screen. A combination of clinical content models can be used to create a template corresponding to a clinical document, which can be used as a screen for doctors to enter information, so that a user can search for and drag and drop the clinical content model. The result is made.

The clinical content model database 130 stores the edited information of the clinical content model under the control of the central processing unit 120. The clinical content model database 130 stores an entity, a qualifier connected to the entity, and a setting value corresponding to the qualifier. The qualifier is generated and stored with reference to the information of the qualifier database 140, and the setting value is generated and stored with reference to the information of the setting value database 150. In addition, the clinical content model database 130 stores information including entity name, entity definition, entity code, and creation date as information for registering an entity. Meanwhile, the clinical content model database 130 may classify and store the generated clinical content models into a clinical domain, a model type, or a value representation type. FIG. 13 is a diagram illustrating an example of a clinical content model classified by clinical regions stored in a clinical content model database, and FIG. 14 is a diagram illustrating an example of a clinical content model classified by model types stored in a clinical content model database. FIG. 15 is a diagram illustrating an example of a clinical content model classified according to a set value expression type stored in a clinical content model database. As shown in FIG. 15, the configuration may be classified and stored according to the detailed types of Assertion, Measurement, Evaluation, Administration, and Procedure for each set value expression type. The clinical content model database 130 stores data in an XML file format.

The quality fire database 140 stores the edit information of the quality fire under the control of the central processing unit 140. The quality database 140 stores information including a quality name, a quality definition, a quality code, and quality weight as information for registering the quality. 16 is a diagram illustrating an example of a clinical content model stored in a quality database. The Qualifier Database 140 stores data in an XML file format. The Qualifier database 140 is structured to interwork with the setting value database 150 under the control of the central processing unit 120.

The setting value database 150 stores edit information of setting values according to the control of the central processing unit 120. The setting value database 150 stores information including setting value names, basic setting values, setting value units, setting value definitions, setting value codes, and data types as information for registering setting values. FIG. 17 illustrates an example of a clinical content model stored in the setting database 150. The setting database 150 stores data in an XML file format. The setting value database 150 is linked to the quality database 140 under the control of the central processing unit 120.

On the other hand, the above-described editing apparatus of the clinical content model of the present invention may be implemented as a computer-readable code / instructions (instructions) / program. For example, it may be implemented in a general-purpose digital computer for operating the code / instructions / program using a computer-readable recording medium. The computer-readable recording medium includes storage media such as magnetic storage media (eg, ROM, floppy disk, hard disk, magnetic tape, etc.), optical reading media (eg, CD-ROM, DVD, etc.) .

FIG. 18 illustrates the modularization of each function performed by the computer-readable recording medium 200 that records a program for performing each function, and includes an entity editing module 210, a qualifier, and a setting value editing module ( 220), a first hierarchical editing module 230, a second hierarchical editing module 240, and a clinical classification classification editing module 250.

The entity editing module 210 edits an entity representing a disease name, a symptom, or a disease constituting the clinical content model. The entity editing module 210 may create a new entity through a user interface screen for editing an entity, and may check and read the existence of an existing entity when searching for existing entity information and registering a new entity, and may read and store the entity. You can also delete it.

The entity editing module 210 performs any one or more of registering, searching, modifying, storing, and deleting an entity. In particular, the entity editing module 210 registers information including entity name, entity definition, entity code, and creation date as information for registering an entity.

The qualifier and setting value editing module 220 edits a qualifier constituting detailed elements of the entity and a setting value corresponding to the qualifier. The quality fire and setting value editing module 220 performs at least one of registration, search, modification, storage, and deletion of the quality and the setting value. In particular, the quality and setting value editing module 220 registers information including a quality name, a quality definition, a quality code, and a quality weight as information for registering the quality. In addition, the qualifier and setting value editing module 220 registers information including setting value names, basic setting values, setting value units, setting value definitions, and setting value codes as information for registering setting values.

The quality and setting value editing module 220 may generate new quality and setting values through a user interface screen for editing and controlling the quality and setting values, searching for existing quality information and setting values, and searching for new quality. Fire and setting values can be read and checked for the existence of existing quality fires and setting values, and the quality and setting values can be saved and deleted.

The quality and setting value editing module 220 provides a user interface screen for editing the quality and setting values in one screen, and interworking of the quality and the value database 150 of FIG. To control.

The first hierarchical editing module 230 performs hierarchical structure editing for each entity.

The first layer editing module 230 is in charge of forming a panel structure for an entity, a section for supporting a template, and managing a hierarchy when generating a template. The first layer editing module 230 may query an existing entity to generate a new panel. Templates can consist of multiple entities and multiple panels, and templates are formalized and electronically processed clinical forms. The first hierarchical layer editing module 230 edits a panel, a template section, a template hierarchy management, etc. for the entity by simple clicking and dragging the mouse.

The second hierarchical editing module 240 performs hierarchical structure editing between entities, qualifiers, and setting values. The second hierarchical editing module 240 displays a user interface screen for hierarchical editing between entities, qualifiers, and setting values, and edits by various combinations of entities, qualifiers, and setting values through the hierarchical editing screen. Do this. To this end, the second hierarchical editing module 240 provides various menu bars for hierarchical structure editing, as shown in FIG. 10. The second hierarchical editing module 240 performs interworking with the quality database 140 and the setting value database 150 to edit the hierarchical structure between the entity, the quality and the setting value.

The clinical classification editing module 250 performs classification editing by any one of the clinical region, the model structure, and the set value expression type of the clinical content model. Editing module 250 for each clinical classification is classified by clinical area, model structure (for example, panel, simple statement, etc.) and set value expression type (for example, Assert, Measurement, Evaluation, Administration, Edit the procedure, etc.)

The entity editing module 210, the quality and setting value editing module 220, the first hierarchy editing module 230, the second hierarchy editing module 240, and the classification classification editing module 250 are each used for the clinical content model. Stores information in a template format of XML (Extensible Markup Language). The entity editing module 210, the quality and setting value editing module 220, the first layer editing module 230, the second layer editing module 240, and the classification classification editing module 250 are each a combination of clinical content models. Create and save a clinical form template in XML format.

Such an apparatus for editing a clinical content model and a computer-readable recording medium recording a program therefor have been described with reference to the embodiments shown in the drawings for clarity of understanding, but these are merely exemplary and are typical in the art. Those skilled in the art will understand from this that various modifications and equivalent other embodiments are possible. Therefore, the true technical protection scope of the present invention will be defined by the appended claims.

1 is a block diagram of an embodiment for explaining an apparatus for editing a clinical content model according to the present invention.

2 illustrates a user interface screen for explaining entity editing control of the central processing unit.

3 illustrates a user interface screen for explaining an entity registration function.

4 illustrates a user interface screen for explaining a search function of an entity.

5 illustrates an example of a user interface screen for explaining the quality control and setting value editing control of the central processing unit.

6 shows an example of a user interface screen for registration of basic setting values.

FIG. 7 illustrates a user interface screen for explaining the interworking of the quality database and the set value database.

8 illustrates an example of a UI screen for editing a hierarchy between entities, qualifiers, and setting values.

9 illustrates an example of a user interface screen for classification editing according to a type of clinical content model.

10 illustrates an example of a user interface screen for generating a template of a clinical content model.

11 shows an example of a template in XML format.

12 illustrates an example of a web form for a pseudo information input screen.

FIG. 13 is a diagram illustrating an example of a clinical content model classified by clinical regions stored in a clinical content model database.

14 is a diagram illustrating an example of a clinical content model classified by model type stored in a clinical content model database.

15 is a diagram illustrating an example of a clinical content model classified according to a set value expression type stored in a clinical content model database.

16 is a diagram illustrating an example of a clinical content model stored in a quality database.

17 is a diagram illustrating an example of a clinical content model stored in a setting database.

18 shows a module of each function performed by a computer-readable recording medium that records a program for performing each function.

Claims (20)

Editing information of an entity representing a disease name, symptom, disease, treatment or prescription, a qualifier constituting detailed elements of the entity, and a setting value corresponding to the qualifier A memory for storing user interface data constituting a user interface screen for inputting / outputting the data; An input unit to receive the edit information; A central processing unit which controls the editing of the entity, the quality and the setting value by using the editing information input through the input unit; An output unit for outputting the editing information according to the control of the central processing unit; A clinical content model database for storing editing information of the clinical content model under control of the central processing unit; A qualifier database for storing editing information of the qualifier under the control of the central processing unit; And A setting value database for storing editing information of the setting value according to the control of the central processing unit; And the central processing unit controls editing of at least one of the registration, search, modification, storage, and deletion of the qualifier and the setting value. The method of claim 1, wherein the central processing unit And editing control of at least one of registration, search, modification, storage and deletion of the entity. The method of claim 2, wherein the clinical content model database is Editing apparatus for a clinical content model, characterized in that the information for registration of the entity, including information including the entity name, entity definition, entity code, creation date. delete The method of claim 1, wherein the quality database is And information including a name of a quality, definition of a quality, definition of a quality code, a weight of a quality, and a weight of a quality as an information for registering the quality. The method of claim 1, wherein the set value database is And information including a set value name, a basic set value, a set value unit, a set value definition, and a set value code as information for registering the set value. The method of claim 1, wherein the central processing unit And editing a hierarchical structure for each of the entities. The method of claim 1, wherein the central processing unit And editing the hierarchical structure between the entity, the qualifier, and the set value. The method of claim 1, wherein the central processing unit The apparatus for editing a clinical content model, characterized in that the classification editing is controlled by any one of the clinical region, the model structure, and the set value expression type of the clinical content model. The method of claim 1, wherein the central processing unit And an apparatus for controlling the clinical content model to be stored in a template format of XML (Extensible Markup Language). An entity editing module for editing an entity representing a disease name, symptom, disease, treatment or prescription constituting a clinical content model; And Record a program for functioning a qualifier constituting the detailed components of the entity and a qualifier and a set value editing module for editing a set value corresponding to the qualifier, A computer-readable recording medium having recorded thereon a program for performing at least one edit control of the qualifier and the set value. The method of claim 11, A computer-readable recording medium having recorded thereon a program for performing at least one of registration, search, modification, storage and deletion of the entity. The method of claim 12, A computer-readable recording medium having recorded thereon a program for registering information including an entity name, an entity definition, an entity code, and a creation date, as information for registering the entity. delete The method of claim 11, A computer-readable recording medium having recorded thereon a program for registering information including a quality name, a quality definition, a quality code, and a quality weight as information for registering the quality. The method of claim 11, A computer-readable recording medium having recorded thereon a program for registering information including setting value names, basic setting values, setting value units, setting value definitions, and setting value codes as information for registering the setting values. The method of claim 11, A first hierarchical editing module for performing hierarchical editing for each of the entities; A computer-readable recording medium having recorded thereon a program for operating the first layer editing module. The method of claim 11, And a second hierarchical editing module configured to perform hierarchical editing between the entity, the qualifier, and the set value. A computer-readable recording medium having recorded thereon a program for operating the second layer editing module. The method of claim 11, It further comprises a clinical classification editing module for performing classification editing to any one of the clinical region, model structure and the set value expression type of the clinical content model, A computer-readable recording medium recording a program for operating the clinical classification module. The method of claim 11, A computer-readable recording medium recording a program expressed in a template format of XML (Extensible Markup Language).

Images