Read the reconciliation report to see pipeline stats, inferred relationships, and post-processing actions.

Where to start

The reconciliation summary gives a higher-level view of pipeline activity than the full resolution report. It covers: how many entities were merged and how many relationships were inferred, plus the specific post-processing actions applied (family history reclassification, status inference, symptom linking).

Fetch as Markdown

The default response is a human-readable Markdown report:

curl "https://api.<workspace-id>.clinia.cloud/patients/{patientId}/reconciliation" \
  -H "X-Clinia-API-Key: <clinia-api-key>"

# Reconciliation Summary - Jane Smith

## Pipeline Stats
- Input entities: 21
- Resolved entities: 18 (3 groups merged)
- Explicit relationships: 8
- Inferred relationships: 14
- Post-process actions: 3

## Merged Entity Groups
- Type 2 Diabetes Mellitus (condition): 2 sources, matched by deterministic-code (0.90)
- Metformin 1000mg BID (medication): 2 sources, matched by nlp-normalization (0.78)
- eGFR (lab): 2 sources, matched by embedding-similarity (0.82)

## Inferred Relationships
- metformin → prescribed_for → type_2_diabetes_mellitus (0.90)
- hba1c → monitors → type_2_diabetes_mellitus (0.95)
- chronic_kidney_disease → complication_of → type_2_diabetes_mellitus (0.88)

## Post-Process Actions
- [reclassify-to-family-history] Family history of colon cancer (Z80.0) → family_history type
- [infer-status] "Hx of hypertension" → status: resolved
- [link-symptom] Fatigue → likely parent: type_2_diabetes_mellitus

Fetch as JSON

For programmatic access, append ?format=json:

curl "https://api.<workspace-id>.clinia.cloud/patients/{patientId}/reconciliation?format=json" \
  -H "X-Clinia-API-Key: <clinia-api-key>"

The JSON response has four sections: stats, mergedEntities, inferredRelationships, and postProcessActions.

Understanding inferred relationships

Inferred relationships come from the clinical knowledge base, they are not present in the source records. The pipeline adds them in Phase 2 of the resolution pipeline.

Common inferred types:

Relationship	Example
`prescribed_for`	metformin → type_2_diabetes
`monitors`	hba1c → type_2_diabetes
`complication_of`	ckd → type_2_diabetes
`risk_factor_for`	hyperlipidemia → cad

These relationships are what powers condition stories, the "Current Treatment" and "Monitoring Labs" tables come from prescribed_for and monitors edges, and the "Complications" section comes from complication_of edges.

Understanding post-process actions

Post-processing runs after entity deduplication and adds or adjusts nodes and edges without re-running the 4-layer cascade.

Action type	What it does
`reclassify-to-family-history`	Conditions coded as "hx of X" or "family history of X" are moved to the family history subgraph
`infer-status`	Conditions with textual cues ("resolved", "in remission", "former") have their status set accordingly
`link-symptom`	Non-specific symptoms (fatigue, nausea) are linked to likely parent conditions via clinical knowledge
`filter`	Entities determined to be duplicates or administrative artifacts after the main pipeline are removed

Comparing to the full resolution report

	Reconciliation	Resolution
Scope	Summary stats + actions	Every entity with full provenance
Inferred relationships	✓ Listed	✗ Not included
Post-process actions	✓ Listed	✗ Not included
Conflict detail	✗ Not included	✓ Full field-by-field conflicts
Good for	Understanding what happened overall	Debugging a specific entity

See Audit Entity Resolution for per-entity provenance detail.

Review the Reconciliation Summary