Mandatory and Must Support Data Elements

The following data elements must always be present (in other words, mandatory resource properties where the minimum cardinality is 1) or must be supported (Must Support definition). Servers cannot restrict access to mandatory elements when authorizing an application. However, servers may choose to provide additional information or may be required to do so by national or other profiles that apply to the server's context.

Each Condition SHALL have:

• a code identifying the condition, problem, or diagnosis
• a patient
• at least a category code of "problem-list-item"

Applications must also support:

• a clinical status
• a verification status

Profile Specific Implementation Rules and Guidance

Retrieving the Current Problem List:

The current problem list is retrieved by specifying the patient, category and clinical-status:

GET [url]/Condition?patient=[patient-id]&category=problem-list-item&clinical-status=active

Condition Codes

All Condition resources are required to have a code, but the coding systems used around the world and even within jurisdictions very wildly. This specification does not fix any kind of value set that controls what kind of codes can be used - other national specifications etc will place their own restrictions on the codes.

Client Applications should be prepared to encounter codes they do not recognize and handle the records accordingly. Servers SHOULD populate Condition.code.coding.display and/or Condition.code.text so that clients can always at least display the condition even if they do not know the codes that are used.

Clients should be careful making use of the code search parameter given that the codes used vary so much.

Safety Issues

• Clients SHALL not treat all conditions as if they are part of the patient's current problem list
  • Note that some Condition resources may not have these status codes - this is usually due to poor record keeping reflected in legacy data
  • Servers SHOULD avoid leaving these status codes missing
• Clients SHALL pay attention to the clinicalStatus and verificationStatus and display and process them correctly
• Clients SHALL still work safely when the server does not support all the search parameters listed in the IPA Server Capability Statement. (see also Search advice)

• Differential Table
• Key Elements Table
• Snapshot Table
• Statistics/References
• All

This structure is derived from Condition

Name	Flags	Card.	Type	Description & Constraints
Condition		0..*	Condition	Detailed information about conditions, problems or diagnoses
clinicalStatus	SO	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	SO	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
code	SO	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
subject	SO	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints
Condition	C	0..*	Condition	Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
clinicalStatus	?!SOΣC	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Binding: ConditionClinicalStatusCodes (required): The clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	?!SOΣC	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ConditionVerificationStatus (required): The verification status to support or decline the clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
code	SOΣ	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Binding: Condition/Problem/DiagnosisCodes (example): Identification of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
subject	SOΣ	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Condition.clinicalStatus	required	ConditionClinicalStatusCodes http://hl7.org/fhir/ValueSet/condition-clinical|4.0.1 from the FHIR Standard
Condition.verificationStatus	required	ConditionVerificationStatus http://hl7.org/fhir/ValueSet/condition-ver-status|4.0.1 from the FHIR Standard
Condition.category	extensible	ConditionCategoryCodes http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.category:problem-list-item	extensible	Pattern: problem-list-item http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.code	example	Condition/Problem/DiagnosisCodes http://hl7.org/fhir/ValueSet/condition-code from the FHIR Standard

Name	Flags	Card.	Type	Description & Constraints
Condition	C	0..*	Condition	Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this condition
clinicalStatus	?!SOΣC	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Binding: ConditionClinicalStatusCodes (required): The clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	?!SOΣC	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ConditionVerificationStatus (required): The verification status to support or decline the clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
severity		0..1	CodeableConcept	Subjective severity of condition Binding: Condition/DiagnosisSeverity (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.
code	SOΣ	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Binding: Condition/Problem/DiagnosisCodes (example): Identification of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
bodySite	Σ	0..*	CodeableConcept	Anatomical location, if relevant Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
subject	SOΣ	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
onset[x]	Σ	0..1		Estimated or actual date, date-time, or age
onsetDateTime			dateTime
onsetAge			Age
onsetPeriod			Period
onsetRange			Range
onsetString			string
abatement[x]	C	0..1		When in resolution/remission
abatementDateTime			dateTime
abatementAge			Age
abatementPeriod			Period
abatementRange			Range
abatementString			string
recordedDate	Σ	0..1	dateTime	Date record was first recorded
recorder	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Who recorded the condition
asserter	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Person who asserts this condition
stage	C	0..*	BackboneElement	Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
summary	C	0..1	CodeableConcept	Simple summary (disease specific) Binding: ConditionStage (example): Codes describing condition stages (e.g. Cancer stages).
assessment	C	0..*	Reference(ClinicalImpression | DiagnosticReport | Observation)	Formal record of assessment
type		0..1	CodeableConcept	Kind of staging Binding: ConditionStageType (example): Codes describing the kind of condition staging (e.g. clinical or pathological).
evidence	C	0..*	BackboneElement	Supporting evidence con-2: evidence SHALL have code or details
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
code	ΣC	0..*	CodeableConcept	Manifestation/symptom Binding: ManifestationAndSymptomCodes (example): Codes that describe the manifestation or symptoms of a condition.
detail	ΣC	0..*	Reference(Resource)	Supporting information found elsewhere
note		0..*	Annotation	Additional information about the Condition
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Condition.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
Condition.clinicalStatus	required	ConditionClinicalStatusCodes http://hl7.org/fhir/ValueSet/condition-clinical|4.0.1 from the FHIR Standard
Condition.verificationStatus	required	ConditionVerificationStatus http://hl7.org/fhir/ValueSet/condition-ver-status|4.0.1 from the FHIR Standard
Condition.category	extensible	ConditionCategoryCodes http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.category:problem-list-item	extensible	Pattern: problem-list-item http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.severity	preferred	Condition/DiagnosisSeverity http://hl7.org/fhir/ValueSet/condition-severity from the FHIR Standard
Condition.code	example	Condition/Problem/DiagnosisCodes http://hl7.org/fhir/ValueSet/condition-code from the FHIR Standard
Condition.bodySite	example	SNOMEDCTBodyStructures http://hl7.org/fhir/ValueSet/body-site from the FHIR Standard
Condition.stage.summary	example	ConditionStage http://hl7.org/fhir/ValueSet/condition-stage from the FHIR Standard
Condition.stage.type	example	ConditionStageType http://hl7.org/fhir/ValueSet/condition-stage-type from the FHIR Standard
Condition.evidence.code	example	ManifestationAndSymptomCodes http://hl7.org/fhir/ValueSet/manifestation-or-symptom from the FHIR Standard

Differential View

This structure is derived from Condition

Name	Flags	Card.	Type	Description & Constraints
Condition		0..*	Condition	Detailed information about conditions, problems or diagnoses
clinicalStatus	SO	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	SO	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
code	SO	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
subject	SO	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
Documentation for this format

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
Condition	C	0..*	Condition	Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
clinicalStatus	?!SOΣC	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Binding: ConditionClinicalStatusCodes (required): The clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	?!SOΣC	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ConditionVerificationStatus (required): The verification status to support or decline the clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
code	SOΣ	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Binding: Condition/Problem/DiagnosisCodes (example): Identification of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
subject	SOΣ	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Condition.clinicalStatus	required	ConditionClinicalStatusCodes http://hl7.org/fhir/ValueSet/condition-clinical|4.0.1 from the FHIR Standard
Condition.verificationStatus	required	ConditionVerificationStatus http://hl7.org/fhir/ValueSet/condition-ver-status|4.0.1 from the FHIR Standard
Condition.category	extensible	ConditionCategoryCodes http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.category:problem-list-item	extensible	Pattern: problem-list-item http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.code	example	Condition/Problem/DiagnosisCodes http://hl7.org/fhir/ValueSet/condition-code from the FHIR Standard

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Condition	C	0..*	Condition	Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this condition
clinicalStatus	?!SOΣC	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Binding: ConditionClinicalStatusCodes (required): The clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
verificationStatus	?!SOΣC	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ConditionVerificationStatus (required): The verification status to support or decline the clinical status of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
Slices for category	SO	1..*	CodeableConcept	problem-list-item | encounter-diagnosis Slice: Unordered, Open by pattern:$this Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Obligations Actor SHALL:populate-if-known Server
category:problem-list-item	SO	1..1	CodeableConcept	problem-list-item | encounter-diagnosis Binding: ConditionCategoryCodes (extensible): A category assigned to the condition. Required Pattern: At least the following Obligations Actor SHALL:populate-if-known Server
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/condition-category
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: problem-list-item
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
severity		0..1	CodeableConcept	Subjective severity of condition Binding: Condition/DiagnosisSeverity (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.
code	SOΣ	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Binding: Condition/Problem/DiagnosisCodes (example): Identification of the condition or diagnosis. Obligations Actor SHALL:populate-if-known Server SHALL:handle Client
bodySite	Σ	0..*	CodeableConcept	Anatomical location, if relevant Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
subject	SOΣ	1..1	Reference(IPA-Patient)	Who has the condition? Obligations Actor SHALL:populate-if-known Server
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
onset[x]	Σ	0..1		Estimated or actual date, date-time, or age
onsetDateTime			dateTime
onsetAge			Age
onsetPeriod			Period
onsetRange			Range
onsetString			string
abatement[x]	C	0..1		When in resolution/remission
abatementDateTime			dateTime
abatementAge			Age
abatementPeriod			Period
abatementRange			Range
abatementString			string
recordedDate	Σ	0..1	dateTime	Date record was first recorded
recorder	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Who recorded the condition
asserter	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Person who asserts this condition
stage	C	0..*	BackboneElement	Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
summary	C	0..1	CodeableConcept	Simple summary (disease specific) Binding: ConditionStage (example): Codes describing condition stages (e.g. Cancer stages).
assessment	C	0..*	Reference(ClinicalImpression | DiagnosticReport | Observation)	Formal record of assessment
type		0..1	CodeableConcept	Kind of staging Binding: ConditionStageType (example): Codes describing the kind of condition staging (e.g. clinical or pathological).
evidence	C	0..*	BackboneElement	Supporting evidence con-2: evidence SHALL have code or details
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
code	ΣC	0..*	CodeableConcept	Manifestation/symptom Binding: ManifestationAndSymptomCodes (example): Codes that describe the manifestation or symptoms of a condition.
detail	ΣC	0..*	Reference(Resource)	Supporting information found elsewhere
note		0..*	Annotation	Additional information about the Condition
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Condition.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding http://hl7.org/fhir/ValueSet/languages from the FHIR Standard
Condition.clinicalStatus	required	ConditionClinicalStatusCodes http://hl7.org/fhir/ValueSet/condition-clinical|4.0.1 from the FHIR Standard
Condition.verificationStatus	required	ConditionVerificationStatus http://hl7.org/fhir/ValueSet/condition-ver-status|4.0.1 from the FHIR Standard
Condition.category	extensible	ConditionCategoryCodes http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.category:problem-list-item	extensible	Pattern: problem-list-item http://hl7.org/fhir/ValueSet/condition-category from the FHIR Standard
Condition.severity	preferred	Condition/DiagnosisSeverity http://hl7.org/fhir/ValueSet/condition-severity from the FHIR Standard
Condition.code	example	Condition/Problem/DiagnosisCodes http://hl7.org/fhir/ValueSet/condition-code from the FHIR Standard
Condition.bodySite	example	SNOMEDCTBodyStructures http://hl7.org/fhir/ValueSet/body-site from the FHIR Standard
Condition.stage.summary	example	ConditionStage http://hl7.org/fhir/ValueSet/condition-stage from the FHIR Standard
Condition.stage.type	example	ConditionStageType http://hl7.org/fhir/ValueSet/condition-stage-type from the FHIR Standard
Condition.evidence.code	example	ManifestationAndSymptomCodes http://hl7.org/fhir/ValueSet/manifestation-or-symptom from the FHIR Standard

This structure is derived from Condition

Summary

Mandatory: 3 elements
Must-Support: 6 elements

Structures

This structure refers to these other structures:

• IPA-Patient (http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-patient)

Slices

This structure defines the following Slices:

• The element 1 is sliced based on the value of Condition.category