You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ISARIC Core CRF captures serology or genomic results indicating the type of pathogen. For example Influenza A/H3N2, Dengue DENV1, Hepatitis type B. WHO T0 form indicates collection of pathogenic agent, strain and subtype as appropriate.
Would it be useful to add this, in addition to the more general pathogen_type variable, to indicate any serology results that are indicated in the source data?
Genomic clade is captured in a separate variable in the G.h schema.
The text was updated successfully, but these errors were encountered:
sadiekelly
changed the title
Consider addition of pathogen type
Consider addition of pathogen type/strain/subtype
Dec 5, 2023
The existing variable 'pathogen' is a constant pre-filled value for the high level name of the pathogen of interest e.g. Hepatitis.
Additional variable(s) can be added to capture types as identified from testing e.g. Hepatitis type A | Hepatitis type B. To be determined for each pathogen type and a dictionary list created. New types may need to be captured as an 'other' free text field initially and coded post data collection.
@sadiekelly taking a look at ICD-11 for this, https://icd.who.int, seems to have the use cases we are thinking of, including major variants of COVID-19, Influenza A subtypes and many other diseases. ICD is for diseases, so may need a subclass for pathogen only
ISARIC Core CRF captures serology or genomic results indicating the type of pathogen. For example Influenza A/H3N2, Dengue DENV1, Hepatitis type B. WHO T0 form indicates collection of pathogenic agent, strain and subtype as appropriate.
Would it be useful to add this, in addition to the more general pathogen_type variable, to indicate any serology results that are indicated in the source data?
Genomic clade is captured in a separate variable in the G.h schema.
The text was updated successfully, but these errors were encountered: