JoVE Logo

로그인

JoVE 비디오를 활용하시려면 도서관을 통한 기관 구독이 필요합니다. 전체 비디오를 보시려면 로그인하거나 무료 트라이얼을 시작하세요.

기사 소개

  • 요약
  • 초록
  • 서문
  • 프로토콜
  • 결과
  • 토론
  • 공개
  • 감사의 말
  • 자료
  • 참고문헌
  • 재인쇄 및 허가

요약

TBase combines an electronic health record with an innovative research database for kidney transplant recipients. TBase is built upon an in-memory database platform, connected to different hospital systems, and used for regular outpatient care. It automatically integrates all relevant clinical data including transplantation-specific data creating a unique research database.

초록

TBase is an electronic health record (EHR) for kidney transplant recipients (KTR) combining automated data entry of key clinical data (e.g., laboratory values, medical reports, radiology and pathology data) via standardized interfaces with manual data entry during routine treatment (e.g., clinical notes, medication list, and transplantation data). By this means, a comprehensive database for KTR is created with benefits for routine clinical care and research. It enables both easy everyday clinical use and quick access for research questions with highest data quality. This is achieved by the concept of data validation in clinical routine in which clinical users and patients have to rely on correct data for treatment and medication plans and thereby validate and correct the clinical data in their daily practice. This EHR is tailored for the needs of transplant outpatient care and proved its clinical utility for more than 20 years at Charité - Universitätsmedizin Berlin. It facilitates efficient routine work with well-structured, comprehensive long-term data and allows their easy use for clinical research. To this point, its functionality covers automated transmission of routine data via standardized interfaces from different hospital information systems, availability of transplant-specific data, a medication list with an integrated check for drug-drug interactions, and semi-automated generation of medical reports among others. Key elements of the latest reengineering are a robust privacy-by-design concept, modularity, and hence portability into other clinical contexts as well as usability and platform independence enabled by HTML5 (Hypertext Markup Language) based responsive web design. This allows fast and easy scalability into other disease areas and other university hospitals. The comprehensive long-term datasets are the basis for the investigation of Machine Learning algorithms, and the modular structure allows to rapidly implement these into clinical care. Patient reported data and telemedicine services are integrated into TBase in order to meet future needs of the patients. These novel features aim to improve clinical care as well as to create new research options and therapeutic interventions.

서문

Motivation for an integrated electronic health record and research database
Clinical research is based on the availability of high-quality data, regardless of whether classical statistical methods or Machine Learning (ML) techniques are used for analysis1,2. In addition to routine data (e.g., demographic, laboratory, and medication data), domain-specific data (e.g., transplantation-relevant data) are required with high granularity3,4. However, routine care at many university hospitals is performed with hospital information systems (HIS) that neither allow for systematic collection of research-specific data nor for easy data extraction of routine data5,6,7. As a result, clinical researchers create specific research databases, which have a variety of problems including complex process of setting up a database, manual data entry, data protection issues, and long-term maintenance (Table 1). Limited amount of data, missing data, and inconsistencies are a major problem for clinical research in general and impede the use of ML technologies8,9,10,11,12,13. These standalone research databases are usually focused on certain disease or patient aspects, not connected to other databases, and often discontinued after a certain period, resulting in inaccessible "data silos". Ultimately, high-quality, long-term data on various disease aspects are sparse. In the era of digital medicine there is an increasing need for a comprehensive electronic health record (EHR)7,14,15, which enables easy documentation of domain-specific data and automated collection of routine data from the systems of inpatient and outpatient care.

These general considerations apply to transplantation medicine as well16. Hence, a complete documentation of the patient's medical history including all inpatient and outpatient treatments, clinical routine data as well as transplantation-specific data is necessary for successful follow-up care17,18. Since ordinary HIS are static and focused on inpatient treatment, they cannot integrate transplantation-specific data, such as donor data, cold ischemia times, and human leukocyte antigens (HLA) data. However, these data are a basic prerequisite for transplantation research19,20,21,22 as well as from long-term clinical care. While the initial hospital stay usually is only 1-2 weeks and processes as well as early outcomes after kidney transplantation are comparable between many transplant centers, lifelong post-transplant care is complicated and lacks a common structured approach. This motivates an integrated EHR and research database to capture the lifelong post-transplant patient journey.23

In order to integrate these functionalities for routine care and research of KTR, an EHR named "TBase" was developed with the idea that the routine use for post-transplant care will create a unique research database with highest data quality (Table 2).

Design and Architecture
TBase is based on a typical client-server architecture. For development, the components and tools of SAP High Performance Analytic Appliance extended application advanced (SAP HANA XSA) were used. Based on the latest Hypertext Markup Language 5 (HTML5) web-technologies the EHR has been developed and tested for the Google Chrome Engine. This web engine is used by Chrome and the Microsoft Edge Browser and allows to use the EHR in the most frequently used web browsers24 without the need for local installation. The applied technology enables a responsive web design and allows the web-based EHR to be used on all devices (PC, tablet, smartphone). The innovative high-performance development platform is composed of various components (Web IDE, UI5 and HANA DB) and has enabled us to rapidly implement the EHR project TBase with state-of-the-art software tools (Figure 1).

For the representation of patient data, a simple table structure was implemented for an intuitive and self-explanatory design of the EHR. For example, the patient table with the PatientID as the primary key is at the center of the table structure. Almost all tables (except individual sub-tables) are connected to this central table through PatientID (Figure 2).

Figure 3 shows part of TBase's table structure and the data types used in greater detail. The end user can access the data fields via graphical user interface (GUI), for which an example is shown in Figure 4.

This EHR contains all current patient data and is used for routine outpatient care. Important routine clinical data (e.g., laboratory data, medical results, radiology, microbiology, virology and pathology data, hospital data, etc.) are directly imported into TBase via standardized interfaces (e.g., on the basis of Health Level Seven (HL7) - a standard for digital communication in the healthcare sector25). Transplant-specific data such as cold ischemia times, donor data, HLA data as well as follow-up notes, vital signs, medical reports and the medication list are entered by the users via GUI into the EHR. Before data are transferred to the database, an automated plausibility check is performed for prompt detection of erroneous data entry providing the option to correct immediately. In addition, data validation takes part during clinical routine in which clinical users routinely write reports and letters to patients and physicians. These letters must provide correct data (e.g., on medication, lab values and clinical remarks) for further treatment and medication plans. As a consequence physicians and patients constantly validate and correct the clinical data in their daily practice, a process resulting in high data quality. If data are entered via application programming interfaces (API) or other interfaces, plausibility checks are performed in the backend similarly to the plausibility checks in the frontend.

Frontend (GUI)
To implement the frontend, the UI5 Framework is used. This framework provides an extensive library for frontend elements as well as a variety of additional features such as multilingualism and graphical libraries for data visualization. Currently, TBase frontend elements are displayed either in English or German depending on the language setting of the browser.

A master-detail interface is used for the frontend to ensure a simple, intuitive page structure. The upper part of the viewing page consists of individual tabs for the detail pages (basic data, medical data, transplantation data, etc.). This master part remains unchanged regardless of which detail page is shown below (Figure 4). The detail view of each page enables an easy overview on the page topic.

For data manipulation, the EHR has different levels of user rights ("read", "write", "delete", and "administrator"). There is an "edit" level in addition to the "view" level, which can only be activated by users with higher rights than "read". If the user has the right to write, all input fields for data entry are activated and can be filled with data. Users with "delete" rights can delete data via a corresponding button, but only after confirmation through a pop-up window.

Database structure and interfaces
The development of TBase is performed in the development database. Extensive and detailed testing of all software changes such as new functionalities is carried out in the quality assurance database. Software updates that pass the quality control checks are transferred to the live system. For research purposes the live system is copied into the replication database, which can be queried via standard Open Database Connectivity (ODBC) interfaces (e.g., via open-source software R Studio). As there is no direct connection between replication and live system the data in the live system are protected from corruption, loss or manipulation of data. This modular structure and the clear separation of the four databases (development, quality assurance, live system and replication database), which are tailored to the specific needs of developers, researchers, and clinicians facilitates maintenance and data protection of sensitive patient data.

The EHR is fully integrated into the Data Infrastructure of Charité and relies on different interfaces for data import from various data sources. The interface to the HIS imports all relevant data such as administrative data, examinations, medications, laboratory findings and discharge letters. This interface connects both systems via a staging area. Here, all new data (data delta) are transferred from the HIS to TBase in real time. Patients are identified via a patient number or case number and the corresponding data from the HIS is imported (if not already available in TBase).

For outpatients, our laboratory partner provides the laboratory results via HL7 messages. These are deployed to a shared area in the laboratory system and picked up via an HL7 interface and imported into the EHR. For bi-directional communication and data exchange with KTR (via smartphone apps) and home nephrologists, a HL7 Fast Healthcare Interoperability Resource (HL7 FHIR) interface was implemented26. This interface grants interoperability and flexibility for a safe data exchange with other data sources (e.g., Eurotransplant, patient apps) in the future.

User Management and Data Protection
TBase is based on user management at the application level. Thus, the user can only access the frontend of the application, but not the database itself. As described above, a four-stage authorization concept was chosen, reserving user management for those with administrative rights. Administrators use an "Identity Management Console" application to add new users from the Charité user pool for the TBase application and to maintain their user rights (Figure 5). Most users can access all patients in the database. However, it is possible to restrict access for specific users such as study monitors to a group of patients.

Using the commercial in-memory database platform a secure database technology that protects data with strategies such as application-level authorization, single sign-on (SSO), MIT-Kerberos protocol and Security Assertion Mark-up Language (SAML) is used. The platform secures communication, data storage, and application services using the latest encryption and testing techniques. All developments on the database are controlled by authorizations. This ensures the security of data by design at a high level. In addition, all data are kept behind the certified Charité firewall. In compliance with the latest European Union General Data Protection Regulation (EU GDPR) a robust data protection concept was implemented, including data flow diagrams, data protection risk assessment (DSFA) and authorization concept. All documents are laid down in a procedure directory of the Charité Data Protection Office.

프로토콜

The protocol demonstrates the use of the electronic health record TBase, how to add data into the database, and how to extract them for research purposes. All steps are in accordance with the guidelines of the human research ethics committee of Charité - Universitätsmedizin Berlin.

1. Register a new patient and add basic patient data into TBase

  1. Upon registration, transfer the patient's basic data (name, birth date, and health insurance data) from the patient's health insurance card to the hospital information system. During this process, a new unique case number is created. If the patient has never been treated at Charité - Universitätsmedizin Berlin, a new unique patient number is created as well, that clearly identifies this particular patient in the hospital system.
  2. During this registration process, obtain written informed consent from the patient for TBase data processing by Charité - Universitätsmedizin Berlin and the outpatient clinic of Charité (Ambulantes Gesundheitszentrum der Charité) according to the EU GDPR.
  3. Have an employee with appropriate permission add this new patient to TBase. First, sign into TBase via the GUI. For that, enter "https://nephro.tbase.charite.de” into a Chrome-Engine based Web Browser in Charité Intranet. Next, enter the username and password assigned by the TBase administrator. Click Log On.
  4. Next, click on the Add new patient button on bottom of the Patient overview frame on the left. Then, an input screen appears.
  5. Enter the patient's name, birth date, Charité hospital patient number (see above, or alternatively a Charité hospital case number), and the information about patient data processing consent (if it is granted, not granted or revoked by the patient). Click on the Save button on the bottom right when data entry is completed.
    ​NOTE: Now, a new patient has been added to TBase and automatically all available patient data are now transferred from HIS into the TBase EHR system.

2. Viewing and adding data to a patient record in TBase in the Sections: Master Data, Medical Data, Doctors, Diagnosis, Procedures, Transplantation Data, Hospital

  1. Log in to EHR as described in step 1.3.
  2. Search for the desired patient via the search field on the top left via name or birth date. Click on the search button right of the search field or hit Enter. From the results in the Patient overview frame on the left, choose the right patient and click on the name. A new screen appears, showing the selected patient's Master Data.
  3. After searching for a patient, the patient's Master Data viewing page appears by default. To navigate there from another page, click on the Master Data tab on the top left.
    1. To change Master Data, click on the Change button on the bottom right. A new input screen appears.
    2. Now, change data such as patient's phone number, address, add or correct an identification code by typing the new information into the designated input fields. After data entry is completed, submit the changes by clicking on the Save button on the bottom right. After being redirected to the Master Data viewing page, changes can be seen and verified.
  4. To view and change Medical Data, click on the Medical Data tab on the top left. The Medical Data overview appears and shows the existing medical data. They are structured as follows: patient's height, blood type, first dialysis date, primary disease, HLA, genetics data, dialysis data, data on existing HLA-antibodies, transfusion data, risk factors, allergies, structured anamnesis data, death.
    1. To change some of the medical data, click on the Change button on the bottom right. A new input screen appears.
    2. For example, add a primary disease to the patient's medical data by clicking on Primary disease to expand or collapse the data entry form. On the right, the primary disease input field can be used to select one disease out of the preexisting suggestions (e.g., from Eurotransplant primary disease table) or to enter a new disease. Additionally, information about the diagnosis date, the certainty of the disease (biopsy-proven or not) and a comment can be entered. After data entry, submit by clicking on the Submit Values button.
    3. After all changes have been entered and submitted, save the changes by clicking on the Save button on the bottom right. After being redirected to the Medical Data viewing page, all changes can be seen and whether they have been saved correctly.
  5. To view information about the treating physicians, click on the Doctors tab. The Doctors viewing page opens up and shows the existing data about treating physicians. They are structured as follows: physician's name and address, specialization, type (consultant, general practitioner, resident), working facility (dialysis ward, outpatient clinic, etc.), phone number.
    1. To add a new physician, click on the New button on the bottom right. A new input screen opens up. Alternatively, information about existing physicians can be modified by clicking on the physician's name first, and afterward clicking on the Change button on the bottom right.
    2. For example, a new physician can be added to the patient's EHR. Search the list of previously added physicians by entering a name into the search field and clicking on the right entry from the different suggestions. Alternatively, if the desired physician is not in the list, enter the data into the input field below after selecting Add New Physician first.
    3. After all changes have been entered, save the changes by clicking on the Save button on the bottom right. After being redirected to the Doctors viewing page, all changes are visible and the user can verify that the changes have been applied correctly.
  6. To view and change diagnoses, click on the Diagnosis tab on the top left.
    ​NOTE: Most of the diagnoses, procedures and investigations are automatically imported via predefined interfaces from the HIS about inpatient treatment data.
    1. Enter diagnoses made in the outpatient clinic by clicking the New button on the bottom right.
    2. A new diagnosis can be entered, based on International Classification of Diseases 10: Revision (ICD-10). Enter the ICD-10 code or the diagnosis name into the search field in the center of the screen and select the right one from a suggestion list by clicking on it. Next, define the start and end date if applicable and the context, where the diagnosis was made (inpatient or outpatient) by typing these data into the designated input fields.
    3. Submit the data by clicking the Save button on the bottom right. After being redirected to the Diagnosis viewing page, the changes become visible and the user can see, whether data entry was correct.
  7. To view and change procedures, click on the Procedures tab on the top.
    1. Enter additional procedures performed in the outpatient clinic by clicking the New button on the bottom right.
    2. A new procedure can be entered, based on OPS-Code (German version of International Classification of Procedures in Medicine (ICPM) codes). Enter the OPS-code or the procedure's name into the search field in the center of the screen and select the right one from a suggestion list by clicking on it. Next, define the localization (left, right, none) and the context, where the procedure was performed (inpatient or outpatient) by typing these data into the designated input fields.
    3. Submit the data by clicking the Save button on the bottom right. After being redirected to the Procedures viewing page, verify that the changes have been applied correctly.
  8. To view and change data on investigations, click on the Investigations tab on the top.
    NOTE: Since most of the reports in the HIS are provided as text-files, most of the corresponding results in the EHR are text-based as well. In contrast, pathological reports from kidney transplant biopsies are classified according to Banff Classification 201727,28 and the resulting discrete classification data are saved into a corresponding table in the EHR.
    1. To look at the findings of a specific investigation click on the right one in the list below or use the search field above to select it from the suggestion list.
    2. Enter additional investigations performed in the outpatient clinic by clicking the New button on the bottom right.
    3. Enter a new investigation by typing date, type (ultrasound, holter-monitoring, etc.), involved organ and the findings into the designated input fields.
    4. Submit the data by clicking the Save button on the bottom right. After being redirected to the Investigations viewing page, the changes can be seen and verified by the user.
  9. To view and change data on hospitalizations, click on the Hospital tab on the top.
    NOTE: Regularly, KTR that have been transplanted at Charité are hospitalized at the transplant center for subsequent complications. Generated data is firstly stored in the HIS and relevant data (e.g., data about admission or discharge, medical reports) are imported into EHR via HIS interface. External hospitalization have to be entered into EHR manually.
    1. The data on hospitalization is structured as follows: admission, discharge, medical report if available, hospital, ward, and reason for hospitalization. To read the medical report, click on the right one in the list or use the search field above to select it from the suggestion list.
    2. Enter an additional hospitalization (e.g., external hospitalization) by clicking the New button on the bottom right.
    3. Enter a new hospitalization by typing above-mentioned data into the designated input fields.
    4. Submit the data by clicking the Save button on the bottom right. After being redirected to the Hospital viewing page, where the changes become visible and can be verified.
  10. To view and change transplantation data, click on the Transplantation tab on the top right. The Transplantation viewing page appears and shows the existing transplantation data. On the top, navigate between different transplantations by clicking on the corresponding button, if more than one transplantation has been performed.
    1. To view or change information about the donor, click on the View Donor button below the corresponding transplantation date. To enter or change information about the donor, click on the Change button at the bottom right and enter data into the designated input fields and save the changes by clicking on the Save button on the bottom right thereafter.
    2. To add a new transplantation to the patient's EHR, click on the New button on the bottom right on the Transplantation viewing page. Enter transplantation specific data according to the input fields (including information about organ type, transplantation date, ischemia time, procedural complications among others). Save the data to the EHR by clicking on the Save button at the bottom right. The user is then redirected to the Transplantation viewing page to see whether the changes have been saved correctly.
    3. To change information about an existing transplantation, click on the Change button on the bottom right on the Transplantation viewing page, and a new input screen appears where the existing data for the selected transplantation are shown. Change these transplantation specific data according to the input fields (including information about organ type, transplantation date, ischemia time, procedural complications among others). Save the new entry data in the EHR by clicking on the Save button at the bottom right. After being redirected to the Transplantation viewing page, see the changes and check whether changes are entered correctly.

