CN113626460B

CN113626460B - Data interaction method, device and storage medium for different pathology systems

Info

Publication number: CN113626460B
Application number: CN202110782325.XA
Authority: CN
Inventors: 李黎; 何轶兵
Original assignee: Wuhan Champath Image Technology Co ltd
Current assignee: Wuhan Champath Image Technology Co ltd
Priority date: 2021-07-12
Filing date: 2021-07-12
Publication date: 2023-11-03
Anticipated expiration: 2041-07-12
Also published as: CN113626460A

Abstract

The invention discloses a data interaction method, device and storage medium of different pathology systems, and belongs to the technical field of medical data interaction. The method comprises the following steps: establishing interface configuration information of different pathological systems, wherein the interface configuration information comprises a configuration table and a field relation table; acquiring patient information and constructing an application request W as an information extraction basis; judging interface definition modes according to the configuration table, and acquiring return information according to different interface definition modes and configurations in the configuration table; according to the field relation table, retaining a data result R required to be used in a pathological system from the returned information; performing content conversion on the result R according to the field relation table and the conversion configuration file to convert external data into an internally identifiable data structure S; constructing a transmitting module by using a reflection technology through a configuration table; and acquiring relevant data and documents of the pathology report from a pathology system database by using the pathology number pathlogy id, and issuing according to different interface definition modes in the configuration table.

Description

Data interaction method, device and storage medium for different pathology systems

Technical Field

The invention belongs to the technical field of medical data interaction, and particularly relates to a data interaction method, device and storage medium of different pathology systems.

Background

The patient information of pathology report has important reference significance for doctor to diagnose and treat diseases, but at present, most of hospital informatization architectures do not have a standardized interaction mode and data format among subsystems. Therefore, a set of pathological systems need to be well operated under different software environments, and a great deal of interface development work is needed. The interface work requires the data producer and consumer to respectively input new communication, agreement, development, debugging and other costs. Further, repeatedly developing interfaces with the same software behavior is also prone to introducing more errors. With the development of computer development languages, frameworks and data structures, design ideas such as tangent plane oriented programming and interface oriented programming appear. The invention designs a set of pathological diagnosis report method based on a data interface by utilizing a modern computer language and a framework, can reduce the interface coding workload of a pathological system to zero completely through a software configuration form, and greatly reduces the interface development cost of pathological diagnosis software.

Disclosure of Invention

The invention provides a data interaction method, a device and a storage medium for different pathology systems, which improves the secondary development efficiency of the data interaction of the pathology systems and other systems, improves the expansibility of a pathology diagnosis report system and reduces the risk in the data interaction process. The technical scheme is as follows:

in one aspect, an embodiment of the present invention provides a data interaction method for different pathology systems, where the method includes:

s101: interface configuration information of different pathology systems is created, wherein the interface configuration information comprises a configuration table and a field relation table.

S102: patient information is acquired and an application request W is constructed as an information extraction basis, and the patient information is used for a pathology system as pathology examination registration data.

S103: judging interface definition modes according to the configuration table, and acquiring return information according to different interface definition modes and configurations in the configuration table.

S104: the data result R that needs to be used in the pathology system is retained from the return information according to the field relation table.

S105: and carrying out content conversion on the data result R according to the field relation table and the conversion configuration file, so that external data are converted into an internally identifiable data structure S, and the data structure S is used for displaying and maintaining application information or patient information by a pathology system and is used as a data source of patient basic information on a pathology report.

S106: constructing a transmitting module by using a reflection technology through a configuration table; and acquiring relevant data and documents of the pathology report from a pathology system database by using the pathology number pathlogy id, and issuing according to different interface definition modes in the configuration table.

The configuration table comprises an interface classification Category, a table name TableName, a program set name AssembleFullName, a database script command SqlCommand, a database Category DbType, a database connection character string connectionString, a network service address WebServiceUrl, a network service function WebServiceMethod, a conversion configuration file name XsltName and a request parameter Param; the field relation table includes interface class Category, external database table column name ColumnName and internal database table column name PropertyName.

On the other hand, the embodiment of the invention also provides a data interaction device of different pathology systems, which comprises:

and (3) a configuration module: interface configuration information for creating different pathology systems, the interface configuration information comprising a configuration table and a field relation table.

The application information production module: for acquiring patient information for a pathology system as pathology examination registration data and constructing an application request W as an information extraction basis.

An information acquisition module: the method is used for judging the interface definition mode according to the configuration table and acquiring the return information according to different interface definition modes and the configuration in the configuration table.

And a data cleaning module: for retaining data results R from the returned information according to the field relation table, which are to be used in the pathology system.

And a data mapping module: the data structure S is used for displaying and maintaining application information or patient information by a pathology system and is used as a data source of patient basic information on a pathology report.

And a data transmitting module: constructing a transmitting module by using a reflection technology through a configuration table; and acquiring relevant data and documents of the pathology report from a pathology system database by using the pathology number pathlogy id, and issuing according to different interface definition modes in the configuration table.

In yet another aspect, embodiments of the present invention further provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the aforementioned data interaction method for different pathology systems.

The technical scheme provided by the embodiment of the invention has the beneficial effects that: the invention provides a data interaction method, a device and a storage medium for different pathological systems, and has the advantages of high speed, clear definition, good universality, high safety and the like.

Drawings

FIG. 1 is a flow chart of a method of data interaction for different pathology systems in an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present invention more apparent.

Example 1

Referring to fig. 1, an embodiment of the present invention provides a data interaction method for different pathology systems, where the method includes:

s101: and creating interface configuration information of different pathological systems, wherein the interface configuration information comprises a configuration table and a field relation table, and the pathological systems can be HIS, PACS, an integrated platform and the like.

S102: patient information, which can be specifically patient identification information such as an outpatient number, a hospitalization number or a physical examination number, is acquired and an application request W is constructed as an information extraction basis, wherein the patient information is used for a pathology system as pathology examination registration data.

S103: judging interface definition modes according to the configuration table, and acquiring return information according to different interface definition modes and configurations in the configuration table. The interface definition mode is generally based on an application layer protocol above a TCP protocol, the main types are HTTP, HTTPS, SOAP, a database transmission protocol and the like, the definition of the interface mode is D, and D is mainly judged according to whether a ConnectionString is set or not, wherein D can be a database (the ConnectionString is configured) and other (the ConnectionString is not configured); the DB is obtained by directly connecting a database, dynamic query sentences determined by configuration items are required to be formed by a database field splicing mode, and other interface calling modes such as HTTP, webService, socket, dll and the like are corresponding, and the calling modes and the implementation behaviors thereof are mainly responsible for program sets corresponding to an AssembleFullName; the latter constructs Param by configuration, param being an entry for interface conventions. The data directly acquired by the database do not need to be encrypted, and the data directly acquired by the non-database do not need to be encrypted so as to improve the security.

S105: and carrying out content conversion on the result R according to the field relation table and the conversion configuration file, so that external data are converted into an internally identifiable data structure S, and the data structure S is used for displaying and maintaining application information or patient information by a pathology system and is used as a data source of patient basic information on a pathology report.

S106: constructing a transmitting module by using a reflection technology through a configuration table; the method comprises the steps that pathology report related data and documents are obtained from a pathology system database by using a pathology number pathology id, the pathology report is issued according to different interface definition modes in a configuration table, the pathology report is generated by a conventional pathology report system, and the pathology report system is mainly responsible for a flow from specimen collection to diagnosis report issuing of a pathology department; the report from the pathology department is sent by the report issuing unit to the patient or the system used by the relevant doctor. The relevant data and the documents of the pathology report are sent to doctors in relevant departments or the patient himself or herself to report and acquire the relevant data and the documents in a self-help mode.

The configuration table comprises an interface classification Category, a table name TableName, a program set name AssembleFullName, a database script command SqlCommand, a database Category DbType, a database connection character string connectionString, a network service address WebServiceUrl, a network service function WebServiceMethod, a conversion configuration file name XsltName, a request parameter Param and the like; of course, other items may be included as desired, such as a configuration item description memory. The field relation table includes interface classification Category, external database table column name ColumnName, internal database table column name PropertyName, and other items, such as Description, may be included as required.

The step S103 specifically includes:

s1031: judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration or not; if yes, go to step S1032; if not (null), step S1033 is performed.

S1032: preparing a database access component DbConnector according to DbType in the configuration table, establishing database connection according to connectionString in the configuration table, obtaining an SQL query script according to the field relation table, and obtaining return information according to the DbConnector and the SQL query script.

S1033: if the interface contract is accessed through the form of web service, obtaining return information according to WebServiceUrl, webServiceMethod and Assemblely FullName in the configuration table; if the interface is called by other components, designating a program set to refer to other components according to an Assemblely FullName in a configuration table, dynamically loading the reference mode of the components by using MEF technology, adjusting function signature in application program calling, constructing an instance of the Assemblely FullName corresponding to the program set by using reflection technology, executing an interface calling process defined by the instance of the program set, and taking Param in the configuration table as an entry, wherein the data content in the { A } form is replaced by actual data, for example, name in pathological system data can replace { Name } by 'Zhang Sany', and # B# is used as the replacement of special processing text; as an alternative to special processing text, for example, text configured as #time# may be replaced with a specific Time in a format similar to 20210101080000 according to convention; and decrypting the returned information.

Wherein, step S104 includes: and according to the field relation table, the returned information is reserved to form a new data result R by an entry configured by the ColumnName in the field relation table, and the PropertyName in the field relation table is a corresponding pathological system data item.

The step S105 specifically includes: and R replaces the corresponding PropertyName according to the ColumnName configuration item in the field relation table, so that the external data is converted into an internally identifiable data structure S.

The construction process of the SQL query script is ColumnNam: a, propertyName: b, columnName: c, propertyName: d … …; construct as per statement select a as B, C as D from TableName where A = { B }.

The step S106 specifically includes:

s1061: constructing a sending module by using a reflection technology according to an Assemblely FullName in a field relation table, wherein the function of the sending module Interface is defined as Execute; the Execute function obtains pathology reports and related information according to the pathlogy id and performs report transmission according to the interface mode defined in the configuration table.

S1062: judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration (whether the configuration table is empty); if yes, go to step S1063; if not, step S1064 is performed.

S1063: constructing database connection through ConnectionString and DbType in a configuration table, configuring a script by using SqlCommand in the configuration table, and replacing dynamic data by using text template engines marked as { A }, and #B#, thereby forming executable update or insert database scripts; and executing the constructed database script through the corresponding database connection to finish report issuing.

S1064: if the interface is appointed to access through the form of web service, defining an accessed network address according to the WebServiceUrl in the configuration table, defining an access function name according to the WebServiceMethod in the configuration table, and specifically executing according to the AssembleFullName definition in the configuration table; if the interface contract is called by other components, designating a program set to reference the other components according to an Assemblely FullName in a configuration table, and dynamically loading the reference mode of the components by using an MEF technology; constructing an instance of an Assemblely FullName corresponding program set by a reflection technology, executing an interface calling process defined by the program set instance, and taking Param in a configuration table as an entry, wherein the data content in { A }, #B# forms is replaced by actual business data by a template engine technology; and encrypting the data acquired in a non-database direct connection mode.

S1065: and sending a report through a WebServiceMethod function of the WebServiceUrl according to the constructed program set execution function.

Further, the data interaction method of different pathology systems provided by the invention further comprises the following steps: distinguishing the data structure S obtained in the step S105 through field types, segmenting data related to pathological diagnosis through a proprietary pathological word stock, and storing the data for diagnostic analysis into a Hadoop cluster by using MapReduce operation; all data are stored into a pathology system database according to a pathology system data structure, and a corresponding pathology number pathology id is generated.

Example 2 (DB direct connection mode)

S101 acquires patient information: assembling an application message W sent to the HIS system according to the software interface configuration by using the application number patient identification information; the interface configuration is as follows:

the method for assembling the application message is realized by an assembling algorithm through a configuration table and a field relation table, and the DxDBConfigs structure of the configuration table mainly comprises interface classification Category, table name tableName and program set name

The configuration items such as an AssemblelyFullName, a database script command SqlCommand, a database category DbType, a database connection string connectionString, a network service address WebServiceUrl, a network service function WebServiceMethod, a configuration file name XsltName, a request parameter Param, a configuration item description Memo and the like; the field relation table DataExchange TableMappings mainly comprises interface classification Category, an external database table column name ColumnName, an internal database table column name PropertyName and a configuration item Description; the specific configuration is as follows:

category: order extraction-representing that the configuration is triggered in an interface extraction scenario

TableName：EXAM.PATH_TEST_MASTER a

full outer join EXAM.EXAM_MASTER b on a.TEST_NO = b.EXAM_NO

left join EXAM.PATH_TEST_TUMOUR c on a.TEST_NO = c.TEST_NO

left join EXAM.PATH_TEST_WOMAN d on a.TEST_NO = d.TEST_NO

-left join comm. Dept_dicot on a. Order_dept=e. Dept_code-review req_dept room, not associated according to order DEPT

left join COMM.DEPT_DICT f on f.DEPT_CODE = b.REQ_DEPT

left join MEDREC.pat_master_index g on b.PATIENT_ID = g.PATIENT_ID

left JOIN inpadm.pats_in_hospital h on h.patient_id =b.PATIENT_ID

The ward is the data in the inpaddm_in_hot table

left join COMM.DEPT_DICT i on i.DEPT_CODE = h.DEPT_CODE

left join COMM.AREA_DICT j on g.BIRTH_PLACE = j.area_code

left join (select test_no,count(*) times from EXAM.PATH_TEST_MASTER group by test_no) n on a.test_no = n.test_no

The script after the related query of the required data in the HIS database is carried out, in particular as follows,

AssemblyFullName：DataExchange.GetMedicalAdvice.BeiZhong.GetMedicalAdviceBeiZhong

program set name, i.e. the generic name of the class in the corresponding code

Sql command: null-sql command without additional execution

DbType: 1-load oracle Access component

ConnectionString：user id=path;password=path;data source= (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 194.1.2.181)(PORT = 1521))

(connect_data= (service_name=orcl))) -database join string

WebServiceUrl, webServiceMethod, xsltName, param is not applicable to DB direct connection mode.

S102: determining a protocol of an information acquisition interface, and according to actual configuration:

the definition D of the interface mode in the configuration table configuration is acquired, the configuration D is a database (the configuration D) and indicates that the configuration D is acquired by a direct database connection mode, and a dynamic query statement determined by configuration items is formed by a database field splicing mode, wherein the implementation process is as follows:

s1021: preparing a database access component Oracle DbConnector according to a database type DBType (1-oracle) indicated in the configuration table, and establishing database connection according to a configuration item ConnectionString.

The configuration table dataexchange tables contents are shown in table 1, for example:

table 1 configuration table dataexchange tables mapping content examples

A query script is constructed from the TableName in the configuration table and the ColumnName of the field relation table Dataexchange TableMappings, A, propertyName, B, columnName, C, propertyName, D … …: select null Tjh, case write b.patient_source=1 the 'clinic' else 'hospitalization' endPatents Source, … … … … … … … … null Patents AgeUnitfrom EXAM.path_TEST_MASTER a

full outer join EXAM.EXAM_MASTER b on a.TEST_NO = b.EXAM_NO

left join EXAM.PATH_TEST_TUMOUR c on a.TEST_NO = c.TEST_NO

left join EXAM.PATH_TEST_WOMAN d on a.TEST_NO = d.TEST_NO

left join COMM.DEPT_DICT f on f.DEPT_CODE = b.REQ_DEPT

left join MEDREC.pat_master_index g on b.PATIENT_ID = g.PATIENT_ID

left JOIN inpadm.pats_in_hospital h on h.patient_id =b.PATIENT_ID

The ward is the data in the inpaddm_in_hot table

left join COMM.DEPT_DICT i on i.DEPT_CODE = h.DEPT_CODE

left join COMM.AREA_DICT j on g.BIRTH_PLACE = j.area_code

left join (select test_no,count(*) times from EXAM.PATH_TEST_MASTER group by test_no) n on a.test_no = n.test_nowhere a.ExamNo = ‘000001’。

S1022: and connecting the Oracle DbConnector with the generated SQL query script by using a database to execute the command, thereby obtaining a returned result set DS.

S103: and C, cleaning a return result according to the interface mode definition D and the field configuration content of the interface field relation table DataExchange TableMappings, and forming a new data result R by using the items configured by ColumnName in the DataExchange TableMappings in the return result set DS obtained in the step S1022, wherein the data result R only comprises all data required to be used in a pathological system, and the PropertyName in the configuration table is a corresponding pathological system data item.

S104: and (3) carrying out corresponding PropertyName replacement on the result R in the step S103 according to the ColumnName configuration item in the Dataexchange TableMappings, namely, completing all field mapping by ColumnName1- > PropertyName1, columnName2- > PropertyName2 and … … … … ColumnNameN- > PropertyNameN, and thoroughly converting external data into an internally identifiable data structure S.

S104: storing the converted pathological system data into a relational database; the method comprises the following specific steps: distinguishing the data structure S obtained in the step S104 through field types, segmenting data related to pathological diagnosis such as specimen parts, clinical diagnosis, tumor information, gynecological information, operation views and the like through a proprietary pathological word stock, and storing the data for diagnostic analysis into a Hadoop cluster by using MapReduce operation; in addition, all data are stored into a pathology system database according to a pathology system data structure, and a corresponding pathology number pathology id is generated.

S105: the electronic report is sent to the doctor of the relevant department or the patient himself or herself through the report issuing unit based on the interface to obtain the report through self-service mode. The specific issuing steps are as follows:

report issuing the pathology report generated in step S104 and relevant diagnostic data through the configuration of reporting back or reporting archiving by category in the configuration table dxdbcon fig, the contents of which are shown in, for example, table 2:

table 2 dsdbcon figs table content example

The report issuing algorithm comprises the following specific implementation processes:

s1051: constructing a sending module by using reflection technology through an Assemblely FullName in a configuration table DxDBConfig, wherein the function of the sending module Interface is defined as Execute (string pathologyid); and obtaining relevant data and documents of the pathology report from a pathology system database by using a pathology number pathology id, and issuing according to different structures.

S1052: the service type of the report receiver is DB, database connection is constructed through ConnectionString and DbType, script configuration is carried out by using SqlCommand, dynamic data replacement is carried out by using text template engines marked as { A }, and #B#, so that executable update or insert database scripts are formed; the data return interface script of this example is as follows:

BEGIN

update EXAM.PATH_TEST_MASTER

set result_status= '4', final_report_time= '2020-01-01', final_report= 'Zhang three', support_report_time= '2020-01-01', support_report_report= { LastReportDr }

The window test_no= '000001'.

S1053: and executing report issuing, wherein the constructed script accesses the HIS system database through the Oracle DbConnector by using the configured connection character string, and executing the return script.

Example 3 (WebService service mode)

S101 acquires patient information: assembling an application message W sent to the HIS system according to the software interface configuration by using the application number patient identification information; the interface configuration is as follows: the method for assembling the application message is mainly realized through an assembling algorithm by configuration of a configuration table and configuration of a field relation table, wherein the configuration table DxDBConfig structure mainly comprises configuration items such as interface classification Category, table name TableName, program set name AssembleFullName, database script command SqlCommand, database Category DbType, database connection character string connectionString, network service address WebServiceUrl, network service function WebServiceMethod, configuration file name XsltName, request parameter Param, configuration item description Memo and the like; the field relation table dataexchange tables mainly comprises interface classification Category, external database table column name ColumnName and internal database table column name PropertyName. The specific configuration is as follows:

TableName: leave empty-non-database connection does not have a table name

AssemblyFullName

Dataexchange.getmedical address.qingyuan.getmedical advicefromwsqingyuan-neither the full path SqlCommand, dbType, connectionString of the program set to be run applies to webserviceuarl: http:// 172.18.0.63:10019/EaiServer-Webservice service Path webServiceMethod provided by HIS: HIPMessageServer-Webservice corresponds to the method name of the extraction interface, xsltName: and (5) extracting in hospitals for people far away. xslt-xslt file name for result conversion, default will find the file under program directory to make xml data conversion according to convention.

Memo: medical advice extraction interface configuration-interface configuration description of Qingyuan people hospital

Param：<xml version="1.0" encoding="gb2312"

< docbumentelement > < Access Key > [ Access Key ] </Access Key > < method ] </method name > < data Table > < event_id > { event_id } < event_id > < event_no > { event_id } < event_no > < card_no > { output event_id } < input_mode > < 1 input_mode > < input_id > { Tjh } < input_id > < - >, for physical examination

< begin_date > # 365yyyyMMddTime# </begin_date > # yyyyMMddTime# </end_date > < exec_dept >0320</exec_dept > < data_org_id > [ from org ] </data_org_id > < data_sys_id > [ from Sys ] </data_sys_id > </dataTable > </documetElement > -to the entry of Webservice.

S102: and determining the protocol of the information acquisition interface according to the actual configuration.

S1021: the method comprises the steps that definition D of an interface mode in configuration list configuration is obtained, connection string configuration exists, D is non-database direct connection (connection string is not configured), information is obtained by a network request according to the content of WebServiceUrl in a WebService mode, a sending process and conversion of an input parameter and an output parameter are constructed by configuration items, and the method comprises the following specific implementation processes:

s1022: the WebService mode obtains Web service description (wsdl) information of WebService according to the address of webserviceUrl and WebServiceMethod in the configuration table; the Webservice calling component, framework.webservice.dynamicwebservicecoding { random encoding }. Dll, is temporarily created through the information, and Webservice request is performed through the component to obtain the following return result:

U2FsdGVkX190W84KgYu6ONjEWMaiKBahWcVLduLvHx2qIN7+qN5eTimLNuVpy1Yt

wHxS+rTuOIohOAeK02w1WYIJebl+z3YlvdOjhVV+3xNRmpMfKPBXO+tbXuPyuivB

C2pfMa5oA3P/TrV6MZ3g6i06nNwnNn7Mh8nHBs/vGQjLG+vczCL0kEm4VD/VG7NK

qnX2CNG32qbQmKVYsEYRmYEURPCLi5nRBHUucyv49vUQCqPaWLn23iv/xCdk8Mkd

dhuUbV34CwoCFvDD0uTJpQXV4iZ+AoC2TEv6nZ0IyiDd/vg/skLjGJgx20qBzJnT

hjqCuF6cnLmOzOZisSOZ3GUdSC4mkGB2bLDsxyKLi5w66RvENs3PIjfMeszX/YQd

QT7/LEBn+yTabfSNOMDDqOz8NVJmGYTvKzr3lclfUc6wmReYLlr4QL7yTN/OxURl

/gQL9DQ6Q7CVZ3azsNIcrRxUTAQ5inPq7yc8EFN9tNr8ZovwX0Wl1mKCDhmjNR5Y

cExHknuAW+lxDRNbcQginniYtOhkqE86XKTCj5MLpt8I+s5/0UIaXZw/W61tg47Z

mJ/hiksi4OJsKFr51o8jAXxYfwPSHDBhA9hEle9hMS9qKXIEeU5VXgdGRsw78J7c

ImVn8lsstDp0RnkTjwynGH7u1u9ta0VdqSSEdl/meIQcJpeDkCclSXg4/EFbZY4V

JOQjxaE7jfNaOgnVxW1C1uFBjVS4YfAXd5mlt2NnGr9LL/BtmtEFThY1vD4s9kbH

O+cUv/G0ptIK0c4i/JOc2/omUHnw/XPAlA6KEAt4/Swq891HQC0jqsPRbnTjxRhm

TrtDC09/shy/1j8ygnce/1wCV2kU2a60TtMS5VP+lyxAEMjU2iTmJ8NBL3asISN3

