abstractbaseDefinitioncopyrightdate- Values Differ
descriptionexperimentalfhirVersionjurisdiction
jurisdiction[0]kindnamepublisherpurposestatustitletypeurlversion- Values Differ
| Left: | mCSD Endpoint for Document Sharing (https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint.DocShare) |
| Right: | mCSD Endpoint for Document Sharing (https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint.DocShare) |
| Error | StructureDefinition.version | Values for version differ: '3.8.0' vs '3.9.0' |
| Information | StructureDefinition.date | Values for date differ: '2022-08-12T09:41:58-05:00' vs '2024-11-22T14:08:54+00:00' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint | ||
| copyright | |||
| date | 2022-08-12T09:41:58-05:00 | 2024-11-22T14:08:54+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? | ||
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
| jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 | ||
| kind | resource | ||
| name | MCSDEndpointDocShare | ||
| publisher | IHE IT Infrastructure Technical Committee | ||
| purpose | |||
| status | active | ||
| title | mCSD Endpoint for Document Sharing | ||
| type | Endpoint | ||
| url | https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint.DocShare | ||
| version | 3.8.0 | 3.9.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Endpoint | 0..* | MCSDEndpoint | The technical details of an endpoint that can be used for electronic services | 0..* | MCSDEndpoint | The technical details of an endpoint that can be used for electronic services | |||||||||||
 id | Σ | 0..1 | string | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..0 | ?!Σ | 0..0 | |||||||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 Slices for extension | 0..* | Extension | Extension Slice: Unordered, Open by value:url | 0..* | Extension | Extension Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..0 | ?! | 0..0 | |||||||||||||
| identifier | Σ | 0..* | Identifier | should be the homeCommunityId(s) | Σ | 0..* | Identifier | should be the homeCommunityId(s) | |||||||||
| status | ?!SΣ | 1..1 | code | represents the current status of this endpoint. Binding: ?? (required): The status of the endpoint. | ?!SΣ | 1..1 | code | represents the current status of this endpoint. Binding: ?? (required): The status of the endpoint. | |||||||||
| connectionType | Σ | 1..1 | Coding | Protocol/Profile/Standard to be used with this endpoint connection Binding: ?? (required) | Σ | 1..1 | Coding | Protocol/Profile/Standard to be used with this endpoint connection Binding: ?? (required) | |||||||||
| name | Σ | 0..0 | Σ | 0..0 | |||||||||||||
| managingOrganization | Σ | 1..1 | Reference(mCSD Organization) | Organization that manages this endpoint. | Σ | 1..1 | Reference(mCSD Organization) | Organization that manages this endpoint. | |||||||||
| contact | 0..* | ContactPoint | Contact details for source (e.g. troubleshooting) | 0..* | ContactPoint | Contact details for source (e.g. troubleshooting) | |||||||||||
| period | SΣ | 0..1 | Period | Overall deployment lifetime for this endpoint. | SΣ | 0..1 | Period | Overall deployment lifetime for this endpoint. | |||||||||
| payloadType | SΣ | 1..* | CodeableConcept | FormatCode(s) Binding: ?? (example) | SΣ | 1..* | CodeableConcept | FormatCode(s) Binding: ?? (example) | |||||||||
| payloadMimeType | SΣ | 0..* | code | Mimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this) Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed. | SΣ | 0..* | code | Mimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this) Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed. | |||||||||
| address | Σ | 1..1 | url | The technical base address for connecting to this endpoint | Σ | 1..1 | url | The technical base address for connecting to this endpoint | |||||||||
| header | 0..0 | 0..0 | |||||||||||||||
| Documentation for this format | |||||||||||||||||