HL7 v2
Orders, ADT and results messaging
ORM, ORU, ADT and SIU message handling with configurable mapping per sending facility and interface engine.
What problem we solve, by care setting.
Integrations
RADIN speaks the standards radiology runs on. Orders arrive from your EMR, images flow from every modality, results reach referrers, and billing receives clean study data without a custom project for each connection.
Standards
HL7 v2
ORM, ORU, ADT and SIU message handling with configurable mapping per sending facility and interface engine.
FHIR
FHIR resources for patient, appointment, service request, imaging study and diagnostic report where partners support them.
DICOM
C-STORE, C-FIND, C-MOVE, Storage Commitment, Modality Worklist and DICOMweb for cloud-side retrieval.
IHE
Scheduled workflow patterns that behave predictably alongside other IHE-conformant systems in the department.
Systems
EMR / EHR
Orders in, signed reports back, status visible to the ordering provider without leaving their chart.
Billing & RCM
Verified demographics, insurance, authorization and CPT context handed to your billing system or clearinghouse.
Third-party PACS
Run RADIN RIS against an incumbent archive, or route studies to RADIN PACS on your own timeline.
AI marketplace
Vendor-neutral hooks so third-party detection and triage tools can act on studies inside the same worklist.
e-Fax & Radin ePrint
e-Fax delivers signed reports to referring offices. With Radin ePrint installed, staff select it in their existing application's Print menu to send referral documents directly to the imaging center's Document Manager—without printing or scanning paper.
Identity
SAML and OIDC single sign-on with directory-driven provisioning for staff across facilities.
Common questions
Interface scope is agreed during discovery and confirmed in the implementation plan. Standard HL7, FHIR and DICOM connections are part of the platform rather than bespoke engineering.
Yes. RADIN connects through Mirth, Rhapsody, Corepoint and similar engines, or directly where you would rather not add a hop.
Message-level monitoring with exception queues and alerting, so a stalled feed appears as an operational task rather than a silent gap.
Talk to RADIN
Share the systems in scope and we will outline the interfaces, message types and timelines for connecting them.