sgGNXiU+PWsH62iAU4xbJAsA381JzPk4txr3EcqvGW8ye2p3rFFjflUtS60eyY6M

Oy7goZ3WQkpw24WIuyx/YP6wDzs6zTQDrVp7h6tK9+a4k1YKvV2A9R1U/bq6O0YC

EPpn0Uq67hsJvCcEZ6Qfxs3DhgJOdfJeDBQfi9weT0+x60Pq2Yp45B3zvjy62foh

ea7ArAqpdbOFh5fjCE1yow==。

s1023: decrypting the ciphertext data with the agreed key to obtain the following plaintext data:

<DATA>

<ROW>

< Xm > Yang Zhaoyou >

< Xb > Man >

< Nl >77 years old

< Sjks > urological hospitalization Sjks >

< Bq > hospitalization for urology

< Lczd > admission diagnosis: hematuria

</ROW>

</DATASET>

</DATA>

S1024: then, the xml- > xml data is converted by the Xslt extracted by Qingyuan people Hospital to form the xml data with the following format:

< PatitientName > Yang Zhaoyou PatitientName >

< PatitientSex > Men PatitientSex >

< PatitientAgeeUnit > years of age

< InstructionDepartment > urological hospitalization

< Inpatmentarea > for urological hospitalization

< clinical diagnosis > admission diagnosis: hematuria-

</Pitaya>

</ArrayOfPitaya>

The latter is a fixed format agreed with the pathology system, and xml format data from different sources are all converted into the format.

S103: and (3) further performing xml node data cleaning according to the data required by the pathological system, such as: converting the data of the coding type into content medical address- > medical address suitable for being read by a user, converting the date format of year, month and day of birth into the age and age unit 19900101- >31 years, wherein the data result R only comprises all data required to be used in a pathology system, and a data cleaning algorithm is used for checking and cleaning data items required by digital, coding and other data conversion in the pathology system and removing abnormal data to obtain available pathology data; the field mapping algorithm of the example is embodied in an xslt file, and the process of the original xml- > new xml is the data mapping process.

S104: storing the converted pathological system data into a relational database; the method comprises the following specific steps: distinguishing the data after data mapping through field types, segmenting data related to pathological diagnosis such as specimen parts, clinical diagnosis, tumor information, gynecological information, operation findings and the like through a proprietary pathological word stock, and then storing the data for diagnostic analysis into a Hadoop cluster by using MapReduce operation; in addition, the whole data is deserialized and then written into a pathology system database, and a corresponding pathology number pathology id is generated.

S105: the electronic report is sent to the doctor of the relevant department or the patient himself or herself through the report issuing unit based on the interface to obtain the report through self-service mode. The specific issuing steps are as follows: the pathology report generated in step S104 and the related diagnostic data are reported through the configuration of reporting back or reporting archiving by category in the configuration table dsdbcon fig.

The report issuing algorithm comprises the following implementation processes:

S1052: the service type of the report receiver is Webservice, and Web service description (wsdl) information of the Webservice is obtained according to the address of webserviceUrl and WebServiceMethod in the configuration table; the Webservice calling component framework, webservice, dynamicwebservicecoding { random encoding }. Dll, dynamic data replacement using a text template engine labeled { a }, #b #, constructs a message as follows:

1$HIP1105$<POOR_HIP1105 xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ITSVersion="XML_1.0" xsi:schemaLocation="urn:hl7-org:v3 file:///E:/hl7/HL7/v3ballot_fullsite_2011MAY/v3ballot/html/processable/multicacheschemas/HIP1105.xsd">

< | - -message ID- - >

< | - -message time- - >

< | - -message recipient-

<id>

</id>

</device>

</receiver>

</i > -message sender-

<id>

The manufacturer codes-

</id>

</device>

</sender>

The triggerEventID-2.16.840.1.113883.1.18 @ code: new indicates stop, update indicates update, delete indicates delete >

</i > -patient information-

</i > -patient-

< | - -patient identification object ]

<id>

< | - -Domain ID- - >

< | - -patient ID- - >

</i > -hospitalization number identification- >

</id>

The </i > -patient identification card number-

<id>

</id>

<item>

< part value= "Zhang San"/>

</item>

</name>

< | - -sex ]

< administrativeGenderCode code = "0000001" codeseystem= "2.16.156.10011.2.3.3.4" codeseystemname= "physiological sex code table (GB/T2261.1)" >

< displayName value = "Man"/>

</administrativeGenderCode>

< | - -date of birth ]

</patientPerson>

The < | -patient report department code- >

<id>

</id>

< | - -patient report department name- - >

<item>

< part value= "pathology"/>

</item>

</name>

Medical institution code-

<id>

</id>

< | - -medical institution name ]

< item > < part value= "Qingyuan City people Hospital"/>/item >

</name>

</wholeOrganization>

</asOrganizationPartOf>

</providerOrganization>

</patient>

</subject>

The number of times of consultation

