# Lookup Code

This transaction allows a PoS, or any OHIE component, to access terminological information in the terminology service to retrieve detailed information on a code.  A typical example would be to retrieve descriptive information on a laboratory code from the LOINC Code System.&#x20;

Both external systems and systems inside the HIE may perform this transaction directly with the TS. The sequence diagram below shows the steps that occur for a system using this transaction.  &#x20;

1. Lookup: Retrieve information on Code '26453-1' in the LOINC Code System.

| Workflow Maturity             | <p><img src="https://lh5.googleusercontent.com/Vp6XBRGu-U_Dmd5EKNpCZvEEum0CxOcHOj9NgHh8UMMNLMlXHmLcUE_YWueDRr4uqWLzpPfzSBLJ2k33XQIelLypjQ4wyrD17-t33GtLa8fFxW9AYDvXhiJmBl4VaLgKDg" alt=""></p><p>    <strong>Mature</strong></p> | <p></p><ul><li><strong>One or more OpenHIE implementations of this workflow exist  in one or more countries</strong></li><li><strong>Workflow is defined and ARB approved</strong></li><li><strong>Workflow is supported by mature standards</strong></li></ul>                                                                                                                                                                                                                                                                           |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Standards\*                   |                                                                                                                                                                                                                                  | <p>The FHIR CodeSystem lookup operation: <a href="https://www.hl7.org/fhir/codesystem-operation-lookup.html"><https://www.hl7.org/fhir/codesystem-operation-lookup.html></a>. HL7 FHIR Specifications v3.0 or higher support lookup. The response is an object that contains details about the code, including definition, status, designations, and properties.</p><p>This workflow implements the IHE IT Infrastructure Technical Framework Supplement - Sharing Valuesets, Codes, and Maps (SVCM) Transaction: Lookup Code ITI-Y4.</p> |
| Assumptions and Prerequisites |                                                                                                                                                                                                                                  | The required CodeSystems have been preloaded into the Terminology Service and the specified code exists in the Code System.                                                                                                                                                                                                                                                                                                                                                                                                               |
| Actors                        |                                                                                                                                                                                                                                  | <p></p><ul><li>PoS - The point-of-service system  or other HIE component that is requesting to lookup a code.  </li><li>TS - Stores the curated official version of the terminology and codes for the health system.</li></ul>                                                                                                                                                                                                                                                                                                            |

## Interaction Description&#x20;

The following is a description of the interaction steps.&#x20;

![](https://lh4.googleusercontent.com/IVUu_eE18fSlBI25iBniQ7y4DPM7qCbf8_30UqeFWSWl-DNM8FdYCzAIqRnBsMJMcogU1GbsA0VjBplO4eTX9cushkPFDEHoefAUp4vyMdHlqlnI2OT3rx7XFhl9FsZBXQ)

| Ref | Interaction          | Data                                                                                                                               | Transaction Options                         |
| --- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| 1   | Code Lookup request  | <p>The validate-code request is triggered by a PoS or other HIE component.</p><p>Input: A Concept Code and target Code System.</p> | FHIR CodeSystem Resource, $lookup operation |
| 2   | Code Lookup response | <p>The response is sent back to the requesting system.</p><p>Output: an object containing code information.</p>                    | FHIR CodeSystem Resource, $lookup operation |

<br>


---

# 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://guides.ohie.org/arch-spec/introduction/terminology-service-workflow/lookup-code.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.
