CN115562714A - Medical data interface service processing method based on micro-service - Google Patents
Medical data interface service processing method based on micro-service Download PDFInfo
- Publication number
- CN115562714A CN115562714A CN202211209328.5A CN202211209328A CN115562714A CN 115562714 A CN115562714 A CN 115562714A CN 202211209328 A CN202211209328 A CN 202211209328A CN 115562714 A CN115562714 A CN 115562714A
- Authority
- CN
- China
- Prior art keywords
- data processing
- medical data
- data
- interface service
- processed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The application provides a medical data interface service processing method based on micro-services. The server is configured with a plurality of medical data processing interface services, and each medical data processing interface service is respectively associated with a corresponding data set model, and the method comprises the following steps: acquiring a calling request of a client for a target medical data processing interface service in a plurality of medical data processing interface services, wherein the calling request carries authority verification information and medical data to be processed; determining whether the client has the data processing authority or not according to the authority verification information; and under the condition that the client has the data processing authority, processing the medical data to be processed by using the data set model associated with the target medical data processing interface service. Therefore, a plurality of medical data processing interface services are configured through the server side, and each medical data processing interface service is respectively associated with the corresponding data set model, so that deep binding with a service system is avoided, and the problems in the prior art are solved.
Description
Technical Field
The application relates to the technical field of computers, in particular to a medical data interface service processing method based on micro-services.
Background
In the process of acquiring medical data, dirty data, repeated data, and the like generally exist in the acquired medical data, and therefore, data verification, cleaning, and other processing are often required to be performed on the medical data. The current systems for data verification and cleaning are usually deeply tied to the business system, resulting in the need for technicians to continually adjust the relevant codes in the systems for data verification and cleaning as the business system is updated.
Disclosure of Invention
The embodiment of the application aims to provide a medical data interface service processing method based on micro service, which is used for solving the problem that in the prior art, processing such as data verification or cleaning is deeply bound with a service system.
A first aspect of the embodiments of the present application provides a method for processing a medical data interface service based on microservice, where a server is configured with multiple medical data processing interface services, and each medical data processing interface service is associated with a corresponding data set model, and the method includes:
acquiring a calling request of a client to a target medical data processing interface service in the plurality of medical data processing interface services, wherein the calling request carries authority verification information and medical data to be processed;
determining whether the client has a data processing authority or not according to the authority verification information;
and under the condition that the client has the data processing authority, processing the medical data to be processed by using the data set model associated with the target medical data processing interface service.
In one embodiment, the method further comprises:
configuring a name of the target medical data processing interface service and the associated dataset model;
and issuing the target medical data processing interface service so that the client can send a call request of the target medical data processing interface service to the server.
In one embodiment, the data set model associated with the target medical data processing interface service is generated by the following method configuration:
configuring the name and a parameter template of the data set model, wherein the parameter template is provided with a plurality of fields;
adding a field list of the data set model, the field list being used to determine data processing rules for each field in the entry template.
In one embodiment, the method further comprises: and issuing the configured and generated data set model at a data set management center so as to be capable of correlating the data set model when the target medical data processing interface service is configured.
In an embodiment, the processing the medical data to be processed by using the data set model associated with the target medical data processing interface service specifically includes:
and performing data verification or data cleaning on the medical data to be processed according to the data processing rule of each field in the field list of the data set model associated with the target medical data processing interface service.
In an embodiment, the invoking request specifically includes: the HTTP call request comprises a request head and a request body, wherein the request head carries the authority verification information, and the request body carries the medical data to be processed.
In an embodiment, the request header further carries a target data processing type, the request body further carries a data format of the medical data to be processed, and the processing of the medical data to be processed by using the data set model associated with the target medical data processing interface service specifically includes:
storing the medical data to be processed into the data set model;
determining a data processing rule for each field in the data set model according to the target data processing type and the data format of the medical data to be processed;
and processing the medical data to be processed according to the data processing rule.
A second aspect of the embodiments of the present application provides a method for processing a medical data interface service based on a micro service, including:
sending a calling request of a target medical data processing interface service in a plurality of medical data processing interface services configured by a server to the server, so that the server processes medical data to be processed in the calling request by using a data set model associated with the target medical data processing interface service under the condition that the server determines that the client has a data processing authority according to authority verification information in the calling request;
and acquiring a response message generated by the server according to the data processing result.
In one embodiment, the method further comprises: and registering data processing permission to the server by using the permission verification information in advance.
In one embodiment, the method further comprises: and configuring a calling address of the target medical data processing interface service at a client so as to send the calling request to the server through the calling address.
By adopting the method provided by the embodiment of the application, the calling request of the client to the target medical data processing interface service in the plurality of medical data processing interface services of the server is firstly obtained, then whether the client has the data processing authority is determined according to the authority verification information carried by the calling request, and the medical data to be processed is processed by utilizing the data set model associated with the target medical data processing interface service under the condition that the client has the data processing authority. In this way, a plurality of medical data processing interface services are configured at the server side, and each medical data processing interface service is respectively associated with a corresponding data set model, so that data processing codes such as data verification or data cleaning and the like in the prior art are deeply bound with a business data table in a specific business system, the data are verified and cleaned in a mode of calling the medical data processing interface services, the medical data processing interface services are configured as required and the medical data processing interface services are called as required, so that the deep binding with the business system is avoided, and the data processing can be carried out by using the data set model associated with the target medical data processing interface service only by calling the target medical data processing interface service as required, so that the problems in the prior art are solved.
Drawings
To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating interaction between an electronic device and a client according to an embodiment of the present application;
fig. 3 is a schematic flowchart illustrating a method for processing a microservice-based medical data interface service according to an embodiment of the present application;
FIG. 4 is a schematic interaction diagram of a server and a client according to another embodiment of the present application;
FIG. 5 is a flowchart illustrating a method for processing a microservice-based medical data interface service according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a microservice-based medical data interface service processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a microservice-based medical data interface service processing apparatus according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the present application, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying a relative importance or order.
As described above, in the process of acquiring medical data, dirty data, repeated data, and the like are often present in the acquired medical data, and thus, data verification, cleaning, and the like are often required for the medical data. Current systems for data checksum cleansing are typically deeply tied to business systems, resulting in a technician needing to continually adjust the relevant code in the system for data checksum cleansing as business systems are updated.
Based on this, the embodiment of the application provides a medical data interface service processing method and device based on micro-services, an electronic device and a storage medium, which can solve the technical problem. As shown in fig. 1, which is a schematic structural diagram of an electronic device provided in this embodiment, the electronic device 1 includes: at least one processor 11 and a memory 12, one processor being exemplified in fig. 1. The processor 11 and the memory 12 are connected through the bus 10, and the memory 12 stores instructions executable by the processor 11, and the instructions are executed by the processor 11, so that the electronic device 1 can execute all or part of the flow of the data processing method in the embodiment of the present application.
In practical applications, the electronic device 1 may be a mobile phone, a notebook computer, a desktop computer, or a server and a server cluster formed by the mobile phone, the notebook computer, the desktop computer, or the like. For example, in an internet medical scenario, when medical data is processed for a hospital or a medical-related enterprise, the electronic device 1 may be a medical server or a medical server cluster.
As shown in fig. 2, in a micro-service scenario, the electronic device 1 may serve as a server, the server may be a server or a server cluster, the server may be connected to one or more clients 2, the client 2 may be a mobile phone or a computer of a user, or a public information query device installed in a hall of a hospital, and the server may perform data communication with each connected client 2. Therefore, the user can send a call request for the target medical data processing interface service to the server through the client 2, and the server can receive the call request.
For the micro-service-based medical data interface service processing method provided by the application, the method can be used for a server or a client. The server is configured with a plurality of medical data processing interface services, and each medical data processing interface service is associated with a corresponding data set model, and the data set models can be used for processing medical data, including data cleaning, data verification and the like of the medical data.
Fig. 3 is a schematic flowchart of a method for processing a medical data interface service based on microservice according to an embodiment of the present application, where the method may be executed by the electronic device 1 shown in fig. 1 as a server. The method comprises the following steps:
step S31: the method comprises the steps of obtaining a calling request of a client to a target medical data processing interface service in a plurality of medical data processing interface services of a server.
For example, when the client needs to invoke the target medical data processing interface service and performs data processing on medical data (hereinafter referred to as to-be-processed medical data), the invocation request may be sent to the server. Wherein, the calling request carries the authority verification information and the medical data to be processed.
The target medical data processing interface service may be any one of a plurality of medical data processing interface services at the server, may be a preset medical data processing interface service, and may be a medical data processing interface service dynamically configured according to a calling requirement when called by a user. For example, according to actual requirements including call duration, data processing type, data format of medical data to be processed, and the like, a user may screen medical data processing interface services to be called from each medical data processing interface service of a server in advance, take the screened medical data processing interface services as target medical data processing interface services, and configure a call address of the target medical data processing interface services at a client, so that the call request can be sent to the server through the call address.
In an embodiment, the user may configure the call address of the target medical data processing interface service on an information configuration page displayed by the client by means of touch, mouse click, keyboard input, and the like.
In an embodiment, before the user sends the call request to the server through the client, the user may generally register with the server in advance to obtain the permission verification information, for example, the user may register with the server by using a mobile phone number, an identity card number, an identifier of the client, and the like, so that the registered mobile phone number, the identity card number, and the like are used as the permission verification information. In this way, before the invocation request of step S31, the user may log in the account with the permission verification information, and after the login is successful, the invocation request is sent to the server through the client, where the invocation request may include the permission verification information, so that the server can determine whether the client (where the user has logged in) has the data processing permission by using the permission verification information.
In addition, in the step S31, the server may obtain the invocation request in various ways, for example, one way may be to directly receive the invocation request sent by the client; another way may be that the server obtains the call request from the call request queue, for example, in practical applications, because the server is connected with a plurality of clients, when a plurality of different users send call requests to the server through the clients respectively in a short time, the server may receive a large number of call requests in a short time, which results in a large computational pressure, at this time, in order to reduce the computational pressure of the server, the call request queue may be pre-constructed, and the call requests sent by the clients respectively are sequentially added to the call request queue according to the sequence of sending times or other ways, so that the server can sequentially obtain the call requests sent by the clients from the call request queue, thereby lowering the computational pressure of the server.
Step S32: and determining whether the client has the data processing authority or not according to the authority verification information carried by the calling request.
After the server side obtains the call request sent by the client side, whether the client side has the data processing permission or not can be determined according to permission verification information in the call request. For example, a data table may be stored in advance at the server, and the data table records the authority check information having the data processing authority. Therefore, in step S32, the authority verification information in the call request can be compared with the authority verification information recorded in the data table, and if the authority verification information recorded in the data table, including the authority verification information in the call request, is determined through the comparison, it can be determined that the client sending the call request has the data processing authority; otherwise, if the permission verification information recorded in the data table is determined through the comparison, the permission verification information in the call request is not included, which indicates that the verification is not passed, and it can be determined that the client sending the call request does not have the data processing permission. Therefore, step S32 can be realized in this manner.
Step S33: and under the condition that the client has the data processing authority, processing the medical data to be processed by using the data set model associated with the target medical data processing interface service.
As mentioned above, the server is configured with a plurality of medical data processing interface services, and each medical data processing interface service is associated with a corresponding data set model, which can be used for processing medical data, including data cleaning or data verification and the like of the medical data, so in step S33, the medical data to be processed can be processed by using the data set model associated with the target medical data processing interface service, for example, data verification or data cleaning and the like of the medical data to be processed by using the data set model associated with the target medical data processing interface service.
Of course, when the client does not have the data processing authority, the data processing of the medical data to be processed is not performed, and the client is prompted to have no data processing authority.
By adopting the method provided by the embodiment of the application, the calling request of the client to the target medical data processing interface service in the plurality of medical data processing interface services of the server is firstly obtained, then whether the client has the data processing authority is determined according to the authority verification information carried by the calling request, and the medical data to be processed is processed by utilizing the data set model associated with the target medical data processing interface service under the condition that the client has the data processing authority. In the method, a server side can be provided with a plurality of medical data processing interface services, each medical data processing interface service is respectively associated with a corresponding data set model, data processing codes such as data checking or data cleaning and the like in the prior art are deeply bound with a service data table in a specific service system, the data checking and cleaning are converted into a mode of calling the medical data processing interface services, the medical data processing interface services are configured as required, the medical data processing interface services are called as required, so that the deep binding with the service system is avoided, the data set model associated with the target medical data processing interface service can be utilized for data processing only by calling the target medical data processing interface service as required, and the problems in the prior art are solved.
It should be further noted that, in the method provided in this embodiment of the present application, for the data set model associated with each medical data processing interface service in the service end, the data set model may be generated by pre-configuration before being called, or may be generated by dynamic configuration according to a user call requirement, for example, a name of the data set model and a parameter template may be configured first, where the parameter template is provided with a plurality of fields, and then a field list of the data set model is added, where the field list is used to determine a data processing rule of each field in the parameter template. Of course, a unique number of the data set model may also be configured, and the unique number may be a default number generated in a default manner, so that the data set model may correspond to the unique number, and then be searched according to the unique number, and configure the associated data set model.
For a field list of the data set model, the field list may include field attributes, data processing rules, code attributes, and the like, where the values of the field attributes are fields in the entry template; the value of the data processing rule is the data processing rule of each field in the parameter template; the value of the code attribute is the specific program code.
For example, the field value of the field attribute may include id, code and name, which indicates that the participating template includes three fields of id, code and name. Moreover, the data processing rule of the id field is a value range rule, namely the data processing rule of the id field is determined to be a rule conforming to a preset value range; the data processing rule of the name field is a regular rule, namely the data processing rule of the name field is determined to be in accordance with a preset regular rule; the data processing rule of the code field is 'scriptmanager', that is, the data processing rule for determining the code field is determined by the script. In addition, the field list may further include data processing types, such as data checking, data cleaning, format conversion, and the like; data formats, such as XML, JSON, MAP, etc.; other data processing rules, such as data format check rules, data format conversion rules, data filling rules, and the like; and other attributes such as a whether loop attribute, for determining whether a loop is required, and so on.
After the plurality of data set models are configured and generated, the configured and generated data set models can be published in a data set management center, so that the data set models can be associated with a plurality of medical data processing interface services in advance before calling, or the data set models can be dynamically associated with the plurality of medical data processing interface services according to the calling requirement of a user, and then the medical data processing interface services are published, so that a client can send calling requests for the medical data processing interface services to a server, and data processing can be performed by using the data set models associated with the medical data processing interface services.
For example, in the method provided in the embodiment of the present application, a data set model associated with a target medical data processing interface service may also be generated in the manner described above, for example, a name, a unique number, and a parameter template of the data set model may be configured first, the parameter template is provided with a plurality of fields, and then a field list of the data set model is added, where the field list is used to determine data processing rules of each field in the parameter template.
After the data set model associated with the target medical data processing interface service is generated, the data set model can be further issued in a data set management center, so that when the target medical data processing interface service is configured and generated in advance before being called, or when the target medical data processing interface service is dynamically configured and generated according to the calling requirement of a user, the name of the target medical data processing interface service can be configured and the associated data set model can be configured through the data set management center. Of course, after the generation configuration is performed on the target medical data processing interface service, the target medical data processing interface service may also be issued to generate a call address of the target medical data processing interface service, so that the client can send a call request for the target medical data processing interface service to the server according to the call address.
For example, after the user screens out the target medical data processing interface service according to actual needs, the client acquires a call address of the target medical data processing interface service, so that a call request can be sent to the server through the call address.
In step S33, the medical data to be processed is processed by using the data set model associated with the target medical data processing interface service, which may be data verification and data cleaning.
For example, in the above-mentioned manner of configuring the data set model associated with the generation of the target medical data processing interface service, the name, the unique number and the entry template of the data set model are configured first, and then the entry template is provided with a plurality of fields, and a field list of the data set model is added, where the field list is used to determine the data processing rules of each field in the entry template. Therefore, when the medical data to be processed is processed by using the data set model, data verification or data cleaning can be performed on the medical data to be processed according to the data processing rule of each field in the field list of the data set model associated with the target medical data processing interface service.
For example, if the data verification is performed, the medical data to be processed is filled in according to the entry template of the data set model, and then the data verification is performed on the medical data to be processed in each field according to the data processing rule (referred to as a data verification rule at this time) of each field in the field list, including determining whether the value of the medical data to be processed in each field exceeds the value range, whether the data content meets the specification, and the like. If the data cleaning is carried out, the medical data to be processed can be filled in according to the entry template of the data set model, and then the medical data to be processed of each field is subjected to data cleaning according to the data processing rule (called as a data cleaning rule at this time) of each field in the field list, wherein the data cleaning comprises the steps of assigning default values and modifying the value exceeding the value range.
In addition, after the data processing is performed on the medical data to be processed in step S33, the method may further include sending a response message to the client, where the response message is generated according to a result of the data processing.
For example, after the medical data to be processed is subjected to data verification, a response message may be sent to the client, for example, if the data verification result is that the verification fails, the data processing result that the verification fails may be fed back to the client as the response message; in addition, indication information can be further added to the response information, and at this time, the response information includes the indication information in addition to the data processing result that the verification fails, where the indication information can be used to indicate a reason why the verification fails, for example, the medical data to be processed exceeds a value range or the data content does not conform to a specification, so that the user can adjust the medical data to be processed according to the indication information; or, if the check is passed, the data processing result passed through the check may be fed back to the client as a response message.
Of course, after the medical data to be processed is subjected to data cleaning, the data processing result of which the data cleaning is completed may also be fed back to the client as response information for prompting the user that the data cleaning is performed, and of course, the response information may also carry the cleaned medical data to be processed, so that the cleaned medical data to be processed is also fed back to the client through the response information.
It should be further noted that, in practical applications, the client and the server may perform data communication according to an HTTP communication protocol, and may also perform data communication according to other communication protocols. For example, as shown in fig. 4, when data communication is performed between the client and the server according to the HTTP communication protocol, the invocation request sent by the client to the server may be an HTTP invocation request, where the HTTP invocation request may be an invocation request sent according to the HTTP communication protocol. Correspondingly, the server side acquires the call request sent by the client side, and the call request can be an HTTP call request sent by the client side.
The HTTP call Request may include a Request Header (Header in fig. 4) and a Request body (Request in fig. 4) according to the rules of the HTTP communication protocol, wherein the Request Header may include the authority check information in the call Request, and the Request body may include the pending medical data in the call Request. For example, according to the rules of the HTTP communication protocol, the authority verification information may be encapsulated as a request header of the HTTP call request, and the medical data to be processed may be encapsulated as a request body of the HTTP call request.
Correspondingly, after the server side obtains the HTTP calling request, the HTTP calling request can be analyzed according to relevant rules of an HTTP communication protocol, and therefore the permission verification information and the medical data to be processed are obtained by analyzing a request head and a request body of the HTTP calling request.
In the method provided by the embodiment of the application, the request header of the HTTP call request may further carry a target data processing type, and the request body of the HTTP call request may further carry a data format of medical data to be processed. At this time, in step S33, the processing the medical data to be processed by using the data set model associated with the target medical data processing interface service may specifically include: and storing the medical data to be processed into the data set model, determining a data processing rule for each field in the data set model according to the target data processing type and the data format of the medical data to be processed, and processing the medical data to be processed according to the data processing rule.
It should be further noted that the data processing type may include multiple preset data processing types, such as data verification and data cleaning, and the target data processing type may be one or more of the preset data processing types selected as needed; the data format of the to-be-processed medical data carried in the request body may be the data format of the to-be-processed medical data itself, or may be separately stored identification information for identifying the data format of the to-be-processed medical data, and the data format may include any one or more of XML, JSON, MAP, and the like.
Correspondingly, the medical data to be processed is processed by using the data set model associated with the target medical data processing interface service, and the medical data to be processed carried in the request body can be stored in the data set model associated with the target medical data processing interface service. The data set model is provided with a plurality of fields corresponding to the medical data to be processed, and is used for receiving the medical data to be processed carried in the request body and processing the medical data to be processed according to the configuration of the data set model, including the processing of cleaning or checking and the like of the medical data to be processed. More specifically, the data set model may be stored in various fields of the reference template.
And then determining a data processing rule for each field in the data set model according to the processing type of the target data carried in the request header and the data format of the medical data to be processed carried in the request body. It should be noted that a data set model may be configured with multiple sets of data processing rules, which may include, for example, a data checking rule and a data cleansing rule for XML format data, a data checking rule and a data cleansing rule for JSON format data, and a data checking rule and a data cleansing rule for MAP format data. And determining which set of data processing rules need to be used to process the to-be-processed medical data stored in the data set processing model according to the target data processing type carried in the request head and the data format of the to-be-processed medical data carried in the request body.
More specifically, a data set model may include a plurality of field lists, each field list corresponding to a set of data processing rules corresponding to each field; the data processing method can also be used for enabling a data set model to comprise a field list, and the field list stores data processing rules of various fields under various data processing types and various data formats. A target field list in a data set model required to be used can be determined through the target data processing type carried in the request head and the data format of the medical data to be processed carried in the request body, so that the data processing rule of each field in the target field list is obtained; or the target data processing rule of each field in the field list in the data set model to be used can be determined, so that the data processing rule of each field in the data set model can be determined according to the target data processing type and the data format of the medical data to be processed.
And finally, processing the medical data to be processed according to the data processing rule. And performing data processing on the data to be processed stored in the data set model according to the determined data processing rule of each field in the data set model to obtain a corresponding data processing result. More specifically, the medical data to be processed in each field in the reference template may be processed according to the data processing rule corresponding to each field in the determined field list, so as to obtain a corresponding data processing result.
Of course, after the data processing is performed on the medical data to be processed, the server sends a response message to the client, where the response message may also be sent to the client according to an HTTP communication protocol, and the response message may be referred to as an HTTP response message. The HTTP response message also includes a request header and a request body, the request header of the HTTP response message may be empty (not carrying information), and the request body of the HTTP response message may include a data processing result.
Based on the same inventive concept as the method, the embodiment of the application can also provide a medical data interface service processing method based on micro service, and the method is applied to a client. Fig. 5 is a specific flow diagram of the method, which includes the following steps:
step S51: and sending a calling request for a target medical data processing interface service in a plurality of medical data processing interface services configured by the server to the server.
Step S52: and acquiring a response message generated by the server according to the data processing result.
Here, the steps S51 and S52 may be collectively described, in step S51, the client sends the invocation request to the server, where the invocation request carries the authority check information and the medical data to be processed, so that the server determines whether the client has the data processing authority according to the authority check information in the invocation request, and further processes the medical data to be processed in the invocation request by using the data set model associated with the target medical data processing interface service in the case of having the data processing authority. Certainly, after the server processes the medical data to be processed, a response message may be generated according to a data processing result, and then the response message is fed back to the client, so that the client can obtain the response message.
Since the method adopts the same inventive concept as the method shown in fig. 3, the problems in the prior art can be solved, and the description is omitted here.
Based on the same inventive concept as that of the method for processing medical data interface services based on micro services provided by the embodiment of the present application, the embodiment of the present application further provides a device for processing medical data interface services based on micro services, the device is applied to a server, the server is configured with a plurality of medical data processing interface services, each medical data processing interface service is respectively associated with a corresponding data set model, and for specific contents in the embodiment of the device, if there is an unclear point, reference may be made to the method embodiment described above. As shown in fig. 6, the apparatus 60 includes an acquisition unit 601, an authority determination unit 602, and a data processing unit 603, wherein:
an obtaining unit 601, configured to obtain a call request of a client to a target medical data processing interface service in the multiple medical data processing interface services, where the call request carries permission verification information and to-be-processed medical data;
an authority determining unit 602, configured to determine whether the client has a data processing authority according to the authority check information;
a data processing unit 603, configured to process the medical data to be processed by using the data set model associated with the target medical data processing interface service when the client has a data processing right.
With the device 60 provided in the embodiment of the present application, since the device 60 has the same inventive concept as the method provided in the embodiment of the present application, on the premise that the method can solve the technical problem, the device 60 can also solve the technical problem, and details thereof are not repeated here.
In addition, in practical applications, the technical effect obtained by combining the apparatus 60 with specific hardware devices is also within the scope of the present application, for example, different units in the apparatus 60 are distributed in different servers in a distributed cluster by using a distributed cluster manner, so as to improve efficiency and the like.
The apparatus 60 may further comprise a medical data processing interface service configuration publishing unit for configuring the name of the target medical data processing interface service and the associated data set model; and issuing the target medical data processing interface service so that the client can send a call request of the target medical data processing interface service to the server.
The apparatus 60 may further comprise a dataset model generation unit configured to generate a dataset model associated with the target medical data processing interface service by: configuring the name and a parameter template of the data set model, wherein the parameter template is provided with a plurality of fields; adding a field list of the data set model, the field list being used to determine data processing rules for each field in the reference template.
The apparatus 60 may further include a data set model publishing unit, which publishes the configured generated data set model in a data set management center, so as to be able to associate the data set model when configuring the target medical data processing interface service.
Wherein the processing the medical data to be processed by using the data set model associated with the target medical data processing interface service specifically includes: and performing data verification or data cleaning on the medical data to be processed according to the data processing rule of each field in the field list of the data set model associated with the target medical data processing interface service.
The device 60 may further include a response message sending unit, configured to send a response message to the client, where the response message is generated according to a data processing result.
The call request specifically includes: the HTTP call request comprises a request head and a request body, wherein the request head carries the authority verification information, and the request body carries the medical data to be processed.
The processing of the medical data to be processed by using the data set model associated with the target medical data processing interface service may specifically include: storing the medical data to be processed into the data set model; determining a data processing rule for each field in the data set model according to the target data processing type and the data format of the medical data to be processed; and processing the medical data to be processed according to the data processing rule.
Based on the same inventive concept as the method for processing the medical data interface service based on the micro service provided by the embodiment of the present application, the embodiment of the present application further provides a device for processing the medical data interface service based on the micro service, which is applied to a client, wherein the server is configured with a plurality of medical data processing interface services, each medical data processing interface service is respectively associated with a corresponding data set model, and for specific contents in the embodiment of the device, if there is ambiguity, reference may be made to the above method embodiment. As shown in fig. 7, the apparatus 70 includes a call request sending unit 701 and a response message obtaining unit 702, where:
a calling request sending unit 701, configured to send, to a server, a calling request for a target medical data processing interface service in multiple medical data processing interface services configured by the server, so that the server processes, according to permission verification information in the calling request, to-be-processed medical data in the calling request, by using a data set model associated with the target medical data processing interface service when determining that the client has a data processing permission;
a response message obtaining unit 702, configured to obtain a response message generated by the server according to the data processing result.
It is obvious that the device 70 can solve the problems of the prior art, and the description thereof is omitted.
The device 70 may further include a registration unit configured to register a data processing right with the server in advance using the right check information.
The apparatus 70 may further comprise a call address configuration unit configured to configure, at the client, a call address of the target medical data processing interface service, so that the call request can be sent to the server via the call address.
An embodiment of the present invention further provides a storage medium, including: a program that, when run on an electronic device, causes the electronic device to perform all or part of the procedures of the methods in the above-described embodiments. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like. The storage medium may also comprise a combination of memories of the kind described above.
Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A medical data interface service processing method based on micro-services is characterized in that a server is configured with a plurality of medical data processing interface services, and each medical data processing interface service is respectively associated with a corresponding data set model, and the method comprises the following steps:
acquiring a calling request of a client to a target medical data processing interface service in the plurality of medical data processing interface services, wherein the calling request carries authority verification information and medical data to be processed;
determining whether the client has a data processing authority or not according to the authority checking information;
and under the condition that the client has the data processing authority, processing the medical data to be processed by utilizing the data set model associated with the target medical data processing interface service.
2. The method of claim 1, further comprising:
configuring a name of the target medical data processing interface service and the associated dataset model;
and issuing the target medical data processing interface service so that the client can send a call request of the target medical data processing interface service to the server.
3. The method of claim 2, wherein the dataset model associated with the target medical data processing interface service is generated by a method configuration comprising:
configuring the name and a parameter template of the data set model, wherein the parameter template is provided with a plurality of fields;
adding a field list of the data set model, the field list being used to determine data processing rules for each field in the reference template.
4. The method of claim 3, further comprising: and issuing the configured and generated data set model at a data set management center so as to be capable of correlating the data set model when the target medical data processing interface service is configured.
5. The method according to claim 3, wherein the processing the medical data to be processed using the dataset model associated with the target medical data processing interface service comprises:
and performing data verification or data cleaning on the medical data to be processed according to the data processing rule of each field in the field list of the data set model associated with the target medical data processing interface service.
6. The method according to claim 1, wherein the invoking request specifically comprises: the HTTP call request comprises a request head and a request body, the request head carries the authority verification information, and the request body carries the medical data to be processed.
7. The method according to claim 6, wherein the request header further carries a target data processing type, the request body further carries a data format of the medical data to be processed, and the processing of the medical data to be processed using the data set model associated with the target medical data processing interface service specifically includes:
storing the medical data to be processed into the data set model;
determining a data processing rule for each field in the data set model according to the target data processing type and the data format of the medical data to be processed;
and processing the medical data to be processed according to the data processing rule.
8. A medical data interface service processing method based on micro-services is characterized by comprising the following steps:
sending a calling request of a target medical data processing interface service in a plurality of medical data processing interface services configured by a server to the server, so that the server processes medical data to be processed in the calling request by using a data set model associated with the target medical data processing interface service under the condition that the server determines that the client has a data processing authority according to authority verification information in the calling request;
and acquiring a response message generated by the server according to a data processing result.
9. The method of claim 8, further comprising: and registering data processing permission to the server by using the permission verification information in advance.
10. The method of claim 8, further comprising: and configuring a calling address of the target medical data processing interface service at a client so as to send the calling request to the server through the calling address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211209328.5A CN115562714A (en) | 2022-09-30 | 2022-09-30 | Medical data interface service processing method based on micro-service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211209328.5A CN115562714A (en) | 2022-09-30 | 2022-09-30 | Medical data interface service processing method based on micro-service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115562714A true CN115562714A (en) | 2023-01-03 |
Family
ID=84743284
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211209328.5A Pending CN115562714A (en) | 2022-09-30 | 2022-09-30 | Medical data interface service processing method based on micro-service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115562714A (en) |
-
2022
- 2022-09-30 CN CN202211209328.5A patent/CN115562714A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7389791B2 (en) | Implementing Compliance Settings with Mobile Devices to Adhere to Configuration Scenarios | |
| CN104580406B (en) | A kind of method and apparatus of synchronous logging state | |
| CN110557284B (en) | Data aggregation method and device based on client gateway | |
| CN110728455B (en) | Service processing method, service processing device, storage medium and electronic equipment | |
| CN111722947A (en) | Service calling method and system | |
| CN113268336B (en) | Service acquisition method, device, equipment and readable medium | |
| CN111427613B (en) | Application program interface API management method and device | |
| CN110838071A (en) | Policy data processing method and device and server | |
| CN113079164B (en) | Remote control method and device for bastion machine resources, storage medium and terminal equipment | |
| EP3614643A1 (en) | Oauth2 saml token service | |
| US20130096951A1 (en) | Business transaction capture and replay with long term request persistence | |
| US9350738B2 (en) | Template representation of security resources | |
| CN103001934A (en) | Terminal application login method and terminal application login system | |
| US20150326577A1 (en) | Accelerated application authentication and content delivery | |
| CN108764866B (en) | Method and equipment for allocating resources and drawing resources | |
| CN114598750A (en) | Data request processing method and device and storage medium | |
| CN109391658B (en) | Account data synchronization method and equipment, storage medium and terminal thereof | |
| CN112732547B (en) | Service testing method and device, storage medium and electronic equipment | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| CN115562714A (en) | Medical data interface service processing method based on micro-service | |
| CN111988298B (en) | Data processing method, device and equipment | |
| CN114143053A (en) | Third-party service login method and device, terminal equipment and storage medium | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN112837156A (en) | Transaction method and device with fixed execution sequence | |
| CN112860770A (en) | Report generation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |