Saltar al contenido principal

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​

NameTypeRequiredDescription
agent_outputjsonNoAgent's structured output: {severity, findings[], summary}. A JSON string (optionally fenced) is also accepted.
responsetextNoFallback: raw agent response string parsed as JSON when agent_output is absent
datajsonYesDevice-data-source output; supplies patient_id and window
org_idtextNoOrganization ID (threaded from the pipeline execution)
execution_idtextNoPipeline execution ID, recorded so the result is pollable by the frontend

Output ports​

NameTypeRequiredDescription
analysis_idtextNoID of the stored analysis record
severitytextNoResolved severity (defaults to 'info' when the agent output is invalid)
summary_shorttextNoSummary truncated to 256 bytes
validation_failedbooleanNoTrue when the agent output was missing required fields

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Publish to FHIRpublish_to_fhirbooleanNofalseAlso flag the analysis for publication as a FHIR resource.
FHIR Server URLfhir_server_urlstringNoTarget FHIR server base URL (used when Publish to FHIR is enabled).

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Pipeline IDpipeline_idstringNoRecorded with the published analysis for traceability.
Pipeline Namepipeline_namestringNoHuman-readable pipeline name stored alongside the analysis.
Agent IDagent_idstringNoID of the agent that produced the analysis.

Errors​

CodeDescription
DATA_REQUIREDThe required 'data' input is missing
PUBLISH_FAILEDThe 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.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..