Stage 2 of 6 in the device journey
What happens, in order
This is the workflow as shown in the film, recorded in HRI Pro with demonstration data and fictional patients.
- A ProLink device sits in the device clinicProgrammers from Medtronic, Abbott, Boston Scientific and Biotronik send their reports to it over Bluetooth, Wi-Fi, USB or wireless transfer, depending on the programmer.
- HRI Pro parses, matches and tracks the fileThree tabs show where everything is: Processed, Under Review and Transfer Status. The health of the box itself is visible in the header.
- Every file has a trailFrom detected to processed, open any row to see what happened to it and when.
- Failures explain themselvesA failed file shows the reason in words, and a rerun reports back.
- Unmatched patients go to reviewFiles whose patient could not be matched are held with the reason, rather than guessed at.
- Match side by sideFind the record, confirm it against the programmer report, and the file moves to Processed. The follow-up form is already filled in, and the device PDF is one click away.
Why it matters
Supported across four manufacturers
Programmer integration with Medtronic, Abbott, Boston Scientific and Biotronik. HRI is a member of the Medtronic Medpoints Partner Programme and the Abbott Together Partner Programme.
No manual export, no retyping
Programmer data reaches the record without removable media or manual transcription, which removes both a security risk and a source of error.
The source file is kept
The original programmer report stays attached to the follow-up, so the structured values can always be checked against what the programmer actually said.
Built for a locked-down clinical network
ProLink is a dedicated edge device, independent of the hospital's general IT infrastructure. It runs hardened Red Hat Enterprise Linux with Wazuh endpoint detection, and the platform holds Cyber Essentials Plus. Nothing is silently dropped: failed transfers and uncertain matches are queues the team can see.