3. Viewing and selecting laboratory data

  1. Log in to TBase and select the desired patient as described in 1.3 and 2.2.
  2. To view the laboratory data, click on the Laboratory tab on the top, and a tabular overview of the latest laboratory results appears. On the top, all data of the last investigation are visible with a drop-down menu to search for previous lab data and a search field next to it, where one can search for specific laboratory values (e.g., creatinine).
    NOTE: The laboratory values are displayed as follows: date of sample receipt, date of processing, name of the laboratory value, value, unit, reference range, a comment (H … high, L … low, N … normal), and the previous two historic lab values for comparison.
  3. To change a date for view of a historic laboratory investigation, click on the drop-down menu on the top left and select the desired date by clicking on it. All corresponding lab values from this date is then displayed as described above.
  4. To select a specific laboratory value such as creatinine and examine its course over time, type its name into the search field on the top and select the right one from the suggestion list. After clicking the Show Labor button, every result for the selected value of this patient is shown in the chart below.
    1. Alternatively, simply click on the desired value in the initial tabular presentation of a single investigation. This again shows all previous and the current results for this specific laboratory value.
  5. To plot the course of a laboratory value, click the plot symbol next to the desired value. This automatically creates a plot of all existing results for this value. If needed, specify the time range for the plot by selecting a start and end date in the input fields on the top right and add a second value to the plot by selecting it in the designated input field. Go back to the Laboratory viewing page by clicking on the Back button on the bottom right.

4. Viewing and changing medication data: creating a standardized medication list according to German regulations ("Bundeseinheitlicher Medikationsplan")

  1. Log in to TBase and select the desired patient as described in 1.3 and 2.2.
  2. To view the medication data, click on the Medication tab on the top. A tabular overview about the patient's current medication appears. The medication data are shown as follows: starting date, active substance, single dose (e.g., in mg), trading name, dosing scheme, daily dose, dosage form, notification, indication, kind of prescription (internal or external physician, or self-treatment by the patient).
  3. To add a new medication, click on the New button at the bottom right. Enter the name of the substance (or alternatively the trade name), the dosing scheme, and the starting date, which is set automatically at the current date, but can be changed if the starting date was in the past. Additionally, indication and a remark can be added into the designated input fields. Add the medication to the list by clicking on the Save button on the bottom right.
  4. To change an existing medication, click on the appropriate item in the medication list and on the Change button on the bottom right afterwards. Now, changes regarding dosage, application form can be typed into the designated input fields and the changes can be applied by clicking the Save button on the bottom right.
  5. To discontinue a drug, click on the designated drug and click on the Discontinue button on the top.
  6. To search for previous medication, enter the active substance into the search field on the top left and select the right one by clicking on it from the historic medication list. A chart with all previous medications appears, which is structured as stated in 4.2.
  7. To create a standardized medication list for the patient according to German regulations, click on the button Bundeseinheitlicher Medikationsplan on the top right. A PDF-file is created and downloaded automatically for printout.

