Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam

Left:US Core CareTeam Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam)
Right:US Core CareTeam Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam)

Messages

ErrorStructureDefinition.versionValues for version differ: '5.0.1' vs '7.0.0'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2023-10-17'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International / Cross-Group Projects'
InformationStructureDefinition.definitionValues for definition differ: '\-' vs 'The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/CareTeam
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
        .date2022-04-202023-10-17
        • Values Differ
        .descriptionThis profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific uses cases.The US Core CareTeam Profile inherits from the FHIR [CareTeam](https://hl7.org/fhir/R4/careteam.html) resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient to promote interoperability and adoption through common implementation. It specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.
        • Values Differ
        .experimentalfalse
          .fhirVersion4.0.1
            .jurisdiction
              ..jurisdiction[0]urn:iso:std:iso:3166#US
                .kindresource
                  .nameUSCoreCareTeam
                    .publisherHL7 International - Cross-Group ProjectsHL7 International / Cross-Group Projects
                    • Values Differ
                    .purpose
                      .statusactive
                        .titleUS Core CareTeam Profile
                          .typeCareTeam
                            .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam
                              .version5.0.17.0.0
                              • Values Differ

                              Structure

                              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                              .. CareTeam 0..*CareTeamPlanned participants in the coordination and delivery of care for a patient or group
                              0..*CareTeamPlanned participants in the coordination and delivery of care for a patient or group
                                ... 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..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                      ... 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
                                            ... extension 0..*ExtensionAdditional content defined by implementations
                                            0..*ExtensionAdditional content defined by implementations
                                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                              ?!0..*ExtensionExtensions that cannot be ignored
                                                ... identifier Σ0..*IdentifierExternal Ids for this team
                                                Σ0..*IdentifierExternal Ids for this team
                                                  ... status ?!SΣ0..1codeproposed | active | suspended | inactive | entered-in-error
                                                  Binding: ?? (required): Indicates whether the team is current , represents future intentions or is now a historical record.

                                                  ?!SΣ0..1codeproposed | active | suspended | inactive | entered-in-error
                                                  Binding: ?? (required): Indicates whether the team is current , represents future intentions or is now a historical record.

                                                    ... category Σ0..*CodeableConceptType of team
                                                    Binding: ?? (example): Indicates the type of care team.


                                                    Σ0..*CodeableConceptType of team
                                                    Binding: ?? (example): Indicates the type of care team.


                                                      ... name Σ0..1stringName of the team, such as crisis assessment teamΣ0..1stringName of the team, such as crisis assessment team
                                                        ... subject SΣ1..1Reference(US Core Patient Profile)Who care team is forSΣ1..1Reference(US Core Patient Profile S | Group)Who care team is for
                                                          ... encounter Σ0..1Reference(Encounter)Encounter created as part ofΣ0..1Reference(Encounter)Encounter created as part of
                                                            ... period Σ0..1PeriodTime period team coversΣ0..1PeriodTime period team covers
                                                              ... participant SC1..*BackboneElementMembers of the team
                                                              ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
                                                              SC1..*BackboneElementMembers of the team
                                                              ctm-1: CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                  0..*ExtensionAdditional content defined by implementations
                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                      .... role SΣ1..1CodeableConceptType of involvement
                                                                      Binding: ?? (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc.


                                                                      SΣ1..1CodeableConceptType of involvement
                                                                      Binding: ?? (extensible): Indicates specific responsibility of an individual within the care team, such as Primary physician, Team coordinator, Caregiver, etc.


                                                                        .... member SΣ1..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile S | US Core PractitionerRole Profile S | US Core CareTeam Profile | US Core RelatedPerson Profile S)Who is involvedSΣ1..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile S | US Core CareTeam Profile | US Core RelatedPerson Profile S)Who is involved
                                                                          .... onBehalfOf Σ0..1Reference(Organization)Organization of the practitionerΣ0..1Reference(Organization)Organization of the practitioner
                                                                            .... period 0..1PeriodTime period of participant0..1PeriodTime period of participant
                                                                              ... reasonCode 0..*CodeableConceptWhy the care team exists
                                                                              Binding: ?? (example): Indicates the reason for the care team.


                                                                              0..*CodeableConceptWhy the care team exists
                                                                              Binding: ?? (example): Indicates the reason for the care team.


                                                                                ... reasonReference 0..*Reference(Condition)Why the care team exists
                                                                                0..*Reference(Condition)Why the care team exists
                                                                                  ... managingOrganization Σ0..*Reference(Organization)Organization responsible for the care team
                                                                                  Σ0..*Reference(Organization)Organization responsible for the care team
                                                                                    ... telecom 0..*ContactPointA contact detail for the care team (that applies to all members)
                                                                                    0..*ContactPointA contact detail for the care team (that applies to all members)
                                                                                      ... note 0..*AnnotationComments made about the CareTeam
                                                                                      0..*AnnotationComments made about the CareTeam

                                                                                        doco Documentation for this format