19. Informative Annex A - IHE binding (proposed bindings, informative detail)

Role: cross-reference a patient identifier from one domain to another without relying on a single shared identifier across domains. It underlies §5 (subject → local ehr_id). The advisory summarises PIXm as "translating / linking within a community."

Transactions: query via ITI-83 (Mobile Patient Identifier Cross-reference Query, the $ihe-pix operation) with sourceIdentifier=<patientId> and targetSystem=<the domain’s ehr_id system>. Identity feed via ITI-104 (Patient Identity Feed FHIR) seeds the cross-reference with, for example, a local id or an openEHR id.

Used by: N3 (resolution), Step 1 (§4).

Role: find or confirm which person is meant from demographics (name, birth date, location) before identifier mapping, or "searching within a community." An optional input to XCPD matching.

Transactions: ITI-78 (Mobile Patient Demographics Query) and ITI-119 (Patient Demographics Match).

Used by: §4.2 (optional demographic step feeding localization), §14.

Role: discover which communities hold data about the patient and translate identifiers across them, or "cross-community discovery." The proposed localization binding (§14/N4).

Transaction: ITI-55 (Cross Gateway Patient Discovery). The response conveys the patient’s local identifier(s) and home community.

Used by: N4 (localization), Step 1.1 (§4.2).

Not a consent binding. ITI-55 answers a discovery question, which communities hold the patient, and carries no consent decision. Consent is enforced at the node (N27). A deployment wanting Step-1 pre-filtering needs a consent service alongside XCPD, not XCPD itself (§13.2.1).

Role: manage patient identities in a network, covering create, update, merge and split and distributing identity events (FHIR-based, no HL7v2-ADT dependency), or "identity management."

Transactions: ITI-93 (Mobile Patient Identity Feed) and ITI-94 (subscriptions/notifications).

Used by: the identity-lifecycle hooks (§18) and test track 8. Referenced by N3 as the source of identity changes that resolution must respect.

Role: the addressing/directory function, turning an organization or node into its reachable endpoints (PIX Manager, CDR base URL). The proposed addressing binding (§15/N21).

Used by: §15, the registry (N21).

Role: an example document/pointer localization mechanism. Informative only; one of several ways to satisfy N4 (§14.2).