<componentOf1 contextConductionInd="false" typeCode="COMP"

contextControlCode="OP">

<id>

The number of times of consultation

The clinic/hospitalization running water number

</id>

</i > -treatment category coding-

</i > -visit category name-

</code>

</subject>

</encounter>

</componentOf1>

</placerGroup>

</subject>

</i > -document body chapter-

</i > -integral PDF document-

<entry>

</entry>

</section>

</component>

The < | -document describes the chapter-

< component displayName = "document description information" >

<entry>

< | -associated application form information-

< | - -associated application form information(s) Loop-

</applicationNo >

</inFulfillmentOf>

< | -File-related information description- >

Uploading path name of unique path file of < | -fastdfs-

< filePath extension = "ftp://172.18.0.98/0000001" displayName= "File upload Path"/>

The </i > -File name-

< fileName extension = "File" displayName= "File name"/>

</fileInformation>

</i > -reporting related information-

The </I > -report running water number-

< reportSn extension = "0000001" displayname= "local System report number"/>

Version control of running Water number-

< reportSnTwo extension = "88920897-4c13-4952-9783-6374a7cb671a" displayName= "version control number"/>

The reporting type codes-

< reportTypeCode code = "009" displayname= "report type coding"/>

< | - -report type name- - >

< reportTypeName extension = "pathological system report" displayName= "report type name"/>

< | -report format: such as: pdf, jpg, html et al- >

< reportMedailType extension = "pdf" displayname= "report format"/>

The report references the Path Address-

< reportPath extension = "http://198.16.50.30:8080// Report/pitaya/findAll name=0000001" displayname= "Report browsing address"/>

</reportInfomation>

</entry>

</section>

</component>

</structuredBody>

</component>

</controlActProcess>

</POOR_HIP1105>.

S1053: obtaining Web service description (wsdl) information of the Webservice according to the address of webserviceUrl and WebServiceMethod in the configuration table; a Webservice calling component, framework.webservice.dynamicwebservicerating { random encoding }. Dll, is temporarily created from this information, and a Webservice request is made by this component to send the report data.

Example 4

Embodiment 4 provides a data interaction device for different pathology systems, the device comprising:

Wherein, the information acquisition module includes:

a first interface protocol judging unit: the method is used for judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration or not; if yes, executing a first database connection unit; if not, the non-database connection unit is executed.

Database connection unit: the method comprises the steps of preparing a database access component DbConnector according to DbType in a configuration table, establishing database connection according to connectionString in the configuration table, obtaining an SQL query script according to a field relation table, and obtaining return information according to the DbConnector and the SQL query script.

A non-database connection unit: the interface is used for obtaining return information according to WebServiceUrl, webServiceMethod and Assemblely FullName in the configuration table if the interface is accessed through the form of web service; if the interface is called by other components, designating a program set to refer to other components according to an Assemblely FullName in a configuration table, dynamically loading the reference mode of the components by using MEF technology, adjusting function signature when an application program is called, constructing an instance of the Assemblely FullName corresponding to the program set by using a reflection technology, executing an interface calling process defined by the instance of the program set, taking Param in the configuration table as an entry, wherein the data content in the { A } form is replaced by actual data, and taking # B# as a replacement of a special processing text; and decrypting the returned information.

The data transmission module comprises:

a transmission module creation unit: the method comprises the steps that a sending module is constructed by using a reflection technology according to an Assemblely FullName in a field relation table, and the function of the sending module Interface is defined as Execute; the Execute function obtains pathology reports and related information according to the pathlogy id and performs report transmission according to the interface mode defined in the configuration table.

A first interface protocol judging unit: the method is used for judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration or not; if yes, executing a database sending unit; if not, the non-database transmitting unit is executed.

A database transmitting unit: the method comprises the steps of constructing database connection through ConnectionString and DbType in a configuration table, configuring scripts by using SqlCommand in the configuration table, and replacing dynamic data by using text template engines marked as { A }, and #B#, so as to form executable update or insert database scripts; and executing the constructed database script through the corresponding database connection to finish report issuing.

A non-database transmitting unit: if the interface is accessed through the form of web service, defining an accessed network address according to the WebServiceUrl in the configuration table, defining an access function name according to the WebServiceMethod in the configuration table, and specifically executing according to the AssembleFullName definition in the configuration table; if the interface contract is called by other components, designating a program set to reference the other components according to an Assemblely FullName in a configuration table, and dynamically loading the reference mode of the components by using an MEF technology; constructing an instance of an Assemblely FullName corresponding program set by a reflection technology, executing an interface calling process defined by the program set instance, and taking Param in a configuration table as an entry, wherein the data content in { A }, #B# forms is replaced by actual business data by a template engine technology; and encrypting the data acquired in a non-database direct connection mode.

The transmission execution unit: the WebServiceMethod function for sending reports through webserviceureurl according to the structured program set execution function.

