Closed-loop integration
Orders in. Device data in. Clinical results back.
The exact route varies by hospital, but the integration pattern is consistent: HRI receives the patient and order context needed for the device clinic workflow, combines it with the device data, and returns the completed clinical result to the hospital system.
HRI Pro
Longitudinal cardiac device record and clinical workflow
Generic architecture. Exact systems, routes, message profiles and network endpoints are agreed with each hospital.
Hospital interface pattern
A result that closes the original hospital order.
The interface can preserve the order context created in the hospital system, so the device clinic result returns to the correct patient, procedure and order rather than becoming a disconnected PDF.
- Order or worklist createdThe hospital EHR, PAS or CVIS creates the patient and procedure context for an implant or follow-up.
- Interface engine routes the messageThe hospital integration layer maps and routes the order/worklist into the HRI workflow using the agreed interface profile.
- HRI retains the order contextThe hospital order identifier is held with the HRI workflow so it can be returned with the result where the receiving system requires it.
- Device data arrivesIn-clinic programmer data can arrive through ProLink; supported remote monitoring data can arrive through Remote Link.
- Clinician reviews and completes the recordThe physiologist or clinician reviews the device information and completes the clinical follow-up in HRI Pro.
- Result returns to the hospital systemThe completed result/report is sent through the configured results interface, with the originating order context preserved for reconciliation.
- Acknowledgement closes the loopMessage acknowledgements confirm each exchange, and interface monitoring is used during testing and after go-live to confirm the interface is working end to end.
What can be configured
Built around the hospital architecture, not the other way around.
- Orders & worklists
- Configurable HL7 order/worklist interfaces, including procedure and mnemonic mapping to HRI implant and follow-up workflows.
- Results & reports
- Configurable HL7 result/report interfaces, using the agreed interface profile for the receiving CVIS or EHR.
- Order reconciliation
- Hospital order identifiers can be retained in HRI and returned in the result message to support matching back to the originating order.
- Acknowledgements
- End-to-end message acknowledgement and test workflows can be used to validate inbound orders and outbound results before clinical go-live.
- Procedure mapping
- Local procedure codes and mnemonics can be mapped to the relevant HRI workflow, including implant and follow-up distinctions.
- Identity
- Microsoft Entra ID single sign-on can be configured as part of a hospital deployment, with role-based access managed within HRI Pro.
- Network configuration
- Endpoints, routing, ports, whitelisting and firewall rules are agreed with the hospital integration and security teams for each deployment.
- Programmer data
- In-clinic output from Medtronic, Abbott, Boston Scientific and Biotronik programmers is captured through ProLink and associated with the patient record.
- Remote monitoring
- Supported manufacturer remote monitoring transmissions enter the same clinical record through Remote Link.
Implementation
How a hospital interface is brought live.
Integration is delivered with the hospital IT, interface-engine and clinical teams together, because the message transport and the clinical workflow have to agree.
- Map the clinical workflowAgree which procedures are implants, follow-ups or other device clinic activities, and map the local order codes and mnemonics.
- Agree the architectureConfirm the source and destination systems, interface-engine route, environments and responsibility boundaries.
- Configure connectivitySet the agreed endpoints, network routes, firewall rules and whitelisting, documented within the deployment team.
- Configure message profilesMap the inbound order/worklist and outbound result fields, including the patient identifiers and hospital order number required for reconciliation.
- Test both directionsCreate test orders, confirm receipt, return test results and verify acknowledgements and message content with the receiving system.
- Clinical validation and go-liveOnce the technical handshake is complete, the device team validates the implant/follow-up workflow before production go-live.
Why it matters
Integration should remove duplicate work, not create another portal.
Keep the systems already in place
HRI can sit alongside the EHR, PAS, CVIS and interface engine rather than requiring the hospital to replace them.
Keep order context attached
Preserving the hospital order identifier means the completed device clinic result can be reconciled back to the original clinical workflow.
Bring device data into one record
Programmer and remote monitoring data feed the same longitudinal patient record used by the device clinic.
Start light, go deeper later
Demographics only, results only, or the full order and result loop. The depth of integration is a choice the hospital makes, and it can change after go-live.
Integration questions
Does HRI replace the hospital EHR or CVIS?
No. HRI Pro is designed to sit alongside the hospital systems already in place. The exact routing is configured around the local EHR, CVIS, interface engine and network architecture.
Can HRI receive an order and send a result back?
Yes. A typical HL7 integration pattern can receive hospital order or worklist context, retain the hospital order identifier, and return the completed result or report through the configured results interface.
How are hospital order identifiers kept aligned?
The hospital order identifier can be retained with the HRI workflow and returned with the result message where required, allowing the receiving CVIS or EHR to reconcile the completed result to the originating order.
Are ports and interface endpoints fixed?
No. Network routes, endpoints, ports, whitelisting and message profiles are agreed with the hospital integration team for each deployment.
Do we need an interface to start?
No. Integration can be phased. HRI Pro’s core clinical workflows can be deployed without a hospital-system interface, with demographics, orders and results interfaces added when required.
Where does device data enter the workflow?
In-clinic programmer output can enter HRI through ProLink, while supported remote monitoring transmissions can enter through Remote Link. Both feed the same longitudinal cardiac device record.