CN113764085A - Medical service method and system - Google Patents
Medical service method and system Download PDFInfo
- Publication number
- CN113764085A CN113764085A CN202110469802.7A CN202110469802A CN113764085A CN 113764085 A CN113764085 A CN 113764085A CN 202110469802 A CN202110469802 A CN 202110469802A CN 113764085 A CN113764085 A CN 113764085A
- Authority
- CN
- China
- Prior art keywords
- hospital
- service
- server
- docking
- medical
- 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
- 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
Abstract
The application provides a medical service method and system. The method comprises the following steps: the internal server in the medical service system can acquire the business data sent by the front-end equipment. The business data may include hospital identification and business information. The medical service system generates a docking request according to the hospital identification and the service information, and the docking request is used for requesting service from the internal network of the hospital. The healthcare system sends the docking request to the gateway layer. After determining the hospital identifier in the docking request, the gateway server may send the docking request to the corresponding docking server according to the hospital identifier. The docking server forwards the docking request to the hospital internal system. And the internal system of the hospital realizes corresponding service according to the service data in the docking request. The method of the application enables the resources to be uniformly allocated according to the access conditions of various hospitals, and improves the resource utilization rate.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a medical service method and system.
Background
With the continuous development of the internet, many hospitals in China launch network remote medical services. The network telemedicine service is generally realized based on an internet medical platform. The internet medical platform can realize internet medical services such as telephone inquiry, on-line inquiry, health consultation and the like, and can also realize a third-party hospital admission platform.
At present, on the basis of realizing basic medical treatment, factors such as regional differences and medical level differences exist in all hospitals. Therefore, in order to meet the basic and personalized requirements of each hospital, a medical service system is deployed for each hospital separately, and an internet medical platform of the hospital is established. The user can access each hospital through the front page of the internet platform of the hospital, thereby obtaining the medical service of the hospital.
However, when the number of hospitals accessing the internet medical platform is large, since the access amount of each hospital is different, there is a problem that resource allocation is not reasonable, and resource waste may be caused.
Disclosure of Invention
The application provides a medical service method and system, which are used for solving the problem of resource waste caused by unreasonable resource allocation in the prior art.
In a first aspect, the present application provides a method of medical services, comprising:
acquiring service data, wherein the service data comprises hospital identification and service information;
generating a docking request according to the hospital identification and the service information, wherein the docking request is used for requesting service to an internal network of a hospital;
and sending the docking request according to the hospital identification.
Optionally, the generating a docking request according to the hospital identifier and the service information includes:
determining first service data according to the service information, wherein the first service data is service data generated by basic service;
determining second service data according to the hospital identifier and the service information, wherein the second service data is service data generated by a difference service corresponding to the hospital identifier;
and generating a docking request according to the first service data, the second service data and the hospital identification.
Optionally, the hospital identification uniquely corresponds to one hospital internal network.
In a second aspect, the present application provides a medical services system comprising: an internal server, a gateway server and at least one docking server;
the internal server is connected with the gateway server through a network and used for sending a docking request to the gateway server;
the gateway server is used for sending the docking request to the docking server corresponding to the hospital identifier according to the hospital identifier in the docking request;
the docking servers are used for requesting services from the hospital internal systems, and each docking server only corresponds to one hospital internal system.
Optionally, the internal server comprises a common module and a difference module;
the public module is used for executing basic service and generating first service data;
the difference module is used for executing difference business and generating second business data.
Optionally, the gateway server is further configured to convert a protocol of the docking request from a remote call protocol (RPC) to a hypertext transfer security protocol (HTTPS).
Optionally, the docking server is further configured to convert a protocol of the docking request from a hypertext transfer security protocol HTTPS to internet protocol Web Services.
Optionally, the system further comprises: a front-end device;
the front-end equipment is used for acquiring service data through a display interface, and the service data at least comprises hospital identification and service information.
In a third aspect, the present application provides a readable storage medium, in which execution instructions are stored, and when the computer program is executed by a processor of each server in a medical service system, the electronic device executes the medical service method in any one of the possible designs of the first aspect and the first aspect.
In a fourth aspect, the present application provides a computer program product, where the computer program product includes a computer program, and when the computer program is executed by a processor of each server in a medical service system, an electronic device executes the medical service method in any one of the possible designs of the first aspect and the first aspect.
According to the medical service method and the medical service system, the service data sent by the front-end equipment can be obtained through the internal server, and the service data can comprise hospital identification and service information; generating a docking request according to the hospital identification and the service information, wherein the docking request is used for requesting service to an internal network of the hospital; sending the docking request to a gateway layer; after determining the hospital identifier in the docking request, the gateway server may send the docking request to a corresponding docking server according to the hospital identifier; the docking server forwards the docking request to the hospital internal system; the means that the internal system of the hospital realizes the corresponding service according to the business data in the docking request enables the resources to be uniformly allocated according to the access condition of each hospital, and the effect of improving the resource utilization rate is achieved.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic view of an application scenario of a separately deployed medical service system according to an embodiment of the present application;
fig. 2 is a schematic view of an application scenario of a medical service system according to an embodiment of the present application;
FIG. 3 is a flow chart of a method of medical services provided in accordance with an embodiment of the present application;
fig. 4 is a schematic structural diagram of a medical service system according to an embodiment of the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein.
Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
With the continuous development of the internet, many hospitals in China launch network remote medical services. The internet medical platform can realize internet medical services such as telephone inquiry, on-line inquiry, health consultation and the like, and can also realize a third-party hospital to enter the platform. The use of the Internet medical platform effectively mobilizes the existing medical resources, and is convenient for the masses to seek medical advice. In docking each hospital using the internet medical platform, there are factors due to regional differences, medical level differences, and the like of each hospital. Therefore, at present, in order to meet the basic requirements and personalized requirements of each hospital, a mode of individually deploying a set of medical service systems for each hospital is generally adopted to establish an internet medical platform of the hospital. The medical service system can be a set of system built by a Java back-end server.
Fig. 1 is a schematic diagram of an application scenario of a medical service system deployed separately. As shown, each hospital in the application scenario may include a front-end device, a medical services system, and an in-hospital system. For example, as shown in fig. 1, an online user may implement medical services such as online registration, online inquiry, health consultation and the like through a front-end device of a hospital a. Wherein, the front-end equipment of the A hospital can comprise an interactive interface. The interactive interface can be an APP interface of the hospital A, a PC webpage interface of the hospital A, a public number interface, an applet interface and other front-end interfaces. After the user views the medical service of the hospital A through the front-end page on the front-end equipment, the user can select a needed medical server on the front-end interface. The front-end equipment generates business data according to the medical service selected by the user and sends the business data to the medical service system.
Among them, since the medical service system is a medical service system deployed for the a hospital, the medical service system is typically deployed inside the a hospital. The medical service system may include an internal server and a docking server internally. The internal server comprises a plurality of service modules. The business module in the internal server of each hospital can be determined according to the business of the hospital. For example, as shown, the internal server of hospital a may include a business module 1, a business module 2, a business module 3, a business module 4, and a business module 5. And the internal server of the B hospital may include a service module 1, a service module 2, a service module 4 and a service module 5. Wherein, the business module 3 is used for executing the business of the A hospital, and the B hospital does not have the business. The docking server may include a plurality of docking modules, and each docking module may correspond to one service module. For example, as shown in fig. 1, the service data processed by the service module 2 may be sent to the docking module 2 for processing.
Wherein, the internal system of hospital is the office system used in the hospital. To secure medical data, the hospital-internal system generally uses a local area network. The hospital internal system may include a plurality of server modules, each for implementing a different function. Such as subscription registration, obtaining a check-out report, etc. The docking server may forward the service data to different service modules according to the service required by the service in the service data. For example, as shown in fig. 1, the traffic module 2 may forward the traffic data it receives to the service module 2.
The above medical service system is deployed individually for each hospital. The medical service system deployed in the mode has the advantages of convenience in maintenance, high online speed and the like. For example, when a business module of one hospital needs to be modified, modifying the business module of the hospital alone does not have an impact on other hospitals. For another example, when the internet medical platform needs to be newly accessed to a hospital, the deployment mode can realize the rapid online of the medical service system of the hospital. However, the deployment method also has the problems of high maintenance cost, high equipment cost, unreasonable system resource allocation and the like. For example, with the increase of access hospitals, maintenance personnel need to go to each hospital for maintenance when maintaining the medical service system of the hospital, which increases the distance cost. For another example, each additional hospital needs to be configured separately, which increases the expenditure of hardware devices such as servers, network environments, databases, and the like, and thus has a problem of high device cost. As another example, the number of visits to different hospitals is often different. The network and hardware of the hospital with small access amount have the condition of idle resources. In a hospital with a large visit, the use of resources such as network and hardware is in short supply. Further, problems such as unreasonable resource allocation and resource waste occur.
In order to solve the problems, the application provides a medical service system. The medical service system includes an internal server, a gateway server, and at least one docking server. The medical server maintains a docking server that is configured separately for each hospital. Meanwhile, the medical server combines the internal servers originally deployed in each hospital into one internal server. The internal server may include a common module and a differential module therein. The common module is a business module included in each hospital, such as a business module 1, a business module 2, a business module 4, and a business module 5 shown in fig. 1. The difference module is a service module included in a part of hospitals, for example, the service module 3 shown in fig. 1. The medical server is also added with a network server. The network server can forward different service information to different docking servers according to the hospital identification. The medical service system is used, so that the internal server is not required to belong to each hospital, and the hardware cost for distributing the medical server is greatly reduced. Meanwhile, the service modules of all hospitals are arranged in one internal server, so that the maintenance cost of the internal server can be effectively reduced. When the business module in the internal server needs to be updated, the administrator does not have to go to each hospital for updating or remotely direct to achieve updating of the internal server of each hospital. In addition, because the business data of each hospital are forwarded through the internal server, the resources in the internal server can be effectively utilized, the phenomenon that some hospitals are idle due to less access to the resources is avoided, and the problem of resource shortage caused by excessive access amount of some hospitals is also avoided.
The technical solution of the present application will be described in detail below with specific examples. These particular embodiments may be combined with each other below, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 2 is a schematic view illustrating a scenario of a medical service system according to an embodiment of the present application. As shown in the figure, the medical service system of the present application can acquire the business data uploaded by the front-end device. Wherein different hospitals may have different front-end devices, among other things. For example, when a user needs to request service at hospital a, the user may open the a hospital front-end device and implement interaction through its interaction page. Alternatively, different hospitals may have the same head end equipment. For example, a user may select different medical and different services from an APP of an online medical platform after logging into it.
The front-end equipment is connected with an internal server of the medical service system. Since only one internal service system is included in the medical service system. Therefore, whether different hospitals have different head end equipment or different hospitals use the same head end equipment, the service data of the hospitals are uploaded to the internal server. The internal server sets up various business modules according to the requirements of each hospital. The service module may include a common module and a difference module. For example, as shown in fig. 2, the service module 1, the service module 2, the service module 4, and the service module 5 are common modules, and the service module 3 is a difference module. And after receiving the service data uploaded by the front-end equipment, the internal server processes the service data by using the corresponding service module. And the internal server generates a docking request according to the processed service data. The internal server sends the docking request to the gateway layer. As shown in fig. 2, the solid line connection between the internal server and the network management server is the transmission process of the online user requesting the service data of the hospital a, and the dotted line connection between the internal server and the network management server is the transmission process of the online user requesting the service data of the hospital B.
And after receiving the docking request sent by the internal server, the gateway server forwards the request to the corresponding docking server. Wherein one gateway server may correspond to a plurality of docking servers. Each docking server uniquely corresponds to a hospital internal system of a hospital. Since the hospital-internal systems usually work using an internal local area network, and the hospital-internal systems of different hospitals usually have different use environments. Therefore, one docking server is provided for each hospital-internal system. The docking server can be arranged one-to-one according to the internal system of the hospital so as to ensure that the docking request forwarded by the gateway server can be accurately sent to the internal system of the hospital.
Fig. 3 shows a flowchart of a medical service method provided by an embodiment of the present application. On the basis of the embodiment shown in fig. 2, as shown in fig. 3, with the medical service system as the executing subject, the method of the embodiment may include the following steps:
s101, acquiring service data, wherein the service data comprises hospital identification and service information.
In this embodiment, the internal server in the medical service system may obtain the service data sent by the front-end device. The business data may include hospital identification and business information. The hospital identification in the service data is used to indicate which hospital's service the user needs to request. Wherein, the service information is used for indicating the service content required to be requested. For example, when a user needs to request filing at hospital a, the hospital in the service data is identified as hospital a, and the service information includes user information and a filing instruction.
In one example, the hospital identification uniquely corresponds to one hospital internal network.
And S102, generating a docking request according to the hospital identification and the service information, wherein the docking request is used for requesting service to an internal network of the hospital.
In this embodiment, after the internal server in the medical service system acquires the service data, the internal server determines a service module for executing the service data according to the hospital identifier in the service data. For the same service data, different hospital identifications can correspond to different service modules. For example, the filing of hospital a only supports card filing, and the service module used by it may be service module 4. The service module 4 can be used for binding the user information according to the visiting card number of the user. The filing of the B hospital can also support the filing without the card. The service modules used by it may also include a service module 3. The service module 3 is used for judging whether the user transacts the treatment card or not according to the user information. If the user has transacted the treatment card, the service module 3 can directly jump to the service module 4 to bind the user information and the treatment card corresponding to the user information. If the user has not dealt with the treatment card, the service module 3 may assign the treatment card to the user and then jump to the service module 4. After the service data is processed, the internal server may generate a docking request according to the processed service data. The internal server sends the docking request to the gateway server.
In one example, the internal server generating the docking request may include:
In this step, the internal server determines the common module corresponding to the service data according to the service information. The internal server uses the public module to process the service data to obtain first service data. For example, when the service information indicates profiling, the internal server acquires the visiting card information and the user information of the user from the service data.
And 2, determining second service data according to the hospital identification and the service information, wherein the second service data is service data generated by the difference service corresponding to the hospital identification.
In this step, different hospitals may have different service modules for the same service information. And the internal server determines the difference module which needs to be executed when the hospital executes the business information according to the hospital identification and the business information. The internal server uses the difference module to process the service data to obtain second service data. For example, when the service information indicates profiling, the internal server may also assign a new treatment card to the user, thereby obtaining treatment card information.
The step 1 and the step 2 are not limited by the described action sequence, and the step 1 and the step 2 may include one or more service modules respectively, and the execution sequence of the service modules in the step 1 and the step 2 is determined according to actual needs and is not limited by the described action sequence.
And 3, generating a docking request according to the first service data, the second service data and the hospital identification.
In this step, after generating the first service data and the second service data, the internal server generates a docking request together with the first service data, the second service data and the hospital identifier. The docking request is for transmission to the hospital internal system via the gateway server and the docking server. The hospital internal system can execute corresponding service according to the docking request.
And S103, sending a docking request according to the hospital identification.
In this embodiment, after the internal server in the medical service system generates the docking request, the internal server transmits the docking request to the gateway server. And the gateway server acquires the docking request and analyzes the hospital identifier in the docking request. The internal server and the gateway server are both deployed in the management background. Therefore, the internal server and the gateway server can realize the transmission of internal data through the internal network. The internal data is the docking request. The transmission Protocol of the internal data may be a Remote Call Protocol (RPC) Protocol.
After determining the hospital identifier in the docking request, the gateway server may send the docking request to the corresponding docking server according to the hospital identifier. Since the intra-hospital system generally uses an internal network, the docking server is generally deployed inside the hospital in order to ensure communication with the intra-hospital system. Therefore, the gateway server realizes the transmission of the docking request through the external network. The transmission Protocol of the docking request may be a hypertext Transfer Protocol over secure Layer (HTTPS) Protocol. After obtaining the docking request, the gateway server may convert the docking request of the RPC protocol into an HTTPS protocol, so as to output the docking request.
After receiving the docking request, the docking server may convert the docking request from the HTTPS protocol to the Web Services protocol, so that the docking server may forward the docking request to the hospital internal system. After receiving the docking request, the internal system of the hospital realizes corresponding service according to the service data in the docking request. For example, when the service data in the docking request includes profiling, the hospital-internal server may establish a profile of the user in the hospital-internal system after acquiring the user information and the visit card information. The profile includes user information of the user and information of his visiting card. And further, the binding of the user information and the information of the visiting card is realized.
In one example, the docking server may be located in the management back-end when the hospital internal system can connect directly with the external system. In the management background, the docking server uniquely corresponds to one hospital internal system.
According to the medical service method, the internal server in the medical service system can acquire the business data sent by the front-end equipment. The business data may include hospital identification and business information. The medical service system generates a docking request according to the hospital identification and the service information, and the docking request is used for requesting service from the internal network of the hospital. The healthcare system sends the docking request to the gateway layer. After determining the hospital identifier in the docking request, the gateway server may send the docking request to the corresponding docking server according to the hospital identifier. The docking server forwards the docking request to the hospital internal system. And the internal system of the hospital realizes corresponding service according to the service data in the docking request. In the application, the internal servers which need to be deployed to all hospitals are uniformly placed in the background server by using the internal server and the gateway server, so that resources can be uniformly allocated according to the access conditions of all hospitals, and the resource utilization rate is improved. Meanwhile, the use of the internal server greatly reduces the hardware cost for laying out the medical server and the maintenance cost of the internal server.
Fig. 4 shows a schematic structural diagram of a medical service system provided by an embodiment of the present application. As shown in fig. 4, the medical service system 10 of the present embodiment may include: an internal server 11, a gateway server 12 and at least one docking server 13.
The internal server 11 is connected to the gateway server 12 via a network, and is configured to send a docking request to the gateway server 12. The internal server 11 may include a plurality of service modules therein. The service module may be a common module or a differential module. The public module is a business module which is needed to be used by each hospital. Wherein, the difference module is a business module which needs to be used by part of hospitals. Some of the hospitals may be one or more hospitals.
After receiving the service data sent by the front-end device, the internal server 11 determines a corresponding service module according to the hospital identifier. The internal server 11 will process the business data using the property module. The internal server 11 generates a docking request using the processed service data. The internal server 11 sends the corresponding request to the gateway server 12.
Since the internal server 11 and the gateway server 12 are both arranged in the management background. Therefore, the RPC protocol is used for data transmission between the internal server 11 and the gateway server 12.
The gateway server 12 is configured to send a docking request to the docking server 13 corresponding to the hospital identifier according to the hospital identifier in the docking request. The gateway server 12 may parse the docking request for the different hospital identifications. Different hospital identities may correspond to different docking servers 13. Each hospital identification uniquely corresponds to one docking server 13. The gateway server 12 may forward the docking request into its corresponding docking server 13.
Wherein the docking server 13 is typically located in a hospital. Therefore, data transmission between the gateway server 12 and the docking server 13 typically uses the HTTPS protocol. When the gateway server 12 receives the docking request of the RPC protocol. The gateway server 12, in addition to determining its corresponding docking server 13 according to the hospital identifier, may also be configured to convert the protocol of the docking request from the RPC protocol to the HTTPS protocol.
The docking servers 13 are used to request services from the hospital internal systems, each docking server 13 uniquely corresponding to one hospital internal system. To secure medical data, inter alia, hospital internal systems typically use an internal network to enable communication. Therefore, in order to achieve data interaction with the hospital-internal system, the docking server 13 of the hospital is generally provided in the hospital. Also, each docking server 13 typically corresponds uniquely to one hospital's internal system. That is, each docking server 13 uniquely corresponds to a hospital identification. When the docking server 13 receives the docking request sent by the gateway server 12, the docking server 13 may forward the docking request to the in-hospital system.
And the internal system of the hospital executes corresponding service according to the corresponding request. The hospital internal system may also feed back the execution result to the docking server 13 after the execution of the service is completed. The docking server 13 forwards the execution result to the internal server 11 through the web server. When the service module in the internal server 11 needs the execution result as input data, the service module may continue to perform subsequent operations after obtaining the execution result.
The protocol of the docking request received by the docking server 13 is an HTTPS protocol. In order to ensure that the hospital internal system can receive the docking request of the Web Services protocol, the docking server 13 may also be used to convert the protocol of the docking request from the HTTPS protocol to the Web Services protocol.
In one example, the medical service system 10 may further include: the head-end equipment 14.
The front-end equipment comprises an interactive interface. The user can input hospital information, service information and user information through the interactive interface. The interactive interface can be an APP interface, a webpage interface, an applet interface, a public interface and the like. Wherein, each hospital can correspond to an APP, a webpage or an applet. When a user enters the interactive interface of the hospital to generate business data, the interactive interface determines the corresponding hospital identifier according to the corresponding hospital. Alternatively, each hospital participating in the internet medical platform may share an APP, web page, or applet. After the user enters the interactive page, the hospital identification can be acquired by selecting the target hospital.
The medical service system 10 provided in the embodiment of the present application may implement the above method embodiment, and for details of the implementation principle and the technical effect, reference may be made to the above method embodiment, which is not described herein again.
The present application also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is used for implementing the methods provided by the above-mentioned various embodiments when being executed by a processor.
The computer-readable storage medium may be a computer storage medium or a communication medium. Communication media includes any medium that facilitates transfer of a computer program from one place to another. Computer storage media can be any available media that can be accessed by a general purpose or special purpose computer. For example, a computer readable storage medium is coupled to the processor such that the processor can read information from, and write information to, the computer readable storage medium. Of course, a computer readable storage medium may also be integral to the processor. The processor and the computer-readable storage medium may reside in an Application Specific Integrated Circuit (ASIC). Additionally, the ASIC may reside in user equipment. Of course, the processor and the computer-readable storage medium may also reside as discrete components in a communication device.
In particular, the computer-readable storage medium may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random-Access Memory (SRAM), Electrically-Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
The present application also provides a computer program product comprising a computer program stored in a computer readable storage medium. The computer program may be read from a computer-readable storage medium by at least one processor of the apparatus, and execution of the computer program by the at least one processor causes the apparatus to perform the methods provided by the various embodiments described above.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Wherein the modules may be physically separated, e.g. mounted at different locations on one device, or mounted on different devices, or distributed over multiple network elements, or distributed over multiple processors. The modules may also be integrated, for example, in the same device, or in a set of codes. The respective modules may exist in the form of hardware, or may also exist in the form of software, or may also be implemented in the form of software plus hardware. The method and the device can select part or all of the modules according to actual needs to achieve the purpose of the scheme of the embodiment.
When the respective modules are implemented as integrated modules in the form of software functional modules, they may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor to execute some steps of the methods according to the embodiments of the present application.
It should be understood that, although the respective steps in the flowcharts in the above-described embodiments are sequentially shown as indicated by arrows, the steps are not necessarily sequentially executed in the order indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or sub-steps of other steps.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: it is also possible to modify the solutions described in the previous embodiments or to substitute some or all of them with equivalents. And the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A medical service method is applied to a medical service system, and the method comprises the following steps:
acquiring service data, wherein the service data comprises hospital identification and service information;
generating a docking request according to the hospital identification and the service information, wherein the docking request is used for requesting service to an internal network of a hospital;
and sending the docking request according to the hospital identification.
2. The method of claim 1, wherein generating a docking request based on the hospital identification and the business information comprises:
determining first service data according to the service information, wherein the first service data is service data generated by basic service;
determining second service data according to the hospital identifier and the service information, wherein the second service data is service data generated by a difference service corresponding to the hospital identifier;
and generating a docking request according to the first service data, the second service data and the hospital identification.
3. The method of claim 1, wherein the hospital identification uniquely corresponds to a hospital internal network.
4. A medical services system, the system comprising: an internal server, a gateway server and at least one docking server;
the internal server is connected with the gateway server through a network and used for sending a docking request to the gateway server;
the gateway server is used for sending the docking request to the docking server corresponding to the hospital identifier according to the hospital identifier in the docking request;
the docking servers are used for requesting services from the hospital internal systems, and each docking server uniquely corresponds to one hospital internal system.
5. The medical services system of claim 4, wherein the internal server comprises a common module and a difference module;
the public module is used for executing basic service and generating first service data;
the difference module is used for executing difference business and generating second business data.
6. The healthcare system according to claim 4 or 5, wherein the gateway server is further configured to convert the protocol of the docking request from a remote call protocol (RPC) to a hypertext transfer security protocol (HTTPS).
7. The healthcare system according to claim 4 or 5, wherein the docking server is further configured to convert a protocol of the docking request from hypertext transfer secure protocol (HTTPS) to Internet protocol (Web Services).
8. The medical service system according to claim 4 or 5, wherein the system further comprises: a front-end device;
the front-end equipment is used for acquiring service data through a display interface, and the service data at least comprises hospital identification and service information.
9. A computer-readable storage medium, which is applied to a medical service system, and which stores therein a computer program, which when executed by a processor of each server in the medical service system, is used to implement the medical service method according to any one of claims 1 to 3 by the medical service system according to any one of claims 4 to 8.
10. A computer program product for a medical service system, the computer program product comprising a computer program, wherein the computer program, when executed by a processor of a respective server in the medical service system, is adapted to implement the medical service method according to any of claims 1-3 by means of the medical service system according to any of claims 4-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469802.7A CN113764085A (en) | 2021-04-28 | 2021-04-28 | Medical service method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469802.7A CN113764085A (en) | 2021-04-28 | 2021-04-28 | Medical service method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113764085A true CN113764085A (en) | 2021-12-07 |
Family
ID=78786945
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110469802.7A Pending CN113764085A (en) | 2021-04-28 | 2021-04-28 | Medical service method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113764085A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030088441A1 (en) * | 2001-11-08 | 2003-05-08 | Mcnerney Michelle | System for the integrated management of healthcare information |
| CN105205766A (en) * | 2015-08-19 | 2015-12-30 | 四川佳缘电子科技有限公司 | Mobile Internet hospital attendance system based on cloud platform |
| CN108256068A (en) * | 2018-01-16 | 2018-07-06 | 平安医疗健康管理股份有限公司 | Medical institutions' intelligent access system with two-way calling function |
| CN110223207A (en) * | 2019-06-18 | 2019-09-10 | 湖南晖龙集团股份有限公司 | Health service method, electronic equipment and computer readable storage medium on a kind of line Internet-based |
| CN113760386A (en) * | 2021-01-29 | 2021-12-07 | 北京京东拓先科技有限公司 | Access control system, access control method and storage medium |
-
2021
- 2021-04-28 CN CN202110469802.7A patent/CN113764085A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030088441A1 (en) * | 2001-11-08 | 2003-05-08 | Mcnerney Michelle | System for the integrated management of healthcare information |
| CN105205766A (en) * | 2015-08-19 | 2015-12-30 | 四川佳缘电子科技有限公司 | Mobile Internet hospital attendance system based on cloud platform |
| CN108256068A (en) * | 2018-01-16 | 2018-07-06 | 平安医疗健康管理股份有限公司 | Medical institutions' intelligent access system with two-way calling function |
| CN110223207A (en) * | 2019-06-18 | 2019-09-10 | 湖南晖龙集团股份有限公司 | Health service method, electronic equipment and computer readable storage medium on a kind of line Internet-based |
| CN113760386A (en) * | 2021-01-29 | 2021-12-07 | 北京京东拓先科技有限公司 | Access control system, access control method and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9563613B1 (en) | System and method for dynamic portable document file generation | |
| US8250215B2 (en) | Method and system for intelligently leveraging cloud computing resources | |
| US8504400B2 (en) | Dynamically optimized distributed cloud computing-based business process management (BPM) system | |
| CN102202078B (en) | The method and system of a kind of multiple foreign peoples roles for configuration server field | |
| CN103765423B (en) | Gathering transaction data associated with locally stored data files | |
| US20190132222A1 (en) | Apparatus for providing cloud service based on cloud service brokerage and method thereof | |
| US8838738B2 (en) | System and method for processing medical information through medical terminal | |
| CN104246741A (en) | Orchestrating hybrid cloud services | |
| CN103765858B (en) | For period that browses in communication network monitoring the method for user and server user | |
| US9529578B2 (en) | Automated service version upgrading | |
| US10834220B2 (en) | Apparatus for providing cloud brokerage service based on multiple clouds and method thereof | |
| JP6440571B2 (en) | SaaS data linkage support system and SaaS data linkage support method | |
| CN113094136A (en) | Page display control method and device, storage medium and electronic equipment | |
| CN106096926B (en) | Event processing method, device, electronic device and storage medium | |
| KR20150032151A (en) | Apparatus and method for process based collaboration in web of things | |
| CN104780202A (en) | End-to-end cloud service database virtualization and management framework and method | |
| CN113568970A (en) | Application service data management method, device, equipment and storage medium | |
| CN101901421A (en) | Service provider management device, service provider management program, and service provider management method | |
| CN103618758B (en) | Web server and system resource access control method thereof | |
| CN114466005A (en) | Internet of things equipment arrangement | |
| US20200210148A1 (en) | Method for adapting to blockchain and device, terminal and medium performing the same | |
| US10958445B1 (en) | Attribution of network events pursuant to configuring mobile communication devices | |
| CN113764085A (en) | Medical service method and system | |
| Brasileiro et al. | Flexible federation of cloud providers: The EUBrazil cloud connect approach | |
| US20140279990A1 (en) | Managing identifiers |
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 |