5. Viewing and adding entries to the medical course: generating a medical report semi-automatically

  1. Log in to the EHR and select the desired patient as described in 1.3 and 2.2.
  2. To view the medical course, click on the Course tab on the top. A tabular overview about the documentation from the patient's previous appointments is provided. The data are structured as follows: date of the appointment, date of the next appointment, blood pressure, heart rate, temperature, weight, body mass index, urine volume and three text fields divided into public assessment for the patient, internal assessment for use at Charité, and medical assessment for other physicians.
    NOTE: Additionally, there is a summary field at the bottom, which is used to summarize important information about the patient's medical history and make it visible at first sight.
  3. To add a new entry to the medical course, click on the New button on the bottom right. Enter the information assessed into the desired input fields (e.g., vital signs, treating physician, internal assessment or public assessment). Add the date of the next appointment into the designated input field on the top right. Submit the data by clicking the Save button on the bottom right. Users are then redirected to the Course viewing page.
  4. To change an existing entry, click on the appropriate one and click the Change button on the bottom right next. Now, enter additional data into the designated input fields or change existing data. Change or update information in the notification field by typing into it, and submit the changes by clicking the Save button on the bottom right. Users are then redirected to the Course viewing page.
  5. To create an automated medical report, click on the Medical Report button on the bottom right. A new screen appears, with 18 different options (ranging from laboratory results to complete medical report).
    1. For example, create a medical report with a few clicks: Click on Outpatient Medical Report. The patient name, the treating physician, the last date of the laboratory values and last date of medical course are automatically filled out, but can be changed if needed. After confirmation by clicking on OK, a properly formatted word (.doc-) document file is created and downloaded for printout containing the selected information.

6. Logging out

  1. To actively log out of TBase, click the Log out button at the bottom right. Additionally, one is logged out automatically after 60 minutes of inactivity or if the browser is closed.

7. Using the collected data

  1. To query the collected data, use replication server (Figure 1) as described in the Database structure and interfaces section. Any data processing programs that can connect to a database via Open Database Connectivity (ODBC), Java Database Connectivity (JDBC) can be used for the queries. Once the connection to the database has been established, use the open-source software R Studio.
  2. To set up an ODBC database connection, for example, in the Windows operating system, open the ODBC tool and click Add for a new user data source name (DSN) under Control Panel and Security Management. There, enter the available connection data to the replication database. Enter the following data: "Driver Name", "ODBC Connection Name" (set by the user), "Hostname" and the SQL authentication details "User Name", "Password" and "Database Name".
  3. In order to generate a very simple query (e.g., number of transplants divided by gender in the years 2000-2020) in the open-source software R Studio after the ODBC database connection has been set up, open File, New File in the application R Studio at the top left and click on R Script. The example script code (Code 1) is entered in the empty script window that opens.
  4. Click on button Source on the top of the script window and the script is running and then generates the bar chart defined in the script with the data from the connected database (Figure 6).

결과

TBase was first released in 1999 at Charité Campus Mitte and is in use ever since. For more than 20 years the TBase-EHR prospectively collects data from all KTR. Starting in 2001, the other transplant programs at Charité used TBase for the routine care of KTR and wait-listed patients as well. Since 2007, this EHR is in use for routine care of living donors and all patients in the department of nephrology.

By providing the TBase software with its functionalities, which has been furthe...

토론

TBase combines a web-based EHR for specialized outpatient care of KTR with a research database, creating a comprehensive long-term database for patients with kidney disease6,11,15,37. Regarding organizational structure, this is enabled by implementing a modern software design process as an institutional agent and including over 20 years of experience as developers, clinical users and researcher...

공개

The corresponding authors have nothing to declare.

감사의 말

The development of the presented EHR was supported over the last 20 years by internal research funding and public funding from different institutions and foundations.

자료

NameCompanyCatalog NumberComments
Developer platform SAP Web IDESAP SE
GUI Toolbox SAPUI5SAP SE
In-memory database SAP-HANASAP SE
Interface Standard HL7Health Level Seven International
Interface Standard HL7 FHIRHealth Level Seven International
RStudioRStudio Inc.
TBase - Electronic Health RecordCharité - Universitätsmedizin Berlin
Webserver SAP-HANA XSASAP SE

