Patient Matching
Category: Healthcare Standards
Node id: patient-matching
Standards: HIPAA, GDPR, SOC2
Handles patient identity matching, MPI operations, deduplication, merging, and cross-system linking
What it does
- Probabilistic and deterministic patient matching
- MPI (Master Patient Index) search with confidence scoring
- Duplicate patient detection and deduplication
- Record merging with configurable strategies (most_recent, most_complete)
- Cross-system patient identity linking
- Configurable match confidence thresholds
Use cases
- Patient identity resolution across hospital systems
- Duplicate record cleanup in EHR migrations
- Cross-facility patient linking for HIE networks
- MPI maintenance and quality assurance
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
demographics | json | No | Patient demographics for search |
patient | json | No | Patient data for matching |
candidates | json | No | Candidate patients for comparison |
patients | json | No | Patient list for deduplication |
master_patient | json | No | Master patient record for merge |
merge_patients | json | No | Patient records to merge |
source_patient | json | No | Source patient for linking |
target_patient_id | text | No | Target patient ID for linking |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Patient matching data (search results, match scores, duplicates, merged records, links) |
has_match | boolean | No | Whether a match was found |
success | boolean | No | Operation success flag |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | No | search | search, match, deduplicate, merge, link | Patient matching operation to perform |
| Min Confidence | min_confidence | number | No | 0.8 | min 0; max 1 | Minimum match confidence threshold (0.0-1.0) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Algorithm | algorithm | string | No | probabilistic | Matching algorithm (probabilistic, deterministic) | |
| Duplicate Threshold | duplicate_threshold | number | No | 0.95 | min 0; max 1 | Confidence threshold for duplicate detection (0.0-1.0) |
| Merge Strategy | merge_strategy | string | No | most_recent | Strategy for merging records (most_recent, most_complete) | |
| Target System | target_system | string | No | unknown | Target system identifier for linking |
Errors
| Code | Description |
|---|---|
DEMOGRAPHICS_REQUIRED | Demographics data required for search operation |
PATIENT_REQUIRED | Patient data required for match operation |
PATIENTS_REQUIRED | Patient list required for deduplicate operation |
MERGE_DATA_REQUIRED | Master patient and merge patients required for merge |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Result shape varies by operation: search returns matches/best_match, match returns match_results, deduplicate returns duplicate_groups, merge returns merged_patient, link returns link object
- Confidence thresholds: >=0.95 = exact, >=0.85 = probable, >=0.70 = possible, <0.70 = unlikely
- Match scoring weights: SSN(30) > MRN(25) > DOB(20) > last_name(15) > first_name(10) > gender(5) > phone(3) > zip(2)
- has_match is true when at least one match meets the confidence threshold (search) or 0.9 (match)
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..