| TEMPLATE ID | GECCO_Serologischer Befund |
|---|---|
| Concept | GECCO_Serologischer Befund |
| Description | Das Template dient dazu einen serologischen Befund strukturiert abzubilden. |
| Use | Für die Abbildung eines serologischen Befundes. |
| Misuse | Nicht zur Repräsentation von Laborbefunden anderer Bereiche wie der klinischen Chemie. Nicht zur Repräsentation von mikrobiologischen Befunden. Nicht zur Repräsentation von virologischen Befunden (PCR, Antigen, ...). |
| Purpose | Das Template dient dazu einen serologischen Befund strukturiert abzubilden. |
| References | |
| Authors | name: Antje Wulff; organisation: Peter L. Reichertz Institut für Medizinische Informatik; email: antje.wulff@plri.de |
| Other Details Language | name: Antje Wulff; organisation: Peter L. Reichertz Institut für Medizinische Informatik; email: antje.wulff@plri.de |
| Other Details (Language Independent) |
|
| Keywords | Serologischer Befund; Antibodies; Antikörper |
| Language used | en |
| Citeable Identifier | 1246.169.1516 |
| Root archetype id | openEHR-EHR-COMPOSITION.registereintrag.v1 |
| GECCO_Serologischer Befund | GECCO_Serologischer Befund: Generic compilation to represent a data set for research purposes. |
| Other Context | |
| Status | Status: Status of the supplied data for the register entry. Note: This is not the status of individual components.
|
| Kategorie | Kategorie: The classification of the register entry (e.g. type of observation of the FHIR profile). Terminology: http://terminology.hl7.org/CodeSystem/observation-category
|
| Kategorie (LOINC) | Kategorie (LOINC): The classification of the register entry (e.g. type of observation of the FHIR profile). Terminology: LOINC
|
| Befund | Befund: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that 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 | |
| Test name | Test name: Name of the laboratory investigation performed on the specimen(s). A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'. Terminology: http://snomed.info/sct
Annotations
|
| Laboratory test panel | Laboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing. |
| Pro Analyt | Pro Analyt: The result of a laboratory test for a single analyte value. |
| Virusnachweistest | Virusnachweistest: The name of the analyte result. The value for this element is normally supplied in a specialisation, in a template or at run-time to reflect the actual analyte. For example: 'Serum sodium', 'Haemoglobin'. Coding with an external terminology is strongly recommended, such as LOINC, NPU, SNOMED CT, or local lab terminologies. Optional[{fhir_mapping=Observation.code, hl7v2_mapping=OBX.3}] Value set: terminology://fhir.hl7.org/ValueSet/$expand?url=https://www.netzwerk-universitaetsmedizin.de/fhir/ValueSet/sars-cov-2-detection-combined Annotations
|
| Nachweis | Nachweis: The value of the analyte result. For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details. Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}] Value set: terminology://fhir.hl7.org/ValueSet/$expand?url=https://www.netzwerk-universitaetsmedizin.de/fhir/ValueSet/detected-not-detected-inconclusive |
| null_flavour | |
| Quantitatives Ergebnis | Quantitatives Ergebnis: The value of the analyte result. For example '7.3 mmol/l', 'Raised'. The 'Any' data type will need to be constrained to an appropriate data type in a specialisation, a template or at run-time to reflect the actual analyte result. The Quantity data type has reference model attributes that include flags for normal/abnormal, reference ranges and approximations - see https://specifications.openehr.org/releases/RM/latest/data_types.html#_dv_quantity_class for more details. Optional[{fhir_mapping=Observation.value[x], hl7v2_mapping=OBX.2, OBX.5, OBX.6, OBX.7, OBX.8}] |
| Result status | Result status: The status of the analyte result value. The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'. This element allows multiple occurrences to support use cases where more than one type of status need to be implemented. Optional[{fhir_mapping=Observation.status, hl7v2_mapping=OBX.11}]
Annotations
|
| Protocol | |
| Test request details | Test request details: Details about the test request. In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result. As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'. |
| Anforderung | Anforderung: Name of the original laboratory test requested. This data element is to be used when the test requested differs from the test actually performed by the laboratory. Terminology: LOINC
|
| Other contributors | Sarah Ballout; Anneka Sargeant; Eugenia Rinaldi; Cora Drenkhahn; Infection Control Study Group |