FireSonic
Docs/Developer SDK/Developer SDK Overview

Developer SDK Overview

Build customer-specific HL7 v2 → FHIR workflows without modifying the platform core.

The Groovy SDK is the recommended toolkit for customer-specific FireSonic integration logic. It lets developers build, test and debug workflows locally before deploying the same scripts and semantic rules to the runtime platform.

Design principle

Keep generic interoperability in the platform

Scripts should contain local workflow rules, normalization, enrichment, terminology reconciliation, validation reactions, and organization-specific behavior. Generic HL7 → FHIR conversion remains in the platform mapper.

Typical customization

  • Filter messages intentionally.
  • Normalize HL7 values before conversion.
  • Patch or enrich generated FHIR resources.
  • Implement organization-specific workflow logic.
  • Search FHIR and perform terminology translation.
  • Call customer-specific REST services through the managed HTTP client.
  • Use configuration, caches, metrics, retry utilities, and semantic rules.

Engineering workflow

ENGINEERING WORKFLOWdevelop · test · version · validate · deploy
IntelliJ IDEA / EclipseDevelop & debug
→
JUnit / SpockUnit & integration tests
→
GitVersion workflow code
→
GitLab CI / JenkinsCI/CD pipeline
→
FireSonic RuntimeDeploy validated scripts & rules

Develop and debug locally, validate with representative HL7 messages, then deploy the same scripts and semantic rules to FireSonic.