Profile Comparison between http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips vs http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-condition

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Condition
copyright		Used by permission of HL7 International all rights reserved Creative Commons License	Added the item 'Used by permission of HL7 International all rights reserved Creative Commons License'
date	2022-11-22T03:24:39+00:00	2022-08-02	Values Differ
description	This profile represents the constraints applied to the Condition resource by the International Patient Summary (IPS) FHIR Implementation Guide. A record of a problem is represented in the patient summary as an instance of the Condition resource constrained by this profile.	Minimum expectations for a Condition resource when accessed via an International Patient Access API. This profile communicates information about a patient's condition or diagnosis, such as recording primary and secondary diagnoses for encounters or justification for past medications. For the use of the condition resource to get a list of the patient's current problem list, use the [IPA-Problem-List-Item ](StructureDefinition-ipa-problem-list-item.html) profile instead. The difference between this profile and the IPA Problem List Item profile is that this profile does not specify or require a category.	Values Differ
experimental		false	Added the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	http://unstats.un.org/unsd/methods/m49/m49.htm#001
kind	resource
name	ConditionUvIps	IPACondition	Values Differ
publisher	Health Level Seven International - Patient Care Work Group	HL7 International - Patient Care Work Group	Values Differ
purpose	Representation of a problem in the international patient summary		Removed the item 'Representation of a problem in the international patient summary'
status	active
title	Condition (IPS)	IPA-Condition	Values Differ
type	Condition
url	http://hl7.org/fhir/uv/ips/StructureDefinition/Condition-uv-ips	http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-condition	Values Differ
version	1.1.0	1.0.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Condition	C	0..*	Condition	Documentation of a health problem of the patient	C	0..*	Condition	Detailed information about conditions, problems or diagnoses	Elements differ in short: 'Documentation of a health problem of the patient' vs 'Detailed information about conditions, problems or diagnoses'
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this condition	Σ	0..*	Identifier	External Ids for this condition
clinicalStatus	S	1..1	??	Concept - reference to a terminology or just text Binding: ?? (required): The clinical status of the condition or diagnosis.	?!SΣC	0..1	CodeableConcept	active | recurrence | relapse | inactive | remission | resolved Binding: ?? (required): The clinical status of the condition or diagnosis.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'active | recurrence | relapse | inactive | remission | resolved' Elements differ in definition: 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.' vs 'The clinical status of the condition.' Elements differ in comments: 'Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.' vs 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' Element minimum cardinalities differ: '1' vs '0'
verificationStatus		0..1	??	Concept - reference to a terminology or just text Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis.	?!SΣC	0..1	CodeableConcept	unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'unconfirmed | provisional | differential | confirmed | refuted | entered-in-error' Elements differ in definition: 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.' vs 'The verification status to support the clinical status of the condition.' Elements differ in comments: 'This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.' vs 'verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. The data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' Elements differ in definition for mustSupport: 'false' vs 'true'
category	S	0..*	??	Concept - reference to a terminology or just text Binding: ?? (preferred) Additional Bindings Purpose ?? candidate	S	0..*	CodeableConcept	problem-list-item | encounter-diagnosis Binding: ?? (extensible): A category assigned to the condition.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'problem-list-item | encounter-diagnosis' Elements differ in definition: 'A category assigned to the condition. In this profile, a health problem of the patient, therefore a 'problem-list-item'. ' vs 'A category assigned to the condition.' Elements differ in comments: 'In this profile, Condition represents a health problem of the patient. Therefore one of the category value(s) must be problem-list-item.' vs 'The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.'
severity	S	0..1	??	Concept - reference to a terminology or just text Binding: ?? (preferred) Additional Bindings Purpose ?? candidate		0..1	CodeableConcept	Subjective severity of condition Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'Subjective severity of condition' Elements differ in definition: 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.' vs 'A subjective assessment of the severity of the condition as evaluated by the clinician.' Elements differ in comments: 'Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.' vs 'Coding of the severity with a terminology is preferred, where possible.' Elements differ in definition for mustSupport: 'true' vs 'false'
code	S	1..1	??	Concept - reference to a terminology or just text Binding: ?? (preferred): Code for a clinical problem that is selected from SNOMED CT or a code for absent/unknown problem Additional Bindings Purpose ?? candidate ?? candidate	SΣ	1..1	CodeableConcept	Identification of the condition, problem or diagnosis Binding: ?? (example): Identification of the condition or diagnosis.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'Identification of the condition, problem or diagnosis' Elements differ in definition: 'Identification of the condition, problem or diagnosis or recording of "problem absent" or of "problems unknown".' vs 'Identification of the condition, problem or diagnosis.' Example/preferred bindings differ at Condition.code using binding from ConditionUvIps Elements differ in binding.description: 'Code for a clinical problem that is selected from SNOMED CT or a code for absent/unknown problem' vs 'Identification of the condition or diagnosis.'
bodySite		0..*	??	Concept - reference to a terminology or just text Binding: ?? (example)	Σ	0..*	CodeableConcept	Anatomical location, if relevant Binding: ?? (example): Codes describing anatomical locations. May include laterality.	Elements differ in short: 'Concept - reference to a terminology or just text' vs 'Anatomical location, if relevant' Elements differ in definition: 'A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.' vs 'The anatomical location where this condition manifests itself.' Elements differ in comments: 'Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite]. May be a summary code, or a reference to a very precise definition of the location, or both.'
subject	SΣ	1..1	Reference(Patient (IPS))	Who has the condition?	SΣ	1..1	Reference(IPA-Patient)	Who has the condition?
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	SΣC	1..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	Σ	0..1	Identifier	Logical reference, when literal reference is not known	Σ	0..1	Identifier	Logical reference, when literal reference is not known
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of	Σ	0..1	Reference(Encounter)	Encounter created as part of
onset[x]	SΣ	0..1	dateTime S, Age, Period, Range, string	Estimated or actual date, date-time, or age	Σ	0..1	dateTime, Age, Period, Range, string	Estimated or actual date, date-time, or age	Elements differ in definition for mustSupport: 'true' vs 'false'
abatement[x]	C	0..1	dateTime, Age, Period, Range, string	When in resolution/remission	C	0..1	dateTime, Age, Period, Range, string	When in resolution/remission
recordedDate	Σ	0..1	dateTime	Date record was first recorded	Σ	0..1	dateTime	Date record was first recorded
recorder	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Who recorded the condition	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Who recorded the condition
asserter	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Person who asserts this condition	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | RelatedPerson)	Person who asserts this condition
stage	C	0..*	BackboneElement	Stage/grade, usually assessed formally	C	0..*	BackboneElement	Stage/grade, usually assessed formally
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
summary	C	0..1	CodeableConcept	Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).	C	0..1	CodeableConcept	Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages).
assessment	C	0..*	Reference(ClinicalImpression | DiagnosticReport | Observation)	Formal record of assessment	C	0..*	Reference(ClinicalImpression | DiagnosticReport | Observation)	Formal record of assessment
type		0..1	CodeableConcept	Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological).		0..1	CodeableConcept	Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological).
evidence	C	0..*	BackboneElement	Supporting evidence	C	0..*	BackboneElement	Supporting evidence
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
code	ΣC	0..*	CodeableConcept	Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.	ΣC	0..*	CodeableConcept	Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition.
detail	ΣC	0..*	Reference(Resource)	Supporting information found elsewhere	ΣC	0..*	Reference(Resource)	Supporting information found elsewhere
note		0..*	Annotation	Additional information about the Condition		0..*	Annotation	Additional information about the Condition
Documentation for this format