CH EPR FHIR (R4)
4.0.1-ci-build - ci-build 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.1-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-fhir/ and changes regularly. See the Directory of published versions

CapabilityStatement: MHD Document Source (client)

Official URL: http://fhir.ch/ig/ch-epr-fhir/CapabilityStatement/CH.MHD.DocumentSource Version: 4.0.1-ci-build
Draft as of 2020-07-07 Computable Name: CH_MHD_DocumentSource

Copyright/Legal: CC0-1.0

CapabilityStatement for Actor MHD Document Source (client).

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement CH.MHD.DocumentSource

MHD Document Source (client)

  • Implementation Guide Version: 4.0.1-ci-build
  • 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: client

MHD client sends documents and metadata to the Document Recipient [ITI-65].

Security

TLS SHALL be used together with IUA extended access token

Summary of System-wide Interactions
  • Supports the transactioninteraction described as follows:

    http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ch-mhd-providedocumentbundle-comprehensive

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
DocumentReferenceSupported Profiles
  CH MHD DocumentReference Comprehensive
y

Resource Conformance: supported DocumentReference

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