Patient Identifier Cross-referencing for mobile (PIXm)
3.1.0 - Trial-Implementation

Patient Identifier Cross-referencing for mobile (PIXm), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 3.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.PIXm/ and changes regularly. See the Directory of published versions

## CapabilityStatement: IHE ITI Patient Identifier Cross-referencing for mobile (PIXm) - Consumer (client)

Official URL: https://profiles.ihe.net/ITI/PIXm/CapabilityStatement/IHE.PIXm.Consumer | Version: 3.1.0
Active as of 2025-05-30 | Computable Name: IHE_PIXm_Consumer

The Patient Identifier Cross-reference Consumer Actor CapabililtyStatement expresses the requirements that can be utilized while being compliant.

- using FHIR R4
- using json or xml encoding
- ITI-83 the $ihe-pix operation
- should use a security framework. Recommend ATNA, encouraged IHE-IUA or SMART-app-launch

Raw OpenAPI-Swagger Definition file | Download

## IHE ITI Patient Identifier Cross-referencing for mobile (PIXm) - Consumer (client)

- Implementation Guide Version: 3.1.0
- FHIR Version: 4.0.1
- Supported Formats: `application/fhir+xml`, `application/fhir+json`
- Published on: 2025-05-30 13:12:36-0600
- Published by: IHE IT Infrastructure Technical Committee

> Note to Implementers: FHIR Capabilities

> Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

## FHIR RESTful Capabilities

### Mode: `client`

PIXm client queries for Patient Identity Cross-reference matching a query parameters

Security

> Recommend ATNA, encouraged IHE-IUA or SMART-app-launch

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Patient |  |  |  |  |  |  |  |  | `$$ihe-pix`

#### Resource Conformance: supportedPatient

Core FHIR Resource
Patient
Reference Policy
Interaction summary

Extended Operations

Conformance | Operation | Documentation
--- | --- | ---
SHALL | $$ihe-pix |