## Profile Comparison between http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips vs http://hl7.eu/fhir/base-r5/StructureDefinition/condition-eu-core

Left: | Condition (IPS) (http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips)
Right: | Condition (EU core) (http://hl7.eu/fhir/base-r5/StructureDefinition/condition-eu-core)

### Messages

Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips' vs 'http://hl7.eu/fhir/base-r5/StructureDefinition/condition-eu-core'
Information | StructureDefinition.name | Values for name differ: 'ConditionUvIps' vs 'ConditionEuCore'
Information | StructureDefinition.title | Values for title differ: 'Condition (IPS)' vs 'Condition (EU core)'
Information | StructureDefinition.date | Values for date differ: '2024-06-19T10:50:07-05:00' vs '2026-04-27T22:41:19+03:00'
Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Patient Care' vs 'HL7 Europe'
Information | StructureDefinition.jurisdiction | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
Information | StructureDefinition.jurisdiction | Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150'
Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '5.0.0'
Information | StructureDefinition.short | Values for short differ: 'Documentation of a health problem of the patient' vs 'Detailed information about conditions, problems or diagnoses'
Information | StructureDefinition.comment | Values 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.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.'
Information | StructureDefinition.comment | Values 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. 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.' 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 its narrative along with other profiles, value sets, etc.'
Information | StructureDefinition.short | Values for short differ: 'Language of the resource content' vs 'Language of the condition content'
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'Human readable specification of the problem. This is a general notes/comments entry for description of the problem, its diagnosis and prognosis.'
Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'Contained resources do not have a 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.'
Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.'
Information | StructureDefinition.comment | Values 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' 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.'
Information | StructureDefinition.short | Values for short differ: 'Additional content defined by implementations' vs 'Extension'
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'An Extension'
Information | StructureDefinition.definition | Values 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 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).' 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 managable, 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).'
Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).'
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'Globally unique identifier of this problem which remain constant as the resource is updated and propagates from server to server.'
Information | StructureDefinition.comment | Values for comment differ: 'This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.' vs 'This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R5/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.'
Information | StructureDefinition.short | Values for short differ: 'active | recurrence | relapse | inactive | remission | resolved' vs 'active | recurrence | relapse | inactive | remission | resolved | unknown'
Information | StructureDefinition.definition | Values for definition differ: 'The clinical status of the condition.' vs 'The problem status describes the condition of the problem: 1. Active problems are problems of which the patient experiences symptoms or for which evidence exists. 2. If condition is abated, then clinicalStatus must be either inactive, resolved, or remission. 3. Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore.'
Information | StructureDefinition.comment | Values for comment differ: 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' vs 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown'
Warning | Condition.clinicalStatus | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | Condition.clinicalStatus | Element minimum cardinalities differ: '0' vs '1'
Information | StructureDefinition.comment | Values for comment differ: 'This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.' vs 'verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.'
Information | StructureDefinition.short | Values for short differ: 'problem-list-item | encounter-diagnosis' vs 'Category'
Information | StructureDefinition.definition | Values for definition differ: 'A category assigned to the condition. In this profile, a health problem of the patient, therefore a 'problem-list-item'. ' vs 'A category assigned to the condition.'
Information | StructureDefinition.comment | Values for comment differ: 'In this profile, Condition represents a health problem of the patient. Therefore one of the category value(s) must be problem-list-item.' vs 'The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.'
Warning | Condition.category | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Condition.severity | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | StructureDefinition.definition | Values for definition differ: 'Identification of the condition, problem or diagnosis or recording of absent/unknown problems.' vs 'Identification of the condition, problem or diagnosis.'
Warning | Condition.code | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodyStructure resource (e.g. to identify and track separately) then use the standard extension [http://hl7.org/fhir/StructureDefinition/bodySite](http://hl7.org/fhir/extensions/StructureDefinition-bodySite.html). May be a summary code, or a reference to a very precise definition of the location, or both.'
Warning | Condition.subject | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | StructureDefinition.short | Values for short differ: 'Encounter created as part of' vs 'The Encounter during which this Condition was created'
Information | StructureDefinition.comment | Values for comment differ: 'Age is generally used when the patient reports an age at which the Condition began to occur.' vs 'Age is generally used when the patient reports an age at which the Condition began to occur. Period is generally used to convey an imprecise onset that occurred within the time period. For example, Period is not intended to convey the transition period before the chronic bronchitis or COPD condition was diagnosed, but Period can be used to convey an imprecise diagnosis date. Range is generally used to convey an imprecise age range (e.g. 4 to 6 years old). Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe.'
Warning | Condition.onset[x] | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | StructureDefinition.definition | Values for definition differ: 'The date or estimated date that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution' - Conditions are never really resolved, but they can abate.' vs 'The date or estimated date that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution' - Some conditions, such as chronic conditions, are never really resolved, but they can abate.'
Information | StructureDefinition.comment | Values 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. When abatementString exists, it implies the condition is abated.' 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. Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe.'
Information | StructureDefinition.short | Values for short differ: 'Date record was first recorded' vs 'Date when the condition record was created'
Information | StructureDefinition.short | Values for short differ: 'Stage/grade, usually assessed formally' vs 'Stage/grade'
Information | StructureDefinition.definition | Values for definition differ: 'Clinical stage or grade of a condition. May include formal severity assessments.' vs 'A simple summary of the stage such as 'Stage 3' or 'Early Onset'. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer's, or Parkinson disease.'
Information | StructureDefinition.definition | Values for definition differ: '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.' 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 managable, 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.'
Information | StructureDefinition.definition | Values 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 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).' 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 managable, 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).'
Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).'
Information | StructureDefinition.short | Values for short differ: 'Simple summary (disease specific)' vs 'Most recent Stage Group'
Information | StructureDefinition.definition | Values for definition differ: 'A simple summary of the stage such as 'Stage 3'. The determination of the stage is disease-specific.' vs 'A simple summary of the stage such as 'Stage 3' or 'Early Onset'. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer's, or Parkinson disease.'
Information | StructureDefinition.definition | Values for definition differ: 'Reference to a formal record of the evidence on which the staging assessment is based.' vs 'Reference to the evidence on which the staging assessment is based.'
Information | StructureDefinition.short | Values for short differ: 'Kind of staging' vs 'Staging system used.'
Information | StructureDefinition.short | Values for short differ: 'Supporting evidence' vs 'Supporting evidence for the verification status'
Information | StructureDefinition.comment | Values for comment differ: 'The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.' vs 'If the condition was confirmed, but subsequently refuted, then the evidence can be cumulative including all evidence over time. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. For example, if the Condition.code is pneumonia, then there could be an evidence list where Condition.evidence.concept = fever (CodeableConcept), Condition.evidence.concept = cough (CodeableConcept), and Condition.evidence.reference = bronchitis (reference to Condition).'
Information | StructureDefinition.definition | Values for definition differ: 'Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.' vs 'Comment by the one who determined or updated the Problem.'

