JP3189325U - Data processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data processing system capable of compoundly referencing a wide variety of documents, allowing a plurality of staff members to simultaneously edit documents related to the same project, and contributing to team medical care and organizational work styles. SOLUTION: A data process including a plurality of documents recorded according to a predetermined classification and a recording means for recording detailed data corresponding to each item of the document, and an editing means for accessing the recording means and editing them. In the system, the document has at least one item, address information is set in the item, variable length data is stored in the address, the document data is recorded in a unified data format, and the above. The editing means can access the data of the entire document group, and can edit and refer to the data of the items of the document group. [Selection diagram] Fig. 1

Description

  The present invention relates to an electronic document creation device, and in particular, a large number of related documents in a large number of cases, such as medical institutions, schools, administrative institutions, and companies, and a large number of staff members create, edit, and edit various documents. The present invention relates to a data processing system that realizes smooth organizational activities by enabling reference in parallel.

With the expansion of computer usage technology, medical institutions, schools, government agencies, and companies have been introducing document creation devices that use computers instead of paper documents for the purpose of improving work efficiency and speed. ing. In medical institutions, medical records such as medical records such as doctors and nursing records, so-called electronic medical records, as well as medical instructions, are issued by doctors as electronic documents including the date and time of execution and the content of instructions to be performed. In order to clarify accountability, this electronic document is normally authenticated with a password, and the creator and creation date are recorded as non-editable data. Based on this medical instruction document, the medical staff performs a medical practice.
Educational institutions such as schools are also rapidly digitizing documents such as lecture materials, teaching affairs such as exams, and school affairs such as application and permission.
Similarly, in administrative agencies and companies, a wide variety of materials and documents have been digitized to improve the efficiency of paperwork.
Patent Documents 1 and 2 are known as systems for managing and processing such document data.

JP 2010-3125 A JP 2005-18549 A

  Although medical, education, administration, and enterprises all have problems due to common problems, this specification will explain an example of an electronic medical record used in a medical field.

  Since electronic medical records handle enormous amounts of data, special software called database (Data Base Management System) that records, references, and searches data is used. The most used is RDB (Relational Data Base) which records data in a table format (Relation). Relational databases have a relatively simple structure and are capable of high-speed processing. Since a standardized query language called SQL Systemic Query Language has been established from an early stage, not only electronic medical records but also systems that process large amounts of data. It has been used as a standard for a long time.

  A row in the table (record record or tuple tuple) is composed of a group of items designed in advance and represents one item of data. Each item has a predetermined data length (fixed length). Therefore, the data length of one line is also fixed. In the recording file, the next line is recorded from the beginning following the end of the line. When a change such as addition or deletion is added to a group of items constituting one line, the length of one line changes, so the recording file needs to be reconfigured. Reconfiguration after a large amount of data is accumulated requires a large amount of work, so careful design is indispensable at the start of database operation.

  For example, in the basic patient information, the patient ID, name, reading, gender, date of birth, and the like, and the data items necessary for the drug prescription system are drug code, drug name, unit, dose, frequency, instruction, and the like. In the nursing support system, there are a problem number, a problem, a start date / time, an end date / time, etc., and the necessary items are completely different for each department system. It is impossible to process department data with different items with the same relation. Therefore, it was necessary to create and manage separate relations for each department with different items (FIG. 2).

  Conventional electronic medical records have been constructed as a collection of many departmental systems such as a drug prescription system, an injection prescription system, a nursing support system, a radiological interpretation support system, etc. (FIG. 3). Each department system has data in its own format, and the other department systems inquire and respond to data using a standard such as HL-7 (FIG. 4). Each departmental system is highly independent, so it can be developed by hand, and even if it complies with the data exchange standards, user medical institutions can freely combine products from various companies, It should have been possible to build a suitable integrated system in a short period of time at a low cost.

  Furthermore, the relational database several decades ago had a problem that the function such as the index was weak and the operation speed was extremely reduced as the data increased. In order to maintain the operation speed for a long time, it was a preferable form to accumulate and accumulate data for each department. In addition, the medical institutions at that time had thick barriers between occupations, and there were few exchanges on occupations across occupations. Therefore, if there was a department system, it was enough to withstand the work for the staff of that type of job. As described above, the structure of the electronic medical record, which is a group of departmental systems as shown in FIG. 3, is natural and best in the technical environment 20 to 30 years ago, which is the dawn of the electronic medical record. Was the solution.

  However, the situation changed completely in the 21st century. The disease structure associated with the aging of the population has changed, and elderly people who have many diseases at the same time have become subjects of treatment. It has become natural that many occupations such as doctors, nurses, pharmacists, laboratory technicians, rehabilitation staff, etc. collaborate in team medical care. For example, when a pharmacist processes a prescription order, it is necessary to check the appearance of side effects by referring to not only a doctor's article but also a nurse's focus chart, work records of caregivers and rehabilitation staff, and the like. Sharing information among various occupations has become indispensable for optimal medical care and safety management.

  The modern principle of team medicine is team medicine. Rehabilitation staff, registered dietitians, social workers, laboratory technicians, etc., as well as doctors and nurses, can form a team and provide comprehensive medical services to patients, providing highly effective and safe medical services. . In order for team medical care to function effectively, sharing information is a major premise. It is essential to be able to immediately grasp what each job category is thinking, no matter where in the hospital.

  Assuming team medical care, the conventional electronic medical record as shown in FIG. 4 is a collection of departmental systems in which data is distributed and stored in various formats. However, many have occurred. Since departmental systems are enlarged due to excessive functions, or because they are a combination of products from different companies, there are many electronic medical records that operate only one departmental system at a time. In this case, in order to refer to information on other occupations, it is necessary to start up the department system of the occupation to be referred to every several tens of seconds and read the data. After confirmation, you will have to restart the department system for your occupation and restart your work. Since this does not actually work, it tends to be an unconfirmed parting departure. The oversight of important information is a necessary and dangerous situation. Because it is difficult to cross-reference department data, staff members are forced to record all relevant data redundantly for each occupational department as a defensive measure. In this case, it is unavoidable that the recorded contents are inconsistent between departments.

  In one hospital, in order to avoid oversight, the pharmacy manager starts up three PCs at the same time, prescribing treatment with one unit, and checking the doctor's articles and injection prescriptions for the other two units. It is. For occupations that cannot monopolize multiple PCs, the data of another department system is manually re-entered into their department system. This is because two department systems cannot be started up at the same time, and even copy & paste cannot be performed.

  There are many electronic medical records with specifications that proceed with processing after downloading patient data to a terminal PC and recording it on a local hard disk, but in this case there is a risk of leakage of patient personal information due to PC theft. Yes.

  Before discussing the superiority or inferiority of electronic medical records, there are the most basic requirements. It is a function that allows multiple staff members to open a patient's chart at the same time and input medical instructions (orders), articles, etc. in parallel. If you are not satisfied with this feature, you will have trouble. Suppose someone opens a patient chart. When another staff member tries to open the chart for the same patient, a warning such as “This chart is already in use. Open in browse mode” is displayed. In other words, the staff who opened after the second can read (reference) the chart, but cannot input (edit) orders and articles. When it comes to a serious product, it is a specification that can't even be referenced. It will not be much different from the paper medical record era when the staff robbed the charts among the staff.

  From 2008, an additional amount has been added to medical assistants as part of reducing the burden on physicians. In some hospitals, clinical trial assistants have been assigned to outpatients, and trials have started to reduce the outpatient input work of busy doctors. In the electronic medical record lacking the simultaneous input function, the medical assistant cannot open the patient's medical record in the edit mode while the doctor examines and writes the doctor article. For this reason, the doctor's instructions are recorded, and after the doctor's examination is completed, the patient's chart is opened again in the edit mode, and the recorded contents are input. Since the examination scene and the input scene deviate, there is no extreme complexity. The accuracy of the input is difficult to expect. Alternatively, the medical assistant may input everything from the article to the order using the doctor's ID, but it goes without saying that there is a problem in terms of security and legal liability in case of an input error.

  In the past, a prefectural hospital in the San'in region had developed an electronic medical record with a huge amount of subsidies. I have heard a lecture from a hospital official, but remember that there was a strange question and answer with the floor. The question is "How do you handle when the doctor's instructions change during the day?" “Because it is an electronic medical record, if the instructions are changed, all the indications will be rewritten at that moment and it will be natural to continue the work based on the new instructions.” I was surprised. “That's a big problem. The changed instructions are printed out and sent to the nurses in the hospital room by the attending physician and the chief teacher.” Although it did not make sense for several days, I gradually realized that the root cause was the lack of concurrent input capability. If both the doctor's and nurse's PCs are online, there will always be medical records. To prevent this, the nurse's notebook PC was offline after downloading morning instruction data to the notebook PC. At the end of work, the laptop is brought online again, and the records are written back to the server. Even if the instructions are changed, the changes are not reflected on the notebook PC of the nurse who is offline, so the changed part is printed at the nurse station, and the attending physician or the mentor runs to the nurse in charge. . In our hospital's paper chart experience, mistakes occurred four to five times as often as normal changes in instructions in this way. How was this hospital?

  A technical explanation of why parallel input is not possible. As described above, in a relational database supporting an electronic medical record system, data is recorded in a table format, and operations are performed in units of rows in the table. In this case, if multiple records with different contents are written on the same line (when a record conflict occurs), all but one of them will disappear and the consistency of the contents of the entire database will be lost. In extreme cases, the database itself will crash. In order to avoid this problem, the record lock function is used in the database to prohibit rewriting of a record that may cause a conflict. When a staff member opens a patient's chart, this staff may edit, so while this staff member opens the patient's chart, all records for this patient It is locked to the staff and can be referenced, but editing is not possible. This is the reason why parallel input was not possible with the conventional electronic medical chart.

  Questions arise here. Why do I have to lock all records for the patient? Shouldn't it be necessary to lock only one line of the record being edited? Originally, if only the document record being edited is locked, there is no danger of a crash. Usually, because the type of job is divided for each type of document, if only the document that each staff member is currently editing is locked, there is almost no problem in parallel input for other types of job.

  In a conventional electronic medical record consisting of parquet work for department systems, relation data is managed for each department system. In a situation where only one department system can be started up at the same time, and the patient data of that department is downloaded to the terminal PC for editing, other staff to the patient data in the other department system I can not grasp the access status from. In other words, it is the same as offline. In the worst case, the electronic medical record system of the entire hospital will crash if competing writing occurs when editing after downloading and writing back the data. Therefore, as a safety measure, if someone opens a patient's chart in edit mode, all the patient's data must be locked.

  As mentioned above, the best solution was decades ago when modularizing the system for each department, managing the data and software independently for each module, and combining the modules as needed. there were. However, as the way of working at medical institutions has changed, the fact that data is divided and managed by module has become the biggest bottleneck. This is a situation commonly known in the IT industry as a “modularity trap”. The prescription to this problem is the transition to an integrated architecture.

  The present invention has been made to solve such a conventional problem, and the object of the present invention is to refer to a wide variety of documents and to simultaneously reference documents related to the same project by a plurality of staff members. The purpose is to provide a data processing system that enables parallel editing and contributes to team medical care and organized work methods.

  In the data processing system according to claim 1, as means for achieving the object, a plurality of documents recorded in accordance with a predetermined classification and detailed data corresponding to each item of the document are recorded, and the recording means includes A data processing system having an editing means for accessing and editing them, wherein the document has at least one item, address information is set in the item, and variable length data is stored in the address. The document data is recorded in a unified data format, and the editing means can access the data of the entire document group, and can edit and refer to the data of the items of the document group. To do.

  3. The data processing system according to claim 2, wherein information relating to personal information is recorded in the document, and each variable-length data is recorded in association with personal identification information. And

  The data processing system according to claim 3 is characterized in that, in the data processing system according to any one of claims 1 and 2, an access authority authenticating means for permitting access for each document is set.

  In the data processing system according to claim 4, in the data processing system according to any one of claims 1 to 3, the document that is accessed in the edit mode is provided with an access prohibiting unit that prohibits other access. It is characterized by.

  The data processing system according to claim 5 is configured such that the editor and the editing time are recorded accompanying the edited data in the data processing system according to any one of claims 1 to 4.

  According to a sixth aspect of the present invention, there is provided the data processing system according to any one of the first to fifth aspects, wherein style information that defines a display style on the display is set in accordance with a document classification.

In this invention, since the said structure is employ | adopted, it has the following effects.
In the data processing system according to claim 1, since the document has at least one item, address information is set in the item, and variable length data is stored in the address.
An item and a relational database corresponding to the item are configured.
That is, since the document is composed of address information set in the item and variable length data stored in the address, necessary data is collected and stored in variable length data.
Since the document data is composed of a unified data format, the entire data can be handled in an integrated manner, and the data can be referred to and edited smoothly.

  In the data processing system according to claim 2, information relating to personal information is recorded in the document, and each variable-length data is recorded in association with the personal identification information. It is impossible to know the situation, and a data processing system suitable for handling personal information is realized.

  In the data processing system according to the third aspect, since access authority authentication means for determining whether or not to permit access is set for each document, appropriate information management according to the authority of the user is performed.

  5. The data processing system according to claim 4, wherein an access prohibiting means for prohibiting other access is provided for the document accessed in the edit mode, so that simultaneous multiple rewriting of the document is prevented and the document is unified. Sex is secured.

  In the data processing system according to the fifth aspect, the editor and the editing time are recorded along with the edited data. Therefore, the responsibility of each data is clarified.

  In the data processing system according to the sixth aspect, since the style information that defines the display style on the display is set according to the classification of the document, the display style according to the nature of the document is applied and displayed.

It is explanatory drawing of the computer network to which the data processing system of this invention is applied. It is explanatory drawing showing the patient list and medicine list which concern on a prior art example. It is explanatory drawing which shows the data recording method concerning a prior art example. It is explanatory drawing which shows the data recording method by the department system which concerns on a prior art example. It is explanatory drawing which shows a patient list and the recording content of the data. It is explanatory drawing which shows the medicine list and the recording content of the data. It is explanatory drawing which shows the storage mode of the data of the item of a patient list. It is explanatory drawing which shows the database structure of this invention.

The best mode for carrying out the present invention will be described.
As shown in FIG. 1, the data processing system of the present invention is composed of a server that executes a specific process and a client that receives a service from the server. These constitute a network system, and each computer has an input. A device, a control device, a recording device, and the like are provided.
A plurality of computers are connected on the network, and each computer accesses the recording device of the server or the recording device of each computer.

The main data (document group) is recorded in the recording device of the server, but depending on the type of data, it can be recorded by the client computer. The server may be installed at a remote location via the web.
Editing means are installed on the server, client computer, or network, and necessary data is retrieved and aggregated from the data of the server recording means or each recording means connected to the network by commands issued from the client computer. Edit them and present them to the user.
The data processing system is provided with access authority confirmation means, which will be described later, and each staff member at the medical site confirms the authority from the computer at the site and connects to the network.

Hereinafter, specific examples of the present invention will be described.
FIG. 5 and FIG. 6 represent the basic patient information and the drug prescription in the RDB relation format and the XML format, respectively. As mentioned above, each cell of the relational database table: relation must be a fixed-length data set in advance. However, XML-format text data has various lengths (variable length data) and cannot be stored in a relation as it is. Therefore, variable-length XML data is recorded in another recording area, and only a fixed-length address indicating the area in which the XML data is recorded is stored in the relation cell (FIG. 7). In this way, XML data can be processed within the framework of a relational database.

  Such a database is called an XML relational database. In a practical system, if XML is text, processing will be slow, so XML text data is recorded as an object in internal representation (binary format) that can be processed by machine (XML object relational database XML Object Relational Data Base) ). In addition, an index for high-speed processing is prepared. The data amount of the index reaches 4 to 6 times the XML data that is the main body. As a result, it is now possible to process XML data at a high speed that can withstand practical use.

  As described above, all data items of one document can be converted into one XML format data file even if the data item structure for each department is different. Even if the data format of the document is different for each department, if it is converted into XML, it is only one variable length XML file. Therefore, an address indicating all the XML data of a document of the format may be stored in one cell of the relation. In this case, as shown in FIG. 7, all items including the common items such as the patient ID, the document category, the document creation date and the creator, and the actual data item storing the XML data unique to the document are built. The department system data item structure is common and can be easily integrated into one relation. There are also improvements in hardware performance and index performance of XML object relational databases, and it is now more convenient to integrate all electronic medical record data and treat it as a single relation.

Referring to the drawings in detail, FIG. 5 shows a list of information related to individuals, and represents patient ID, reading, gender, date of birth, etc. corresponding to the individual name.
The upper part of FIG. 5 shows a recording format in a conventional relational database, and the lower part of FIG. 5 shows how the upper part of the data is recorded in the XML language.
The area surrounded by the tags in the lower part of FIG. 5 corresponds to one patient, and items such as ID, name, and date of birth are set therein. These data continuously record the personal information of a large number of patients.

The upper part of FIG. 6 is a list of information related to medicines in a recording format in a conventional relational database for each medicine, and represents the form of medicine, usage, etc. (unit, dose, number of times, instructions).
These list data are recorded in the XML language as in FIG. 5, and the lower part of FIG. 6 shows how the upper part of the data is recorded in the XML language.
In the lower part of FIG. 6, an area surrounded by tags corresponds to one medicine, and items such as a medicine name and instructions are set therein. These data continuously record information on a large number of drugs.

FIG. 7 is a table that summarizes information related to individuals.
This table is created in advance in the recording means and created and saved as a document. If necessary, the XML data shown in the lower part of FIGS. 5 and 6 can be created as a list by the editing means.
The editing unit is a unit that accesses the recording unit to search and edit data. The editing unit searches for, retrieves, and creates a list of necessary documents from a group of documents recorded in the recording unit. The list can be created in units of individuals, date units, or other settings according to the purpose. The editing unit obtains, presents, rewrites and saves variable length data recorded in the recording unit.
In FIG. 7, items such as a patient name, basic patient information corresponding to the patient, and a drug prescription are set in one line, and a large number of lines are arranged vertically.
In FIG. 7, basic items such as patient ID, creator ID, creation date and time, and document main items such as patient basic information and drug prescription are set, and the data storage destination address is recorded in each document main item. Has been. Each address stores data corresponding to an item.

  In this way, the address information is recorded in the item of the document subject, and the variable length data is stored in the address. Therefore, all the original document data formats are recorded in a common (unified) data format, They can be selected and collected into a table that you need.

In this embodiment, when a computer is started or when accessing a network, authentication by a user password is performed. This is a means for authenticating the user's access authority. By entering this password, the user is specified, and the user-specific accessible data range is also defined.
For example, some users may be able to access all data, but may be able to access only some data such as drug prescriptions and nursing records.
In addition, the access destination data is set such that it can be accessed in both the edit mode and the reference mode, or can be accessed only in the reference mode.

