Connected records and assistants

Bring records from another clinical system into a case, or let an approved external AI assistant request OncoBrain drafts. Review requirements depend on the connection.

All screenshots use synthetic demo data. The EHR example shows the product flow and does not demonstrate production compatibility with a specific vendor.

What these terms mean

• EHR: an electronic health record, your organization's clinical record system.
• HIE: a health information exchange that can return records from other organizations.
• FHIR R4: a standard format for exchanging healthcare data.
• MCP: a standard connection that lets compatible AI assistants request allowed OncoBrain work.

Add records to a case

Use Intake & sources for all incoming material. You can upload a file, paste text, import from the configured connected EHR, or request outside records through HIE. After confirmation, each item becomes a source in the case and follows the same extraction and review path.

Adding a source does not add a patient-chart fact, diagnosis, order, or clinical decision.

Import from the connected EHR

The connected EHR path reads the configured FHIR R4 record. It does not write back to that EHR.

1. In the Worklist, select Import records and then From the connected EHR.
2. Choose the patient case.
3. Select the returned records, then review the patient identity and material.
4. Confirm the import.

OncoBrain can retain a structured record snapshot and supported documents or images. If an import exceeds the supported size or record limits, it stops and reports the problem.

Confirm only after you have resolved identity differences. The app classifies external identifiers as already linked, new, or conflicting. It refuses an identifier that belongs to another patient. Production use also requires your organization's vendor approval, authorization setup, security review, and validation.

Request outside records through HIE

The HIE path is for records held by another organization. It saves the request so you can leave the case and return while records are gathered.

1. In the Worklist, select Import records and then From outside networks. Choose the patient case. You can also select Add then Find outside records from Intake & sources.
2. Review the legal identity and address that will be sent for matching.
3. Confirm the required attestations, including the treatment relationship.
4. Start the request and return later to review the results.
5. Select the original documents to add as case sources.

OncoBrain keeps records that were already present separate from newly returned documents and shows unsupported results instead of silently converting them. The current adapter supports the Metriport lifecycle. Live use requires approved credentials, agreements, permitted-purpose policy, patient-matching policy, retention rules, and deployment validation.

Generate FHIR output

OncoBrain can generate a FHIR R4 document from an eligible reviewed artifact. The export stays tied to the reviewed version and includes a receipt so the same bytes can be reproduced.

OncoBrain generates this document only. It does not send it to an EHR, update a record, place an order, or create a signed note.

Use an approved external assistant

Compatible assistants can connect through MCP at /api/mcp after signing in and granting access. They can discover cases they are allowed to see, read limited confirmed context, and request an allowed advisory workflow. They cannot access a database connection, local file path, live case workspace, raw prompt, or clinician action control.

An assistant can find authorized cases, read confirmed case context, browse permitted Library documents, and search public web evidence. It can also request a draft and check or cancel that request.

The assistant's permissions come from the access you grant and the user's organization membership. Every request checks both again. Clinical review, chart confirmation, referral disposition, treatment selection, export, signing, and care actions remain in OncoBrain.

For setup and acceptance checks, see Agent-native MCP.