Skip to main content

​
Overview

Stenoa integrates with your existing clinical systems using industry-standard healthcare interfaces. HL7 v2 and FHIR R4 connections allow Stenoa to receive patient-centric updates, initiate workflows based on upstream events, and publish state changes back to your systems, keeping your clinical workflows synchronized across your EMR, PACS, HIS tools, and downstream systems. Inbound messages are validated, normalized into Stenoa’s internal data models, and emitted to the workflow engine. This ensures consult routing, transfers, and task activation remain aligned with the source of truth in your hospital environment.

​
Supported protocols

​
FHIR (R4)

Stenoa exposes authenticated REST endpoints for selectively ingesting the following resources:
  • Patient
  • Encounter
  • Observation
  • DiagnosticReport
  • Communication
Requests must use JSON-encoded FHIR payloads. All endpoints enforce schema validation, required field checks, and authentication.

​
HL7 v2

Stenoa supports ingestion of HL7 v2 messaging from your integration engine over HTTPS or TLS-wrapped MLLP. Supported message types include:
  • ADT (A01–A08): registrations, admissions, transfers, discharges
  • ORM / ORU: orders, results, ECG notifications
  • Custom Z-segments: site-specific routing fields, consult metadata, or operational signals
Messages are parsed, transformed into internal events, and dispatched to workflow processors.

​
Message processing pipeline

Once received, messages pass through Stenoa’s interoperability pipeline:
  1. Transport layer acceptance: HTTPS or TLS-wrapped MLLP.
  2. Message parsing: FHIR JSON schema parsing or HL7 segment and field extraction.
  3. Validation: Required identifiers (MRN, encounter ID, facility code), event type consistency, and timestamp checks
  4. Normalization: Mapping to Stenoa’s internal patient/encounter models, deduplication and version resolution
  5. Record linkage: Patient matching and encounter association.
  6. Data application: Update case metadata, append clinical context, and trigger applicable workflow rules.
This pipeline ensures consistent, deterministic integration behavior across all hospital environments. To configure your FHIR/HL7 integration, contact Support.