A method and system for visualizing report design

Abstract

The application discloses a kind of visual report design method and system, it is related to Web front-end development technical field, including: user creates dynamic report through Web end, configures medical data source and associated field, to establish the import mapping channel of medical data and report unit;Design report appearance style and static content, the static content includes table header, cell constraint;According to the associated field, report appearance style and static content identify form scene, activate medical scene enhancement function, according to the medical data source content feature, carry out page column design or conditional rendering adaptive setting, output design report.Solve the medical data report form system development cost, research and development standard is not consistent, there is product quality level, product flexibility, poor reusability, weak integration capability technical problem.It is reached in reducing development threshold, while, it guarantees the uniformity of research and development standard, and product flexibility and reusability technical effect.

Description

Technical Field

[0001] This invention relates to the field of Web front-end development technology, and in particular to a visual report design method and system. Background Technology

[0002] Core technologies in web front-end development include foundational technologies such as HTML, JavaScript, and CSS for building user interfaces and interactions; it also involves the design and application principles based on non-linear report models, supporting the dynamic generation and display of complex data structures through flexible data organization methods; it further involves the Java programming language in the back-end technology field, efficient read and write support for multiple databases, data persistence; automated data import and export processing technologies, enabling seamless conversion and migration of multi-format and multi-source data; and version management technologies, used to implement version control and historical traceability of data models, configuration files, and business logic, ensuring system maintainability and stability; and it can achieve efficient data querying, processing, and analysis by combining flexible SQL writing capabilities with high-performance visualization tools.

[0003] In the healthcare IT industry, reports, tables, lists, and invoices are currently mostly implemented and deployed through in-house development by R&D personnel or by abstracting components. These scenarios cover a significant portion of the functionalities and interfaces of healthcare IT systems and are crucial in both system operation (tables, lists) and user productivity (invoices and printing). However, this approach often suffers from high R&D costs, high barriers to entry for R&D personnel, inconsistent development standards, uneven product quality, poor product flexibility and reusability, and weak integration capabilities. Summary of the Invention

[0004] To address the aforementioned technical problems, this application provides a visual report design method and system to solve the technical issues of high development costs, inconsistent R&D standards, uneven product quality, poor product flexibility and reusability, and weak integration capabilities in existing medical data report and document information systems.

[0005] In view of the above problems, this application provides a visual report design method and system.

[0006] In a first aspect, the present invention provides a visual report design method, comprising: a user creating a dynamic report through a web interface, configuring medical data sources and associated fields to establish an import mapping channel between medical data and report units; designing the report appearance style and static content, wherein the static content includes table headers and cell constraints; identifying form scenarios based on the associated fields, report appearance style, and static content, activating medical scenario enhancement functions, and performing page column design or conditional rendering adaptive settings based on the characteristics of the medical data source content, and outputting the designed report.

[0007] Secondly, this invention provides a visual report design system, comprising: a visual configuration module for users to create dynamic reports via a web interface, configure medical data sources and associated fields to establish an import mapping channel between medical data and report units; a form selection design module for designing the appearance style and static content of the report, wherein the static content includes table headers and cell constraints; and a form scene enhancement module for identifying form scenes based on the associated fields, report appearance style, and static content, activating medical scene enhancement functions, and performing page column design or conditional rendering adaptive settings based on the content characteristics of the medical data source, and outputting the designed report.

[0008] One or more technical solutions provided in this application have at least the following technical effects or advantages:

[0009] This invention enables users to create dynamic reports via a web interface, configure medical data sources and associated fields to establish an import mapping channel between medical data and report units, design the report's appearance and static content (including headers and cell constraints), identify form scenarios based on the associated fields, report appearance, and static content, activate enhanced medical scenario functions, and adaptively set page column design or conditional rendering based on the characteristics of the medical data source content, outputting the designed report. This method eliminates the need for R&D coding, providing a visual report designer that allows users to directly design page interactions to develop interfaces and functional logic for reports, tables, lists, and invoices that meet business scenarios. This achieves the technical effect of lowering the development threshold while ensuring unified R&D standards, reliable product quality, and product flexibility and reusability. Therefore, it effectively solves the technical problems of high development costs, inconsistent R&D standards, uneven product quality, poor product flexibility and reusability, and weak integration capabilities in existing medical data report and document information systems.

[0010] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely exemplary. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0012] Figure 1 A flowchart illustrating a visual report design method provided in an embodiment of this application;

[0013] Figure 2 This is a schematic diagram of the structure of a visual report design system provided in an embodiment of this application.

[0014] Attached image labels: 10-Visual configuration module, 20-Form selection design module, 30-Form scenario enhancement module. Detailed Implementation

[0015] This application provides a visual report design method and system, which solves the technical problems of high development cost, inconsistent R&D standards, uneven product quality, poor product flexibility and reusability, and weak integration capabilities in the existing medical data report and document information system.

[0016] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. It should be understood that this application is not limited to the exemplary embodiments described herein. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application. It should also be noted that, for ease of description, only the parts related to this application are shown in the accompanying drawings, not all of them.

[0017] Example 1, as Figure 1 As shown, this application provides a visual report design method, including:

[0018] First, users create dynamic reports via the web interface, configure medical data sources and related fields to establish an import mapping channel between medical data and report units.

[0019] This method allows users to develop reports, tables, lists, and invoices using only a web-based visual design interface. When a user accesses the medical report design platform through a web browser, they first enter the dynamic report creation interface. The system establishes an authentication connection with the hospital information system or laboratory information system via the OAuth 2.0 security protocol, completing the access authentication of the medical data source. The user selects the target medical data table from the tree-like directory provided by the system, such as a laboratory report data table. The platform automatically parses the database structure and generates a list of related fields containing medical business semantics, such as marking the patient ID as a key index field and marking the hemoglobin value as a numerical test indicator with the unit of measurement g / L.

[0020] Furthermore, users can create dynamic reports via the web interface, configure medical data sources and associated fields, and establish an import mapping channel between medical data and report cells. This includes: establishing a follow-binding relationship between a visual mobile identifier and associated fields; moving the associated fields to the report cells based on the follow-binding relationship, and establishing an import mapping channel between medical data and report cells, which is used to import the medical data source into the report cells according to the binding relationship between associated fields and report cells.

[0021] Specifically, after creating a dynamic report and setting the report data source and related fields, users can drag and drop fields to bind them to cells in the design canvas. For example, users can start establishing an import mapping channel between medical data and report cells: by dragging and dropping the "hemoglobin value" field icon to a cell position on the report design canvas, structured binding description information is generated in real time, recording key parameters such as field name, data source location, and display constraints.

[0022] The mapping channel establishment process involves three layers of technology: the front-end binding layer generates a description of the correspondence between fields and cells; the logic control layer analyzes the field characteristics and triggers the corresponding processing mechanism; and the data pipeline layer establishes a real-time data flow from the medical database to the report cells.

[0023] This includes establishing an import mapping channel between medical data and report units, specifically further including:

[0024] Identify the number of entries in the associated field; when the associated field is a multi-entry field, set an expansion direction to constrain the import and fill direction of the associated field; set a parent cell based on the scenario filtering conditions of the associated field to filter the cell data field import based on the parent cell data; set the import mapping channel based on the expansion direction and the parent cell.

[0025] The process of setting a parent cell based on the scenario filtering conditions of the associated fields also includes: setting multi-level filtering conditions based on the scenario filtering conditions of the associated fields; setting parent cell cascading filtering based on the multi-level filtering conditions; and dynamically generating cascading filtering SQL on the backend based on the parent cell cascading filtering.

[0026] Specifically, during the drag-and-drop process and binding with cells in the design canvas, the system automatically detects field characteristics. By analyzing the metadata structure of the medical data source, it automatically identifies the number of entries in the associated field. For example, when the "Routine Blood Test Items" field is associated with a dataset containing 20 test indicators (white blood cell count, red blood cell count, etc.), the system marks it as a multi-entry field. At this point, the expansion direction setting interface is triggered: the user can choose the import fill direction to be downward (vertically fill rows) or to the right (horizontally fill columns). Taking a patient's test report as an example, when the user drags the "Test Items" field to cell B5 and selects "Expand Down," the system automatically generates a cell matrix from B5 to B24, with each row carrying one test indicator.

[0027] When a field is identified as a multi-entry field (e.g., a patient has 20 historical test records), a pop-up panel displays the expansion direction for the user to choose from. When the user selects the "Expand Down" mode, the system automatically creates a dynamic row copy engine, generating 19 data display rows below this cell. For medical data with such multi-entry correlation requirements, the system introduces a parent cell filtering mechanism. To filter row and column data, a parent cell can be set for each cell, and the cell data field will be filtered based on the parent cell data. For example, when the user sets a parent cell for the "Test Results" field, such as binding it to cell A2 for "Patient ID," a scene filtering condition is established: only displaying test results corresponding to the current patient ID. This process involves three layers: Front-end configuration: the user establishes parent-child cell relationships by dragging and dropping, such as the "Test Results" cell pointing to the "Patient ID" cell; Logic generation: the system automatically parses the filtering logic so that the current cell value equals the parent cell value; Back-end execution: dynamically constructs SQL statements, with parameters bound to the A2 cell value in real time.

[0028] It can also establish multi-level parent grids based on the correlation between medical data and the screening conditions, and use the screening relationships between the multiple levels to perform multi-level screening.

[0029] In complex medical scenarios with multi-level medical data filtering conditions, such as in a three-tiered management system of department-doctor-patient, the system supports multi-level filtering conditions. The multi-level parent-cell mechanism achieves precise control by simulating the tree-like relationship of medical data. Multi-level data filtering is performed within the medical reporting system, constructing a hierarchical filtering chain. For example, when a user sets a three-level parent cell for the "Drug Prescription Details" field, the first level "Department" is bound to cell A1, the second level "Doctor" to cell B1, and the third level "Patient" to cell C1. Dynamic relationship mapping is achieved: the department level A1 filters N clinical units across the hospital (e.g., internal medicine, surgery); the doctor level B1 dynamically loads the doctor list based on the department results; and the patient level C1 loads the corresponding patient pool based on the doctor selection. The implementation process is executed through a medical relationship graph. The department-doctor-patient association matrix is ​​pre-loaded, and after triggering the parent-cell cascading filtering, the system generates a cascading SQL engine for parameterized query filtering.

[0030] Next, design the report's appearance and static content, including the header and cell constraints.

[0031] Specifically, during report generation, users can design the appearance and static content of the reports or forms. During the design process, users can insert their own content or select content from a preset report library. This library includes commonly used medical scenario reports and forms. Each scenario type of report or form offers various configuration options for appearance styles, colors, fonts, and structures. It also supports most Excel-like operations, such as merging, freezing, cell style settings, operation rollback, and content clearing. Users can design cell headers and set constraints on content parameters according to the requirements of the designed reports or forms. Header content includes hospital name, logo, department, business name, etc., and constraint settings include cell size, layout structure, cell operation parameters, font, cell spacing rules, canvas layout distribution, cell expansion limits, etc.

[0032] Then, based on the associated fields, report appearance style and static content, the form scenario is identified, the medical scenario enhancement function is activated, and the page column design or conditional rendering adaptive settings are performed according to the content characteristics of the medical data source, and the designed report is output.

[0033] Specifically, in the medical reporting system, the triggering of scene recognition and enhancement functions begins with the intelligent analysis of multi-dimensional features. After the user completes field binding (e.g., "hemoglobin" to cell B5) and sets static content (e.g., diagnostic area constraint ≥40×60mm), the system activates the feature fusion analysis engine. In the scenario-based processing flow of the medical reporting system, the feature fusion recognition engine scans the medical semantic tags of associated fields, such as pre-set medical terms like "test items" and "reference values," combined with specific layout features in the report's appearance, such as vertical double solid lines identifying as document copy separators, frozen first row indicating a long table feature, and the semantic content of the report title extracted from static content (e.g., lab reports, medical records, reimbursement forms, nurse handover orders, etc.), as well as the physical constraint parameters set in the cells, such as the size rule of diagnostic area ≥40×60mm, to construct a decision matrix for the medical scenario. When a field set is detected to contain more than three test-related fields and has a diagnostic area constraint, it is determined to be a medical scenario, and the medical scenario enhancement function module is then activated.

[0034] Based on the identified medical scenario's corresponding form enhancement requirements, corresponding processing is performed, including column segmentation or rendering of test data, generating designed reports. These reports can be viewed visually via the web or further revised and optimized to determine the final design. This eliminates the need for R&D coding, providing a visual report designer that allows users to directly design page interactions and develop interfaces and functional logic for reports, tables, lists, and invoices that meet business scenarios. This achieves the technical effect of lowering the development threshold while ensuring uniform R&D standards, product reliability, and product flexibility and reusability. This solves the technical problems of high development costs, inconsistent R&D standards, uneven product quality, poor product flexibility and reusability, and weak integration capabilities in existing medical data report and document information systems.

[0035] Specifically, the process of identifying form scenarios based on the associated fields, report appearance styles, and static content, and activating the medical scenario enhancement function, includes: performing field analysis on the associated fields to identify medical data scenario characteristics; parsing style attributes based on the report appearance styles to identify the sequential layout; performing semantic analysis of the table headers of the static content to identify scenario constraint requirements, and performing cell constraint analysis to identify print size and format constraints; and integrating and parsing the medical data scenario characteristics, sequential layout, identified scenario constraint requirements, and print size and format constraints to locate the form scenario and scenario enhancement requirements, thereby activating the medical scenario enhancement function.

[0036] Specifically, by utilizing bound data fields and a pre-built medical terminology database, the medical attributes of the fields are identified. This database is set according to industry terminology standards or local standards. For example, if ≥3 LAB_ITEM type fields such as "Test Item" and "Reference Value" are detected, the identification result is: marking a test report scenario (85% confidence level); if fields such as "Drug Name" and "Dosage" are detected, the identification result is: marking a prescription scenario; clinical label parsing: "Hemoglobin" carries a critical value label, establishing and activating a real-time early warning mechanism, etc. This establishes a data type association between fields and identifies the characteristics of medical data scenarios. These characteristics refer to the set of business needs and technical constraints embodied by medical fields in specific clinical scenarios; essentially, they are expressed by mapping the target requirements of medical business processes through field attributes.

[0037] The report is scanned using computer vision algorithms to identify continuous solid lines in the vertical and horizontal directions. Line width constraints include: cutting line width (e.g., setting the width ≥ 2 pixels to avoid confusion with decorative lines); spacing constraints include: spacing between rows (e.g., setting the spacing ≤ 5mm according to the medical insurance invoice industry standard). Based on the identified report format, the distribution of each table style and its report attributes are determined. According to the distribution relationship and style attribute relationship, the row layout is obtained. Row layout refers to the structured design of medical invoice reports that achieves multi-row reuse through physical separation and functional partitioning. Its core is to divide a single invoice into multiple functionally independent and physically separable row areas to meet the needs of multi-party collaboration and archiving in the medical process.

[0038] Deep analysis of static content is performed: The header semantic analysis engine recognizes the title text, such as "pathology diagnosis report," using OCR technology, and calls the natural language processing model to match the pre-set medical scenario keyword library. When words such as "pathology" and "diagnosis" are detected, the constraint requirement of a minimum white space of 40×60mm in the diagnosis area is activated. The synchronously running cell constraint analysis module parses the size and format rules in the design elements, converts user-defined physical constraints, such as the minimum width of 40mm in the diagnosis area, into pixel-level parameters, and extracts the coordinates of the pre-printed area to ensure that the printed output meets the rigid requirements of the medical document standard.

[0039] Based on the obtained medical data scene characteristics, sequential layout, scene constraint requirements, and print size and format constraints, the alignment analysis of each structure of the report is performed to determine the display requirements, printing requirements, and / or scene characteristic requirements of each field of the report canvas structure. The characteristic requirements of each dimension are integrated according to the alignment relationship. Based on the structural positioning of the report and the required content of each positioning structure, the medical scene enhancement function is activated. The medical scene enhancement function is to enhance the display of the report design content for the functional requirements of the report in the medical scene, so as to meet the report design in the medical scene.

[0040] The fusion of each dimension can be calculated using weighted fusion, with feature fusion performed by setting priority weights for each dimension. The system dynamically assigns weights to the recognition results of different dimensions. For example, when ≥3 LAB_ITEM type fields (such as "test item", "reference value", "unit") are recognized and the sequential layout detects "horizontal cutting line + medical insurance code area", the weight of medical data features is increased to 70%, and the weight of sequential layout accounts for 30%, comprehensively determining the feature requirements of the scenario. If there are conflicting requirements in the recognition results, the features with higher priority are adopted first.

[0041] Furthermore, activating the medical scenario enhancement function involves adaptively setting page column design or conditional rendering based on the content characteristics of the medical data source, and outputting a design report. This includes: matching field constraints on the content characteristics of the medical data source based on the form scenario and scenario enhancement requirements; establishing a binding relationship between the page column design or conditional rendering and the data source fields based on the constraint matching relationship, wherein the data source field binding relationship has a scenario enhancement tag; and performing page column design or conditional rendering on the bound data source fields according to the corresponding scenario enhancement requirement parameters based on the scenario enhancement tag.

[0042] Specifically, based on the obtained medical enhancement requirements, the report design structure is refined and implemented for each part. According to the target object of the scenario enhancement requirements, the data source fields are first located, that is, which fields need to be enhanced. Then, according to the specific field constraints, the requirements for column design or rendering are parsed and matched, that is, whether the data source content of the matching relationship needs to be designed in columns or rendered. The data source fields are bound according to the requirement correspondence, the enhancement requirement tags of each data source are determined, and the mapping relationship between the data source and the report structure and the enhancement processing requirements are established using the enhancement tags of the data source fields.

[0043] Example: The scenario involves a user creating an emergency laboratory test report template, with the enhanced requirement being real-time alerts for critical values. To meet this requirement, data source characteristics are analyzed, data source fields are scanned, and field matching relationships are identified: Serum potassium (K+): the terminology matches as LAB_CRITICAL (critical value label); the data type is numeric, and a threshold rule is bound (>5.5 mmol / L triggers an alarm); constraint matching determines the fields, thresholds, and rendering requirements, generating corresponding enhanced labels. When the data source field in the imported report reaches the threshold requirement, an alarm is displayed and rendered to visually represent the alarm data content, generating the corresponding designed report.

[0044] This application also includes:

[0045] Interactive printing optimization instructions, including at least continuous printing optimization instructions, duplex printing optimization instructions, and end-page optimization instructions; based on the printing optimization instructions and the page column design, conditional interaction is performed to determine the printing area and locate the printing layout constraints; according to the printing layout constraints, the field data of the printing area is located by coordinates or the printing parameters are set.

[0046] Specifically, the output process integrates print optimization commands, which users can configure according to their print optimization needs. For scenarios involving continued printing, such as interrupted medical order printing, the system records the breakpoint information, the last page line number plus the page hash, and performs coordinate offset positioning during continuation: canvas elements are converted to print dot matrix coordinates and repositioned based on the offset value. For example, when continuing printing on a shift change, the header is automatically removed and the Y-coordinate of the continuation starting point is calculated as start_Y = last_row / total_rows*page_height, ensuring continuous printing on the same sheet of paper while leaving a 20×15mm handover signature area to avoid paper waste. For duplex printing, the system outputs pages in ascending order for odd-numbered pages and in reverse order for even-numbered pages, such as the page sequence [1,3,5]→[6,4,2], resulting in a 70% reduction in binding misalignment rate in actual tests. End-page optimization dynamically detects blank lines and applies line filtering parameters to skip invalid printing.

[0047] Furthermore, based on the print layout constraints, coordinate positioning or print parameter settings are performed on the field data of the print area, including: when the print optimization instruction is a continuous print optimization instruction, offset coordinate positioning is performed using preset coordinate offset settings; canvas elements are converted into dot matrix coordinates, dot matrix coordinate mapping is performed based on the offset coordinates, and a coordinate positioning relationship between the print area and the canvas is established, wherein the print parameters are set to omit the unified header.

[0048] Specifically, during continuation print optimization, the user selects the continuation print area, including the row and column matrix content. The system identifies the previous print position of the continuation task, locates the continuation position using canvas dot matrix coordinates, and establishes a mapping relationship between the continuation print row and column matrix and the dot matrix coordinate area—that is, the coordinate positioning relationship between the print area and the canvas. The continuation print content is then executed according to this coordinate positioning relationship, while omitting the header content and printing only the continuation print area. Through precise coordinate mapping, intelligent area omission, and deep embedding of medical rules, the system achieves core benefits such as saving paper consumables, increasing continuation print positioning accuracy, and improving clinical efficiency. The system first converts the user-selected continuation print area from canvas coordinates to physical print coordinates using a dot matrix coordinate engine. Based on the breakpoint hash value, it locks the position of the last line of the previous print, calculates the vertical offset, and repositions the continuation print start point to a precise position on the same sheet of paper. Simultaneously activated, the header fingerprint recognition mechanism automatically filters out duplicate header lines.

[0049] Furthermore, after performing the continuation printing positioning, the canvas position of the continuation printing matrix can be identified. When it exceeds the canvas edge, adaptive compression can be performed. For example, when the continuation printing content contains five types of medicines in horizontal columns, adaptive column compression is triggered, with column spacing changing from 5mm to 3mm and intelligent line wrapping (over-wide column line breaks) to ensure that a single sheet of paper carries the maximum amount of information. This achieves the technical effect of improving the efficiency and accuracy of medical document continuation printing through a dual optimization design that utilizes a coordinate mapping engine and optimizes the reuse of blank areas.

[0050] Furthermore, based on the print layout constraints, the field data of the print area are configured with print parameters, including: when the print optimization instruction is a double-sided printing optimization instruction, the print parameter settings include reversing the second print order according to the first print order, wherein the first print order and the second print order are odd and even print orders, respectively.

[0051] Specifically, when executing the duplex printing optimization command, the printing sequence is reconstructed using an odd-even page reverse sorting algorithm to achieve precise alignment of the front and back content after physical binding. First, a first printing order (odd-numbered page sequence) is generated based on the original pagination results; for example, if a medical order form has 6 pages, the output sequence is [P1, P3, P5]. Then, the second printing order (even-numbered page sequence) is reverse-sorted. This avoids inconsistencies in the printing order that require manual adjustment, significantly reducing manual workload and improving printing efficiency, especially important for high-volume printing.

[0052] When the print optimization instruction is a last page optimization instruction, the print parameter settings include a last page specified line filtering parameter, which is used to filter the last page of the print.

[0053] Specifically, when executing the end-page optimization command, the dynamic line filtering engine intelligently compresses blank areas. Its core lies in the precise execution of specified line filtering parameters on the end page. The specific process is as follows: First, the DOM structure of the end page is scanned to identify three types of target lines—completely blank lines (such as unfilled notes lines), decorative dividing lines (placeholders without data), and low-information-density lines (such as cells containing only "No special instructions"). Key lines (such as reserved doctor signature lines) are exempted based on the medical rule base. Filtering parameters take effect according to a tiered strategy: completely blank lines are deleted first (saving 40% of end-page space). By setting filtering parameters for specified lines or blank lines, printing waste caused by printing subsequent blank content is avoided.

[0054] In summary, the present invention has at least the following beneficial effects:

[0055] 1. By using web-based visual design, the development and coding process is eliminated. A visual report designer allows users to directly design page interactions and develop a set of interfaces and functional logic for reports, tables, lists, tickets, and other scenarios that meet business needs. This lowers the development threshold while ensuring the uniformity of development standards, product quality, flexibility, and reusability.

[0056] 2. Through automated data import and export processing technology, seamless conversion and migration of multi-format and multi-source data can be achieved; and version management technology can be used to realize version control and historical traceability of data models, configuration files and business logic to ensure the maintainability and stability of the system; by combining flexible SQL writing capabilities and high-performance visualization tools, efficient data querying, processing and analysis can be achieved.

[0057] 3. Through the medical scenario enhancement function, adaptive enhancement processing is performed on the report design requirements in medical scenarios. The feature automatically identifies scenario characteristics such as test reports and prescription documents, and dynamically injects the enhancement requirements for display, so that the report design can accurately match the clinical scenario and business processing requirements.

[0058] 4. By optimizing printing to meet the printing needs in medical scenarios, it achieves seamless and precise positioning of medical order continuation printing on the same sheet, automatic reverse sorting of double-sided printing to reduce the binding misalignment rate to near zero, and intelligent compression of blank pages at the end to completely eliminate invalid blank pages. This significantly improves the efficiency of medical document execution and reduces consumable costs, while meeting the report design specifications in medical scenarios.

[0059] Example 2, based on the same inventive concept as the visualization report design method in the foregoing examples, such as... Figure 2 As shown, this application provides a visual report design system, wherein the system includes:

[0060] The visual configuration module 10 is used by users to create dynamic reports through the web interface, configure medical data sources and related fields, and establish an import mapping channel between medical data and report units.

[0061] The form selection design module 20 is used to design the appearance style and static content of the report, including the table header and cell constraints.

