Profile Comparison between http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan

Left:Argonaut CarePlan Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan)
Right:US Core CarePlan Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan'
InformationStructureDefinition.nameValues for name differ: 'Argonaut CarePlan Profile' vs 'USCoreCarePlanProfile'
InformationStructureDefinition.statusValues for status differ: 'draft' vs 'active'
InformationStructureDefinition.dateValues for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17'
InformationStructureDefinition.publisherValues for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#US'
WarningStructureDefinition.fhirVersionValues for fhirVersion differ: '1.0.2' vs '4.0.1'
InformationStructureDefinition.shortValues for short differ: 'Argonaut CarePlan Profile' vs 'Healthcare plan for patient or group'
InformationStructureDefinition.definitionValues for definition differ: 'Healthcare plan for patient or group.' vs '\-'
InformationCarePlanStructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.contained.empty())
InformationCarePlanStructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
InformationCarePlanStructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
InformationCarePlanStructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
InformationCarePlanStructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (text.`div`.exists())
InformationStructureDefinition.commentValues for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
InformationStructureDefinition.definitionValues for definition differ: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.'
InformationStructureDefinition.definitionValues for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
InformationStructureDefinition.commentValues for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
InformationStructureDefinition.commentValues for comment differ: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
InformationStructureDefinition.definitionValues for definition differ: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
InformationStructureDefinition.commentValues for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'
InformationCarePlan.textElement minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
InformationStructureDefinition.definitionValues for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
InformationStructureDefinition.shortValues for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
InformationStructureDefinition.shortValues for short differ: 'generated | extensions | additional | empty' vs 'generated | additional'
InformationStructureDefinition.definitionValues for definition differ: 'generated | additional.' vs 'The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.'
InformationStructureDefinition.commentValues for comment differ: 'The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.' vs 'The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.'
WarningCarePlan.text.divElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.commentValues for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
InformationStructureDefinition.shortValues for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
InformationStructureDefinition.definitionValues for definition differ: 'This records identifiers associated with this care plan that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).' vs 'Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Need to allow connection to a wider workflow.' vs 'Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers.'
InformationStructureDefinition.shortValues for short differ: 'Who care plan is for' vs 'Who the care plan is for'
InformationStructureDefinition.shortValues for short differ: 'proposed | draft | active | completed | cancelled' vs 'draft | active | on-hold | revoked | completed | entered-in-error | unknown'
ErrorCarePlan.statusUnable to resolve left value set http://hl7.org/fhir/ValueSet/care-plan-status at CarePlan.status
InformationStructureDefinition.commentValues for comment differ: 'Any activities scheduled as part of the plan should be constrained to the specified period.' vs 'Any activities scheduled as part of the plan should be constrained to the specified period regardless of whether the activities are planned within a single encounter/episode or across multiple encounters/episodes (e.g. the longitudinal management of a chronic condition).'
InformationStructureDefinition.shortValues for short differ: 'Who is responsible for contents of the plan' vs 'Who is the designated responsible party'
InformationStructureDefinition.definitionValues for definition differ: 'Identifies the individual(s) or ogranization who is responsible for the content of the care plan.' vs 'When populated, the author is responsible for the care plan. The care plan is attributed to the author.'
InformationStructureDefinition.commentValues for comment differ: 'Collaborative care plans may have multiple authors.' vs 'The author may also be a contributor. For example, an organization can be an author, but not listed as a contributor.'
InformationCarePlan.authorElement maximum cardinalities differ: '2147483647' vs '1'
InformationStructureDefinition.commentValues for comment differ: 'There may be multiple axis of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern.' vs 'There may be multiple axes of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Links plan to the conditions it manages. Also scopes plans - multiple plans may exist addressing different concerns.' vs 'Links plan to the conditions it manages. The element can identify risks addressed by the plan as well as active conditions. (The Condition resource can include things like 'at risk for hypertension' or 'fall risk'.) Also scopes plans - multiple plans may exist addressing different concerns.'
InformationStructureDefinition.shortValues for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
InformationStructureDefinition.definitionValues for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
InformationStructureDefinition.shortValues for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
InformationStructureDefinition.shortValues for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
InformationStructureDefinition.shortValues for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
InformationStructureDefinition.definitionValues for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
InformationStructureDefinition.shortValues for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
InformationStructureDefinition.shortValues for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
InformationStructureDefinition.definitionValues for definition differ: 'Detailed description of the type of planned activity; e.g. What lab test, what procedure, what kind of encounter.' vs 'Detailed description of the type of planned activity; e.g. what lab test, what procedure, what kind of encounter.'
InformationStructureDefinition.shortValues for short differ: 'Why activity should be done' vs 'Why activity should be done or why activity was prohibited'
InformationStructureDefinition.definitionValues for definition differ: 'Provides the rationale that drove the inclusion of this particular activity as part of the plan.' vs 'Provides the rationale that drove the inclusion of this particular activity as part of the plan or the reason why the activity was prohibited.'
InformationStructureDefinition.shortValues for short differ: 'Condition triggering need for activity' vs 'Why activity is needed'
InformationStructureDefinition.definitionValues for definition differ: 'Provides the health condition(s) that drove the inclusion of this particular activity as part of the plan.' vs 'Indicates another resource, such as the health condition(s), whose existence justifies this request and drove the inclusion of this particular activity as part of the plan.'
InformationStructureDefinition.shortValues for short differ: 'not-started | scheduled | in-progress | on-hold | completed | cancelled' vs 'not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error'
InformationStructureDefinition.commentValues for comment differ: 'Some aspects of status can be inferred based on the resources linked in actionTaken. Note that 'status' is only as current as the plan was most recently updated.' vs 'Some aspects of status can be inferred based on the resources linked in actionTaken. Note that 'status' is only as current as the plan was most recently updated. The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the activity.'
InformationCarePlan.activity.detail.statusElement minimum cardinalities differ: '0' vs '1'
InformationCarePlan.noteElement maximum cardinalities differ: '1' vs '2147483647'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/CarePlan
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Added the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2016-10-18T00:00:00+11:002023-10-17
      • Values Differ
      .descriptionThis profile sets minimum expectations for the CarePlan resource to record, search, and fetch assessment and plan of treatment data 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 and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases.
      • Added the item 'This profile sets minimum expectations for the CarePlan resource to record, search, and fetch assessment and plan of treatment data 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 and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases.'
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion1.0.24.0.1
      • Values Differ
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
        • Added the item 'urn:iso:std:iso:3166#US'
        .kindresource
          .nameArgonaut CarePlan ProfileUSCoreCarePlanProfile
          • Values Differ
          .publisherArgonaut ProjectHL7 International / Cross-Group Projects
          • Values Differ
          .purpose
            .statusdraftactive
            • Values Differ
            .titleUS Core CarePlan Profile
            • Added the item 'US Core CarePlan Profile'
            .typeCarePlan
              .urlhttp://fhir.org/guides/argonaut/StructureDefinition/argo-careplanhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan
              • Values Differ
              .version7.0.0-ballot
              • Added the item '7.0.0-ballot'

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
              .. CarePlan 0..*CarePlanArgonaut CarePlan Profile
              0..*CarePlanHealthcare plan for patient or group
              • StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.contained.empty())
              • StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
              • StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
              • StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
              • StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (text.`div`.exists())
              ... id Σ0..1idLogical 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: ?? (required): A human language.

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

                    Additional BindingsPurpose
                    ??Max Binding
                      ... text S1..1NarrativeText summary of the resource, for human interpretationS0..1NarrativeText summary of the resource, for human interpretation
                      • Element minimum cardinalities differ: '1' vs '0'
                      .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                        .... extension 0..*ExtensionAdditional Content defined by implementations
                        0..*ExtensionAdditional content defined by implementations
                        Slice: Unordered, Open by value:url
                          .... status S1..1codegenerated | extensions | additional | empty
                          Binding: ?? (required)
                          S1..1codegenerated | additional
                          Binding: ?? (required): Constrained value set of narrative statuses.

                            .... div C1..1xhtmlLimited xhtml content
                            txt-2: The narrative SHALL have some non-whitespace content
                            txt-1: The narrative SHALL contain only the basic html formatting elements described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
                            txt-3: The narrative SHALL contain only the basic html formatting attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
                            SC1..1xhtmlLimited xhtml content
                            txt-1: The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes
                            txt-2: The narrative SHALL have some non-whitespace content
                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                            ... 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 plan
                                  Σ0..*IdentifierExternal Ids for this plan
                                    ... subject S1..1Reference(Argonaut Patient Profile)Who care plan is forSΣ1..1Reference(US Core Patient Profile S | Group)Who the care plan is for
                                      ... status ?!S1..1codeproposed | draft | active | completed | cancelled
                                      Binding: ?? (required)
                                      ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                      Binding: ?? (required): Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.

                                      • Unable to resolve left value set http://hl7.org/fhir/ValueSet/care-plan-status at CarePlan.status
                                      ... context Σ0..1Reference(Encounter | EpisodeOfCare)Created in context of
                                      • Removed this element
                                      ... period Σ0..1PeriodTime period plan coversΣ0..1PeriodTime period plan covers
                                        ... author Σ0..*Reference(Patient | Practitioner | RelatedPerson | Organization)Who is responsible for contents of the plan
                                        Σ0..1Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam)Who is the designated responsible party
                                        • Element maximum cardinalities differ: '2147483647' vs '1'
                                        ... modified Σ0..1dateTimeWhen last updated
                                        • Removed this element
                                        ... category SC1..*CodeableConceptType of plan
                                        Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.


                                        arg-1: Must have a category of 'careplan' and a code system 'http://argonaut.hl7.org'
                                        SΣ1..*CodeableConceptType of plan
                                        Slice: Unordered, Open by pattern:$this
                                        Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.


                                          ... description Σ0..1stringSummary of nature of planΣ0..1stringSummary of nature of plan
                                            ... addresses Σ0..*Reference(Condition)Health issues this plan addresses
                                            Σ0..*Reference(Condition)Health issues this plan addresses
                                              ... support 0..*Reference(Resource)Information considered as part of plan
                                              • Removed this element
                                              ... relatedPlan 0..*BackboneElementPlans related to this one
                                              • Removed this element
                                              ... participant 0..*BackboneElementWho's involved in plan?
                                              • Removed this element
                                              ... goal 0..*Reference(Goal)Desired outcome of plan
                                              0..*Reference(Goal)Desired outcome of plan
                                                ... activity C0..*BackboneElementAction to occur as part of plan
                                                cpl-3: Provide a reference or detail, not both
                                                C0..*BackboneElementAction to occur as part of plan
                                                cpl-3: Provide a reference or detail, not both
                                                  .... id 0..1idxml:id (or equivalent in JSON)0..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
                                                      ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                        .... actionResulting 0..*Reference(Resource)Appointments, orders, etc.
                                                        • Removed this element
                                                        .... progress 0..*AnnotationComments about the activity status/progress
                                                        0..*AnnotationComments about the activity status/progress
                                                          .... reference C0..1Reference(Appointment | CommunicationRequest | DeviceUseRequest | DiagnosticOrder | MedicationOrder | NutritionOrder | Order | ProcedureRequest | ProcessRequest | ReferralRequest | SupplyRequest | VisionPrescription)Activity details defined in specific resourceC0..1Reference(Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription | RequestGroup)Activity details defined in specific resource
                                                            .... detail C0..1BackboneElementIn-line definition of activityC0..1BackboneElementIn-line definition of activity
                                                              ..... id 0..1idxml:id (or equivalent in JSON)0..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
                                                                  ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                    ..... category 0..1CodeableConceptdiet | drug | encounter | observation | procedure | supply | other
                                                                    Binding: ?? (example): High-level categorization of the type of activity in a care plan.

                                                                    • Removed this element
                                                                    ..... code 0..1CodeableConceptDetail type of activity
                                                                    Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.

                                                                    0..1CodeableConceptDetail type of activity
                                                                    Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.

                                                                      ..... reasonCode 0..*CodeableConceptWhy activity should be done
                                                                      Binding: ?? (example): Identifies why a care plan activity is needed. Can include any health condition codes as well as such concepts as "general wellness", prophylaxis, surgical preparation, etc.


                                                                      0..*CodeableConceptWhy activity should be done or why activity was prohibited
                                                                      Binding: ?? (example): Identifies why a care plan activity is needed. Can include any health condition codes as well as such concepts as "general wellness", prophylaxis, surgical preparation, etc.


                                                                        ..... reasonReference 0..*Reference(Condition)Condition triggering need for activity
                                                                        0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Why activity is needed
                                                                          ..... goal 0..*Reference(Goal)Goals this activity relates to
                                                                          0..*Reference(Goal)Goals this activity relates to
                                                                            ..... status ?!0..1codenot-started | scheduled | in-progress | on-hold | completed | cancelled
                                                                            Binding: ?? (required): Indicates where the activity is at in its overall life cycle.

                                                                            ?!1..1codenot-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error
                                                                            Binding: ?? (required): Codes that reflect the current state of a care plan activity within its overall life cycle.

                                                                            • Element minimum cardinalities differ: '0' vs '1'
                                                                            ..... statusReason 0..1CodeableConceptReason for current status
                                                                            Binding: ?? (example): Describes why the current activity has the status it does; e.g. "Recovering from injury" as a reason for non-started or on-hold, "Patient does not enjoy activity" as a reason for cancelling a planned activity.

                                                                            0..1CodeableConceptReason for current status
                                                                              ..... prohibited ?!1..1booleanDo NOT do
                                                                              • Removed this element
                                                                              ..... scheduled[x] 0..1Timing, Period, stringWhen activity is to occur0..1Timing, Period, stringWhen activity is to occur
                                                                                ..... location 0..1Reference(Location)Where it should happen0..1Reference(Location)Where it should happen
                                                                                  ..... performer 0..*Reference(Practitioner | Organization | RelatedPerson | Patient)Who will be responsible?
                                                                                  0..*Reference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device)Who will be responsible?
                                                                                    ..... product[x] 0..1CodeableConcept, Reference(Medication | Substance)What is to be administered/supplied
                                                                                    Binding: ?? (example): A product supplied or administered as part of a care plan activity.

                                                                                    0..1CodeableConcept, Reference(Medication | Substance)What is to be administered/supplied
                                                                                    Binding: ?? (example): A product supplied or administered as part of a care plan activity.

                                                                                      ..... dailyAmount 0..1QuantityHow to consume/day?0..1QuantityHow to consume/day?
                                                                                        ..... quantity 0..1QuantityHow much to administer/supply/consume0..1QuantityHow much to administer/supply/consume
                                                                                          ..... description 0..1stringExtra info describing activity to perform0..1stringExtra info describing activity to perform
                                                                                            ..... kind 0..1codeAppointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription
                                                                                            Binding: ?? (required): Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.

                                                                                            • Added this element
                                                                                            ..... instantiatesCanonical 0..*canonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition)Instantiates FHIR protocol or definition
                                                                                            • Added this element
                                                                                            ..... instantiatesUri 0..*uriInstantiates external protocol or definition
                                                                                            • Added this element
                                                                                            ..... doNotPerform ?!0..1booleanIf true, activity is prohibiting action
                                                                                            • Added this element
                                                                                            .... outcomeCodeableConcept 0..*CodeableConceptResults of the activity
                                                                                            Binding: ?? (example): Identifies the results of the activity.


                                                                                            • Added this element
                                                                                            .... outcomeReference 0..*Reference(Resource)Appointment, Encounter, Procedure, etc.
                                                                                            • Added this element
                                                                                            ... note 0..1AnnotationComments about the plan0..*AnnotationComments about the plan
                                                                                            • Element maximum cardinalities differ: '1' vs '2147483647'
                                                                                            ... instantiatesCanonical Σ0..*canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition)Instantiates FHIR protocol or definition
                                                                                            • Added this element
                                                                                            ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                                                                            • Added this element
                                                                                            ... basedOn Σ0..*Reference(CarePlan)Fulfills CarePlan
                                                                                            • Added this element
                                                                                            ... replaces Σ0..*Reference(CarePlan)CarePlan replaced by this CarePlan
                                                                                            • Added this element
                                                                                            ... partOf Σ0..*Reference(CarePlan)Part of referenced CarePlan
                                                                                            • Added this element
                                                                                            ... intent ?!SΣ1..1codeproposal | plan | order | option
                                                                                            Binding: ?? (required): Codes indicating the degree of authority/intentionality associated with a care plan

                                                                                            • Added this element
                                                                                            ... title Σ0..1stringHuman-friendly name for the care plan
                                                                                            • Added this element
                                                                                            ... encounter Σ0..1Reference(Encounter)Encounter created as part of
                                                                                            • Added this element
                                                                                            ... created Σ0..1dateTimeDate record was first recorded
                                                                                            • Added this element
                                                                                            ... contributor 0..*Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam)Who provided the content of the care plan
                                                                                            • Added this element
                                                                                            ... careTeam 0..*Reference(CareTeam)Who's involved in plan?
                                                                                            • Added this element
                                                                                            ... supportingInfo 0..*Reference(Resource)Information considered as part of plan
                                                                                            • Added this element

                                                                                            doco Documentation for this format