> 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/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/7-task-oriented-analytics/7.1-point-of-care-analytics/7.1.3-point-of-care-reporting.md).

# Point of Care Reporting

When it comes to reporting needs, the preference of most clinicians is to 'collect once and use many times'. SNOMED CT enables this goal to be achieved by allowing data to be captured at the appropriate level of detail and then queried at the same or less detailed level. SNOMED CT supports point of care reporting requirements using any (or all) of the SNOMED CT analytics techniques described before, including subsets, subsumption, defining relationships and description logic. Examples of point of care reporting requirements may include:

* Helping clinicians remember preventative services (reminders)
* Identifying patients with care gaps and risk factors
* Monitoring patient compliance with prescribed treatments
* Reporting clinical data to registries, such as cancer, stroke, and infectious disease registries
* Billing and reimbursement[1](https://confluence.ihtsdotools.org/display/DOCANLYT/7.1.3+Point+of+Care+Reporting#Footnote1)

When supporting a reporting requirement in which double counting must be avoided (such as statistical reporting, administrative reporting, billing, or reimbursement), SNOMED CT codes can be mapped to statistical classifications (such as ICD-9 and ICD-10).

When the source data uses a coding system without the same reporting capabilities as SNOMED CT, or when a variety of coding systems are used, coded data can be mapped into SNOMED CT to support the reporting requirements.

***

<table><thead><tr><th width="100.28515625">Footnotes Ref</th><th>Notes</th></tr></thead><tbody><tr><td>1</td><td>Note: In some healthcare environments this is a point of care activity, while in others it is not.</td></tr></tbody></table>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Data+Analytics+Guide&#x26;entry.670899847=Point%20of%20Care%20Reporting" class="button primary">Provide Feedback</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/7-task-oriented-analytics/7.1-point-of-care-analytics/7.1.3-point-of-care-reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.