HEALTH INTEROPERABILITYREVIEW

Move data. Preserve meaning. Prove the exchange.

Coverage desk

Public Health

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Netsmart task queues need claim-and-reassignment receipts

Netsmart says CareConnect Inbox supports group and individual task assignment inside Netsmart EHR workflows. A buyer should test the exact custody transition from a shared queue to a named worker, including competing claims, returns, reassignment, service-level clock changes, escalation, closure, and reopening, because a current owner or closed status cannot reconstruct who held responsibility at each step.

Clinical Architecture PIQXL scores need use-case acceptance rules

Clinical Architecture says PIQXL Gateway uses its PIQI Framework to score exchanged patient information and highlight root causes of data-quality issues. A score can direct investigation, but a receiving organization still has to define the exchange population, the measure, the threshold, the exception owner, and whether a particular record is fit for its intended use.

Iguana interfaces need generation-specific lifecycle records

iNTERFACEWARE says it supports both Iguana 6 and the newer IguanaX, plans to evolve them gradually, and does not intend to force disruptive migrations. Continued product support is important evidence, but each production interface still needs its own version, dependency, security, test, change, stay-or-migrate decision, parallel-run result, rollback plan, and operational acceptance.

Qvera AI mapping scripts need message-level validation

Qvera says its interface engine's AI Companion can generate mapping scripts, debug errored messages, and troubleshoot connectivity across an engine that supports HL7, FHIR, DICOM, X12, and other formats. Generated code can accelerate integration work, but it remains a proposed transformation until representative messages, versions, semantics, exceptions, privacy controls, and production receipts are validated.

Azure de-identification needs method-and-purpose evidence

Microsoft says Azure Health Data Services can extract, redact, or replace protected-health-information entities in unstructured text for secondary use. A completed job does not establish that the output is anonymous, permitted for the intended recipient, fit for the analysis, or safe to link with other data.

b.well consumer-mediated exchange needs consent-version receipts

b.well Connected Health presents a consumer-mediated health-data network and says patient consent is central to some life-sciences workflows. Consent should be a versioned, purpose- and recipient-specific authorization with downstream receipts; a connected record, app session, or earlier approval does not establish that every later acquisition, disclosure, normalization, or use remains authorized.

Medication history is not an active-medication list

Surescripts presents medication-history, e-prescribing, formulary, benefit, and prior-authorization services as distinct parts of its health-information network. A returned history should remain source evidence until a clinician reconciles patient match, prescriptions, fills, cancellations, reversals, timing, adherence uncertainty, and current intent into an active list.

Infor full item loads need a stock-state commit record

Infor says Clinical Bridge can process full item loads of more than 50,000 items in minutes, supports near-real-time updates, and carries stock and non-stock item data. Speed does not establish that one complete item epoch became visible. Preserve the source cutoff, expected batch, staged exceptions, commit policy, visibility time, and stock-state transitions in one load record.

An eHealth Exchange query needs permitted-purpose and responder-scope evidence

eHealth Exchange operates a nationwide health-information network and is a Designated QHIN under TEFCA, with official materials describing query, document exchange, public-health, federal, and other services. A successful query can prove that a request traveled and produced a response, but it does not by itself establish that the purpose, patient match, responders, data classes, and resulting use were appropriate and complete.

Health Language mappings need source codes and version history

Wolters Kluwer presents Health Language for managing evolving terminologies, normalizing health data, and supporting interoperability and data quality. A standardized target can improve exchange and analytics, but the original code, terminology editions, mapping rule, ambiguity, and authorized use must remain visible.