Full-stack engineer building healthcare interoperability tools — FHIR R4, HL7v2, SMART-on-FHIR, Epic integrations.

productHunt

github

Kundan Sinha • Peerlist

<h3>Technical Overview</h3>This project provides a comprehensive TypeScript SDK designed to streamline healthtech integrations. It addresses two common challenges: establishing connectivity with live hospital systems via SMART on FHIR, and translating between legacy HL7v2/C-CDA formats and the modern FHIR standard. The SDK is modular, consisting of six independently installable packages, allowing users to integrate only the necessary components.<ul><li>Core Functionality: Offers HL7v2/CDA to FHIR translation, US Core validation, and essential primitives like audit logging, encrypted storage, scope enforcement, and TLS enforcement.</li><li>Protocol Adapters: Includes adapters for MLLP, HTTP, and file/SFTP ingest and delivery.</li><li>Secrets Management: Provides implementations for various secrets providers, including OS keychain, HashiCorp Vault, and AWS Secrets Manager.</li><li>SMART on FHIR Connector: A vendor-agnostic connector for SMART on FHIR, supporting backend-services and authorization_code+PKCE authentication, read/write/search operations, and Bulk Data $export.</li><li>Pipeline Engine: A deployable runtime for pipelines, featuring YAML configuration, persistence, audit logging, and a CLI.</li><li>MCP Tooling: Offers an MCP tool surface over a scope-checked, audit-logged API.</li></ul><h3>Compliance and Security</h3>The SDK is built with HIPAA and SOC 2 compliance in mind, enforcing TLS, tamper-evident audit trails, and secure secret management. However, it's crucial to understand that using this library does not automatically grant compliance; organizational practices and audits are essential.<h3>Installation and Usage</h3>While not yet published to npm, the project can be built from source. Installation involves cloning the repository, running npm install, and then building the packages. Once published, packages can be installed via npm, such as @interop-gateway/core for translation and validation, or @interop-gateway/mcp for the full MCP server.Example usage demonstrates translating HL7v2 messages to FHIR bundles and connecting to live SMART on FHIR endpoints.