In this embodiment, an access prohibiting means is provided for prohibiting access to the same document data by another user when access in the edit mode occurs.
This is to prevent the data from being rewritten multiple times at the same time and to lose the unity. For example, when one user is editing the patient basic information document of a patient, Access to the document data in the edit mode is prohibited.
This access prohibition means is set for each document. As an example of the setting method, a flag is set at the beginning of a line representing a document. When this flag is on, access by other users in the edit mode is prohibited.
The user who has accessed the flagged document is informed that editing is in progress, and access is denied or only access in the reference mode is permitted.

The flag of access prohibition means is set for each document. For example, in FIG. 7, even when the flag is set for the patient ID 0001 “Patient basic information”, the “medicine prescription” document for the same patient ID 0001 may not be set.
Similarly, even when a flag is set for “medicine prescription” for patient ID 0002, a flag may not be set for the item “patient basic information” for the same patient ID 0002.
Thus, even for the same patient, a document with a flag and a document with no flag appear in the chart, and access is restricted on a document-by-document basis instead of prohibiting access to the entire individual chart. As a result, it is possible to prevent the editing of the charts by the editor and to perform independent editing for each document.
In other words, since one chart is divided into a plurality of documents, editing such as rewriting can be performed independently for each document.

  In this embodiment, when editing is performed, the editor ID and the editing date and time are recorded in document units. In addition to the editing confirmation, the editor ID and the editing date are written in the respective items. It can be said that it is a more preferable form because it is possible to perform search processing using items easily with processing instructions such as SQL statements, but it is possible to create each tag in XML data without writing items and write directly in the tag good.

  In the present embodiment, each piece of personal information stored in the XML format is recorded in association with individual identification information for each item. Therefore, when referring to or editing in the item unit of the document, the personal name of the data corresponding to the item is specified. Accordingly, during data editing, it is impossible to know who the data is after editing, and a data processing system suitable for handling personal information is realized.

  In this embodiment, various documents for handling personal information are recorded, and various documents are created by the editing means. Each document is set with style information that defines the display style on the display according to the classification. Therefore, although the basic data is centrally managed in the XML format, the data edited by the editing means is presented to the user terminal in a format that is easy to see with a style selected according to the document classification.

As shown in FIG. 4, the conventional department system individually manages data and inquires and responds to data in a format such as HL-7, so that multi-dimensional reference is extremely complicated. However, if the data structure is unified, complicated references can be easily realized by hitting a SQL sentence once.
Also, in the modular structure, there is a tendency to bring in all the data of other modules in an attempt to complete everything in one module. For this reason, there is a problem that data is duplicated in various modules and the consistency thereof is easily lost. When data reference of other departments becomes easy, duplicate data itself becomes unnecessary, and the problem of inconsistency disappears automatically.

  Each department system no longer needs to perform data management independently. As shown in FIG. 8, each department system refers to necessary data from a centralized database (database bus data base BUS) and writes a processing result to the database bus. As a matter of course, the written changes are automatically reflected to other department systems.

  By unifying relational data, it is easy to grasp which document is being edited by who at a certain moment. A document being edited may be locked by setting an edit prohibition flag only on the document. The unreasonable and excessive restriction of prohibiting editing of all the patient's document records as seen in the conventional electronic medical record is not necessary. Since the types of documents to be edited differ depending on the occupation, even if a plurality of occupations open the same patient chart at the same time, the problem of simultaneous editing rarely occurs. In the outpatient department, a medical assistant can input oral instructions simultaneously in the vicinity of the doctor, so that the efficiency of the examination and the accuracy of the input are maintained.

  In addition to the variable length document content data itself, information indicating the following document attributes is indispensable not only for medical institutions but also for education, administration, and companies. (1) What is the document related to, (2) Which category the document belongs to, (3) Who created it, (4) When it was created / edited .

The ID for identifying the case of (1) is a patient ID for a medical institution, a student ID for an educational institution, a resident ID for an administrative institution, a customer ID for a company, or a project ID. and so on. In any case, an appropriate ID may be selected as a group of documents in an environment where the document creation apparatus is used.
(2) The document category ID is a group of documents constituting the case and indicates the type of document. In medical, basic patient information, drug prescriptions, etc., in education, unit registration application, test results, etc., in government, family register copy, resident card, tax payment history, etc. and so on. It goes without saying that the content and format described vary depending on the document category.
(3) The position, type of job, scope of responsibility, etc. vary depending on the staff. Needless to say, in addition to creating and editing unauthorized documents, reference is not permitted in some cases. It is indispensable in the operation of this document creation device to perform personal authentication with a password or the like and specify the access authority of the staff.
(4) The document creation date and time is often a problem due to the legal proof of the document, and must be strictly managed so as not to be falsified.

  Depending on the operating environment of the document creation apparatus, it is useful to save the original document as a history so that the change history can be referred to at any time even if the document is changed or deleted.

  In the embodiment, the variable length document content data is collected into one XML file. However, when the amount is long, it may be divided into a plurality of XML files and recorded. Further, as will be described later, it may be recorded as a plurality of variable length data such as document content data and document format.

  The case ID, document category, creator, creation / editing time, etc., indicating the document attributes are recorded as independent items in the relational database as shown in FIG. Since it can process, it can be said that it is more preferable. However, if the index of XML data that is the substance of variable-length document content data is substantial, in some cases, an arbitrary item indicating an attribute may be included in the variable-length document content XML data.

  In this embodiment, XML, which is considered to be the most versatile, is used as a format for expressing variable-length document content data, but {id: 123456 name: Ichiro Tanaka kana: Ichiro Tanaka sex: male birthday: 19800102} The same effect can be obtained with a format called JSON, in which tag name: value pairs are listed. Also, a format called CSV format in which values are separated by commas “,”, or a format in which document contents are written as text without any internal structure is possible, but it is difficult to create an index. However, this is not necessarily the preferred format.

  In addition to the document content data, information such as the document print format and data format such as data limit values is also important. These format data are also variable length data, but differ depending on the category of the document. Normally, registration of format data is managed in a separate relation in the same manner, and only the format data ID is recorded. However, if there are a wide variety of variations depending on individual documents, this format data is also document-specific, just like document content data. The corresponding XML format file may be recorded and the address to the file may be recorded.

  The present invention may be completed on a single computer in a personal clinic or the like. Usually, a data management computer called a server computer and a plurality of client computers scattered in the field are connected by a network called a LAN. Offered in form. In the future, the form of using virtual server computers built on the Internet via the Internet browser, such as SaaS or cloud, will increase.

  Although the embodiments have been described above, the specific configuration of the present invention is not limited to the above-described embodiments, and design changes and the like within a range not departing from the gist of the invention are also included in the present invention.

Claims (6)

A data processing system comprising a plurality of documents recorded in accordance with a predetermined classification and detailed data corresponding to each item of the document, and an editing means for accessing the recording means and editing them ,
The document has at least one item, address information is set in the item, variable-length data is stored in the address,
The document data is recorded in a uniform data format,
A data processing system characterized in that the editing means can access data of an entire document group, and can edit and refer to data of items in the document group.   2. The data processing system according to claim 1, wherein information relating to personal information is recorded in the document, and each variable-length data is recorded in association with personal identification information.   3. A data processing system according to claim 1, wherein an access authority authentication means for determining whether to permit access for each document is set.   4. The data processing system according to claim 1, further comprising access prohibiting means for prohibiting other accesses to the document accessed in the edit mode.   The data processing system according to claim 1, wherein an editor and an editing time are recorded accompanying the edited data.   6. The data processing system according to claim 1, wherein style information that defines a display style on the display is set in accordance with the classification of the document.