Hi HN,

I'm launching Cloud Health Office v3.0.0 — an open-source platform for healthcare payer EDI integration.

## The Problem

Healthcare payers (insurance companies) spend 6-8 weeks integrating each new payer for EDI transactions (claims, eligibility, prior auth). The process is: - Entirely manual - Vendor lock-in heavy - Compliance-intensive (HIPAA, CMS regulations) - Expensive ($50k-$100k per integration)

With the CMS-0057-F deadline (Jan 1, 2027), most payers need to support FHIR APIs but have no clear path.

## What I Built

A production-ready platform that: - Handles X12 EDI (270/271/276/277/278/837/835/275) ↔ FHIR R4 transformation - Deploys to any cloud (Azure/AWS/GCP via Kubernetes) - Zero-code payer onboarding (5 minutes vs weeks) - CMS-0057-F compliant out of the box - 424 automated tests

Tech stack: TypeScript/Node.js, Kubernetes, Argo Workflows, Kafka, HashiCorp Vault

## Why Open Source

Healthcare interoperability should be a solved problem. The industry is fragmented with proprietary solutions. I wanted to create a reference implementation that: - Shows how to do FHIR properly - Avoids vendor lock-in - Reduces barrier to entry for health tech startups - Helps payers meet regulatory deadlines

## Current Status

- v3.0.0 just shipped (multi-cloud support) - 424 tests passing - Production deployments in test environments - Apache 2.0 license

Repo: https://github.com/aurelianware/cloudhealthoffice

Would love feedback from the HN community, especially around: - Multi-cloud deployment patterns - FHIR implementation edge cases - Healthcare compliance automation

Happy to answer questions!

Show HN: Cloud Health Office – Open-source multi-cloud EDI+FHIR platform