Integrations: Technical

---

Event Callbacks

Does RadPair provide callbacks/events for actions like report started, saved as draft, preliminary report created, or report discarded?

Currently, these specific event callbacks are not built-in. However, RadPair plans to implement additional event types (e.g., removing a report) in future releases.

---

Authentication

How does RadPair handle authentication if we want multiple customers or organizations to have unique accounts?

By default, a single admin account can generate authentication tokens for specific users. If you prefer a separate admin for each customer or sub-organization, RadPair supports distinct admin accounts to limit which users each admin can manage. You can also pass an internal_org_id parameter to differentiate sub-organizations internally.

---

HL7 Feeds

Will we need an ORM HL7 feed for every new report created through RadPair?

An ORM feed is not strictly required by default. However, it depends on your specific workflow and whether you plan to distribute ORU messages for all exams. RadPair can discuss customization options to see what fits best for your needs.

---

Metadata Parameters

What is the purpose of the metadata_source parameter?

The metadata_source field identifies where the data is originating (e.g., your application). It can help RadPair apply specialized parsing or logic. The accession_number is used to uniquely identify a report. Additional fields such as MRN may be added in future updates.

---

Data Separation

How does RadPair ensure separation of patient data between different customers if the system only requires an accession_number plus one extra parameter?

For each organization, the accession_number serves as a unique key. RadPair also plans to support more fields to guarantee uniqueness within a single organization. This ensures that exams and data remain distinct for different customers.