CN117577259A - Method for generating lightweight document suite based on Libreoffice - Google Patents
Method for generating lightweight document suite based on Libreoffice Download PDFInfo
- Publication number
- CN117577259A CN117577259A CN202410062283.6A CN202410062283A CN117577259A CN 117577259 A CN117577259 A CN 117577259A CN 202410062283 A CN202410062283 A CN 202410062283A CN 117577259 A CN117577259 A CN 117577259A
- Authority
- CN
- China
- Prior art keywords
- data
- document
- data element
- suite
- array
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000013507 mapping Methods 0.000 claims description 10
- 238000013459 approach Methods 0.000 claims description 3
- 230000003542 behavioural effect Effects 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000002604 ultrasonography Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000000605 extraction Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 210000001015 abdomen Anatomy 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 210000004204 blood vessel Anatomy 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 208000015181 infectious disease Diseases 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Computing Systems (AREA)
- Public Health (AREA)
- Medical Informatics (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Epidemiology (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for generating a lightweight document suite based on Libreoffice, which comprises the following steps of S1, creating an ODT document based on Libreoffice according to clinical requirements, wherein the document consists of a data element node list and typesetting patterns, and IDs in the data element nodes are mapped with clinical projects; s2, converting the ODT document into lightweight package JSON format data through an odtToWebDocument interface, synchronously updating clinical data into the package data through a fileContentDeValue method of a package object, and introducing the package into a device terminal to generate a lightweight document package for writing by doctors; s3, carrying out structured storage on the data sheet of the ODT document, wherein the data sheet is an SQL data sheet of a database, and comprises transverse storage and longitudinal storage which are used for printing files by doctors.
Description
Technical Field
The application relates to the field of data processing, in particular to a method for generating a lightweight document suite based on Libreoffice.
Background
In clinical business, medical care needs writing various non-medical records besides writing medical record records. In the traditional system, a corresponding writing interface is manufactured for a specific document, and then a set of storage logic is realized, so that the method cannot randomly modify the expansion content, a page is required to be manufactured again and a program is required to be reissued for different writing requirements, the customization requirement is also required to be realized by modifying codes, and the method is very unfriendly from the aspects of development and implementation, has very large code maintenance workload and is not flexible.
Therefore, a mode similar to medical record documents is hoped, different writing requirements can be met by manufacturing various writing templates, complex business in medical record writing is not needed, lightweight document writing kits (IDES) of various systems can be supported, synchronous updating of basic data is realized, full-structured storage of data is realized, and extraction of various data is facilitated.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides a method for generating a lightweight document suite based on LibreOffice.
According to an aspect of the present invention, a method for generating a lightweight document suite based on LibreOffice is provided, including:
s1, creating an ODT document based on LibreOffice according to clinical requirements, wherein the document consists of a data element node list and a typesetting style, and IDs in the data element nodes are mapped with clinical projects;
s2, converting the ODT document into lightweight package JSON format data through an odtToWebDocument interface, synchronously updating clinical data into the package data through a fileContentDeValue method of a package object, and introducing the package into a device terminal to generate a lightweight document package for writing by doctors;
s3, carrying out structured storage on the data sheet of the ODT document, wherein the data sheet is an SQL data sheet of a database, and comprises transverse storage and longitudinal storage which are used for printing files by doctors.
Further, the ODT document also includes XML-formatted data of a combination of style and document data.
The ODT document is converted into lightweight suite JSON format data through an odtToWebDocument interface, and the interface is realized by a back end;
and synchronously updating the clinical data into the data of the suite by the fileContentDeValue method of the suite object, wherein the method is also realized by a back end.
The suite is embodied as a front-end component and enables storage of data, and the suite object is embodied as a behavioral approach created in the suite.
Further, the specific steps of the lateral storage include:
the data element nodes and the transverse data table are subjected to ID mapping to generate a document template;
recording and storing the document template newly built by the user, wherein a data element node list is acquired through getDeList () during storing, and a data element object is acquired after traversing the data element node list;
and carrying out transverse structural dump on the data in the data element object by utilizing the sql grammar.
The longitudinal storage concrete steps comprise:
acquiring Doc objects of a document, and acquiring all table object lists in the document by using a getAllStructureTable DataList () method of the Doc objects, wherein the table objects are JSON data;
traversing the table object list, analyzing data attributes in the JSON data, wherein the data is a row array, and acquiring table object array data if the row array element is not empty;
acquiring a data element object array according to an interface getCells (), acquiring data element object array data if the data element object array element is not empty, and performing ID mapping on the table object array data and the data element object array data to generate a table dump list;
traversing the data element object array to obtain a JSON array of data element code ID, value and value code combination, combining the JSON array with the transversely stored ID, inserting the JSON array into the form dump fine table in batches, and completing the structural storage of form entry.
The above technical solutions in the embodiments of the present application have at least one of the following technical effects:
the invention provides a method for flexibly and quickly generating a customized form lightweight document suite based on a Libreoffice document, and the core of the method is that forms can be quickly generated according to clinical customization demands, and the functions of synchronous updating of basic data, full-structured storage of data, preview printing and the like are realized, and the realization process comprises the following two links:
1) The ODT document template is converted into a lightweight sleeve and front-end loading is realized, the editor sleeve is provided with a template, and the front-end can complete loading of the editor sleeve by simply introducing relevant document template information.
2) The editing suite is internally provided with a set of perfect structured dump mechanism, and only document IDs are required to be bound in the application layer, other structured content editing suites are realized, the application layer basically does not need repeated processing of data structuring, and only template making and application effects are required to be concerned.
Drawings
The accompanying drawings are included to provide a further understanding of the embodiments and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments and together with the description serve to explain the principles of the invention. Many of the intended advantages of other embodiments and embodiments will be readily appreciated as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.
FIG. 1 shows a flow diagram of generating a lightweight document suite based on Libreoffice, according to an embodiment of the invention;
FIG. 2 illustrates a form template terminal loading diagram in accordance with a specific embodiment of the present invention;
FIG. 3 illustrates a schematic diagram of a structured dump flow implemented by a lightweight document suite according to a specific embodiment of the invention;
FIG. 4 illustrates a lateral ID mapping template diagram in accordance with a specific embodiment of the present invention;
FIG. 5 illustrates a vertical representation of a dump tab according to a specific embodiment of the invention.
Detailed Description
The present application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
FIG. 1 is a schematic flow chart of generating a lightweight document package based on LibreOffice according to an embodiment of the invention, and the specific steps include:
step S1, creating an ODT document based on LibreOffice according to clinical requirements, wherein the document consists of a data element node list and a typesetting style, and IDs in the data element nodes are mapped with clinical projects;
in this embodiment, the data element node includes editing various attributes in the following format:
{
DeId: "DE10.00.001"// coding
ID is "20200325-161028886000000-1774542872"// data element unique ID
value: "woman",// data element value
code: "1"// data element encoding
type: "input",// node type
title: "name"// node title
...
}
The mapping of the ID in the data element node with the clinical item may be embodied in embodiments in which CT is mapped with an examination application form or in which aids is mapped with an infection report card.
S2, converting the ODT document into lightweight package JSON format data through an odtToWebDocument interface, synchronously updating clinical data into the package data through a fileContentDeValue method of a package object, and introducing the package into a device terminal to generate a lightweight document package for writing by doctors;
the ODT document also includes XML-formatted data of a combination of style and document data.
The ODT document is converted into lightweight suite JSON format data through an odtToWebDocument interface, and the interface is realized by a back end;
and synchronously updating the clinical data into the data of the suite by the fileContentDeValue method of the suite object, wherein the method is also realized by a back end.
The suite is embodied as a front-end component and enables storage of data, and the suite object is embodied as a behavioral approach created in the suite.
The external member is essentially a front-end component, based on a unit of function division, the external member object is a specific behavior method defined in the component, and the corresponding external member object can be called to complete the corresponding function.
The method for introducing the kit into the equipment terminal in this embodiment is as follows:
this.$refs.idesEditorView.initEditor(documentInfo,deOutData,tableInfo);
wherein the documetInfo format is as follows:
documentInfo: {
the template class code is '2',// template class id, which can not be transmitted
the templateId is '329',// template id
documetId:',// document id, space time indicates new creation
}
If the written document is opened, the documetid cannot be empty;
if a document is created, the templateId cannot be empty.
Wherein deOutData may be null, and if other node data except the basic information is to be updated, the service layer obtains data and transmits the data to the suite component, and node mapping update is performed in the suite component. If the patient gender map data element "DE10.00.001", the incoming deOutData format is as follows:
[{
deId: "DE10.00.001",
value: "women",
code: "1"
}]
where tableInfo may be empty, essentially filling in the table data information. The data elements of each longitudinal node of the table information are identical, and if the table information is updated according to the deOutData data element list, the contents of the data elements are identical, so that the table nodes are updated in other ways. The generated table is shown in fig. 2 in the following format:
{
"tableId": "testTable",
"tableName": "table 1",
"dataList": [
{
"no": 1,
"name" abdomen ultrasound routine examination (appendix) ".
},
{
"no": 2,
"name" heart color Doppler ultrasound "
},
{
"no": 3,
"name" neck blood vessel color Doppler ultrasound "
}
]
}
Each business layer needs to make templates as above, make project and template ID mapping, front end operate related business, and load components to quickly multiplex lightweight document suite.
S3, carrying out structured storage on the data sheet of the ODT document, wherein the data sheet is an SQL data sheet of a database, and comprises transverse storage and longitudinal storage which are used for printing files by doctors.
The realization of the structured dump of the lightweight document suite is mainly convenient for the extraction and the utilization of data, the structured dump needs to be carried out on all data element nodes of a document, a transverse or longitudinal key-value table is supported to be stored, and the whole editing suite is stored as shown in fig. 3, and the specific flow is as follows:
the transverse storage method specifically comprises the following steps:
the data element nodes and the transverse data table are subjected to ID mapping to generate a document template, as shown in FIG. 4;
and recording and storing the document template newly built by the user, wherein a data element node list is acquired through getDeList () during storing, and a data element object is acquired after traversing the data element node list. In this embodiment, the data element object is as follows:
{
deId: "DE10.00.001",
value: "women",
code: "1"
}
and carrying out transverse structural dump on the data in the data element object by utilizing the sql grammar. In this embodiment, the statement that the sql syntax implements dump is:
insert into the transverse dump table (document ID, field 1, field 2, value (document ID, value 1, value 2.)
The longitudinal storage concrete steps comprise:
acquiring Doc objects of a document, and acquiring all table object lists in the document by using a getAllStructureTable DataList () method of the Doc objects, wherein the table objects are JSON data;
traversing the table object list, analyzing data attributes in the JSON data, wherein the data is a row array, and acquiring table object array data if the row array element is not empty;
acquiring a data element object array according to an interface getCells (), acquiring data element object array data if the data element object array element is not empty, and performing ID mapping on the table object array data and the data element object array data to generate a table dump list;
traversing the data element object array to obtain a JSON array of data element code ID, value and value code combinations, as shown in fig. 5, in this embodiment, the codes are as follows:
{
deId: "DE10.00.001",
value: "women",
code: "1"
}
and combining with the transversely stored IDs, inserting the JSON arrays into the form dump list in batches, and finishing the structured storage of the form entry.
After all the data are stored, the user can open again and modify again next time, and the structured data are subjected to deletion-before-insertion mode, so that the continuous structured storage of the document is completed, and the full structured dump of the document suite is realized.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments described in the present application may be implemented by software, or may be implemented by hardware.
The foregoing description is only of the preferred embodiments of the present application and is presented as a description of the principles of the technology being utilized. It will be appreciated by persons skilled in the art that the scope of the invention referred to in this application is not limited to the specific combinations of features described above, but it is intended to cover other embodiments in which any combination of features described above or equivalents thereof is possible without departing from the spirit of the invention. Such as the above-described features and technical features having similar functions (but not limited to) disclosed in the present application are replaced with each other.
Claims (8)
1. A method for generating a lightweight document suite based on LibreOffice, comprising the steps of:
s1, creating an ODT document based on LibreOffice according to clinical requirements, wherein the document consists of a data element node list and a typesetting style, and IDs in the data element nodes are mapped with clinical projects;
s2, converting the ODT document into lightweight package JSON format data through an odtToWebDocument interface, synchronously updating clinical data into the package data through a fileContentDeValue method of a package object, and introducing the package into a device terminal to generate a lightweight document package for writing by doctors;
s3, carrying out structured storage on the data sheet of the ODT document, wherein the data sheet is an SQL data sheet of a database, and comprises transverse storage and longitudinal storage which are used for printing files by doctors.
2. The method according to claim 1, characterized in that: the ODT document also includes XML-formatted data of a combination of style and document data.
3. The method according to claim 1, characterized in that: the ODT document is converted into lightweight suite JSON format data through an odtToWebDocument interface, and the interface is realized by a back end;
the clinical data is synchronously updated into the data of the suite through the fileContentDeValue method of the suite object, and the method is also realized by the back end.
4. A method according to claim 3, characterized in that: the suite is embodied as a front-end component and enables storage of data, and the suite object is embodied as a behavioral approach created in the suite.
5. The method according to claim 1, characterized in that: the transverse storage method specifically comprises the following steps:
the data element nodes and the transverse data table are subjected to ID mapping to generate a document template;
recording and storing the document template newly built by the user, wherein a data element node list is acquired through getDeList () during storing, and a data element object is acquired after traversing the data element node list;
and carrying out transverse structural dump on the data in the data element object by utilizing the sql grammar.
6. The method according to claim 1, characterized in that: the longitudinal storage concrete steps comprise:
acquiring Doc objects of a document, and acquiring all table object lists in the document by using a getAllStructureTableData List () method of the Doc objects, wherein the table objects are JSON data;
traversing the table object list, analyzing data attributes in the JSON data, wherein the data is a row array, and acquiring table object array data if the row array element is not empty;
acquiring a data element object array according to an interface getCells (), acquiring data element object array data if the data element object array element is not empty, and performing ID mapping on the table object array data and the data element object array data to generate a table dump list;
traversing the data element object array to obtain a JSON array of data element code ID, value and value code combination, combining the JSON array with the transversely stored ID, inserting the JSON array into the form dump fine table in batches, and completing the structural storage of form entry.
7. A computer readable medium, having stored thereon a computer program which, when executed by a processor, implements the method of any of claims 1-6.
8. A computing system comprising a processor and a memory, the processor configured to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410062283.6A CN117577259B (en) | 2024-01-16 | 2024-01-16 | Method for generating lightweight document suite based on Libreoffice |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410062283.6A CN117577259B (en) | 2024-01-16 | 2024-01-16 | Method for generating lightweight document suite based on Libreoffice |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117577259A true CN117577259A (en) | 2024-02-20 |
| CN117577259B CN117577259B (en) | 2024-04-09 |
Family
ID=89862927
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410062283.6A Active CN117577259B (en) | 2024-01-16 | 2024-01-16 | Method for generating lightweight document suite based on Libreoffice |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117577259B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106845054A (en) * | 2015-12-04 | 2017-06-13 | 北大医疗信息技术有限公司 | Electronic health record edit methods and system based on HTML5 |
| CN107895590A (en) * | 2017-11-27 | 2018-04-10 | 深圳中兴网信科技有限公司 | Process record figure automatic drafting method, device, equipment and medium |
| US20200219593A1 (en) * | 2017-12-31 | 2020-07-09 | Snapiot Inc | Automatic self-documentation in a mobile-native clinical trial operations system and service suite |
| CN112417836A (en) * | 2020-11-27 | 2021-02-26 | 智业软件股份有限公司 | Automatic table generation method, terminal equipment and storage medium |
| CN114118018A (en) * | 2021-11-25 | 2022-03-01 | 福建博思软件股份有限公司 | Implementation mode of cross-platform electronic report |
| CN114691712A (en) * | 2022-03-23 | 2022-07-01 | 智业软件股份有限公司 | Method and device for generating bill and storage medium |
| CN114817341A (en) * | 2022-06-30 | 2022-07-29 | 北京奥星贝斯科技有限公司 | Method and device for accessing database |
| CN115146584A (en) * | 2022-07-06 | 2022-10-04 | 成都成电医星数字健康软件有限公司 | Full-structured Web version electronic medical record editor system |
| CN117238433A (en) * | 2023-11-10 | 2023-12-15 | 智业软件股份有限公司 | Method for automatically isolating document data based on Libreoffice |
-
2024
- 2024-01-16 CN CN202410062283.6A patent/CN117577259B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106845054A (en) * | 2015-12-04 | 2017-06-13 | 北大医疗信息技术有限公司 | Electronic health record edit methods and system based on HTML5 |
| CN107895590A (en) * | 2017-11-27 | 2018-04-10 | 深圳中兴网信科技有限公司 | Process record figure automatic drafting method, device, equipment and medium |
| US20200219593A1 (en) * | 2017-12-31 | 2020-07-09 | Snapiot Inc | Automatic self-documentation in a mobile-native clinical trial operations system and service suite |
| CN112417836A (en) * | 2020-11-27 | 2021-02-26 | 智业软件股份有限公司 | Automatic table generation method, terminal equipment and storage medium |
| CN114118018A (en) * | 2021-11-25 | 2022-03-01 | 福建博思软件股份有限公司 | Implementation mode of cross-platform electronic report |
| CN114691712A (en) * | 2022-03-23 | 2022-07-01 | 智业软件股份有限公司 | Method and device for generating bill and storage medium |
| CN114817341A (en) * | 2022-06-30 | 2022-07-29 | 北京奥星贝斯科技有限公司 | Method and device for accessing database |
| CN115146584A (en) * | 2022-07-06 | 2022-10-04 | 成都成电医星数字健康软件有限公司 | Full-structured Web version electronic medical record editor system |
| CN117238433A (en) * | 2023-11-10 | 2023-12-15 | 智业软件股份有限公司 | Method for automatically isolating document data based on Libreoffice |
Non-Patent Citations (2)
| Title |
|---|
| KLAASSE, JR (KLAASSE, JILL R.): "TraceBase; A database structure for forensic trace analysis", 《SCIENCE & JUSTICE》, 15 July 2021 (2021-07-15) * |
| 杨家钰: "医院智慧办公系统设计与应用", 《中国数字医学》, 15 December 2023 (2023-12-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117577259B (en) | 2024-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109086199B (en) | Method, terminal and storage medium for automatically generating test script | |
| CN104350494A (en) | Providing assistance with reporting | |
| CN112463149B (en) | Software-defined satellite-oriented reusable code library construction method and device | |
| CN112417836A (en) | Automatic table generation method, terminal equipment and storage medium | |
| CN116089126A (en) | Method, device and equipment for acquiring data in real time and readable storage medium | |
| CN104598437B (en) | The dynamic realizing method of header information in electronic health record | |
| CN117577259B (en) | Method for generating lightweight document suite based on Libreoffice | |
| CN114691712A (en) | Method and device for generating bill and storage medium | |
| CN114238527A (en) | Data processing method and data processing device based on object relation mapping | |
| CN113094039B (en) | Automatic code generation system based on database table | |
| CN112364619B (en) | User-defined form generation method, terminal equipment and storage medium | |
| CN109840078B (en) | Method and device for collaboratively editing hierarchical metadata | |
| CN116069330A (en) | Middle and background template construction method, device and storage medium | |
| CN109960590A (en) | A method of optimization embedded system diagnostic printing | |
| JP3758282B2 (en) | Information retrieval device | |
| CN111223555B (en) | DICOM expansion method for medical image artificial intelligence auxiliary diagnosis result representation | |
| CN114860668A (en) | Online dynamic generation method and device for data file | |
| CN114724665A (en) | BS version-based electronic medical record splitting method for multi-end written medical record | |
| CN113961569A (en) | Medical data ETL task synchronization method and device | |
| CN113177696A (en) | Method and system for generating controlled file template of medicine quality system | |
| CN111276222A (en) | Method for continuously converting medical image file into jpg mapping file based on python | |
| CN112506506B (en) | Method, device, equipment and medium for configuring pages of electronic medical record browser | |
| CN116226066B (en) | Low code platform code synchronization method and device, electronic equipment and storage medium | |
| CN109522216A (en) | Team's interface exploitation cooperative system and method based on API testing tool export data | |
| CN113205881A (en) | Thinking-guidance-graph-based OpenEHR prototype and template automatic generation method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |