Getting Started
Import the SDK into IntelliJ IDEA or Eclipse and run a local workflow.
Requirements
| Component | Requirement |
|---|---|
| Java | JDK 25 |
| Build | Maven |
| IDE | IntelliJ IDEA or Eclipse |
| Project | FireSonic SDK distribution |
Project structure
firesonic-sdk/
├── pom.xml
├── src/
│ └── main/
│ └── java/
│ └── io/firesonic/runner/
│ └── RunSdk.java
├── config/
│ ├── sdk.properties
│ ├── firesonic-sdk.lic
│ └── certs/
├── scripts/
│ ├── Main.groovy
│ ├── script.properties
│ └── core/
├── rules/
│ └── semantic/
├── input/
└── output/
| Path | Purpose |
|---|---|
pom.xml | Maven project definition and SDK dependencies. |
src/main/java/io/firesonic/runner/RunSdk.java | Local SDK launcher used to run or debug workflows from the IDE. |
config/sdk.properties | Local SDK runtime settings such as input, output mode, FHIR endpoint and SDK directories. |
config/firesonic-sdk.lic | FireSonic Developer SDK license file. |
config/certs/ | Additional trusted TLS certificates used by local SDK integrations when required. |
scripts/script.properties | Customer workflow configuration injected into scripts. |
scripts/Main.groovy | Main integration script implementing IntegrationScript. |
scripts/core/ | Reusable helper classes and customer-specific workflow components. |
rules/semantic/ | Semantic validation rules executed before FHIR delivery. |
input/ | Representative HL7 messages used for local testing. |
output/ | Generated FHIR Bundles and local execution results. |
Two configuration files, two responsibilities
sdk.properties controls local SDK execution. script.properties contains customer and workflow settings injected into Groovy scripts.
IDE setup
IDE
Eclipse
- Extract the SDK distribution to a local working folder.
- Select File → Import → Maven → Existing Maven Projects.
- Choose the extracted
firesonic-sdkdirectory and wait for Maven dependencies to resolve. - Set the project JRE to Java 25.
- Right-click the project and select Configure → Convert to Groovy Project.
- If dependencies are missing, run Maven → Update Project and enable Force Update of Snapshots/Releases.
IntelliJ IDEA
- Extract the SDK distribution to a local working folder.
- Open the SDK directory or its
pom.xmlas a Maven project. - Set the Project SDK to Java 25.
- Allow IntelliJ IDEA to import and resolve Maven dependencies.
- Mark
scripts/andrules/as source roots when required. - Create or select the SDK launcher configuration and choose Run or Debug.
First local run
Start with local Bundle output. This keeps the first execution independent of a FHIR server and makes it easy to inspect the generated resources.
sdk.input.dir=./input
sdk.output.mode=folder
sdk.output.dir=./output
sdk.scripts.dir=./scripts
IDE
IntelliJ IDEA
- Place a representative HL7 message under
input/. - Configure
config/sdk.properties. - Open
src/main/java/io/firesonic/runner/RunSdk.javain IntelliJ IDEA. - Run or debug
RunSdk.javausing the SDK launcher configuration. - Inspect the generated FHIR Bundle under
output/. - When needed, switch the SDK output mode to a development FHIR server and run the same workflow again.
Eclipse
- Place a representative HL7 message under
input/. - Configure
config/sdk.properties. - Open
src/main/java/io/firesonic/runner/RunSdk.javain Eclipse. - Choose Run As → Java Application or Debug As → Java Application.
- Inspect the generated FHIR Bundle under
output/. - When needed, switch the SDK output mode to a development FHIR server and run the same workflow again.
