Perform IHE PIXm cross-reference patient identifiers using the $ihe-pix operation

domain: profiles.ihe.net · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Identify the PIXm Patient Identifier Cross-reference Manager actor endpoint; it exposes the $ihe-pix operation on the Patient resource type as defined in IHE PIXm v3.1.0 (transaction ITI-83)
  2. Invoke the type-level operation: GET [base]/Patient/$ihe-pix?sourceIdentifier=<system>|<value> where sourceIdentifier is the known patient identifier in a specific domain (e.g., 'urn:oid:1.2.840.114350.1.13.0|MRN-12345')
  3. Optionally add the targetSystem parameter to restrict returned identifiers to a specific domain: GET [base]/Patient/$ihe-pix?sourceIdentifier=<system>|<value>&targetSystem=<target-oid> to retrieve only the identifier in the target system
  4. Parse the Parameters response resource: the server returns a Parameters resource with parameter elements named 'targetIdentifier' (each containing an Identifier for a cross-referenced domain) and 'targetId' (containing a FHIR Patient resource reference)
  5. Use the returned cross-referenced identifiers to look up the patient in other systems or to populate the patient identifier field in a resource being submitted to another domain
  6. Handle 'patient not found' (404) or 'identifier ambiguous' (OperationOutcome) responses by falling back to PDQm demographics query for patient matching

Known gotchas

Related routes

Query a patient's identities across systems using IHE PIXm and PDQm mobile profiles
profiles.ihe.net · 5 steps · unrated
implement classic hl7v2-based ihe pdq and pix patient matching (iti-21 and iti-9) distinct from the newer fhir-based pdqm/pixm mobile profiles
profiles.ihe.net · 5 steps · unrated
Discover a patient's identity across communities using IHE XCPD Cross-Community Patient Discovery
profiles.ihe.net · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans