CH EPR FHIR (R4)
4.0.0-ci-build - DSTU3 Switzerland flag

CH EPR FHIR (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-mhealth/ and changes regularly. See the Directory of published versions

CapabilityStatement: PIXm Patient Identity Source (client)

Official URL: http://fhir.ch/ig/ch-epr-fhir/CapabilityStatement/CH.PIXm.Source Version: 4.0.0-ci-build
Draft as of 2020-07-09 Computable Name: CH_PIXm_Source

Copyright/Legal: CC0-1.0

The Patient Identity Source Actor CapabilityStatement expresses the requirements that can be utilized while being compliant. - using FHIR R4 - using json or xml encoding - using conditional update for [ITI-104] - provide supported Patient profile for crosss-referencing for [ITI-104]

Raw OpenAPI-Swagger Definition file | Download

PIXm Patient Identity Source (client)

  • Implementation Guide Version: 4.0.0-ci-build
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: Thu Jul 09 00:00:00 UTC 2020
  • 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: client

PIXm client registers data of a specific patient in the Patient Identifier Cross-reference Manager [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: supportedPatient

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

Supported Profiles

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