The foregoing description of the preferred embodiments of the invention is not intended to limit the invention to the precise form disclosed, and any such modifications, equivalents, and alternatives falling within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

1. A method of data interaction for different pathology systems, the method comprising:

s101: creating interface configuration information of different pathological systems, wherein the interface configuration information comprises a configuration table and a field relation table;

s102: acquiring patient information and constructing an application request W as an information extraction basis, wherein the patient information is used as pathology examination registration data by a pathology system;

s103: judging interface definition modes according to the configuration table, and acquiring return information according to different interface definition modes and configurations in the configuration table;

s104: according to the field relation table, retaining a data result R required to be used in a pathological system from the returned information;

s105: the data result R is subjected to content conversion according to the field relation table and the conversion configuration file, so that external data are converted into an internally identifiable data structure S, and the data structure S is used for displaying and maintaining application information or patient information by a pathology system and is used as a data source of patient basic information on a pathology report;

s106: constructing a transmitting module by using a reflection technology through a configuration table; acquiring relevant data and documents of a pathology report from a pathology system database by using a pathology number pathology id, and issuing according to different interface definition modes in a configuration table;

the configuration table comprises an interface classification Category, a table name TableName, a program set name AssembleFullName, a database script command SqlCommand, a database Category DbType, a database connection character string connectionString, a network service address WebServiceUrl, a network service function WebServiceMethod, a conversion configuration file name XsltName and a request parameter Param; the field relation table comprises interface classification Category, an external database table column name ColumnName and an internal database table column name PropertyName;

the step S103 specifically includes:

s1031: judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration or not; if yes, go to step S1032; if not, executing step S1033;

s1032: preparing a database access component DbConnector according to DbType in the configuration table, establishing database connection according to connectionString in the configuration table, obtaining an SQL query script according to the field relation table, and obtaining return information according to the DbConnector and the SQL query script;

s1033: if the interface contract is accessed through the form of web service, obtaining return information according to WebServiceUrl, webServiceMethod and Assemblely FullName in the configuration table;

if the interface is called by other components, designating a program set to refer to other components according to an Assemblely FullName in a configuration table, dynamically loading the reference mode of the components by using MEF technology, adjusting function signature when an application program is called, constructing an instance of the Assemblely FullName corresponding to the program set by using a reflection technology, executing an interface calling process defined by the instance of the program set, taking Param in the configuration table as an entry, wherein the data content in the { A } form is replaced by actual data, and taking # B# as a replacement of a special processing text; decrypting the returned information;

step S104 includes:

according to the field relation table, the returned information is reserved to form a new data result R by an entry configured by ColumnName in the field relation table, and the PropertyName in the field relation table is a corresponding pathological system data item;

the step S105 specifically includes:

the data result R is replaced by corresponding PropertyName according to a ColumnName configuration item in the field relation table, so that external data are converted into an internal identifiable data structure S;

the step S106 specifically includes:

s1061: constructing a sending module by using a reflection technology according to an Assemblely FullName in a field relation table, wherein the function of the sending module Interface is defined as Execute; the Execute function obtains pathology reports and related information according to the pathlogy id and executes report sending according to an interface mode defined in the configuration table;

s1062: judging whether the database is directly connected according to whether the ConnectionString in the configuration table has configuration or not; if yes, go to step S1063; if not, go to step S1064;

s1063: constructing database connection through ConnectionString and DbType in a configuration table, configuring a script by using SqlCommand in the configuration table, and replacing dynamic data by using text template engines marked as { A }, and #B#, thereby forming executable update or insert database scripts; the constructed database script is connected with the corresponding database to execute report issuing;

s1064: if the interface is appointed to access through the form of web service, defining an accessed network address according to the WebServiceUrl in the configuration table, defining an access function name according to the WebServiceMethod in the configuration table, and specifically executing according to the AssembleFullName definition in the configuration table;

if the interface contract is called by other components, designating a program set to reference the other components according to an Assemblely FullName in a configuration table, and dynamically loading the reference mode of the components by using an MEF technology; constructing an instance of an Assemblely FullName corresponding program set by a reflection technology, executing an interface calling process defined by the program set instance, and taking Param in a configuration table as an entry, wherein the data content in { A }, #B# forms is replaced by actual business data by a template engine technology;

encrypting the data obtained in a non-database direct connection mode;

s1065: sending a report through a WebServiceMethod function of WebServiceUrl according to the constructed program set execution function;

2. The method of data interaction for different pathology systems according to claim 1, further comprising:

distinguishing the data structure S obtained in the step S105 through field types, segmenting data related to pathological diagnosis through a proprietary pathological word stock, and storing the data for diagnostic analysis into a Hadoop cluster by using MapReduce operation; all data are stored into a pathology system database according to a pathology system data structure, and a corresponding pathology number pathology id is generated.

3. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, implements a method for data interaction of different pathology systems according to any one of claims 1-2.