Integrations

Integrations connect the Health AI Platform to external or cross-service data sources.

In this repository, three integration themes matter most:

1. Patient Graph for core clinical context
2. Junction for deployment-specific clinical data connectivity
3. Genetics inputs as part of workflow context and condition evaluation

Integration model

The platform treats integrations as inputs to orchestration, not as hidden side effects.

External system or service
        |
        v
Typed client or validated config
        |
        v
Normalized runtime context
        |
        v
Workflow or agent execution

Sections

• Junction
• Patient Graph
• Genetics Inputs

Example: normalize external data into workflow context

const context = {
  patientId: 'user_123',
  data: {
    biomarker: { TSH: 4.2 },
    medications: ['metformin'],
    genetics: { MTHFR: 'C677T/C677T' },
  },
};

The workflow engine only needs this normalized shape. It does not need to know whether a value came from Patient Graph, a manual form, or a future external adapter.

Current-state guidance

• Use Patient Graph when you need concrete, repo-backed APIs today.
• Treat Junction as an integration seam documented by environment and deployment guidance.
• Treat Genetics Inputs as supported context data rather than a dedicated vendor integration in this branch.