SpecsModelExploreRequirements
SpecsModelExploreRequirements
Clinical Ingestion
Overview
Guide
Twin streams
Links and Communications
IDproduct.ingestion
DescriptionHL7 v2 and FHIR ingestion gateways.
Keyingestion
Typesystem
Statusactive
TeamClinical Ingestion
Owner
ingestion@healthcare.example
TechnologiesJava, HL7, FHIR, MLLP
Tags
Table of contents
Guide
Clinical Ingestion
Internal structure
Containers
Links and Communications
Requirements

Attributes

protocolHL7 v2 + FHIR R4
throughput50k msgs/h

Guide

Clinical Ingestion

Clinical Ingestion is the hospital-facing edge of the platform. Every HL7 message and FHIR call from external systems enters here before canonical data is written to Clinical Data.

Responsibility in one sentence

Accept hospital traffic reliably, acknowledge fast, archive raw payloads, map to the canonical model and hand off to Clinical Data.

Internal structure

Could not build diagram for model "example-healthcare".

Containers

HL7 Gateway

MLLP listener and HL7 v2 parser.

FHIR Gateway

FHIR R4 REST endpoint with mTLS and consent enforcement.

Mapping Service

Maps HL7 v2 messages to internal canonical model.

  • MLLP termination and HL7 parsing with ACK/NAK.
  • FHIR R4 REST with SMART auth and consent enforcement.
  • HL7→canonical mapping with terminology resolution.

Links and Communications

4 outgoing links

Outgoing Links(4)

Target objectLabelLink typeRelationRaw idRequiredDescription
Hospital EHR

example-healthcare.external_systems.ehr_system

external
receives HL7 from—linksexternal_systems.ehr_system——
Laboratory System

example-healthcare.external_systems.lab_system

external
receives HL7 from—linksexternal_systems.lab_system——
FHIR Partner

example-healthcare.external_systems.fhir_partner

external
exchanges FHIR with—linksexternal_systems.fhir_partner——
Clinical Data

example-healthcare.product.clinical_data

system
writes into—linksproduct.clinical_data——

Requirements