CH EPR mHealth (R4)
3.0.0 - DSTU3 Switzerland flag

This page is part of the CH EPR mHealth (R4) (v3.0.0: DSTU3) 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

Provide Document Bundle [ITI-65]

This section describes the additional requirements for the Swiss EPR of the Provide Document Bundle [ITI-65] transaction defined in the MHD Profile published in the IHE ITI Trial Implementation “Mobile Access to Health Documents”.

Scope

In the Swiss EPR the transaction is used by the MHD Document Source to store documents in the EPR.

Actor Roles

Actor: Document Source
Role: Sends documents and metadata to the Document Recipient.
Actor: Document Recipient
Role: Accepts the document and metadata sent from the Document Source.

Referenced Standards

  1. Mobile access to Health Documents (MHD), Rev. 4.0.2 – Trial-Implementation, November 8, 2021
  2. This MHD Profile is based on Release 4 of the HL7® FHIR® standard.

Messages

Interaction Diagram for [ITI-65]Document SourceDocument RecipientRequest to publish documentsDocuments published

Provide Document Bundle Request Message

The FHIR Bundle.meta.profile shall have the following value:

https://profiles.ihe.net/ITI/MHD/StructureDefinition/IHE.MHD.Comprehensive.ProvideBundle

The additional Swiss EPR metadata is defined with:

The request Bundle SHALL follow the CH MHD Provide Document Bundle Comprehensive Profile (example: Bundle: 2-7-BundleProvideDocument).

DeletionStatus

The optional metadata about the DeletionStatus of the document is represented in the DocumentReference using the extension with the URL http://fhir.ch/ig/ch-epr-mhealth/StructureDefinition/ch-ext-deletionstatus. The values are defined in the ValueSet DocumentEntry.Ext.EprDeletionStatus.

SubmissionSet.Author.AuthorRole

The SubmissionSet.Author element MAY be used to track the user who made the latest changes to the document metadata. If present, the value of the AuthorRole attribute SHALL be taken from the SubmissionSet.Author.AuthorRole value set with the OID 2.16.756.5.30.1.127.3.10.1.41. The required metadata about the AuthorRole of the Author is represented in the List for the SubmissionSet using the extension with the URL http://fhir.ch/ig/ch-epr-mhealth/StructureDefinition/ch-ext-author-authorrole. The values are defined in the ValueSet SubmissionSet.Author.AuthorRole.

DocumentEntry.originalProviderRole

An extra metadata attribute SHALL be used to distinguish document originally provided by patients or their representatives from documents originally provided by healthcare professionals, assistants, technical users or document administrators. The extra metadata attribute SHALL be set by the Document Source actor to the role value of the current user and SHALL NOT be updated by Update Initiator or Document Administrator actors. The required metadata about the originalProviderRole of the Author is represented in the DocumentReference using the extension with the URL http://fhir.ch/ig/ch-epr-mhealth/StructureDefinition/ch-ext-author-authorrole. The values are defined in the ValueSet DocumentEntry.originalProviderRole.

Provide Document Bundle Response Message

The response Bundle SHALL follow the CH MHD Provide Document Bundle Comprehensive Response Profile (example: Bundle: 2-7-BundleProvideDocument-Response).

CapabilityStatement Resource

The CapabilityStatement resource for the Document Source is MHD Document Source.

The CapabilityStatement resource for the Document Recipient is MHD Document Recipient.

Security Consideration

TLS SHALL be used. This national extension enforces authentication and authorization of access to the Document Recipient using the IUA profile with extended access token. Consequently the Provide Document Bundle [ITI-65] request must authorize using the [ITI-72] transaction of the IUA profile.

The traceparent header is required, as described in Trace Context header.

Security Audit Considerations

Document Source Audit

The Document Source shall be able to record an Audit Event for Provide Bundle Transaction at Source. Audit Example for a Provide Bundle Transaction from source perspective.

Document Recipient Audit

The Document Recipient shall be able to record an Audit Event for Provide Bundle Transaction at Recipient. Audit Example for a Provide Bundle Transaction from recipient perspective.