TEMPLATE GECCO_Virologischer Befund (GECCO_Virologischer Befund)

TEMPLATE IDGECCO_Virologischer Befund
ConceptGECCO_Virologischer Befund
DescriptionDas Template dient dazu einen virologischen PCR- oder Antigentest-Befund strukturiert abzubilden.
UseFür die Abbildung eines virologischen Befundes als PCR- oder Antigentest.
MisuseNicht zur Repräsentation von Laborbefunden anderer Bereiche wie der klinischen Chemie. Nicht zur Repräsentation von mikrobiologischen Befunden.
PurposeDas Template dient dazu einen virologischen PCR- oder Antigentest-Befund strukturiert abzubilden.
References
Authorsname: Antje Wulff; organisation: Peter L. Reichertz Institut für Medizinische Informatik; email: antje.wulff@plri.de
Other Details Languagename: Antje Wulff; organisation: Peter L. Reichertz Institut für Medizinische Informatik; email: antje.wulff@plri.de
Other Details (Language Independent)
  • MetaDataSet:Sample Set : Template metadata sample set
  • MD5-CAM-1.0.1: b5681676880594d6c4d27ae91d5182cf
  • PARENT:MD5-CAM-1.0.1: CD5C7EF669BF9300C4CE104319009B71
  • Original Language: ISO_639-1::de
  • Sem Ver: 3.0.0
KeywordsVirologischer Befund; PCR; Antigen; SARS-CoV-2; Corona; Virus; Befund; Nachweis
Language useden
Citeable Identifier1246.169.1454
Root archetype idopenEHR-EHR-COMPOSITION.registereintrag.v1
GECCO_Virologischer BefundGECCO_Virologischer Befund: Generic compilation to represent a data set for research purposes.
Other Context
StatusStatus: Status of the supplied data for the register entry. Note: This is not the status of individual components.
  • registered 
  • preliminary 
  • final 
  • amended 
KategorieKategorie: The classification of the register entry (e.g. type of observation of the FHIR profile).
Terminology: http://terminology.hl7.org/CodeSystem/observation-category
  • Laboratory 
Kategorie (LOINC)Kategorie (LOINC): The classification of the register entry (e.g. type of observation of the FHIR profile).
Terminology: http://loinc.org
  • Laboratory studies (set) 
BefundBefund: 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 eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
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)'.
Terminology: http://snomed.info/sct
  • Detection of virus (procedure) 

Annotations

  • 26436-6: laboratory
Laboratory test panelLaboratory test panel: Laboratory test result as a panel/battery/profile structure common to clinical pathology testing.
Pro AnalytPro Analyt: The result of a laboratory test for a single analyte value.
VirusnachweistestVirusnachweistest: 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}]
Terminology: LOINC
  • SARS-CoV-2 (COVID-19) RNA [Presence] in Respiratory specimen by NAA with probe detection 

Annotations

  • Hl7V2 Mapping: OBX.3
  • Fhir Mapping: Observation.code
NachweisNachweis: 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

Annotations

  • Hl7V2 Mapping: OBX.2, OBX.5, OBX.6, OBX.7, OBX.8
  • Fhir Mapping: Observation.value[x]
Result statusResult 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}]
  • registered
  • preliminary
  • final
  • amended
  • corrected
  • cancelled
  • entered-in-error
  • unknown

Annotations

  • Hl7V2 Mapping: OBX.11
  • Fhir Mapping: Observation.status
Other contributorsSarah Ballout; Anneka Sargeant; Eugenia Rinaldi; Cora Drenkhahn; Infection Control Study Group