> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/logicnets-software-component-details/healthcare-integration-interoperability-suite/informatics-runtime-module-ln-inr.md). # Informatics Runtime Module (LN-INR) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-b325112eeee12a9fe2d2201fa15b43e7321cb54d%2F2d058e1e-72fe-402b-a6d9-f3ce97c05f1c.png?alt=media) ### License: Per User of Informatics-enabled Applications 1. Supports use of both named and concurrent user licenses 2. Transaction or system licenses can also be made available on request. ### LN-INR Description The Informatics Runtime Module enables the LogicNets base system and its overlying frameworks to dynamically map and render the informatics data values linked to the data object model in the application’s design as well as the coding information from integrated external healthcare applications. This applies both for data entering an application via web services and the application-generated results, whether displayed on screen, incorporated into documents or included in structured output such as FHIR, XML, etc sent back to the clinical workflow. This module works in conjunction with the Informatics Authoring Module to allow external clinical workflow applications to communicate standard healthcare concepts into a LogicNets application, mapping them to the underlying concepts that drive the modeled logic and to receive computed results back in the desired coded format. ### Services and Deployment Considerations Generally, the Informatics Runtime module does not require any professional services. PG-HE2-231127 --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community-test.logicnets.com/release-9/logicnets-software-component-details/healthcare-integration-interoperability-suite/informatics-runtime-module-ln-inr.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.