Powered by ID Integration, Inc.
Work with the systems you already use, including major EHRs (Epic, Oracle Health, MEDITECH, athenahealth, eClinicalWorks, NextGen), LIS platforms (Epic Beaker, Clinisys/Sunquest, Orchard), and CMMS tools (Nuvolo, Accruent/Connectiv, Four Rivers TMS).
Use Case
Show ready or available equipment near the point of care. Make tray readiness visible on perioperative boards. Attach device IDs to encounters for charge capture and documentation.
How It Works
Publish concise readiness and last observed location signals tied to a non-PHI asset key. Link back to details in the tracking system when a deeper lookup is needed.
Why It Matters
Faster room turns, fewer delays, and better charge integrity.
Use Case
Align custody events to lab milestones such as order, collection, pickup, receipt and accessioning. Reconcile expected versus received at pathology receiving.
How It Works
Write time and place events against the LIS order number using the interface engine or approved APIs. Record cold-chain pass or fail where required.
Why It Matters
Fewer lost or mixed specimens, faster recovery, and audit-ready logs.
Dive Deeper: LIS/EHR Integration for Specimens - Write concise, audit-ready specimen events without duplicates or PHI on tags.
Use Case
Keep preventive maintenance and recalls on schedule. Reduce second passes and validate asset location before dispatch.
How It Works
Sync asset master data and statuses. Send movement events and ready or clean states to drive work orders and technician routing.
Why It Matters
Higher on-time preventative maintenance, less time hunting, and better device uptime.
Use Case
Leaders track utilization, rental avoidance, locate time, room turn time, custody completeness, and exception trends across the network.
How It Works
Stream events to the data platform through secure feeds. Maintain a stable asset or specimen key for joins.
Why It Matters
Shared facts for decisions and ROI reporting.
Identity and access: SSO and role-based permissions with least-privilege scopes for apps and interfaces.
PHI boundaries: Patient data remains in the EHR and LIS. Asset and specimen tags carry non-PHI keys linked through secure lookups.
Auditability: Immutable event logs with user, time, source, and payload checksums.
Resilience: Queue, buffer, and replay. Deduplicate by message IDs. Alert on stalled interfaces.
Change control: Versioned endpoints, non-production sandboxes, and defined release windows.
Asset events: last seen location by zone or room, ready or clean or in use, assigned or returned, taken to service, or recall hold.
Specimen events: bag association, depart unit, arrive receiving, accessioned, exception such as partial receipt, off route, or cold-chain fail or pass.
Perioperative signals: tray ID, set completeness flag, delivered to room, case pick verified, available for case.
Map decisions to data.
Identify which screens and queues need signals such as perioperative boards, LIS worklists, and CMMS calendars.
Pick the keys.
Standardize the non-PHI identifiers used to join systems such as asset ID, tray ID and accession.
Select the path.
Use interface engine routes with HL7 or FHIR or direct REST APIs with signed payloads.
Stage and test.
Validate read-zone accuracy and message timing with a short pilot route or device class.
Harden and scale.
Add buffering, alerts and dashboards, then extend to additional units and use cases.
Measure and report.
Track KPIs and publish monthly wins to leadership.
Perioperative: percentage of cases with tray ready a set number of minutes before scheduled start, first-case on-time starts
Lab: custody completeness percentage, median collection to receipt time by priority class, re-collection rate
Clinical engineering: PM on-time rate, recall closure time, median locate time
Finance and operations: avoided rentals, utilization within target bands, reduction in delay minutes
