> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/implementation-guides/snomed-ct-guide-for-covid-19/2-coding-covid-19-related-data.md). # Coding COVID-19 Related Data The collection of coded COVID-19 related data can be critical for frontline service delivery, pandemic surveillance, and retrospective data analysis. The following table lists a collection of data elements for which SNOMED CT can be used to capture COVID-19 related data.

\|--- Provider and facility details(\[section 2.1]\( * Healthcare profession * Site of care * Health management finding * Personal protective equipment Patient demographics * Biological sex * Gender identity * Marital or partnership status * Nationality * Ethnic group * Racial group * Occupation * Travel history * Residential location type * Next of kin relationship * Living arrangements * Care and support circumstances Clinical assessment * Symptoms * Severity * Clinical measurements * Clinical examination findings * Diagnosis and certainty * Secondary conditions and complications * Potential risk factors * Comorbidities * Exposure event * Covid-19 and viral co-infections Tests and Investigations * Specimen * Laboratory tests * Radiology procedures * Substances and virus * Laboratory test results * Other investigations Prevention, treatment and education * Prevention * Prevention findings * Education * Medication * Administrative procedures * Therapeutic procedures * Treatment findings * Treatment equipment **Note** The SNOMED CT subsets are provided as a guide only, and may need to be constrained or extended to meet local requirements. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snomed.org/implementation-guides/snomed-ct-guide-for-covid-19/2-coding-covid-19-related-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.