> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/msi/review-and-correct-device-knowledge.md). # Know your device MSI reads the documents attached to your device and builds a single body of knowledge about it: its profile, architecture, security registers, requirements and a searchable knowledge base. Threat models, audits, eSTAR checks and Ask MSI all read from this same knowledge, so a correction you make here carries through to every analysis. ## Before you begin * Select the device you want to review. See [Find your way around MSI](/medcrypt-documentation/msi/get-started.md#switch-organization-workspace-or-device). * Attach at least one document collection to the device. A collection is a folder of documents (design documents, test reports, specifications, SBOMs) that MSI reads from. * Anyone who can see the device can view its knowledge. To identify or edit the architecture and security registers, your organization's plan must include Threat Modeling. ## Open Device Knowledge In the sidebar, select **Device Knowledge**. The header shows the device name, its class and type, and the state of its knowledge base: | Status | Meaning | | ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | | **Ready** | Every attached document has been read. | | **Ready (stale sources)** | Usable, but some sources have changed since they were read. | | **Reading documents** | MSI is reading documents now. | | **Knowledge base is empty** / **Knowledge base not created** | No documents have been read yet. Attach or upload documents. | | **Blocked** | Something needs attention. A callout under the header names the collection and files involved. | Select **Update from documents** to re-read every attached document. This rebuilds the architecture and knowledge base and re-checks both for contradictions. Work already in progress isn't duplicated. Select **How this works** for a technical explanation of how Device Knowledge is built. Everything on this page applies to the device version selected in the page header. See [Manage device versions and changes](/medcrypt-documentation/msi/review-and-correct-device-knowledge/manage-device-versions-and-changes.md). ## Find your way around the tabs The page has three tab groups. Select a group, then a tab. **Knowledge** | Tab | What it shows | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Profile** | Device name, class, type, whether it's a cyber device (one that can connect to the internet, so FDA cybersecurity requirements apply), connectivity, intended usage environment, risk formula, IEC 62304 software safety class, and **Environment assumptions**. | | **Architecture** | The data-flow diagram and the **Device Asset Register**: components, interfaces, data flows and trust boundaries (the lines where the level of trust changes, such as between the device and a hospital network). | | **Security** | Data assets, threat actors and controls for this version. | | **Requirements** | The requirements register and a **Traceability matrix**. | | **Knowledge base** | The pages MSI wrote from your documents. | | **Explore** | Search for any part of your device and see what MSI knows about it and where each fact came from. | | **Contradictions** | Places where your documents disagree, plus document processing status. | | **Design file** | The QMS documents this device is expected to maintain, and which of your uploads stand for each. | | **Collections** | The document collections attached to this device. | **Security posture** has **Vulnerabilities**, **SBOM** and **Cost of Delay**. Vulnerabilities depend on an active SBOM (software bill of materials) for the version. **Versions** has **Versions** and **Change tracking**. ## Correct the device profile 1. Select the **Profile** tab, then **Edit profile**. 2. Change the values that are wrong, then select **Save changes**. Each value carries a label showing where it came from, such as **You set this** or **Not established**. Re-reading documents can overwrite profile edits, so check the profile again after each **Update from documents**. ## Review and correct the architecture 1. Select the **Architecture** tab. If the register is empty, select **Identify architecture**. 2. Use the **Review** filter to show **Unreviewed** elements first. 3. Select an element in the register or the diagram to open its details, including its **Evidence**, **Connections**, **Security** and **History**. 4. Take one of these actions: * **Confirm**: the element is correct as extracted. * **Edit**: change its type, name, description, your document's ID, data classification or trust boundary, then select **Save changes**. * **Refute**: the documents don't support it. It's removed, your reason is recorded, and it won't be extracted again. You can restore it. * **Retire**: it isn't part of the device. Record why. * **Remove from threat model** or **Add to threat model**: keep the element on the device but change whether it's analyzed. Each element's review state appears in the register: | State | Meaning | | -------------- | ------------------------------------------------------------------- | | **Unreviewed** | Nobody has checked it yet. | | **Confirmed** | A person confirmed it. | | **Corrected** | A person changed it. | | **Not found** | The last run didn't find it in the documents. Keep it or retire it. | | **Refuted** | A person said the documents don't support it. | Your confirmed and edited values are kept when MSI re-reads documents. If a newer document disagrees with one of your decisions, it appears on the **Contradictions** tab for you to settle. To make larger changes, select **Add element**, or select **Edit diagram** and describe the change in words (for example, "add a Bluetooth interface on the pump that sends telemetry to the mobile app"). Review the proposed register changes, then select **Apply changes**. If you already have an architecture diagram, select **Use this diagram** to upload it. ## Resolve contradictions The **Contradictions** tab shows a count when critical contradictions are pending. 1. Select the **Contradictions** tab. Turn on **Critical & unresolved only** to focus on what matters most. 2. For each contradiction, expand **Compare sources** to see what each document says. 3. Resolve it: * Select **Smart Resolve**, optionally select **Get LLM suggestion**, choose an **Action** (keep one claim, merge into a new value, or retract both), add a **Resolution note**, and select **Resolve**. * Or select **Status** (or **Resolve**), choose **Resolved**, **Dismissed** or **Confirmed**, and select **Save**. 4. To handle several at once, select their checkboxes, then select **Dismiss selected** or **Mark resolved**. Under **Decisions contradicted by newer documents**, choose **The document is right** or **Keep my value**. Either answer is recorded as your decision. ## Add documents to the device 1. Select the **Collections** tab. 2. To attach an existing collection, select **Attach collection**, choose it, and select **Attach**. To create a new one, use the same flyout. 3. To upload files, select a collection's name. **Documents** opens with that collection selected. Select **Upload**, or drag files onto the page. MSI reads new documents automatically; you don't need to run an update. Track progress on the **Contradictions** tab under **Source documents** and **Processing detail**. To stop using a collection, select its delete icon to detach it. The primary collection can't be detached. ## Next steps * [Trace an AI claim to its source](/medcrypt-documentation/msi/review-and-correct-device-knowledge/trace-an-ai-claim-to-its-source.md): check how well each fact is supported. * [Manage device versions and changes](/medcrypt-documentation/msi/review-and-correct-device-knowledge/manage-device-versions-and-changes.md): see what changed and when. * [Review your threat model](/medcrypt-documentation/msi/review-your-threat-model.md): put the corrected architecture to work. --- # 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://docs.medcrypt.com/medcrypt-documentation/msi/review-and-correct-device-knowledge.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.