CN113379384A - Medical event big data platform - Google Patents
Medical event big data platform Download PDFInfo
- Publication number
- CN113379384A CN113379384A CN202110650184.6A CN202110650184A CN113379384A CN 113379384 A CN113379384 A CN 113379384A CN 202110650184 A CN202110650184 A CN 202110650184A CN 113379384 A CN113379384 A CN 113379384A
- Authority
- CN
- China
- Prior art keywords
- event
- management
- data
- layer
- report
- 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
- 238000004458 analytical method Methods 0.000 claims abstract description 24
- 230000006872 improvement Effects 0.000 claims abstract description 24
- 238000000034 method Methods 0.000 claims abstract description 21
- 238000012544 monitoring process Methods 0.000 claims abstract description 15
- 230000008569 process Effects 0.000 claims abstract description 10
- 238000007726 management method Methods 0.000 claims description 115
- 230000002411 adverse Effects 0.000 claims description 30
- 238000011156 evaluation Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 20
- 230000008520 organization Effects 0.000 claims description 18
- 238000003908 quality control method Methods 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 9
- 238000011049 filling Methods 0.000 claims description 8
- 238000013075 data extraction Methods 0.000 claims description 7
- 238000011068 loading method Methods 0.000 claims description 7
- 230000006870 function Effects 0.000 claims description 6
- 239000000463 material Substances 0.000 claims description 6
- 238000003066 decision tree Methods 0.000 claims description 5
- 229940079593 drug Drugs 0.000 claims description 5
- 239000003814 drug Substances 0.000 claims description 5
- 230000010354 integration Effects 0.000 claims description 5
- 238000010276 construction Methods 0.000 claims description 4
- 238000013500 data storage Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 claims description 3
- 238000002955 isolation Methods 0.000 claims description 3
- 238000002360 preparation method Methods 0.000 claims description 3
- 238000000556 factor analysis Methods 0.000 abstract description 6
- 238000011161 development Methods 0.000 abstract description 4
- 238000007621 cluster analysis Methods 0.000 abstract description 2
- 238000004141 dimensional analysis Methods 0.000 abstract description 2
- 238000012423 maintenance Methods 0.000 description 4
- 239000011159 matrix material Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000000474 nursing effect Effects 0.000 description 3
- 230000003111 delayed effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000002265 prevention Effects 0.000 description 2
- 238000012502 risk assessment Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 206010002091 Anaesthesia Diseases 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000037005 anaesthesia Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 208000015181 infectious disease Diseases 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F18/00—Pattern recognition
- G06F18/20—Analysing
- G06F18/23—Clustering techniques
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Data Mining & Analysis (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Evolutionary Computation (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Bioinformatics & Computational Biology (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Evolutionary Biology (AREA)
- Artificial Intelligence (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Life Sciences & Earth Sciences (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The invention discloses a medical event big data platform, which is applied to the technical field of information and comprises the following steps: the system comprises an infrastructure layer, a data layer, a supporting layer, an application layer and a display layer. The invention realizes the overall process management of adverse event reporting, disposal, monitoring, tracking, analysis, rectification and learning; forming multi-dimensional analysis conclusions such as cluster analysis, factor analysis and the like by using reliable quality analysis tools and algorithms; the method provides more data support for future benign development of medical quality supervision and medical risk monitoring, has good expansibility, and can meet the requirement of continuous improvement and upgrade.
Description
Technical Field
The invention relates to the technical field of information, in particular to a medical event big data platform.
Background
With the increasing concern on the safety of patients at home and abroad, the importance of China on the safety of the patients is also improved by a new height.
In order to improve the quality control of hospitals and the safety guarantee capability of patients, a standardized, normalized and intelligent supervision system is formed, the refined closed-loop management of medical safety (adverse) events is realized, the overall control capability of management departments is improved, and powerful guarantee is provided for hospital grade review and JCI authentication. Therefore, it is an urgent need of those skilled in the art to provide a medical event big data platform for managing medical safety (adverse) events, and reducing the occurrence rate of adverse events, improving the satisfaction of patients, and effectively improving the medical-patient relationship through event prevention, reporting, handling, supervision, analysis and improvement.
Disclosure of Invention
In view of the above, the present invention provides a medical event big data platform, which is a problem that needs to be solved by those skilled in the art to manage medical safety (adverse) events, and reduce the occurrence rate of adverse events and improve the satisfaction of patients through event prevention, reporting, handling, supervision, analysis and improvement.
In order to achieve the purpose, the invention adopts the following technical scheme:
a medical event big data platform, comprising: the system comprises an infrastructure layer, a data layer, a supporting layer, an application layer and a display layer;
the infrastructure layer is used for controlling hardware, processing data, maintaining a server and guaranteeing safety equipment;
the data layer is used for collecting and fusing third-party data and then gathering and integrating the third-party data in a centralized manner;
the supporting layer is used for providing data service;
the application layer is divided into two dimensions, namely a user layer and a management layer, and is used for opening different functional module authorities for different users through different role characteristics of the users;
and the display layer is used for carrying out application display service for the user.
Preferably, the infrastructure layer includes: the system comprises a server, a database, an operating system and middleware;
the server is used for providing continuous internet application and service, file uploading, data storage, application service or website browsing;
the database is used for managing data and providing a uniform interface and service for other applications;
the operating system is used for computer equipment management and provides an interface for a user and an application program;
the middleware is used for providing an environment for running and developing the application software on the upper layer of the current layer.
Preferably, the data layer includes: the system comprises an event level library, an influence degree library, an event factor library, a treatment result library, a patient identity library, a fee library, a medical insurance category library, an improvement suggestion library, a user library, an organization library, an event report library, a quality report library, data extraction, data classification, data synchronization, data integration and data loading;
the data extraction is used for acquiring basic information and treatment information of the patient;
the data classification is used for carrying out visualized statistics on the same data;
the data synchronization is used for synchronizing third-party data; the third-party data is HIS/LIS data of a hospital;
the data integration is to integrate different data into a chart for centralized comparison and display;
and the data loading is used for calling the data.
Preferably, the support layer includes: the system comprises an application support, a function support component, an integrated service component and a safety support component;
the application support is used for establishing a supervision system;
the functional support component is used for carrying out comprehensive management on reporting, handling, tracking, evaluating, analyzing, improving and learning around events;
the integrated service component is used for ensuring the support and the call among all services of the system;
the safety support component is used for data isolation among user roles and division of user permissions of different organizations.
Preferably, the application layer includes: event reporting, event handling, event management, report to be handled, report to be submitted, evaluation to be handled, quality control evaluation to be handled, general overview, root cause analysis, content center, level, degree of influence, classification, factor, result, identity, fee, medical insurance category, improvement suggestion, personnel category, place of occurrence, organization, user management, role management, and log management;
the event report is used for reporting adverse event information by reporting personnel;
the event handling is used for carrying out corresponding department handling or department combined handling after classifying the adverse events;
the event management is used for managing the circulation of the submitted events;
the report is to be dealt with and is used for reporting the condition that personnel check the state information of the adverse event and fail to report the monitoring condition;
the report to be submitted is used for displaying and storing the adverse events which are not submitted;
the to-be-disposed evaluation is used for evaluating the reported adverse events;
the evaluation to be quality controlled is used for displaying the event that the evaluation of the personnel to be quality controlled is finished;
the general overview is used for displaying event general information;
the root cause analysis is used for displaying and operating, and simultaneously, comprehensively guiding and managing the early preparation, the near-end cause, the root cause and the effect analysis of the RCA root cause analysis;
the content center is used for displaying and issuing policy consultation, learning materials and notice;
the level is used for clearly defining the event level according to the industry standard and a national medical safety report and learning system;
the influence degree is used for building an influence degree dictionary related to the event level;
the classification is used for establishing multi-level event classification aiming at patients, medical staff and medical institutions;
the factors are used for managing the factors of the multi-stage events;
the result is used for managing the treatment result of adverse events of patients, instrument consumables and medicines;
the identity, the fee category, and the medical insurance category for patient information interfacing;
the improvement suggestions are used for managing the improvement suggestions of different events and supporting the supplementary input when the user fills the report;
the personnel category is used for managing the personnel category;
the place of occurrence is used for dictionary management of the place of occurrence and supports a multi-level structure;
the organization mechanism is used for managing departments, departments and ward areas step by combining the organization mechanism construction condition of the medical institution to form organization mechanism information;
the user management is used for carrying out account password distribution and basic information filling;
the role management is used for allocating roles to the accounts;
the log management is used for recording the adding, deleting and changing operations of the user and simultaneously sorting and summarizing error logs occurring in the operation process of the system.
Preferably, the display layer comprises: the system comprises a reporting end, a processing end and a management end;
the report end is used for reporting adverse event reports to a reporter;
the processing end is used for processing adverse events by functional departments;
and the management terminal is used for managing adverse events and managing a system by a management department.
Preferably, the system management includes: menu management, department management, system user management, role management, personal information management, log management, password management, and dictionary management.
Preferably, the dictionary management is a basic module for maintaining the system operation, and includes: event level, degree of influence, event classification, event factor, place of occurrence, event result, improvement suggestion, treatment result, fee management, patient identity, medical insurance category, personnel category, data dictionary, content type, decision tree configuration and emphasis configuration, emphasis parameter.
According to the technical scheme, compared with the prior art, the invention provides a medical event big data platform which comprises the following steps: the invention realizes the overall process management of adverse event reporting, disposal, monitoring, tracking, analysis, rectification and learning; forming multi-dimensional analysis conclusions such as cluster analysis, factor analysis and the like by using reliable quality analysis tools and algorithms; the method provides more data support for future benign development of medical quality supervision and medical risk monitoring, has good expansibility, and can meet the requirement of continuous improvement and upgrade.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a diagram of a medical event big data platform system architecture according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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 invention.
Example 1
Referring to fig. 1, the present embodiment discloses a medical event big data platform system, including:
the system comprises an infrastructure layer, a data layer, a supporting layer, an application layer and a display layer;
the infrastructure layer is used for controlling hardware, processing data, maintaining a server and guaranteeing safety equipment;
the data layer is used for collecting and fusing third-party data, gathering and integrating the third-party data, and processing data loading;
a support layer for providing centralized data services;
the application layer is divided into two dimensions, namely a user layer and a management layer, and is used for opening different functional module authorities for different users through different role characteristics of the users;
and the display layer is used for providing application display services of a report end, a processing end and a quality control end for a clinical department reporter, a functional department handler and a quality department of a management department.
In one particular embodiment, the infrastructure layer includes: the system comprises a server, a database, an operating system and middleware;
the server is used for providing continuous Internet application and service, and providing file uploading, data storage, application service or website browsing;
the database is used for managing data and providing a uniform interface and service for other applications;
the operating system is used for managing the computer equipment, improving the utilization rate of the computer equipment and the system throughput, and providing interfaces for users and application programs for the users to use;
and the middleware is used for providing an operation and development environment for the application software on the upper layer of the layer and helping a user to flexibly and efficiently develop and integrate the complex application software.
In one embodiment, the hospital systems are connected in the later period, and the infrastructure layer may comprise storage equipment, network equipment, safety equipment and the like.
In one particular embodiment, the data layer includes: the system comprises an event level library, an influence degree library, an event factor library, a treatment result library, a patient identity library, a fee library, a medical insurance category library, an improvement suggestion library, a user library, an organization library, an event report library, a quality report library, data extraction, data classification, data synchronization, data integration and data loading;
data extraction is used for acquiring basic information and treatment information of a patient, namely, the data extraction is in butt joint with the existing HIS system of a hospital, so that the basic information and the treatment information of the patient can be automatically acquired after the ID of the patient is input;
data classification, namely performing visualized statistics on the same data for event analysis;
data synchronization for synchronizing third party data;
integrating data, namely integrating different data into a chart for centralized comparison and display for event analysis;
data loading, for the invocation of required data, i.e. a call of system functions to required data, for respective logical needs and processing.
In one embodiment, the third party data is HIS/LIS data for a hospital.
In one particular embodiment, the support layer comprises: the system comprises an application support, a function support component, an integrated service component and a safety support component;
the application support is used for improving the quality control of a hospital and the safety guarantee capability of a patient, and a standardized, normalized and intelligent supervision system is formed;
the functional support component is used for carrying out comprehensive management on reporting, handling, tracking, evaluating, analyzing, improving and learning around an event;
the integrated service component is used for ensuring the support and the call among all services of the system;
and the safety support component is used for data isolation among user roles and division of user permissions of different organizations.
In one particular embodiment, the application layer includes: event reporting, event handling, event management, report to be handled, report to be submitted, evaluation to be handled, quality control evaluation to be handled, general overview, root cause analysis, content center, level, degree of influence, classification, factor, result, identity, fee, medical insurance category, improvement suggestion, personnel category, place of occurrence, organization, user management, role management, and log management;
the event report is used for reporting adverse event information by a reporting person;
event handling, which is used for handling corresponding departments or jointly handling departments after the adverse events are classified;
event management, for the flow management of submitted events, comprising: a to-be-submitted report, a to-be-treated evaluation report, a to-be-treated report, a to-be-assessed report, a my treatment, a my assessment, and a total report;
the report is to be dealt, and is used for reporting personnel to visually browse the current conditions of to-be-submitted, return, overtime non-treatment, to-be-treated evaluation and report missing monitoring;
the report to be submitted is used for displaying and saving the adverse events which are not submitted;
the to-be-treated evaluation is used for evaluating the reported adverse events;
the quality control evaluation is used for displaying the event of finishing the evaluation of the personnel to be quality controlled;
a general overview for displaying event level and influence analysis, sac risk assessment matrix, department severity condition, patient class event classification/age group and gender/identity/fee condition, medical staff class occurrence person type/department distribution condition, medical institution class event department distribution condition, occurrence place, date and time, unexpected reentry condition, pareto factor analysis, fishbone map factor analysis, and treatment result and improvement suggestion analysis;
root cause analysis, which is used for displaying and operating, and simultaneously guides and manages the early preparation, the near-end cause, the root cause and the effect analysis of the RCA root cause analysis in all aspects;
the content center is used for displaying and issuing policy consultation, learning materials and notice notification;
the level is used for clearly defining the event level according to the industry standard and the national medical safety report and learning system;
the influence degree is used for building an influence degree dictionary and is associated with the event levels one by one;
classification, for establishing a multi-level event classification for patients, medical staff and medical institutions;
the factors are used for carrying out factor analysis on the supporting clustering events and managing the factors of the multi-stage events according to the completeness of the adverse events; establishing a factor dictionary, and developing around six categories of human, machine, material, method, ring and measurement;
the result is used for managing the treatment result after adverse events occur to patients, instrument consumables and medicines;
identity, charge and medical insurance category, which is used for patient information docking and is taken from a relevant service system, and editing operation is not carried out in the system;
the improvement suggestions are used for managing the improvement suggestions of different events and supporting the supplementary input when the user fills the report;
a staff category for managing staff categories and setting basic category doctors, pharmacists, nursing staff, technicians, management and others;
the place of occurrence is used for the dictionary management of the place of occurrence, manages the place of occurrence and supports a multilevel structure;
the organization mechanism is used for managing departments, ward areas and the like step by combining the construction condition of the organization mechanism of the medical institution to form organization mechanism information;
user management, which is used for carrying out account password allocation and basic information filling; the module is mainly used for carrying out account number and password distribution and basic information filling, and logging in the system through the account number after adding;
and (4) role management, wherein a system builds a role management module through a classical authority design mode RBAC, allocates roles for the account, and controls a user to access a management background through the roles to obtain different management modules, function operations and data authorities. Meanwhile, the administrator can assign roles to the accounts of the current level and the subordinate level, and the role batch assignment is supported. The system is provided with four roles of a reporter, a handler, a quality controller and an administrator, wherein the first three roles are service roles, and the fourth role is a management role;
log management, which is used to record the operation of adding, deleting and changing users and to collect and summarize the error log occurred in the operation process of the system. On one hand, the method meets the requirement of back check of managers on the operation of important nodes, and on the other hand, the method assists technical maintenance personnel in quickly positioning operation hidden dangers.
In one particular embodiment, the event report:
the adverse event report form comprises report basic information, event conditions, processing analysis and event improvement, and relates to more than 30 events of 3 damage groups, such as patient safety, medical management, nursing management, drug management, instrument consumables, medical technology management, blood transfusion management, infection management, information management, logistics management, patient satisfaction, public security management and the like; the expanded major category relates to more than 100 detailed event categories, and supports multi-choice categories when reporting events.
Event information:
basic information of the patient: automatically recording the sex, age, identity and the like of inpatients and outpatients by adopting unique items such as patient ID and the like; and the table is automatically filled after the patient outpatient diagnosis condition, the outpatient operation condition, the admission diagnosis condition and the hospitalization operation condition are docked with the HIS system.
Event information: managing the time, the place and the participants of the event;
event situation: filling in event types, influence degrees, event levels, main expressions, occurrence places and the like, wherein the places can cover information of buildings and departments in a hospital and record the information of places outside the hospital;
and (3) processing and analyzing: managing the conditions of the notifiers, the event occurrence factors, the measures taken by departments and the treatment results;
event improvement: filling in event improvement suggestions and analysis tool application suggestions;
a treatment department: event handling departments may be automatically associated.
Anonymous submission: in order to improve the enthusiasm of medical staff, the system supports anonymous submission of adverse events, processes such as treatment staff and the like are anonymous after submission, and simultaneously, target values of the department are not counted.
Temporary preservation: the clinical medical staff is busy in work and the content of adverse event information is more, so that the temporary storage is supported in the system for the user to have good operation experience.
Event related information: and forming a visual time axis for the operation time and personnel of each process node of the event, displaying a recently issued system in a hospital, and displaying the previous adverse event of the patient.
In one embodiment, the report is to do:
aiming at a management page specially designed by a reporter, the conditions of current to-be-submitted, return, overtime non-treatment, to-be-treated evaluation and report missing monitoring are visually browsed, statistics display and list visual display are supported, and the operation is convenient and rapid.
And (3) waiting for submission of an event: displaying the latest report information to be submitted (event level and classification), supporting more checking, supporting immediate submission and deletion operation, and supporting PDF export of full report information (self-printing after export) after entering details;
a return in event: department personnel are required to pay close attention to the event handling condition, the returned event is modified, resubmitted or deleted, report information (level, classification and return reason) in the current return is displayed, more viewing is supported, and editing, deleting and detailed operation are supported;
timeout not handled event: the situation of the current overtime untreated event of the treatment department is displayed, so that department personnel can conveniently perform treatment reminding (grade, classification, treatment department and remaining time) according to needs, and detailed operation is supported;
to-be-treated evaluation event: in order to improve the attention of clinical departments to the subsequent progress of adverse events and improve the treatment effectiveness of treatment departments, the clinical departments evaluate (grade and classification) the treatment conditions of the treatment departments, and support evaluation and detailed operation;
and (4) missing report monitoring: the system can realize the service butt joint with the existing system of the hospital and realize the real-time monitoring of the failure report and the failure report of the adverse events.
In a particular embodiment, event handling:
and locking treatment departments according to event classification, and supporting multi-department joint treatment. When an error is found in the event report or a handling department error exists, the event report can be returned. When the report information is correct, the process of treatment, the treatment result, the treatment mode and the attribute, effectiveness and timeliness of the report information are described in detail.
List to be disposed: displaying information to be treated, including numbers, levels, classifications, influence degrees, reporters, occurrence places, occurrence time, reporting time, overtime time and remaining time, and supporting treatment, return and detail operations;
and (3) withdrawing: the treating personnel preliminarily checks whether the report information is wrong, returns the event if the report information is wrong, and judges whether the return is effective or not by the quality control department after the return;
treatment: the report information is subjected to offline treatment if no obvious error exists after the report information is preliminarily checked, and the treatment mode, the treatment content and the treatment result are recorded in the system to identify whether the situations of delayed report and lie report exist or not; meanwhile, the timely condition, the actual condition and the effective treatment condition of the report of the clinical department are evaluated;
treatment statistics: the treated conditions, the conditions to be treated and the overtime treatment conditions in the month are counted, and the treatment conditions reported by each department are shown in a stacked bar graph form (only the treatment quantity of the home department is shown).
In one embodiment, the method further comprises quality control monitoring:
aiming at a management page specially designed by a manager of a quality control department, the current serious event, the mandatory report event, the report missing condition, the overtime non-handling condition and the condition to be audited are visually checked. The method and the device realize the tracking of the key events, the reminding of overtime treatment and the processing of personal work.
Class I/II events: events with corresponding event levels of I level or II level belong to important attention events in a hospital; after checking the mandatory report event, only searching the special classification;
SAC risk assessment matrix: classifying the events and grouping the events by using the influence degrees and the occurrence frequencies, wherein the severity comprises five grades of severity (corresponding to the influence degree I grade), more severity (corresponding to the influence degree G grade and H grade), medium severity (corresponding to the influence degree E grade and F grade), slightly severity (corresponding to the influence degree D grade) and slight severity (corresponding to the influence degree C grade); the occurrence frequency is divided into five types, wherein once in weeks means that the occurrence frequency of events is higher than 1 time in 1 month in the last 1 year, and the occurrence frequency is higher than 1 time in 1 year and is less than 1 time in 1 month in the last 1 year;
and (3) events to be audited: the quality controller checks and distributes the events returned by the operation of the disposal department, the disposal department can be adjusted when the events are distributed to the disposal department, the state of the event report after storage is to be disposed, and the state of the event report after storage is to be submitted when the events are distributed to a clinical department;
and (4) missing report monitoring: the monitored report information is displayed, and a quality controller can conveniently carry out report reminding on a disposal department: event handling departments can be automatically associated;
timeout not handled: the number of the events which are not processed in the overtime currently is displayed by taking a processing department as a unit, and the detailed event information can be displayed, so that a quality controller can conveniently perform processing reminding.
In one embodiment, the method further comprises quality control monitoring: by interfacing with the existing business system of the hospital, fixed event classifications such as patient anesthesia death and the like are obtained, automatic reminding and one-touch reporting are supported, and reports which are not reported for a long time or are deleted maliciously can be defined as being withheld. And reading, verifying and storing the specified event classification data by other business system interfaces according to the monitoring requirement. After the event is stored, the corresponding department personnel reports or deletes the event (deal with the wrong monitoring data), and the management role such as a quality controller can also mark the event which is not reported for a long time as being withheld.
In a specific embodiment, the method further comprises the following steps of:
the method comprises the steps of analyzing the level and the degree of influence of an event, evaluating a sac risk matrix, analyzing the severity condition of each department, classifying/age group and sex/identity/fee condition of a patient event, distributing the type/department of a medical staff event, distributing the department of a medical institution event, distributing the occurrence place, date and time, unexpected return condition, analyzing pareto factor, analyzing fishbone map factor, analyzing the treatment result and improving the suggestion and the like.
In a particular embodiment, further comprising a quality report:
reporting the target value: accumulating the time progress and the target value progress, the situation of an unreported event, the situation of the completion of the target value and the situation of the event report trend. Reporting a problem condition: leaky/concealed/panic/slow, return, fit, valid, etc. situations and reporter category situations.
Time schedule and target value schedule: accumulating the report condition of the current query time in the same year;
event classification not reported: displaying the event classification with the report quantity of 0 under the query condition;
each department reports the completion of the target value: appointing time and reporting the report condition of each department under the condition of the department of the reporting department;
the target value completes the trend: counting by time dimension, report quantity and target value conditions of different periods;
reporting a problem: and carrying out example statistics on the possible situations of missing report, concealed report, lie report, delayed report, return, actual behavior and effective situation in the reporting process.
In one particular embodiment, the presentation layer comprises: the system comprises a reporting end, a processing end and a management end;
the height reporting end is used for reporting adverse event reports to a reporter;
the processing end is used for processing adverse events by functional departments;
and the management end is used for managing adverse events and managing the system by a management department.
In one embodiment, system management comprises: menu management, department management, system user management, role management, personal information management, log management, password management, and dictionary management.
The menu management is used by development or operation and maintenance personnel, is closed to a common user and comprises the type, name, icon, link and the like of the menu. Department and department management, which combines the construction situation of the organization of the medical institution to manage the departments, ward areas and the like step by step to form relatively complete organization information. The system user management, the system user refers to system maintenance, work handling and leader under relevant organization, the module is mainly used for distributing account number and password, filling in basic information, and logging in the system through the account number after adding. And (4) role management, wherein a system builds a role management module through a classical authority design mode RBAC, allocates roles for the account, and controls a user to access a management background through the roles to obtain different management modules, function operations and data authorities. Meanwhile, the administrator can assign roles to the accounts of the current level and the subordinate level, and the role batch assignment is supported. The system is provided with four roles of a reporter, a handler, a quality controller and an administrator, wherein the first three roles are business roles, and the fourth role is a management role. And personal information management, which supports the adjustment of names, categories, jobs, titles, contact calls and mailboxes. And log management, namely recording the main operations of adding, deleting and changing users in the system, and simultaneously sorting and summarizing error logs occurring in the operation process of the system, so that on one hand, the condition that managers check back the operation of important nodes is met, and on the other hand, technical maintenance personnel are assisted to quickly position hidden operating hazards is met. Password management, providing user to modify the login password of the user, inputting the original password for verification and inputting a new password to complete password modification. The dictionary management is a basic module for maintaining the operation of the system, necessary configuration of service data such as adverse event related event levels, influence degrees, event classification, event factors and the like is completed through establishment of system management, and unified management, flexible expansion, system control and the like are realized.
In one embodiment, dictionary management is a basic module for maintaining system operation, including: event level, degree of influence, event classification, event factor, place of occurrence, event result, improvement suggestion, treatment result, fee management, patient identity, medical insurance category, personnel category, data dictionary, content type, decision tree configuration and emphasis configuration, emphasis parameter.
In one embodiment, the temporal level, according to industry standards and national medical safety reporting and learning systems, defines the event level explicitly, i.e., the level I-IV event level. Meanwhile, the report time and the treatment time required by each level are configured; as shown in table 1:
TABLE 1 event level dictionary
In a specific embodiment, the influence degree is one-to-one associated with the event level by building a standard influence degree dictionary; as shown in table 2:
in one particular embodiment, event classification builds a multi-level event classification for the three major groups involved in adverse events, namely patients, medical personnel and medical institutions.
In one embodiment, event factors manage multiple levels of event factors to support event factor analysis for clustering and the integrity of adverse events. The establishment of the factor dictionary is expanded around six categories of human, machine, material, method, ring and measurement.
In one embodiment, the venue is managed, a venue dictionary is managed, the venue is managed, and a multi-level structure is supported.
In one embodiment, the event results are used to manage the possible treatment results of patients, equipment consumables, drugs, etc. after adverse events.
In one embodiment, the improvement suggestions are managed for different events, and the user is supported to supplement the input when filling the report.
In a particular embodiment, the treatment results, which manage the treatment results, support a multi-level structure.
In one embodiment, the fee management involves patient information interfacing, taking from the relevant business system, and doing no editing within the system.
In one embodiment, patient identity, which relates to patient information interfacing, is obtained from the relevant business system without editing or the like within the system.
In one embodiment, the medical insurance category relates to patient information interfacing, taken from a related business system, without editing, etc. within the system.
In one embodiment, the personnel category, the management of personnel categories, the setting of basic categories physicians, pharmacists, nursing staff, technicians, administration, and others.
In one embodiment, the data dictionary manages data of other dictionary types, which currently includes data of job title, position, team member category, and the like.
In one embodiment, the content type manages policy information and the type of the subdivision of the learning material.
In one embodiment, the decision tree configuration and the emphasis configuration configure the abnormal event decision tree, including question, option (yes/no), and answer.
In a specific embodiment, the system parameters and the hospital parameters are managed by focusing on the parameters, wherein the hospital parameters are used for configuration (low use frequency, part of the parameters need to be matched by designers) of a system login page, quality control department information and the like; the system parameters comprise RCA group number, treatment department authority modification and the like.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention in a progressive manner. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. A medical event big data platform, comprising: the system comprises an infrastructure layer, a data layer, a supporting layer, an application layer and a display layer;
the infrastructure layer is used for controlling hardware, processing data, maintaining a server and guaranteeing safety equipment;
the data layer is used for collecting and fusing third-party data and then gathering and integrating the third-party data in a centralized manner;
the supporting layer is used for providing data service;
the application layer is divided into two dimensions, namely a user layer and a management layer, and is used for opening different functional module authorities for different users through different role characteristics of the users;
and the display layer is used for carrying out application display service for the user.
2. The medical event big data platform of claim 1,
the infrastructure layer includes: the system comprises a server, a database, an operating system and middleware;
the server is used for providing continuous internet application and service, file uploading, data storage, application service or website browsing;
the database is used for managing data and providing a uniform interface and service for other applications;
the operating system is used for computer equipment management and provides an interface for a user and an application program;
the middleware is used for providing an environment for running and developing the application software on the upper layer of the current layer.
3. The medical event big data platform of claim 1,
the data layer includes: the system comprises an event level library, an influence degree library, an event factor library, a treatment result library, a patient identity library, a fee library, a medical insurance category library, an improvement suggestion library, a user library, an organization library, an event report library, a quality report library, data extraction, data classification, data synchronization, data integration and data loading;
the data extraction is used for acquiring basic information and treatment information of the patient;
the data classification is used for carrying out visualized statistics on the same data;
the data synchronization is used for synchronizing third-party data;
the data integration is to integrate different data into a chart for centralized comparison and display;
and the data loading is used for calling the data.
4. The medical event big data platform of claim 1,
the support layer includes: the system comprises an application support, a function support component, an integrated service component and a safety support component;
the application support is used for establishing a supervision system;
the functional support component is used for carrying out comprehensive management on reporting, handling, tracking, evaluating, analyzing, improving and learning around events;
the integrated service component is used for ensuring the support and the call among all services of the system;
the safety support component is used for data isolation among user roles and division of user permissions of different organizations.
5. The medical event big data platform of claim 1,
the application layer comprises: event reporting, event handling, event management, report to be handled, report to be submitted, evaluation to be handled, quality control evaluation to be handled, general overview, root cause analysis, content center, level, degree of influence, classification, factor, result, identity, fee, medical insurance category, improvement suggestion, personnel category, place of occurrence, organization, user management, role management, and log management;
the event report is used for reporting adverse event information by reporting personnel;
the event handling is used for carrying out corresponding department handling or department combined handling after classifying the adverse events;
the event management is used for managing the circulation of the submitted events;
the report is to be dealt with and is used for reporting the condition that personnel check the state information of the adverse event and fail to report the monitoring condition;
the report to be submitted is used for displaying and storing the adverse events which are not submitted;
the to-be-disposed evaluation is used for evaluating the reported adverse events;
the evaluation to be quality controlled is used for displaying the event that the evaluation of the personnel to be quality controlled is finished;
the general overview is used for displaying event general information;
the root cause analysis is used for displaying and operating, and simultaneously, comprehensively guiding and managing the early preparation, the near-end cause, the root cause and the effect analysis of the RCA root cause analysis;
the content center is used for displaying and issuing policy consultation, learning materials and notice;
the level is used for clearly defining the event level according to the industry standard and a national medical safety report and learning system;
the influence degree is used for building an influence degree dictionary related to the event level;
the classification is used for establishing multi-level event classification aiming at patients, medical staff and medical institutions;
the factors are used for managing the factors of the multi-stage events;
the result is used for managing the treatment result of adverse events of patients, instrument consumables and medicines;
the identity, the fee category, and the medical insurance category for patient information interfacing;
the improvement suggestions are used for managing the improvement suggestions of different events and supporting the supplementary input when the user fills the report;
the personnel category is used for managing the personnel category;
the place of occurrence is used for dictionary management of the place of occurrence and supports a multi-level structure;
the organization mechanism is used for managing departments, departments and ward areas step by combining the organization mechanism construction condition of the medical institution to form organization mechanism information;
the user management is used for carrying out account password distribution and basic information filling;
the role management is used for allocating roles to the accounts;
the log management is used for recording the adding, deleting and changing operations of the user and simultaneously sorting and summarizing error logs occurring in the operation process of the system.
6. The medical event big data platform of claim 1,
the display layer comprises: the system comprises a reporting end, a processing end and a management end;
the report end is used for reporting adverse event reports to a reporter;
the processing end is used for processing adverse events by functional departments;
and the management terminal is used for managing adverse events and managing a system by a management department.
7. The medical event big data platform according to claim 6,
the system management comprises: menu management, department management, system user management, role management, personal information management, log management, password management, and dictionary management.
8. The medical event big data platform of claim 7,
the dictionary management is a basic module for maintaining the system operation, and comprises the following steps: event level, degree of influence, event classification, event factor, place of occurrence, event result, improvement suggestion, treatment result, fee management, patient identity, medical insurance category, personnel category, data dictionary, content type, decision tree configuration and emphasis configuration, emphasis parameter.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110650184.6A CN113379384A (en) | 2021-06-10 | 2021-06-10 | Medical event big data platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110650184.6A CN113379384A (en) | 2021-06-10 | 2021-06-10 | Medical event big data platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113379384A true CN113379384A (en) | 2021-09-10 |
Family
ID=77573847
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110650184.6A Pending CN113379384A (en) | 2021-06-10 | 2021-06-10 | Medical event big data platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113379384A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114145944A (en) * | 2021-10-20 | 2022-03-08 | 赣州市第五人民医院 | Adverse event prompt card and method suitable for nursing station |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104732327A (en) * | 2015-01-31 | 2015-06-24 | 付洋 | Network reporting system for medical adverse events in hospital |
| CN105791416A (en) * | 2016-04-13 | 2016-07-20 | 山东省立医院 | Medical device administration event report and safety early warning information orientation transmission system |
| CN105976291A (en) * | 2016-05-30 | 2016-09-28 | 镇江市第人民医院 | Hospital adverse event reporting processing system and hospital adverse event reporting processing method |
| CN112927786A (en) * | 2021-03-15 | 2021-06-08 | 浙江省武义县第一人民医院 | Hospital adverse event management system |
-
2021
- 2021-06-10 CN CN202110650184.6A patent/CN113379384A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104732327A (en) * | 2015-01-31 | 2015-06-24 | 付洋 | Network reporting system for medical adverse events in hospital |
| CN105791416A (en) * | 2016-04-13 | 2016-07-20 | 山东省立医院 | Medical device administration event report and safety early warning information orientation transmission system |
| CN105976291A (en) * | 2016-05-30 | 2016-09-28 | 镇江市第人民医院 | Hospital adverse event reporting processing system and hospital adverse event reporting processing method |
| CN112927786A (en) * | 2021-03-15 | 2021-06-08 | 浙江省武义县第一人民医院 | Hospital adverse event management system |
Non-Patent Citations (3)
| Title |
|---|
| 杨静等: "基于医院信息化的医疗不良事件内部报告系统构建", 《上海交通大学学报(医学版)》 * |
| 董云红等: "医疗安全不良事件报告管理系统的设计与临床应用", 《护理管理杂志》 * |
| 雷震: "基于贝叶斯算法的医院不良事件分析系统研究与应用", 《中国优秀硕士学位论文全文数据库医药卫生科技辑》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114145944A (en) * | 2021-10-20 | 2022-03-08 | 赣州市第五人民医院 | Adverse event prompt card and method suitable for nursing station |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8086472B2 (en) | Apparatus and method for managing prescription benefits | |
| US7483908B2 (en) | Context management with audit capability | |
| US8131764B2 (en) | Standing order database search system and method for internet and intranet application | |
| US6363393B1 (en) | Component based object-relational database infrastructure and user interface | |
| JP4963760B2 (en) | Numerous integrated biomedical sources | |
| US20040249676A1 (en) | Management systems and methods | |
| US20040078228A1 (en) | System for monitoring healthcare patient encounter related information | |
| CN110993079A (en) | Medical quality control management platform | |
| US7464043B1 (en) | Computerized method and system for obtaining, storing and accessing medical records | |
| US20090217340A1 (en) | Methods and systems for clinical context management via context injection into components and data | |
| CN115579117A (en) | Data assets system and method of medical data | |
| CN113379384A (en) | Medical event big data platform | |
| Soontornpipit et al. | The study of hospital information systems in the 8th health region | |
| WO2008052093A2 (en) | Method and system for providing storage and retrieval of clinical information | |
| CN112734362A (en) | Method for implementing enterprise management decision supervision operation system | |
| WO2002052483A2 (en) | System and method for integration of health care records, and for a seamless user interface, for an integrated electronic health care information system | |
| US20220148693A1 (en) | Patent-centric health care system | |
| Mahmoud et al. | Information systems technology and healthcare quality improvement | |
| Coleman et al. | Multidimensional analysis: a management tool for monitoring HIPAA compliance and departmental performance | |
| Hamilton | Application layer security requirements of a medical information system | |
| US20170300644A1 (en) | Surveillance information system to facilitate detection and review of potential hipaa violations | |
| Rockoff | The social implications of health care communication systems | |
| US20070174093A1 (en) | Method and system for secure and protected electronic patient tracking | |
| Staccini et al. | Confidentiality issues within a clinical information system: Moving from data-driven to event-driven design | |
| US20130339054A1 (en) | System and method for providing medical information to labor and delivery staff |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210910 |
|
| RJ01 | Rejection of invention patent application after publication |