Image output management method for medical images
By generating output event records containing key information and using hash digests and QR code technology, the accuracy and reliability issues of image output records in existing technologies are solved, and the traceability and immutability of image output behavior are achieved.
Patent Information
- Application Number
- CN202511560321.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-29
- Publication Date
- 2026-03-17
AI Technical Summary
Existing medical image output management methods lack key data such as patient identification, examination number, and DICOM image identification, resulting in output records not being able to accurately correspond to specific image content, posing risks of duplicate registration and tampering, and lacking reliable traceability credentials.
The system generates output event records containing operator identifiers, department identifiers, patient identifiers, examination numbers, DICOM image identifiers, etc., and uses globally unique numbers for deduplication. It combines SHA-256 hash digest data and WORM media preservation integrity index, and embeds QR codes for tamper-proof traceability.
It achieves context binding, content consistency, and visual auditing of image output behavior, ensuring the accuracy and immutability of output records and providing a stable traceability foundation.
Smart Images
Figure CN121687409A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of medical information management technology, and more specifically to an image output management method for medical images. Background Technology
[0002] In the daily clinical activities of medical institutions, DICOM format imaging data is a crucial foundation for various medical examinations and diagnoses. After generation, imaging data typically needs to be output to different media, such as CDs, films, printed reports, or external network terminals, for use in clinical consultations, referrals, and medical record archiving. To ensure smooth workflow, medical institutions generally deploy image output management solutions to receive output requests from systems such as PACS, RIS, and HIS, and to perform the packaging, conversion, output, and recording of image content locally.
[0003] Existing methods typically generate basic output logs upon receiving an output request and transmit image files to the target carrier or target network location, enabling cross-departmental access and cross-node distribution of image content. They can also record information such as operator identification, workstation identification, and output timestamps, providing basic event traceability capabilities. Some methods also aggregate output logs through a centralized archiving system to support workload statistics and process auditing within the hospital.
[0004] However, these methods generally have three shortcomings: First, the output logs only contain partial contextual information and lack key data such as patient identification, examination number, and DICOM image identifiers, making it impossible to accurately correspond the output records to specific image content and hindering precise traceability afterward. Second, output log records are often generated directly based on operation events and lack deduplication and integrity verification mechanisms, making them prone to duplicate registrations under network jitter or repeated requests, affecting the consistency and verifiability of the records. Third, the log file content can be modified or deleted later, lacking tamper-proof storage and visual association identifiers, and failing to provide stable traceability evidence for image output behavior. Summary of the Invention
[0005] To address the aforementioned technical problems, this invention provides an image output management method for medical imaging.
[0006] An image output management method for medical images, the method comprising: S11, based on the image output request record output context parameters, generate an output event record containing operator identifier, department identifier, patient identifier, examination number, DICOM image identifier, output type, output target address, workstation identifier and output timestamp, and write a globally unique number generated based on the timestamp into the output event record; S12, filter unregistered records by comparing the global unique number with the local cache index, generate deduplicated output event records, and write the deduplicated output event records sequentially into the cache log file; S13, generate a number string based on the globally unique number of the output event record in the cache log file, and perform SHA-256 operation based on the number string to generate batch hash digest data; S14. Generate integrity index data based on batch hash digest data, number range, generation time and execution node number, and write the integrity index data into the WORM medium for storage. At the same time, write the physical offset address of the integrity index data into the corresponding output event record. S15, write the integrity index data and its referenced output event records into the audit database, generate a QR code based on the globally unique number of the records already in the database, and embed the QR code into the output carrier.
[0007] 2. The image output management method for medical images according to claim 1, characterized in that the step of generating output event records is as follows: S111: By receiving the image output request record, the operator identifier, department identifier, and workstation identifier are extracted to obtain the operator context parameters; S112, extract patient identifier, examination number and DICOM image identifier by parsing the image output request record to obtain image content parameters; S113, based on the operator context parameters and image content parameters, write the output type, output target address and output timestamp to generate an output event record; S114. Generate a globally unique number based on the output timestamp and write it to the output event record.
[0008] Furthermore, the logic for generating a globally unique ID in the output event record is as follows: S114.1, Perform a concatenation operation based on the output timestamp and the operator identifier to obtain the initial number string; S114.2 Calculate the CRC check code using the initial number string and generate the check number segment; S114.3, concatenate the initial number string with the check number segment to obtain a globally unique number.
[0009] Furthermore, the step of generating the deduplicated output event record is as follows: S121, generate a cache number index by reading the globally unique number of all output event records in the cache log file; S122, compare the globally unique number with the cache number index, filter out the output event records that are not registered in the cache number index, and obtain the unregistered records; S123, based on the unregistered records, sort them in chronological order, generate deduplicated and output event records; S124, write the deduplicated output event records to the cache log file in sequence.
[0010] Furthermore, the step of generating the cache number index is characterized by: S121.1 Extract each output event record from the cached log file; S121.2 Extract the globally unique ID from each output event record; S121.3, arrange all globally unique IDs in order of appearance to generate a cache ID index.
[0011] Furthermore, the step of generating batch hash digest data is as follows: S131, Concatenate the globally unique IDs of all output event records in the cache log file to obtain the ID string; S132, perform SHA-256 operation on the numbered string to obtain the hash calculation result; S133: Write the hash calculation result and the length value of the number string into the digest structure to generate batch hash digest data.
[0012] Furthermore, the step of generating the integrity index data is as follows: S141, extract batch hash digest data, number range, generation time and execution node number to obtain index input parameters; S142, Perform structured mapping based on index input parameters to generate complete index data; S143, Write the integrity index data to the WORM medium and return the physical offset address; S144, write the physical offset address to the corresponding output event record.
[0013] Furthermore, the logic for generating the physical offset address is as follows: S143.1, based on the pre-allocated fixed block segment in the WORM medium, locate the next writable physical address and use it as the starting address of the segment to be written; S143.2, Calculate the address offset based on the segment start address and the integrity index data length; S143.3, sum the starting address of the segment with the address offset to obtain the physical offset address.
[0014] Furthermore, the steps for embedding the QR code into the output carrier are as follows: S151, Synchronously write the integrity index data and its corresponding output event records into the audit database; S152, based on the output event record that has been successfully written to the database, retrieve its corresponding globally unique number to generate a QR code; S153, Write the generated QR code into the reserved identification area of the output carrier.
[0015] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention generates output event records based on image output request records and embeds globally unique numbers to achieve structured recording of key information such as operator identifier, department identifier, patient identifier, examination number, and DICOM image identifier during the image output process. This ensures the binding and association between output behavior and contextual information, thereby providing a stable data positioning foundation for subsequent traceability and verification.
[0016] In addition, the present invention also establishes an integrity verification certificate for output behavior records by writing the deduplicated output event records into the cache log file and generating batch hash digest data based on the globally unique number, thereby avoiding record confusion caused by duplicate output requests and ensuring that the contents of the cache log file can be consistently mapped to the actual output operation. Furthermore, this invention generates integrity index data based on batch hash digest data and writes it into the WORM medium. At the same time, it registers the physical offset address in the output event record and associates it with a QR code to write it into the audit database, so as to realize the immutable registration and visual traceability of the entire image output process, thereby providing a complete closed-loop traceable audit guarantee for medical image output behavior. In summary, this invention achieves simultaneous protection of medical image output behavior in terms of context binding, content consistency, and visual audit traceability by performing structured registration, integrity verification, and tamper-proof traceability storage of output event records throughout the entire process. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.
[0018] Figure 1 This is a flowchart of an image output management method for medical images provided in Embodiment 1 of the present invention. Detailed Implementation
[0019] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0020] Example 1
[0021] Please see Figure 1 As shown, this embodiment discloses an image output management method for medical images, the method comprising: S11, based on the image output request record output context parameters, generate an output event record containing operator identifier, department identifier, patient identifier, examination number, DICOM image identifier, output type, output target address, workstation identifier and output timestamp, and write a globally unique number generated based on the timestamp into the output event record; Specifically, the steps for outputting event logs are as follows: S111: By receiving the image output request record, the operator identifier, department identifier, and workstation identifier are extracted to obtain the operator context parameters; It should be noted that the operator identifier, department identifier, and workstation identifier are transmitted from the hospital information system (HIS) interface and written into the output request header area.
[0022] S112, extract patient identifier, examination number and DICOM image identifier by parsing the image output request record to obtain image content parameters; It should be noted that: DICOM image identifiers are located in labels (0008, 0018) of the image dataset, while patient identifiers and examination numbers are located in labels (0010, 0020) and (0008, 0050). A label offset table must be used during parsing.
[0023] S113, based on the operator context parameters and image content parameters, write the output type, output target address and output timestamp to generate an output event record; This can be understood as follows: the output timestamp is generated by the system clock and is used to record the time when the image output event occurs; the output event record is a structured field record containing context and content fields, which is used to describe the behavioral context of an image output operation.
[0024] S114. Generate a globally unique number based on the output timestamp and write it to the output event record.
[0025] Specifically, the logic for generating a globally unique ID in the output event record is as follows: S114.1, Perform a concatenation operation based on the output timestamp and the operator identifier to obtain the initial number string; The concatenation operation is represented as: In the formula, The initial number string, To output the timestamp, Identify the operator; S114.2 Calculate the CRC check code using the initial number string and generate the check number segment; In one specific embodiment, the initial number string is divided into multiple data bytes, each data byte containing 8 bits; Set up a 32-bit parity register and initialize all bits to 1. Read each data byte sequentially and perform a bitwise XOR operation between the 8 bits of the current data byte and the highest 8 bits of the parity register. After the XOR operation is completed, shift the parity register left by 1 bit and fill the least significant bit with 0. Repeat this shifting process 8 times. After all data bytes have undergone the above XOR and shift processing, the final 32-bit binary value retained in the check register is the check number segment. S114.3, concatenate the initial number string with the check number segment to obtain a globally unique number.
[0026] In one specific embodiment, all character content in the initial number string is written to the buffer in its original order; a fixed-length separator is appended to the end of the initial number string; the 32-bit binary content of the check number segment is converted into printable character format; the converted character content is written after the separator in byte order; and the complete concatenated character sequence in the buffer is output as a globally unique number.
[0027] It should be noted that the globally unique number is composed of an initial number string, a separator, and a verification number segment concatenated sequentially. It carries both time and operator information as well as verification information, and is used to achieve unique positioning in subsequent record retrieval and integrity verification.
[0028] S12, filter unregistered records by comparing the global unique number with the local cache index, generate deduplicated output event records, and write the deduplicated output event records sequentially into the cache log file; It should be noted that the deduplicated output event records intercept duplicate output requests by removing output event records already registered in the local cache index, ensuring that the log content corresponds one-to-one with the actual output behavior.
[0029] Specifically, the steps for generating the deduplicated output event record are as follows: S121, generate a cache number index by reading the globally unique number of all output event records in the cache log file; It should be noted that the output event record is a structured storage unit, which includes fields such as operator identifier, department identifier, patient identifier, examination number, DICOM image identifier, output type, output target address, workstation identifier, output timestamp, and globally unique number.
[0030] Specifically, the steps for generating the cache number index are as follows: S121.1 Extract each output event record from the cached log file; S121.2 Extract the globally unique ID from each output event record; Position the identifier number field offset in the output event log; read the content of the number field according to the offset position; output the content of the number field as a globally unique number; It should be noted that the globally unique number is used to uniquely identify each output event record, providing a basis for comparison in subsequent duplicate record determination; S121.3, arrange all globally unique IDs in order of appearance to generate a cache ID index.
[0031] S122, compare the globally unique number with the cache number index, filter out the output event records that are not registered in the cache number index, and obtain the unregistered records; In one specific embodiment, the extracted globally unique IDs are written into the ID index structure one by one according to the physical line number order of the output events recorded in the cache log file; a cache ID index containing an ID order field and a line number mapping field is generated. It should be noted that: the cache number index is a list of numbers maintained in chronological order, used to support subsequent duplicate record screening processing; the unregistered records are output event records filtered after comparing with the cache number index, which come from records whose globally unique numbers do not appear in the cache number index.
[0032] S123, based on the unregistered records, sort them in chronological order, generate deduplicated and output event records; It should be noted that the deduplicated output event records are sorted in chronological order before being written to the cached log file to ensure that the log order is consistent with the actual order in which the events occur.
[0033] S124, write the deduplicated output event records to the cache log file in sequence.
[0034] It should be noted that: the cached log file is used as a local persistent medium to record all output events, and S124 appends the deduplicated output event records to it to complete the registration process.
[0035] S13, generate a number string based on the globally unique number of the output event record in the cache log file, and perform SHA-256 operation based on the number string to generate batch hash digest data; It should be noted that the batch hash digest data serves as an integrity verification credential, used to establish tamper-proof digest information for the current set of all output event records.
[0036] Specifically, the steps for generating batch hash digest data are as follows: S131, Concatenate the globally unique IDs of all output event records in the cache log file to obtain the ID string; In one specific embodiment, all output event records in the cached log file are extracted; the globally unique number of each output event record is read; and all globally unique numbers are concatenated into a continuous character sequence according to the physical line number order recorded in the cached log file, and output as a number string. It should be noted that the number string is the result of concatenating the globally unique numbers of all output event records in the current cached log file. S132, perform SHA-256 operation on the numbered string to obtain the hash calculation result; In one specific embodiment, the number string is divided into multiple data blocks by bytes; bit-by-bit grouping, circular shifting and XOR compression are performed on each data block; after all data blocks have been processed, a 256-bit binary check value is output as the hash calculation result. It should be noted that the hash calculation result is a unique fixed-length digest calculated based on the numbered string, which can be used to determine whether the source content of the digest has been tampered with; S133, Write the hash calculation result and the length value of the number string into the digest structure to generate batch hash digest data; In a specific embodiment, a summary structure field is created; the length value of the number string is written; the hash calculation result is written; and the entire summary structure is output as batch hash summary data. It should be noted that: the batch hash digest data includes the source number range length and the corresponding hash check value, which can provide a traceability basis for the subsequent integrity index generation; the length value of the number string is the statistical result of the total number of characters in the number string, which is directly obtained from the number string generation step.
[0037] S14. Generate integrity index data based on batch hash digest data, number range, generation time and execution node number, and write the integrity index data into the WORM medium for storage. At the same time, write the physical offset address of the integrity index data into the corresponding output event record. It should be noted that the integrity index data is a structured index that records the batch content range and verification summary, which is used to quickly locate and verify the integrity of a specified output batch in subsequent traceability audits.
[0038] Specifically, the steps for generating the integrity index data are as follows: S141, extract batch hash digest data, number range, generation time and execution node number to obtain index input parameters; In one specific embodiment, batch hash digest data is read from the digest generation module; the number range is extracted from the event cache management module; the generation time is obtained from the system clock; the execution node number is read from the node configuration table; and the four data items are encapsulated into index input parameters. It should be noted that: the number range refers to the minimum and maximum values of the globally unique numbers of the output event records in the current batch. It is used to identify the number range of all output events in the current batch, ensuring that the integrity index records the range information of the current batch; the generation time refers to the system timestamp when the integrity index data of the current batch was generated; the row node number refers to the system node or server identifier that performed the current integrity index generation operation; the index input parameters are all the necessary information for constructing the integrity index data; S142, Perform structured mapping based on index input parameters to generate complete index data; In one specific embodiment, field labels are assigned to the index input parameters; each field label is bound to its corresponding value and written into the index structure; the generated index structure is output as complete index data. It should be noted that the integrity index data includes a summary check value and a batch range identifier, which can support subsequent batch verification and data location. S143, Write the integrity index data to the WORM medium and return the physical offset address; Specifically, the logic for generating the physical offset address is as follows: S143.1, based on the pre-allocated fixed block segment in the WORM medium, locate the next writable physical address and use it as the starting address of the segment to be written; It should be noted that a fixed block segment is a contiguous storage area pre-defined on the WORM medium. Its boundaries are fixed and will not be adjusted. The starting address of the segment is the starting address of this write operation. A fixed block segment consists of multiple consecutive storage blocks. In one specific embodiment, the system reserves a fixed block segment in the WORM medium during the initialization phase and records the reference start address of the segment. Each time a write operation is performed, the system locates the next writable physical address by querying the write pointer position within the segment and uses that physical address as the start address of the segment being written. It should be noted that the writing process only appends sequentially within the fixed block segment. That is, each time a write operation is performed, the next writable physical address is located based on the write pointer position as the starting address of the segment, rather than dynamically allocating a new storage block. For example, suppose that during the initialization phase, the system reserves a fixed block segment in the WORM medium through the storage controller and records the base starting address of the fixed block segment as 0x2000 and the segment capacity as 40KB. When writing integrity index data for the first time, the system queries the write pointer position within the fixed block segment based on the byte length of the integrity index data. The next writable physical address obtained is 0x2000, which is used as the starting address of the segment to be written. When writing integrity index data for the second time, the write pointer has already pointed to the position where the previous write ended. The system continues to query within this fixed block segment. The next writable physical address is 0x4000. This physical address is then used as the starting address of the segment to be written, and so on. S143.2, Calculate the address offset based on the segment start address and the integrity index data length; In one specific embodiment, the byte length of the integrity index data is obtained; the byte length is converted to an integer multiple of the storage block size; the converted total byte length is recorded as the address offset; Represented as: In the formula, This is the converted total length in bytes. The length of the integrity index data in bytes. This refers to the size of the storage block. It should be noted that the address offset is the write span reserved from the starting address of the segment to ensure that the records are stored continuously in the physical block segment; For example, assume that the integrity index data is 900 bytes long, the storage block size is 512 bytes, and the segment start address is 0x2000; This means that a write span of 1024 bytes needs to be reserved continuously after the segment start address 0x2000 as the address offset; S143.3, sum the starting address of the segment and the address offset to obtain the physical offset address; In one specific embodiment, the system only returns the calculated physical offset address, for example: If the starting address of the segment is 0x2000, the address offset is 1024, which is 0x400 after decimal processing, then the physical offset address is: That is: 0x2000 + 1024 = 0x2000 + 0x400 = 0x2400; Then 0x2400 is the physical offset address of the integrity index data within the fixed block segment; It should be noted that the physical offset address serves as the physical locator for the integrity index data. The physical offset address is a key parameter for establishing a bidirectional association between the event record and the integrity index data, and is used for subsequent registration. S144, Write the physical offset address to the corresponding output event record; In one specific embodiment, the system locates the reserved offset address field in the output event record structure, writes the physical offset address in a fixed format, and updates the record status to "indexed". It should be noted that by embedding the physical offset address into the output event record, a two-way traceability binding between the event record and the integrity index data can be achieved, supporting subsequent source tracing and auditing.
[0039] S15, write the integrity index data and its referenced output event records into the audit database, generate a QR code based on the globally unique number of the records already in the database, and embed the QR code into the output carrier; It should be noted that the audit database is a long-term storage medium used to record the source, generation node, and integrity certificate of all output images to support post-audit traceability. Specifically, the steps for embedding the QR code into the output carrier are as follows: S151, Synchronously write the integrity index data and its corresponding output event records into the audit database; In one specific implementation, the system creates a database transaction, writing data sequentially to the index table and the event table. Specifically... S151.1 Write the integrity index data into the index table, which includes at least the following fields: summary check value, number range, generation time, execution node number, and physical offset address; S151.2 Write the output event records that correspond one-to-one with the integrity index data into the event table. The fields included must include at least: operator identifier, department identifier, patient identifier, examination number, DICOM image identifier, output type, output target address, workstation identifier, output timestamp, and globally unique number. S151.3, establish a relationship constraint between the index table and the event table using the same globally unique number; after the data write verification passes, commit the transaction and return a successful data entry status; It should be noted that: the integrity index data used for writing comes from the structured mapping results of S14 / S142, and the physical offset address comes from the calculation return of S143; the output event records used for writing come from the generation results of S11; transactional writing ensures the consistent registration of the two types of data in the audit database, avoiding the inconsistency of "index has been entered into the database but event has not" or vice versa. S152, based on the output event record that has been successfully written to the database, retrieve its corresponding globally unique number to generate a QR code; In one specific embodiment, the system uses a globally unique identifier as input and employs a QR code encoding module to generate a corresponding QR code dot matrix. The generation process is as follows: read the globally unique identifier of the target output event record from the audit database; convert the globally unique identifier into a byte stream using UTF-8 encoding; call the QR code encoding module to complete encoding and error correction processing, and output the QR code bitmap data (including the module matrix and margins); the QR code version parameters, error correction level, and module size are given by the system configuration items.
[0040] It should be noted that: system configuration items are stored in the workstation software's configuration file and are loaded at runtime; the QR code carries only a single payload of a globally unique number to ensure that after scanning and parsing, the corresponding output event record and integrity index data in the audit database can be directly retrieved, achieving unique traceability; S153, Write the generated QR code into the reserved identification area of the output carrier; In one specific embodiment, for digital output carriers, including but not limited to electronic reports, image files, or DICOM exported files, the generated QR code is superimposed onto a reserved identification area at a predetermined position by an image compositing module. The reserved identification area includes, but is not limited to, a single line, the bottom right side of the report page or the corner mark area of the image canvas. Update the status of the identifier area in the output carrier metadata to "written"; for physical output carriers, such as film or paper reports, the system sends the QR code to the printing component, completes synchronous printing in the reserved identifier area, and registers the correspondence between the output carrier and its globally unique number in the distribution record; It should be noted that the location and size of the reserved identification area are preset by the workstation's template and remain consistent under the same template. After the QR code is embedded, bidirectional retrieval and verification of output event records and integrity index data can be achieved in the audit database based on the globally unique number, forming a closed-loop traceability link of "visual identification of carrier - database retrieval - index positioning".
[0041] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless network. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.
[0042] In the several embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only one method, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0043] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0044] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0045] Some of the data in the above formula are calculated by removing dimensions and taking their numerical values. The formula is the closest to the real situation obtained by software simulation of a large amount of collected data. The preset parameters and preset thresholds in the formula are set by those skilled in the art according to the actual situation or obtained through simulation of a large amount of data.
[0046] The above embodiments are only used to illustrate the technical methods of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical methods of the present invention without departing from the spirit and scope of the technical methods of the present invention.
Claims
1. An image output management method for medical images, characterized in that, The method includes: S11, based on the image output request record output context parameters, generate an output event record containing operator identifier, department identifier, patient identifier, examination number, DICOM image identifier, output type, output target address, workstation identifier and output timestamp, and write a globally unique number generated based on the timestamp into the output event record; S12, filter unregistered records by comparing the global unique number with the local cache index, generate deduplicated output event records, and write the deduplicated output event records sequentially into the cache log file; S13, generate a number string based on the globally unique number of the output event record in the cache log file, and perform SHA-256 operation based on the number string to generate batch hash digest data; S14. Generate integrity index data based on batch hash digest data, number range, generation time and execution node number, and write the integrity index data into the WORM medium for storage. At the same time, write the physical offset address of the integrity index data into the corresponding output event record. S15, write the integrity index data and its referenced output event records into the audit database, generate a QR code based on the globally unique number of the records already in the database, and embed the QR code into the output carrier.
2. The image output management method for medical images according to claim 1, characterized in that, The steps for generating output event records are as follows: S111: By receiving the image output request record, the operator identifier, department identifier, and workstation identifier are extracted to obtain the operator context parameters; S112, extract patient identifier, examination number and DICOM image identifier by parsing the image output request record to obtain image content parameters; S113, based on the operator context parameters and image content parameters, write the output type, output target address and output timestamp to generate an output event record; S114. Generate a globally unique number based on the output timestamp and write it to the output event record.
3. The image output management method for medical images according to claim 2, characterized in that, The logic for generating the globally unique ID in the output event record is as follows: S114.1, Perform a concatenation operation based on the output timestamp and the operator identifier to obtain the initial number string; S114.2 Calculate the CRC check code using the initial number string and generate the check number segment; S114.3, concatenate the initial number string with the check number segment to obtain a globally unique number.
4. The image output management method for medical images according to claim 3, characterized in that, The steps for generating the deduplicated output event record are as follows: S121, generate a cache number index by reading the globally unique number of all output event records in the cache log file; S122, compare the globally unique number with the cache number index, filter out the output event records that are not registered in the cache number index, and obtain the unregistered records; S123, based on the unregistered records, sort them in chronological order, generate deduplicated and output event records; S124, write the deduplicated output event records to the cache log file in sequence.
5. The image output management method for medical images according to claim 4, characterized in that, The steps for generating the cache number index are as follows: S121.1 Extract each output event record from the cached log file; S121.2 Extract the globally unique ID from each output event record; S121.3, arrange all globally unique IDs in order of appearance to generate a cache ID index.
6. The image output management method for medical images according to claim 5, characterized in that, The steps for generating batch hash digest data are as follows: S131, Concatenate the globally unique IDs of all output event records in the cache log file to obtain the ID string; S132, perform SHA-256 operation on the numbered string to obtain the hash calculation result; S133: Write the hash calculation result and the length value of the number string into the digest structure to generate batch hash digest data.
7. The image output management method for medical images according to claim 6, characterized in that, The steps for generating integrity index data are as follows: S141, extract batch hash digest data, number range, generation time and execution node number to obtain index input parameters; S142, Perform structured mapping based on index input parameters to generate complete index data; S143, Write the integrity index data to the WORM medium and return the physical offset address; S144, write the physical offset address to the corresponding output event record.
8. The image output management method for medical images according to claim 7, characterized in that, The logic for generating the physical offset address is as follows: S143.1, based on the pre-allocated fixed block segment in the WORM medium, locate the next writable physical address and use it as the starting address of the segment to be written; S143.2, Calculate the address offset based on the segment start address and the integrity index data length; S143.3, sum the starting address of the segment with the address offset to obtain the physical offset address.
9. The image output management method for medical images according to claim 8, characterized in that, The steps for embedding a QR code into the output carrier are as follows: S151, Synchronously write the integrity index data and its corresponding output event records into the audit database; S152, based on the output event record that has been successfully written to the database, retrieve its corresponding globally unique number to generate a QR code; S153, Write the generated QR code into the reserved identification area of the output carrier.