| TEMPLATE ID | SR_HLA-Befund |
|---|---|
| Concept | SR_HLA-Befund |
| Description | Zur Dokumentation von HLA-Befunden eines Patienten. |
| Use | Zur Repräsentation des HLA-Befunds eines Patienten inklusive der HLA-Typisierung. |
| Purpose | Zur Dokumentation von HLA-Befunden eines Patienten. |
| References | |
| Authors | Name: Nina Schewe; Organisation: Hochschule Hannover; Email: nina.schewe@hs-hannover.de |
| Other Details Language | Name: Nina Schewe; Organisation: Hochschule Hannover; Email: nina.schewe@hs-hannover.de |
| Other Details (Language Independent) |
|
| Keywords | HLA; Antikörper; Screening; Spezifität; HLA-Befund; HvG-Mismatch; Spezifizierung |
| Language used | en |
| Citeable Identifier | 1246.169.505 |
| Root archetype id | openEHR-EHR-COMPOSITION.report-result.v1 |
| HLA-Befund | HLA-Befund: Document to communicate information to others about the result of a test or assessment. |
| Other Context | |
| Case identification | Case identification: To record case identification details for public health purposes. |
| Fallnummer | Fallnummer: The identifier of this case. |
| HLA-Screening | HLA-Screening: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| 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)'.
|
| Laboratory analyte result | Laboratory analyte result: The result of a laboratory test for a single analyte value. |
| Analyte name | Analyte name: 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}]
|
| Analyte result | Analyte result: 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}]
|
| HLA-Spezifität | HLA-Spezifität: 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}] |
| Test method | Test method: Description about the method used to perform the test. Coding with a terminology is desirable, where possible. |
| HLA-Spezifizierung | HLA-Spezifizierung: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| 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)'.
|
| Laboratory analyte result | Laboratory analyte result: The result of a laboratory test for a single analyte value. |
| Analyte name | Analyte name: 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}]
|
| Analyte result | Analyte result: 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}] |
| HLA-Spezifität | HLA-Spezifität: 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}] |
| Test method | Test method: Description about the method used to perform the test. Coding with a terminology is desirable, where possible. |
| HLA-Patiententypisierung | HLA-Patiententypisierung: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| 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)'.
|
| Laboratory test panel | Laboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing. |
| Laboratory analyte result | Laboratory analyte result: The result of a laboratory test for a single analyte value. |
| Analyte name | Analyte name: 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}]
|
| Analyte result | Analyte result: 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}] |
| HLA-Spendertypisierung | HLA-Spendertypisierung: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| 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)'.
|
| Laboratory test panel | Laboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing. |
| Laboratory analyte result | Laboratory analyte result: The result of a laboratory test for a single analyte value. |
| Analyte name | Analyte name: 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}]
|
| Analyte result | Analyte result: 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}] |
| HvG-Mismatch | HvG-Mismatch: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual. |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| 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)'.
|
| Laboratory analyte result | Laboratory analyte result: The result of a laboratory test for a single analyte value. |
| untersuchter HvG-Mismatch | untersuchter HvG-Mismatch: 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}] |
| DSA | DSA: 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}] |
| HLA-Spezifität | HLA-Spezifität: 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}] |
| Test method | Test method: Description about the method used to perform the test. Coding with a terminology is desirable, where possible. |