Document Subscription for Mobile (DSUBm)
1.0.1-current - ci-build

Document Subscription for Mobile (DSUBm), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.DSUBm/ and changes regularly. See the Directory of published versions

## Document Subscription for Mobile (DSUBm) Home

Official URL: https://profiles.ihe.net/ITI/DSUBm/ImplementationGuide/ihe.iti.dsubm | Version: 1.0.1-current
Active as of 2025-04-28 | Computable Name: IHE_ITI_DSUBm

The Document Subscription for Mobile (DSUBm) Profile describes the use of document subscription and notification mechanisms for RESTful applications. In a similar way to the DSUB Profile, a subscription is made in order to receive a notification when a document publication event matches the criteria expressed in the subscription.

This profile can be applied in a RESTful-only environment as MHDS but it can also be used with different non-mobile profiles such as XDS.b and DSUB. This profile intends to grant the same functionality as the DSUB Profile and its supplements regarding Document subscription but also adding some other functionalities (e.g., Subscription Search).

This profile intends to be compliant with Subscriptions R5 Backport.

Significant Changes, Open and Closed Issues

### Organization of This Guide

This guide is organized into the following sections:

- Volume 1: Actors, Transactions and Use Cases
  - Actors, Transactions, and Content
  - Actor Options
  - Actor Required Groupings
  - Overview
  - Security Considerations
  - Cross Profile Considerations
- Volume 2: Transaction Detail
  - Resource Subscription [ITI-110]
  - Resource Publish [ITI-111]
  - Resource Notify [ITI-112]
  - Resource Subscription Search [ITI-113]
  - Resource SubscriptionTopic Search [ITI-114]
- Other
  - Changes to Other IHE Specifications
  - Download and Analysis
  - Test Plan

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

### Conformance Expectations

IHE uses the normative words: “REQUIRED”, “REQUIRED NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “recommended”, “MAY”, and “OPTIONAL” according to standards conventions.

#### Required Support

The use of `RequiredSupport` in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

RequiredSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor SHALL populate the elements marked with RequiredSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors SHOULD handle these elements being populated or being absent/empty. Note that sometimes RequiredSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.