This page is part of the IHE ITI Mobile Care Services Discovery (v4.0.0-comment: Publication Ballot 8) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Mobile Care Services Discovery (mCSD) Home

Official URL: https://profiles.ihe.net/ITI/mCSD/ImplementationGuide/ihe.iti.mcsd				Version: 4.0.0-comment
Active as of 2025-03-12				Computable Name: IHE_ITI_mCSD

The Mobile Care Services Discovery (mCSD) Profile supports RESTful queries across related care services resources.

The loosely coupled design and flexible querying capability of the mCSD Profile means it can be deployed within a variety of eHealth architectures and support a wide array of care workflows.

Organization of This Guide

This guide is organized into the following main sections:

1. Volume 1: Profiles
   1. Introduction
   2. Actors, Transactions, and Content Modules
   3. Actor Options
   4. Required Groupings
   5. Overview
   6. Security Considerations
   7. Cross-Profile Considerations
   8. Deployment Considerations
   9. Endpoint Usage Considerations
2. Volume 2: Transaction Detail
   1. Find Matching Care Services [ITI-90]
   2. Request Care Services Updates [ITI-91]
   3. Care Services Feed [ITI-130]
3. Other
   1. Changes to Other IHE Specifications
   2. Download and Analysis
   3. Test Plan

Click on any of the links above, navigate the contents using the table of contents, or if you are looking for a specific artifact, check out the index.

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 is 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.