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) - Source (client)

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

The Patient Identity Source Actor CapabililtyStatement expresses the requirements that can be utilized while being compliant.

- using FHIR R4
- using json or xml encoding
- using conditional update for ITI-104
- using conditional delete for ITI-104 if Remove Patient Option is supported
- provide supported Patient profile for crosss-referencing for ITI-104
- 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) - Source (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`

The PIXm Source is the producer and publisher of patient identity data.

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 | D | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Patient | Supported Profiles PIXm Patient constraints for Feed |  |  | y |  | y |  |  |  |

#### Resource Conformance: supportedPatient

Core FHIR Resource
Patient
Reference Policy
Interaction summary

- Supports
  `update`

  conditional update for [ITI-104]

  `delete`

  conditional delete for [ITI-104] for Remove Patient Option

Supported Profiles

PIXm Patient constraints for Feed