> 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/logicnets-voice-recognition-connector-ln-voi.md). # LogicNets Voice Recognition Connector (LN-VOI) ### License: Per User of Voice-driven LogicNets Applications 1. Supports use of both named and concurrent user licenses 2. Currently available in conjunction with the Assessment Framework (ASF) 3. Requires separate acquisition from the provider of the integrated Voice Recognition product including any required audio equipment. LogicNets does not provide support for these components. 4. Currently supported vendors:, G2 Speech ### LN-VOI Description The LogicNets Voice Recognition Connector allows supported Use Case Frameworks (in particular the ASF) to operate in conjunction with integrated voice recognition systems. The feature allows the framework to be configured to react to voice-driven commands. Users can speak the name of navigation options from the Framework display. They can specify any displayed topic tab they wish to activate and indicate the name of the question they wish to answer. Having navigated to an item, they can then speak the data entry. For pre-set selection inputs, they speak the caption label. They can also speak free-form numeric and text values for text and number inputs. Commands to delete or amend incorrect responses are included. LogicNets currently supports Voice Recognition tools from G2 Speech (a Recognosco-based system). Application admins access and set VR configuration options through the Use Case Framework configuration interface. ### Services and Deployment Considerations The LogicNets Voice Recognition Connector requires Deployment Services (LN-DS) for integration into any user environment. Services can include: * Training for application admins including integration into applications and use of configuration tools for the feature. PG-HE5-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/logicnets-voice-recognition-connector-ln-voi.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.