TEMPLATE Nephro_HLA Befund (Nephro_HLA Befund)

TEMPLATE IDNephro_HLA Befund
ConceptNephro_HLA Befund
DescriptionZur Repräsentation der Ergebnisse einer HLA-Untersuchung eines Patienten im Rahmen des NephroDigital-Projektes.
UseZur Darstellung der Ergebnisse einer HLA-Untersuchung.
PurposeZur Repräsentation der Ergebnisse einer HLA-Untersuchung eines Patienten im Rahmen des NephroDigital-Projektes.
References
AuthorsName: Nina Schewe; Organisation: Medizinische Hochschule Hannover; Email: Schewe.Nina@mh-hannover.de
Other Details LanguageName: Nina Schewe; Organisation: Medizinische Hochschule Hannover; Email: Schewe.Nina@mh-hannover.de
Other Details (Language Independent)
  • MetaDataSet:Sample Set : Template metadata sample set
KeywordsHLA; Antikörper; DSA; HvG; Mismatch; HLA Screening; HLA Spezifizierung
Language useden
Citeable Identifier1246.169.995
Root archetype idopenEHR-EHR-COMPOSITION.report-result.v1
HLA BefundHLA Befund: Document to communicate information to others about the result of a test or assessment.
Other Context
Case identificationCase identification: To record case identification details for public health purposes.
Case identifierCase identifier: The identifier of this case.
HLA-ScreeningHLA-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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • HLA-Screening
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
Analyte nameAnalyte 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}]
  • HLA-Klasse I
  • HLA-Klasse II
Analyte resultAnalyte 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}]
  • positiv
  • negativ
HLA-SpezifitätHLA-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 methodTest method: Description about the method used to perform the test.
Coding with a terminology is desirable, where possible.
HLA-SpezifizierungHLA-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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • HLA-Spezifizierung
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
Analyte nameAnalyte 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}]
  • HLA-Klasse I
  • HLA-Klasse II
Analyte resultAnalyte 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ätHLA-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 methodTest method: Description about the method used to perform the test.
Coding with a terminology is desirable, where possible.
HLA-PatiententypisierungHLA-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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • HLA-Patiententypisierung
Laboratory test panelLaboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing.
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
Analyte nameAnalyte 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}]
  • HLA-A
  • HLA-B
  • HLA-C
  • HLA-DRB1
  • HLA-DQB1
  • HLA-DQA1
  • HLA-DPB1
  • HLA-DRB3
  • HLA-DRB4
  • HLA-DRB5
  • HLA-DPA1
Analyte resultAnalyte 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-SpendertypisierungHLA-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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • HLA-Spendertypisierung
Laboratory test panelLaboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing.
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
Analyte nameAnalyte 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}]
  • HLA-A
  • HLA-B
  • HLA-C
  • HLA-DRB1
  • HLA-DQB1
  • HLA-DQA1
  • HLA-DPB1
  • HLA-DRB3
  • HLA-DRB4
  • HLA-DRB5
  • HLA-DPA1
Analyte resultAnalyte 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-MismatcheHvG-Mismatche: 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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • HvG-Mismatche
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
HvG-MismatchHvG-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}]
Donorspezifische AntikörperDonorspezifische Antikörper: 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ätHLA-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 methodTest method: Description about the method used to perform the test.
Coding with a terminology is desirable, where possible.
Panel reactive AntibodiesPanel reactive Antibodies: 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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Test nameTest 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)'.
  • Panel reactive Antibodies
Laboratory analyte resultLaboratory analyte result: The result of a laboratory test for a single analyte value.
Analyte nameAnalyte 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 resultAnalyte 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}]
Units: %