Skip to content

E15 — Cross-system identity & mobility #187

Description

@Taleef7

Epic E15 — Cross-system identity & mobility

Goal: Handle a person existing in multiple provider databases/systems (a provider-database selector), duplicate reconciliation (the DUPLICATE badge), and mobility (employee moves country; patient moves provider/oncologist) so compliance history follows the person.

Why it matters (Doug, June 15): "provider database dropdown (same employee in two different systems)" · "expatriate might move from one country to another" · "someone might move from one oncologist to another" · the DUPLICATE badge in vamsi4.png; employee search in vamsi5.png. WorkWell assumes a single directory; reality is many systems + moving people.

Acceptance

  • An identity model that resolves one person across >=2 source systems (provider-DB selector in the UI; deterministic match/merge keys).
  • Duplicate detection + reconciliation surface (flag + resolve), audited.
  • Compliance history is continuous across a documented move (country / provider change) for a sample subject.

Notes

  • Pairs with E12 (multi-source adapters) and E13 (multi-tenant). Largely design-first; identity matching is sensitive — conservative, auditable, human-in-the-loop. Owner-gated for schema.

Dependency: E12, E13.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendenhancementNew feature or requestepicRoadmap epic (tracks sub-issues)questionFurther information is requestedwebchart-convergenceJune-15 demo feedback: converge with MIE WebChart Vaccine Compliance

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions