A low-code rapid development method for medical informatization
By integrating medical standard terminology services and a script editor into a rapid development system, the challenges of high professional knowledge requirements, weak business logic support, and compliance in medical information development have been solved, enabling efficient and flexible construction of medical applications and system integration.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHENGDU MEDICAL STAR TECH CO LTD
- Filing Date
- 2026-03-23
- Publication Date
- 2026-06-19
Smart Images
Figure CN122240072A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of medical informatics and software development technology, and in particular to a low-code rapid development method for medical informatics. Background Technology
[0002] In the field of healthcare informatics, the development and iteration of business systems such as integrated Hospital Information Systems (HIS), Electronic Medical Records (EMR), and Laboratory Information Systems (LIS) have long faced significant challenges. Traditional coding development models are time-consuming, costly, and demanding on developers' medical expertise. In recent years, although some low-code platforms have attempted to be applied to healthcare scenarios, they still suffer from the following prominent drawbacks: 1. Weak Support for Medical Business Logic: The visual components and configuration rules of general low-code platforms cannot directly and conveniently express complex medical business rules, such as: automatically associating clinical pathways based on diagnostic codes (ICD-10), dynamically calculating reference ranges based on test results (LOINC codes) and patient age and gender, and complex medical order packages and execution logic. Handling these logics still requires a large amount of backend coding, significantly reducing the value of low-code.
[0003] 2. Difficulty in Integrating Medical Data Standards: Medical data has strict standardization requirements, and existing low-code platforms lack inherent and convenient support for medical data standards. When defining data models, developers find it difficult to directly reference and bind standard terminology systems, and cannot easily achieve standard-based data mapping and conversion with non-standard systems, resulting in poor system interoperability.
[0004] 3. Slow response to specialized and personalized needs: Business processes vary significantly across different departments (e.g., radiology, pharmacy, emergency). General-purpose platforms struggle to quickly abstract and reproduce these specialized process templates. When clinicians request modifications to personalized business processes, relying on the development team to code responses is cumbersome and fails to meet the rapidly changing needs of clinical practice.
[0005] 4. Compliance and auditing requirements are difficult to embed: Medical systems have mandatory requirements for data modification logs, operation auditing, and access control. Applications generated by general low-code platforms often require additional development to meet the audit trail clauses in standards such as the "Evaluation of Functional Application Level of Electronic Medical Record Systems," increasing development complexity and compliance risks. Summary of the Invention
[0006] To address the aforementioned issues, this invention provides a low-code rapid development method for medical information systems. This method enables medical information system developers, as well as business personnel with some IT knowledge, to quickly build medical application modules or systems that conform to medical data standards, embed complex clinical logic, meet compliance requirements, and are easy to integrate through visual modeling combined with dedicated scripts.
[0007] To achieve the objectives of this invention, the following solution is adopted: A low-code rapid development method for medical informatics, employing a rapid development system, the system comprising: A medical data model designer that integrates medical standard terminology services; The medical business script engine has a built-in script editor and an integrated function library. All functions in the function library have a pre-defined relationship with the standard names, attributes and event combinations of medical business entities. A medical workflow orchestrator with built-in flowchart tools; Compliance feature auto-generator; FHIR Interface Generation and Deployment Manager; The method includes the following steps: S100: The medical data model designer receives several medical business entities created by the user, as well as several attributes and events defined for each medical business entity. It then provides the user with a medical standard terminology service. After the user selects from these, it binds a standard name to each medical business entity and automatically generates standard code. S200: The medical business script engine receives all medical business entities from the medical data model designer, matches corresponding functions for each medical business entity through a combination of standard names, attributes, and events using the script editor, and automatically writes business logic scripts using the matched functions. S300: The medical process orchestrator creates business process nodes for each corresponding medical business entity and business logic script. Then, it outputs all business process nodes to the user through a flowchart tool. After the user edits the execution order and judgment logic between the business process nodes, the medical business process is generated. S400: The compliance feature autogenerator integrates multiple compliance features; S500: The FHIR Interface Generation and Deployment Manager automatically compiles all medical business entities, business logic scripts, medical business processes, and compliance features into FHIR resources, encapsulates the FHIR resources into services that provide FHIR interfaces, and generates independent installation packages or Docker images that are integrated with the hospital's existing information platform.
[0008] Furthermore, the medical standard terminology service integrates multiple medical standard terminology dictionaries, including ICD-10, LOINC, and SNOMED CT.
[0009] Furthermore, the medical data model designer provides users with an entity editing interface. In S100, the medical data model designer receives medical business entities created by users through the entity editing interface and provides users with medical standard terminology services through the entity editing interface.
[0010] Furthermore, the medical data model designer provides users with attribute binding interfaces and event binding interfaces. In S100, the medical data model designer receives the attributes and events defined by the user for the medical business entity through the attribute binding interface and event binding interface, respectively.
[0011] Furthermore, the function library includes terminology mapping functions, clinical decision support rule triggering functions, and timeline calculation functions.
[0012] Furthermore, the flowchart tool provides users with a process editing interface, which includes a canvas and a logic editing table. In S300, all business process nodes are output to the user through the process editing interface. The canvas is used by the user to edit the execution order between business process nodes, and the logic editing table is used by the user to edit the judgment logic.
[0013] Furthermore, the types of compliance features include audit logs generated from all data additions and modifications, role-based data access control logic applied to all healthcare business entities, and patient privacy protection prompts and operation confirmation steps embedded before several preset business process nodes.
[0014] Furthermore, the compliance feature auto-generator includes a log generation module, an access control module, and an additional embedding module. In S400, all data additions and modifications are generated as audit logs through the log generation module. All medical business entities apply role-based data access control logic through the access control module. Before business process nodes, patient privacy protection prompts and operation confirmation steps are embedded through the additional embedding module.
[0015] Furthermore, the FHIR interface generation and deployment manager includes an FHIR resource mapping converter and an application packaging and deployment engine. In the S500, the FHIR resource mapping converter is used to compile FHIR resources, and the application packaging and deployment engine is used to encapsulate FHIR resources and generate installation packages or Docker images.
[0016] The beneficial effects of this technical solution are as follows: 1. By embedding medical terminology services and medical data model templates, the development process complies with industry standards from the outset, significantly reducing the upfront investment required for developers' medical expertise and ensuring the standardization and interoperability potential at the data level.
[0017] 2. The medical business script engine provides a powerful and convenient tool for handling flexible and ever-changing clinical rules and calculation logic, enabling medical business logic that originally required complex coding to be quickly configured and modified through scripts, greatly improving development efficiency and flexibility.
[0018] 3. The compliance feature auto-generator ensures that all generated applications automatically have a complete audit trail, access control and privacy protection framework, reducing compliance risks caused by human oversight and simplifying the evaluation and preparation work before the system goes live.
[0019] 4. The FHIR interface generation and deployment manager enables developed application modules to have open interfaces based on the FHIR standard, making it easy to integrate with other FHIR-compliant systems or regional medical information platforms within the hospital, which helps to build an open medical application ecosystem.
[0020] 5. Enable medical staff or IT personnel familiar with departmental operations to directly participate in or even lead the construction and optimization of departmental characteristic applications, quickly respond to clinical needs, and promote the development of medical informatization in a deeper and more specialized direction. Attached Figure Description
[0021] Figure 1 A flowchart illustrating the steps of a low-code rapid development method for medical information systems according to an embodiment of this application is shown.
[0022] Figure 2 The main architecture diagram of the rapid development system according to an embodiment of this application is shown. Detailed Implementation
[0023] To make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be described in detail below. However, the embodiments described in this application are only some embodiments of this application, and not all embodiments.
[0024] A low-code rapid development method for healthcare informatics, employing methods such as... Figure 2 The rapid development system shown includes a medical data model designer, a medical business script engine, a medical process orchestrator, an automatic compliance feature generator, and an FHIR interface generation and deployment manager.
[0025] The medical data model designer integrates a medical standard terminology service, which includes multiple medical standard terminology dictionaries, including ICD-10, LOINC, and SNOMED CT. The medical data model designer provides users with an entity editing interface, attribute binding interface, and event binding interface.
[0026] The medical business script engine has a built-in script editor and an integrated function library. The function library includes terminology mapping functions, clinical decision support rule triggering functions, and timeline calculation functions. All functions in the function library have a pre-defined relationship with the standard names, attributes, and event combinations of medical business entities.
[0027] The medical workflow orchestrator has a built-in flowchart tool that provides users with a workflow editing interface, which includes a canvas and a logic editing table.
[0028] The compliance feature generator includes a log generation module, an access control module, and an additional embedded module.
[0029] The FHIR interface generation and deployment manager includes an FHIR resource mapping converter and an application packaging and deployment engine.
[0030] like Figure 1 As shown, the low-code rapid development method for healthcare informatics is implemented according to the following steps: S100: The medical data model designer receives several medical business entities created by the user through the entity editing interface, as well as several attributes defined by the attribute binding interface and several events defined by the event binding interface for each medical business entity. Then, it provides the user with medical standard terminology services through the entity editing interface. After the user selects from these, it binds a standard name to each medical business entity and automatically generates standard code. S200: The medical business script engine receives all medical business entities from the medical data model designer, matches corresponding functions for each medical business entity through a combination of standard names, attributes, and events using the script editor, and automatically writes business logic scripts using the matched functions. S300: The medical process orchestrator creates business process nodes for each group of corresponding medical business entities and business logic scripts. Then, it outputs all business process nodes to the user through the process editing interface. After the user edits the execution order between the business process nodes through the canvas and the judgment logic through the logic editing table, the medical business process is generated. S400: The compliance feature auto generator integrates multiple compliance features, including generating audit logs from all data additions and modifications in the system through the log generation module, applying role-based data access control logic to all medical business entities through the access control module, and embedding patient privacy protection prompts and operation confirmation steps before several preset business process nodes through the additional embedding module. S500: The FHIR resource mapping converter of the FHIR interface generation and deployment manager automatically compiles all medical business entities, business logic scripts, medical business processes, audit logs, data access control logic, patient privacy protection prompts and operation confirmation links into FHIR resources. Through the application packaging and deployment engine, the FHIR resources are encapsulated into services that provide FHIR interfaces, generating independent installation packages or Docker images that are integrated with the hospital's existing information platform.
[0031] The above are only some of the embodiments listed in this application and are not intended to limit this application.
Claims
1. A low-code rapid development method for medical informatics, characterized in that, A rapid development system is employed, the system comprising: A medical data model designer that integrates medical standard terminology services; The medical business script engine has a built-in script editor and an integrated function library. All functions in the function library have a pre-defined relationship with the standard names, attributes and event combinations of medical business entities. A medical workflow orchestrator with built-in flowchart tools; Compliance feature auto-generator; FHIR Interface Generation and Deployment Manager; The method includes the following steps: S100: The medical data model designer receives several medical business entities created by the user, as well as several attributes and events defined for each medical business entity. It then provides the user with a medical standard terminology service. After the user selects from these, it binds a standard name to each medical business entity and automatically generates standard code. S200: The medical business script engine receives all medical business entities from the medical data model designer, matches corresponding functions for each medical business entity through a combination of standard names, attributes, and events using the script editor, and automatically writes business logic scripts using the matched functions. S300: The medical process orchestrator creates business process nodes for each corresponding medical business entity and business logic script. Then, it outputs all business process nodes to the user through a flowchart tool. After the user edits the execution order and judgment logic between the business process nodes, the medical business process is generated. S400: The compliance feature autogenerator integrates multiple compliance features; S500: The FHIR Interface Generation and Deployment Manager automatically compiles all medical business entities, business logic scripts, medical business processes, and compliance features into FHIR resources, encapsulates the FHIR resources into services that provide FHIR interfaces, and generates independent installation packages or Docker images that are integrated with the hospital's existing information platform.
2. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The medical standard terminology service integrates multiple medical standard terminology dictionaries, including ICD-10, LOINC, and SNOMEDCT.
3. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The medical data model designer provides users with an entity editing interface. In S100, the medical data model designer receives medical business entities created by users through the entity editing interface and provides users with medical standard terminology services through the entity editing interface.
4. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The medical data model designer provides users with attribute binding interfaces and event binding interfaces. In S100, the medical data model designer receives the attributes and events defined by the user for the medical business entity through the attribute binding interface and event binding interface, respectively.
5. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The function library includes terminology mapping functions, clinical decision support rule triggering functions, and timeline calculation functions.
6. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The flowchart tool provides users with a process editing interface, which includes a canvas and a logic editing table. In S300, all business process nodes are output to the user through the process editing interface. The canvas is used by the user to edit the execution order between business process nodes, and the logic editing table is used by the user to edit the judgment logic.
7. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The types of compliance features include audit logs generated from all data additions and modifications, role-based data access control logic applied to all healthcare business entities, and patient privacy protection prompts and operation confirmation steps embedded before several preset business process nodes.
8. The low-code rapid development method for medical informatization according to claim 7, characterized in that, The compliance feature generator includes a log generation module, an access control module, and an additional embedding module. In S400, all data additions and modifications are generated as audit logs through the log generation module. All medical business entities apply role-based data access control logic through the access control module. Patient privacy protection prompts and operation confirmation steps are embedded before business process nodes through the additional embedding module.
9. The low-code rapid development method for medical information systems according to claim 1, characterized in that, The FHIR interface generation and deployment manager includes an FHIR resource mapping converter and an application packaging and deployment engine. In the S500, the FHIR resource mapping converter is used to compile FHIR resources, and the application packaging and deployment engine is used to encapsulate FHIR resources and generate installation packages or Docker images.