# EHR Reporting and Analytics

The design of SNOMED CT facilitates the use of a range of powerful reporting and analytic techniques. For more information about the applications of these techniques, please see the guide to [Data Analytics with SNOMED CT](https://app.gitbook.com/o/h8Z6qGxuQrzM9vbx5bPT/s/uKngFry3XF9A8phdXFe8/). The same techniques can also be employed to support clinical decision support as described in the guide to Decision Support with SNOMED CT.

The table below shows a summary of the terminology services required to support reporting and analytics.

## Services Required to Support EHR Reporting and Analytics

<table data-full-width="true"><thead><tr><th width="371.734375">Practical Requirement</th><th width="341.0703125">Required Services</th><th>Dependendies</th></tr></thead><tbody><tr><td>Enable the selection of SNOMED CT edition and version to be used.<br><br>REQUIRED</td><td><a href="../4-terminology-service-types/4.1-select-edition-and-version">Select Edition and Version</a></td><td>N/A</td></tr><tr><td><p>Get terms for concepts to use in human readable representations of:</p><ul><li>Query specifications</li><li>Reports and analytics results</li></ul><p>REQUIRED</p></td><td><a href="../4-terminology-service-types/4.3-get-terms-for-a-concept">Get Terms for a Concept</a></td><td>N/A</td></tr><tr><td>Apply concept subsumption tests as part of a reporting or analytics query<br><br>REQUIRED</td><td><a href="../4-terminology-service-types/4.5-get-and-test-concept-subtypes-and-supertypes">Get and Test Concept Subtypes and Supertypes</a></td><td>N/A</td></tr><tr><td>Apply reference set membership criteria as part of a reporting or analytics query<br><br>REQUIRED</td><td><a href="../4-terminology-service-types/4.6-get-and-test-reference-set-membership">Get and Test Reference Set Membership</a></td><td>N/A</td></tr><tr><td>Validate expression constraints<br><br>REQUIRED</td><td><p><a href="../4-terminology-service-types/4.7-validate-and-apply-expression-constraints">Validate and Apply Expression Constraints</a></p><ul><li>Validate an expression constraint</li></ul></td><td>N/A</td></tr><tr><td>Apply an <a data-footnote-ref href="#user-content-fn-1">expression constraint query</a> as part of a reporting or analytics query<br><br>REQUIRED</td><td><p><a href="../4-terminology-service-types/4.7-validate-and-apply-expression-constraints">Validate and Apply Expression Constraints</a></p><ul><li>Get all concepts that conform to an expression constraint</li></ul></td><td>N/A</td></tr><tr><td><p>Find concepts to include in a reporting or analytics query including:</p><ul><li><p>Concept identifiers for use in expression constraints and queries including:</p><ul><li>Reference set identifiers for reference set membership tests</li><li>Supertypes for subsumption tests</li><li>Attributes and value ranges for using in expression constraints and queries</li></ul><p>REQUIRED</p></li></ul></td><td><p><a href="../4-terminology-service-types/4.8-find-concepts">Find Concepts</a></p><ul><li>Get concepts using constrained term searches</li></ul><p><a href="../4-terminology-service-types/4.13-get-concept-model-rules">Get Concept Model Rules</a></p><ul><li>Create queries that are consistent with concept model rules</li></ul></td><td>N/A</td></tr><tr><td><p>Include subsumed or equivalent expressions in the results of a reporting or analytics query</p><p>OPTIONAL<br></p></td><td><a href="../4-terminology-service-types/4.15-test-expression-subsumption">Test Expression Subsumption</a></td><td>N/A</td></tr></tbody></table>

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

[^1]: Implementation of expression constraints in a reporting or analytics queries differs from use of a constraints when searching the terminology. When a constraint is applied to a set of instance records it may be necessary to take account of the ways in which data is represented in the EHR. For example, as noted in the previous section, the data entry context may have a meaning binding that modifies the interpretation of a particular concept.


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/ehr-reporting-and-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.