> 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-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/record-artifact.md).

# Record Artifact

<table><thead><tr><th width="298.8697509765625">Definition</th><th>Examples</th></tr></thead><tbody><tr><td>Clinical documents, or parts thereof</td><td><ul><li>422813005 | Document section (record artifact) |</li><li>416575001 | Perioperative record (record artifact) |</li></ul></td></tr></tbody></table>

A r*ecord artifact* is an entity that is created by a person or persons for the purpose of providing other people with information about events or states of affairs.

* In general, a record is *virtual*, that is, it is independent of its particular physical instantiation/s. It consists of information elements (usually words, phrases and sentences, but also numbers, graphs, and other information elements).

Record artifacts need not be complete reports or records. They can be parts of a larger Record artifact.

* For example,
  * A 184225006 | Computer record of patient (record artifact)| is a Record artifact that also may contain other Record artifacts in the form of individual documents or reports, e.g., 726738003 | Cytology report (record artifact)|. These may, in turn, contain more finely granular Record artifacts, such as sections, and even section headers, e.g., 422813005 | Document section (record artifact)|.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Record%20Artifact" class="button primary">Provide Feedback</a>


---

# 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-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/record-artifact.md?ask=<question>&goal=<endgoal>
```

`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.