> For the complete documentation index, see [llms.txt](https://s-itou-personal.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://s-itou-personal.gitbook.io/home/readme.md). # AI版服薬指導サポートシステム操作マニュアル {% columns %} {% column valign="middle" %} (forestchart-ai) {% endcolumn %} {% column valign="middle" %}

{% endcolumn %} {% endcolumns %} {% hint style="info" %} [**お知らせ** 2026/06/08 ： 6月内で利用可能なサンプル患者の一覧](https://s-itou-personal.gitbook.io/home/sample/) {% endhint %}
Cover image

:leaf:

ログイン操作ログインの方法と注意点はこちら１．ログイン画面login.png

:server:

SOAP分析指導音声の取り込み、分析方法はこちら２．SOAP分析画面mic.png

:terminal:

指導サポート指導前のサポート情報を取得する方法はこちら３．指導サポート画面assistance.png
✅監査サポート現在飲んでいる薬の監査サポート情報を取得する方法はこちら４．監査サポート画面medicine.png
📔登録患者一覧各画面で登録された情報を確認する場合はこちら５．登録患者一覧画面medical-book.png
--- # 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://s-itou-personal.gitbook.io/home/readme.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.