[0062] The form scenario enhancement module 30 is used to identify the form scenario based on the associated fields, report appearance style and static content, activate the medical scenario enhancement function, perform page column design or conditional rendering adaptive settings based on the content characteristics of the medical data source, and output the designed report.

[0063] Furthermore, the visualization configuration module 10 includes:

[0064] The binding unit is used to establish the following binding relationship between the visual mobile identifier and the associated field.

[0065] The mapping import unit is used to move the associated fields to the report unit based on the following binding relationship, establish an import mapping channel between medical data and report units, and import the medical data source into the report unit according to the binding relationship between the associated fields and report cells.

[0066] Furthermore, the mapping import unit is also used to perform the following steps:

[0067] Identify the number of entries for the associated fields.

[0068] When the associated field is a multi-entry field, set the expansion direction to constrain the import and filling direction of the associated field.

[0069] Based on the scenario filtering conditions of the associated fields, a parent cell is set, which is used to import and filter cell data fields based on the data in the parent cell.

[0070] The import mapping channel is set based on the expansion direction and the parent cell.

[0071] Furthermore, the mapping import unit is also used to perform the following steps:

[0072] Set multi-level filtering conditions based on the scenario filtering conditions of the associated fields.

[0073] Based on the multi-level filtering conditions, set up parent-cell cascade filtering.

[0074] Based on the parent-cell cascading filter, the backend dynamically generates cascading filter SQL.

[0075] Furthermore, the form scenario enhancement module 30 includes:

[0076] The field scene identification unit is used to perform field analysis on the associated fields and identify medical data scene characteristics.

[0077] The style recognition unit is used to parse style attributes and identify sequential layouts based on the appearance style of the report.

[0078] The static scene recognition unit is used to perform semantic analysis of the table header to identify scene constraint requirements and to perform cell constraint analysis to identify print size and format constraints.

[0079] The scene enhancement activation unit is used to integrate and analyze the medical data scene features, sequential layout, identification scene constraint requirements, and print size and format constraints to locate the form scene and scene enhancement requirements, and activate the medical scene enhancement function.

[0080] Furthermore, the form scenario enhancement module 30 is also used to perform the following steps:

[0081] Based on the form scenario and scenario enhancement requirements, field constraint matching is performed on the content features of the medical data source.

[0082] Based on the constraint matching relationship, establish the binding relationship between the page column design or conditional rendering and the data source field, wherein the data source field binding relationship has a scene enhancement tag.

[0083] Based on the scene enhancement tags, the bound data source fields are used for page column design or conditional rendering according to the corresponding scene enhancement requirement parameters.

[0084] Furthermore, the system also includes a printing optimization module for performing the following steps:

[0085] Interactive printing optimization instructions, which include at least continuous printing optimization instructions, duplex printing optimization instructions, and end-page optimization instructions.

[0086] Based on the print optimization instructions and the page column design, the printing area is determined and the print layout constraints are located.

[0087] Based on the print layout constraints, coordinate positioning or print parameter settings are performed on the field data of the print area.

[0088] Furthermore, the printing optimization module is used to perform the following specific steps:

[0089] When the printing optimization instruction is a continuous printing optimization instruction, the offset coordinate positioning is performed using the preset coordinate offset setting.

[0090] Convert canvas elements to bitmap coordinates, perform bitmap coordinate mapping based on offset coordinates, and establish the coordinate positioning relationship between the printing area and the canvas. The printing parameters are set to omit the unified header.

[0091] Furthermore, the printing optimization module is used to perform the following specific steps:

[0092] When the printing optimization instruction is a double-sided printing optimization instruction, the printing parameter settings include reversing the second printing order according to the first printing order, wherein the first printing order and the second printing order are odd and even printing orders, respectively.

[0093] When the print optimization instruction is a last page optimization instruction, the print parameter settings include a last page specified line filtering parameter, which is used to filter the last page of the print.

[0094] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A visual report design method, characterized in that, include: Users can create dynamic reports via the web interface, configure medical data sources and related fields to establish an import mapping channel between medical data and report units; Design the appearance and static content of the report, including the table header and cell constraints; Based on the associated fields, report appearance style and static content, identify the form scenario, activate the medical scenario enhancement function, and based on the content characteristics of the medical data source, perform page column design or conditional rendering adaptive settings, and output the designed report. Users create dynamic reports via the web interface, configuring medical data sources and associated fields to establish an import mapping channel between medical data and report cells, including: Establish a visual binding relationship between mobile identifiers and associated fields; Based on the aforementioned binding relationship, the associated fields are moved to the report unit, establishing an import mapping channel between medical data and report units, which is used to import the medical data source into the report unit according to the binding relationship between the associated fields and report cells; Based on the associated fields, report appearance style, and static content, the form scenario is identified, and the enhanced medical scenario function is activated, including: Field analysis is performed on the associated fields to identify the characteristics of the medical data scenario; Based on the report's appearance style, parse the style attributes and identify the sequential layout; Perform semantic analysis on the header of the static content to identify scenario constraint requirements, and perform cell constraint analysis to identify print size and format constraints; The medical data scenario features, sequential layout, scenario constraints, and print size and format constraints are integrated and analyzed to locate the form scenario and scenario enhancement requirements, and activate the medical scenario enhancement function. Activate the enhanced medical scenario features, and based on the content characteristics of the medical data source, perform adaptive settings for page column design or conditional rendering, and output design reports, including: Based on form scenarios and scenario enhancement requirements, field constraint matching is performed on the content features of the medical data source. Based on the constraint matching relationship, establish the binding relationship between the page column design or conditional rendering and the data source field, wherein the binding relationship of the data source field has a scene enhancement tag; Based on the scene enhancement tags, the bound data source fields are used for page column design or conditional rendering according to the corresponding scene enhancement requirement parameters.

2. The visual report design method according to claim 1, characterized in that, Establish an import mapping channel between medical data and report units, including: Identify the number of entries for the associated fields; When the associated field is a multi-entry field, set the expansion direction to constrain the import and filling direction of the associated field; Based on the scenario filtering conditions of the associated fields, a parent cell is set, which is used to import and filter cell data fields based on the data in the parent cell; The import mapping channel is set based on the expansion direction and the parent cell.

3. The visual report design method according to claim 2, characterized in that, Setting a parent cell based on the scenario filtering conditions of the associated fields also includes: Set multi-level filtering conditions based on the scenario filtering conditions of the associated fields; Based on the aforementioned multi-level filtering conditions, set up a parent-cell cascading filter; Based on the parent-cell cascading filter, the backend dynamically generates cascading filter SQL.

4. The visual report design method according to claim 1, characterized in that, Also includes: Interactive printing optimization instructions, which include at least continuous printing optimization instructions, duplex printing optimization instructions, and end-page optimization instructions; Based on the print optimization instructions and the page column design, the printing area is determined and the print layout constraints are located. Based on the print layout constraints, coordinate positioning or print parameter settings are performed on the field data of the print area.

5. The visual report design method according to claim 4, characterized in that, Based on the aforementioned print layout constraints, coordinate positioning or print parameter settings are performed on the field data of the print area, including: When the printing optimization instruction is a continuous printing optimization instruction, the offset coordinate positioning is performed using the preset coordinate offset setting; Convert canvas elements to bitmap coordinates, perform bitmap coordinate mapping based on offset coordinates, and establish the coordinate positioning relationship between the printing area and the canvas. The printing parameters are set to omit the unified header.

6. The visual report design method according to claim 4, characterized in that, Based on the aforementioned print layout constraints, print parameters are set for the field data in the print area, including: When the printing optimization instruction is a double-sided printing optimization instruction, the printing parameter settings include reversing the second printing order according to the first printing order, wherein the first printing order and the second printing order are odd and even printing orders, respectively. When the print optimization instruction is a last page optimization instruction, the print parameter settings include a last page specified line filtering parameter, which is used to filter the last page of the print.

7. A visual report design system, characterized in that, The system is used to perform the method according to any one of claims 1-6, comprising: The visual configuration module allows users to create dynamic reports via the web interface, configure medical data sources and related fields, and establish an import mapping channel between medical data and report units. The form selection design module is used to design the appearance style and static content of the report, including the table header and cell constraints. The form scenario enhancement module is used to identify form scenarios based on the associated fields, report appearance style and static content, activate the medical scenario enhancement function, and perform page column design or conditional rendering adaptive settings according to the content characteristics of the medical data source, and output the designed report.

Images