Edge Connector Security and Ingestion
How the Regenemm Edge Connector securely ingests approved clinical and administrative data flows under Hub governance.
Edge Connector Security and Ingestion
The Regenemm Edge Connector is designed to help approved clinical and administrative data flows enter the Regenemm platform securely, traceably, and under Hub governance.
In healthcare, important information often begins outside the application layer: pathology reports, radiology reports, HL7 messages, HealthLink-related messages, practice management system signals, local server exports, or other approved system outputs.
The Edge Connector is the secure ingestion layer that helps bring those signals into Regenemm Voice.
Role in the Regenemm Architecture
Regenemm is built around a Hub-and-Spoke architecture.
- Regenemm Voice is the Hub and clinical control plane.
- Spokes provide bounded workflow surfaces.
- The Edge Connector securely ingests approved external and local data flows.
- Regenemm Link supports patient-controlled records and sharing.
- Regenemm Connect supports standards-based interoperability.
- The Knowledge Base supports evidence retrieval.
- Agentic assistants operate inside declared workflow, role, consent, audit, and human-review boundaries.
The Edge Connector sits close to external systems, but it does not replace the Hub.
Its purpose is to capture, identify, attribute, and route approved data into Regenemm Voice for governance.
External systems
↓
Edge Connector
↓
Regenemm Voice Hub
↓
Governed Spoke workflows
What the Edge Connector May Ingest
Depending on configuration and customer approval, the Edge Connector may support ingestion from sources such as:
- HL7 messages;
- HealthLink-related messages;
- pathology reports;
- radiology reports;
- practice management system signals;
- approved local server folders;
- approved clinical-system exports;
- billing-relevant administrative events;
- other authorised clinical or operational feeds.
The exact source systems, pathways, and data classes depend on the deployment.
Hub-First Ingestion
The Edge Connector is designed to feed governed ingestion events into Regenemm Voice.
Regenemm Voice then governs:
- clinical state;
- patient matching;
- source attribution;
- audit;
- provenance;
- workflow routing;
- Spoke updates;
- agentic task eligibility;
- patient-facing release rules;
- external transmission rules.
The Edge Connector should not become an ungoverned permanent clinical record store.
The design rule is:
Edge Connector ingests.
Regenemm Voice governs.
Spokes contextualise.
Audit persists.
Why This Matters
A new result or report can affect many downstream workflows.
For example, an ingested pathology report may affect:
- a pre-operative readiness workflow in Hospital Hub;
- a medication or anticoagulation review;
- a patient record in Regenemm Link;
- a follow-up obligation in Home Hub;
- a billing-readiness workflow;
- a medicolegal chronology;
- a triage or escalation pathway;
- a future interoperability output through Regenemm Connect.
The Edge Connector does not decide all of those consequences by itself. It feeds the Hub, and the Hub governs routing according to workflow, consent, role, policy, and audit requirements.
Security Posture
The Edge Connector is designed as a controlled ingestion boundary.
Depending on deployment, Edge Connector controls may include:
- secure network connectivity;
- Tailscale-wrapped connectivity where configured;
- source-system attribution;
- message fingerprinting;
- parser and mapping version tracking;
- ingestion audit records;
- replay controls;
- failure queue visibility;
- retention limits for local buffers;
- Hub-first routing;
- access separation from ordinary user interfaces;
- credential isolation;
- monitoring and alerting.
The Edge Connector should operate with least-privilege access to approved sources only.
Local Data Handling
The Edge Connector may need temporary local handling for ingestion, parsing, retry, or failure management.
Local handling should be limited to what is required for safe operation.
The intended model is:
- local buffers are temporary;
- local retention is limited;
- local storage is not an independent clinical record;
- failures are visible and reviewable;
- successful ingestion is attributed and auditable;
- durable clinical state returns to Regenemm Voice.
Audit and Provenance
Every material ingestion event should be attributable.
Where applicable, Regenemm should be able to record:
- source system;
- source location or feed;
- message or document type;
- ingestion timestamp;
- source timestamp where available;
- message fingerprint;
- parser version;
- mapping version;
- patient or episode match status;
- accepted, rejected, duplicate, or quarantined state;
- downstream Hub event;
- workflow consequences.
This supports clinical review, troubleshooting, medicolegal reconstruction, and data-quality improvement.
Patient Matching and Safety
Clinical ingestion workflows require careful patient matching.
Where data cannot be confidently matched, the system should avoid silently attaching it to the wrong patient record.
Unmatched, ambiguous, duplicate, malformed, or unexpected messages should be routed to a safe review or quarantine pathway.
Agentic Workflow Boundary
Agentic assistants may use Edge Connector data only when a declared workflow permits it.
That means:
- the workflow must be authorised;
- the agent must have a declared role;
- the data class must be permitted;
- the tool grant must be valid;
- the purpose must be appropriate;
- audit must be recorded;
- human review must occur where clinically material.
Agents should not directly access local clinical servers or Edge Connector source locations outside declared policy.
Relationship to Regenemm Connect
The Edge Connector and Regenemm Connect serve different roles.
| Component | Primary role |
|---|---|
| Edge Connector | Secure ingestion from local or near-local clinical and administrative sources |
| Regenemm Connect | Standards-based interoperability with EMR, SMART on FHIR, MHR pathways, and external systems |
| Regenemm Voice | Hub governance, persistence, audit, orchestration, and clinical control plane |
The Edge Connector brings data into the platform.
Connect supports structured interoperability with external systems.
Regenemm Voice governs both.
Summary
The Edge Connector is a secure ingestion layer for healthcare data flows.
It is designed to:
- receive approved clinical and administrative data;
- preserve source attribution;
- avoid ungoverned local permanence;
- feed Regenemm Voice as the Hub;
- support audit and provenance;
- trigger downstream governed workflows;
- operate inside least-privilege and network-controlled boundaries.
The invariant is:
Edge Connector captures.
Regenemm Voice governs.
Spokes contextualise.
Agents assist only when authorised.
Humans review where clinically material.
Audit persists.
Contact
For Edge Connector, security, or integration enquiries: