A medical testing instrument docking configuration system
Through the combination of docking port configuration module, device driver management module and inspection data processing module, the problem of docking configuration of multiple inspection instruments is solved, and a fast and unified inspection data interface is realized, which improves inspection efficiency and experience, and supports multiple docking mode and transmission protocol.
Patent Information
- Application Number
- CN202310086247.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-31
- Publication Date
- 2025-01-10
- Estimated Expiration
- 2043-01-31
AI Technical Summary
There are many inspection instruments from different manufacturers in medical institutions, which are difficult to achieve rapid and unified inspection data interface configuration, affecting the data interaction and summary analysis of the information system.
Provide a medical inspection instrument docking configuration system, including docking port configuration module, device driver management module and inspection data processing module. By obtaining interface configuration files, loading drivers, calling docking threads, receiving and converting inspection data, it supports multiple docking The methods are TCP/IP, COM, database, and use HL7, ASTM, SQL and other transmission protocols.
It realizes rapid docking of a variety of inspection instruments, reduces the secondary development of repeated docking, improves inspection efficiency and experience, supports docking and driving of heterogeneous inspection instruments, and enhances the data collection capabilities of medical institutions' information system.
Smart Images

Figure CN116189867B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of medical information technology, and in particular to a medical testing instrument docking configuration system. Background Art
[0002] After decades of development, the HIS information system of medical institutions has begun to take shape. Medical institutions have successively established hospital-wide automatic analysis systems for test results. However, in the testing departments of medical institutions, there are tens of thousands of testing instruments used to collect and analyze patients' physiological indicators and samples. Since these instruments and equipment come from different manufacturers, they each provide their own test data docking specifications to transmit the test data to the HIS information system of the medical institution, thereby establishing a complete patient medical record. Therefore, it is difficult to achieve fast and unified test data interface configuration between numerous testing instruments and the HIS information system of the medical institution, and it affects the data interaction and data summary analysis of the HIS paper of the medical institution's information system. In view of this, how to provide a system and method that can be configured with multiple docking modes to achieve rapid docking of testing instruments has become an urgent problem to be solved in the clinical testing stage. Summary of the invention
[0003] In order to solve the problems existing in the prior art, the present invention provides a medical testing instrument docking configuration system, including a docking port configuration module, a device driver management module and a test data processing module, wherein the docking port configuration module is used to obtain an interface configuration file from the testing instrument and determine the testing instrument driver to be loaded; the interface configuration file includes configuration parameter information for the testing instrument;
[0004] The device driver management module is used to, after determining the test instrument driver program that needs to be loaded, load the test instrument driver program according to the configuration parameter information and call the docking thread in the test instrument driver program;
[0005] The test data processing module is used to, after completing the interface docking of the test instrument, receive the test data sent by the test instrument, convert the test data according to the data format corresponding to the configuration parameter information, and transmit the converted test data to the information system HIS of the medical institution.
[0006] The configuration parameter information includes a docking port and a transmission protocol; the type of the docking port includes TCP / IP, COM or database, and the transmission protocol includes HL7, ASTM or SQL.
[0007] Preferably, the device driver management module is further configured to load a driver file of the corresponding testing instrument by mapping according to the configuration parameter information if the testing instrument is configured to start automatically.
[0008] Preferably, the device driver management module is further configured to, after selecting the corresponding current docking thread, determine the resource constraints formed by each running docking thread already included in the inspection instrument driver;
[0009] The determined current docking thread is pre-invoked to determine whether the current docking thread satisfies the multiple resource constraints.
[0010] Preferably, only when the determined current docking thread satisfies at least one of the resource constraints, the selected current docking thread is loaded into the inspection instrument driver and started.
[0011] Preferably, the docking port configuration module is further configured to request the current transmission protocol to be processed by the inspection instrument driver by reading the interface configuration file; configure a device protocol stack for multiple inspection instruments in the inspection instrument driver, the device protocol stack pre-stores the identifier of the current transmission protocol to indicate the use of the current transmission protocol, loads the port feature value for the current transmission protocol from the interface configuration file, and starts the hardware initialization of each inspection instrument.
[0012] Preferably, the port characteristic value includes the maximum sending buffer size of the current transmission protocol and the maximum receiving buffer size of the current transmission protocol.
[0013] Preferably, when the type of the docking port is TCP / IP and the transmission protocol is HL7, the inspection data is transmitted in a message in the following format:
[0014] <sb>dddddd <eb> <cr>
[0015] in <sb>is the start block character, ddddd is the HL7 message, <eb>is the end block character, <cr>It is to transmit the return value.
[0016] Preferably, when the type of the docking port is COM and the transmission protocol is ASTM, when the inspection instrument needs to send inspection data, it first sends <enq>The control command character is sent to the information system HIS. If the information system HIS has resources to receive data, it will respond <ack>To the test instrument, otherwise answer <nak>, the test instrument successfully received <ack>After the control command character, the data frame will be sent. When the data frame is sent, <eot>The control command characters inform the information system HIS.
[0017] Preferably, when the docking port type is a database port and the transmission protocol is SQL, the information system HIS is connected to the database component of the testing instrument according to the database address in the configuration parameter information, and uses SQL to read the row data in the corresponding data table and convert it into standard testing data; the converted testing data is sent to the information system HIS for reception.
[0018] Compared with the prior art, the present invention has the following beneficial effects:
[0019] The present invention provides a medical testing instrument docking configuration system, including a docking port configuration module, a device driver management module and a test data processing module, wherein the docking port configuration module is used to obtain an interface configuration file from the testing instrument and determine the testing instrument driver program to be loaded; the interface configuration file includes configuration parameter information for the testing instrument; the device driver management module is used to load the testing instrument driver program according to the configuration parameter information after determining the testing instrument driver program to be loaded, and call the docking thread in the testing instrument driver program; the test data processing module is used to receive the test data sent by the testing instrument after completing the interface docking of the testing instrument, and convert the test data according to the data format corresponding to the configuration parameter information, and transmit the converted test data to the information system HIS of the medical institution. The scheme of the present invention integrates the inspection management based on multi-device scenarios, and uses the basic device management function to provide the docking driver of heterogeneous testing instruments, which can more quickly and efficiently realize the support of the medical institution information system HIS docking the testing instrument, and collect the test data, provide configuration management of multiple docking modes for the testing instrument, reduce the secondary development of repeated docking, realize the rapid docking of the testing instrument, and improve the inspection efficiency and experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 A block diagram of a medical testing instrument docking configuration system according to an embodiment of the present invention.
[0021] Figure 2 This is a module diagram of the medical testing instrument docking configuration system according to an embodiment of the present invention.
[0022] Figure 3 The present invention is a flowchart of the medical testing instrument docking configuration system according to an embodiment of the present invention.
[0023] Figure 4 Flow chart of transmitting inspection data according to ASTM protocol according to a preferred embodiment of the present invention. DETAILED DESCRIPTION
[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. It is obvious that the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present invention.
[0025] The medical testing instrument docking configuration system of the present invention forms a multi-device multi-driver platform system based on the inspection management of multiple device scenarios, and matches the diversity of the inspection instrument docking methods based on the diversity of device drivers. Inspection instruments can be divided into multiple docking types, including TCP / IP, COM, database, etc., and the transmission protocols involved cover HL7, ASTM, SQL, JSON and private transmission protocols, etc. The device docking configuration system configures the corresponding docking device driver mode for the inspection instrument.
[0026] The medical testing instrument docking configuration system is built on the basic equipment management platform, including functional modules such as device driver management, docking port configuration, and test data processing. At the same time, the device driver module can also be called to interact with the testing instrument in a fully automatic, semi-automatic or manual manner, and after obtaining the test result data from the device, it is converted into standard data in a unified data format and transmitted to the medical institution's information system HIS. The interface types that interact with the testing instrument and perform data docking include TCP / IP, COM (serial port), database access, data file reading and writing, etc. The docking data format supports HL7, ASTM, JSON, etc. In addition, it can be expanded in the device driver to meet the customization needs of the testing instrument.
[0027] In order to better understand the present invention, the content of the present invention is further described below in conjunction with the accompanying drawings and examples.
[0028] The present invention provides a medical testing instrument docking configuration system, such as Figure 1 As shown, the medical testing instrument docking configuration system can be set at the testing instrument end, or at the medical information system HIS service end, or between the two. The medical testing instrument docking configuration system includes: a docking port configuration module 101, a device driver management module 102 and a test data processing module 103. The docking port configuration module 101 is used to obtain an interface configuration file from the testing instrument and determine the testing instrument driver that needs to be loaded. The interface configuration file includes configuration parameter information for the testing instrument. The device driver management module 102 is used to load the testing instrument driver according to the configuration parameter information after determining the testing instrument driver that needs to be loaded, and call the docking thread in the testing instrument driver. The test data processing module 103 is used to receive the test data sent by the testing instrument after completing the interface docking of the testing instrument, and convert the test data according to the data format corresponding to the configuration parameter information, and transmit the converted test data to the medical institution's information system HIS.
[0029] Specifically, see Figure 2 After the device docking configuration system is running, it first reads the device configuration content of the interface configuration file (SystemSetting.xml), and obtains the list of devices that need to be connected and displays it in the running window. If the test instrument is configured to start automatically, the driver file (.dll) of the corresponding test instrument is loaded by mapping according to the configuration parameter information. After successful loading, the corresponding method in the driver (such as StartConnection) is called and the configuration parameters are passed in. Among them, the configuration parameters may include docking ports, transmission protocols, etc.
[0030] The driver of the testing instrument selects and starts the corresponding docking thread according to the connection configuration information such as the docking port and transmission protocol in the configuration parameters. For example, the current testing instrument uses the ATSM protocol to transmit test data through the COM interface. The driver of the testing instrument parses the configuration information, obtains the port type (COM) and the protocol number (ATSM), and selects the docking thread corresponding to the COM port and ATSM in the driver set to achieve docking and communication with the medical institution information system HIS.
[0031] Specifically, the driver set includes a plurality of candidate docking threads associated with each interface or protocol. For a determined current docking thread among the plurality of candidate docking threads, a resource constraint formed by each running docking thread already included in the inspection instrument driver is determined. The determined current docking thread is pre-called to determine whether the determined current docking thread satisfies the plurality of resource constraints. Only when the determined current docking thread satisfies at least one of the determined resource constraints, the selected current docking thread is loaded into the inspection instrument driver and started. By determining whether the resource constraints of the thread are satisfied, resource contention and deadlock state can be avoided, and reliable operation of multiple threads can be ensured.
[0032] Figure 3 The present invention is a flowchart of the medical testing instrument docking configuration system of the preferred embodiment of the present invention. Specifically, when the current transmission protocol to be processed by the testing instrument driver is requested from the testing instrument driver by reading the interface configuration file, a device protocol stack is configured for multiple testing instruments in the testing instrument driver, the device protocol stack pre-stores the identifier of the current transmission protocol to indicate the use of the current transmission protocol, the port feature value for the current transmission protocol is loaded from the interface configuration file, and the hardware initialization of each testing instrument is started.
[0033] For example, the characteristic value may include the size of the maximum send buffer of the current transmission protocol and the size of the maximum receive buffer of the current transmission protocol. Then, the configuration information of the selected docking thread is obtained according to the configuration primitive, and the configuration primitive is used to control the setting of the configuration parameters of the selected docking thread. The configuration parameters corresponding to the obtained configuration information are set according to the configuration primitive. The docking thread definition metadata containing the configuration primitive is read. The selected docking thread is configured into the inspection instrument driver according to the configuration parameters. For example, the selected docking thread can be started to pass the set configuration parameters to the started docking thread. When setting the configuration parameters, the characteristic value needs to be assigned to the configuration parameters according to the configuration primitive.
[0034] In a preferred embodiment, when a configuration parameter needs to be modified, the configuration parameter is read from a parameter list for storing current values of the configuration parameter; the configuration parameter is modified according to the acquired configuration primitive, and the modified configuration parameter is stored back into the parameter list.
[0035] In the preferred embodiment below, the TCP / IP interface type is taken as an example to illustrate:
[0036] When the testing instrument uses the HL7 protocol to transmit data via TCP / IP, the monitoring service is started, including loading the IP address and port information. After receiving the data sent by the testing instrument, it is received and converted into standard testing data in accordance with the HL7 protocol. TCP / IP is a byte stream protocol and does not provide message boundaries. HL7, as an upper-layer protocol, is message-based, but it does not provide a message termination mechanism. In order to determine the message boundaries, the preferred embodiment of the present invention uses the minimum underlying protocol HL7 Interface Standards Version 2.3.1.
[0037] Communication layer messages are sent in the following format:
[0038] <sb>dddddd <eb> <cr>
[0039] in: <sb>=Start Block character (start block character, 1 byte)
[0040] For example, you can use ASCII <vt>, which is , is different from the characters SOH or STX in ASCII.
[0041] Where ddddd = Data (variable number of bytes). The ddddd is an HL7 message, which only includes ISO 8859-1 characters (hexadecimal values 20-FF) and <cr>, excluding other control and unprintable characters.
[0042] <eb>=End Block character (end block character, 1 byte)
[0043] For example, you can use ASCII <fs>, which is , which is different from the ASCII characters ETX or EOT.
[0044] <cr>=Carriage Return (transmission return value, 1 byte)
[0045] Each HL7 message consists of multiple segments, each of which consists of <cr>For example, the ASCII carriage return character, , can be used.
[0046] Each segment consists of a three-character segment name and a fixed number of domains. The domains are composed of components and subcomponents. The delimiters of each component unit are defined in the MSH field of each message.
[0047] For example:
[0048] MSH|^~\&|Factory|DXI300|||20060427194802||ORU^R01|1|P|2.3.1||||0||ASCII|||
[0049] The five characters after MSH are used to distinguish the delimiters of various domains, components, and subcomponents. The HL7 standard uses the following characters in Table 1:
[0050] Table 1
[0051] character meaning | Field separator ^ Component separator & Subcomponent separator ~ Repeating delimiter \ Escape Characters
[0052] The first field of the MSH includes various delimiters. Some fields are empty below because they are optional and not used by the HL7 interface. The detailed field definitions and selection rules are described in Table 2 below.
[0053] Table 2
[0054] serial number meaning Domain 9: Contains message type and event (ORU, R01) Domain 10: Contains a message ID that uniquely identifies the message Domain 11: Contains the processing ID (P for product) Domain 12: Defines the HL7 version used by the message (2.3.1)
[0055] For any message, the segments following the MSH segment follow a predefined order, which is described below. These grammatical structures are used to indicate that segments are optional or repeated:
[0056] [] indicates that the segments are optional, and {} indicates that each segment can be repeated 0, 1, or more times.
[0057] In the process of matching HL7 message character strings, the present invention provides the following matching method: First, three lookup tables, OFFSET, MAP1 and MAP2, are constructed, and the text scanning and search matching are completed through these three tables.
[0058] The OFFSET table is used to record the distance that the message string moves to the right, processes substrings of all lengths, and fills in the corresponding OFFSET value. If there are identical character blocks in multiple pattern strings or prefixes of the same pattern, only the minimum value in the OFFSET value is retained. The MAP1 table records the mapping relationship between the suffixes of pattern strings of all lengths and the pattern string itself. When the value of OFFSET is 0, it indicates that there is a mapping relationship between the substring and the corresponding pattern string. The MAP2 table records the mapping relationship between the prefixes of pattern strings of all lengths and the pattern string itself. The values of the MAP2 table store multiple pattern strings in the form of a linked list. When matching, scan λ characters each time T[m-λ+1]>T[m], where m is the character number. The specific process includes scanning the last λ bits of the message string and calculating its hash value h through the record content of the MAP1 table. λ . Find OFFSET, if OFFSET[h λ ]<0, m-λ+1 bit; if OFFSET[h λ ]>0, the pointer slides backward OFFSET[h λ When OFFSET[h]=0, it indicates that a match may occur, and the MAP1 table is searched to determine which pattern string is matched.
[0059] According to the above data structure of the message content, the start block and the end block must be matched during matching. The matching process is as follows:
[0060] 1. Assuming that there is a received message block in the buffer, match the start block with the message block one by one.
[0061] 2. If the start block is found, continue matching the end block until all characters in the message block are matched, and save the position of the successful match in a preset array.
[0062] 3. If there is no start block or end block, clear the buffer.
[0063] In another optional embodiment, the present invention takes the COM interface type as an example to illustrate the conversion process of the inspection data:
[0064] The COM method uses the ATSM protocol, which monitors the COM port, including the baud rate, check bit, etc. When the data sent by the test instrument is received, it is received and converted into standard test data according to the ASTM protocol.
[0065] In the ASTM protocol, when the test instrument needs to send test data, it first sends <enq>The control command character is sent to the information system HIS. If the information system HIS has resources to receive data, it will respond <ack>To the test instrument, otherwise answer <nak>, the test instrument successfully received <ack>After the control command character, the data frame will be sent. When the data frame is sent, <eot>The control command character notifies the information system HIS and the sending process is completed. The sending and receiving process is as follows Figure 4 shown.
[0066] Specifically, multiple message records are defined in the ASTM protocol, and the inspection data sent includes part or all of the following message records, which are:
[0067] Message Header Record
[0068] Patient Information Record
[0069] Test Order Record
[0070] Test Result Record
[0071] Comment Record
[0072] Request Information Record
[0073] Message Terminator Record
[0074] For example, a complete sample test result data frame structure based on the ASTM protocol is as follows: Each ASTM message consists of multiple message records. <cr>Ending:
[0075] 1.Message Header Record
[0076] 2. Patient Information Record
[0077] 3. Test Order Record
[0078] 4. Comment Record (optional)
[0079] 5.Result Record
[0080] ···
[0081] Each message record consists of a 1-character record name and a certain number of fields, and the fields can be composed of components. The H record in the header of each message defines the separators of each component unit.
[0082] For example:
[0083] H|\^&|||DXI300^01.03.07.03^123456|||||||PR|1394-97|20090910102501 <cr>
[0084] The four characters after H are used to define the separators for differentiating fields, repetitions, and components. The ASTM interface uses the following characters in Table 3:
[0085] Table 3
[0086] character meaning | Field separator \ Repeating delimiter ^ Component separator & Escape Characters
[0087] In addition, when the domain content contains the characters in Table 3, it is necessary to use escape characters to escape them. In the ASTM standard, "|" is escaped to "&|".
[0088] First, the device driver management module generates an XML driver configuration file for the test instrument. The XML driver configuration file includes multiple format parameters that describe the test instrument driver program of the test instrument. The format parameters include any one or more of the following: driver identification; baud rate, parity code, buffer size, timestamp information, token information, data style. The medical information system HIS retrieves an XML driver configuration file compatible with the test instrument, loads the driver configuration XML file into the driver framework, and after receiving the test data from the test instrument, converts the received data into ASTM format, and outputs the data in ASTM format to the information system HIS.
[0089] In order to clearly describe the inspection data processing process of the present invention, the following describes a calling example of the ATSM protocol under the COM interface type in the form of source code:
[0090]
[0091]
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099] In yet another optional embodiment, the present invention uses the database interface type as an example to illustrate the conversion process of the inspection data:
[0100] When the testing instrument uses the SQL protocol to transmit data through the database, the medical institution's information system HIS connects to the database component of the testing instrument according to the database address in the configuration parameters, and uses SQL to read the row data in the corresponding data table and convert it into standard testing data. After the test data is obtained and converted into standard test data, it is sent to the medical institution's information system HIS for reception.
[0101] In the case of a database interface, there is a certain association relationship between the data table records in the medical test data, that is, for the same test object, certain combinations of values may appear in common between the field attributes. The embodiment of the present invention first converts the combined test data into a vector in a high-dimensional space to obtain a vector representation of the combined test data. For example, xa and xb can be used as vector representations of the combined test data Ka and Kb, respectively, and used as inputs of the deep learning model.
[0102] Perform stochastic gradient descent on xa and xb through the deep learning model to obtain implicit features ca and cb; continue to use ca as the input of the LTSM network to obtain τa, the output of the hidden layer, as the explicit feature;
[0103] Fusion optimization is performed on the implicit feature cb and the explicit feature τa, and the minimum tolerance value of the entire deep learning model is preset And calculate the current tolerance value e:
[0104]
[0105] If e is less than the preset minimum tolerance value Then calculate the cosine similarity of Ka and Kb. If e is greater than or equal to the preset minimum tolerance value Then discard. k It indicates that the classification algorithm of the support vector machine is executed on the k-th dimensional vector of the combined test data, where K is the dimension of the combined test data.
[0106] The step of converting the combined test data into a vector in a high-dimensional space further includes: assuming that the dimension of the high-dimensional space is μ, and the numerical lengths of the combined test data Ka and Kb are la and lb respectively, then the vector representations of Ka and Kb are respectively:
[0107]
[0108]
[0109] And Xa∈R la*μ , Xb∈R lb*μ , where R represents the vector space, x i a and x i b are the numeric vectors of the i-th position of xa and xb respectively.
[0110] After the above intelligent processing based on deep learning, the combined inspection data is semantically decomposed and feature extracted, and the similarity of the entire record is calculated based on numerical features, which adapts to the characteristics of the inspection data.
[0111] It can be seen that the medical testing instrument docking configuration system provided by the present invention is a device docking configuration system for testing management based on multi-device scenarios, which can more quickly and efficiently support the medical institution information system HIS to dock testing instruments with various interfaces, and collect medical testing data, provide configuration management of multiple docking methods for testing instruments, and reduce secondary development of repeated docking.
[0112] 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 ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0113] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on a plurality of computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program codes.
[0114] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data mining device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data mining device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0115] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data mining device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, the instruction device being implemented in the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0116] These computer program instructions may also be loaded onto a computer or other programmable data mining device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0117] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are included in the scope of the claims of the present invention to be approved.< / cr> < / cr> < / eot> < / ack> < / nak> < / ack> < / enq> < / cr> < / cr> < / fs> < / eb> < / cr> < / vt> < / sb> < / cr> < / eb> < / sb> < / eot> < / ack> < / nak> < / ack> < / enq> < / cr> < / eb> < / sb> < / cr> < / eb> < / sb>
Claims
1. A medical testing instrument docking configuration system, comprising a docking port configuration module, a device driver management module and a test data processing module, characterized in that: The docking port configuration module is used to obtain an interface configuration file from the inspection instrument and determine the inspection instrument driver that needs to be loaded; the interface configuration file includes configuration parameter information for the inspection instrument; the interface configuration file is read to request the inspection instrument driver for the current transmission protocol to be processed by the inspection instrument driver; the device driver management module is used to, after determining the inspection instrument driver that needs to be loaded, load the inspection instrument driver according to the configuration parameter information, and call the docking thread in the inspection instrument driver, configure a device protocol stack for multiple inspection instruments in the inspection instrument driver, the device protocol stack pre-stores the identifier of the current transmission protocol to indicate the use of the current transmission protocol, loads the port feature value for the current transmission protocol from the interface configuration file, and starts the hardware initialization of each inspection instrument; the feature value includes the maximum send buffer size of the current transmission protocol, and the maximum receive buffer size of the current transmission protocol; Acquire configuration information of the selected docking thread according to a configuration primitive, wherein the configuration primitive is used to control the setting of configuration parameters of the selected docking thread; set configuration parameters corresponding to the acquired configuration information according to the configuration primitive; read docking thread definition metadata including the configuration primitive; configure the selected docking thread into the inspection instrument driver according to the configuration parameters; When the configuration parameters need to be modified, the configuration parameters are read from the parameter list for storing the current values of the configuration parameters; the configuration parameters are modified according to the acquired configuration primitives, and the modified configuration parameters are stored again in the parameter list; The inspection data processing module is used to receive the inspection data sent by the inspection instrument after completing the interface docking of the inspection instrument, and convert the inspection data according to the data format corresponding to the configuration parameter information. There is a certain correlation between the data table records in the medical inspection data, that is, for the same inspection object, certain combinations of numerical values may appear together between the attributes of each field; first, the combined inspection data is converted into a vector in a high-dimensional space to obtain a vector representation of the combined inspection data, and xa and xb are used as vector representations of the combined inspection data Ka and Kb respectively, which are used as inputs of the deep learning model; xa and xb are subjected to random gradient descent operations through the deep learning model to obtain implicit features ca and cb; ca continues to be used as the input of the LTSM network to obtain τa output by the hidden layer as an explicit feature; the implicit feature cb and the explicit feature τa are fused and optimized, and the minimum tolerance value of the entire deep learning model is preset And calculate the current tolerance value e: If e is less than the preset minimum tolerance value Then calculate the cosine similarity of Ka and Kb; if e is greater than or equal to the preset minimum tolerance value Then discard; among them, svm k It represents the classification algorithm of the support vector machine executed on the k-th dimensional vector of the combined test data, where K is the dimension of the combined test data; wherein the combined test data is converted into a vector in a high-dimensional space, assuming that the dimension of the high-dimensional space is μ, and the numerical lengths of the combined test data Ka and Kb are la and lb respectively, then the vector representations of Ka and Kb are respectively: And Xa∈R la*μ , Xb∈R lb*μ , where R represents the vector space, x i a and x i b are the numerical vectors of the i-th position of xa and xb respectively; The converted test data is transmitted to the medical institution's information system HIS.
2. The medical testing instrument docking configuration system according to claim 1, characterized in that: The configuration parameter information includes a docking port and a transmission protocol; The type of the docking port includes a TCP / IP port, a COM port or a database port, and the transmission protocol includes HL7, ASTM or SQL.
3. The medical testing instrument docking configuration system according to claim 1, characterized in that: The device driver management module is further configured as follows: If the testing instrument is configured to start automatically, the driver file of the corresponding testing instrument is loaded by mapping according to the configuration parameter information.
4. The medical testing instrument docking configuration system according to claim 1, characterized in that: The device driver management module is further configured as follows: After selecting the corresponding current docking thread, determining the resource constraints formed by each running docking thread already included in the inspection instrument driver; The determined current docking thread is pre-invoked to determine whether the current docking thread satisfies the multiple resource constraints.
5. The medical testing instrument docking configuration system according to claim 4, characterized in that: Only when the determined current docking thread satisfies at least one of the resource constraints, the selected current docking thread is loaded into the inspection instrument driver and started.
6. The medical testing instrument docking configuration system according to claim 2, characterized in that: When the type of the docking port is TCP / IP and the transmission protocol is HL7, the inspection data is transmitted in the following message format: <sb>dddddd <eb> <cr>< / cr> < / eb> < / sb> in <sb>is the start block character, ddddd is the HL7 message, <eb>is the end block character, <cr> It is to transmit the return value.< / cr> < / eb> < / sb> 7. The medical testing instrument docking configuration system according to claim 2, characterized in that: When the type of the docking port is COM and the transmission protocol is ASTM, when the inspection instrument needs to send inspection data, first send <enq>The control command character is sent to the information system HIS. If the information system HIS has resources to receive data, it will respond <ack>To the test instrument, otherwise answer <nak> ;< / nak> < / ack> < / enq> The test instrument successfully received <ack>After the control command character, the data frame will be sent. When the data frame is sent, <eot> The control command characters inform the information system HIS.< / eot> < / ack> 8. The medical testing instrument docking configuration system according to claim 2, characterized in that: When the docking port type is a database port and the transmission protocol is SQL, the information system HIS is connected to the database component of the inspection instrument according to the database address in the configuration parameter information, and uses SQL to read the row data in the corresponding data table and convert it into standard inspection data; the converted inspection data is sent to the information system HIS for reception.
Citation Information
Patent Citations
Inspection instrument and communication interface, communication system and communication method thereof
CN111985190A
Intermediate system of data interchange, and method of data interchange based on measuring instrument
CN1874273A