Raw JSON
{'hasResults': False, 'derivedSection': {'miscInfoModule': {'versionHolder': '2025-12-24'}}, 'protocolSection': {'designModule': {'phases': ['NA'], 'studyType': 'INTERVENTIONAL', 'designInfo': {'allocation': 'RANDOMIZED', 'maskingInfo': {'masking': 'DOUBLE', 'whoMasked': ['INVESTIGATOR', 'OUTCOMES_ASSESSOR']}, 'primaryPurpose': 'PREVENTION', 'interventionModel': 'CROSSOVER'}, 'enrollmentInfo': {'type': 'ACTUAL', 'count': 203}}, 'statusModule': {'overallStatus': 'COMPLETED', 'startDateStruct': {'date': '2021-05-01', 'type': 'ACTUAL'}, 'expandedAccessInfo': {'hasExpandedAccess': False}, 'statusVerifiedDate': '2022-03', 'completionDateStruct': {'date': '2022-09-30', 'type': 'ACTUAL'}, 'lastUpdateSubmitDate': '2022-10-18', 'studyFirstSubmitDate': '2019-08-08', 'studyFirstSubmitQcDate': '2019-08-14', 'lastUpdatePostDateStruct': {'date': '2022-10-19', 'type': 'ACTUAL'}, 'studyFirstPostDateStruct': {'date': '2019-08-16', 'type': 'ACTUAL'}, 'primaryCompletionDateStruct': {'date': '2022-07-30', 'type': 'ACTUAL'}}, 'outcomesModule': {'primaryOutcomes': [{'measure': 'correct approval for operation', 'timeFrame': '1 day', 'description': 'number of patients that were approved correctly for surgery'}], 'secondaryOutcomes': [{'measure': 'missing examinations', 'timeFrame': '1 day', 'description': 'number of examinations that were recommended by the guidelines but not applied to the patient'}, {'measure': 'unnecessary examinations', 'timeFrame': '1 day', 'description': 'number of examinations that were not recommended by the guidelines but nevertheless applied'}, {'measure': 'mortality', 'timeFrame': '30 days', 'description': 'in-hospital mortality'}, {'measure': 'length of hospital stay', 'timeFrame': '30 days', 'description': 'length of hospital stay'}, {'measure': 'postoperative complications', 'timeFrame': '30 days', 'description': 'postoperative complications assessed by the Clavien-Dindo-Classification (I: no intervention, II: pharmacologic intervention, IIIa:intervention without general anesthesia, IIb: intervention requiring general anesthesia, IV:life-threatening intervention with dysfunction of one organ, IVb: life-threatening intervention with multi-organ dysfunction, V:death'}]}, 'oversightModule': {'oversightHasDmc': False, 'isFdaRegulatedDrug': False, 'isFdaRegulatedDevice': False}, 'conditionsModule': {'conditions': ['Pre-operative Assessment', 'Adults', 'Non-cardiac Surgery']}, 'referencesModule': {'references': [{'pmid': '38971713', 'type': 'DERIVED', 'citation': 'Kagerbauer SM, Wissler J, Andonov DI, Ulm B, Schneider G, Podtschaske AH, Blobner M, Jungwirth B. Implementation of a software-based decision support tool for guideline-appropriate preoperative evaluation: a prospective agreement study. Br J Anaesth. 2024 Sep;133(3):519-529. doi: 10.1016/j.bja.2024.06.001. Epub 2024 Jul 5.'}]}, 'descriptionModule': {'briefSummary': 'Aim of the project is the development of a software for implementation of anesthesiology guidelines in the preoperative evaluation. The software bases on the 2014 and 2018 guidelines of the European Society of Anesthesiology (ESA) for the pre-operative evaluation of adults undergoing non-cardiac surgery.\n\nTraditional premedication is compared with the new software-guided premedication by using a cross-over design. 200 patients are included in the study, 100 of which are first evaluated the traditional way and then with the software, 100 patients are treated the other way round. Results of the two premedication methods are compared according to the primary endpoint "correct approval for OP" and the secondary endpoints number of missed apparative examinations, number of unnecessary apparative examinations, time required for premedication, length of hospital stay, mortality and postoperative complications.', 'detailedDescription': 'Type of study:\n\nMonocentric, prospective cohort study\n\nProcedure for informing and obtaining consent:\n\nPatients who are prepared for surgery in the anesthetic outpatient department or enrolled in the pre-medication list and who meet all inclusion criteria and no exclusion criteria will be identified before the anesthesia consultation. The patients will be informed about the purpose and the course of the study in oral and written form, after which the written consent of the patient will be given before the study-relevant data and examinations are carried out.\n\nDescription of the data sources (medical records, questionnaires, etc.):\n\nData Sources: Patient\'s medical history, patient history and physical examination, data on standardized Thieme Compliance anesthesia sheets, and existing findings, either external, patient-brought or in-house findings from the SAP. These data are entered into the PDMS. The name of the premedic anesthetist is not relevant for the evaluation and will not be deposited.\n\nListing / description of the data to be collected:\n\nWith the PDMS, all anesthesia-relevant data is collected. These include the history of the patient, current complaints, medication history, physical examination and findings from supplementary equipment examinations. The data of the anonymized control group are extracted exclusively from the PDMS.\n\nTiming (appointments) for the individual study participant:\n\nAfter the patient has been informed and has consented, after randomization either the premedication as usual with the "old PDMS module" is performed and then a second time with the new software module by another doctor or vice versa, first with the new software and then in the traditional way. This type of cross-over design is done to avoid carry-over effects. The conventional premedicating physician does not know about the patient\'s participation in the study and makes the decision about the OP release as well as any necessary additional examinations in the usual way and dismisses the patient with the usual pre-hospitalization standard.\n\nThe premedication with the new software module is carried out by a doctor who has been trained in it and does not know the result of the first premedication interview. With the help of the new software, the decision on release and possible additional examinations is also made here. The data from the two premedication interviews are stored in xml format in the MRI Data Room and entered in a pseudonymized form in a database. This is done promptly on the day of premedication. A specialist trained in the guidelines, who is blinded to the premedication procedure, compares the results of both premedications. He decides whether the release was correct in both of the above cases or not. If it turns out that the results of both premedications differ and possibly a revision of the premedication document is necessary, unblinding and, if necessary, correction of the premedication document takes place.\n\nFurthermore, the time required for the premedication interview is analyzed as well as the correct arrangement of additional examinations. The secondary outcome parameters are collected using the KIS (clinic information system) and PDMS.\n\nAs a comparison population with respect to the secondary endpoints, a conventionally premedicated patient collective, whose anonymized data is extracted from the existing PDMS database, is used in the same period. The endpoint of the comparison is the occurrence of postoperative complications corresponding to a clavia-dindo score of ≥ 3. This corresponds to the events of re-intervention, admission to intensive care unit or death.\n\nExpected end of data collection With hospital discharge, the data collection for the individual patient is completed.'}, 'eligibilityModule': {'sex': 'ALL', 'stdAges': ['ADULT', 'OLDER_ADULT'], 'maximumAge': '100 Years', 'minimumAge': '18 Years', 'healthyVolunteers': False, 'eligibilityCriteria': 'Inclusion Criteria:\n\n* age \\>= 18 years\n* ASA 3 or 4\n* elective surgery\n* written informed consent\n\nExclusion Criteria:\n\n* emergency surgery\n* patient not being able to give informed consent\n* non-german-speaking patients'}, 'identificationModule': {'nctId': 'NCT04058769', 'acronym': 'SGGIP', 'briefTitle': 'Software-guided Guideline Implementation in Premedication', 'organization': {'class': 'OTHER', 'fullName': 'Technical University of Munich'}, 'officialTitle': 'Software Development for Anesthesiology Guideline Implementation in the Perioperative Course', 'orgStudyIdInfo': {'id': '38/19 S-SR'}}, 'armsInterventionsModule': {'armGroups': [{'type': 'OTHER', 'label': 'Software first', 'description': 'Patients that are pre-operatively assessed first software-guided and then traditional', 'interventionNames': ['Device: Premedication Guide']}, {'type': 'OTHER', 'label': 'Traditional', 'description': 'Patients that are first pre-operatively assessed in the traditional way and then with aid of the software', 'interventionNames': ['Device: Premedication Guide']}], 'interventions': [{'name': 'Premedication Guide', 'type': 'DEVICE', 'description': 'Software with guidelines recommendations for preoperative assessment', 'armGroupLabels': ['Software first', 'Traditional']}]}, 'contactsLocationsModule': {'locations': [{'zip': '81675', 'city': 'Munich', 'country': 'Germany', 'facility': 'TU Muenchen', 'geoPoint': {'lat': 48.13743, 'lon': 11.57549}}]}, 'ipdSharingStatementModule': {'ipdSharing': 'NO'}, 'sponsorCollaboratorsModule': {'leadSponsor': {'name': 'Technical University of Munich', 'class': 'OTHER'}, 'collaborators': [{'name': 'Health Information Management, Belgium', 'class': 'OTHER'}], 'responsibleParty': {'type': 'SPONSOR'}}}}