Profile Comparison between http://fhir.org/guides/argonaut/StructureDefinition/argo-condition vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns

Left:Argonaut Condition Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-condition)
Right:US Core Condition Problems and Health Concerns Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-condition' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns'
InformationStructureDefinition.nameValues for name differ: 'Argonaut Condition Profile' vs 'USCoreConditionProblemsHealthConcernsProfile'
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 Condition Profile' vs 'Detailed information about conditions, problems or diagnoses'
InformationStructureDefinition.definitionValues for definition differ: 'Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary.' vs '\-'
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.'
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 'Extension'
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 'An 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 condition 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 condition 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 condition as it is known by various participating systems and in a way that remains consistent across servers.'
InformationStructureDefinition.shortValues for short differ: 'Encounter when condition first asserted' vs 'Encounter created as part of'
InformationStructureDefinition.definitionValues for definition differ: 'Encounter during which the condition was first asserted.' vs 'The Encounter during which this Condition was created or to which the creation of this record is tightly associated.'
InformationStructureDefinition.commentValues for comment differ: 'This record indicates the encounter this particular record is associated with. In the case of a 'new' diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first 'known'.' vs 'This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a 'new' diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first 'known'.'
ErrorCondition.codeUnable to resolve left value set http://hl7.org/fhir/ValueSet/daf-problem at Condition.code
InformationStructureDefinition.shortValues for short differ: 'complaint | symptom | finding | diagnosis' vs 'category codes'
WarningCondition.categoryElements differ in definition for mustSupport: 'false' vs 'true'
InformationCondition.categoryElement maximum cardinalities differ: '1' vs '2147483647'
InformationStructureDefinition.shortValues for short differ: 'active | relapse | remission | resolved' vs 'active | recurrence | relapse | inactive | remission | resolved'
InformationStructureDefinition.shortValues for short differ: 'provisional | differential | confirmed | refuted | entered-in-error | unknown' vs 'unconfirmed | provisional | differential | confirmed | refuted | entered-in-error'
InformationCondition.verificationStatusElement minimum cardinalities differ: '1' vs '0'
WarningCondition.onset[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'If/when in resolution/remission' vs 'When in resolution/remission'
InformationStructureDefinition.commentValues for comment differ: 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid.' vs 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.'
WarningCondition.abatement[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationCondition.stageElement maximum cardinalities differ: '1' vs '2147483647'
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: 'Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed.' vs 'Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.'
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).'
InformationCondition.evidence.codeElement maximum cardinalities differ: '1' vs '2147483647'
InformationStructureDefinition.commentValues for comment differ: 'May be a summary code, or a reference to a very precise definition of the location, or both.' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Condition
      .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
      .descriptionThe US Core Condition Problems and Health Concerns Profile is based upon the core FHIR Condition Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 'Problems' and 'Health Concerns' requirements and SDOH 'Problems/Health Concerns' requirements. In version 5.0.0, The US Core Condition Profile has been split into the US Core Condition Encounter Diagnosis Profile and US Core Condition Problems and Health Concerns Profile. To promote interoperability and adoption through common implementation, this profile defines constraints and extensions on the Condition resource for the minimal set of data to record, search, and fetch information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented and categorized as a problem or health concern including information about a Social Determinants of Health-related condition. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when and constrains the way the elements are used using this profile. It provides the floor for standards development for specific use cases.
      • Added the item 'The US Core Condition Problems and Health Concerns Profile is based upon the core FHIR Condition Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 'Problems' and 'Health Concerns' requirements and SDOH 'Problems/Health Concerns' requirements. In version 5.0.0, The US Core Condition Profile has been split into the US Core Condition Encounter Diagnosis Profile and US Core Condition Problems and Health Concerns Profile. To promote interoperability and adoption through common implementation, this profile defines constraints and extensions on the Condition resource for the minimal set of data to record, search, and fetch information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented and categorized as a problem or health concern including information about a Social Determinants of Health-related condition. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when and constrains the way the elements are used using this 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 Condition ProfileUSCoreConditionProblemsHealthConcernsProfile
          • Values Differ
          .publisherArgonaut ProjectHL7 International / Cross-Group Projects
          • Values Differ
          .purpose
            .statusdraftactive
            • Values Differ
            .titleUS Core Condition Problems and Health Concerns Profile
            • Added the item 'US Core Condition Problems and Health Concerns Profile'
            .typeCondition
              .urlhttp://fhir.org/guides/argonaut/StructureDefinition/argo-conditionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns
              • 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
              .. Condition C0..*ConditionArgonaut Condition Profile
              arg-1: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error. Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
              C0..*ConditionDetailed information about conditions, problems or diagnoses
              con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item
              con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission
              con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
                ... 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 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..*ExtensionExtension
                            Slice: Unordered, Open by value:url
                              ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                              ?!0..*ExtensionExtensions that cannot be ignored
                                ... identifier Σ0..*IdentifierExternal Ids for this condition
                                Σ0..*IdentifierExternal Ids for this condition
                                  ... patient S1..1Reference(Argonaut Patient Profile)Who has the condition?
                                  • Removed this element
                                  ... encounter Σ0..1Reference(Encounter)Encounter when condition first assertedΣ0..1Reference(Encounter)Encounter created as part of
                                    ... asserter Σ0..1Reference(Practitioner | Patient)Person who asserts this conditionΣ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Person who asserts this condition
                                      ... dateRecorded Σ0..1dateWhen first entered
                                      • Removed this element
                                      ... code S1..1CodeableConceptIdentification of the condition, problem or diagnosis
                                      Binding: ?? (extensible): Valueset to describe the actual problem experienced by the patient

                                      SΣ1..1CodeableConceptIdentification of the condition, problem or diagnosis
                                      Binding: ?? (extensible): Valueset to describe the actual problem experienced by the patient

                                      • Unable to resolve left value set http://hl7.org/fhir/ValueSet/daf-problem at Condition.code
                                      ... category 1..1CodeableConceptcomplaint | symptom | finding | diagnosis
                                      Binding: ?? (preferred): Extended category code valueset to support the intent of the separate concepts of problems and health concerns

                                      S1..*CodeableConceptcategory codes
                                      Slice: Unordered, Open by pattern:$this
                                      Binding: ?? (extensible): A category assigned to the condition.


                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      • Element maximum cardinalities differ: '1' vs '2147483647'
                                      ... clinicalStatus ?!S0..1codeactive | relapse | remission | resolved
                                      Binding: ?? (required)
                                      ?!SΣC0..1CodeableConceptactive | recurrence | relapse | inactive | remission | resolved
                                      Binding: ?? (required)
                                        ... verificationStatus ?!S1..1codeprovisional | differential | confirmed | refuted | entered-in-error | unknown
                                        Binding: ?? (required)
                                        ?!SΣC0..1CodeableConceptunconfirmed | provisional | differential | confirmed | refuted | entered-in-error
                                        Binding: ?? (required)
                                        • Element minimum cardinalities differ: '1' vs '0'
                                        ... severity Σ0..1CodeableConceptSubjective severity of condition
                                        Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.

                                        0..1CodeableConceptSubjective severity of condition
                                        Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.

                                          ... onset[x] Σ0..1dateTime, Quantity, Period, Range, stringEstimated or actual date, date-time, or ageSΣ0..1dateTime S, Age, Period, Range, stringEstimated or actual date, date-time, or age
                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                          ... abatement[x] Σ0..1dateTime, Quantity, boolean, Period, Range, stringIf/when in resolution/remissionSC0..1dateTime S, Age, Period, Range, stringWhen in resolution/remission
                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                          ... stage ΣC0..1BackboneElementStage/grade, usually assessed formally
                                          con-1: Stage SHALL have summary or assessment
                                          C0..*BackboneElementStage/grade, usually assessed formally
                                          con-1: Stage SHALL have summary or assessment
                                          • Element maximum cardinalities differ: '1' vs '2147483647'
                                          .... 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
                                                .... summary ΣC0..1CodeableConceptSimple summary (disease specific)
                                                Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).

                                                C0..1CodeableConceptSimple summary (disease specific)
                                                Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).

                                                  .... assessment ΣC0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
                                                  C0..*Reference(ClinicalImpression | DiagnosticReport | Observation)Formal record of assessment
                                                    .... type 0..1CodeableConceptKind of staging
                                                    Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological).

                                                    • Added this element
                                                    ... evidence ΣC0..*BackboneElementSupporting evidence
                                                    con-2: evidence SHALL have code or details
                                                    C0..*BackboneElementSupporting evidence
                                                    con-2: evidence SHALL have code or details
                                                      .... 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
                                                            .... code ΣC0..1CodeableConceptManifestation/symptom
                                                            Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.

                                                            ΣC0..*CodeableConceptManifestation/symptom
                                                            Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.


                                                            • Element maximum cardinalities differ: '1' vs '2147483647'
                                                            .... detail ΣC0..*Reference(Resource)Supporting information found elsewhere
                                                            ΣC0..*Reference(Resource)Supporting information found elsewhere
                                                              ... bodySite Σ0..*CodeableConceptAnatomical location, if relevant
                                                              Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                              Σ0..*CodeableConceptAnatomical location, if relevant
                                                              Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                ... notes Σ0..1stringAdditional information about the Condition
                                                                • Removed this element
                                                                ... subject SΣ1..1Reference(US Core Patient Profile S | Group)Who has the condition?
                                                                • Added this element
                                                                ... recordedDate SΣ0..1dateTimeDate record was first recorded
                                                                • Added this element
                                                                ... recorder Σ0..1Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)Who recorded the condition
                                                                • Added this element
                                                                ... note 0..*AnnotationAdditional information about the Condition
                                                                • Added this element

                                                                doco Documentation for this format