CH EPR FHIR (R4)
4.0.1-ballot - ballot Switzerland flag

This page is part of the CH EPR FHIR (R4) (v4.0.1-ballot: DSTU 4 Ballot 2) based on FHIR (HL7® FHIR® Standard) 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

CapabilityStatement: PIXm Patient Identifier Cross-reference Manager (server)

Official URL: http://fhir.ch/ig/ch-epr-fhir/CapabilityStatement/CH.PIXm.Manager Version: 4.0.1-ballot
Draft as of 2020-07-07 Computable Name: CH_PIXm_Manager

Copyright/Legal: CC0-1.0

The Patient Identifier Cross-reference Manager CapabilityStatement expresses the requirements that shall be provided. - using FHIR R4 - using json and xml encoding - support the $ihe-pix operation - support conditional update for [ITI-104] - support conditional delete for [ITI-104] if Remove Patient Option is supported - used with IHE-IUA

Raw OpenAPI-Swagger Definition file | Download

PIXm Patient Identifier Cross-reference Manager (server)

  • Implementation Guide Version: 4.0.1-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: 2020-07-07
  • Published by: eHealth Suisse

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: server

PIXm server resolves the local ID sent with the request to the MPI-PID and EPR-SPID [ITI-83]. PIXm server stores the patient data provided with the request and assigns it to or creates a master patient record and a MPI-PID [ITI-104].

Security

TLS SHALL be used together with IUA basic access token

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
PatientSupported Profiles
  CH PIXm Patient Feed		y

Resource Conformance: supported Patient

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

Supported Profiles

http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ch-pixm-patient-feed