| TEMPLATE ID | GECCO_Dokumentation_HD |
|---|---|
| Concept | GECCO_Dokumentation_HD |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Other Details (Language Independent) |
|
| Keywords | GECCO; NUM; FoDaPl |
| Language used | en |
| Citeable Identifier | 1246.169.2322 |
| Revision | 7 |
| Root archetype id | openEHR-EHR-COMPOSITION.registereintrag.v1 |
| GECCO_Dokumentation_HD | GECCO_Dokumentation_HD: Generic compilation to represent a data set for research purposes. |
| content | |
| Other Context | |
| Status | Status: Status of the supplied data for the register entry. Note: This is not the status of individual components.
|
| Vorerkrankungen | Vorerkrankungen: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Vorliegende Diagnose | Vorliegende Diagnose: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual. Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'. |
| Data | |
| Problem/Diagnosis name | Problem/Diagnosis name: Identification of the problem or diagnosis, by name. Coding of the name of the problem or diagnosis with a terminology is preferred, where possible. Terminology: http://snomed.info/sct
|
| Anatomical location | Anatomical location: A physical site on or within the human body. |
| Body site name | Body site name: Identification of a single physical site either on, or within, the human body. This data element is the only mandated data point in this archetype and should be used as the primary data point to record an anatomical location with a commonly used name. It is strongly recommended that 'Body site name' be recorded as specifically as is anatomically possible. For example: record 'upper eyelid' rather than recording 'eyelid' with 'upper' as a qualifier; 'fifth rib' rather than 'rib' with a numeric qualifier. Use the other data elements for laterality, aspect, region and anatomical line to provide more detail. This data element should be coded with a terminology capable of triggering decision support, where possible - an appropriate termset for use here could comprise individual concepts or a list of precoordinated terms. Free text should be used only if there is no appropriate terminology available. If body site name is already identified in the parent archetype, then this data element may be redundant. Alternatively, a use case has been identified where the value may be duplicated into this element to support semantic querying using this archetype, rather than the data element within the parent. Terminology: http://snomed.info/sct
|
| Specific site | Specific site: Additional detail using a specific region or a point on, or within, the identified body site. Use to increase precision of identification of the body site, if required. For example, the upper right quadrant or McBurney's point on the abdominal wall or interphalangeal joint of the great toe. If the 'Body site name' data element uses pre-coordinated terms that include the specific site, then this data element is redundant. |
| Laterality | Laterality: The side of the body on which the identified body site is located. If the identified body site has no laterality, this data element should not have a value. If the 'Body site name' data element uses pre-coordinated terms that include laterality, then this data element is redundant.
|
| Cause | Cause: A cause, set of causes, or manner of causation of the problem or diagnosis. Also known as 'aetiology' or 'etiology'. Coding with an external terminology is preferred, where possible. |
| Date/time of onset | Date/time of onset: Estimated or actual date/time that signs or symptoms of the problem/diagnosis were first observed. Data captured/imported as "Age at onset" should be converted to a date using the subject's date of birth. |
| Severity | Severity: An assessment of the overall severity of the problem or diagnosis. If severity is included in the Problem/diagnosis name via precoordinated codes, this data element becomes redundant. Note: more specific grading of severity can be recorded using the Specific details SLOT.
|
| Date/time of resolution | Date/time of resolution: Estimated or actual date/time of resolution or remission for this problem or diagnosis, as determined by a healthcare professional. Partial dates are acceptable. If the subject of care is under the age of one year, then the complete date or a minimum of the month and year is necessary to enable accurate age calculations - for example, if used to drive decision support. Data captured/imported as "Age at time of resolution" should be converted to a date using the subject's date of birth. |
| Comment | Comment: Additional narrative about the problem or diagnosis not captured in other fields. |
| Ausgeschlossene Diagnose | Ausgeschlossene Diagnose: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past. |
| Data | |
| Exclusion statement | Exclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item. This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant. Terminology: http://snomed.info/sct
|
| Problem/Diagnose | Problem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'. Terminology: http://snomed.info/sct
|
| Name der Körperstelle | Name der Körperstelle: Additional narrative about the Specific Exclusion not captured in other fields. Terminology: http://snomed.info/sct
|
| Unbekannte Diagnose | Unbekannte Diagnose: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording. |
| Data | |
| Unbekannte Diagnose | Unbekannte Diagnose: Positive statement that no information is available. For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used". Terminology: http://snomed.info/sct
|
| Aussage über die fehlende Information | Aussage über die fehlende Information: Description of the reason why there is no information available. For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible. Terminology: http://snomed.info/sct
|
| Symptome | Symptome: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Vorliegendes Symptom | Vorliegendes Symptom: Reported observation of a physical or mental disturbance in an individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Symptom/Sign name | Symptom/Sign name: The name of the reported symptom or sign. Symptom name should be coded with a terminology, where possible. Terminology: http://snomed.info/sct
|
| Body site | Body site: Simple body site where the symptom or sign was reported. Occurrences of this data element are set to 0..* to allow multiple body sites to be separated out in a template if desired. This allows for representation of clinical scenarios where a symptom or sign needs to be recorded in multiple locations or identifying both the originating and distal site in pain radiation, but where all of the other attributes such as impact and duration are identical. If the requirements for recording the body site are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the Detailed anatomical location' SLOT in this archetype. If the anatomical location is included in the Symptom name via precoordinated codes, this data element becomes redundant. If the anatomical location is recorded using the 'Structured body site' SLOT, then use of this data element is not allowed - record only the simple 'Body site' OR 'Structured body site', but not both. |
| Episode onset | Episode onset: The onset for this episode of the symptom or sign. While partial dates are permitted, the exact date and time of onset can be recorded, if appropriate. If this symptom or sign is experienced for the first time or is a re-occurrence, this date is used to represent the onset of this episode. If this symptom or sign is ongoing, this data element may be redundant if it has been recorded previously. |
| Severity category | Severity category: Category representing the overall severity of the symptom or sign. Defining values such as mild, moderate or severe in such a way that is applicable to multiple symptoms or signs plus allows multiple users to interpret and record them consistently is not easy. Some organisations extend the value set further with inclusion of additional values such as 'Trivial' and 'Very severe', and/or 'Mild-Moderate' and 'Moderate-Severe', adds to the definitional difficulty and may also worsen inter-recorder reliability issues. Use of 'Life-threatening' and 'Fatal' is also often considered as part of this value set, although from a pure point of view it may actually reflect an outcome rather than a severity. In view of the above, keeping to a well-defined but smaller list is preferred and so the mild/moderate/severe value set is offered, however the choice of other text allows for other value sets to be included at this data element in a template. Note: more specific grading of severity can be recorded using the 'Specific details' SLOT. Terminology: http://snomed.info/sct
|
| Resolution date/time | Resolution date/time: The timing of the cessation of this episode of the symptom or sign. If 'Date/time of onset' and 'Duration' are used in systems, this data element may be calculated, or alternatively, considered redundant. While partial dates are permitted, the exact date and time of resolution can be recorded, if appropriate. |
| Ausgeschlossenes Symptom | Ausgeschlossenes Symptom: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past. |
| Data | |
| Exclusion statement | Exclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item. This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant. Terminology: http://snomed.info/sct
|
| Problem/Diagnose | Problem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'. Terminology: http://snomed.info/sct
|
| Unbekanntes Symptom | Unbekanntes Symptom: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording. |
| Data | |
| Unbekanntes Symptom | Unbekanntes Symptom: Positive statement that no information is available. For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used". Terminology: http://snomed.info/sct
|
| Aussage über die fehlende Information | Aussage über die fehlende Information: Description of the reason why there is no information available. For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible. Terminology: http://snomed.info/sct
|
| Prozeduren | Prozeduren: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Procedure | Procedure: A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes. |
| Description | |
| Procedure name | Procedure name: Identification of the procedure by name. Coding of the specific procedure with a terminology is preferred, where possible. Terminology: http://snomed.info/sct
|
| Indication | Indication: The clinical or process-related reason for the procedure. Coding of the indication with a terminology is preferred, where possible. This data element allows multiple occurrences. For example: 'Failed bowel preparation' or 'Bowel cancer screening'. |
| Body site | Body site: Identification of the body site for the procedure. Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'Procedure detail' SLOT in this archetype. If the anatomical location is included in the 'Procedure name' via precoordinated codes, this data element becomes redundant. Terminology: http://snomed.info/sct
|
| Medical device | Medical device: An instrument, apparatus, implant, material or similar, used in the provision of healthcare. In this context, a medical device includes a broad range of devices which act through a variety of physical, mechanical, thermal or similar means but specifically excludes devices which act through medicinal means such as pharmacological, metabolic or immunological methods. The scope is inclusive of disposable devices as well as durable or persisting devices that require tracking, maintenance activities or regular calibration, recognising that each type of device has specific data recording requirements. |
| Device name | Device name: Identification of the medical device, preferably by a common name, a formal fully descriptive name or, if required, by class or category of device. This data element will capture the term, phrase or category used in clinical practice. For example: <brand name><machine> (XYZ Audiometer); <size> <brand name> <intravenous catheter> (14G Jelco IV catheter); or <brand name/type> <implant>. Coding with a terminology is desirable, where possible, although this may be local and depending on local supplies available. Terminology: http://snomed.info/sct
|
| Procedure type | Procedure type: The type of procedure. This pragmatic data element may be used to support organisation within the user interface. Terminology: http://snomed.info/sct
|
| Durchführungsabsicht | Durchführungsabsicht: Reason that the activity or care pathway step for the identified procedure was carried out. For example: the reason for the cancellation or suspension of the procedure. |
| Comment | Comment: Additional narrative about the activity or care pathway step not captured in other fields. |
| Nicht durchgeführte Prozedur | Nicht durchgeführte Prozedur: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past. |
| Data | |
| Exclusion statement | Exclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item. This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
|
| Eingriff | Eingriff: The Procedure to which the 'Exclusion statement' applies. For example: 'Heart surgery' or 'Appendectomy' or 'Hip replacement'. Terminology: http://snomed.info/sct
|
| Unbekannte Prozedur | Unbekannte Prozedur: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording. |
| Data | |
| Unbekannte Prozedur | Unbekannte Prozedur: Positive statement that no information is available. For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used". Terminology: http://snomed.info/sct
|
| Aussage über die fehlende Information | Aussage über die fehlende Information: Description of the reason why there is no information available. For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
|
| Raucherverhalten | Raucherverhalten: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Raucherstatus | Raucherstatus: Summary or persistent information about the tobacco smoking habits of an individual. |
| Data | |
| Overall status | Overall status: Statement about current smoking behaviour for all types of tobacco.
|
| Overall description | Overall description: Narrative summary about the individual's overall tobacco smoking pattern and history. Use this data element to record a narrative description of the tobacco smoking habits for this individual or to incorporate unstructured tobacco smoking information from existing or legacy clinical systems into an archetyped format. Terminology: http://loinc.org
|
| Frailty-Skala | Frailty-Skala: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Clinical Frailty Scale (CFS) | Clinical Frailty Scale (CFS): An assessment scale used to screen for frailty and to broadly stratify degrees of fitness and frailty in an older adult. Also known as the Rockwood Clinical Frailty Scale. |
| Data | |
| Any point in time event | Any point in time event: Default, unspecified point in time event which may be explicitly defined in a template or at run-time. |
| Data | |
| Assessment | Assessment: Assessed level of frailty.
|
| DNR-Anordnung | DNR-Anordnung: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Advance care directive | Advance care directive: A framework to communicate the preferences of an individual for future medical treatment and care. |
| Data | |
| Type of directive | Type of directive: The type of advance care directive. A short text description of the nature of the advance care directive. Coding of the type of directive with a terminology is preferred, where possible. It is expected that this is largely localised to reflect local policy and legislation. For example, in the Netherlands, advance care directive types include, but are not limited to, 'Treatment prohibition', 'Treatment prohibition with completion of Completed Life', 'Euthanasia request' and 'Declaration of life'. In the UK, advance care directive types include 'Advance Decision', 'Advance Directive' and 'Advance Statement'. Terminology: http://terminology.hl7.org/CodeSystem/consentcategorycodes
|
| Description | Description: Narrative description of the overall advance care directive. May be used to record a narrative overview of the complete advance care directive, which may or may not be supported by structured data. Details of specific structured findings can be included using CLUSTER archetypes in the 'Directive details' slot. This data element may be used to capture legacy data that is not available in a structured format. Terminology: http://snomed.info/sct
|
| Reisehistorie | Reisehistorie: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Reisehistorie | Reisehistorie: Details about a specific trip or travel event. |
| Data | |
| Description | Description: Narrative description about the whole trip, especially about potential exposure to health risks. Terminology: http://snomed.info/sct
|
| Specific destination | Specific destination: Details about a single location visited on a trip. |
| Country | Country: The country visited. Terminology: urn:iso:std:iso:3166; iso3166-1-2
|
| State/region | State/region: The region visited. Different regions within the same country maybe identified if they potentially pose different health risks. Terminology: iso/bundeslaender
|
| City | City: The city visited. Different cities within the same country or region maybe identified if they potentially pose different health risks. |
| Date of entry | Date of entry: Date of entry to the identified location. |
| Date of exit | Date of exit: Date of exit from the identified location. |
| Keine Reisehistorie | Keine Reisehistorie: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past. |
| Data | |
| Exclusion statement | Exclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item. This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant. Terminology: http://snomed.info/sct
|
| Problem/Diagnose | Problem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'. Terminology: http://loinc.org
|
| Unbekannte Reisehistorie | Unbekannte Reisehistorie: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording. |
| Data | |
| Fehlende Information | Fehlende Information: Positive statement that no information is available. For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used". Terminology: http://loinc.org
|
| Aussage über die fehlende Information | Aussage über die fehlende Information: Description of the reason why there is no information available. For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible. Terminology: http://snomed.info/sct
|
| Radiologischer Befund | Radiologischer Befund: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Imaging examination result | Imaging examination result: Record the findings and interpretation of an imaging examination performed. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Test name | Test name: The name of the imaging examination or procedure performed. Coding with a terminology, potentially a pre-coordinated term specifying both modality and anatomical location, is desirable where possible. Possible candidate terminologies: LOINC, SNOMED CT or RadLex. Terminology: http://loinc.org
|
| Findings | Findings: Narrative description of the clinical findings. Terminology: http://snomed.info/sct
|
| Körpergewicht | Körpergewicht: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Body weight | Body weight: Measurement of the body weight of an individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Weight | Weight: The weight of the individual. 0..1000 kg |
| Körpergröße | Körpergröße: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Height/Length | Height/Length: Height, or body length, is measured from crown of head to sole of foot. Height is measured with the individual in a standing position and body length in a recumbent position. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Height/Length | Height/Length: The length of the body from crown of head to sole of foot. 0..1000; 0..250 Units:
|
| Personendaten | Personendaten: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Personendaten | Personendaten: Demografische Daten zu einer Person wie Geburtsdatum und Telefonnummer. |
| Data | |
| Angaben zum Tod | Angaben zum Tod: * |
| Verstorben? | Verstorben?: * |
| Ethnischer Hintergrund | Ethnischer Hintergrund: Detaillierte Beschreibung des ethnischen Hintergrundes einer Person, um Besondheiten, wie Medikamentenverträglichkeit oder Gesundheitsrisiken abzubilden. |
| Ethnischer Hintergrund | Ethnischer Hintergrund: Der ethnische Hintergrund einer Person.
|
| Gender | Gender: Details about the gender of an individual. |
| Data | |
| Administrative gender | Administrative gender: The gender of an individual used for administrative purposes. This element is what most systems today describes as 'Sex' or 'Gender'. For example 'Male', 'Female', 'Other'. This aligns with HL7 FHIR 'Person.gender'. Coding with a terminology is recommended, where possible. Terminology: local_terms
|
| Geschlecht bei der Geburt | Geschlecht bei der Geburt: The sex of an individual determined by anatomical characteristics observed and registered at birth. For example: 'Male', 'Female', 'Intersex'. Coding with a terminology is recommended, where possible. Use the element 'Comment' or the SLOT 'Details' if needed to register more specific details of the individuals gender. |
| Impfstatus | Impfstatus: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Impfung | Impfung: Any activity related to the planning, scheduling, prescription management, dispensing, administration, cessation and other use of a medication, vaccine, nutritional product or other therapeutic item. This is not limited to activities performed based on medication orders from clinicians, but could also include for example taking over the counter medication. |
| Description | |
| Impfstoff | Impfstoff: Name of the medication, vaccine or other therapeutic/prescribable item which was the focus of the activity. For example: 'Atenolol 100mg' or 'Tenormin tablets 100mg'. It is strongly recommended that the 'Medication item' is coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack used. Free text entry should only be used if there is no appropriate terminology available. Terminology: http://snomed.info/sct
|
| Verabreichte Dosis | Verabreichte Dosis: The combination of a medication amount and administration timing for a single day, in the context of a medication order or medication management. For example: '2 tablets at 6pm' or '20mg three times per day'. Please note: this cluster allows multiple occurrences to enable representation of a complete set of dose patterns for a single dose direction. |
| Dosage sequence | Dosage sequence: The intended position of this dosage within the overall sequence of dosages. For example: '1', '2', '3'. Where multiple dosages are expressed, the 'Pattern sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab in the morning, (2) 2 tab at 2pm, (3) 1 tab at night. >=1 |
| Dose amount | Dose amount: The value of the amount of medication administered at one time, as a real number, or range of real numbers, and associated with the Dose unit. For example: 1, 1.5, 0.125 or 1-2, 12.5-20.5 >=0 |
| Clinical indication | Clinical indication: The clinical reason for the medication activity. For example: 'Angina' or 'Pain'. Coding of the indication with a terminology is preferred, where possible. This data element allows multiple occurrences. If only an ACTION is used to record a medication indication, this data element can be used without additional consideration. However, if a clinical indication is recorded for both the Medication order INSTRUCTION and this Medication management ACTION, be aware that these indications might not be consistent." |
| Impfung gegen | Impfung gegen: Reason that the pathway step for the identified medication was carried out. For example: 'Postponed - Patient not avalable at administration time', 'Cancelled - Adverse reaction'. Note: This is not the reason for the medication instruction, but rather the specific reason that a care step was carried out, and will often be used to document some variance from the original order. Terminology: http://snomed.info/sct
|
| Unbekannter Impfstatus | Unbekannter Impfstatus: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording. |
| Data | |
| Absence statement | Absence statement: Positive statement that no information is available. For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used". Terminology: http://hl7.org/fhir/uv/ips/CodeSystem/absent-unknown-uv-ips
|
| Protocol | |
| Last updated | Last updated: The date at which the absence was last updated. |
| SARS-CoV-2 Exposition | SARS-CoV-2 Exposition: A generic section header which should be renamed in a template to suit a specific clinical context. |
| SARS-CoV-2 Exposition | SARS-CoV-2 Exposition: Risk assessment for an individual who may have been exposed to an infectious agent. |
| Data | |
| Infectious agent | Infectious agent: Identification of the organism, material, symptoms or condition to which the individual has been exposed.
|
| Exposition vorhanden? | Exposition vorhanden?: Narrative description about the overall exposure. Terminology: http://snomed.info/sct
|
| Specific exposure details | Specific exposure details: Details about a single exposure. Multiple exposures can be recorded, using one instance of this cluster per exposure. |
| Description of exposure | Description of exposure: Details about the method of exposure. For example: airborne, direct contact, or needle stick.
|
| Date/time of exposure | Date/time of exposure: Date and time of exposure. Can be cloned in template and renamed for specific Date/time at onset of exposure and cessation of exposure. |
| Schwangerschaftsstatus | Schwangerschaftsstatus: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Pregnancy status | Pregnancy status: Statement about whether the individual is or may be pregnant or not. |
| Data | |
| Any event | Any event: * |
| Data | |
| Status | Status: Is there a pregnancy present? Terminology: http://loinc.org
|
| Körpertemperatur | Körpertemperatur: A generic section header which should be renamed in a template to suit a specific clinical context. |
| Body temperature | Body temperature: A measurement of the body temperature, which is a surrogate for the core body temperature of the individual. |
| Data | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Data | |
| Temperature | Temperature: The measured temperature. 0..100; 30..200 Units:
|
| Protocol | |
| Location of measurement | Location of measurement: Simple description about the site of measurement.
|
| Other contributors | Erenik Krasniqi |