2.7. Condition

⚠️ This is a template for describing your Profile (StructureDefinition) resource. To start, update the canonical URL above to the one of your resource. Don't forget to remove this paragraph.

2.7.1. Metadata

These are the details for this resource:

Name	Canonical_URL	Status
Condition	http://nhc.gov.cn/fhir/StructureDefinition/ChineseConditionProfile	active

2.7.2. Resource content

These are different views on this resource:

This is the tree view:

Condition	I		Condition	There are no (further) constraints on this element Element id Condition Short description Detailed information about conditions, problems or diagnoses Definition A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. Data type Condition Constraints con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item `clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()` con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission `abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()` con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error `verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()` dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `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()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() Mappings rim: Entity. Role, or Act workflow: Event sct-concept: < 243796009 \|Situation with explicit context\| : 246090004 \|Associated finding\| = ( ( < 404684003 \|Clinical finding\| MINUS ( << 420134006 \|Propensity to adverse reactions\| OR << 473010000 \|Hypersensitivity condition\| OR << 79899007 \|Drug interaction\| OR << 69449002 \|Drug action\| OR << 441742003 \|Evaluation finding\| OR << 307824009 \|Administrative status\| OR << 385356007 \|Tumor stage finding\|)) OR < 272379006 \|Event\|) v2: PPR message rim: Observation[classCode=OBS, moodCode=EVN, code=ASSERTION, value<Diagnosis]
id	Σ	0..1	string	There are no (further) constraints on this element Element id Condition.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id Condition.meta Short description Metadata about the resource Definition 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. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id Condition.implicitRules Short description A set of rules under which this content was created Definition 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. Comments 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. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
language		0..1	codeBinding	There are no (further) constraints on this element Element id Condition.language Short description Language of the resource content Definition The base language in which the resource is written. Comments 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). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
text		0..1	Narrative	There are no (further) constraints on this element Element id Condition.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition 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. Comments 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. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id Condition.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition 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. Comments 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. Data type Resource Mappings rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Condition.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id Condition.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition 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). Requirements 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id Condition.identifier Short description External Ids for this condition Definition 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. Requirements Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers. Comments This is a business identifier, not a resource identifier (see discussion). 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. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.identifier w5: FiveWs.identifier rim: .id
clinicalStatus	Σ ?! I	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Condition.clinicalStatus Short description active \| recurrence \| relapse \| inactive \| remission \| resolved Definition The clinical status of the condition. Comments 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. Data type CodeableConcept Binding The clinical status of the condition or diagnosis. ConditionClinicalStatusCodes (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.status w5: FiveWs.status sct-concept: < 303105007 \|Disease phases\| v2: PRB-14 rim: Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="clinicalStatus", moodCode=EVN].value
verificationStatus	Σ ?! I	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Condition.verificationStatus Short description unconfirmed \| provisional \| differential \| confirmed \| refuted \| entered-in-error Definition The verification status to support the clinical status of the condition. Comments 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. Data type CodeableConcept Binding The verification status to support or decline the clinical status of the condition or diagnosis. ConditionVerificationStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.status w5: FiveWs.status sct-concept: < 410514004 \|Finding context value\| v2: PRB-13 rim: Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="verificationStatus", moodCode=EVN].value sct-attr: 408729009
category		0..*	CodeableConceptBinding	There are no (further) constraints on this element Element id Condition.category Short description problem-list-item \| encounter-diagnosis Definition A category assigned to the condition. Comments The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. Data type CodeableConcept Binding A category assigned to the condition. ConditionCategoryCodes (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.class sct-concept: < 404684003 \|Clinical finding\| v2: 'problem' if from PRB-3. 'diagnosis' if from DG1 segment in PV1 message rim: .code
severity		0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id Condition.severity Short description Subjective severity of condition Definition A subjective assessment of the severity of the condition as evaluated by the clinician. Comments Coding of the severity with a terminology is preferred, where possible. Data type CodeableConcept Binding A subjective assessment of the severity of the condition as evaluated by the clinician. Condition/DiagnosisSeverity (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.grade sct-concept: < 272141005 \|Severities\| v2: PRB-26 / ABS-3 rim: Can be pre/post-coordinated into value. Or ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="severity"].value sct-attr: 246112005
code	Σ	0..1	CodeableConceptBinding	Element id Condition.code Short description Identification of the condition, problem or diagnosis Alternate names type Definition Identification of the condition, problem or diagnosis. Requirements 0..1 to account for primarily narrative only resources. Data type CodeableConcept Binding Identification of the condition or diagnosis. chinese-diagnosis-valueset (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.code w5: FiveWs.what[x] sct-concept: code 246090004 \|Associated finding\| (< 404684003 \|Clinical finding\| MINUS << 420134006 \|Propensity to adverse reactions\| MINUS << 473010000 \|Hypersensitivity condition\| MINUS << 79899007 \|Drug interaction\| MINUS << 69449002 \|Drug action\| MINUS << 441742003 \|Evaluation finding\| MINUS << 307824009 \|Administrative status\| MINUS << 385356007 \|Tumor stage finding\|) OR < 413350009 \|Finding with explicit context\| OR < 272379006 \|Event\| v2: PRB-3 rim: .value sct-attr: 246090004
bodySite	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id Condition.bodySite Short description Anatomical location, if relevant Definition The anatomical location where this condition manifests itself. Comments 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. May be a summary code, or a reference to a very precise definition of the location, or both. Data type CodeableConcept Binding Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings sct-concept: < 442083009 \|Anatomical or acquired body structure\| rim: .targetBodySiteCode sct-attr: 363698007
subject	Σ	1..1	Reference(Patient \| Group)	There are no (further) constraints on this element Element id Condition.subject Short description Who has the condition? Alternate names patient Definition Indicates the patient or group who the condition record is associated with. Requirements Group is typically used for veterinary or public health use cases. Data type Reference(Patient \| Group) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.subject w5: FiveWs.subject[x] v2: PID-3 rim: .participation[typeCode=SBJ].role[classCode=PAT] w5: FiveWs.subject
encounter	Σ	0..1	Reference(Encounter)	There are no (further) constraints on this element Element id Condition.encounter Short description Encounter created as part of Definition The Encounter during which this Condition was created or to which the creation of this record is tightly associated. Comments 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". Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.context w5: FiveWs.context v2: PV1-19 (+PV1-54) rim: .inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
onset[x]	Σ	0..1		There are no (further) constraints on this element Element id Condition.onset[x] Short description Estimated or actual date, date-time, or age Definition Estimated or actual date or date-time the condition began, in the opinion of the clinician. Comments Age is generally used when the patient reports an age at which the Condition began to occur. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.occurrence[x] w5: FiveWs.init v2: PRB-16 rim: .effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value
onsetDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
onsetAge			Age	There are no (further) constraints on this element Data type Age
onsetPeriod			Period	There are no (further) constraints on this element Data type Period
onsetRange			Range	There are no (further) constraints on this element Data type Range
onsetString			string	There are no (further) constraints on this element Data type string
abatement[x]	I	0..1		There are no (further) constraints on this element Element id Condition.abatement[x] Short description When in resolution/remission Definition 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. Comments 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. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.done[x] rim: .effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed
abatementDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
abatementAge			Age	There are no (further) constraints on this element Data type Age
abatementPeriod			Period	There are no (further) constraints on this element Data type Period
abatementRange			Range	There are no (further) constraints on this element Data type Range
abatementString			string	There are no (further) constraints on this element Data type string
recordedDate	Σ	0..1	dateTime	There are no (further) constraints on this element Element id Condition.recordedDate Short description Date record was first recorded Definition The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.recorded v2: REL-11 rim: .participation[typeCode=AUT].time
recorder	Σ	0..1	Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson)	There are no (further) constraints on this element Element id Condition.recorder Short description Who recorded the condition Definition Individual who recorded the record and takes responsibility for its content. Data type Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.author rim: .participation[typeCode=AUT].role
asserter	Σ	0..1	Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson)	There are no (further) constraints on this element Element id Condition.asserter Short description Person who asserts this condition Definition Individual who is making the condition statement. Data type Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.source v2: REL-7.1 identifier + REL-7.12 type code rim: .participation[typeCode=INF].role
stage	I	0..*	BackboneElement	There are no (further) constraints on this element Element id Condition.stage Short description Stage/grade, usually assessed formally Definition Clinical stage or grade of a condition. May include formal severity assessments. Data type BackboneElement Constraints con-1: Stage SHALL have summary or assessment `summary.exists() or assessment.exists()` ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage/grade"]
id		0..1	string	There are no (further) constraints on this element Element id Condition.stage.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Condition.stage.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Condition.stage.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition 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). Requirements 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
summary	I	0..1	CodeableConcept	There are no (further) constraints on this element Element id Condition.stage.summary Short description Simple summary (disease specific) Definition A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. Data type CodeableConcept Binding Codes describing condition stages (e.g. Cancer stages). ConditionStage (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings sct-concept: < 254291000 \|Staging and scales\| v2: PRB-14 rim: .value
assessment	I	0..*	Reference(ClinicalImpression \| DiagnosticReport \| Observation)	There are no (further) constraints on this element Element id Condition.stage.assessment Short description Formal record of assessment Definition Reference to a formal record of the evidence on which the staging assessment is based. Data type Reference(ClinicalImpression \| DiagnosticReport \| Observation) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .self
type		0..1	CodeableConcept	There are no (further) constraints on this element Element id Condition.stage.type Short description Kind of staging Definition The kind of staging, such as pathological or clinical staging. Data type CodeableConcept Binding Codes describing the kind of condition staging (e.g. clinical or pathological). ConditionStageType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage type"]
evidence	I	0..*	BackboneElement	There are no (further) constraints on this element Element id Condition.evidence Short description Supporting evidence Definition Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition. Comments The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. Data type BackboneElement Constraints con-2: evidence SHALL have code or details `code.exists() or detail.exists()` ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: .outboundRelationship[typeCode=SPRT].target[classCode=OBS, moodCode=EVN]
id		0..1	string	There are no (further) constraints on this element Element id Condition.evidence.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Condition.evidence.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Condition.evidence.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition 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). Requirements 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: N/A
code	Σ I	0..*	CodeableConcept	There are no (further) constraints on this element Element id Condition.evidence.code Short description Manifestation/symptom Definition A manifestation or symptom that led to the recording of this condition. Data type CodeableConcept Binding Codes that describe the manifestation or symptoms of a condition. ManifestationAndSymptomCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.reasonCode w5: FiveWs.why[x] sct-concept: < 404684003 \|Clinical finding\| rim: [code="diagnosis"].value
detail	Σ I	0..*	Reference(Resource)	There are no (further) constraints on this element Element id Condition.evidence.detail Short description Supporting information found elsewhere Definition Links to other relevant information, including pathology reports. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings w5: FiveWs.why[x] rim: .self
note		0..*	Annotation	There are no (further) constraints on this element Element id Condition.note Short description Additional information about the Condition Definition Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. Data type Annotation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings workflow: Event.note v2: NTE child of PRB rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value

This is the detailed view:

Condition
Definition	A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
Cardinality	0...*
Invariants	con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item `clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()` con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission `abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()` con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error `verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()` dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `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()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` dom-6: A resource should have narrative for robust management text.`div`.exists()
Mappings	rim: Entity. Role, or Act workflow: Event sct-concept: < 243796009 \|Situation with explicit context\| : 246090004 \|Associated finding\| = ( ( < 404684003 \|Clinical finding\| MINUS ( << 420134006 \|Propensity to adverse reactions\| OR << 473010000 \|Hypersensitivity condition\| OR << 79899007 \|Drug interaction\| OR << 69449002 \|Drug action\| OR << 441742003 \|Evaluation finding\| OR << 307824009 \|Administrative status\| OR << 385356007 \|Tumor stage finding\|)) OR < 272379006 \|Event\|) v2: PPR message rim: Observation[classCode=OBS, moodCode=EVN, code=ASSERTION, value<Diagnosis]
Condition.id
Definition	The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Cardinality	0...1
Type	string
Summary	True
Comments	The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
Condition.meta
Definition	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.
Cardinality	0...1
Type	Meta
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Condition.implicitRules
Definition	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.
Cardinality	0...1
Type	uri
Modifier	True
Summary	True
Comments	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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Condition.language
Definition	The base language in which the resource is written.
Cardinality	0...1
Type	code
Binding	A human language. CommonLanguages (preferred)
Comments	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).
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Condition.text
Definition	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.
Cardinality	0...1
Type	Narrative
Alias	narrative, html, xhtml, display
Comments	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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: Act.text?
Condition.contained
Definition	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.
Cardinality	0...*
Type	Resource
Alias	inline resources, anonymous resources, contained resources
Comments	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.
Mappings	rim: N/A
Condition.extension
Definition	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.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: N/A
Condition.modifierExtension
Definition	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).
Cardinality	0...*
Type	Extension
Modifier	True
Alias	extensions, user content
Requirements	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.
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: N/A
Condition.identifier
Definition	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.
Cardinality	0...*
Type	Identifier
Summary	True
Requirements	Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.
Comments	This is a business identifier, not a resource identifier (see discussion). 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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.identifier w5: FiveWs.identifier rim: .id
Condition.clinicalStatus
Definition	The clinical status of the condition.
Cardinality	0...1
Type	CodeableConcept
Binding	The clinical status of the condition or diagnosis. ConditionClinicalStatusCodes (required)
Modifier	True
Summary	True
Comments	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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.status w5: FiveWs.status sct-concept: < 303105007 \|Disease phases\| v2: PRB-14 rim: Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="clinicalStatus", moodCode=EVN].value
Condition.verificationStatus
Definition	The verification status to support the clinical status of the condition.
Cardinality	0...1
Type	CodeableConcept
Binding	The verification status to support or decline the clinical status of the condition or diagnosis. ConditionVerificationStatus (required)
Modifier	True
Summary	True
Comments	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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.status w5: FiveWs.status sct-concept: < 410514004 \|Finding context value\| v2: PRB-13 rim: Observation ACT .inboundRelationship[typeCode=COMP].source[classCode=OBS, code="verificationStatus", moodCode=EVN].value sct-attr: 408729009
Condition.category
Definition	A category assigned to the condition.
Cardinality	0...*
Type	CodeableConcept
Binding	A category assigned to the condition. ConditionCategoryCodes (extensible)
Comments	The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.class sct-concept: < 404684003 \|Clinical finding\| v2: 'problem' if from PRB-3. 'diagnosis' if from DG1 segment in PV1 message rim: .code
Condition.severity
Definition	A subjective assessment of the severity of the condition as evaluated by the clinician.
Cardinality	0...1
Type	CodeableConcept
Binding	A subjective assessment of the severity of the condition as evaluated by the clinician. Condition/DiagnosisSeverity (preferred)
Comments	Coding of the severity with a terminology is preferred, where possible.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.grade sct-concept: < 272141005 \|Severities\| v2: PRB-26 / ABS-3 rim: Can be pre/post-coordinated into value. Or ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="severity"].value sct-attr: 246112005
Condition.code
Definition	Identification of the condition, problem or diagnosis.
Cardinality	0...1
Type	CodeableConcept
Binding	Identification of the condition or diagnosis. chinese-diagnosis-valueset (required)
Summary	True
Alias	type
Requirements	0..1 to account for primarily narrative only resources.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.code w5: FiveWs.what[x] sct-concept: code 246090004 \|Associated finding\| (< 404684003 \|Clinical finding\| MINUS << 420134006 \|Propensity to adverse reactions\| MINUS << 473010000 \|Hypersensitivity condition\| MINUS << 79899007 \|Drug interaction\| MINUS << 69449002 \|Drug action\| MINUS << 441742003 \|Evaluation finding\| MINUS << 307824009 \|Administrative status\| MINUS << 385356007 \|Tumor stage finding\|) OR < 413350009 \|Finding with explicit context\| OR < 272379006 \|Event\| v2: PRB-3 rim: .value sct-attr: 246090004
Condition.bodySite
Definition	The anatomical location where this condition manifests itself.
Cardinality	0...*
Type	CodeableConcept
Binding	Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (example)
Summary	True
Comments	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. May be a summary code, or a reference to a very precise definition of the location, or both.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	sct-concept: < 442083009 \|Anatomical or acquired body structure\| rim: .targetBodySiteCode sct-attr: 363698007
Condition.subject
Definition	Indicates the patient or group who the condition record is associated with.
Cardinality	1...1
Type	Reference(Patient \| Group)
Summary	True
Alias	patient
Requirements	Group is typically used for veterinary or public health use cases.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.subject w5: FiveWs.subject[x] v2: PID-3 rim: .participation[typeCode=SBJ].role[classCode=PAT] w5: FiveWs.subject
Condition.encounter
Definition	The Encounter during which this Condition was created or to which the creation of this record is tightly associated.
Cardinality	0...1
Type	Reference(Encounter)
Summary	True
Comments	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".
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.context w5: FiveWs.context v2: PV1-19 (+PV1-54) rim: .inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
Condition.onset[x]
Definition	Estimated or actual date or date-time the condition began, in the opinion of the clinician.
Cardinality	0...1
Type	dateTime
Summary	True
Comments	Age is generally used when the patient reports an age at which the Condition began to occur.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.occurrence[x] w5: FiveWs.init v2: PRB-16 rim: .effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value
Condition.abatement[x]
Definition	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.
Cardinality	0...1
Type	dateTime
Comments	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.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.done[x] rim: .effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed
Condition.recordedDate
Definition	The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.
Cardinality	0...1
Type	dateTime
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.recorded v2: REL-11 rim: .participation[typeCode=AUT].time
Condition.recorder
Definition	Individual who recorded the record and takes responsibility for its content.
Cardinality	0...1
Type	Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson)
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.author rim: .participation[typeCode=AUT].role
Condition.asserter
Definition	Individual who is making the condition statement.
Cardinality	0...1
Type	Reference(Practitioner \| PractitionerRole \| Patient \| RelatedPerson)
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.source v2: REL-7.1 identifier + REL-7.12 type code rim: .participation[typeCode=INF].role
Condition.stage
Definition	Clinical stage or grade of a condition. May include formal severity assessments.
Cardinality	0...*
Type	BackboneElement
Invariants	con-1: Stage SHALL have summary or assessment `summary.exists() or assessment.exists()` ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage/grade"]
Condition.stage.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
Condition.stage.extension
Definition	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.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a
Condition.stage.modifierExtension
Definition	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).
Cardinality	0...*
Type	Extension
Modifier	True
Summary	True
Alias	extensions, user content, modifiers
Requirements	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.
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: N/A
Condition.stage.summary
Definition	A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.
Cardinality	0...1
Type	CodeableConcept
Binding	Codes describing condition stages (e.g. Cancer stages). ConditionStage (example)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	sct-concept: < 254291000 \|Staging and scales\| v2: PRB-14 rim: .value
Condition.stage.assessment
Definition	Reference to a formal record of the evidence on which the staging assessment is based.
Cardinality	0...*
Type	Reference(ClinicalImpression \| DiagnosticReport \| Observation)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: .self
Condition.stage.type
Definition	The kind of staging, such as pathological or clinical staging.
Cardinality	0...1
Type	CodeableConcept
Binding	Codes describing the kind of condition staging (e.g. clinical or pathological). ConditionStageType (example)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage type"]
Condition.evidence
Definition	Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.
Cardinality	0...*
Type	BackboneElement
Comments	The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.
Invariants	con-2: evidence SHALL have code or details `code.exists() or detail.exists()` ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: .outboundRelationship[typeCode=SPRT].target[classCode=OBS, moodCode=EVN]
Condition.evidence.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
Condition.evidence.extension
Definition	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.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a
Condition.evidence.modifierExtension
Definition	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).
Cardinality	0...*
Type	Extension
Modifier	True
Summary	True
Alias	extensions, user content, modifiers
Requirements	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.
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: N/A
Condition.evidence.code
Definition	A manifestation or symptom that led to the recording of this condition.
Cardinality	0...*
Type	CodeableConcept
Binding	Codes that describe the manifestation or symptoms of a condition. ManifestationAndSymptomCodes (example)
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.reasonCode w5: FiveWs.why[x] sct-concept: < 404684003 \|Clinical finding\| rim: [code="diagnosis"].value
Condition.evidence.detail
Definition	Links to other relevant information, including pathology reports.
Cardinality	0...*
Type	Reference(Resource)
Summary	True
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	w5: FiveWs.why[x] rim: .self
Condition.note
Definition	Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.
Cardinality	0...*
Type	Annotation
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	workflow: Event.note v2: NTE child of PRB rim: .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value

This is the resource in XML:

<StructureDefinition xmlns="http://hl7.org/fhir">
    <id value="condition" />
    <url value="http://nhc.gov.cn/fhir/StructureDefinition/ChineseConditionProfile" />
    <name value="Condition" />
    <status value="active" />
    <kind value="resource" />
    <abstract value="false" />
    <type value="Condition" />
    <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Condition" />
    <differential>
        <element id="Condition.code">
            <path value="Condition.code" />
            <binding>
                <strength value="required" />
                <valueSet value="https://disease-code-cm.com/fhir/ValueSet/icd10cm-tcm-combo" />
            </binding>
        </element>
    </differential>
</StructureDefinition>

This is the resource in JSON:

{
    "resourceType": "StructureDefinition",
    "id": "condition",
    "url": "http://nhc.gov.cn/fhir/StructureDefinition/ChineseConditionProfile",
    "name": "Condition",
    "status": "active",
    "kind": "resource",
    "abstract": false,
    "type": "Condition",
    "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Condition",
    "differential": {
        "element":  [
            {
                "id": "Condition.code",
                "path": "Condition.code",
                "binding": {
                    "strength": "required",
                    "valueSet": "https://disease-code-cm.com/fhir/ValueSet/icd10cm-tcm-combo"
                }
            }
        ]
    }
}

Condition

2.7.3. Terminology Bindings

These are the terminology bindings within this resource:

Path	Conformance	ValueSet
Condition.code	required	https://disease-code-cm.com/fhir/ValueSet/icd10cm-tcm-combo

2.7.4. Constraints

These are the constraints (invariants) defined within this resource: