GB2376760A - Computer system for processing patient information - Google Patents
Computer system for processing patient information Download PDFInfo
- Publication number
- GB2376760A GB2376760A GB0100064A GB0100064A GB2376760A GB 2376760 A GB2376760 A GB 2376760A GB 0100064 A GB0100064 A GB 0100064A GB 0100064 A GB0100064 A GB 0100064A GB 2376760 A GB2376760 A GB 2376760A
- Authority
- GB
- United Kingdom
- Prior art keywords
- details
- database
- database means
- respective patient
- readily accessible
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- 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/60—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 operation of medical equipment or devices
- G16H40/67—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 operation of medical equipment or devices for remote operation
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
A computer system for processing patient information enables efficient handling of the details and treatment of patients in a hospital, clinic or other healthcare facility. In use, the details and treatment of the patients are held on a first database in the form of large multipurpose database tables. This data, which can also be received from other systems or supplementary databases via a first server, is not aggregated, grouped or treated and consists of all type of patient activity and information. In order to reduce the time taken to search and query all patient activity, the details of each respective patient are extracted from the first database into a second database and the details of each respective patient are modified, using stored procedures, into readily accessible information. These stored procedures may include applying grouping fields to each data record to allow queries to focus quickly on pre-defined data tables, or applying user-defined count fields to each data record to allow quick aggregation of values. As the data is extracted from the first database it may undergo further validation checks and certain field values can be amended where errors are known to have occurred. The readily accessible information may then be accessed by an end user using local application software, which is connected over a public network to the second database. In use, local application software uses an Open Database Connectivity (ODBC) connection to couple to the second databases.
Description
<Desc/Clms Page number 1>
METHOD AND APPARATUS FOR PROCESSING
PATIENT INFORMATION
This invention relates to a method and apparatus for processing patient information. Said method and apparatus enabling efficient handling of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility.
Presently, the amount of information that is generated when a patient is treated in a hospital, clinic or other healthcare facility has increased dramatically. Typically, this information may include basic personal details such as name, address and date of birth, along with their previous medical history and results of any diagnostic procedures or tests. In addition, details of all treatment, medication administered or surgical procedures performed will be entered into the medical records of such patient.
In recent years, the detailed medical records of patients in hospitals, clinics or other healthcare facilities have been retained In database packages, held on local servers However, whilst such packages may be adequate for managing day to day patient care, the increasing demands being placed on hospitals, clinics or other healthcare facilities in terms of public accountability mean that the time taken by such packages to process collective details of each patient's medical record can be prohibitive
Mandatory inclusion in recently instigated performance league tables and other clinical indicators, means that collated information as diverse as, for example, average length of stay, average length of waiting time, surgical procedure success rates, average time in theatre for certain procedures, manpower levels, waiting lists and average treatment costing is often required. Clearly, with standard packages, the length of time taken to search
<Desc/Clms Page number 2>
and query the entire database and prepare these reports would be considerable.
It is the object of the present invention to provide a method and apparatus for enabling efficient handling of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility. Such details of a plurality of patients being processed, combined and optimised such that the information can be readily accessed. Such processing may include the steps of, for example, grouping, counting, aggregating and validating, so that large volumes of data can be accessed by local software over, for example, a public network. Such local software configured to efficiently generate remote queries and reports
According to the present invention there ! S provided a method for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by a first server means, comprising the steps of :- extracting said details of each respective patient from said first database means into a second database means, said details of each respective patient being modified, using stored procedures, into readily accessible information; providing user access to said readily accessible information held on said second database means via a second server means, over a public network; and providing local application means connected to said public network for generating remote queries and reports from said readily accessible information.
<Desc/Clms Page number 3>
In a preferred embodiment, said first database means holds all type of patient activity and information. The details of each respective patient being entered either manually into the first database means, or imported from other systems via the first server means. During treatment of each respective patient, the medical records of such patient are continually updated so that, for example, details of any diagnostic procedures or tests, medication administered or surgical procedures performed are retained in said first database means.
Said second database means IS intended as a decision support system, or a data warehouse, which ultimately comprises all types of patient activity as recorded on said first database means, and received from other systems. In use, the second database means may consist of a number of data tables, views of data tables and stored procedures. Such tables and views of tables are created by extracting the data from tables in the first database means using stored procedures. Such stored procedures physically create tables in said second database means, and they also apply numerous processes to the data that is being extracted. These processes permit query design within said second database means that is not possible on the source database, said first database means
Such processes, using stored procedures, may include applying grouping fields to each data record to allow quenes to focus quickly on predefined data sets; applying user defined count fields to said first database table records to allow quick aggregation of values; production of error reports; general cleaning of data and updating records where first database means holds incorrect details ; creation of new record types within said second database means to permit sophisticated quenes that are not available on said first database means and creation of pre-aggregated tables permitting simplified query design and execution
<Desc/Clms Page number 4>
Further preferably, the local application means, for generating remote queries and reports from said second database means, may be provided using a self-executing form-based application. The local application means contains pre-designed queries and reports, all of which are developed to meet the needs of the specific end user. In use, said local application means may use an Open Database Connectivity (ODBC) connection to said second database means.
Also according to the present invention there is provided an apparatus for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, comprising :- first database means, being provided on a first server means, for enabling the storage and access to details of each respective patent held therein; second database means, being provided on a second server means, for enabling the extraction of said details of each respective patient from said first database means, during extraction said details of each respective patient being modified, using stored procedures, into readily accessible information ; and local application means, connected to said second database means over a public network, for enabling the generation of remote queries and reports from said readily accessible information.
Further according to the present invention there is provided a computer program product for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by a first server means, comprising :- computer readable program means for extracting said details of each respective patient from said first database means into a second database
<Desc/Clms Page number 5>
means, said details of each respective patient being modified, using stored procedures, into readily accessible information; computer readable program means for providing user access o said readily accessible information held on said second database means via a second server means, over a public network; and computer readable program means for providing local application means connected to said public network for generating remote queries and reports from said readily accessible information.
The advantages of the present invention are that time taken to search and query all patient activity and information in a hospital, clinic or other healthcare facility, is significantly reduced. Details of each patient being processed, combined and optimised such that the information can be readily accessed. Such processing may include the steps of, for example, grouping, counting, aggregating and validating, so that large volumes of data can be accessed by local software over, for example, a public network.
It will be obvious to those skilled in the art that variations of the present invention are possible, and it is intended that the present invention may be used other than specifically as described herein.
A specific non-limiting embodiment of the invention will be described by way of example and with reference to the accompanying drawings, in which-
Figure 1 illustrates a schematic diagram of the present invention
Figure 2 shows schematically how the present invention may be implemented with the second database means divided into, for example, four separate categories of patient data tables and views of tables.
<Desc/Clms Page number 6>
Figure 3 illustrates how the patient record tables and views of tables may be further divided to provide additional view categories.
Referring now to the drawings, the proposed scheme is illustrated in Figure 1. In the present invention, the first and second database means are provided by two Microsoft SQL Server 7.0 databases, which reside on separate servers. The local application software, being located on the user's personal computer (PC), is created using a self-executing Microsoft Access form-based application.
In use, the first database means consists of patient record views in the form of large multipurpose database tables This data, which may be received from other systems or supplementary databases via the first server means, is not aggregated, grouped or treated, and consists of all type of patient activity and information
The second database means is intended as a decision support system, or a data warehouse, which ultimately comprises all type of patient activity and information as recorded on the first database means, and that received from other systems. As the data is extracted from the first database means into the second database means, it undergoes many validation checks and certain field values are amended where errors are known to have occurred An outcome of this data cleaning is the production of a suite of error reports that may be returned to operational staff for remedial action on the first database means, or Imported to other systems via the first server means.
Tables and views of tables in the second database means are created by running stored procedures against tables and views of tables in the first database means. The results are counted and validated during this process.
Additionally, as the patient details are extracted into the second database means, many grouping categories are inserted into such patient records to
<Desc/Clms Page number 7>
allow large volumes of data to be aggregated into specific levels, which may include, for example, age groups and speciality groups. Also, specific count fields are inserted into such records to allow simple counting of, for example, new day cases or inpatient cases.
The entire cleaning and extraction processes to transfer around one month's worth of admitted patient's details into, for example, eight categories in the second database means takes around two and a half hours at present server usage levels. However, the resultant readily accessible information is a much simplified data set in a usable form that is less susceptible to the errors of everyday operational activities. In particular, the data stored in the second database means is organised and readily available to decision makers and other users.
The local application means of Figure 1 contains pre-designed quenes and reports, all of which may be run without specific user knowledge of Microsoft Access, or of the queries and report design requirements. The local application means may be developed to meet the requirements of specific end users and, as such, the content will vary between users depending on their particular requirements. In the present invention, the local application means uses an Open Database Connectivity (ODBC) connection to couple to the second database means
Figure 2 illustrates schematically how the present invention may be implemented with the second database means divided into, for example, four separate categories of patient data tables and views of tables. These tables and views of tables include patient record tables which contain group and count fields of all type of patient activity and information. Typically, this may include basic personal details such as name, address and date of birth, along with the patient's previous medical history and results of any diagnostic procedures or tests. In addition, details of all treatment, medication
<Desc/Clms Page number 8>
administered or surgical procedures performed will be entered into the medical records via the first database means.
The semi-aggregated tables referred in Figure 2 may be aggregated to specific levels to allow flexible use of such data by managers and other decision makers. Likewise, clinical proforma tables consist of combined data collected from the first database means or other supplementary databases, which is grouped into various count fields to provide summarised clinical information. The reference tables of Figure 2 may include grouped reference data, such as clinical or diagnostic coding.
In a further attempt to fully describe the present invention, the four separate categories of patient data tables and views of tables of Figure 2 can, of course, be further sub-divided into additional tables and views of tables. By way of illustration, Figure 3 shows the patient record tables and views of tables of Figure 2 further divided to provide four additional view categories The purpose of this is to simplify queries and to focus particular queries into the correct data set to use. To illustrate, the four view categories illustrated in Figure 3 are concerned with details of admitted patients for inpatient and day case activity.
Specifically, the admissions tables and views of tables looks only at the consultant, and therefore speciality, under whom the patient is admitted into hospital, which is termed the first consultant episode Irrespective of the number of transfers the patient experiences whilst in hospital, only the one record will be present or counted in these views. By aggregating such data according to the present invention, the local application means can generate remote queries and reports from such pre-grouped and counted data.
Example queries may take the form :- The number of admissions from elective waiting lists
<Desc/Clms Page number 9>
The number of individual patients admitted from a specific GP practice The number of individual patients admitted from a particular area The number of re-admissions Ward of admission
The next table referred to in Figure 3 is termed finished consultant episodes. Each time a patient is transferred between consultants an episode record is created. Therefore, if a patient IS transferred between three different consultants during their stay in hospital, then three records are created in this view; each consultant being identified. Again, example queries using the local application means may take the form :- The numbers of patients under the care of a particular consultant at any time during their stay in hospital Operations performed at any time during a patient's stay in hospital Changes in diagnosis of those requiring episode specific diagnosis such as palliative care during a patient's stay in hospital Health related groupings
The discharge and deaths category of Figure 3 Includes only records for the final episode during the patient's stay in hospital. Hence, the consultant identified here is the discharging consultant or the consultant at the time of death. Example queries may be- Length of stay in hospital Deaths in hospital Time of discharge Post operative length of stay Discharges or deaths by final hospital ward Re-admissions by discharging consultant
<Desc/Clms Page number 10>
The ward activity views are designed specifically to look at ward activity grouped data, and create records for all patients who have been on the ward.
This includes not just those admitted to the ward, or episodes ending on the ward, but also discharges from the ward. Additionally, transfers onto the ward or transfers from the ward who would not otherwise be identified in the other views are grouped. Again, example queries using the local application means may include :- Bed occupancy by ward Daily bed occupancy Ward transfers Ward activity within specific consultant episodes
Various alterations and modifications may be made to the present invention without departing from the scope of the invention For example, although particular embodiments refer to the efficient handling of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, this is in no way intended to be limiting as, in use, any particular group of details, held on the first database means, may be being modified, using stored procedures, into readily accessible information
Claims (27)
- CLAIMS 1. A method for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by a first server means, comprising the steps of: extracting said details of each respective patient from said first database means into a second database means, said details of each respective patient being modified, using stored procedures, into readily accessible information; providing user access to said readily accessible information held on said second database means via a second server means, over a public network; and providing local application means connected to said public network for generating remote queries and reports from said readily accessible information.
- 2. A method as claimed in claim 1, wherein said details of each respective patient are entered either manually into the first database means, or imported from other systems via said first server means.
- 3. A method as claimed in claims 1 or 2, wherein said details of each respective patient include basic personal details such as name, address and date of birth, their previous medical history and results of any diagnostic procedures or tests.
- 4. A method as claimed in any of claims 1 to 3, wherein said details of each respective patient are continually updated during treatment in a hospital, clinic or other healthcare facility, such that details of all treatment and<Desc/Clms Page number 12>medication administered or surgical procedures performed are retained in said first database means.
- 5. A method as claimed in claim 1, wherein said readily accessible information further comprises a plurality of data tables and views of data tables.
- 6. A method as claimed in claim 1, wherein the step of extracting said details of each respective patient from said first database means into a second database means, said details of each respective patient being modified, using stored procedures, into readily accessible information further comprises the step of applying numerous processes to each data record that is being extracted.
- 7. A method as claimed in claim 6, wherein said processes include applying grouping fields to each data record to allow queries to focus quickly on pre-defined data tables.
- 8. A method as claimed in claim 6, wherein said processes include applying user-defined count fields to each data record to allow quick aggregation of values.
- 9. A method as claimed in claim 6, wherein said processes include creating new data record types within said second database means to permit sophisticated queries that are not available on said first database means.
- 10. A method as claimed in claim 6, wherein said processes include applying validation checks to each data record and amending field values where errors are known to have occurred.<Desc/Clms Page number 13>
- 11. A method as claimed in claim 10, wherein if said validation checks do find errors, said second database means produces an error report that may be returned to operational staff for remedial action on the first database means or imported into other systems via the first server means.
- 12. A method as claimed in claim 1, wherein said public network comprises an Open Database Connectivity (ODBC) connection.
- 13. A method as claimed in claim 1, wherein said local application means comprises a self-executing form-based application.
- 14. An apparatus for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, comprising: first database means, being provided on a first server means, for enabling the storage and access to details of each respective patient held therein; second database means, being provided on a second server means, for enabling the extraction of said details of each respective patient from said first database means, during extraction said details of each respective patient being modified, using stored procedures, into readily accessible information; and local application means, connected to said second database means over a public network, for enabling the generation of remote queries and reports from said readily accessible information.
- 15. An apparatus as claimed in claim 14, wherein the details of each respective patient held on first database means may be received from other systems or other supplementary databases via the first server means.<Desc/Clms Page number 14>
- 16. An apparatus as claimed in claim 14, wherein said readily accessible information stored on said second database means further comprises a plurality of data tables and views of data tables.
- 17. An apparatus as claimed in claim 16, wherein said readily accessible information stored on said second database means includes grouping categories inserted in said plurality of data tables and views of data tables to allow large volumes of data to be aggregated into specific levels.
- 18. An apparatus as claimed in claim 16, wherein said readily accessible information stored on said second database means includes user-defined count categories inserted in said plurality of data tables and views of data tables to allow quick aggregation of values.
- 19. An apparatus as claimed in claim 16, wherein said plurality of data tables and views of data tables can be further sub-divided into additional tables and views of tables.
- 20. An apparatus as claimed in claim 14, wherein said local application means comprises a self-executing form-based application.
- 21. An apparatus as claimed in claim 14, wherein said local application means contains pre-designed queries and reports.
- 22. An apparatus as claimed in claim 14, wherein said public network comprises an Open Database Connectivity (ODBC) connection.
- 23. An apparatus as claimed in claim 14, wherein said first server means and said second server means physically reside on separate servers.<Desc/Clms Page number 15>
- 24. A computer program product for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by a first server means, comprising: computer readable program means for extracting said details of each respective patient from said first database means into a second database means, said details of each respective patient being modified, using stored procedures, into readily accessible information; computer readable program means for providing user access to said readily accessible information held on said second database means via a second server means, over a public network; and computer readable program means for providing local application means connected to said public network for generating remote queries and reports from said readily accessible information.
- 25. A method for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by a first server means as herein described.
- 26. An apparatus for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility as described herein with reference to Figures 1 to 3 of the accompanying drawings.
- 27. A computer program product for enabling the efficient processing of the details and treatment of a plurality of patients in a hospital, clinic or other healthcare facility, the details of each respective patient being held on a first database means, with access to said first database means being provided by<Desc/Clms Page number 16>a first server means as described herein with reference to Figures 1 to 3 of the accompanying drawings.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0100064A GB2376760A (en) | 2001-01-03 | 2001-01-03 | Computer system for processing patient information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0100064A GB2376760A (en) | 2001-01-03 | 2001-01-03 | Computer system for processing patient information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| GB0100064D0 GB0100064D0 (en) | 2001-02-14 |
| GB2376760A true GB2376760A (en) | 2002-12-24 |
Family
ID=9906161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB0100064A Withdrawn GB2376760A (en) | 2001-01-03 | 2001-01-03 | Computer system for processing patient information |
Country Status (1)
| Country | Link |
|---|---|
| GB (1) | GB2376760A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007107726A1 (en) * | 2006-03-18 | 2007-09-27 | Isoft Applications Limited | Data input method |
| CN102646149A (en) * | 2011-02-18 | 2012-08-22 | 上海理工大学 | Information data management method of patient suffering from muscle dysfunction |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5903889A (en) * | 1997-06-09 | 1999-05-11 | Telaric, Inc. | System and method for translating, collecting and archiving patient records |
| WO1999063886A1 (en) * | 1998-06-12 | 1999-12-16 | Conception Technology Incorporated | Information management system for personal health digitizers |
| WO2000057339A2 (en) * | 1999-03-24 | 2000-09-28 | Koninklijke Philips Electronics N.V. | System and method for presentation of computerized patient records across a network |
-
2001
- 2001-01-03 GB GB0100064A patent/GB2376760A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5903889A (en) * | 1997-06-09 | 1999-05-11 | Telaric, Inc. | System and method for translating, collecting and archiving patient records |
| WO1999063886A1 (en) * | 1998-06-12 | 1999-12-16 | Conception Technology Incorporated | Information management system for personal health digitizers |
| WO2000057339A2 (en) * | 1999-03-24 | 2000-09-28 | Koninklijke Philips Electronics N.V. | System and method for presentation of computerized patient records across a network |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007107726A1 (en) * | 2006-03-18 | 2007-09-27 | Isoft Applications Limited | Data input method |
| AU2007228610B2 (en) * | 2006-03-18 | 2011-10-20 | Isoft Applications Limited | Data input method |
| CN102646149A (en) * | 2011-02-18 | 2012-08-22 | 上海理工大学 | Information data management method of patient suffering from muscle dysfunction |
Also Published As
| Publication number | Publication date |
|---|---|
| GB0100064D0 (en) | 2001-02-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8032394B1 (en) | System and method for a patient-specific and optimization of medical therapy by simultaneous symbolic reasoning in all clinical dimensions | |
| US8983951B2 (en) | Techniques for relating data in healthcare databases | |
| Irving et al. | Haloperidol versus placebo for schizophrenia | |
| US20020082868A1 (en) | Systems, methods and computer program products for creating and maintaining electronic medical records | |
| US8335698B2 (en) | Optimizing cluster based cohorts to support advanced analytics | |
| US20090024414A1 (en) | Analytical methods and software product for automated health care information systems | |
| US20010025246A1 (en) | System and method for providing medication management | |
| Singh et al. | Factors to overcoming barriers affecting electronic medical record usage by physicians | |
| Khodambashi | Lean analysis of an intra-operating management process-identifying opportunities for improvement in health information systems | |
| WO2022229964A1 (en) | Method of generating a diseases database, usage of the diseases database, and system therefor | |
| Altmann et al. | GTDS--a tool for tumor registries to support shared patient care. | |
| US20160378922A1 (en) | Methods and apparatuses for electronically documenting a visit of a patient | |
| CN114141340A (en) | Method, device and equipment for reasonably controlling cost in medical process | |
| Pearce | Electronic medical records-where to from here? | |
| GB2376760A (en) | Computer system for processing patient information | |
| EP2320342A1 (en) | System and method for creating data links between diagnostic and prescription information records | |
| McDonald et al. | Data standards in health care | |
| Scott et al. | Using bar-code technology to capture clinical intervention data in a hospital with a stand-alone pharmacy computer system | |
| KR20050033274A (en) | Hospital management system for providing a variaty of analyzing service | |
| Johnson et al. | Generic database design for patient management information. | |
| CN110379478A (en) | Prescription intelligently comments on system | |
| Pates et al. | Adding value to clinical data by linkage to a public death registry | |
| Krastev et al. | Common Data Model for Interoperability of Observational Health Data: Bulgarian Diabetes Register Pharmacology Case Study | |
| Cui | Ontology-guided health information extraction, organization, and exploration | |
| Soteriades et al. | Electronic health record diagnosis tool and a cross reference between coding standards |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |