Mobile Care Services Discovery (mCSD)
3.8.1-current - ci-build International flag

Mobile Care Services Discovery (mCSD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 3.8.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of and changes regularly. See the Directory of published versions

Mobile Care Services Discovery (mCSD)

Official URL: Version: 3.8.1-current
Active as of 2024-05-06 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 four main sections:

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

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: Shall, Should, and May according to standards conventions.

mCSD uses Must Support in StructureDefinition profiles. This is equivalent to the IHE use of R2 as defined in Appendix Z.


You can also download:

The source code for this Implementation Guide can be found on IHE GitHub.

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.iti.mcsd.r4) and R4B (ihe.iti.mcsd.r4b) are available.

Dependency Table

.. Mobile Care Services Discovery (mCSD)ihe.iti.mcsd#3.8.1-currentR4
... HL7 Terminology (THO)hl7.terminology.r4#5.5.0R4Automatically added as a dependency - all IGs depend on HL7 Terminology
... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.1.0R4Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
... Basic Audit Log Patterns (BALP)ihe.iti.balp#1.1.4-currentR4

Package hl7.fhir.uv.extensions.r4#5.1.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package ihe.iti.balp#1.1.4-current

The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Mon, May 6, 2024 21:41+0000+00:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.