Skip to Content
Health Ai PlatformIntegrationsGenetics Inputs

Genetics Inputs

Genetics appears in the current platform primarily as workflow input, not as a fully implemented vendor integration.

That distinction matters:

  • the workflow DSL and condition evaluator can inspect genetics fields
  • workflows can branch on genetics-related values already present in context.data
  • this repository snapshot does not expose a dedicated genetics ingestion service, SNP pipeline, or external genetics adapter

Current supported pattern

The workflow engine supports dot-path conditions such as:

condition: "genetics.MTHFR === 'C677T/C677T'"

That pattern is covered by the condition evaluator and the test suite.

Example workflow

id: methylation-review-v1
name: Methylation Review
version: 1.0.0
steps:
  - id: check-mthfr
    type: check_biomarker
    condition: "genetics.MTHFR === 'C677T/C677T'"
    action:
      type: check_value
      params:
        biomarker: homocysteine
        threshold: 10
        operator: ">"
  - id: recommend-follow-up
    type: send_notification
    condition: "check-mthfr.result === true"
    action:
      type: notify
      params:
        channel: email
        message: "Review methylation-related biomarkers alongside genetics context."

Example runtime context

const result = await workflow.execute({
  patientId: 'patient-42',
  data: {
    genetics: {
      MTHFR: 'C677T/C677T',
    },
    biomarker: {
      homocysteine: 12.4,
    },
  },
});

Keep genetics data simple and explicit when passing it into workflows:

const context = {
  patientId: 'patient-42',
  data: {
    genetics: {
      MTHFR: 'C677T/C677T',
      APOE: 'E3/E4',
    },
  },
};

What this section does not imply

These docs do not imply that the current branch provides:

  • raw genetics file upload
  • variant normalization pipeline
  • vendor OAuth for genetics systems
  • genomic interpretation APIs

If you add one of those later, keep the split clean:

  1. ingestion and normalization
  2. storage and patient context
  3. workflow branching

Safe usage guidance

Use genetics as one input among many, not as a standalone decision source.

condition: "genetics.MTHFR === 'C677T/C677T' && biomarker.homocysteine > 10"

That keeps the platform aligned with its existing deterministic workflow model.

IntegrationsJunction Integration