Modèles de données sélectionnés

Vous devez être connecté pour sélectionner plusieurs modèles de données, les télécharger ou les analyser.

6 Résultats de recherche.
Pertinence Commentaire Plus récent Moins récent

26672_Common Data Elements Myeloid Leukemia (MDS AML CML) - Global Disease Course

- 20/09/2021 - 13 Formulaires, 3 Groupes Item, 11 Eléments de données, 1 Langue
Groupes Item: Global Disease Course, Red Cell Transfusion, Platelet Cell Transfusion
Common Data Elements Myeloid Leukemia (MDS, AML, CML) for use in clinical routine and clinical trial documentation. https://www.ncbi.nlm.nih.gov/pubmed/27577388

Physical Examination/Follow up

3 Groupes Item 14 Eléments de données

Administrative/Demographic Details

1 Groupe Item 11 Eléments de données

Medical History

3 Groupes Item 9 Eléments de données

Lab: Cytology/Cytogenetics/Cytochemistry

1 Groupe Item 29 Eléments de données

Lab: Immunophenotyping

1 Groupe Item 17 Eléments de données

Lab: Molecular Genetics

1 Groupe Item 27 Eléments de données

Acute Myeloid Leukemia - Treatment Details

- 20/09/2021 - 13 Formulaires, 6 Groupes Item, 39 Eléments de données, 1 Langue
Groupes Item: Therapeutic procedure; Details, Adverse Event, Hemopoietic stem cell transplant, Platelet Engraftment, Neutrophil Engraftment, Therapeutic procedure; Status
Acute Myeloid Leukemia Common Data Elements Holz

Medical History

6 Groupes Item 20 Eléments de données

Lab: Cytology/Cytogenetics/Cytochemistry

3 Groupes Item 43 Eléments de données

Lab: Molecular Genetics, Immunophenotyping, Cytogenetics

1 Groupe Item 1 Élément de données

Physical Examination/Follow-up

4 Groupes Item 27 Eléments de données

Lab: Infectiology

1 Groupe Item 11 Eléments de données

Lab: Molecular Genetics

1 Groupe Item 23 Eléments de données

Sentinel Common Data Model Procedure

- 25/08/2019 - 1 Formulaire, 1 Groupe Item, 8 Eléments de données, 1 Langue
Groupe Item: Procedure
Sentinel: Overview and Description of the Common Data Model v7.0.0 "The primary goal of Sentinel is to build and operate a national public health surveillance system to monitor the safety of FDA-regulated medical products, including drugs, biologics, and devices. Sentinel is part of the Sentinel Initiative, the FDA’s response to a congressional mandate to create an active surveillance system using electronic health data.The Sentinel program will undertake three major types of activities: (1) prospective evaluation of accumulating experience about specific medical products and specific suspected safety problems; (2) evaluation of the impact of FDA actions (e.g., labeling changes) on medical practice and health outcomes; and (3) rapid assessment of past experience in response to FDA questions about specific exposures and outcomes." For more information about Sentinel visit the website at: www.sentinelsystem.org For comments and suggestions, please email: info@sentinelsystem.org The SCDM Procedure Table contains one record per unique combination of PatID, EncounterID, PX, and PX_CodeType. This table should capture all uniquely recorded procedures for all encounters.

SpezifischeDiagnosen MS University Hospital Muenster (UKM) Subform

- 20/09/2021 - 1 Formulaire, 1 Groupe Item, 23 Eléments de données, 1 Langue
Groupe Item: Diagnosen
Hospital Routine Documentation Subform at the University Hospital Muenster. Original Form name: SpezifischeDiagnosen.

Procedure (EHR Archetype) - openEHR-EHR-ACTION.procedure.v1

- 08/07/2017 - 1 Formulaire, 1 Groupe Item, 24 Eléments de données, 7 Langues
Groupe Item: openEHR-EHR-ACTION.procedure.v1.xml
Derived from www.openehr.org . Use to record information about the activities required to carry out a procedure, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording of data against specific activities, as defined by the 'Pathway' careflow steps in this archetype. The scope of this archetype encompasses activities for a broad range of clinical procedures performed for evaluative, investigative, screening, diagnostic, curative, therapeutic or palliative purposes. Examples range from the relatively simple activities, such as insertion of an intravenous cannula, through to complex surgical operations. Additional structured and detailed information about the procedure can be captured using purpose-specific archetypes inserted into the 'Procedure detail' slot, where required. Timings related to a procedure can be managed in one of two ways: - Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step. - Archetyped data elements: --- the 'Scheduled date/time' data element is intended to record the precise time when the procedure is planned. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the procedure was scheduled into a system, not the intended date/time on which the procedure is intended to be carried out; and --- the 'Final end date/time' is intended to record the precise time when the procedure was ended. It can be used to document the complex procedures with multiple components. Note: the corresponding ACTION time attribute for the 'Procedure performed' will document the time each component performed was commenced. This 'Final end date/time' data element will record the date/time of the final active component of the procedure. This will enable a full duration of the active procedure to be calculated. Within the context of an Operation Report, this archetype will be used to record only what was done during the procedure. Separate archetypes will be used to record the other required components of the Operation Report, including the taking of tissue specimen samples, use of imaging guidance, operation findings, post-operative instructions and plans for follow up. Within the context of a Problem list or summary, this archetype may be used to represent procedures that have been performed. The EVALUATION.problem_diagnosis will be used to represent the patient's problems and diagnoses. In practice, many procedures (for example, in ambulatory care) will occur once and not be ordered in advance. The details about the procedure will be added against the pathway step, 'Procedure completed'. In some cases a recurring procedure will be ordered, and in this situation data against the 'Procedure performed' step will be recorded on each occasion, leaving the instruction in the active state. When the last occurrence is recorded the 'Procedure completed' action is recorded showing that this order is now in the completed state. In other situations, such as secondary care, there may be a formal order for a procedure using a corresponding INSTRUCTION archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out. Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the procedure itself but may be a failed attempt or another activity such as postponing the procedure. If there is a formal order for the procedure, the state of this order is represented by the Pathway step against which the data is recorded. For example, using this archetype the progressing state of a Gastroscopy order may be recorded through separate entries in the EHR progress notes at each 'Pathway' step: - record the scheduled Start date/time for the gastroscopy (Procedure scheduled); and - record that the gastroscopy procedure has been completed, including information about the procedure details (Procedure completed). Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the procedure (using the 'Procedure performed' pathway step) or the time that the procedure was aborted (using the 'Procedure aborted' pathway step).

OPS Chapter 1 Diagnostic Procedures

- 03/09/2015 - 1 Formulaire, 1 Groupe Item, 1 Élément de données, 2 Langues
Groupe Item: OPS 1
derived from: OPS - German Procedure Classification https://www.dimdi.de/static/en/klassi/ops/index.htm DIMDI publishes the OPS classification on behalf of the Federal Ministry of Health; it is in the public domain. Its use in inpatient care is laid down in § 301 Volume V of the German Social Security Code (SGB V) and for surgical procedures in the outpatient sector in § 295 SGB V.

Contact

Utilisez ce formulaire pour les retours, les questions et les améliorations suggérées.

Les champs marqués d’un * sont obligatoires.

Aide

Do you need help on how to use the search function? Please watch the corresponding tutorial video for more details and learn how to use the search function most efficiently.

Watch Tutorial