참고문헌

  1. Halleck, F., et al. Integrated care of renal transplant patients - Development of an electronic health care service platform. Dialyse aktuell. 20 (06), 285-290 (2016).
  2. Sonntag, D., et al. The Clinical Data Intelligence Project. Informatik-Spektrum. 39 (4), 290-300 (2016).
  3. Kara, E., et al. A Domain-adapted Dependency Parser for German Clinical Text. Proceedings of the 14th Conference on Natural Language Processing. , (2018).
  4. Maier, C., et al. Experiences of Transforming a Complex Nephrologic Care and Research Database into i2b2 Using the IDRT Tools. Journal of Healthcare Engineering. 2019, 5640685 (2019).
  5. Jensen, P. B., Jensen, L. J., Brunak, S. Mining electronic health records: towards better research applications and clinical care. Nature Reviews Genetics. 13 (6), 395-405 (2012).
  6. Schmidt, D., et al. A novel tool for the identification of correlations in medical data by faceted search. Computers in Biology and Medicine. 85, 98-105 (2017).
  7. Veit, K., Wessels, M., Deiters, W. Gesundheitsdaten und Digitalisierung - Neue Anforderungen an den Umgang mit Daten im Gesundheitswesen. Digitale Transformation von Dienstleistungen im Gesundheitswesen VI: Impulse für die Forschung. , 19-33 (2019).
  8. Ehrler, F., Geissbuhler, A., Jimeno, A., Ruch, P. Data-poor categorization and passage retrieval for gene ontology annotation in Swiss-Prot. BMC Bioinformatics. 6, 23 (2005).
  9. Esteban, C., Schmidt, D., Krompaß, D., Tresp, V. Predicting Sequences of Clinical Events by Using a Personalized Temporal Latent Embedding Model. 2015 International Conference on Healthcare Informatics. , 130-139 (2015).
  10. Roller, R., et al. Detecting Named Entities and Relations in German Clinical Reports. Language Technologies for the Challenges of the Digital Age. , 146-154 (2018).
  11. Roller, R., et al. A fine-grained corpus annotation schema of German nephrology records. Clinical Natural Language Processing Workshop (ClinicalNLP). , (2016).
  12. Esteban, C., Staeck, O., Baier, S., Yang, Y., Tresp, V. Predicting Clinical Events by Combining Static and Dynamic Information Using Recurrent Neural Networks. IEEE International Conference on Healthcare Informatics (ICHI). , 93-101 (2016).
  13. Schmidt, D., Niemann, M., Trzebiatowski, G. L. v. The Handling of Missing Values in Medical Domains with Respect to Pattern Mining Algorithms. Proceedings of the 24th International Workshop on Concurrency, Specification and Programming (CS&P 2015). 1492, 147-154 (2015).
  14. Burchardt, A., Uszkoreit, H. IT für soziale Inklusion: Digitalisierung - Künstliche Intelligenz - Zukunft für alle. De Gruyter. , (2018).
  15. Schroter, G., Lindemann, L. F. TBase2 - A Web-Based Electronic Patient Record. Fundamenta Informaticae. 43 (1-4), 343-353 (2000).
  16. Duettmann, W., et al. eHealth in Transplantation. Transplant International. , (2020).
  17. Durr, M., et al. Late Conversion to Belatacept After Kidney Transplantation: Outcome and Prognostic Factors. Transplantation Proceedings. 49 (8), 1747-1756 (2017).
  18. Halleck, F., et al. MHealth and digital management after kidney transplantation. Nieren- und Hochdruckkrankheiten. 46, 474-480 (2017).
  19. Düttmann-Rehnolt, W., et al. Neuartige Kommunikationswege und Strukturen zur Optimierung der häuslichen Versorgung am Beispiel von nierentransplantierten Patienten. Digitale Transformation von Dienstleistungen im Gesundheitswesen VI: Impulse für die Forschung. , 407-421 (2019).
  20. Hils, S., Bogatyreva, L., Hauschke, D., Pisarski, P. Telemedical Supported Aftercare as an Innovative Project-Study Improves the Quality of Life After Living Kidney Transplantation - A Single Center Experience. American Journal of Transplantation. 14 (3), 843 (2014).
  21. Schmidt, D., et al. Integrierte Versorgung chronisch kranker Patienten am Beispiel von MACSS: Digitalisierung - Künstliche Intelligenz - Zukunft für alle. IT für soziale Inklusion. , 41-50 (2018).
  22. Massie, A. B., Kucirka, L. M., Segev, D. L. Big data in organ transplantation: registries and administrative claims. American Journal of Transplantation. 14 (8), 1723-1730 (2014).
  23. McAdams-DeMarco, M. A., et al. Frailty, Length of Stay, and Mortality in Kidney Transplant Recipients: A National Registry and Prospective Cohort Study. Annals of surgery. 266 (6), 1084-1090 (2017).
  24. The Most Popular Browsers. w3schools.com Available from: https://www.w3schools.com/browsers/ (2020)
  25. H.L.S.I. HL7 International Available from: https://www.hl7.org/ (2020)
  26. Duettmann, W., et al. Digital home monitoring of patients after kidney transplantation: The MACCS platform. Journal of Visualized Experiments. , (2021).
  27. Haas, M., et al. The Banff 2017 Kidney Meeting Report: Revised diagnostic criteria for chronic active T cell-mediated rejection, antibody-mediated rejection, and prospects for integrative endpoints for next-generation clinical trials. American Journal of Transplantation. 18 (2), 293-307 (2018).
  28. Roufosse, C., et al. A 2018 Reference Guide to the Banff Classification of Renal Allograft Pathology. Transplantation. 102 (11), 1795-1814 (2018).
  29. Duerr, M., et al. Increased incidence of angioedema with ACE inhibitors in combination with mTOR inhibitors in kidney transplant recipients. Clinical Journal of the American Society of Nephrology. 5 (4), 703-708 (2010).
  30. Lachmann, N., et al. Invited letter in response to "Predicted indirectly recognizable HLA epitopes (PIRCHE): Only the tip of the iceberg?". American Journal of Transplantation. 18 (2), 523-524 (2018).
  31. Huber, L., Naik, M., Budde, K. Desensitization of HLA-incompatible kidney recipients. The New England Journal of Medicine. 365 (17), 1644-1645 (2011).
  32. Choi, M., et al. Low Seroprevalence of SARS-CoV-2 Antibodies during Systematic Antibody Screening and Serum Responses in Patients after COVID-19 in a German Transplant Center. Journal of Clinical Medicine. 9 (11), (2020).
  33. Lehner, L. J., et al. Analysis of Risk Factors and Long-Term Outcomes in Kidney Transplant Patients with Identified Lymphoceles. Journal of Clinical Medicine. 9 (9), (2020).
  34. Zhang, Q., et al. The relationship between proteinuria and allograft survival in patients with transplant glomerulopathy: a retrospective single-center cohort study. Transplant International. , (2020).
  35. Bissler, J., et al. Everolimus for angiomyolipoma associated with tuberous sclerosis complex or sporadic lymphangioleiomyomatosis (EXIST-2): A multicentre, randomised, double-blind, placebo-controlled trial. Lancet. 381, (2013).
  36. Budde, K., et al. Everolimus-based, calcineurin-inhibitor-free regimen in recipients of de-novo kidney transplants: an open-label, randomised, controlled trial. Lancet. 377 (9768), 837-847 (2011).
  37. Lindemann, G., Schröter, K., Schlaefer, A., Budde, K., Neumayer, H. H. Web-Based Patient Records - The Design of TBase2. New Aspects of High Technology in Medicine. , (2000).
  38. Big Data Project | BigMedilytics | The largest initiative to transform healthcare sector. BigMedilytics Available from: https://www.bigmedilytics.eu/big-data-project/ (2020)
  39. Duettmann, W., et al. Telemedizinische Betreuung von Patienten nach Nierentransplantation: Was beinhaltet MACCS. Nieren- und Hochdruckkrankheiten. 49, (2020).

재인쇄 및 허가

JoVE'article의 텍스트 или 그림을 다시 사용하시려면 허가 살펴보기

허가 살펴보기

더 많은 기사 탐색

TBaseIntegrated Electronic Health RecordKidney TransplantResearch DatabasePost transplant CareClinical RoutineData ValidationHL7 StandardsModular Database DesignPatient Data EntryMedication PlansHealth Records ManagementElectronic Health Record SystemOutpatient Clinics

This article has been published

Video Coming Soon

JoVE Logo

개인 정보 보호

이용 약관

정책

연구

교육

JoVE 소개

Copyright © 2025 MyJoVE Corporation. 판권 소유