> 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/situation-with-explicit-context/situation-with-explicit-context-naming-conventions.md).

# Situation with Explicit Context Naming Conventions

For information on precoordinated naming patterns that have been reviewed or are currently in review, see [Pre-coordination Naming Patterns project](https://conf.spaces.snomed.org/wiki/spaces/IHTSDO1/pages/130978180/Pre-coordination+Naming+Patterns+Project). Unreviewed patterns for the Situation with explicit context hierarchy can be found [here](https://conf.spaces.snomed.org/wiki/spaces/IHTSDO1/pages/130978836/Unreviewed+Patterns+by+Hierarchy). New content should conform with the naming patterns; however, legacy content may not.

* For example,
  * **Acceptable naming pattern**
    * FSN: declined (situation)
    * PT: declined
    * SYN: refused (This is optional).
      * 736013005 |Body weight measurement declined (situation)|

**The following naming patterns are no longer accepted for addition to the International Edition:**

* Procedure offered
* Procedure not offered
* Procedure done
* Procedure not done

Note that 385658003 |Done (qualifier value)| (a descendent of 410523001 |Post-starting action status (qualifier value)|) remains in use as the target value of the 408730004 |Procedure context (attribute)| in *History of \<procedure>* concepts.

Not every naming pattern is found in the Pre-coordination Naming Pattern project. Some naming patterns can be prescribed in [Templates](https://conf.spaces.snomed.org/wiki/spaces/SCTEMPLATES/overview?homepageId=133988366). Others can come from trackers or fast track documents, such as the examples below.

**716186003 |No known allergy (situation)|**

* FSN: No known allergy (situation)
* PT: No known allergy
* SYN: NKA - No known allergy

**428197003 |No known insect allergy (situation)|**

* FSN: No known insect allergy (situation)
* PT: No known insect allergy

## History of finding or disorder occurring in past pregnancy

For concepts relating to a history of a finding, disorder, procedure, or event occurring in a past pregnancy of the subject of the record, use an FSN and PT of |Past pregnancy history of X (situation)|. These concepts are subtypes of 271903000 |History of pregnancy (situation)|.

* For example,
  * 161804005 |Past pregnancy history of antepartum hemorrhage (situation)| is a subtype of 271903000 |History of pregnancy (situation)|

For content relating to *family* history, this must be specified in both the FSN and preferred term to distinguish between past pregnancy of the subject of the medical record.

* For example,
  * |*Past pregnancy history* of neonatal death (situation)| versus |*Family* *history* of neonatal death (situation)|

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Situation%20with%20Explicit%20Context%20Naming%20Conventions" 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/situation-with-explicit-context/situation-with-explicit-context-naming-conventions.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.