Publish Analysis
Category: Integration
Node id: analysis-publish
Standards: GDPR, HIPAA
Publish an agent's structured analysis (severity, findings, summary) for a patient to the Connect analyses store, optionally flagging it for FHIR publication.
What it does
- Persists agent analyses keyed by patient + execution for frontend polling
- Tolerant parsing of agent output (object, JSON string, or fenced JSON)
- Optional FHIR publication flag
Runtime
- Performance tier:
medium
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
agent_output | json | No | Agent's structured output: {severity, findings[], summary}. A JSON string (optionally fenced) is also accepted. |
response | text | No | Fallback: raw agent response string parsed as JSON when agent_output is absent |
data | json | Yes | Device-data-source output; supplies patient_id and window |
org_id | text | No | Organization ID (threaded from the pipeline execution) |
execution_id | text | No | Pipeline execution ID, recorded so the result is pollable by the frontend |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
analysis_id | text | No | ID of the stored analysis record |
severity | text | No | Resolved severity (defaults to 'info' when the agent output is invalid) |
summary_short | text | No | Summary truncated to 256 bytes |
validation_failed | boolean | No | True when the agent output was missing required fields |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Publish to FHIR | publish_to_fhir | boolean | No | false | Also flag the analysis for publication as a FHIR resource. | |
| FHIR Server URL | fhir_server_url | string | No | Target FHIR server base URL (used when Publish to FHIR is enabled). |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Pipeline ID | pipeline_id | string | No | Recorded with the published analysis for traceability. | ||
| Pipeline Name | pipeline_name | string | No | Human-readable pipeline name stored alongside the analysis. | ||
| Agent ID | agent_id | string | No | ID of the agent that produced the analysis. |
Errors
| Code | Description |
|---|---|
DATA_REQUIRED | The required 'data' input is missing |
PUBLISH_FAILED | The Connect analyses API returned a non-2xx status |
Runtime notes
- Requires the 'data' input (patient_id + window come from it).
- When the agent output lacks severity/findings, the record is still published with validation_failed=true and severity='info'.
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..