Joining up the whole system — connectors, standards and the live integration layer

Health data lives in dozens of systems. commvita is built to connect to all of them — monitor every integration for health (commvita™ PulseGrid), speak every standard (HL7 v2, FHIR R4/R5, GP Connect, NRL, IHE), and run a live integration layer (ADT feed, message queue, FHIR browser, patient matching) rather than a set of static diagrams.

Ahead of the field

The integration layer is part of the product, not a second product you license. No separate middleware licence and no per-channel fee, and the connector monitoring and the exchange hub are live. The message engine and the visual mapper are demonstrated surfaces today, which this document rates plainly instead of hiding.From commvita’s own assessment of this module against the systems it competes with. Our assessment, not an independent one.

Live vs demonstrated: Live — real, API-backed platform logic (wired end-to-end today) Demonstrated — representative control surface with seeded data / illustrative UI mock-up

Connect, translate, act

Connect → translate → act. Each integration is monitored for health, its messages translated to a canonical FHIR model, and the result acted on live — ADT events matched to a patient, results filed, alerts raised.

Connect anything

PulseGrid · Connector Wizard

commvita™ PulseGrid monitors the 12 pre-seeded EPR connectors with dual-endpoint, protocol-native probes — MLLP handshake for HL7 v2, FHIR /metadata ping, REST /health — so you know which side failed. An 8-step Connector Wizard stands up a new source.

Where in commvita /connector-dashboard · inventory API /system-connectors · /connector-wizard.

Speak every standard

HL7 v2 · FHIR · IHE · SMART

An HL7 v2 engine, a visual HL7↔FHIR Transformation Studio, a Schema Library (FHIR R4/R5 + UK Core), CDS Hooks, SMART on FHIR app launch and IHE profiles (PIX/PDQ/XDS/MHD/ATNA) — plus GP Connect, NRL and FHIR Bulk $export.

Where in commvita /hl7-engine · /transformation-studio · /smart-on-fhir · /ihe-profiles.

Act on it — live

EPR Hub integration layer

The EPR Hub is the live layer: a real-time ADT event feed, a message queue with retry, a FHIR R4 browser and a patient-matching console — the place inbound events become filed, matched clinical data.

Where in commvita /epr-hub · API /epr/ (adt-events · messages · fhir-query · patient-matches).

commvita™ PulseGrid / Live Board System Administrator

●1 integration degraded — MLLP handshake refused on the Pathology target. Source is healthy; the target side is down.detecting

Integration	Source	Target	Protocol	Latency
EMIS Web → commvita	up	up	FHIR R4	120 ms
Pathology (ORU) → EPR Hub	up	refused	HL7 v2 MLLP	—
Oracle Cerner ADT	up	slow	HL7 v2	910 ms
GP Connect Access Record	up	up	FHIR R4	240 ms

Run probe nowAcknowledge & escalate

Representative UI — illustrative (assurance feed simulated; connector inventory is live)

Both sides of every integration, watched

PulseGrid probes SOURCE and TARGET independently with the protocol’s own handshake, rolls integrations up per clinical service, and drives an alert ladder (detect → acknowledge → escalate) with an append-only ack audit.

/connector-dashboard · Live BoardMLLP · FHIR /metadata · REST /health

Translate to one canonical model

The Transformation Studio maps HL7 v2 segments and legacy Read/CTV3 codes to canonical FHIR R4, tested against sample messages — so downstream modules see one shape, whatever the source spoke.

/transformation-studio/schema-library · UK Core

File it against the right patient

The EPR Hub matches inbound ADT/ORU to the person (NHS number + demographics), queues with retry on failure, and surfaces unmatched messages for a human — no silent drops.

/epr-hub · Patient matching/epr/patient-matches

Where it lives in commvita

Capability	Route	Standard	Status
PulseGrid integration assurance (inventory)	/connector-dashboard	API /system-connectors	● Live
PulseGrid live board & alerts	/connector-dashboard	MLLP / FHIR / REST probes	☉ Demonstrated
EPR Hub (ADT feed, queue, FHIR, matching)	/epr-hub	API /epr/ · HL7 ADT · FHIR R4	● Live
Connector Wizard (8-step config)	/connector-wizard	vendor adapters	☉ Demonstrated
HL7 v2 engine	/hl7-engine	HL7 v2.x · ACK	☉ Demonstrated
Transformation Studio (HL7↔FHIR)	/transformation-studio	HL7 v2 · FHIR R4	☉ Demonstrated
SMART on FHIR · CDS Hooks	/smart-on-fhir · /cds-hooks	SMART · CDS Hooks	☉ Demonstrated
IHE profiles (PIX/PDQ/XDS/MHD/ATNA)	/ihe-profiles	IHE	☉ Demonstrated
GP Connect	/gp-connect	GP Connect Access Record	☉ Demonstrated
NRL Connector	/nrl-connector	National Record Locator v3.0 · FHIR R4	☉ Demonstrated
FHIR Bulk $export · R5 Subscriptions	/fhir-bulk	FHIR R4 $export · R5	☉ Demonstrated
TEFCA / QHIN exchange (US)	/tefca	TEFCA v1.1 · US Core	☉ Demonstrated

Integration is where projects die. Integration is where health IT projects go to die. commvita treats it as a first-class, monitored, standards-native capability — you can see every connector’s health on both sides, translate anything to one FHIR model, and watch inbound events become filed clinical data. Non-SaMD integration control surface.

Strategic commissioning & emerging IHOs. A capitated, outcome-based contract only works if every provider around the patient sees the same record. This integration layer is that backbone for an emerging Integrated Health Organisation (IHO): shared information across acute, community, primary and social care (shared care records, GP Connect, NRL, Neighbourhood Health Record), so strategic commissioners and IHOs can align incentives to whole-population outcomes not activity.