Patient Identifier Cross-referencing for mobile (PIXm)
3.0.4 - Trial-Implementation International flag

This page is part of the IHE Patient Identifier Cross-referencing for Mobile (v3.0.4: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, 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.0.4
Active as of 2024-02-22 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.0.4
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: Thu Feb 22 13:12:36 CST 2024
  • 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

Summary of System-wide Interactions

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 TypeProfileRSUCDSearches_include_revincludeOperations
PatientSupported profiles:
  PIXm Patient constraints for Feed		yy

Resource Conformance: supportedPatient

Core FHIR Resource
Patient
Reference Policy
Interaction summary
  • Supports update, delete.

Supported Profiles

https://profiles.ihe.net/ITI/PIXm/StructureDefinition/IHE.PIXm.Patient