Data Integration
Connect to HL7 V2 and CCDA sources via six connectivity methods. Currently auto-detects format, parses, normalizes, and produces clean output with AI-assisted data cleaning and full audit logging.
Input Formats
Currently auto-detects whether a file is HL7 V2 or CCDA based on content — no manual format selection required.
Parse and normalize HL7 V2 messages with support for all major message types and automated validation.
Extract structured clinical data from CCDA XML documents and CCD files.
Every record gets scored. Every source gets a report. Quality is built into the pipeline, not checked after.
GKE-hosted pipeline with async job processing and multi-tenant output storage.
Connectivity
Each connectivity type includes real connection testing — Currently probes the source before activation.
Upload HL7 or CCDA files directly through the dashboard with drag-and-drop, batch processing, and job tracking.
Automated file transfer with host, port, path, and credential configuration. Connection tested via real SSH2/FTP handshake.
Programmatic ingestion at /api/v1/upload with organization context. Supports bearer token, API key, and basic auth.
Pull from GCS buckets with service account JSON credentials. Tests connection with ListObjects before activation.
Connect to S3 with access key/secret and region. Tests connection with ListObjectsV2 before activation.
Ingest from Azure containers with SAS token authentication. Tests connection with container blob listing.
Get started
Start processing HL7 messages, ensure data quality, and enable FHIR-based interoperability — all from one platform.