This page is part of the IHE Patient Identifier Cross-referencing for Mobile (v3.0.2: Trial Implementation) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

1:41. PIXm Home

Official URL: https://profiles.ihe.net/ITI/PIXm/ImplementationGuide/ihe.iti.pixm				Version: 3.0.2
Active as of 2022-03-01				Computable Name: IHE_PIXm
Copyright/Legal: IHE http://www.ihe.net/Governance/#Intellectual_Property

The Patient Identifier Cross-reference for Mobile (PIXm) Profile provides RESTful transactions for mobile and lightweight browser-based applications to create, update and delete patient records in a Patient Identifier Cross-reference Manager and to query the Patient Identifier Cross-reference Manager for a patient’s cross-domain identifiers.

Organization of This Guide

This guide is organized into four main sections:

1. Volume 1: Use-Case analysis
   1. 41.1 PIXm Actors, Transactions, and Content Modules
   2. 41.2 PIXm Actor Options
   3. 41.3 PIXm Required Actor Groupings
   4. 41.4 PIXm Overview
   5. 41.5 PIXm Security Considerations
   6. 41.6 PIXm Cross Profile Considerations
2. Volume 2: Transaction Detail
   1. 3.83 Patient Identifier Cross-reference Query [ITI-83]
   2. 3.104 Patient Identity Feed FHIR [ITI-104]
3. Test Plan
4. Changes to other Profiles

See also the table of contents and the index of artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

PIXm uses Must Support in StructureDefinitions with the definition found in Appendix Z. This is equivalent to the IHE use of R2 as defined in Appendix Z.

Download

You can also download:

• this entire guide,
• the definition resources in json, xml, or ttl format, or
• the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on Github.