# Historical Summaries

One major ambition of healthcare IT is to make effective summaries of a patient's clinical history available to healthcare providers (especially in emergency situations). Typically a patient's clinical data is scattered across a number of healthcare institutions using a variety of information models and coding systems. Even within a single institution patient data may be captured across many episodes of care, many devices, and often many software systems.

SNOMED CT can help to support the integration of this information by serving as a common reference terminology into which other code systems can be mapped. It can also be used to unlock clinical data that was captured by source systems in free text narrative, and to summarize large volumes of data by grouping codes together into more general categories. SNOMED CT can also be used to enable clinicians to filter large volumes of data to select those records that are relevant to the current care episode – for example identifying all previous records of a heart attack.

One significant example of this is the UK NHS Summary Care Record (SCR) service,[1](https://confluence.ihtsdotools.org/display/DOCANLYT/7.1.1+Historical+Summaries#Footnote1) which uses SNOMED CT to represent a number of types of clinical information including medical history, medications, adverse reactions and allergies. This service uses a summary extracted from detailed patient care records held in a variety of disparate systems. Where the source data is not stored natively in SNOMED CT, they are mapped into SNOMED CT prior to transmission. Over 40 million people in England (80% of the population) now have a summary care record. This service now contributes to the safe and efficient assessment and treatment of these people, and has greatly improved the accuracy and timeliness of medicines reconciliation.

***

<table><thead><tr><th width="74.38671875">Footnotes Ref</th><th>Notes</th></tr></thead><tbody><tr><td>1</td><td><em>Vendor Introduction to SNOMED CT</em> , 2015, <a href="http://snomed.org/vendorintro">http://snomed.org/vendorintro</a>.</td></tr><tr><td>2</td><td>S. Sachdea, <em>SCR reaches 40m patients</em> , E-Health Insider, 2 July 2014, <a href="http://www.digitalhealth.net/news/29744/scr-reaches-50m-patients">www.digitalhealth.net/news/29744/scr-reaches-50m-patients</a>.</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=Historical%20Summaries" class="button primary">Provide Feedback</a>


---

# 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-data-analytics-guide/7-task-oriented-analytics/7.1-point-of-care-analytics/7.1.1-historical-summaries.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.
