# model of use

## model of use

An information model designed to align with or meet specific intended purpose.

#### Notes

* A *model or use* may represent information in a way that directly relates to the way data was captured or specific requirements for reporting arising from a particular use case.
* In contrast, a model of meaning provides a common representation of particular types of information that supports a range of different uses.

#### Examples

* Family history information be recorded in different ways depending on when and how the data was collected. Three of the many possible methods of collection are shown below.

| **Method of Collection**                       | **Possible Model of Use Record**                                   |
| ---------------------------------------------- | ------------------------------------------------------------------ |
| Checkbox in a questionnaire                    | "Yes" recorded against the label "Family history of heart disease" |
| Coded entry in a family history record section | Family history record entry containing: \[ 56265001                |
| Coded entry from a picklist or search          | Clinical record entry containing: \[ 275120007                     |

* A decision support rule may need to show an alert in patients with a family history of heart disease. An effective *model of meaning* needs to ensure the required information is accessible to the rules engine irrespective of the way it was originally recorded. The table below shows one way to resolve each of three *model of use* records into a common form to support effective retrieval.

| **Model of Use Record**                                            | **Possible Model of Meaning Resolutions**                 |
| ------------------------------------------------------------------ | --------------------------------------------------------- |
| "Yes" recorded against the label "Family history of heart disease" | Map "Yes" response to questionnaire entry to \[ 275120007 |
| Family history record entry containing: \[ 56265001                | Heart disease                                             |
| Clinical record entry containing: \[ 275120007                     | Family history: Cardiac disorder                          |

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=model%20of%20use" 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-international-documents/snomed-ct-glossary/m/model-of-use.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.