Profile Comparison between https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint vs https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint

Left:mCSD Endpoint (https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint)
Right:mCSD Endpoint (https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint)

Messages

ErrorStructureDefinition.versionValues for version differ: '3.8.0' vs '3.9.0'
InformationStructureDefinition.dateValues for date differ: '2022-08-12T09:41:58-05:00' vs '2024-11-22T14:08:54+00:00'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Endpoint
      .copyright
        .date2022-08-12T09:41:58-05:002024-11-22T14:08:54+00:00
        • Values Differ
        .descriptionA profile on the mCSD Endpoint. An Organization may be reachable through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization. Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource.
          .experimental
            .fhirVersion4.0.1
              .jurisdiction
                ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
                  .kindresource
                    .nameMCSDEndpoint
                      .publisherIHE IT Infrastructure Technical Committee
                        .purpose
                          .statusactive
                            .titlemCSD Endpoint
                              .typeEndpoint
                                .urlhttps://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.Endpoint
                                  .version3.8.03.9.0
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                  .. Endpoint 0..*EndpointThe technical details of an endpoint that can be used for electronic services
                                  0..*EndpointThe technical details of an endpoint that can be used for electronic services
                                    ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                                        ... implicitRules ?!Σ0..0?!Σ0..0
                                          ... language 0..1codeLanguage of the resource content
                                          Binding: ?? (preferred): A human language.

                                          Additional BindingsPurpose
                                          ??Max Binding
                                          0..1codeLanguage of the resource content
                                          Binding: ?? (preferred): A human language.

                                          Additional BindingsPurpose
                                          ??Max Binding
                                            ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                              ... contained 0..*ResourceContained, inline Resources
                                              0..*ResourceContained, inline Resources
                                                ... Slices for extension 0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                0..*ExtensionExtension
                                                Slice: Unordered, Open by value:url
                                                  ... modifierExtension ?!0..0?!0..0
                                                    ... identifier Σ0..*IdentifierIdentifies this endpoint across multiple systems
                                                    Σ0..*IdentifierIdentifies this endpoint across multiple systems
                                                      ... status ?!SΣ1..1coderepresents the current status of this endpoint.
                                                      Binding: ?? (required): The status of the endpoint.

                                                      ?!SΣ1..1coderepresents the current status of this endpoint.
                                                      Binding: ?? (required): The status of the endpoint.

                                                        ... connectionType Σ1..1CodingProtocol/Profile/Standard to be used with this endpoint connection
                                                        Binding: ?? (extensible)
                                                        Σ1..1CodingProtocol/Profile/Standard to be used with this endpoint connection
                                                        Binding: ?? (extensible)
                                                          ... name Σ0..1stringA name that this endpoint can be identified byΣ0..1stringA name that this endpoint can be identified by
                                                            ... managingOrganization Σ1..1Reference(mCSD Organization)Organization that manages this endpoint.Σ1..1Reference(mCSD Organization)Organization that manages this endpoint.
                                                              ... contact 0..*ContactPointContact details for source (e.g. troubleshooting)
                                                              0..*ContactPointContact details for source (e.g. troubleshooting)
                                                                ... period SΣ0..1PeriodOverall deployment lifetime for this endpoint.SΣ0..1PeriodOverall deployment lifetime for this endpoint.
                                                                  ... payloadType Σ1..*CodeableConceptThe type of content that may be used at this endpoint (e.g. XDS Discharge summaries)
                                                                  Binding: ?? (example)
                                                                  Σ1..*CodeableConceptThe type of content that may be used at this endpoint (e.g. XDS Discharge summaries)
                                                                  Binding: ?? (example)
                                                                    ... payloadMimeType Σ0..*codeMimetype 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.


                                                                    Σ0..*codeMimetype 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..1urlThe technical base address for connecting to this endpointΣ1..1urlThe technical base address for connecting to this endpoint
                                                                        ... header 0..*stringUsage depends on the channel type
                                                                        0..*stringUsage depends on the channel type

                                                                          doco Documentation for this format