RadFuzion field notes
Technical perspectives on DICOM, HL7, PACS integration, structured reporting, and the operational work behind reliable imaging workflows.
Most DICOM routers forward studies between on-prem nodes and stop there. A practical checklist for evaluating one — cloud destinations, HL7 awareness, tag correction, failure behavior, and testability.
Read the articlearrow_forwardHand-keying ultrasound and bone-density measurements is a quiet tax on every exam. Here is how to value automating it — by the labor it replaces, not a vendor list price — and how to keep the AI cost in check.
Read the articlearrow_forwardSee how RadSR condenses native DICOM Structured Reports, extracts measurements from ultrasound and bone density images, protects PHI, and maps clinical meaning into stable reporting fields.
Read the articlearrow_forwardNormalize outside study names to local terminology during PACS migrations, patient-disc imports, and teleradiology workflows—at the HL7 level, the DICOM level, or both.
Read the articlearrow_forwardWhen older priors live outside the reading PACS, on-demand prefetch restores context. AI-assisted selection can choose relevant priors like a radiologist instead of multiplying rules.
Read the articlearrow_forwardSome cloud PACS and RIS platforms stop short of DICOM Modality Worklist. See how RadList turns HL7 orders into accurate, station-aware MWL responses.
Read the articlearrow_forwardCloud PACS downtime can begin in the data center, the vendor platform, or the network between you. Learn how an on-prem reading fallback keeps images, dictation, prelims, and delivery moving.
Read the articlearrow_forward