Patient Identifier Cross-referencing for mobile (PIXm)
3.0.5-current - ci-build International flag

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.0.5-current 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.0.5-current
Active as of 2024-07-08 Computable Name: IHE_PIXm_Consumer

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

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement IHE.PIXm.Consumer

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

  • Implementation Guide Version: 3.0.5-current
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: 2024-07-08 16:49:44+0000
  • 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

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 TypeProfileRSUCSearches_include_revincludeOperations
Patient 

Resource Conformance: supported Patient

Core FHIR Resource
Patient
Reference Policy
Interaction summary

    Extended Operations
    ConformanceOperationDocumentation
    SHALL$$ihe-pix