StructureDefinition-IHE.mCSD.Endpoint.DocShare

Source

medcom.sor.mcsd#current:Mobile Care Services Discovery (mCSD) (v4.0.1)

resourceType

StructureDefinition

IHE.mCSD.Endpoint.DocShare

canonical

https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint.DocShare

version

3.8.1-current

status

active

publisher

IHE IT Infrastructure Technical Committee

name

MCSDEndpointDocShare

title

mCSD Endpoint for Document Sharing

date

2023-05-08T13:26:42+00:00

description

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?

jurisdictions

fhirVersion

4.0.1

kind

resource

abstract

false

sdTtype

Endpoint

derivation

constraint

base

https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint

Usages

mCSD Organization Affiliation DocumentSharing (target profile)
IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Supplier (profile)
IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Consumer (profile)
IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Supplier (profile)
IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Consumer (profile)

Name	Flags	Card.	Type	Description & Constraints
Endpoint			MCSDEndpoint
specificType	S	0..*	CodeableConcept	Endpoint Specific Type URL: https://profiles.ihe.net/ITI/mCSD/StructureDefinition/ihe-endpointspecifictype Binding: mCSD Endpoint Types ValueSet ( preferred )
identifier				should be the homeCommunityId(s)
connectionType				Binding: mCSD Endpoint Core Document Sharing Types ValueSet ( required )
name		.. 0
payloadType	S			FormatCode(s)
payloadMimeType	S
address
header		.. 0
Documentation for this format

Produced 08 Sep 2023