# FHIR and SWEC Comparison

In the context of this SNOMED implementation guide, we have chosen to use the FHIR context model as an example of an information model for several reasons. FHIR is a widely adopted standard in the healthcare industry for exchanging electronic health records and related data. Its modular and extensible design makes it an ideal candidate to demonstrate how context information can be represented outside terminologies like SNOMED CT.

Here is your table cleanly formatted and optimized for GitBook, using Markdown and consistent styling for readability and responsiveness.

***

## Clinical Findings with Context vs. FHIR Resources

\
The following table maps SNOMED CT “Situations with Explicit Context” subhierarchies to relevant FHIR resources, showing how clinical context is represented across terminology and information models.

<table data-full-width="true"><thead><tr><th>SNOMED CT Situation (Subhierarchy)</th><th>FHIR Resource</th><th>Domain</th><th>Context</th><th>Subject</th><th>Temporal Context</th></tr></thead><tbody><tr><td>417662000 |History of clinical finding in subject (situation)|</td><td>Condition</td><td>Clinical finding</td><td>Known present</td><td>Subject of record</td><td>In the past</td></tr><tr><td>416471007 |Family history of clinical finding (situation)|</td><td>FamilyMemberHistory</td><td>Clinical finding</td><td>Known present</td><td>Person in the family</td><td>Current or past</td></tr><tr><td>160266009 |No family history of clinical finding (situation)|</td><td><em>(None / N/A)</em></td><td>Clinical finding</td><td>Known absent</td><td>Person in the family</td><td>All times of past</td></tr><tr><td>1260502004 |History of event in life of subject (situation)|</td><td>Condition</td><td>Event</td><td>Known present</td><td>Subject of record</td><td>In the past</td></tr><tr><td>373572006 |Clinical finding absent (situation)|</td><td>Observation</td><td>Clinical finding</td><td>Known absent</td><td>Subject of record</td><td>Current or specified time</td></tr><tr><td><em>History Events with finding context</em></td><td>Observation</td><td>Event</td><td>Known absent</td><td>Subject of record</td><td>Current or specified time</td></tr><tr><td>373573001 |Clinical finding present (situation)|</td><td>Condition</td><td>Clinical finding</td><td>Known present</td><td>Subject of record</td><td>Current</td></tr><tr><td>443859009 |Possible clinical finding (situation)|</td><td>Condition</td><td>Clinical finding</td><td>Known possible</td><td>Subject of record</td><td>Current or specified time</td></tr><tr><td>443938003 |Procedure carried out on subject (situation)|</td><td>Procedure</td><td>Procedure</td><td>Done</td><td>Subject of record</td><td>Current or specified time</td></tr><tr><td>416237000 |Procedure not done (situation)|</td><td>Procedure</td><td>Procedure</td><td>Not done</td><td>Subject of record</td><td>Current or specified time</td></tr><tr><td>439763000 |Procedure on family member (situation)|</td><td>Procedure</td><td>Procedure</td><td>—</td><td>Person in the family</td><td>Current or specified time</td></tr></tbody></table>

***

#### Notes

* Where FHIR Resource is listed as N/A, there may be no direct mapping in the base FHIR specification.
* Context properties such as subject and temporal frame help clarify how the SNOMED concept aligns with FHIR resource attributes like subject, status, or effective\[x].

## Clinical Findings with Context vs. FHIR Resources

The table below maps specific types of Situations with Explicit contexts to specific FHIR resources and states the associated context properties

### Attributes vs. FHIR Resource Elements

As seen in the previous table, depending on the type of context represented in the SWEC concept, it can be transformed into a Condition or Observation resource. Here, we provide some examples of values for different key elements.

#### Condition Resource vs. |History of clinical finding in subject|

<table data-full-width="false"><thead><tr><th>FHIR Element Name</th><th>FHIR Element Value</th><th>SNOMED Attribute</th><th>SNOMED Value</th></tr></thead><tbody><tr><td>Condition.clinicalStatus</td><td>inactive</td><td>Temporal context</td><td>In the past</td></tr><tr><td>Condition.code</td><td>Clinical finding</td><td>Associated finding</td><td>&#x3C;&#x3C; Clinical finding</td></tr></tbody></table>

#### Condition Resource vs. |Clinical finding present|

| FHIR Element Name        | FHIR Element Value | SNOMED Attribute   | SNOMED Value        |
| ------------------------ | ------------------ | ------------------ | ------------------- |
| Condition.clinicalStatus | active             | Temporal context   | Current             |
| Condition.code           | Clinical finding   | Associated finding | << Clinical finding |

#### Observation Resource vs. |Clinical finding absent|

| FHIR Element Name | FHIR Element Value | SNOMED Attribute   | SNOMED Value        |
| ----------------- | ------------------ | ------------------ | ------------------- |
| Observation.code  | Clinical finding   | Associated finding | << Clinical finding |
| Observation.value | Known absent       | Finding context    | Known absent        |

#### Procedure Resource vs |Procedure Done|

| FHIR Element Name    | FHIR Element Value | SNOMED Attribute        | SNOMED Value            |
| -------------------- | ------------------ | ----------------------- | ----------------------- |
| Procedure.code       | Procedure          | Associated procedure    | << Procedure            |
| Procedure.status     | Completed          | Procedure context       | Done                    |
| Procedure.category   | Surgical           | (Ancestor)              | Surgical procedure      |
| Procedure.reasonCode | Disease            | Has focus               | << Clinical finding     |
| Procedure.bodySite   | Body site          | Procedure site - direct | << Anatomical structure |

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Context+Representation+Guide&#x26;entry.670899847=FHIR%20and%20SWEC%20Comparison" 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/implementation-guides/context-representation-implementation-guide/6-technical-application/6.3-context-representation-transformations/6.3.1-fhir-and-swec-comparison.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.