Condition resource implementation guidance

Condition: Implementation Guidance

Usage

The Condition resource will be used to carry the chief concern and any secondary concerns which reflect the outcome of triage.

Detailed implementation guidance for a Condition resource in the CDS context is given below:

Name Cardinality Type FHIR Documentation CDS Implementation Guidance
id 0..1 id Logical id of this artifact Note that this will always be populated except when the resource is being created (initial creation call)
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.
Common Languages (Extensible but limited to All Languages)
text 0..1 Narrative Text summary of the resource, for human interpretation
contained 0..* Resource Contained, inline Resources This SHOULD NOT be populated.
extension 0..* Extension Additional Content defined by implementations
modifierExtension 0..* Extension Extensions that cannot be ignored
identifier0..*IdentifierExternal Ids for this condition 
clinicalStatus0..1codeactive | recurrence | inactive | remission | resolved Condition Clinical Status Codes  (Required)This MUST be populated with 'active'. No other values are valid.
verificationStatus0..1codeprovisional | differential | confirmed | refuted | entered-in-error | unknownAll values are valid. In practice this is likely to be 'provisional' most of the time.
category0..*CodeableConceptproblem-list-item | encounter-diagnosis Condition Category Codes  (Example)This MUST be populated with the value 'concern' as per the ValueSet | UEC-ConditionCategory-1 (Required)
severity0..1CodeableConceptSubjective severity of condition Condition/Diagnosis Severity (Preferred)This SHOULD be populated where available.
code0..1CodeableConceptIdentification of the condition, problem or diagnosis Condition/Problem/Diagnosis Codes (Example)This MUST be populated with a relevant SNOMED code. Common Urgent and Emergency Care conditons can be found in the relevant custom ValueSet UEC Condition Code(Example).
bodySite0..*CodeableConceptAnatomical location, if relevant SNOMED CT Body Structures (Example)This SHOULD be populated where available.
subject1..1Reference(Patient | Group)Who has the condition?This MUST be the Patient.
context0..1Reference(Encounter | EpisodeOfCare)Encounter or episode when condition first assertedThis MUST be populated with the Encounter.
onset[x]0..1 Estimated or actual date, date-time, or ageThis MUST NOT be populated.
abatement[x]0..1 If/when in resolution/remissionThis MUST NOT be populated.
assertedDate0..1dateTimeDate record was believed accurateIf populated, SHOULD be the Date of triage result
asserter0..1Reference(Practitioner |  | Patient |  | RelatedPerson)Person who asserts this conditionThis MUST NOT be populated.
stage0..1BackboneElementStage/grade, usually assessed formally
+ Stage SHALL have summary or assessment
summary0..1CodeableConceptSimple summary (disease specific) Condition Stage (Example)This SHOULD be populated where available.
assessment0..*Reference(ClinicalImpression |  | DiagnosticReport  |  Observation)Formal record of assessmentThis SHOULD be populated where available.
evidence0..*BackboneElementSupporting evidence
+ evidence SHALL have code or details
code0..*CodeableConceptManifestation/symptom Manifestation and Symptom Codes  (Example)This MUST NOT be populated.
detail0..*Reference(Any)Supporting information found elsewhereThis MUST be populated with reference to the Observations or QuestionnaireResponses where available.
note0..*AnnotationAdditional information about the ConditionThis MUST NOT be populated.
Tags: rest fhir api