Mobile Care Services Discovery (mCSD)
4.0.0-comment - ballot International flag

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

Resource Profile: mCSD Endpoint for Document Sharing

Official URL: https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint.DocShare Version: 4.0.0-comment
Active as of 2025-03-12 Computable Name: MCSDEndpointDocShare

A profile on the mCSD Endpoint for Document Sharing environments.

Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource. Thus a XCA Responding Gateway will need two Endpoint instances to express Query vs Retrieve.

Open-Issues:

  1. That payloadType and payloadMimeType are either empty to indicate that the endpoint is not constrained; or fully populated.
  2. That payloadType and PayloadMimeType for XCA/XDS/MHD Query and XCA/XDS/MHD Retrieve would be the same thus replicating the capability at both endpoints.
  3. It did not seem right that Query be indicated with a mimeType of ebRegistry as that is not helpful to the use-case.
  4. should the homeCommunityId be mandated here, should those behind it be here, should this be empty?
  5. would a Proxy service that is supporting OrgAff be a good example of NOT putting a homeCommunityId in the endpoint.identifier?

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MCSDEndpoint

NameFlagsCard.TypeDescription & Constraintsdoco
.. Endpoint 0..* MCSDEndpoint The technical details of an endpoint that can be used for electronic services
... Slices for extension Content/Rules for all slices
.... extension:specificType S 0..* CodeableConcept Endpoint Specific Type
URL: https://profiles.ihe.net/ITI/mCSD/StructureDefinition/ihe-endpointspecifictype
Binding: mCSD Endpoint Types ValueSet (preferred)
... identifier 0..* Identifier should be the homeCommunityId(s)
... connectionType 1..1 Coding Protocol/Profile/Standard to be used with this endpoint connection
Binding: mCSD Endpoint Core Document Sharing Types ValueSet (required)
... name 0..0
... payloadType S 1..* CodeableConcept FormatCode(s)
... payloadMimeType S 0..* code Mimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this)
... address 1..1 url The technical base address for connecting to this endpoint
... header 0..0

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Endpoint.connectionTyperequiredMCSDEndpointTypesCoreDocShareVS
https://profiles.ihe.net/ITI/mCSD/ValueSet/MCSDEndpointTypesCoreDocShareVS
from this IG

 

Other representations of profile: CSV, Excel, Schematron