ICIDM-UNASKED-001 · RELATIONSHIP_SPARSE
Why is the Cryptococcus × Whole-genome sequencing relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Cryptococcus · Technology: Whole-genome sequencing · Observed papers: 0
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-002 · RELATIONSHIP_SPARSE
Why is the Arboviruses × Clinical trial / therapy relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Arboviruses · Technology: Clinical trial / therapy · Observed papers: 0
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-003 · RELATIONSHIP_SPARSE
Why is the Aspergillus × Whole-genome sequencing relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Aspergillus · Technology: Whole-genome sequencing · Observed papers: 0
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-004 · RELATIONSHIP_SPARSE
Why is the Staphylococcus aureus / MRSA × Serology / immunology relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Staphylococcus aureus / MRSA · Technology: Serology / immunology · Observed papers: 0
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-005 · RELATIONSHIP_SPARSE
Why is the Bordetella pertussis × Clinical trial / therapy relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Bordetella pertussis · Technology: Clinical trial / therapy · Observed papers: 1
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-006 · RELATIONSHIP_SPARSE
Why is the Influenza / respiratory viruses × Whole-genome sequencing relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Influenza / respiratory viruses · Technology: Whole-genome sequencing · Observed papers: 2
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-007 · RELATIONSHIP_SPARSE
Why is the Streptococcus pneumoniae × Bioinformatics / modelling relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Streptococcus pneumoniae · Technology: Bioinformatics / modelling · Observed papers: 0
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-008 · RELATIONSHIP_SPARSE
Why is the Influenza / respiratory viruses × Bioinformatics / modelling relationship sparse in the publication corpus, and is this a true capability gap, a terminology/classification gap, or simply an unrepresented relationship?
Pathogen: Influenza / respiratory viruses · Technology: Bioinformatics / modelling · Observed papers: 1
Boundary: Publication sparsity does not imply scientific absence or institutional incapability.
Reality Return: Review source classifications and institutional history before deciding whether targeted evidence search or a new experiment is warranted.
CANDIDATE_UNASKEDHI REVIEW REQUIREDICIDM-UNASKED-009 · STALE_OR_DORMANT
The Streptococcus pneumoniae × PCR / molecular diagnostics relationship was recurrent but has not appeared recently in the corpus. Is the capability obsolete, absorbed into newer methods, dormant, or simply relabelled?
Pathogen: Streptococcus pneumoniae · Technology: PCR / molecular diagnostics · Observed papers: 8 · Last signal: 2012
Boundary: No recent publication signal does not prove loss of capability.
Reality Return: Trace later methods, teams, datasets and capability records before treating the relationship as lost.
CANDIDATE_UNASKEDHI REVIEW REQUIRED