CN112306585A - Medical insurance interface data processing method, data processing device and readable storage medium - Google Patents

Medical insurance interface data processing method, data processing device and readable storage medium Download PDF

Info

Publication number
CN112306585A
CN112306585A CN202011201648.7A CN202011201648A CN112306585A CN 112306585 A CN112306585 A CN 112306585A CN 202011201648 A CN202011201648 A CN 202011201648A CN 112306585 A CN112306585 A CN 112306585A
Authority
CN
China
Prior art keywords
medical insurance
data processing
service
format
processing method
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
Application number
CN202011201648.7A
Other languages
Chinese (zh)
Inventor
赵西沛
韩红强
宋德彬
张磊磊
王亚东
薛英雷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yonyou Network Technology Co Ltd
Original Assignee
Yonyou Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Yonyou Network Technology Co Ltd filed Critical Yonyou Network Technology Co Ltd
Priority to CN202011201648.7A priority Critical patent/CN112306585A/en
Publication of CN112306585A publication Critical patent/CN112306585A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/448Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482Procedural
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/258Data format conversion from or to a database
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/602Providing cryptographic facilities or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245Protecting personal data, e.g. for financial or medical purposes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT 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/40ICT 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 of medical equipment or devices, e.g. scheduling maintenance or upgrades
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2107File encryption

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Bioethics (AREA)
  • General Business, Economics & Management (AREA)
  • Biomedical Technology (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Medical Informatics (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Public Health (AREA)
  • Primary Health Care (AREA)
  • Epidemiology (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Data Mining & Analysis (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

The invention provides a medical insurance interface data processing method, a data processing device and a readable storage medium. The medical insurance interface data processing method comprises the following steps: constructing an entity object of the target service according to the attribute information of the target service; calling a medical insurance interface based on a preset medical insurance entry function; and according to the medical insurance document information corresponding to the medical insurance interface, carrying out data processing on the entity object to obtain the service message in the corresponding format. The medical insurance interface data processing method provided by the invention standardizes the process of medical insurance interface development, enables the customer to realize the medical insurance development according to the development technical guide and the steps, focuses the focus of the medical insurance development from the process development to the data layer processing, realizes the low coupling of the medical insurance interface and the HIS system, and improves the reusability of the HIS product.

Description

Medical insurance interface data processing method, data processing device and readable storage medium
Technical Field
The invention relates to the technical field of medical treatment, in particular to a medical insurance interface data processing method, a medical insurance interface data processing device and a computer readable storage medium.
Background
The development of the medical insurance interface is an extremely important part of a hospital Information system his (hospital Information system), and in a certain sense, the implementation quality of the medical insurance interface directly influences the overall progress and effect of a project, but due to the complexity and variability of medical insurance policies and the fact that medical insurance policies in different regions often have great regional differences, in the process of project delivery, software design and development often encounter many problems which are complex or difficult to solve.
In addition, policy modification procedures are often encountered in the implementation of the process. This adds considerable difficulty to software design and implementation to some extent. Meanwhile, uncertainty in the design of medical insurance interface software can be caused, and a lot of repeated labor can be caused as a direct result.
Most of the traditional HIS interface development is based on customer development on a project site, because projects have requirements of construction periods, customers often lack perfect top-level design and method when developing interfaces, codes with poor expansibility, low maintainability and high service intrusion are written out by adopting stack development, and once the codes are changed into a project, the project basically faces the dilemma of redevelopment, and the reusability is poor.
Disclosure of Invention
The present invention is directed to solving at least one of the problems of the prior art or the related art.
Therefore, one aspect of the invention is to provide a medical insurance interface data processing method.
Another aspect of the present invention is to provide a medical insurance interface data processing apparatus.
Yet another aspect of the present invention is directed to a readable storage medium.
In view of this, according to an aspect of the present invention, a method for processing medical insurance interface data is provided, including: constructing an entity object of the target service according to the attribute information of the target service; calling a medical insurance interface based on a preset medical insurance entry function; and according to the medical insurance document information corresponding to the medical insurance interface, carrying out data processing on the entity object to obtain the service message in the corresponding format.
The medical insurance interface data processing method provided by the invention firstly extracts the attribute information of the target service, and constructs the entity object of the target service based on the attribute information, thereby unifying the processing mode of transaction parameters. Secondly, by presetting a standardized medical insurance entry function and embedding the standardized medical insurance entry function into the HIS end, the HIS end service and the medical insurance end service are isolated, the medical insurance processing process is not directly embedded into the HIS end service, and the standardized medical insurance entry function is only embedded into a service trigger point where the service occurs. Therefore, the HIS end service and the medical insurance end service can be decoupled, the completeness of the HIS main program of each hospital can be met, and the HIS main program can be flexibly expanded to carry out customized development. Meanwhile, the position, the function name and the step of calling the medical insurance processing at the HIS end are clarified and normalized as much as possible by utilizing the commonality and shielding individuality, and unnecessary repeated labor and maintenance of different programs are avoided. And then, according to the medical insurance document information corresponding to the medical insurance interface, performing data processing on the entity object, thereby obtaining the service message in the format required by the medical insurance interface. Therefore, the method can support the transmission of various parameter types, realize the automatic analysis, automatic formatting and standardized processing of the parameters and greatly reduce the redundant code quantity. The medical insurance interface data processing method provided by the invention standardizes the process of medical insurance interface development, enables the customer to realize the medical insurance development according to the development technical guide and the steps, focuses the focus of the medical insurance development from the process development to the data layer processing, realizes the low coupling of the medical insurance interface and the HIS system, and improves the reusability of the HIS product.
The medical insurance interface data processing method provided by the invention can also have the following technical characteristics:
in the above technical solution, the step of performing data processing on the entity object according to the medical insurance document information corresponding to the medical insurance interface to obtain the service packet in the corresponding format specifically includes: according to the medical insurance document information, the entity object is converted into a first service message in a corresponding format; encrypting the first service message based on the condition that the first service message needs to be encrypted to obtain a second service message and sending the second service message to a medical insurance interface; and directly sending the first service message to the medical insurance interface under the condition that the first service message does not need to be encrypted.
In the technical scheme, a method for processing the entity object according to the medical insurance document information corresponding to the medical insurance interface to obtain the service message in the corresponding format is limited. Specifically, firstly, according to the medical insurance document information, the entity object of the target service is converted into a first service message in a format required by the medical insurance interface. And then, judging whether the first service message needs to be encrypted, if so, encrypting the first service message to obtain a second service message, and outputting the second service message to a medical insurance interface. And if the first service message does not need to be encrypted, directly outputting the first service message to the medical insurance interface. By the technical scheme of the invention, the low coupling of the medical insurance interface and the HIS system is realized, and the transaction safety is improved.
In any of the above technical solutions, the entity object includes a tag, and any one of the following items or a combination thereof: patient name, sex, medical insurance information, location of visit, project of visit, unit price, total cost.
In the technical scheme, the entity object comprises a label, and any one or a combination of the name, the gender and the medical insurance information of the patient, the location of the patient, the treatment item, the unit price and the total cost, wherein the label can be the label of the entity object or the label of any field in the entity object. By abstracting the business data into the entity object and setting the tag, on one hand, the processing mode of the parameter can be normalized, so that the redundant code amount is reduced, and on the other hand, annotation information can be added to the entity object, such as information of encryption and the like, so that the safety of the transaction process is ensured.
In any of the above technical solutions, the step of converting the entity object of the target service into the first service packet in the corresponding format according to the medical insurance document information specifically includes: under the condition that the corresponding format is the first preset format, converting the entity object of the target service into the target object of the first preset format, and generating a first service message according to the target object; and generating a first service message according to the entity object of the target service under the condition that the corresponding format is a second preset format.
In the technical scheme, a method for converting the entity object of the target service into the first service message in the corresponding format according to the medical insurance document information is limited. Specifically, if the format required by the medical insurance interface is a first preset format, and the first preset format is an XML format or a JSON format, the entity object of the target service is converted into an expression mode of XML or JSON, and the target object of the expression mode is reflected to generate the first service message. And if the format required by the medical insurance interface is a second preset format which is a self-defined format and comprises self-defined information such as a separator '|', reflecting the entity object of the target service to generate a first service message. By the technical scheme, the parameter can be automatically analyzed, automatically formatted and processed in a standardized way, research and development personnel or implementers can be helped to better implement medical insurance, and the development and delivery efficiency is improved.
In any of the above technical solutions, the first preset format is an XML format or a JSON format; the second preset format is a custom format.
In the technical scheme, the first preset format is an XML format or a JSON format, but is not limited thereto; the second preset format is a custom format.
In any of the above technical solutions, the method for processing medical insurance interface data further includes: and encrypting the first service message based on the condition that the label is the preset information.
In the technical scheme, whether the first service message is encrypted is judged through the label, and when the label is the preset information, the first service message needs to be encrypted.
In any of the above technical solutions, the method for processing medical insurance interface data further includes: and receiving a result message fed back by the medical insurance interface, and performing data reverse processing on the result message so as to convert the result message into a result entity of the target service.
In the technical scheme, the result message fed back by the medical insurance interface is received, and data reverse processing is performed on the result message, specifically, decryption processing and encoding processing are included, so that the result message is converted into a result body of the target service and is returned to the HIS. By the technical scheme of the invention, the bidirectional data format conversion of the HIS end service and the medical insurance end service is realized, so that the medical insurance interface development process is better normalized, and the low coupling of the medical insurance interface and the HIS system is realized.
In any of the above technical solutions, the preset medical insurance entry function includes a medical insurance initialization function, a medical insurance card reading function, and an in-patient service function or an out-patient service function.
In the technical scheme, the preset medical insurance entrance function comprises a medical insurance initialization function, a medical insurance card reading function, an inpatient service function related to the core service of the institution, and an outpatient service function related to the core service of the outpatient service. Moreover, the position, the function name and the step of calling the medical insurance processing at the HIS end are clarified and normalized as much as possible by utilizing the commonality and shielding individuality, and unnecessary repeated labor and maintenance of different programs are avoided.
According to another aspect of the present invention, there is provided a software dependency analysis apparatus, including: a memory storing a program; and the processor is used for realizing the medical insurance interface data processing method according to any one of the technical schemes when executing the program.
According to the software dependency relationship analysis device provided by the invention, the steps of the medical insurance interface data processing method according to any one of the above technical schemes are realized when the processor executes the program, so that the software dependency relationship analysis device has all the beneficial effects of the medical insurance interface data processing method according to any one of the above technical schemes.
According to still another aspect of the present invention, a readable storage medium is provided, on which a program is stored, and the program, when executed by a processor, implements the medical insurance interface data processing method according to any one of the above technical solutions.
According to the readable storage medium provided by the invention, when the program is executed by the processor, the steps of the medical insurance interface data processing method according to any one of the above technical schemes are realized, so that the readable storage medium has all the beneficial effects of the medical insurance interface data processing method according to any one of the above technical schemes.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The above and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flow chart of a medical insurance interface data processing method according to a first embodiment of the invention;
FIG. 2 is a flow chart illustrating a medical insurance interface data processing method according to a second embodiment of the present invention;
FIG. 3 is a flow chart of a medical insurance interface data processing method according to a third embodiment of the invention;
FIG. 4 is a flow chart of a medical insurance interface data processing method according to a fourth embodiment of the invention;
FIG. 5 is a flow chart of a medical insurance interface data processing method according to a fifth embodiment of the invention;
fig. 6 shows an interaction diagram of the HIS side and the medical insurance side of the medical insurance interface data processing method according to the sixth embodiment of the present invention;
fig. 7 shows a schematic block diagram of a medical insurance interface data processing apparatus of an embodiment of the present invention.
Detailed Description
In order that the above objects, features and advantages of the present invention can be more clearly understood, a more particular description of the invention will be rendered by reference to the appended drawings. It should be noted that the embodiments of the present invention and features of the embodiments may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, however, the present invention may be practiced in other ways than those specifically described herein, and therefore the scope of the present invention is not limited to the specific embodiments disclosed below.
According to an embodiment of an aspect of the present invention, a medical insurance interface data processing method is provided, which is described in detail by the following embodiment.
First embodiment, fig. 1 is a flowchart illustrating a medical insurance interface data processing method according to a first embodiment of the present invention. The medical insurance interface data processing method comprises the following steps:
102, constructing an entity object of the target service according to the attribute information of the target service;
step 104, calling a medical insurance interface based on a preset medical insurance entry function;
and step 106, performing data processing on the entity object according to the medical insurance document information corresponding to the medical insurance interface to obtain the service message in the corresponding format.
According to the medical insurance interface data processing method provided by the embodiment of the invention, firstly, the attribute information of the target service is extracted, and the entity object of the target service is constructed based on the attribute information, so that the processing mode of the transaction parameters is unified. Secondly, by presetting a standardized medical insurance entry function and embedding the standardized medical insurance entry function into the HIS end, the HIS end service and the medical insurance end service are isolated, the medical insurance processing process is not directly embedded into the HIS end service, and the standardized medical insurance entry function is only embedded into a service trigger point where the service occurs. Therefore, the HIS end service and the medical insurance end service can be decoupled, the completeness of the HIS main program of each hospital can be met, and the HIS main program can be flexibly expanded to carry out customized development. Meanwhile, the position, the function name and the step of calling the medical insurance processing at the HIS end are clarified and normalized as much as possible by utilizing the commonality and shielding individuality, and unnecessary repeated labor and maintenance of different programs are avoided. And then, according to the medical insurance document information corresponding to the medical insurance interface, performing data processing on the entity object, thereby obtaining the service message in the format required by the medical insurance interface. Therefore, the method can support the transmission of various parameter types, realize the automatic analysis, automatic formatting and standardized processing of the parameters and greatly reduce the redundant code quantity. The medical insurance interface data processing method provided by the invention standardizes the process of medical insurance interface development, enables the customer to realize the medical insurance development according to the development technical guide and the steps, focuses the focus of the medical insurance development from the process development to the data layer processing, realizes the low coupling of the medical insurance interface and the HIS system, and improves the reusability of the HIS product.
Second embodiment, fig. 2 is a flowchart illustrating a medical insurance interface data processing method according to a second embodiment of the present invention. The medical insurance interface data processing method comprises the following steps:
step 202, constructing an entity object of the target service according to the attribute information of the target service;
step 204, calling a medical insurance interface based on a preset medical insurance entry function;
step 206, converting the entity object into a first service message in a corresponding format according to the medical insurance document information corresponding to the medical insurance interface;
in step 208, is the first service packet encrypted? If yes, go to step 210, if no, go to step 212;
step 210, encrypting the first service message to obtain a second service message and sending the second service message to a medical insurance interface;
and step 212, directly sending the first service message to a medical insurance interface.
In this embodiment, a method for performing data processing on the entity object according to the medical insurance document information corresponding to the medical insurance interface to obtain the service packet in the corresponding format is limited. Specifically, firstly, according to the medical insurance document information, the entity object of the target service is converted into a first service message in a format required by the medical insurance interface. And then, judging whether the first service message needs to be encrypted, if so, encrypting the first service message to obtain a second service message, and outputting the second service message to a medical insurance interface. And if the first service message does not need to be encrypted, directly outputting the first service message to the medical insurance interface. Through the embodiment of the invention, the low coupling of the medical insurance interface and the HIS system is realized, and the transaction safety is improved.
Third embodiment, fig. 3 is a flowchart illustrating a medical insurance interface data processing method according to a third embodiment of the present invention. The medical insurance interface data processing method comprises the following steps:
step 302, constructing an entity object of the target service according to the attribute information of the target service;
step 304, calling a medical insurance interface based on a preset medical insurance entry function;
step 306, determining a corresponding format according to the medical insurance document information corresponding to the medical insurance interface;
step 308, converting the entity object of the target service into a target object in a first preset format based on the condition that the corresponding format is the first preset format, and generating a first service message according to the target object; generating a first service message according to the entity object of the target service under the condition that the corresponding format is a second preset format;
in step 310, is the first service packet encrypted? If yes, go to step 312, otherwise go to step 314;
step 312, encrypting the first service message to obtain a second service message and sending the second service message to the medical insurance interface;
and step 314, directly sending the first service message to the medical insurance interface.
In this embodiment, a method for converting an entity object of a target service into a first service packet in a corresponding format according to medical insurance document information is defined. Specifically, if the format required by the medical insurance interface is a first preset format, and the first preset format is an XML format or a JSON format, the entity object of the target service is converted into an expression mode of XML or JSON, and the target object of the expression mode is reflected to generate the first service message. And if the format required by the medical insurance interface is a second preset format which is a self-defined format and comprises self-defined information such as a separator '|', reflecting the entity object of the target service to generate a first service message. The embodiment of the invention can realize automatic parameter analysis, automatic formatting and standardized processing, can help research and development personnel or implementers to better implement medical insurance, and improves the development and delivery efficiency.
In this embodiment, the first preset format is an XML format or a JSON format; the second preset format is a custom format.
In this embodiment, the first preset format is an XML format or a JSON format, but is not limited thereto; the second preset format is a custom format.
Fourth embodiment, fig. 4 is a flowchart illustrating a medical insurance interface data processing method according to a fourth embodiment of the present invention. The medical insurance interface data processing method comprises the following steps:
step 402, constructing an entity object of the target service according to the attribute information of the target service;
step 404, calling a medical insurance interface based on a preset medical insurance entry function;
step 406, determining a corresponding format according to the medical insurance document information corresponding to the medical insurance interface;
step 408, based on the condition that the corresponding format is the first preset format, converting the entity object of the target service into the target object of the first preset format, and generating a first service message according to the target object; generating a first service message according to the entity object of the target service under the condition that the corresponding format is a second preset format;
step 410, determining whether the tag of the entity object is preset information, if so, executing step 412, otherwise, executing step 414;
step 412, encrypting the first service message to obtain a second service message and sending the second service message to a medical insurance interface;
and step 414, directly sending the first service message to the medical insurance interface.
In this embodiment, whether to encrypt the first service packet is determined by the tag, and when the tag is the preset information, the first service packet needs to be encrypted.
Fifth embodiment, fig. 5 is a flowchart illustrating a medical insurance interface data processing method according to a fifth embodiment of the present invention. The medical insurance interface data processing method comprises the following steps:
step 502, constructing an entity object of the target service according to the attribute information of the target service;
step 504, calling a medical insurance interface based on a preset medical insurance entry function;
step 506, determining a corresponding format according to the medical insurance document information corresponding to the medical insurance interface;
step 508, based on the condition that the corresponding format is the first preset format, converting the entity object of the target service into the target object of the first preset format, and generating a first service message according to the target object; generating a first service message according to the entity object of the target service under the condition that the corresponding format is a second preset format;
step 510, determining whether the tag of the entity object is preset information, if so, executing step 512, and if not, executing step 514;
step 512, encrypting the first service message to obtain a second service message and sending the second service message to a medical insurance interface;
step 514, directly sending the first service message to a medical insurance interface;
and 516, receiving the result message fed back by the medical insurance interface, and performing data reverse processing on the result message to convert the result message into a result entity of the target service.
In this embodiment, the result message fed back by the medical insurance interface is received, and data reverse processing is performed on the result message, specifically, decryption processing and encoding processing are included, so that the result message is converted into a result entity of the target service and returned to the HIS system. Through the embodiment of the invention, the bidirectional data format conversion between the HIS end service and the medical insurance end service is realized, so that the process of medical insurance interface development is better normalized, and the low coupling between the medical insurance interface and the HIS system is realized.
In any of the above embodiments, the entity object comprises a tag, and any one or a combination of: patient name, sex, medical insurance information, location of visit, project of visit, unit price, total cost.
In this embodiment, the physical object includes a label, and any one or a combination of the name, the sex, the medical insurance information, the location of the visit, the item of the visit, the unit price, and the total cost of the patient, wherein the label may be the label of the physical object, or the label of any field in the physical object. By abstracting the business data into the entity object and setting the tag, on one hand, the processing mode of the parameter can be normalized, so that the redundant code amount is reduced, and on the other hand, annotation information can be added to the entity object, such as information of encryption and the like, so that the safety of the transaction process is ensured.
In any of the above embodiments, the preset medical insurance entry function includes a medical insurance initialization function, a medical insurance card reading function, and an in-patient business function or an out-patient business function.
In this embodiment, the preset medical insurance entrance function includes a medical insurance initialization function, a medical insurance card reading function, and an in-patient business function related to the core business of the institution, and an out-patient business function related to the core business of the out-patient. Moreover, the position, the function name and the step of calling the medical insurance processing at the HIS end are clarified and normalized as much as possible by utilizing the commonality and shielding individuality, and unnecessary repeated labor and maintenance of different programs are avoided.
The sixth embodiment provides a software dependency relationship analysis method. The software dependency relationship analysis method comprises the following steps:
firstly, a standardized medical insurance entry function (namely a preset medical insurance entry function) is preset, the commonalities and the shielding individuality are utilized, the position, the function name and the step of calling medical insurance processing at the HIS end are clarified and normalized as much as possible, and unnecessary repeated labor and different program maintenance are avoided. The standardized medical insurance entry function mainly comprises the following parts:
a medical insurance initialization function;
a medical insurance card reading function;
core service of hospitalization: medical insurance admission registration, medical insurance admission registration revocation, medical insurance discharge registration revocation, medical insurance discharge settlement revocation, medical insurance pre-settlement, medical insurance (doctor's advice/charge) detail uploading, and medical insurance (doctor's advice/charge) detail revocation;
the core business of the outpatient service: the medical insurance outpatient service registration, the medical insurance outpatient service registration cancellation, the medical insurance outpatient service charge settlement cancellation and the medical insurance outpatient service charge pre-settlement.
And secondly, embedding a standardized medical insurance entrance function into an HIS service trigger point, isolating the HIS end service and the medical insurance end service, not directly embedding a medical insurance processing process in the HIS end service, and only embedding the standardized medical insurance (transaction) entrance function into the service trigger point where the service occurs. Therefore, the HIS end service and the medical insurance end service can be decoupled. The completeness of the HIS main program of each hospital can be met, and the HIS main program can be flexibly expanded to carry out customized development.
And thirdly, according to the medical insurance document information corresponding to the medical insurance interface, carrying out data processing on the entity object to obtain the service message in the corresponding format. The step can support the transmission of various parameter types (XML, custom separator '|', JSON), realize the automatic analysis, automatic formatting and standardized processing of the parameters, and greatly reduce the redundant code quantity.
At present, it is difficult to develop and complete a medical insurance interface and want to perform networking debugging, and the following problems are mainly faced: whether the local medical insurance environment provides a test network environment or not and whether the hospital has medical insurance network conditions or not. Based on the uncertainty of the problems, a virtual medical insurance service is instantiated according to the entity information of the medical insurance document information and is used for offline debugging.
Fig. 6 shows an interaction diagram of the HIS side and the medical insurance side of the medical insurance interface data processing method according to the sixth embodiment of the present invention. The process of assembling entities and adding annotations in the service data is to construct entity objects of the target service according to the attribute information of the target service, and it should be noted that one entity includes one or more entity objects.
And the common message processor performs data processing on the entity object according to the medical insurance document information corresponding to the medical insurance interface to obtain the service message in the corresponding format. Firstly, a judgment process of advanced characteristics is carried out, specifically, a format required by a medical insurance interface is determined according to medical insurance document information, if the corresponding format is XML or JSON, the high-level characteristics are judged to be possessed, an advanced adapter is adopted to convert an entity object into a target object in an XML or JSON expression mode, and then the target object is reflected to generate a message (namely, a first service message). And if the corresponding format is the self-defined format, directly carrying out data processing on the entity object so as to generate a message (namely the first service message) in a reflection mode.
The encryption/decryption method is, but not limited to, BASE 64.
And defining an adaptive message processor to encode the result message, and specifically, constructing a result entity through generic parsing.
The software dependency relationship analysis method provided by the embodiment has the following beneficial technical effects:
the method has the advantages that the process of medical insurance interface development is standardized, so that the public can realize medical insurance development according to steps according to the development technical guide, and the key point of medical insurance development focuses on data level processing from process development.
And secondly, low coupling of the medical insurance interface and the HIS service system is realized, and the reusability of the HIS product is improved.
And thirdly, the virtual medical insurance service solves the problem of difficulty in debugging when the private network limit of the medical insurance network is limited.
According to another aspect of the present invention, a software dependency analysis apparatus is provided, and fig. 7 shows a schematic block diagram of a medical insurance interface data processing apparatus 700 according to an embodiment of the present invention. The medical insurance interface data processing apparatus 700 includes: a memory 702, the memory 702 storing a program; a processor 704, wherein the processor 704 executes the program to implement the medical insurance interface data processing method according to any of the above embodiments.
In the medical insurance interface data processing apparatus 700 provided in this embodiment, when the processor 704 executes the program, the steps of the medical insurance interface data processing method according to any of the above embodiments are implemented, so that the medical insurance interface data processing apparatus 700 includes all the beneficial effects of the medical insurance interface data processing method according to any of the above embodiments.
According to an embodiment of a further aspect of the present invention, a readable storage medium is provided, on which a program is stored, which when executed by a processor implements the medical insurance interface data processing method according to any one of the embodiments described above.
The readable storage medium provided by this embodiment, when being executed by the processor, implements the steps of the medical insurance interface data processing method according to any of the above embodiments, and therefore, the readable storage medium includes all the beneficial effects of the medical insurance interface data processing method according to any of the above embodiments.
In the description herein, the terms "first" and "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance unless explicitly stated or limited otherwise; the terms "connected," "mounted," "secured," and the like are to be construed broadly and include, for example, fixed connections, removable connections, or integral connections; may be directly connected or indirectly connected through an intermediate. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
In the description herein, the description of the terms "one embodiment," "some embodiments," "specific embodiments," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A medical insurance interface data processing method is characterized by comprising the following steps:
constructing an entity object of the target service according to the attribute information of the target service;
calling the medical insurance interface based on a preset medical insurance entry function;
and according to the medical insurance document information corresponding to the medical insurance interface, performing data processing on the entity object to obtain a service message in a corresponding format.
2. The medical insurance interface data processing method according to claim 1, wherein the step of performing data processing on the entity object according to medical insurance document information corresponding to the medical insurance interface to obtain the service packet in the corresponding format specifically includes:
according to the medical insurance document information, the entity object is converted into a first service message in a corresponding format;
encrypting the first service message based on the condition that the first service message needs to be encrypted to obtain a second service message and sending the second service message to the medical insurance interface;
and directly sending the first service message to the medical insurance interface under the condition that the first service message does not need to be encrypted.
3. The medical insurance interface data processing method of claim 2,
the entity object comprises a tag, and any one or combination of: patient name, sex, medical insurance information, location of visit, project of visit, unit price, total cost.
4. The medical insurance interface data processing method according to claim 3, wherein the step of converting the entity object of the target service into the first service packet in the corresponding format according to the medical insurance document information specifically includes:
based on the condition that the corresponding format is a first preset format, converting the entity object of the target service into the target object of the first preset format, and generating the first service message according to the target object;
and generating the first service message according to the entity object of the target service under the condition that the corresponding format is a second preset format.
5. The medical insurance interface data processing method of claim 4,
the first preset format is an XML format or a JSON format;
the second preset format is a custom format.
6. The medical insurance interface data processing method of claim 5, further comprising:
and encrypting the first service message based on the condition that the label is preset information.
7. The medical insurance interface data processing method according to any one of claims 2 to 6, further comprising:
and receiving a result message fed back by the medical insurance interface, and performing data reverse processing on the result message so as to convert the result message into a result entity of the target service.
8. The medical insurance interface data processing method of claim 7, further comprising:
the preset medical insurance entrance function comprises a medical insurance initialization function, a medical insurance card reading function and an inpatient service function or an outpatient service function.
9. A software dependency analysis apparatus, comprising:
a memory storing a program;
a processor implementing the medical insurance interface data processing method of any one of claims 1 to 8 when executing the program.
10. A readable storage medium on which a program is stored, the program implementing the medical insurance interface data processing method according to any one of claims 1 to 8 when executed by a processor.
CN202011201648.7A 2020-11-02 2020-11-02 Medical insurance interface data processing method, data processing device and readable storage medium Pending CN112306585A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011201648.7A CN112306585A (en) 2020-11-02 2020-11-02 Medical insurance interface data processing method, data processing device and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011201648.7A CN112306585A (en) 2020-11-02 2020-11-02 Medical insurance interface data processing method, data processing device and readable storage medium

Publications (1)

Publication Number Publication Date
CN112306585A true CN112306585A (en) 2021-02-02

Family

ID=74334239

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011201648.7A Pending CN112306585A (en) 2020-11-02 2020-11-02 Medical insurance interface data processing method, data processing device and readable storage medium

Country Status (1)

Country Link
CN (1) CN112306585A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113641354A (en) * 2021-08-03 2021-11-12 挂号网(杭州)科技有限公司 Service data processing method and device, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111182025A (en) * 2019-11-26 2020-05-19 腾讯科技(深圳)有限公司 Message processing method, device, server and storage medium
WO2020119097A1 (en) * 2018-12-13 2020-06-18 平安医疗健康管理股份有限公司 Data standardization processing method and device, and storage medium
CN111314375A (en) * 2020-03-16 2020-06-19 青岛百洋智能科技股份有限公司 Medical insurance data adaptation engine, medical insurance data adaptation method, electronic equipment and storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020119097A1 (en) * 2018-12-13 2020-06-18 平安医疗健康管理股份有限公司 Data standardization processing method and device, and storage medium
CN111182025A (en) * 2019-11-26 2020-05-19 腾讯科技(深圳)有限公司 Message processing method, device, server and storage medium
CN111314375A (en) * 2020-03-16 2020-06-19 青岛百洋智能科技股份有限公司 Medical insurance data adaptation engine, medical insurance data adaptation method, electronic equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
吴长坤;: "医院信息管理系统与医保系统接口的设计与实现", 科技创新导报, no. 16, 1 June 2010 (2010-06-01), pages 220 *
孙桢;江干桢;张群瑜;: "基于数据标准的医保接口框架设计与实现", 医院管理论坛, no. 02, 20 February 2020 (2020-02-20), pages 71 - 73 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113641354A (en) * 2021-08-03 2021-11-12 挂号网(杭州)科技有限公司 Service data processing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US8990834B2 (en) Managing healthcare information in a distributed system
US10430549B2 (en) Teleradiology image processing system
US8612255B1 (en) System and method for standardized and automated appeals process
US10089132B2 (en) Methods and systems for providing a customized network
US7778844B2 (en) System and method for managing the exchange of information between healthcare systems
US20100017316A1 (en) Automated expense report
US20150120329A1 (en) Operating system
KR100696708B1 (en) Medical information online transmission system
US20050033605A1 (en) Configuring a semantic network to process health care transactions
US20060173672A1 (en) Processing health care transactions using a semantic network
US20070033137A1 (en) Converting patient payments into standardized electronic payment documents
US9721231B2 (en) Computer system for processing data from a plurality of remote input devices for transmission to a third-party computer
Rodrigues et al. e-Health systems: theory and technical applications
US20060026037A1 (en) Online doctor/patient lead system and associated methods
US20050033583A1 (en) Processing transactions using a structured natural language
US20050010394A1 (en) Configuring a semantic network to process transactions
CN112306585A (en) Medical insurance interface data processing method, data processing device and readable storage medium
KR20050015059A (en) Medical treatment information provision system
US11715089B2 (en) Methods and systems for electronic communication between users, provider, and payers
KR100561316B1 (en) General Medical Prescription Transmitting System
US20140046681A1 (en) Response Message Normalization System
KR20100127939A (en) System and method for managing cooperation business service and recording medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination