Page cover

Integration Settings

Integration Settings

Enable external connectivity and controls for embedded usage of RADPAIR.

Overview

Decide how your organization connects to external systems. In this section, you can enable or restrict webhooks, iframe events, and API access, and define which parent domains are allowed for iframe embedding. Any changes made here will also apply to sub-organizations when you cascade settings.

Enable Integration

Toggle integration features on or off.

When enabled:

  • Webhooks fire as configured

  • Iframe postMessage events are allowed

  • External API access is active

When disabled:

  • Webhooks won’t fire

  • Iframe events are suppressed

  • External API access is disabled for this org

Security tip: Only enable in environments where you control webhook endpoints and parent iframe apps. Always keep API keys and webhook secrets secure.

Cascading

Use the Cascade button to apply it to sub-organizations. Learn more about how cascading works here.

Whitelisting Domains

Define which parent domains are allowed to post messages to an embedded RADPAIR iframe.

Purpose

Restricts iframe postMessage to trusted origins.

Format

  • Host or wildcard host, no scheme (e.g., example.com, *.example.com)

  • One entry per line; press Enter to add

Recommendations

  • Use the smallest necessary wildcard (prefer reports.example.com over *.example.com)

  • Include all environments (dev, staging, prod) as separate entries if needed

Examples

app.examplehealth.com
*.partner-example.com
localhost

Wildcards (*.example.com) include all subdomains. Use with care to avoid over‑permissive access.

Enable Report Linking

Allow users to link and unlink reports that share the same Medical Record Number (MRN) directly in the report UI.

Overview

Enable or disable in-app report linking functionality. When turned on, users can manage report links from the UI instead of only through the integration API.

Requires: Integration enabled Cascade: Enabled by default unless overridden by a child org

Behavior

When enabled:

  • Users can link/unlink reports with the same MRN directly from the report interface

When disabled:

  • Linking is only available via the integration API

  • In-app linking controls are hidden

When to Use

  • Your workflows benefit from quickly cross-referencing related studies/reports by MRN

  • You manage linking validation through your integration layer

Considerations

  • Ensure your integration consumes report links where applicable

  • Changes may affect downstream systems if they rely on a single canonical report

Tip: Linking is most effective when downstream systems are designed to handle multiple related reports per MRN.

Pre-Findings Processing

Overview

Automatically convert structured measurement data from DICOM SR and other sources into human-readable clinical summaries that appear in the transcript for radiologist review and editing.

What It Does

When a study includes structured measurements in the pre_findings metadata field, RADPAIR:

  1. Processes the JSON data through an LLM

  2. Generates a formatted clinical summary

  3. Inserts the text into the transcript box (fully editable)

Example Output:

Aorta – proximal 1.7 cm, mid 1.9 cm, distal 1.9 cm
Pancreas – head 1.3 cm, body 1.5 cm, tail 2.4 cm
Right kidney – 5.6 × 5.8 × 3.1 cm (vol 51.7 ml)

Configuration

Organization Settings (Admin)

Pre-Findings Processing Prompt

  • Customize how measurements are formatted

  • Add organization-specific instructions

  • Leave blank to use system default

Default System Prompt:

You are preparing data for incorporation into a radiology report. Please take the extracted DICOM SR data and format it concisely into a summary with one line per organ with a description of the organ, followed by the measurement. Where measurements are taken in 3 planes, format it as length × width × height. Any measurements should be rounded to one decimal place.

Behavior

When Enabled

  • Structured measurements in pre_findings are automatically processed

  • Formatted text appears in transcript

  • Processing completes in <5 seconds

  • Radiologists can edit, delete, or add to the text

When Disabled

  • pre_findings data is ignored

  • Normal report workflow continues

Requirements

Integration Requirements:

  • Send pre_findings JSON field in metadata payload

  • Use underscore naming convention (not camelCase)

  • Supports upsert for incremental updates

Metadata Structure:

{
  "pre_findings": {
    "report_info": { ... },
    "anatomical_findings": [ ... ]
  }
}

Cascading

Use the Cascade button to apply custom prompts to sub-organizations.

When to Use

✅ Enable when:

  • Studies include DICOM SR measurement data

  • Radiologists need formatted measurements in transcript

  • You want to reduce manual transcription time

❌ Disable when:

  • No structured measurement data is available

  • Organization prefers manual entry only

  • Testing/validation is incomplete

Limitations

  • English language only

  • Single prompt per organization (not modality-specific)

  • No automatic reprocessing when prompt changes

  • Synchronous processing may add latency to report loading

Future Enhancements:

  • Tech worksheet integration

  • Modality-specific prompts (CT, MRI, US, XR)

  • OCR from scanned documents

  • Measurement trending and abnormal value flagging

PreviousOrganization SettingsNextCascading Changes

Last updated