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: DAFCondition

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/condition-daf-dafcondition

Defines constraints and extensions on the condition resource for use in querying and retrieving patient's information related to problems which includes conditions, findings, symptoms etc.

This profile was published on Thu, Aug 21, 2014 00:00+1000 as a draft by U.S. Office of the National Coordinator (ONC).

Formal Views of Profile Content

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

This structure is derived from Condition.

Summary

Terminology Bindings

  • Condition.code SHALL come from Valueset to describe the actual problem experienced by the patient (Extensible)
  • Condition.severity SHALL come from Valueset to identify the severity of the problem

Required/Prohibited Elements

  • The element Condition.patient is required
  • The element Condition.code is required
  • The element Condition.clinicalStatus is required
NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionThe occurrence of a condition.
... 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
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierExternal Ids for this condition
... patient S1..1patient-daf-dafpatientWho has the condition?
... encounter S0..1encounter-daf-dafencounterEncounter when condition first asserted
... asserter S0..1pract-daf-dafpract, patient-daf-dafpatientPerson 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 S0..1CodeableConceptmild | moderate | severe | fatal
Binding: DAFProblemSeverity (required)
... onsetDateTime S0..1dateTimeEstimated or actual date, date-time, or age
... abatementBoolean S0..1booleanConstrained to Boolean.
... stage 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 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 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 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, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship 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, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... notes S0..1stringAdditional information about the Condition

todo

This structure is derived from Condition.

Summary

Terminology Bindings

  • Condition.code SHALL come from Valueset to describe the actual problem experienced by the patient (Extensible)
  • Condition.severity SHALL come from Valueset to identify the severity of the problem

Required/Prohibited Elements

  • The element Condition.patient is required
  • The element Condition.code is required
  • The element Condition.clinicalStatus is required

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionThe occurrence of a condition.
... 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
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierExternal Ids for this condition
... patient S1..1patient-daf-dafpatientWho has the condition?
... encounter S0..1encounter-daf-dafencounterEncounter when condition first asserted
... asserter S0..1pract-daf-dafpract, patient-daf-dafpatientPerson 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 S0..1CodeableConceptmild | moderate | severe | fatal
Binding: DAFProblemSeverity (required)
... onsetDateTime S0..1dateTimeEstimated or actual date, date-time, or age
... abatementBoolean S0..1booleanConstrained to Boolean.
... stage 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 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 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 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, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship 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, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... notes S0..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.severityDAFProblemSeverityrequiredCondition/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)
.