> 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-terminology-services-guide/3-terminology-service-use-cases/ehr-reporting-and-analytics.md). # 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://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/). 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

Practical Requirement	Required Services	Dependendies
Enable the selection of SNOMED CT edition and version to be used. REQUIRED	Select Edition and Version	N/A
Get terms for concepts to use in human readable representations of: Query specifications Reports and analytics results REQUIRED	Get Terms for a Concept	N/A
Apply concept subsumption tests as part of a reporting or analytics query REQUIRED	Get and Test Concept Subtypes and Supertypes	N/A
Apply reference set membership criteria as part of a reporting or analytics query REQUIRED	Get and Test Reference Set Membership	N/A
Validate expression constraints REQUIRED	Validate and Apply Expression Constraints Validate an expression constraint	N/A
Apply an expression constraint query as part of a reporting or analytics query REQUIRED	Validate and Apply Expression Constraints Get all concepts that conform to an expression constraint	N/A
Find concepts to include in a reporting or analytics query including: Concept identifiers for use in expression constraints and queries including: Reference set identifiers for reference set membership tests Supertypes for subsumption tests Attributes and value ranges for using in expression constraints and queries REQUIRED	Find Concepts Get concepts using constrained term searches Get Concept Model Rules Create queries that are consistent with concept model rules	N/A
Include subsumed or equivalent expressions in the results of a reporting or analytics query OPTIONAL	Test Expression Subsumption	N/A

Provide Feedback [^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 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/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/ehr-reporting-and-analytics.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.