### Metadata

Name | Value | Comments
--- | --- | ---
abstract | false |
baseDefinition | http://hl7.org/fhir/StructureDefinition/Condition |
copyright |  | Copyright HL7 Europe. Licensed under creative commons public domain (CC0 1.0). | Added the item 'Copyright HL7 Europe. Licensed under creative commons public domain (CC0 1.0).'
date | 2024-06-19T10:50:07-05:00 | 2026-04-27T22:41:19+03:00 | Values Differ
description | This profile represents the constraints applied to the Condition resource by the International Patient Summary (IPS) FHIR Implementation Guide. A record of a problem is represented in the patient summary as an instance of the Condition resource constrained by this profile. | This profile introduces essential constraints and extensions for the Condition resource that apply across multiple use cases. | Values Differ
experimental |  |
fhirVersion | 4.0.1 | 5.0.0 | Values Differ
jurisdiction |  |
jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 |  | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
jurisdiction[1] |  | http://unstats.un.org/unsd/methods/m49/m49.htm#150 | Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150'
kind | resource |
name | ConditionUvIps | ConditionEuCore | Values Differ
publisher | HL7 International / Patient Care | HL7 Europe | Values Differ
purpose | Representation of a problem in the international patient summary |  | Removed the item 'Representation of a problem in the international patient summary'
status | active |
title | Condition (IPS) | Condition (EU core) | Values Differ
type | Condition |
url | http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips | http://hl7.eu/fhir/base-r5/StructureDefinition/condition-eu-core | Values Differ
version | 2.0.0 |

