Interoperability

Regenemm Connect

The governed interoperability surface between Regenemm workflows and approved external healthcare systems.

Connect supports structured exchange while preserving identity, consent, provenance, residency, release, and audit boundaries around clinical data movement.

Request demo API docs

What Connect supports

Standards-based exchange

Connect is positioned for governed interoperability pathways such as FHIR, HL7, EMR/EHR exchange, My Health Record-related workflows, and structured import/export packages.

External-system boundaries

Each integration boundary should preserve source, destination, authority, mapping, consent position, residency posture, and auditability where applicable.

Hub-aligned mapping

External system payloads map into Regenemm domain objects through controlled pathways rather than bypassing the Hub or creating unreviewed clinical truth.

Audit-aware handoff

Import, export, and exchange events should be attributable and reviewable, with request correlation across the Hub and spoke boundary.

Integration surfaces

FHIR R4 and AU Core-oriented exchange patterns

HL7 and HealthLink-related message pathways where configured

EMR, EHR, practice management, pathology, and radiology integration boundaries

My Health Record-related pathways where configured and authorised

Import/export packages tied to source, recipient, purpose, and release state

Integration readiness checks and audit-safe operational status

Relationship to the Hub

Connect contextualises interoperability workflows and external-system exchange.

Regenemm Voice remains the Hub for canonical state, release gates, provenance, and durable audit.

Integration pathways should fail closed when identity, consent, mapping, residency, or audit controls are not satisfied.