> 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-international-documents/snomed-ct-glossary/h/human-readable-concept-model.md).
# human readable concept model
## human readable concept model
A rendering of the machine readable concept model rules designed to be included in guidance documents.
#### Notes
* The *human readable concept model* is generated by processing the machine readable concept model to ensure that it accurately reflects the rules.
* The *human readable concept model* is presented in tables that organize the information from the perspective of concept model domains and attributes. These tables include:
* Expression constraint language representations of domains and ranges;
* Constraints on attribute cardinality and attribute in group cardinality.
* Selected *human readable concept model* tables are included in the SNOMED CT Editorial Guide and will also appear where relevant in other SNOMED CT guides.
## Alternatives
* **HRCM**
##
Provide Feedback
---
# 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-international-documents/snomed-ct-glossary/h/human-readable-concept-model.md?ask=&goal=
```
`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.