### Structure

Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Condition | C | 0..* | Condition | Documentation of a health problem of the patient | C | 0..* | Condition | Detailed information about conditions, problems or diagnoses |
id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
language |  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
|  | 0..1 | code | Language of the condition content Binding: ?? (required): IETF language tag for a human language
Additional Bindings | Purpose
?? | Starter
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements |
contained |  | 0..* | Resource | Contained, inline Resources |  | 0..* | Resource | Contained, inline Resources |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Extension Slice: Unordered, Open by value:url |
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored |
identifier | Σ | 0..* | Identifier | External Ids for this condition | Σ | 0..* | Identifier | External Ids for this condition |
clinicalStatus | ?!SO Σ C | 0..1 | ?? | active | recurrence | relapse | inactive | remission | resolved Binding: ?? (required): The clinical status of the condition or diagnosis.
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
| ?!Σ C | 1..1 | CodeableConcept | active | recurrence | relapse | inactive | remission | resolved | unknown Binding: ?? (required) | Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '0' vs '1'
verificationStatus | ?!Σ C | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis. | ?!Σ | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required) |
category | SO | 0..* | ?? | problem-list-item | encounter-diagnosis Binding: ?? (extensible)
Additional Bindings | Purpose
?? | candidate
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
| C | 0..* | CodeableConcept | Category Binding: ?? (preferred): A category assigned to the condition. | Elements differ in definition for mustSupport: 'true' vs 'false'
severity | SO | 0..1 | ?? | Subjective severity of condition Binding: ?? (preferred)
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
|  | 0..1 | CodeableConcept | Subjective severity of condition Binding: ?? (preferred) | Elements differ in definition for mustSupport: 'true' vs 'false'
code | SO Σ | 1..1 | ?? | Identification of the condition, problem or diagnosis Binding: ?? (preferred): Code for a clinical problem (or absent/unknown problem) that is selected from SNOMED CT
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
| Σ | 1..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: ?? (preferred)
Additional Bindings | Purpose
?? | Preferred
| Elements differ in definition for mustSupport: 'true' vs 'false'
bodySite | Σ | 0..* | CodeableConcept | Anatomical location, if relevant Binding: ?? (preferred) | Σ C | 0..* | CodeableConcept | Anatomical location, if relevant Binding: ?? (preferred) Constraints: eu-bodysite-1 |
id |  |  |  |  |  | 0..1 | id | Unique id for inter-element referencing | Added this element
Slices for extension |  |  |  |  |  | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | Added this element
coding |  |  |  |  | Σ | 0..* | Coding | Code defined by a terminology system | Added this element
text |  |  |  |  | Σ | 0..1 | string | Plain text representation of the concept | Added this element
subject | SO Σ | 1..1 | Reference(Patient (IPS)) | Who has the condition?
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
| Σ | 1..1 | Reference(Patient (EU core)) | Who has the condition? | Elements differ in definition for mustSupport: 'true' vs 'false'
id |  | 0..1 | string | Unique id for inter-element referencing |  |  |  |  | Removed this element
Slices for extension |  | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |  |  |  |  | Removed this element
reference | SO Σ C | 1..1 | string | Literal reference, Relative, internal or absolute URL
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
|  |  |  |  | Removed this element
type | Σ | 0..1 | uri | Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model). |  |  |  |  | Removed this element
identifier | Σ | 0..1 | Identifier | Logical reference, when literal reference is not known |  |  |  |  | Removed this element
display | Σ | 0..1 | string | Text alternative for the resource |  |  |  |  | Removed this element
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of | Σ | 0..1 | Reference(Encounter) | The Encounter during which this Condition was created |
Slices for onset[x] | SO Σ | 0..1 | dateTime, Age, Period, Range, string | Estimated or actual date, date-time, or age Slice: Unordered, Open by type:$this
Obligations | Actor
SHALL:populate-if-known | Creator (IPS)
SHALL:handle | Consumer (IPS)
SHOULD:display | Consumer (IPS)
| Σ | 0..1 | dateTime, Age, Period, Range, string | Estimated or actual date, date-time, or age Slice: Unordered, Open by type:$this | Elements differ in definition for mustSupport: 'true' vs 'false'
abatement[x] | C | 0..1 | dateTime, Age, Period, Range, string | When in resolution/remission | C | 0..1 | dateTime, Age, Period, Range, string | When in resolution/remission Slice: Unordered, Open by type:$this |
recordedDate | Σ | 0..1 | dateTime | Date record was first recorded | Σ | 0..1 | dateTime | Date when the condition record was created |
recorder | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Who recorded the condition |  |  |  |  | Removed this element
asserter | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Person who asserts this condition |  |  |  |  | Removed this element
stage | C | 0..* | BackboneElement | Stage/grade, usually assessed formally | C | 0..* | BackboneElement | Stage/grade |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
summary | C | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). | C | 0..1 | CodeableConcept | Most recent Stage Group Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). |
assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment |
type |  | 0..1 | CodeableConcept | Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). |  | 0..1 | CodeableConcept | Staging system used. Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). |
evidence | C | 0..* | BackboneElement | Supporting evidence | Σ | 0..* | CodeableReference(Resource) | Supporting evidence for the verification status Binding: ?? (example) |
id |  | 0..1 | string | Unique id for inter-element referencing |  |  |  |  | Removed this element
extension |  | 0..* | Extension | Additional content defined by implementations |  |  |  |  | Removed this element
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |  |  |  |  | Removed this element
code | Σ C | 0..* | CodeableConcept | Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition. |  |  |  |  | Removed this element
detail | Σ C | 0..* | Reference(Resource) | Supporting information found elsewhere |  |  |  |  | Removed this element
note |  | 0..* | Annotation | Additional information about the Condition |  | 0..* | Annotation | Additional information about the Condition |
participant |  |  |  |  | Σ | 0..* | BackboneElement | Who or what participated in the activities related to the condition and how they were involved | Added this element
Documentation for this format