This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

StructureDefinition: QICore-Condition

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/condition-qicore-qicore-condition

Profile of Condition for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.

This profile was published on Fri, Feb 27, 2015 00:00+1100 as a draft by Health Level Seven, Inc. - CQI WG.

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Condition.

unable to summarise extension (wrong count)

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionDetailed information about conditions, problems or diagnoses
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... condition-contributionToDeath 0..1CodeableConceptExtension
... condition-criticality 0..1CodeableConceptExtension
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal Ids for this condition
... patient S1..1patient-qicore-qicore-patientWho has the condition?
... encounter S0..1encounter-qicore-qicore-encounterEncounter when condition first asserted
... asserter 0..1patient-qicore-qicore-patient, practitioner-qicore-qicore-practitionerPerson who asserts this condition
... dateAsserted S0..1dateWhen first detected/suspected/entered
... code S1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: DAFProblemCode (extensible)
... category S0..1CodeableConceptE.g. complaint | symptom | finding | diagnosis
Binding: ConditionCategory (required)
... clinicalStatus ?! S1..1codeprovisional | working | confirmed | refuted | entered-in-error | unknown
Binding: ConditionClinicalStatus (required)
... severity 0..1CodeableConceptSubjective severity of condition
Binding: ConditionSeverity (example)
... onset[x] S0..1dateTime, Age, Period, Range, stringEstimated or actual date, date-time, or age
... abatement[x] S0..1date, Age, boolean, Period, Range, stringIf/when in resolution/remission
... stage S I0..1Stage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... summary S I0..1CodeableConceptSimple summary (disease specific)
.... assessment I0..*ResourceFormal record of assessment
... evidence I0..*Supporting evidence
con-2: evidence SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptManifestation/symptom
.... detail I0..*ResourceSupporting information found elsewhere
... location S I0..*Anatomical location, if relevant
con-3: location SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code S I0..1CodeableConceptLocation - may include laterality
.... detail I0..1stringPrecise location details
... dueTo I0..*Causes for this Condition
con-4: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1condition-qicore-qicore-condition, procedure-qicore-qicore-procedure, medicationadministration-qicore-qicore-medicationadministration, medicationstatement-qicore-qicore-medicationstatement, immunization-qicore-qicore-immunizationRelationship target resource
... occurredFollowing I0..*Precedent for this Condition
con-5: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1condition-qicore-qicore-condition, procedure-qicore-qicore-procedure, medicationadministration-qicore-qicore-medicationadministration, medicationstatement-qicore-qicore-medicationstatement, immunization-qicore-qicore-immunizationRelationship target resource
... notes 0..1stringAdditional information about the Condition

todo

This structure is derived from Condition.

unable to summarise extension (wrong count)

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionDetailed information about conditions, problems or diagnoses
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... condition-contributionToDeath 0..1CodeableConceptExtension
... condition-criticality 0..1CodeableConceptExtension
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal Ids for this condition
... patient S1..1patient-qicore-qicore-patientWho has the condition?
... encounter S0..1encounter-qicore-qicore-encounterEncounter when condition first asserted
... asserter 0..1patient-qicore-qicore-patient, practitioner-qicore-qicore-practitionerPerson who asserts this condition
... dateAsserted S0..1dateWhen first detected/suspected/entered
... code S1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: DAFProblemCode (extensible)
... category S0..1CodeableConceptE.g. complaint | symptom | finding | diagnosis
Binding: ConditionCategory (required)
... clinicalStatus ?! S1..1codeprovisional | working | confirmed | refuted | entered-in-error | unknown
Binding: ConditionClinicalStatus (required)
... severity 0..1CodeableConceptSubjective severity of condition
Binding: ConditionSeverity (example)
... onset[x] S0..1dateTime, Age, Period, Range, stringEstimated or actual date, date-time, or age
... abatement[x] S0..1date, Age, boolean, Period, Range, stringIf/when in resolution/remission
... stage S I0..1Stage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... summary S I0..1CodeableConceptSimple summary (disease specific)
.... assessment I0..*ResourceFormal record of assessment
... evidence I0..*Supporting evidence
con-2: evidence SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptManifestation/symptom
.... detail I0..*ResourceSupporting information found elsewhere
... location S I0..*Anatomical location, if relevant
con-3: location SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code S I0..1CodeableConceptLocation - may include laterality
.... detail I0..1stringPrecise location details
... dueTo I0..*Causes for this Condition
con-4: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1condition-qicore-qicore-condition, procedure-qicore-qicore-procedure, medicationadministration-qicore-qicore-medicationadministration, medicationstatement-qicore-qicore-medicationstatement, immunization-qicore-qicore-immunizationRelationship target resource
... occurredFollowing I0..*Precedent for this Condition
con-5: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1condition-qicore-qicore-condition, procedure-qicore-qicore-procedure, medicationadministration-qicore-qicore-medicationadministration, medicationstatement-qicore-qicore-medicationstatement, immunization-qicore-qicore-immunizationRelationship target resource
... notes 0..1stringAdditional information about the Condition

XML Template

JSON Template

todo

 

Other representations of profile: (todo)

Terminology Bindings

PathNameConformanceValueSet
Condition.languageLanguagerequiredhttp://tools.ietf.org/html/bcp47
Condition.codeDAFProblemCodeextensibleProblem Value Set
Condition.categoryConditionCategoryrequiredCondition/Problem/Diagnosis Codes
Condition.clinicalStatusConditionClinicalStatusrequiredConditionClinicalStatus
Condition.severityConditionSeverityexampleCondition/Diagnosis Severity
Condition.dueTo.codeConditionKindexampleCondition/Problem/Diagnosis Codes
Condition.occurredFollowing.codeConditionKindexampleCondition/Problem/Diagnosis Codes

Constraints

IdPathNameDetails
con-1Condition.stageStage ruleStage SHALL have summary or assessment
XPath: exists(f:summary) or exists(f:assessment)
con-2Condition.evidenceEvidenceevidence SHALL have code or details
XPath: exists(f:code) or exists(f:detail)
con-3Condition.locationLocationlocation SHALL have code or details
XPath: exists(f:code) or exists(f:detail)
con-4Condition.dueToRelationship1Relationship SHALL have either a code or a target
XPath: exists(f:code) != exists(f:target)
con-5Condition.occurredFollowingRelationship2Relationship SHALL have either a code or a target
XPath: exists(f:code) != exists(f:target)
.