In
HRI ProOne governed clinical platform for the device journeyOut
- Integration
- HL7 order/worklist in, result/report back with the hospital order context preserved. Integration & interoperability
- Identity
- Microsoft Entra ID single sign-on supported
- Hosting
- Country-specific cloud deployment with in-country data residency.
- Access
- Role-based, multi-site, with a full audit trail
- Programmer capture
- ProLink edge device in the clinic. Programmer integration with Medtronic, Abbott, Boston Scientific and Biotronik
- ProLink security
- Hardened Red Hat Enterprise Linux, Wazuh endpoint detection, independent of the hospital's general IT network. Full specification on request
- Data out
- PDF reports, Excel exports and filtered operational views
Security and procurement
Certified, audited and ready for procurement.
- ISO/IEC 27001:2022
- Certified by West Assured (INAB-accredited). Scope: the systems, services and people supporting the cloud-based cardiac device management platform and the National Cardiac Device Registry.
- Cyber Essentials Plus
- Independent technical assurance under the UK government-backed scheme.
- Penetration testing
- Independent web application and API testing of the platform.
- Audit trail
- Clinical and administrative actions are recorded, with reasons where a record is changed.
- Data protection
- Operated in line with GDPR.
- Procurement routes
- UK: G-Cloud 15, and eligible under the Medtronic Medpoints and Abbott Together partner programmes. Ireland: HSE National Application Registry. Australia: per-deployment procurement.
- Device regulation
- Built to support EU MDR 2017/745, Australia's TGA framework and UK MDR requirements, including UDI capture through GS1 barcode scanning at implant.
- Regulatory status
- HRI Pro is clinical data management software, not a medical device. Its intended purpose is to record, store, structure and present cardiac device data. It parses programmer and remote monitoring reports into structured fields and presents the original report alongside the HRI follow-up; it does not analyse or interpret that data to inform a clinical decision, and the reviewing clinician remains responsible for the record.
- Data controllership
- For clinical care delivered through HRI Pro, each hospital is data controller and HRI is its data processor. For the cross-hospital National Cardiac Device Registry in Ireland, HRI is data controller under data sharing agreements with participating hospitals. Arrangements outside Ireland are established per market and deployment.
National since 2008
All private cardiac hospitals and the vast majority of HSE cardiac device services. Listed on the HSE National Application Registry and recognised by HIQA as Ireland's national cardiac device registry.
Deployment-ready
Australian deployment capability with in-country representation, local hosting, workflows aligned with Australian UDI requirements, and ProLink support for on-site integration. Supported by Enterprise Ireland's market validation programme.
Listed on G-Cloud 15
UK public-sector buyers can procure HRI Pro through the Crown Commercial Service G-Cloud 15 framework, and purchases are eligible under the Medtronic Medpoints and Abbott Together partner programmes. Registered presence in Belfast, with Cyber Essentials Plus in place.
What IT teams tend to ask
Is this another remote monitoring portal?
No. It is the system of record for the device clinic, from implant onward. Remote transmissions are one input among several. How it connects to the EHR and CVIS
What goes on our network?
Very little. ProLink is a dedicated edge device that runs independently of the hospital's general IT infrastructure, with its own always-on connection to HRI Pro. It runs hardened Red Hat Enterprise Linux with enterprise endpoint protection. ProLink
Who can see what?
Access is role-based and multi-site, every action is logged, and a group super-admin sees only the hospitals they cover.