CN111091894A

CN111091894A - Electrocardio equipment data processing method

Info

Publication number: CN111091894A
Application number: CN201911355946.9A
Authority: CN
Inventors: 祝佳骏; 李睿
Original assignee: Mobilemd System Jiaxing Co ltd
Current assignee: Shanghai Yikai Intelligent Technology Co ltd
Priority date: 2019-12-25
Filing date: 2019-12-25
Publication date: 2020-05-01

Abstract

The invention provides a method for processing data of electrocardio equipment, which comprises the following steps: different electrocardiograph devices collect electrocardiograph data in different formats; sending the electrocardiogram data with different formats to a server; the server sends the electrocardio data with the unified format to a back end after the electrocardio data are analyzed, wherein the analysis further comprises the following steps: monitoring whether the different electrocardio devices send new electrocardio data or not; selecting a subclass of a corresponding analysis abstract class to analyze according to the electrocardiodata with different formats, and analyzing the subclass into the electrocardiodata with the uniform format; and sending the electrocardio data with the uniform format to a back-end server. The invention realizes that the unified format data is automatically sent to the first-stage ward management system after the electrocardiographic examination of the testee is finished, thereby improving the accuracy and the efficiency.

Description

Electrocardio equipment data processing method

Technical Field

The invention mainly relates to a data processing method, in particular to a method for processing data of electrocardio equipment.

Background

Electrocardiography is an indispensable examination for a trial, and electrical data is important throughout the trial. The electrocardiograph equipment docking means that electrocardiograph data generated when a subject examines an electrocardiogram is docked into a system.

At present, the electrocardiogram data is connected to the system and transcribed to the system by copying the data. Or using traditional client CS software provided by an electrocardio manufacturer to view and copy data. The data is obtained by an artificial transcription method. It can be seen that the current solution does not support automatic transcription of electrocardiographic data into a system, and if electrocardiographic device data of different manufacturers need to be docked and transcribed everywhere, electrocardiographic data of different manufacturer software needs to be checked, unified processing cannot be achieved. The artificial transcription method has low efficiency and is easy to have errors, which is not favorable for the first-stage test.

Aiming at the problem of low butting efficiency of the electrocardio equipment, an effective solution is not provided at present.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a method for automatically inputting data into a system based on an electrocardiograph device, and through automatically inputting and uniformly storing electrocardiograph data of different electrocardiograph device manufacturers, on one hand, errors caused by artificial transcription are effectively avoided, and on the other hand, the overall efficiency of a first-stage test is improved.

In order to solve the technical problem, the invention provides a method for processing data of electrocardiograph equipment, which is characterized by comprising the following steps:

firstly, acquiring electrocardiogram data with different formats by different electrocardiogram equipment;

step two, sending the electrocardio data with different formats to a server;

step three, the server sends the electrocardio data with the unified format to a back end after the electrocardio data are analyzed, wherein the analysis further comprises the following steps:

step three, monitoring whether the different electrocardio devices send new electrocardio data or not; secondly, selecting a subclass of a corresponding analysis abstract class according to the electrocardiogram data with different formats for analysis, and analyzing the subclass into the electrocardiogram data with the uniform format;

and step four, sending the electrocardio data with the uniform format to a back-end server.

Preferably, the invention further provides a method for processing the data of the electrocardio equipment, which is characterized in that,

the parsing comprises a parser template design pattern, the parser template design pattern further comprising:

judging whether the electrocardiogram data file exists on a server hard disk or not;

judging whether the size of the electrocardiogram data file is normal or not;

and judging whether the electrocardio data file has a unique device mark.

the third step further comprises the step of combining the parser template design mode with the XML data files of the electrocardio data with different formats, wherein the parsing of the XML data files comprises the steps of completing the parsing of the XML data files through dom4j according to the definition tags in the XML data files, and extracting the electrocardio data in the XML data files.

the parser template design mode further comprises unified preprocessing of the electrocardio data files in different formats.

the preprocessing further comprises judging whether the electrocardio data file exists or not and judging whether the content of the electrocardio data file is complete or not.

after the preprocessing, the electrocardio data in different formats are delivered to different analyzer template subclasses for analyzing data and converting the data into internal electrocardio format data, and then the electrocardio data obtained by analyzing are converted into an ECGData electrocardio internal unified data format.

the electrocardio internal unified data format comprises examination starting time, heart rate, P-R interval, QRS time limit, QT interval, QTc interval, QRS electric axis, P electric axis and T electric axis.

the fourth step further comprises: and converting the electrocardio data with the unified format, and re-assigning values to the unified conversion object by taking values of the electrocardio data object.

Compared with the prior art, the invention realizes that the unified format data is automatically sent to the first-stage ward management system after the electrocardiographic examination of the testee is finished, thereby improving the accuracy and the efficiency.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 is a flow chart of the processing of electrocardiograph data in accordance with the present invention;

fig. 2 is a detailed flowchart of step 4 in fig. 1.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only examples or embodiments of the application, from which the application can also be applied to other similar scenarios without inventive effort for a person skilled in the art. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

As used in this application and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present application unless specifically stated otherwise. Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description. Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate. In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

In the description of the present application, it is to be understood that the orientation or positional relationship indicated by the directional terms such as "front, rear, upper, lower, left, right", "lateral, vertical, horizontal" and "top, bottom", etc., are generally based on the orientation or positional relationship shown in the drawings, and are used for convenience of description and simplicity of description only, and in the case of not making a reverse description, these directional terms do not indicate and imply that the device or element being referred to must have a particular orientation or be constructed and operated in a particular orientation, and therefore, should not be considered as limiting the scope of the present application; the terms "inner and outer" refer to the inner and outer relative to the profile of the respective component itself.

Spatially relative terms, such as "above … …," "above … …," "above … …," "above," and the like, may be used herein for ease of description to describe one device or feature's spatial relationship to another device or feature as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if a device in the figures is turned over, devices described as "above" or "on" other devices or configurations would then be oriented "below" or "under" the other devices or configurations. Thus, the exemplary term "above … …" can include both an orientation of "above … …" and "below … …". The device may be otherwise variously oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.

It should be noted that the terms "first", "second", and the like are used to define the components, and are only used for convenience of distinguishing the corresponding components, and the terms have no special meanings unless otherwise stated, and therefore, the scope of protection of the present application is not to be construed as being limited. Further, although the terms used in the present application are selected from publicly known and used terms, some of the terms mentioned in the specification of the present application may be selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Further, it is required that the present application is understood not only by the actual terms used but also by the meaning of each term lying within.

Referring to fig. 1, a flow chart of data processing of an electrocardiograph apparatus according to the present invention is shown.

Step 1, starting an electrocardio device;

step 2, the subject performs an electrocardiogram test and acquires electrocardiogram data through an electrocardiogram device;

in this case, the configuration of different electrocardiographic device manufacturers is different, so that the acquired data formats are completely different;

step 3, sending the electrocardiogram data of the testee to a server;

step 4, the server analyzes the electrocardio data by adopting an adaptive program and sends the electrocardio data to the back end;

the adapter in this step aims to convert the data of different vendors into an internal unified format. For example, A, B two manufacturers of electrocardiograph devices produce different data formats, such as two different data formats including xml and abc, and the data formats are analyzed into a unified electrocardiograph data format by this step and then sent to the back end.

Step 5, the back-end server receives the electrocardio data, specifically, the back-end server compares the checking date of the electrocardio data with the planned electrocardio checking date of the subject to select a proper form, calculates and stores the proper form into a data table;

and 6, finishing the whole process.

With respect to the step 4, the flow of the method will be further described in detail with reference to fig. 2, and the procedure of the adaptation program will be specifically described as follows:

step 21, starting the process;

step 22, configuring different folders according to different electrocardiographic devices and monitoring;

for example, the server IP address, e.g., 192.168.100.100, is configured on a different electrocardiograph device to home on the same server.

In addition, an A electrocardiogram manufacturer configures an electrocardiogram file folder to be C:/ABC, and a B electrocardiogram manufacturer configures an electrocardiogram file folder to be D:/ACB;

namely, three files are generated under each configured folder, the first file is the file names of the other two files and indicates that the generation of the electrocardiogram data is finished, and the other two files are the electrocardiogram data files obtained by testing.

The purpose of the monitoring in the process is to notify the program when a new file is generated in the folder.

Specifically, the program scans the folder every 5 seconds according to the configured scanning interval, and when a new file is generated under the folder, the program receives a message or notification that the new file is generated, thereby starting to parse the data file.

The specific implementation is accomplished through the commonsu packet of apache.

Step 23, generating data files in the configuration file folder;

step 24, using the common io packet of apache to monitor the set folder, wherein the interval time for scanning the folder is configured, and according to the configured interval time, for example, scanning the files in the folder every 5 seconds, comparing the files with the files in the folder scanned last time, when the number of the files is increased or decreased, the program will receive the notification of generating the new increase of the files;

step 25, analyzing and processing files of different types;

the file analysis in the invention adopts a template method design mode, and uniformly preprocesses different types of files, such as judging whether the data files exist or not and judging whether the content of the data files is complete or not. All data files are preprocessed by the abstract parser class of the abstract parser.

The data file corresponds to an electrocardiogram data file generated by the electrocardiogram equipment.

In the analysis processing step, data files generated by electrocardio equipment of different manufacturers and different models are analyzed and processed by a program in a unified way, and the specific implementation steps are as follows:

combining the template method design mode with the analysis of the ECG data XML file.

Step 251, sending the acquired electrocardiogram data file to an analyzer;

step 252, the parser designs a pattern code by using a template method;

step 253, the parser template includes the following functions:

firstly, judging whether an electrocardiogram data file exists on a server hard disk;

secondly, judging whether the size of the electrocardiogram data file is normal or not, wherein 0KB represents that the data is abnormal;

thirdly, judging whether the unique equipment mark exists in the electrocardiogram data file or not;

fourthly, the data file is analyzed. The corresponding subclass of the analytic abstract class is selected according to the electrocardiogram data files of different manufacturers and different models to complete the analysis, which is equivalent to defining a standard for the analytic abstract class, and the concrete realization is finished by different subclasses. The expansibility is good, then only the subclass of the abstract class needs to be added for the electrocardio data files of other manufacturers, and the function of the abstract class can be reused. The specific analysis adopts a mode of analyzing an XML data file, completes the analysis of the XML through dom4j according to the definition tags in the XML, and extracts the electrocardiogram data in the XML.

Step 254, storing the analyzed electrocardiogram data in a temporary java object, and finishing by means of object assignment;

step 255, return store completed data object. Usually, the data format generated by different electrocardiographic devices is an XML file, such as 100200300.XML, and electrocardiographic data is obtained by parsing the XML file and completed by a dom4j package. Different configuration folders correspond to different analysis classes, and the analysis classes can acquire the electrocardiogram data according to different XML files.

Step 26, obtaining the analyzed data and converting the data into a uniform format;

and uniformly converting the acquired electrocardiogram data into internal electrocardiogram format data.

(after preprocessing of the abstract server class, the data file is handed to different template subclasses to analyze the data and convert the internal electrocardio format data. for example, ECGXMLPArser class processes XML data and inherits the abstract class of the abstract server class, VSXMLPArser class processes XML data of other electrocardio manufacturers and inherits the abstract class of the abstract server class

And after the analysis is finished, obtaining the electrocardiogram data object, converting the data before sending the data, and re-assigning values to the unified conversion object by taking values of the electrocardiogram data object.

Step 27, sending the data in the unified format;

the converted internal electrocardio-format data is sent to a back-end application server through an HTTP request;

and step 28, ending.

The adaptation program of the invention adopts java language development, and cross-platform support is adopted to deploy and install on different systems. The program is adapted to various different hardware measuring devices, and the electrocardio device and the vital sign instrument which are in butt joint at present are respectively in butt joint with different third-party hardware manufacturers. By the method, the butt joint is uniformly processed, so that the butt joint work of the measurement hardware equipment of the same manufacturer and different models is reduced. The data format structure of the same manufacturer is basically the same, and the program well encapsulates the same processing so as to be convenient for the subsequent multiplexing of equipment with other models. The package adopts a template method design mode, defines a common abstract processing logic, and determines whether a data file generated for hardware equipment in the program exists or not and whether the content of the data file is complete or not. Concrete processing logic that is not a common abstraction is handled by a subclass of concrete template methods.

Flow charts are used herein to illustrate operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing disclosure is by way of example only, and is not intended to limit the present application. Various modifications, improvements and adaptations to the present application may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present application and thus fall within the spirit and scope of the exemplary embodiments of the present application.

Also, this application uses specific language to describe embodiments of the application. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the present application is included in at least one embodiment of the present application. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the present application may be combined as appropriate.

Aspects of the present application may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present application may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).

The computer readable medium may comprise a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, and the like, or any suitable combination. The computer readable medium can be any computer readable medium that can communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device. Program code on a computer readable medium may be propagated over any suitable medium, including radio, electrical cable, fiber optic cable, radio frequency signals, or the like, or any combination of the preceding.

Similarly, it should be noted that in the preceding description of embodiments of the application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to require more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

Although the present application has been described with reference to the present specific embodiments, it will be recognized by those skilled in the art that the foregoing embodiments are merely illustrative of the present application and that various changes and substitutions of equivalents may be made without departing from the spirit of the application, and therefore, it is intended that all changes and modifications to the above-described embodiments that come within the spirit of the application fall within the scope of the claims of the application.

Claims

1. A method for processing data of an electrocardio device is characterized by comprising the following steps:

step two, sending the electrocardio data with different formats to a server;

2. The method for processing electrocardiograph data according to claim 1,

judging whether the size of the electrocardiogram data file is normal or not;

and judging whether the electrocardio data file has a unique device mark.

3. The method for processing electrocardiograph data according to claim 2,

4. The method for processing electrocardiograph data according to claim 3,

5. The method for processing electrocardiograph data according to claim 4,

6. The method for processing electrocardiograph data according to claim 5,

7. The method for processing electrocardiograph data according to claim 6,

8. The method for processing electrocardiograph data according to claim 7,