CN112434187A - Medical data service method and system based on configurable API (application program interface) - Google Patents
Medical data service method and system based on configurable API (application program interface) Download PDFInfo
- Publication number
- CN112434187A CN112434187A CN202011309565.XA CN202011309565A CN112434187A CN 112434187 A CN112434187 A CN 112434187A CN 202011309565 A CN202011309565 A CN 202011309565A CN 112434187 A CN112434187 A CN 112434187A
- Authority
- CN
- China
- Prior art keywords
- interface
- module
- data service
- medical data
- xml
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000010276 construction Methods 0.000 claims description 6
- 238000010168 coupling process Methods 0.000 abstract description 2
- 238000005859 coupling reaction Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 201000010099 disease Diseases 0.000 description 4
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000035515 penetration Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/81—Indexing, e.g. XML tags; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/83—Querying
- G06F16/835—Query processing
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Theoretical Computer Science (AREA)
- Public Health (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Medical Informatics (AREA)
- Biomedical Technology (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- Primary Health Care (AREA)
- Software Systems (AREA)
- Pathology (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention discloses a medical data service method and system based on a configurable API (application program interface), belonging to the field of big data, wherein the method comprises the following steps: constructing a spring framework, wherein the spring framework comprises an administration tool eureka; specifying within a configuration file the administrative tool eureka instance that needs to be connected, the enabling of discovery and enabling of discovery of other instances in a start-up function within the administrative tool eureka instance; acquiring a message body in an XML format, wherein the message body comprises at least one tag; analyzing the at least one label to obtain corresponding parameters; and calling a back-end interface through the parameters and obtaining an XML result set. The method and the device have the advantages that the parameter type, the number and the like of the rear-end interface are changed from unchangeable to changeable, and the high-coupling front end and the rear end are decoupled to a certain degree, so that developers do not need to use repeated codes on the same business logic for many times, and the debugging cost is reduced.
Description
Technical Field
The invention relates to the field of big data, in particular to a medical data service method and system based on a configurable API (application program interface).
Background
The medical data service system is an important system for managing hospital information and comprises a front end, a back end, a database and other components. The front end is responsible for displaying pages to users, and the back end is responsible for processing business logic, inquiring data in a database and the like.
In most medical data service systems of hospitals, the interaction between the front end and the back end is realized by transmitting parameters, and the front end only needs to transmit the parameters required by the back end and receive the query result set transmitted back by the back end. When the front end queries the back end, it is a common practice in the industry to fix parameters of the back end interfaces, that is, request parameters of each back end interface are fixed parameters (fixed type and fixed number). If the medical data service system adds other parameter inquiry on the existing service, an interface is reserved firstly, and the interface parameters are expected by developers. After the service is on line, the parameter type is adjusted according to the entity service, the interfaces with different parameters of the same service are newly added, and simultaneously, each interface is formed into a document for the user to refer to. In some scenarios, when the front end needs to query multiple parameters of the same service to the back end, the front end needs to split the multiple parameters into a single parameter, the single parameter is transmitted to the corresponding back end interface for querying, and then each individual query result is merged and displayed.
The above prior art solutions have the following disadvantages:
when a service requires parameter change, although only the parameter type or the parameter number is changed, the backend interface of the fixed parameters is difficult to change in time, which results in a longer development period and an increased workload of personnel.
When a back-end interface is newly developed, a developer is unskilled in service, so that the reserved interface does not meet requirements on the service, the back-end interface needs to be added after the service is online, and the project cost is increased. Meanwhile, due to the writing level problem of the document at the rear end, the document is difficult to understand by the user, and the problem that the user is difficult to use exists.
When the front end needs to query for many times, splitting multiple parameters into a single parameter consumes certain performance of the front end, and the response speed to the front end is obviously reduced. Meanwhile, multiple query requests occupy excessive bandwidth, so that network congestion is caused, and query efficiency is reduced.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a medical data service method and system based on a configurable API (application program interface). the parameter type, the number and the like of a rear-end interface are changed from unchangeable to changeable, and the high-coupling front end and the rear end are decoupled to a certain degree, so that developers do not need to use repeated codes on the same business logic for many times, and the debugging cost is reduced.
The invention discloses a medical data service method based on a configurable API (application program interface), which comprises the following steps:
constructing a spring framework, wherein the spring framework comprises an administration tool eureka;
specifying within a configuration file the administrative tool eureka instance that needs to be connected, the enabling of discovery and enabling of discovery of other instances in a start-up function within the administrative tool eureka instance;
acquiring a message body in an XML format, wherein the message body comprises at least one tag;
analyzing the at least one label to obtain corresponding parameters;
and calling a back-end interface through the parameters and obtaining an XML result set.
Specifically, before obtaining the message body in the XML format, the method further includes:
acquiring a service number, a service name and a service type;
determining that the message format is XML or JSON;
importing or inputting a message template and storing the message template into a database; the parameter type in the message template corresponds to the back-end interface to be called.
Specifically, the service number is a unique identification and cannot be repeated.
Specifically, analyzing the at least one tag to obtain a corresponding parameter includes:
analyzing the tag in the message body in the XML format through a jackson library;
obtaining corresponding parameters from the label, and obtaining a back-end interface to be called according to the parameter type;
and assembling a plurality of parameters into an object and transmitting the object into a corresponding rear-end interface.
Specifically, if the number of objects is greater than the maximum query number N, the first N objects are transmitted to the backend interface; and the back end analyzes the object, obtains fields in the object, queries the fields to generate a single result set, and combines all the single result sets into an XML result set.
Specifically, the message body in the XML format includes a front-end service request and a third-party service request.
The invention discloses a medical data service system based on a configurable API (application program interface), which comprises:
the spring framework comprises a construction module, a management module and a management module, wherein the construction module is used for constructing a spring framework which comprises a management tool eureka;
a specifying module, configured to specify, in a configuration file, the management tool eureka instance that needs to be connected, where the start function in the management tool eureka instance is allowed to be discovered and other instances are allowed to be discovered;
the message acquisition module is used for acquiring a message body in an XML format, and the message body comprises at least one tag;
the analysis module is used for analyzing the at least one label to obtain a corresponding parameter;
and the result acquisition module is used for calling the back-end interface through the parameters and acquiring an XML result set.
Through the technical scheme, the technical effects are as follows: according to the method and the system, a data service system is added in the front end and the back end and serves as a role of a middle person to analyze parameters and call a corresponding back end interface, so that the later maintenance cost and the new development function cost are greatly reduced. Meanwhile, under the condition that the server is not added, the front-end data request is processed concurrently, and the performance is improved. And the front end does not need to request for many times when carrying out multi-parameter query, and returns a result set once.
Drawings
FIG. 1 is a block diagram of a hardware configuration of a data service computer disclosed in an embodiment of the present application;
FIG. 2 is a flow chart of a medical data service method disclosed in an embodiment of the present application;
FIG. 3 is a flow chart of a front-end or third party registration process disclosed in an embodiment of the present application;
FIG. 4 is a diagram of a front-end or third-party registration interface disclosed in an embodiment of the present application;
FIG. 5 is a flowchart illustrating a tag parsing process disclosed in an embodiment of the present application;
fig. 6 is a maximum query number interface diagram disclosed in an embodiment of the present application.
Detailed Description
Exemplary embodiments will now be described more fully with reference to the accompanying drawings. The exemplary embodiments, however, may be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.
The embodiment of the application provides a medical data service method and a medical data service system based on a configurable API (application program interface), the standard for transmitting query data is specified, and a message body in an XML format in one query request comprises a plurality of parameters, so that a single query request is realized, and a plurality of result sets are returned at one time; the method can be applied to data service systems in various fields. The medical data service method may be executed in a server, a computer, or a similar arithmetic device. Taking an example of the data service computer running on a computer, fig. 1 is a hardware structure block diagram of the data service computer disclosed in the embodiment of the present application. As shown in fig. 1, computer 10 may include one or more (only one shown in fig. 1) processors 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, and optionally may also include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those of ordinary skill in the art that the configuration shown in FIG. 1 is illustrative only and is not intended to limit the configuration of the computer described above. For example, computer 10 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 may be used for storing a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the medical data service method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by executing the computer program stored in the memory 104, so as to implement the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by the communications provider of computer 10. In one example, the transmission device 106 includes a Network adapter (NIC), which can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
FIG. 2 is a flow chart of a medical data service method disclosed in an embodiment of the present application; the method comprises the following steps:
s1, constructing a spring framework, wherein the spring framework comprises a management tool eureka;
in order to improve high concurrency and high availability of a data service system, the system adopts a springclosed framework to support multi-instance deployment; the management multi-instance is a spring framework default self-contained management tool: eureka.
S2, specifying the management tool eureka instance needing to be connected in a configuration file, wherein discovery is allowed and other instances are allowed in a starting function in the management tool eureka instance;
the administrative tool eureka can automatically implement load balancing, that is, when the front end requests the data service system, eureka can randomly distribute the request to each instance, so as to implement high availability.
S3, acquiring a message body in an XML format, wherein the message body comprises at least one tag;
in the embodiment of the invention, the message body is service data generated on line by an internet hospital, such as diagnosis and treatment service and reimbursement service, and comprises data generated on a plurality of front ends, such as inquiry data and filled case data of a patient end, triage data of a hospital end, receiving data and prescription data of a doctor end and the like. Generating a data body in an XML format through the service data; each business data corresponds to an object, and the object consists of a plurality of labels;
in an embodiment of the present invention, the tag content may include a version number, patient information, and medical information, where the version number is used to mark version replacement of the tag to adapt to a change situation of the tag content that is developed over time, and the patient information includes: user account, time, hospital ID, gender, age, etc., the medical information includes: disease type, examination items, and case information.
S4, analyzing the at least one label to obtain corresponding parameters;
in the embodiment of the invention, the labels in the message body input by the front end or the third party are keywords such as the age, sex, disease category and examination item of the patient, and the labels in the message body are analyzed to obtain corresponding parameters, wherein the corresponding parameters can be 'highly fatal diseases for men aged 30-40'.
And S5, calling a rear-end interface through the parameters and obtaining an XML result set.
In the embodiment of the invention, the number of times to be inquired is determined through a plurality of parameters in the data body in the XML format, the back-end interface is respectively called for many times by using a loop mechanism, and the back-end interface receives the parameters and then analyzes the parameters through jackson to obtain a list containing the parameters. Traversing the parameters in the list, generating a single result set for each parameter, transmitting the single result set into a jackson library, combining the result sets into an XML result set, returning the XML result set to the front end, and rendering and displaying the front end based on the XML result set.
In terms of high concurrency, data service systems introduce redis. The redis caches frequently used data in the database, thereby improving the response speed of the system. The system also limits cache penetration and cache avalanche at the same time, and limits the front-end calling frequency when cache avalanche and penetration occur in redis. Simultaneously, taking corresponding measures: starting a database to be directly connected; limiting the front-end connection frequency to a lower level; and informing the operation and maintenance personnel to check redis.
The above process is a front-end or third-party standard query process. The data service plays the role of a middle person, namely, the data service process does not directly inquire data but acts as a proxy in the middle. The fixed parameter type is changed into a key value pair in an XML mode, and the parameter type is dynamically changed. Meanwhile, multiple parameters are packaged in one XML file by utilizing the repeatability of XML tags and tags, so that a front end or a third party does not need to request for multiple parameters for query for multiple parameters for once, multiple parameters are requested for once, and a result set is returned for once.
Optionally, fig. 3 is a flowchart of a front-end or third-party registration process disclosed in the embodiment of the present application; before obtaining the message body in the XML format, the method further includes:
s01, acquiring a service number, a service name and a service type;
in the embodiment of the present invention, fig. 4 is a front-end or third-party registration interface diagram disclosed in the embodiment of the present application; contacting a data service system administrator to enter a data service system background, and adding front-end or third-party information in the background; the front-end or third-party information includes a service number, a service name, and a service type.
In the embodiment of the invention, the service number is the unique identification of the front end or the third party, and the service number cannot be repeated because the front end or the third party may exist in a plurality of numbers; the service name can be defined by self according to requirements, such as a user a _ electronic medical record system and a user b _ disease statistical data system; the service type is a DataService type;
s02, determining that the message format is XML or JSON;
in the embodiment of the invention, the message format is obtained by the user through autonomous selection in the front-end interface. XML is an extensible markup language, a subset of the standard universal markup language, and is a markup language used to mark electronic documents to be structured.
S03, importing or inputting a message template and storing the message template into a database; the parameter type in the message template corresponds to the back-end interface to be called.
In the embodiment of the invention, the message template stores the information of the front-end interface in a key-value pair mode, and each item on the front-end interface has a fixed label corresponding to the item in the message template; the message template can be imported in a file form or directly input on an interface, and then the imported or input message template is stored in a database so as to call the template in later use.
The data service process can not directly identify the front-end and back-end programs, and can be used only by registering and configuring in the data service system, thereby facilitating the unified management of each front-end and third party.
Optionally, fig. 5 is a flowchart for parsing a tag disclosed in the embodiment of the present application; analyzing the at least one label to obtain corresponding parameters, including:
s21, analyzing the tag in the message body in the XML format through a jackson library;
in the embodiment of the present invention, a jackson library is referred to in the IDEA, which is a commercially sold Java Integrated Development Environment (IDE) tool software, developed by jetbranches software corporation (formerly known as IntelliJ), and provides community versions with Apache 2.0 open authorization and commercial versions of proprietary software, which developers can select for downloading.
S22, obtaining corresponding parameters from the tags, and obtaining a rear-end interface to be called according to the parameter types;
in the embodiment of the present invention, the parameter is included in the body, an XML or json (json, JavaScript Object Notation, JS Object Notation) string in the body of the HTTP request is serialized into a map structure, and the map structure is traversed to obtain a field value corresponding to the tag.
And S23, assembling a plurality of parameters into objects and transmitting the objects into corresponding rear-end interfaces.
In the embodiment of the invention, when the database is queried through the program, parameters needing to be queried in the program are not directly specified, but a lot of data are abstracted into one object. Such as: the database has fields of gender, age, height, weight, etc., and these fields are abstracted to the object, and the data is queried according to the object.
And (4) optional. If the number of the objects is larger than the maximum query times N, transmitting the first N objects into a rear-end interface; and the back end analyzes the object, obtains fields in the object, queries the fields to generate a single result set, and combines all the single result sets into an XML result set.
In the embodiment of the present invention, a plurality of queries is an important part. One request can be inquired for many times, so that the inquiry times can be controlled, the use pressure of the network can be effectively reduced, the use efficiency is increased, and the inquiry is normalized. Meanwhile, the DOS attack can be prevented by limiting the query times. DoS is a short term for Denial of Service, i.e., Denial of Service, and the attack behavior of DoS is called DoS attack, which aims to make a computer or a network unable to provide normal services. The most common DoS attacks are computer network broadband attacks and connectivity attacks. For example: when inquiring the patient information, the inquiry of 50 pieces of patient information at most can be limited by one inquiry, and the inquiry can be customized according to the needs. When querying the user right, it is restricted to query only one user right (current user) at a time.
In the embodiment of the present invention, fig. 6 is a maximum query number interface diagram disclosed in the embodiment of the present application; the maximum connection times are set on the front end or third party page, and the setting is set before the request of the front end or the third party and is stored in a database. When the front end or the third party sends a data service request, the data service system finds the maximum query times N in the database. If the number of the objects is larger than the maximum query times N, transmitting the first N objects into a rear-end interface; and if the number of the objects is less than the maximum query times N, normally querying according to the method.
In the embodiment of the invention, multi-parameter multi-time query can also be realized by using a plurality of distributed servers. And a plurality of servers are deployed by using nginx, the gateways are unified externally, a plurality of requests are distributed to each server when the front end requests data, and each server only executes one query, so that the plurality of queries can be realized. Meanwhile, the scheme needs to use a deployment strategy of 1+1+ N +1, 1 front end, one data service system, N background logic processing servers and 1 database. The scheme is suitable for a high-concurrency query environment, each backend program in nginx can perform multiple queries, and load can be balanced.
Optionally, the message body in the XML format includes a front-end service request and a third-party service request.
In the embodiment of the invention, the transmission protocol of the data service system is based on the web service frame, so that all third-party frames using the web service protocol can transmit data with the data service system after being authorized by an administrator.
The embodiment also discloses a medical data service system based on the configurable API interface, which includes:
the spring framework comprises a construction module, a management module and a management module, wherein the construction module is used for constructing a spring framework which comprises a management tool eureka;
a specifying module, configured to specify, in a configuration file, the management tool eureka instance that needs to be connected, where the start function in the management tool eureka instance is allowed to be discovered and other instances are allowed to be discovered;
the message acquisition module is used for acquiring a message body in an XML format, and the message body comprises at least one tag;
the analysis module is used for analyzing the at least one label to obtain a corresponding parameter;
and the result acquisition module is used for calling the back-end interface through the parameters and acquiring an XML result set.
Further, still include:
the input module is used for acquiring a service number, a service name and a service type;
the format determining module is used for determining that the message format is XML or JSON;
the template acquisition module is used for importing or inputting a message template and storing the message template into a database; the parameter type in the message template corresponds to the back-end interface to be called.
Further, the service number in the input module is a unique identification and cannot be repeated.
Further, the parsing module includes:
the tag analysis module is used for analyzing tags in the message body in the XML format through a jackson library;
the parameter acquisition module is used for acquiring corresponding parameters from the tags and acquiring a back-end interface to be called according to the parameter types;
and the assembling module is used for assembling the plurality of parameters into objects and transmitting the objects into the corresponding rear-end interface.
Further, if the number of the objects in the assembly module is larger than the maximum query times N, the first N objects are transmitted into a rear-end interface; and the back end analyzes the object, obtains fields in the object, queries the fields to generate a single result set, and combines all the single result sets into an XML result set.
Further, the message body in the XML format includes a front-end service request and a third-party service request.
Since the principle of the medical data service system for solving the problems is similar to the medical data service method, the implementation of the medical data service system can refer to the implementation of the method, and details are not repeated here.
The embodiment of the invention also provides a server, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the steps of the medical data service method are realized when the processor executes the computer program.
The embodiment of the invention also provides a computer readable storage medium, wherein a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the steps of the medical data service method are executed.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium, which for purposes of this specification, can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated together. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer readable storage medium.
Finally, it should be noted that: the above-mentioned embodiments are merely specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A medical data service method based on a configurable API (application program interface), which is characterized by comprising the following steps:
constructing a spring framework, wherein the spring framework comprises an administration tool eureka;
specifying within a configuration file the administrative tool eureka instance that needs to be connected, the enabling of discovery and enabling of discovery of other instances in a start-up function within the administrative tool eureka instance;
acquiring a message body in an XML format, wherein the message body comprises at least one tag;
analyzing the at least one label to obtain corresponding parameters;
and calling a back-end interface through the parameters and obtaining an XML result set.
2. The medical data service method based on the configurable API interface as recited in claim 1, wherein the step of obtaining the message body in the XML format further comprises:
acquiring a service number, a service name and a service type;
determining that the message format is XML or JSON;
importing or inputting a message template and storing the message template into a database; the parameter type in the message template corresponds to the back-end interface to be called.
3. The medical data service method based on the configurable API as recited in claim 2, wherein the front-end service number is a unique identification and cannot be repeated.
4. The medical data service method based on the configurable API interface as recited in claim 1, wherein parsing the at least one tag to obtain corresponding parameters comprises:
analyzing the tag in the message body in the XML format through a jackson library;
obtaining corresponding parameters from the label, and obtaining a back-end interface to be called according to the parameter type;
and assembling a plurality of parameters into an object and transmitting the object into a corresponding rear-end interface.
5. The medical data service method based on the configurable API interface as recited in claim 4, wherein if the number of the objects is larger than the maximum number of times of inquiry N, the first N objects are transmitted to the backend interface; and the back end analyzes the object, obtains fields in the object, queries the fields to generate a single result set, and combines all the single result sets into an XML result set.
6. The medical data service method based on the configurable API interface as recited in claim 1, wherein the message body in the XML format comprises a front-end service request and a third-party service request.
7. A medical data service system based on a configurable API interface, comprising:
the spring framework comprises a construction module, a management module and a management module, wherein the construction module is used for constructing a spring framework which comprises a management tool eureka;
a specifying module, configured to specify, in a configuration file, the management tool eureka instance that needs to be connected, where the start function in the management tool eureka instance is allowed to be discovered and other instances are allowed to be discovered;
the message acquisition module is used for acquiring a message body in an XML format, and the message body comprises at least one tag;
the analysis module is used for analyzing the at least one label to obtain a corresponding parameter;
and the result acquisition module is used for calling the back-end interface through the parameters and acquiring an XML result set.
8. The medical data service system based on the configurable API interface as recited in claim 7, further comprising:
the input module is used for acquiring a service number, a service name and a service type;
the format determining module is used for determining that the message format is XML or JSON;
the template acquisition module is used for importing or inputting a message template and storing the message template into a database; the parameter type in the message template corresponds to the back-end interface to be called.
9. The medical data service system based on the configurable API interface as recited in claim 7, wherein the parsing module comprises:
the tag analysis module is used for analyzing tags in the message body in the XML format through a jackson library;
the parameter acquisition module is used for acquiring corresponding parameters from the tags and acquiring a back-end interface to be called according to the parameter types;
and the assembling module is used for assembling the plurality of parameters into objects and transmitting the objects into the corresponding rear-end interface.
10. The medical data service system based on the configurable API interface as recited in claim 7, wherein if the number of the objects in the assembly module is greater than the maximum number of queries N, the first N objects are transmitted to the backend interface; and the back end analyzes the object, obtains fields in the object, queries the fields to generate a single result set, and combines all the single result sets into an XML result set.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011309565.XA CN112434187A (en) | 2020-11-20 | 2020-11-20 | Medical data service method and system based on configurable API (application program interface) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011309565.XA CN112434187A (en) | 2020-11-20 | 2020-11-20 | Medical data service method and system based on configurable API (application program interface) |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112434187A true CN112434187A (en) | 2021-03-02 |
Family
ID=74693075
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011309565.XA Withdrawn CN112434187A (en) | 2020-11-20 | 2020-11-20 | Medical data service method and system based on configurable API (application program interface) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112434187A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113450914A (en) * | 2021-04-20 | 2021-09-28 | 心医国际数字医疗系统(大连)有限公司 | Rule management system and method for early warning of medical emergency value and early warning system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106656953A (en) * | 2016-09-23 | 2017-05-10 | 焦点科技股份有限公司 | Method for realizing safe interface calling between systems based on Internet |
| CN110677427A (en) * | 2019-10-08 | 2020-01-10 | 山东浪潮商用系统有限公司 | Multi-message analysis method |
-
2020
- 2020-11-20 CN CN202011309565.XA patent/CN112434187A/en not_active Withdrawn
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106656953A (en) * | 2016-09-23 | 2017-05-10 | 焦点科技股份有限公司 | Method for realizing safe interface calling between systems based on Internet |
| CN110677427A (en) * | 2019-10-08 | 2020-01-10 | 山东浪潮商用系统有限公司 | Multi-message analysis method |
Non-Patent Citations (1)
| Title |
|---|
| 张开琦等: "基于微服务架构的中医信息服务系统设计与应用", 《电子测量技术》, vol. 43, no. 3, pages 1 - 5 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113450914A (en) * | 2021-04-20 | 2021-09-28 | 心医国际数字医疗系统(大连)有限公司 | Rule management system and method for early warning of medical emergency value and early warning system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9111004B2 (en) | Temporal scope translation of meta-models using semantic web technologies | |
| US9996464B2 (en) | Metadata cache management | |
| US8949311B2 (en) | Dynamic, non-intrusive personalization of web services | |
| US9026412B2 (en) | Managing and maintaining scope in a service oriented architecture industry model repository | |
| RU2648966C2 (en) | Apparatus and method for processing multiple open api | |
| CN109766082B (en) | Method and device for application program page jump | |
| CN107809383B (en) | MVC-based path mapping method and device | |
| WO2011035944A1 (en) | Managing application state information by means of a uniform resource identifier (uri) | |
| KR101107319B1 (en) | Method and System for Providing Web Portal Service based on Open Application Program Interface | |
| US9715545B2 (en) | Continuous collection of web API ecosystem data | |
| US7926065B2 (en) | Method and system for dynamically specifying a format for data provided by a web service invocation | |
| CN103684977B (en) | Method for sending information and device, method for information display and device | |
| CN112434187A (en) | Medical data service method and system based on configurable API (application program interface) | |
| US11593418B2 (en) | System and method for a semantically-driven smart data cache | |
| CN113900907A (en) | Mapping construction method and system | |
| US9690577B1 (en) | Legacy applications as web services | |
| CN111046316B (en) | Application on-shelf state monitoring method, intelligent terminal and storage medium | |
| CN108540439A (en) | Data analysis method and system, equipment and storage medium | |
| CN115022397B (en) | Interface parameter simplifying method and device, electronic equipment and storage medium | |
| CN115080616A (en) | Dictionary data acquisition method and device, storage medium and electronic equipment | |
| US20220367017A1 (en) | Health data management methods, health data management device and background device | |
| KR20040045149A (en) | Registry system and management method for by using uddi web service based on the ebxml registry | |
| US20040210631A1 (en) | Method and apparatus for accessing legacy data in a standardized environment | |
| US20150006690A1 (en) | Feature set negotiation framework | |
| US20090077032A1 (en) | Calm capable of searching agent service through web, agent system using the same and operation method of agent system |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210302 |
|
| WW01 | Invention patent application withdrawn after publication |