For PIXm: send a GET request to the Patient Identity Cross-Reference Manager's PIXm endpoint using the patient's known identifier as a query parameter (e.g., GET [base]/Patient?identifier=system|value&_format=json) to retrieve all cross-referenced identifiers
Parse the returned Bundle of Patient resources and extract the identifier elements from each entry to collect all known identifiers for the patient across domains
For PDQm: send a GET request to the Patient Demographics Supplier with demographic search parameters (family, given, birthdate, gender, address-city) to perform a patient demographics query
Evaluate the Bundle entries in the PDQm response, checking Patient.meta.tag or extensions for match confidence scores where supported
Use the resolved patient identifiers from PIXm to scope subsequent FHIR resource queries to the correct patient domain identifier
Known gotchas
PIXm requires that the querying system be a recognized Domain Participant — the manager will not return identifiers for domains the requester is not authorized to see, which can cause confusion when fewer identifiers than expected are returned
PDQm servers must support at minimum one of family, given, birthdate, or identifier as search parameters but implementations vary; always check the CapabilityStatement for supported parameters before constructing a demographics query
PIXm and PDQm use FHIR REST but the IHE profiles constrain which search parameters and response Bundle profiles are required — generic FHIR Patient search may return results that do not conform to PIXm/PDQm response profiles
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp