> 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-authoring-module-ln-inf.md). # Informatics Authoring Module (LN-INF) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-27bbdf163173fea3a31d1a854f2025d62ce30976%2Fbba4709f-04c4-4b7f-a207-c116f878bd3e.png?alt=media) ### License: Per Designer User Notes: 1. Must be licensed in conjunction with the Informatics Runtime Module in order for informatics handling to be executed in LogicNets runtime applications. 2. May be licensed separately to support modeled guideline exports for use with external runtime systems ### LN-INF Description The LogicNets Informatics Authoring Module enables a series of features in the LogicNets Designer environment to support the use of healthcare informatics. Activating Informatics Authoring adds additional functionality to the LogicNets Designer parts and data table editors so that healthcare informatics code sets with critical meta data can be directly entered and easily associated with data objects within the author’s data model. Data sets can also be imported or setup and managed in bulk with informatics options available to identify and properly label code sets associated with specified fields. Informatics can thereby be used as important metadata components in mapping modeled data and logic concepts to health information. ### Services and Deployment Considerations LogicNets offers training services (LN-TS) to assist designer users in working with informatics in their modeled content. LogicNets offers Design and Deployment services (LN-DS) to implement informatics support with specific coding systems including the ability to integrate to code system websites to dynamically find, assign, and confirm values. These services usually require development and acceptance by customer of a formal SoW PG-HE1-250101 --- # 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-authoring-module-ln-inf.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.