CN107945853B - Medical quality reporting system based on metadata - Google Patents
Medical quality reporting system based on metadata Download PDFInfo
- Publication number
- CN107945853B CN107945853B CN201610881241.0A CN201610881241A CN107945853B CN 107945853 B CN107945853 B CN 107945853B CN 201610881241 A CN201610881241 A CN 201610881241A CN 107945853 B CN107945853 B CN 107945853B
- Authority
- CN
- China
- Prior art keywords
- description
- data
- named
- name
- user
- 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.)
- Active
Links
- 238000012800 visualization Methods 0.000 claims abstract description 15
- 238000012550 audit Methods 0.000 claims description 10
- 238000007726 management method Methods 0.000 claims description 9
- 230000000007 visual effect Effects 0.000 claims description 6
- 238000004458 analytical method Methods 0.000 claims description 5
- 238000013524 data verification Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 238000004364 calculation method Methods 0.000 claims description 3
- 238000004140 cleaning Methods 0.000 claims description 3
- 238000003032 molecular docking Methods 0.000 claims description 3
- 238000000034 method Methods 0.000 claims description 2
- 238000012986 modification Methods 0.000 claims description 2
- 230000004048 modification Effects 0.000 claims description 2
- 238000012795 verification Methods 0.000 claims 7
- 238000007781 pre-processing Methods 0.000 claims 4
- 238000009877 rendering Methods 0.000 claims 3
- 238000009825 accumulation Methods 0.000 claims 2
- 238000012937 correction Methods 0.000 claims 2
- 230000000694 effects Effects 0.000 claims 2
- 238000001914 filtration Methods 0.000 claims 2
- 238000012805 post-processing Methods 0.000 claims 2
- 238000007792 addition Methods 0.000 claims 1
- 230000001174 ascending effect Effects 0.000 claims 1
- 238000013479 data entry Methods 0.000 claims 1
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 230000002452 interceptive effect Effects 0.000 claims 1
- 230000003442 weekly effect Effects 0.000 claims 1
- 238000003908 quality control method Methods 0.000 abstract description 8
- 230000009286 beneficial effect Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000011161 development Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 2
- 206010002091 Anaesthesia Diseases 0.000 description 1
- 230000037005 anaesthesia Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Landscapes
- Medical Treatment And Welfare Office Work (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to the medical field, in particular to a medical quality reporting system based on metadata, which comprises: the user unit is used for inputting and/or inquiring medical quality information by platform users, hospital users and subject users; the reporting unit is used for uploading the medical quality information to a database unit according to the reporting mode described by the metadata; the query unit is used for querying the medical quality information by the user unit; and the database unit is used for storing the medical quality information. The medical quality reporting system provided by the invention can flexibly select a medical quality reporting mode, can flexibly set a reporting professional project, does not need secondary development, and is beneficial to inquiring and analyzing medical quality data by multiple users and adapting to the fields of rapidly developing medical disciplines and medical quality control by an agile visualization technology.
Description
Technical Field
The invention relates to the field of medical treatment, in particular to a medical treatment quality reporting system based on metadata.
Background
In 2009, the former ministry of health promulgated "medical quality control center management approach" (wei-medical administration No. [2009]51 "), in which the medical quality control center was required to establish a data database of relevant specialties. Currently, the medical quality control center mobile phone professional relevant medical quality information data of each hospital is generally processed by paper filling, mail reporting or investigation. A small part of medical quality control centers establish relevant medical quality control indexes of various hospitals and specialties of a network direct reporting system mobile phone. In 2015, the national health care committee released six major medical quality control indexes such as anesthesia, and due to the differences among major properties, the medical quality control indexes of each major were different.
The mobile phone information is difficult to gather and sort in a paper or mail reporting mode, and effective analysis and utilization can be carried out only by sorting and inputting the data by special arrangement personnel.
Because the medical quality control indexes of all the professions are different, the medical professions set by all the hospitals are also different, and the network with relatively fixed collected data items is difficult to cover all the hospitals and all the professions, which is not beneficial to effectively managing and utilizing the data of each profession.
Moreover, medical science is a rapidly-developing subject, and from 2009 to 2015, medical quality control indexes are continuously changed, and the change of the indexes needs large-scale modification of an information system, particularly an acquisition module, so that the workload is high and tedious. Therefore, the solidified network direct reporting system is not suitable for rapidly developing medical disciplines.
Disclosure of Invention
The invention aims to overcome the defects in the prior art and provide a medical quality reporting system which can flexibly set reporting items and flexibly select reporting modes and has a visual analysis function. In order to achieve the above purpose, the invention provides the following technical scheme:
a metadata-based medical quality reporting system, comprising:
the user unit is used for inputting and/or inquiring medical quality information by platform users, hospital users and subject users;
the reporting unit is used for uploading the medical quality information to a database unit according to the reporting mode described by the metadata;
the query unit is used for querying the medical quality information by the user unit;
and the database unit is used for storing the medical quality information.
Further, the user unit further comprises a platform management unit for managing medical institutions and medical specialties; the management comprises the following steps: new, modified, deleted and queried.
Further, the metadata includes metadata describing data types, input manners, processing manners, storage manners, presentation manners, data sources, thresholds, indexing manners, sorting manners, audit decisions, and clinical data calculation manners.
Further, the reporting mode includes data filling, interface docking and template reporting.
And further, reporting the medical quality information according to discipline specialties.
Furthermore, each specialty corresponds to a set of metadata, and the network report form, the report data interface and the report template of each subject specialty are generated according to the metadata of the specialty.
Furthermore, the query unit further comprises an agile visualization module for completing the visualization display and analysis of the medical quality information. The agility visualization module generates an agility visualization template, the agility visualization template comprises a report and/or a chart, and data can be visually displayed from any dimensionality to help health administration departments, hospitals and subjects to inquire and analyze medical quality data.
Furthermore, the user unit further comprises an application interface module, which is used for binding the platform user, the hospital user and the subject user with a mobile application account and logging in from a mobile application terminal.
Preferably, the mobile application is WeChat, and the user reports and queries the medical quality information through the WeChat.
Furthermore, the medical quality information reported by the reporting unit is subjected to data cleaning and data verification and then is stored in the database unit.
Compared with the prior art, the invention has the beneficial effects that:
the medical quality reporting system based on the metadata can flexibly select a medical quality reporting mode, can flexibly set a reporting professional project, does not need secondary development, and is beneficial to inquiring and analyzing medical quality data by multiple users and adapting to the fields of rapidly developing medical disciplines and medical quality control by an agile visualization technology.
Description of the drawings:
fig. 1 is a structure diagram of a metadata-based medical quality reporting system according to the present invention;
FIG. 2 is a schematic diagram of the data processing of the system;
the labels in the figure are: 01-user unit, 02-reporting unit, 03-database unit, 04 query unit.
Detailed Description
The present invention will be described in further detail with reference to test examples and specific embodiments. It should be understood that the scope of the above-described subject matter is not limited to the following examples, and any techniques implemented based on the disclosure of the present invention are within the scope of the present invention.
Example 1
A metadata-based medical quality reporting system, as shown in fig. 1, includes:
the user unit 01 is used for inputting and/or inquiring medical quality information by platform users, hospital users and subject users;
the reporting unit 02 uploads the medical quality information to a database unit according to the reporting mode described by the metadata;
the query unit 04 is used for querying the medical quality information by the user unit;
and the database unit 03 is used for storing the medical quality information.
Further, the user unit 01 further comprises a platform management unit for managing medical institutions and medical specialties; the management comprises the following steps: new, modified, deleted and queried. The platform users mainly belong to medical and health management departments, the hospital users mainly belong to various medical institutions, and the subject users mainly belong to professional medical staff of various subjects in the hospital. The platform user manages medical institution information and subject professional information through the platform management unit; the hospital user manages subject professional information needing to be reported through the platform; the subject specialty information set by the hospital user has unique correspondence in the subject specialty set by the platform user.
Further, a set of metadata includes three aspects, namely, aggregate metadata, which corresponds to a table in the database and describes the overall attributes of the data aggregate, and field metadata, which corresponds to a field in the database and describes the attributes of the individual data. The last aspect is a dictionary bound to field metadata, which is a two-dimensional array describing the name (name) and corresponding value (value) of the option. The collection metadata and the field metadata are distinguished according to the described objects, namely, the collection metadata is used for describing the attributes of the data collection, and the field metadata is used for describing the attributes of the data field.
Further, the metadata includes metadata describing data types, input manners, processing manners, storage manners, presentation manners, data sources, thresholds, indexing manners, sorting manners, audit decisions, and clinical data calculation manners. Table 1 lists the basic metadata information used by the medical quality reporting system.
Table 1 basic metadata information table
Further, the reporting mode includes data filling, interface docking and template reporting. The hospital user and the subject user can arbitrarily select the reporting mode to finish the reporting of the medical quality information. The data is filled, namely a report form is dynamically generated according to the set of metadata description corresponding to the discipline specialty, and the hospital user or the discipline user reports the medical quality information through the filled report form. The reporting form has flexibility, and reporting items can be newly added, deleted or modified. The interface is connected with the medical quality reporting system, namely the medical quality reporting system is connected with the medical institution system, and the medical institution system sends reported medical quality data to the medical quality reporting system at regular time. And the template reporting means that the reporting unit provides an Excel reporting template for a hospital user or a subject user to download and fill in, and the template is uploaded after the completion of the filling in to complete the medical quality reporting. The template reporting provides a reporting mode for hospitals with bad network environment, and for hospitals without networks, the templates can be copied to places with networks to complete quality reporting and submitting after being filled in.
And further, reporting the medical quality information according to discipline specialties.
Furthermore, each discipline corresponds to a set of metadata, and the network report form, the report data interface and the report template of each discipline are generated according to the metadata of the discipline.
Further, the query unit 04 further includes an agile visualization module, which is used for completing the visualization display and analysis of the medical quality information. The agile visualization module can perform visualization display on data from any dimensionality by using an agile business intelligence technology, and help health competent departments, hospitals and subjects to inquire and analyze medical quality data. And the platform users, the hospital users and the subject users view the visual display templates generated by the corresponding visual templates according to the permission and the parameters configured by the system. The parameters include time, area names, subject identification, hospital identification, professional identification, and index identification. And the user enters the corresponding visual display template through the permission and the parameters configured by the system, and checks the required medical quality information as required. The visual display template comprises report display and chart display.
Further, the user unit 01 further includes an application interface module, which is used for binding a mobile application account by the platform user, the hospital user, and the subject user, and logging in from a mobile application terminal.
Preferably, the mobile application is WeChat.
Further, the user reports and queries the medical quality information through WeChat.
Further, as shown in fig. 2, the medical quality information reported by the reporting unit is subjected to data cleaning and data verification, and then is stored in the database unit.
Claims (9)
1. A medical quality reporting system based on metadata is characterized by comprising:
the user unit is used for inputting and/or inquiring medical quality information by platform users, hospital users and subject users;
the reporting unit is used for uploading the medical quality information to a database unit according to the reporting mode described by the metadata;
the query unit is used for querying the medical quality information by the user unit;
the database unit is used for storing the medical quality information;
the metadata describes data types, input modes, processing modes, storage modes, presentation modes, data sources, threshold values, index modes, sorting modes, auditing judgment and clinical data calculation modes,
the basic metadata information used by the medical quality reporting system comprises:
a description named < bind specialties > is < specialties to which the metadata set belongs >;
a description with the name < data set name > is < meaning that the data set represents >;
the description named < identification > is the unique English identification of < metadata set, and cannot contain space and special characters >;
the description named as < version number > is < version number of metadata set, once the metadata set information itself changes, the version number will automatically increase, which is convenient for distinguishing the version of data >;
the description named as a storage mode is iterative update or incremental accumulation, the iterative update represents that after data is recorded for the first time, subsequent recording is always updated on the basis of the first time, and the incremental accumulation represents that one piece of data is inserted into the database every time the data is newly added;
a description named < collection frequency > is < yearly, monthly, weekly, daily >;
a description named < time to delay period > is < set time to delay range >;
the description named < enable notification or not > is < if turned on, notification will be made if the data triggers a threshold, notification will be processed according to type >;
the description named as the notification mode is < including three types of short message, mail and WeChat, or any combination type, short message notification, the telephone number for filling in and receiving notification, and mail for filling in and receiving notification >;
the description named as < notify message or mail > is < record message or mail address needed to be notified >;
the description of the name of the user role authority white list is that the authority corresponding to the adding, deleting, modifying and checking is associated with the role, if the white list is set, other user roles are ignored, only the white list role has the corresponding authority, and meanwhile, the black list cannot be set >;
the description of the name of the user role authority blacklist is that the authority corresponding to the addition, deletion, modification and check is associated with the role, if the blacklist is set, other roles except the blacklist all have the authority, and meanwhile, a white list cannot be set >;
the description named as < user role data filtering script > is < when the user inquires data, different data filtering conditions are set corresponding to different roles >;
the description named as the < newly added preprocessing script > is < the script which needs to be executed when the user newly adds data and enters a form page >;
the description named as < newly added post-processing script > is < script to be executed when a user newly adds data and submits a form page >;
the description named as < update preprocessing script > is < script to be executed when a user updates data, entering a form page >;
the description named as < update post-processing script > is < script to be executed when a user adds new data, a form is submitted >;
a description named < view preprocessing script > is < script to be executed when rendering data >;
the description of the name < preprocessing script of list > is < script to be called when rendering list data, to process data >;
the description named < metadata classification > is a field classification list required for definition, and when a form is dynamically rendered, a user input area is rendered according to classification >;
a specification named < flow class data > is a < system reserved field for determining whether the set of metadata is allowed to be modified >;
the description named as < new button text > is < text which needs to be displayed by the new data button and is defaulted as new >;
a description named < update button text > is < text that the update data button needs to display, default to update >;
a description named < view button text > is < text that needs to be displayed by view data button, and is viewed by default >;
a description named < delete button text > is < text to be displayed for deleting data button, and default is delete >;
the description named as < enable distributed storage > is a field reserved for the system, and when the system performs storage distributed expansion, whether distributed storage is adopted or not can be set for a data set as required >;
a description named < audit enabled > < data audit flow started >;
the description named as < audit user list > is < array, user list needing to participate in audit is added according to the flow sequence >;
a description named < creator only update > < if set to yes, only the user who created the data can update or delete the data >;
a description of the name < creator update exception role > < if an exception is set, the corresponding role has the authority to update and delete data >;
the description of the name < whether draft > is stored as draft so that the draft metadata will not be valid for the next continued editing >;
the names and corresponding descriptions of field metadata include:
a description of the name < chinese name > < simultaneous for display on the user input interface >;
the description named as < identification > is < unique English identification, and cannot contain special characters >;
a description named < description > is < suggestive text displayed on the user input interface >;
a description named < group id > is < group to which the metadata belongs in the metadata set >;
the description named as < data type > is < including character string, number, date, boolean, dictionary, file, array, object types, different types of data, corresponding metadata characteristics are different >;
a description of the name < query condition > is < whether or not it is displayed in the data list as a query condition >;
the description named < render index > is < order of dataforms when dynamic rendering is performed >;
the description of the name < whether to index > is < whether to serve as the index of the database, and the index can accelerate the search speed of the data >;
the description named as 'ascending sort' is a sort mode of 'index', and the description is sorted in sequence when the system is started, and sorted in descending order when the system is not started, and is set to be effective after the index is set;
the description named as the hash index is the hash index which is set to take effect after the index is set, and the hash index has higher speed when being accurately inquired >;
a description named < unique > is < cannot be repeated throughout the data set value >;
a description named < full-text index > < enter full-text index library >;
a description of the name < fill or not > is < if set to fill, null verification would be performed at the user input interface >;
a description of the name < list display > is < whether the field is displayed in the data table list >;
a description named < trigger script > is < trigger script after the user completes the input and focus is moved away >;
the description named as < trigger script content > is < script content to be executed, the script adopts JS, data is completely controlled through the script, and meanwhile interactive operation is carried out through the script and other fields >;
the description of the name < encryption or not > is that whether the content corresponding to the field needs to be encrypted for storage or not, and the field set to be encrypted cannot become an index and cannot participate in searching >;
a description with the name of < default value > is < default value of the field under the condition that the user does not input, if the field is of date type, 0 is filled in to represent the current time, and the scope correction time can be filled in, see date type description >;
a description of the name < enable or disable remark > is < enter with remark when the limitation of the field itself cannot satisfy the data entry of the system >;
the description named as < enable or disable constraint > is that < constraint is used for data verification between different tables, conventional verification can be directly set through constraint, and responsible for verification can be set through a trigger >;
the specification named < constraint operator > is < operator required to participate in constraint operations >;
a description named < constraint table > < target table required to participate in verification >;
a description named < constraint field > < target field required to participate in verification >;
the description with the name of < user role authority white list > is < corresponding authority for editing and checking, and is associated with roles, if the white list is set, other user roles are ignored, only the white list role has corresponding authority, and meanwhile, the black list cannot be set >;
the description with the name of < user role authority blacklist > is < corresponding authority for editing and checking, and is associated with the role, if the blacklist is set, other roles except the blacklist all have the authority, and meanwhile, a white list cannot be set >;
a description named < enter rule > is < add, update, or view, or any combination >;
the description named as < flow class field > is a reserved field of the system, and is used for judging whether the field allows the user to define completely or not;
wherein the name and corresponding description of the string type includes:
a description named < max length > is < max input length >;
a description named < regular expression > < rule verification for input content >;
a description named < regular error prompt > is < prompt to be displayed when verification fails >;
a specification named < render type > is < single-line or multi-line, rendered with a single-line text box or multi-line text box >;
wherein the names of the numeric types and the corresponding descriptions include:
a description named < min > < fillable min >;
a description named < max > < max-fillable >;
a description named < threshold or not > is used in the threshold rule of the other field after < set as threshold parameter >;
a description named < threshold rule > is < warning value of data >;
wherein the name and corresponding description of the date type includes:
a description named < enter mode > is < time and/or date >;
a description named < format > is < format of date display >;
the description named as < enter minimum range correction > is < input value and unit, no limitation is imposed if filling is not carried out, filling 0 represents the current time, -1d represents the previous day, 1d represents the next day, 1m represents the next month, and 1y represents the next year >;
a specification with the name < associated constraint field name > is < field representation requiring constraint, must exist in the table, otherwise the constraint does not take effect >;
a description named < constraint type > is < begin or end >;
wherein the dictionary type names and corresponding descriptions include:
the description with the name < dictionary identification > is < dictionary identification needing to be associated, and selection is carried out through a pull-down menu >;
wherein the name and corresponding description of the boolean type includes:
the description named as < presentation mode > is < including a pull-down menu form, a check box form, and a button form >;
wherein the name and corresponding description of the object type includes:
the description named < metadata set identification > is < object metadata set identification needing to be associated, selected through a pull-down menu >;
the name < object storage mode > is < array or single, and the object corresponding to the field is stored in array mode or single mode >;
wherein the name and corresponding description of the default metadata comprises:
a description named < data number > is < data-corresponding unique number >;
a description named < update time > is < time recorded when data changes occur >;
a description named < creation time > is < time created at the time of data creation, which will not change after creation >;
a description of the name < draft or not > is < temporarily store data as draft >;
the description named as < historical auditor state > is < object array, including whether audit is passed, auditor and remark >;
the description named as < historical audit role state > indicates that < when audit is required, a certain role can be set as an auditor, and users with the role can perform audit >.
2. The medical quality reporting system of claim 1, wherein the subscriber unit comprises
The platform management unit is used for managing medical institutions and medical specialties; the management comprises the following steps: new, modified, deleted and queried.
3. The medical quality reporting system of claim 1, wherein the reporting modes include data filling, interface docking, and template reporting.
4. The medical quality reporting system of claim 3, wherein the medical quality information is reported according to disciplines.
5. The medical quality reporting system of claim 4, wherein the web report form, the report data interface, and the report template for each discipline specialty are generated based on the specialty's metadata.
6. The medical quality reporting system of claim 1, wherein the query unit further comprises an agile visualization module for performing a visual display and analysis of the medical quality information.
7. The medical quality reporting system of claim 6, wherein the agility visualization module generates an agility visualization template, the agility visualization template comprising a report and/or a chart.
8. The medical quality reporting system of claim 1, wherein the user unit further comprises an application interface module, which is configured to bind the platform user, the hospital user, and the discipline user to a mobile application account, log in from a mobile application terminal, and complete medical quality reporting and/or querying.
9. The medical quality reporting system of claim 1, wherein the medical quality information reported by the reporting unit is subjected to data cleaning and data verification and then stored in the database unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610881241.0A CN107945853B (en) | 2016-10-09 | 2016-10-09 | Medical quality reporting system based on metadata |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610881241.0A CN107945853B (en) | 2016-10-09 | 2016-10-09 | Medical quality reporting system based on metadata |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107945853A CN107945853A (en) | 2018-04-20 |
| CN107945853B true CN107945853B (en) | 2022-02-18 |
Family
ID=61928129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610881241.0A Active CN107945853B (en) | 2016-10-09 | 2016-10-09 | Medical quality reporting system based on metadata |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107945853B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109325076B (en) * | 2018-06-07 | 2020-03-27 | 北京百度网讯科技有限公司 | Data management method and device in Internet of things, computer device and readable medium |
| CN110795448B (en) * | 2020-01-03 | 2020-04-07 | 四川大学华西医院 | Metadata management method and device and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101661508A (en) * | 2009-09-29 | 2010-03-03 | 金蝶软件（中国）有限公司 | Method for generating memu for multi-technology platform and device thereof |
| CN101719119A (en) * | 2009-11-18 | 2010-06-02 | 上海众恒信息产业有限公司 | Report management system and method |
| CN104899194A (en) * | 2014-01-09 | 2015-09-09 | 武汉联影医疗科技有限公司 | Creating method of medical report on the basis of HTML (Hypertext Markup Language) 5 |
| CN105825046A (en) * | 2016-03-13 | 2016-08-03 | 冯贵良 | Medical data collecting and processing method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130290022A1 (en) * | 2012-04-27 | 2013-10-31 | Netspective Communications Llc | System and method for creating metadata-based natural language processing capabilities |
| CN103530524A (en) * | 2013-10-24 | 2014-01-22 | 徐州通软计算机系统集成有限公司 | Medical information intelligent data platform, use method and application thereof |
-
2016
- 2016-10-09 CN CN201610881241.0A patent/CN107945853B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101661508A (en) * | 2009-09-29 | 2010-03-03 | 金蝶软件（中国）有限公司 | Method for generating memu for multi-technology platform and device thereof |
| CN101719119A (en) * | 2009-11-18 | 2010-06-02 | 上海众恒信息产业有限公司 | Report management system and method |
| CN104899194A (en) * | 2014-01-09 | 2015-09-09 | 武汉联影医疗科技有限公司 | Creating method of medical report on the basis of HTML (Hypertext Markup Language) 5 |
| CN105825046A (en) * | 2016-03-13 | 2016-08-03 | 冯贵良 | Medical data collecting and processing method and device |
Non-Patent Citations (2)
| Title |
|---|
| "医院开发质控信息平台实践探讨";陈露等;《中国数字医学》;20141031;第9卷(第10期);摘要，正文第1-3节 * |
| "省级医疗质量管理与控制信息系统设计";严莉萌等;《解放军医院管理杂志》;20150930;第22卷(第9期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107945853A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230244858A1 (en) | Systems and methods for annotating and linking electronic documents | |
| CN105765559B (en) | Interactive case management system | |
| US11430078B2 (en) | Management systems and methods for claim-based patent analysis | |
| CN110119395B (en) | Method for realizing association processing of data standard and data quality based on metadata in big data management | |
| US9798813B2 (en) | Extensible person container | |
| CN111274294B (en) | Universal distributed heterogeneous data integrated logic convergence organization, release and service method and system | |
| CN115757689A (en) | Information query system, method and equipment | |
| US20040083422A1 (en) | System and method for automatically generating patent analysis reports | |
| CN115579117A (en) | Data assets system and method of medical data | |
| CN107945853B (en) | Medical quality reporting system based on metadata | |
| US11636162B2 (en) | Multi-database document search system architecture | |
| CN107680690B (en) | Clinical information system based on metadata | |
| CN110337648B (en) | System and method for efficiently distributing alert messages | |
| CN106156459A (en) | A kind of management system of ophthalmologic examination report | |
| Niu | Recordkeeping metadata and archival description: a revisit | |
| CN108205564B (en) | Knowledge system construction method and system | |
| JP2011243066A (en) | Electronic document management device, display method, display program and record medium | |
| US8799326B2 (en) | System for managing electronically stored information | |
| Santonastaso et al. | An Exploratory Study of the Digital Competences of Italian Accountants: Some Preliminary Results | |
| Graën et al. | Swissdox@ LiRI–a large database of media articles made accessible to researchers | |
| Li et al. | Curating the Chinese ancient book catalogs: Leveraging the dual roles of humanities scholars as experts and users in collaborative practice | |
| Kahvedžić | Digital forensics and the DSAR effect | |
| Beaver | Survey Data Cleaning Guidelines:(SPSS and Stata) | |
| Osborne et al. | Archiving, editing, and reading on the AustESE Workbench: Assembling and theorizing an ontology-based electronic scholarly edition of Joseph Furphy’s Such is Life | |
| Hill | What’s in a name? Prototyping a name authority service for UK repositories |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A metadata based medical quality reporting system Granted publication date: 20220218 Pledgee: Chengdu small business financing Company Limited by Guarantee Pledgor: SICHUAN SMART-MEDICINE TECHNOLOGY Co.,Ltd. Registration number: Y2024980025139 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |