DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . For a full list of available versions, see the Directory of published versions . Page versions: . Page versions: R5 R4B R4 R3 R2

4.3 9.2 Resource Condition - Content Resource Condition - Content

Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary.
Patient Care Patient Care Work Group Work Group Maturity Level : 2 Maturity Level : 2 Compartments : : Encounter , , Patient , , Practitioner

Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary.

4.3.1 Scope and Usage 9.2.1 Scope and Usage Used to record detailed information pertinent to a clinician's assessment and assertion of a particular aspect of a person's state of health. Examples of condition include problems, diagnoses, concerns, issues. There are many uses of condition which include: recording a problem, diagnosis, health concern or health issue during an encounter the use of such information to populate a problem list of a summary statement such as a discharge summary This resource is used to record detailed information about a clinician's assessment and assertion of a particular aspect of a patient's state of health. It is intended for use to record information about a disease/illness identified from application of clinical reasoning over the pathologic and pathophysiologic findings (diagnosis), or identification of health issues/situations that require ongoing monitoring and/or management (health issue/concern), or identification of health issues/situations considered harmful, potentially harmful and required to be investigated and managed (problems). The condition resource may also be used to record certain health state of a patient which does not normally present negative outcome (until complications are predicted or detected), e.g. pregnancy. Examples of complications of pregnancy include: hyperemesis gravidarum, preeclampsia, eclampsia - which are captured as problems/diagnoses.

Used to record detailed information pertinent to a clinician's assessment and assertion of a particular aspect of a person's state of health. Examples of condition include problems, diagnoses, concerns, issues. There are many uses of condition which include:

  • recording a problem, diagnosis, health concern or health issue during an encounter
  • the use of such information to populate a problem list of a summary statement such as a discharge summary

This resource is used to record detailed information about a clinician's assessment and assertion of a particular aspect of a patient's state of health. It is intended for use to record information about a disease/illness identified from application of clinical reasoning over the pathologic and pathophysiologic findings (diagnosis), or identification of health issues/situations that require ongoing monitoring and/or management (health issue/concern), or identification of health issues/situations considered harmful, potentially harmful and required to be investigated and managed (problems).

The condition resource may also be used to record certain health state of a patient which does not normally present negative outcome (until complications are predicted or detected), e.g. pregnancy. Examples of complications of pregnancy include: hyperemesis gravidarum, preeclampsia, eclampsia - which are captured as problems/diagnoses.

4.3.2 Boundaries and Relationships 9.2.2 Boundaries and Relationships The condition resource may be referenced by other resources as "reasons" for an action (e.g.

The condition resource may be referenced by other resources as "reasons" for an action (e.g. MedicationOrder , , Procedure , DiagnosticOrder , etc.) This resource is not to be used to record information about subjective and objective information that might lead to the recording of a Condition. Such signs and symptoms that are typically captured using the , DiagnosticRequest , etc.)

This resource is not to be used to record information about subjective and objective information that might lead to the recording of a Condition. Such signs and symptoms that are typically captured using the Observation resource; although in some cases a persistent symptom, e.g. fever, headache may be captured as a condition before a definitive diagnosis can be discerned by a clinician.

The condition resource also specifically excludes AllergyIntolerance as those are handled with their own resource.

STU Note: The Condition.category element is a CodeableConcept data type with a preferred (not required resource; although in some cases a persistent symptom, e.g. fever, headache may be captured as a condition before a definitive diagnosis can be discerned by a clinician. The condition resource also specifically excludes AllergyIntoelrance as those are handled with their own resource. This resource is referenced by ) binding to four category codes: complaint | symptom | finding | diagnosis from the FHIR-defined condition-category code system and value set. In GFORGE # 10091 , the conformance requirements for code vs. CodeableConcept (4a) note that a CodeableConcept should use a standard terminology such as SNOMED CT. The Patient Care WG has recommended that Condition.category be changed to a code data type with a required binding to the condition-category value set (containing the four codes: complaint | symptom | finding | diagnosis as noted above).

Feedback is sought particularly on these questions:

  1. Is CodeableConcept needed for Condition.category? If so, what are the concepts that could be used from SNOMED CT for this constrained value set? How would this impact searching by category?
  2. If Condition.category is changed to a code data type, is the use of the current four codes adequate for condition classification, or are additional codes needed? If so, what would these be? Note the recommendation to make this a required , not a preferred binding. Please comment on the impact of high level categories vs. more granular categories.

PLANNED CHANGE:

Communication is one of the Event resources in the FHIR Workflow specification. As such, it is expected to be adjusted to align with the Event workflow pattern which will involve adding a number of additional data elements and potentially renaming a few elements. Any concerns about performing such alignment are welcome as ballot comments and/or tracker items.

This resource is referenced by CarePlan , , ClinicalImpression , DiagnosticOrder , , Encounter , , EpisodeOfCare , , Goal , , MedicationOrder , , MedicationStatement , , Procedure , , ProcedureRequest , , RiskAssessment and and VisionPrescription

4.3.3 Resource Content 9.2.3 Resource Content

Structure

Encounter when condition first asserted
Name Flags Card. Type Description & Constraints Description & Constraints doco
. . Condition Σ DomainResource Detailed information about conditions, problems or diagnoses Detailed information about conditions, problems or diagnoses
. . . identifier Σ 0..* Identifier External Ids for this condition External Ids for this condition
. . patient . clinicalStatus Σ ?! Σ 1..1 Reference ( Patient ) 0..1 Who has the condition? encounter code active | relapse | remission | resolved
Σ 0..1 Reference ( Encounter Condition Clinical Status Codes ( Required )
. . asserter . verificationStatus ?! Σ 0..1 1..1 Reference ( Practitioner | Patient code ) Person who asserts this condition provisional | differential | confirmed | refuted | entered-in-error | unknown
ConditionVerificationStatus ( Required )
. . dateRecorded . category Σ 0..1 date CodeableConcept When first entered complaint | symptom | finding | diagnosis
Condition Category Codes ( Preferred )
. . code . severity Σ 1..1 0..1 CodeableConcept Identification of the condition, problem or diagnosis Subjective severity of condition
Condition/Problem/Diagnosis Codes ( Example Condition/Diagnosis Severity ( Preferred )
. . category . code Σ 0..1 1..1 CodeableConcept complaint | symptom | finding | diagnosis Identification of the condition, problem or diagnosis
Condition Category Codes ( Preferred Condition/Problem/Diagnosis Codes ( Example )
. . clinicalStatus . bodySite ?! Σ 0..1 0..* code CodeableConcept active | relapse | remission | resolved Anatomical location, if relevant
Condition Clinical Status Codes ( Preferred SNOMED CT Body Structures ( Example )
. . verificationStatus . subject ?! Σ 1..1 code provisional | differential | confirmed | refuted | entered-in-error | unknown ConditionVerificationStatus Reference ( Required Patient | Group ) Who has the condition?
. . severity . context Σ 0..1 CodeableConcept Subjective severity of condition Condition/Diagnosis Severity Reference ( Preferred Encounter | EpisodeOfCare ) Encounter when condition first asserted
. . . onset[x] Σ 0..1 Estimated or actual date, date-time, or age Estimated or actual date, date-time, or age
. . . . onsetDateTime dateTime
. . . . onsetAge onsetQuantity Age
. . . . onsetPeriod Period
. . . . onsetRange Range
. . . . onsetString string
. . . abatement[x] Σ 0..1 If/when in resolution/remission If/when in resolution/remission
. . . . abatementDateTime dateTime
. . . . abatementAge abatementQuantity Age
. . . . abatementBoolean boolean
. . . . abatementPeriod Period
. . . . abatementRange Range
. . . . abatementString string
. . . dateRecorded Σ 0..1 date When first entered
... asserter Σ 0..1 Reference ( Practitioner | Patient ) Person who asserts this condition
. . . stage Σ I 0..1 BackboneElement Stage/grade, usually assessed formally Stage/grade, usually assessed formally
Stage SHALL have summary or assessment Stage SHALL have summary or assessment
. . . . summary Σ I 0..1 CodeableConcept Simple summary (disease specific) Simple summary (disease specific)
Condition Stage ( Condition Stage ( Example )
. . . . assessment Σ I 0..* Reference ( ClinicalImpression | | DiagnosticReport | | Observation ) Formal record of assessment Formal record of assessment
. . . evidence Σ I 0..* BackboneElement Supporting evidence Supporting evidence
evidence SHALL have code or details evidence SHALL have code or details
. . . . code Σ I 0..1 CodeableConcept Manifestation/symptom
Manifestation and Symptom Codes ( Manifestation and Symptom Codes ( Example )
. . . . detail Σ I 0..* Reference ( Any ) Supporting information found elsewhere bodySite Σ 0..* CodeableConcept Anatomical location, if relevant SNOMED CT Body Structures ( Example ) Supporting information found elsewhere
. . notes . note Σ 0..1 0..* string Annotation Additional information about the Condition Additional information about the Condition

Documentation for this format doco Documentation for this format

UML Diagram UML Diagram ( Legend )

Condition ( ( DomainResource ) This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation) This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation) identifier : : Identifier [0..*] [0..*] Indicates the patient who the condition record is associated with The clinical status of the condition (this element modifies the meaning of other elements) patient : Reference [1..1] « Patient » clinicalStatus : code [0..1] « Encounter during which the condition was first asserted The clinical status of the condition or diagnosis. (Strength=Required) encounter : Reference [0..1] « Encounter » Condition Clinical Status ! » Individual who is making the condition statement The verification status to support the clinical status of the condition (this element modifies the meaning of other elements) asserter : Reference [0..1] « Practitioner | Patient » verificationStatus : code [1..1] « A date, when the Condition statement was documented The verification status to support or decline the clinical status of the condition or diagnosis. (Strength=Required) dateRecorded : date [0..1] ConditionVerificationStatus ! » Identification of the condition, problem or diagnosis A category assigned to the condition code : category : CodeableConcept [1..1] « [0..1] « Identification of the condition or diagnosis. (Strength=Example) A category assigned to the condition. (Strength=Preferred) Condition/Problem/Diagnosis ?? » Condition Category ? » A category assigned to the condition A subjective assessment of the severity of the condition as evaluated by the clinician category : severity : CodeableConcept [0..1] « [0..1] « A category assigned to the condition. (Strength=Preferred) A subjective assessment of the severity of the condition as evaluated by the clinician. (Strength=Preferred) Condition Category Condition/Diagnosis Severity ? » ? » The clinical status of the condition (this element modifies the meaning of other elements) Identification of the condition, problem or diagnosis clinicalStatus : code [0..1] « : CodeableConcept [1..1] « The clinical status of the condition or diagnosis. (Strength=Preferred) Identification of the condition or diagnosis. (Strength=Example) Condition Clinical Status ? » Condition/Problem/Diagnosis ?? » The verification status to support the clinical status of the condition (this element modifies the meaning of other elements) The anatomical location where this condition manifests itself verificationStatus : code [1..1] « bodySite : CodeableConcept [0..*] « The verification status to support or decline the clinical status of the condition or diagnosis. (Strength=Required) Codes describing anatomical locations. May include laterality. (Strength=Example) ConditionVerificationStatus ! » SNOMED CT Body Structures ?? » A subjective assessment of the severity of the condition as evaluated by the clinician Indicates the patient or group who the condition record is associated with severity : CodeableConcept subject : Reference [1..1] « Patient [0..1] « | Group » A subjective assessment of the severity of the condition as evaluated by the clinician. (Strength=Preferred) Encounter during which the condition was first asserted Condition/Diagnosis Severity context : Reference [0..1] « Encounter ? » | EpisodeOfCare » Estimated or actual date or date-time the condition began, in the opinion of the clinician Estimated or actual date or date-time the condition began, in the opinion of the clinician onset[x] : : Type [0..1] « [0..1] « dateTime | Quantity ( Age )| | Period | Range | string » » The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate abatement[x] : : Type [0..1] « [0..1] « dateTime | Quantity ( Age )| | boolean | Period | Range | string » » The anatomical location where this condition manifests itself A date, when the Condition statement was documented bodySite : CodeableConcept [0..*] « dateRecorded : date [0..1] Codes describing anatomical locations. May include laterality. (Strength=Example) Individual who is making the condition statement SNOMED CT Body Structures asserter : Reference [0..1] « Practitioner ?? » | Patient » Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis notes : string [0..1] note : Annotation [0..*] Stage A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific summary : : CodeableConcept [0..1] « [0..1] « Codes describing condition stages (e.g. Cancer stages). (Strength=Example) Codes describing condition stages (e.g. Cancer stages). (Strength=Example) Condition Stage Condition Stage ?? » ?? » Reference to a formal record of the evidence on which the staging assessment is based Reference to a formal record of the evidence on which the staging assessment is based assessment : : Reference [0..*] « [0..*] « ClinicalImpression | DiagnosticReport | Observation » » Evidence A manifestation or symptom that led to the recording of this condition A manifestation or symptom that led to the recording of this condition code : : CodeableConcept [0..1] « [0..1] « Codes that describe the manifestation or symptoms of a condition. (Strength=Example) Codes that describe the manifestation or symptoms of a condition. (Strength=Example) Manifestation and Symptom ?? » Manifestation and Symptom ?? » Links to other relevant information, including pathology reports Links to other relevant information, including pathology reports detail : : Reference [0..*] « [0..*] « Any » » Clinical stage or grade of a condition. May include formal severity assessments Clinical stage or grade of a condition. May include formal severity assessments stage [0..1] Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed evidence [0..*]

XML Template XML Template <

<Condition xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <</patient>
 <</encounter>
 <</asserter>
 <
 <</code>
 <</category>
 <
 <
 <</severity>
 <</onset[x]>
 <</abatement[x]>
 <
  <</summary>
  <</assessment>

 <identifier><!-- 0..* Identifier External Ids for this condition --></identifier>
 <clinicalStatus value="[code]"/><!-- 0..1 active | relapse | remission | resolved -->
 <verificationStatus value="[code]"/><!-- 1..1 provisional | differential | confirmed | refuted | entered-in-error | unknown -->
 <category><!-- 0..1 CodeableConcept complaint | symptom | finding | diagnosis --></category>
 <severity><!-- 0..1 CodeableConcept Subjective severity of condition --></severity>
 <code><!-- 1..1 CodeableConcept Identification of the condition, problem or diagnosis --></code>
 <bodySite><!-- 0..* CodeableConcept Anatomical location, if relevant --></bodySite>
 <subject><!-- 1..1 Reference(Patient|Group) Who has the condition? --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter when condition first asserted --></context>
 <onset[x]><!-- 0..1 dateTime|Age|Period|Range|string Estimated or actual date,  date-time, or age --></onset[x]>
 <abatement[x]><!-- 0..1 dateTime|Age|boolean|Period|Range|string If/when in resolution/remission --></abatement[x]>
 <dateRecorded value="[date]"/><!-- 0..1 When first entered -->
 <asserter><!-- 0..1 Reference(Practitioner|Patient) Person who asserts this condition --></asserter>
 <stage>  <!-- 0..1 Stage/grade, usually assessed formally -->
  <summary><!-- ?? 0..1 CodeableConcept Simple summary (disease specific) --></summary>
  <assessment><!-- ?? 0..* Reference(ClinicalImpression|DiagnosticReport|Observation) Formal record of assessment --></assessment>

 </stage>
 <
  <</code>
  <</detail>

 <evidence>  <!-- 0..* Supporting evidence -->
  <code><!-- ?? 0..1 CodeableConcept Manifestation/symptom --></code>
  <detail><!-- ?? 0..* Reference(Any) Supporting information found elsewhere --></detail>

 </evidence>
 <</bodySite>
 <

 <note><!-- 0..* Annotation Additional information about the Condition --></note>

</Condition>

JSON Template JSON Template { "resourceType" : "",

{doco
  "resourceType" : "Condition",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "
  "
  "
  "
  "

  "identifier" : [{ Identifier }], // External Ids for this condition
  "clinicalStatus" : "<code>", // active | relapse | remission | resolved
  "verificationStatus" : "<code>", // R!  provisional | differential | confirmed | refuted | entered-in-error | unknown
  "category" : { CodeableConcept }, // complaint | symptom | finding | diagnosis
  "severity" : { CodeableConcept }, // Subjective severity of condition
  "code" : { CodeableConcept }, // R!  Identification of the condition, problem or diagnosis
  "bodySite" : [{ CodeableConcept }], // Anatomical location, if relevant
  "subject" : { Reference(Patient|Group) }, // R!  Who has the condition?
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter when condition first asserted

  // onset[x]: Estimated or actual date,  date-time, or age. One of these 5:
  ">",
  " },
  " },
  " },
  ">",

  "onsetDateTime" : "<dateTime>",
  "onsetAge" : { Age },
  "onsetPeriod" : { Period },
  "onsetRange" : { Range },
  "onsetString" : "<string>",

  // abatement[x]: If/when in resolution/remission. One of these 6:
  ">",
  " },
  ">,
  " },
  " },
  ">",
  "
    "
    "

  "abatementDateTime" : "<dateTime>",
  "abatementAge" : { Age },
  "abatementBoolean" : <boolean>,
  "abatementPeriod" : { Period },
  "abatementRange" : { Range },
  "abatementString" : "<string>",
  "dateRecorded" : "<date>", // When first entered
  "asserter" : { Reference(Practitioner|Patient) }, // Person who asserts this condition
  "stage" : { // Stage/grade, usually assessed formally
    "summary" : { CodeableConcept }, // C? Simple summary (disease specific)
    "assessment" : [{ Reference(ClinicalImpression|DiagnosticReport|Observation) }] // C? Formal record of assessment

  },
  "
    "
    "

  "evidence" : [{ // Supporting evidence
    "code" : { CodeableConcept }, // C? Manifestation/symptom
    "detail" : [{ Reference(Any) }] // C? Supporting information found elsewhere

  }],
  "
  "

  "note" : [{ Annotation }] // Additional information about the Condition

}

Turtle Template


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Condition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Condition.identifier [ Identifier ], ... ; # 0..* External Ids for this condition
  fhir:Condition.clinicalStatus [ code ]; # 0..1 active | relapse | remission | resolved
  fhir:Condition.verificationStatus [ code ]; # 1..1 provisional | differential | confirmed | refuted | entered-in-error | unknown
  fhir:Condition.category [ CodeableConcept ]; # 0..1 complaint | symptom | finding | diagnosis
  fhir:Condition.severity [ CodeableConcept ]; # 0..1 Subjective severity of condition
  fhir:Condition.code [ CodeableConcept ]; # 1..1 Identification of the condition, problem or diagnosis
  fhir:Condition.bodySite [ CodeableConcept ], ... ; # 0..* Anatomical location, if relevant
  fhir:Condition.subject [ Reference(Patient|Group) ]; # 1..1 Who has the condition?
  fhir:Condition.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter when condition first asserted
  # Condition.onset[x] : 0..1 Estimated or actual date,  date-time, or age. One of these 5
    fhir:Condition.onsetDateTime [ dateTime ]
    fhir:Condition.onsetAge [ Age ]
    fhir:Condition.onsetPeriod [ Period ]
    fhir:Condition.onsetRange [ Range ]
    fhir:Condition.onsetString [ string ]
  # Condition.abatement[x] : 0..1 If/when in resolution/remission. One of these 6
    fhir:Condition.abatementDateTime [ dateTime ]
    fhir:Condition.abatementAge [ Age ]
    fhir:Condition.abatementBoolean [ boolean ]
    fhir:Condition.abatementPeriod [ Period ]
    fhir:Condition.abatementRange [ Range ]
    fhir:Condition.abatementString [ string ]
  fhir:Condition.dateRecorded [ date ]; # 0..1 When first entered
  fhir:Condition.asserter [ Reference(Practitioner|Patient) ]; # 0..1 Person who asserts this condition
  fhir:Condition.stage [ # 0..1 Stage/grade, usually assessed formally
    fhir:Condition.stage.summary [ CodeableConcept ]; # 0..1 Simple summary (disease specific)
    fhir:Condition.stage.assessment [ Reference(ClinicalImpression|DiagnosticReport|Observation) ], ... ; # 0..* Formal record of assessment
  ];
  fhir:Condition.evidence [ # 0..* Supporting evidence
    fhir:Condition.evidence.code [ CodeableConcept ]; # 0..1 Manifestation/symptom
    fhir:Condition.evidence.detail [ Reference(Any) ], ... ; # 0..* Supporting information found elsewhere
  ], ...;
  fhir:Condition.note [ Annotation ], ... ; # 0..* Additional information about the Condition
]

Changes since DSTU2

Condition
Condition.clinicalStatus Add Binding http://hl7.org/fhir/ValueSet/condition-clinical (required)
Condition.subject Renamed from patient to subject
Add Reference(Group)
Condition.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
Condition.onset[x] Remove Quantity{http://hl7.org/fhir/StructureDefinition/Age}, Add Age
Condition.abatement[x] Remove Quantity{http://hl7.org/fhir/StructureDefinition/Age}, Add Age
Condition.note Renamed from notes to note
Max Cardinality changed from 1 to *
Type changed from string to Annotation

See the Full Difference for further information

Structure

Encounter when condition first asserted
Name Flags Card. Type Description & Constraints Description & Constraints doco
. . Condition Σ DomainResource Detailed information about conditions, problems or diagnoses Detailed information about conditions, problems or diagnoses
. . . identifier Σ 0..* Identifier External Ids for this condition External Ids for this condition
. . patient . clinicalStatus Σ ?! Σ 1..1 Reference ( Patient ) 0..1 Who has the condition? encounter code active | relapse | remission | resolved
Σ 0..1 Reference ( Encounter Condition Clinical Status Codes ( Required )
. . asserter . verificationStatus ?! Σ 0..1 1..1 Reference ( Practitioner | Patient code ) Person who asserts this condition provisional | differential | confirmed | refuted | entered-in-error | unknown
ConditionVerificationStatus ( Required )
. . dateRecorded . category Σ 0..1 date CodeableConcept When first entered complaint | symptom | finding | diagnosis
Condition Category Codes ( Preferred )
. . code . severity Σ 1..1 0..1 CodeableConcept Identification of the condition, problem or diagnosis Subjective severity of condition
Condition/Problem/Diagnosis Codes ( Example Condition/Diagnosis Severity ( Preferred )
. . category . code Σ 0..1 1..1 CodeableConcept complaint | symptom | finding | diagnosis Identification of the condition, problem or diagnosis
Condition Category Codes ( Preferred Condition/Problem/Diagnosis Codes ( Example )
. . clinicalStatus . bodySite ?! Σ 0..1 0..* code CodeableConcept active | relapse | remission | resolved Anatomical location, if relevant
Condition Clinical Status Codes ( Preferred SNOMED CT Body Structures ( Example )
. . verificationStatus . subject ?! Σ 1..1 code provisional | differential | confirmed | refuted | entered-in-error | unknown ConditionVerificationStatus Reference ( Required Patient | Group ) Who has the condition?
. . severity . context Σ 0..1 CodeableConcept Subjective severity of condition Condition/Diagnosis Severity Reference ( Preferred Encounter | EpisodeOfCare ) Encounter when condition first asserted
. . . onset[x] Σ 0..1 Estimated or actual date, date-time, or age Estimated or actual date, date-time, or age
. . . . onsetDateTime dateTime
. . . . onsetAge onsetQuantity Age
. . . . onsetPeriod Period
. . . . onsetRange Range
. . . . onsetString string
. . . abatement[x] Σ 0..1 If/when in resolution/remission If/when in resolution/remission
. . . . abatementDateTime dateTime
. . . . abatementAge abatementQuantity Age
. . . . abatementBoolean boolean
. . . . abatementPeriod Period
. . . . abatementRange Range
. . . . abatementString string
. . . dateRecorded Σ 0..1 date When first entered
... asserter Σ 0..1 Reference ( Practitioner | Patient ) Person who asserts this condition
. . . stage Σ I 0..1 BackboneElement Stage/grade, usually assessed formally Stage/grade, usually assessed formally
Stage SHALL have summary or assessment Stage SHALL have summary or assessment
. . . . summary Σ I 0..1 CodeableConcept Simple summary (disease specific) Simple summary (disease specific)
Condition Stage ( Condition Stage ( Example )
. . . . assessment Σ I 0..* Reference ( ClinicalImpression | | DiagnosticReport | | Observation ) Formal record of assessment Formal record of assessment
. . . evidence Σ I 0..* BackboneElement Supporting evidence Supporting evidence
evidence SHALL have code or details evidence SHALL have code or details
. . . . code Σ I 0..1 CodeableConcept Manifestation/symptom
Manifestation and Symptom Codes ( Manifestation and Symptom Codes ( Example )
. . . . detail Σ I 0..* Reference ( Any ) Supporting information found elsewhere bodySite Σ 0..* CodeableConcept Anatomical location, if relevant SNOMED CT Body Structures ( Example ) Supporting information found elsewhere
. . notes . note Σ 0..1 0..* string Annotation Additional information about the Condition Additional information about the Condition

Documentation for this format doco Documentation for this format

UML Diagram UML Diagram ( Legend )

Condition ( ( DomainResource ) This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation) This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation) identifier : : Identifier [0..*] [0..*] Indicates the patient who the condition record is associated with The clinical status of the condition (this element modifies the meaning of other elements) patient : Reference [1..1] « Patient » clinicalStatus : code [0..1] « Encounter during which the condition was first asserted The clinical status of the condition or diagnosis. (Strength=Required) encounter : Reference [0..1] « Encounter » Condition Clinical Status ! » Individual who is making the condition statement The verification status to support the clinical status of the condition (this element modifies the meaning of other elements) asserter : Reference [0..1] « Practitioner | Patient » verificationStatus : code [1..1] « A date, when the Condition statement was documented The verification status to support or decline the clinical status of the condition or diagnosis. (Strength=Required) dateRecorded : date [0..1] ConditionVerificationStatus ! » Identification of the condition, problem or diagnosis A category assigned to the condition code : category : CodeableConcept [1..1] « [0..1] « Identification of the condition or diagnosis. (Strength=Example) A category assigned to the condition. (Strength=Preferred) Condition/Problem/Diagnosis ?? » Condition Category ? » A category assigned to the condition A subjective assessment of the severity of the condition as evaluated by the clinician category : severity : CodeableConcept [0..1] « [0..1] « A category assigned to the condition. (Strength=Preferred) A subjective assessment of the severity of the condition as evaluated by the clinician. (Strength=Preferred) Condition Category Condition/Diagnosis Severity ? » ? » The clinical status of the condition (this element modifies the meaning of other elements) Identification of the condition, problem or diagnosis clinicalStatus : code [0..1] « : CodeableConcept [1..1] « The clinical status of the condition or diagnosis. (Strength=Preferred) Identification of the condition or diagnosis. (Strength=Example) Condition Clinical Status ? » Condition/Problem/Diagnosis ?? » The verification status to support the clinical status of the condition (this element modifies the meaning of other elements) The anatomical location where this condition manifests itself verificationStatus : code [1..1] « bodySite : CodeableConcept [0..*] « The verification status to support or decline the clinical status of the condition or diagnosis. (Strength=Required) Codes describing anatomical locations. May include laterality. (Strength=Example) ConditionVerificationStatus ! » SNOMED CT Body Structures ?? » A subjective assessment of the severity of the condition as evaluated by the clinician Indicates the patient or group who the condition record is associated with severity : CodeableConcept subject : Reference [1..1] « Patient [0..1] « | Group » A subjective assessment of the severity of the condition as evaluated by the clinician. (Strength=Preferred) Encounter during which the condition was first asserted Condition/Diagnosis Severity context : Reference [0..1] « Encounter ? » | EpisodeOfCare » Estimated or actual date or date-time the condition began, in the opinion of the clinician Estimated or actual date or date-time the condition began, in the opinion of the clinician onset[x] : : Type [0..1] « [0..1] « dateTime | Quantity ( Age )| | Period | Range | string » » The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate abatement[x] : : Type [0..1] « [0..1] « dateTime | Quantity ( Age )| | boolean | Period | Range | string » » The anatomical location where this condition manifests itself A date, when the Condition statement was documented bodySite : CodeableConcept [0..*] « dateRecorded : date [0..1] Codes describing anatomical locations. May include laterality. (Strength=Example) Individual who is making the condition statement SNOMED CT Body Structures asserter : Reference [0..1] « Practitioner ?? » | Patient » Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis notes : string [0..1] note : Annotation [0..*] Stage A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific summary : : CodeableConcept [0..1] « [0..1] « Codes describing condition stages (e.g. Cancer stages). (Strength=Example) Codes describing condition stages (e.g. Cancer stages). (Strength=Example) Condition Stage Condition Stage ?? » ?? » Reference to a formal record of the evidence on which the staging assessment is based Reference to a formal record of the evidence on which the staging assessment is based assessment : : Reference [0..*] « [0..*] « ClinicalImpression | DiagnosticReport | Observation » » Evidence A manifestation or symptom that led to the recording of this condition A manifestation or symptom that led to the recording of this condition code : : CodeableConcept [0..1] « [0..1] « Codes that describe the manifestation or symptoms of a condition. (Strength=Example) Codes that describe the manifestation or symptoms of a condition. (Strength=Example) Manifestation and Symptom ?? » Manifestation and Symptom ?? » Links to other relevant information, including pathology reports Links to other relevant information, including pathology reports detail : : Reference [0..*] « [0..*] « Any » » Clinical stage or grade of a condition. May include formal severity assessments Clinical stage or grade of a condition. May include formal severity assessments stage [0..1] Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed evidence [0..*]

XML Template XML Template <

<Condition xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <</identifier>
 <</patient>
 <</encounter>
 <</asserter>
 <
 <</code>
 <</category>
 <
 <
 <</severity>
 <</onset[x]>
 <</abatement[x]>
 <
  <</summary>
  <</assessment>

 <identifier><!-- 0..* Identifier External Ids for this condition --></identifier>
 <clinicalStatus value="[code]"/><!-- 0..1 active | relapse | remission | resolved -->
 <verificationStatus value="[code]"/><!-- 1..1 provisional | differential | confirmed | refuted | entered-in-error | unknown -->
 <category><!-- 0..1 CodeableConcept complaint | symptom | finding | diagnosis --></category>
 <severity><!-- 0..1 CodeableConcept Subjective severity of condition --></severity>
 <code><!-- 1..1 CodeableConcept Identification of the condition, problem or diagnosis --></code>
 <bodySite><!-- 0..* CodeableConcept Anatomical location, if relevant --></bodySite>
 <subject><!-- 1..1 Reference(Patient|Group) Who has the condition? --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter when condition first asserted --></context>
 <onset[x]><!-- 0..1 dateTime|Age|Period|Range|string Estimated or actual date,  date-time, or age --></onset[x]>
 <abatement[x]><!-- 0..1 dateTime|Age|boolean|Period|Range|string If/when in resolution/remission --></abatement[x]>
 <dateRecorded value="[date]"/><!-- 0..1 When first entered -->
 <asserter><!-- 0..1 Reference(Practitioner|Patient) Person who asserts this condition --></asserter>
 <stage>  <!-- 0..1 Stage/grade, usually assessed formally -->
  <summary><!-- ?? 0..1 CodeableConcept Simple summary (disease specific) --></summary>
  <assessment><!-- ?? 0..* Reference(ClinicalImpression|DiagnosticReport|Observation) Formal record of assessment --></assessment>

 </stage>
 <
  <</code>
  <</detail>

 <evidence>  <!-- 0..* Supporting evidence -->
  <code><!-- ?? 0..1 CodeableConcept Manifestation/symptom --></code>
  <detail><!-- ?? 0..* Reference(Any) Supporting information found elsewhere --></detail>

 </evidence>
 <</bodySite>
 <

 <note><!-- 0..* Annotation Additional information about the Condition --></note>

</Condition>

JSON Template JSON Template { "resourceType" : "",

{doco
  "resourceType" : "Condition",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "
  "
  "
  "
  "
  "
  "
  "
  "
  "

  "identifier" : [{ Identifier }], // External Ids for this condition
  "clinicalStatus" : "<code>", // active | relapse | remission | resolved
  "verificationStatus" : "<code>", // R!  provisional | differential | confirmed | refuted | entered-in-error | unknown
  "category" : { CodeableConcept }, // complaint | symptom | finding | diagnosis
  "severity" : { CodeableConcept }, // Subjective severity of condition
  "code" : { CodeableConcept }, // R!  Identification of the condition, problem or diagnosis
  "bodySite" : [{ CodeableConcept }], // Anatomical location, if relevant
  "subject" : { Reference(Patient|Group) }, // R!  Who has the condition?
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter when condition first asserted

  // onset[x]: Estimated or actual date,  date-time, or age. One of these 5:
  ">",
  " },
  " },
  " },
  ">",

  "onsetDateTime" : "<dateTime>",
  "onsetAge" : { Age },
  "onsetPeriod" : { Period },
  "onsetRange" : { Range },
  "onsetString" : "<string>",

  // abatement[x]: If/when in resolution/remission. One of these 6:
  ">",
  " },
  ">,
  " },
  " },
  ">",
  "
    "
    "

  "abatementDateTime" : "<dateTime>",
  "abatementAge" : { Age },
  "abatementBoolean" : <boolean>,
  "abatementPeriod" : { Period },
  "abatementRange" : { Range },
  "abatementString" : "<string>",
  "dateRecorded" : "<date>", // When first entered
  "asserter" : { Reference(Practitioner|Patient) }, // Person who asserts this condition
  "stage" : { // Stage/grade, usually assessed formally
    "summary" : { CodeableConcept }, // C? Simple summary (disease specific)
    "assessment" : [{ Reference(ClinicalImpression|DiagnosticReport|Observation) }] // C? Formal record of assessment

  },
  "
    "
    "

  "evidence" : [{ // Supporting evidence
    "code" : { CodeableConcept }, // C? Manifestation/symptom
    "detail" : [{ Reference(Any) }] // C? Supporting information found elsewhere

  }],
  "
  "

  "note" : [{ Annotation }] // Additional information about the Condition

}
 
Alternate
definitions:

Turtle Template


@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:Condition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:Condition.identifier [ Identifier ], ... ; # 0..* External Ids for this condition
  fhir:Condition.clinicalStatus [ code ]; # 0..1 active | relapse | remission | resolved
  fhir:Condition.verificationStatus [ code ]; # 1..1 provisional | differential | confirmed | refuted | entered-in-error | unknown
  fhir:Condition.category [ CodeableConcept ]; # 0..1 complaint | symptom | finding | diagnosis
  fhir:Condition.severity [ CodeableConcept ]; # 0..1 Subjective severity of condition
  fhir:Condition.code [ CodeableConcept ]; # 1..1 Identification of the condition, problem or diagnosis
  fhir:Condition.bodySite [ CodeableConcept ], ... ; # 0..* Anatomical location, if relevant
  fhir:Condition.subject [ Reference(Patient|Group) ]; # 1..1 Who has the condition?
  fhir:Condition.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter when condition first asserted
  # Condition.onset[x] : 0..1 Estimated or actual date,  date-time, or age. One of these 5
    fhir:Condition.onsetDateTime [ dateTime ]
    fhir:Condition.onsetAge [ Age ]
    fhir:Condition.onsetPeriod [ Period ]
    fhir:Condition.onsetRange [ Range ]
    fhir:Condition.onsetString [ string ]
  # Condition.abatement[x] : 0..1 If/when in resolution/remission. One of these 6
    fhir:Condition.abatementDateTime [ dateTime ]
    fhir:Condition.abatementAge [ Age ]
    fhir:Condition.abatementBoolean [ boolean ]
    fhir:Condition.abatementPeriod [ Period ]
    fhir:Condition.abatementRange [ Range ]
    fhir:Condition.abatementString [ string ]
  fhir:Condition.dateRecorded [ date ]; # 0..1 When first entered
  fhir:Condition.asserter [ Reference(Practitioner|Patient) ]; # 0..1 Person who asserts this condition
  fhir:Condition.stage [ # 0..1 Stage/grade, usually assessed formally
    fhir:Condition.stage.summary [ CodeableConcept ]; # 0..1 Simple summary (disease specific)
    fhir:Condition.stage.assessment [ Reference(ClinicalImpression|DiagnosticReport|Observation) ], ... ; # 0..* Formal record of assessment
  ];
  fhir:Condition.evidence [ # 0..* Supporting evidence
    fhir:Condition.evidence.code [ CodeableConcept ]; # 0..1 Manifestation/symptom
    fhir:Condition.evidence.detail [ Reference(Any) ], ... ; # 0..* Supporting information found elsewhere
  ], ...;
  fhir:Condition.note [ Annotation ], ... ; # 0..* Additional information about the Condition
]

Changes since DSTU2

Condition
Condition.clinicalStatus Add Binding http://hl7.org/fhir/ValueSet/condition-clinical (required)
Condition.subject Renamed from patient to subject
Add Reference(Group)
Condition.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
Condition.onset[x] Remove Quantity{http://hl7.org/fhir/StructureDefinition/Age}, Add Age
Condition.abatement[x] Remove Quantity{http://hl7.org/fhir/StructureDefinition/Age}, Add Age
Condition.note Renamed from notes to note
Max Cardinality changed from 1 to *
Type changed from string to Annotation

See the Full Difference for further information

 

Alternate definitions: Master Definition ( XML , JSON ), XML Schema / Schematron , Resource Profile ( XML , (for ) + JSON Schema , ShEx (for Turtle ), Questionnaire )

4.3.3.1 Terminology Bindings 9.2.3.1 Terminology Bindings

Condition.code Condition.category Condition.clinicalStatus Condition.verificationStatus Condition.severity Condition.stage.summary Condition.evidence.code Condition.bodySite
Path Definition Type Reference
Condition.clinicalStatus Identification of the condition or diagnosis. The clinical status of the condition or diagnosis. Example Required Condition/Problem/Diagnosis Codes Condition Clinical Status Codes
Condition.verificationStatus A category assigned to the condition. The verification status to support or decline the clinical status of the condition or diagnosis. Preferred Required Condition Category Codes ConditionVerificationStatus
Condition.category The clinical status of the condition or diagnosis. A category assigned to the condition. Preferred Condition Clinical Status Codes Condition Category Codes
Condition.severity The verification status to support or decline the clinical status of the condition or diagnosis. A subjective assessment of the severity of the condition as evaluated by the clinician. Required Preferred ConditionVerificationStatus Condition/Diagnosis Severity
Condition.code A subjective assessment of the severity of the condition as evaluated by the clinician. Identification of the condition or diagnosis. Preferred Example Condition/Diagnosis Severity Condition/Problem/Diagnosis Codes
Condition.bodySite Codes describing condition stages (e.g. Cancer stages). Codes describing anatomical locations. May include laterality. Example Condition Stage SNOMED CT Body Structures
Condition.stage.summary Codes that describe the manifestation or symptoms of a condition. Codes describing condition stages (e.g. Cancer stages). Example Manifestation and Symptom Codes Condition Stage
Condition.evidence.code Codes describing anatomical locations. May include laterality. Codes that describe the manifestation or symptoms of a condition. Example SNOMED CT Body Structures Manifestation and Symptom Codes

4.3.3.2 Constraints 9.2.3.2 Constraints

  • con-1 : On Condition.stage: Stage SHALL have summary or assessment (xpath on f:Condition/f:stage: exists(f:summary) or exists(f:assessment) : On Condition.stage: Stage SHALL have summary or assessment ( expression on Condition.stage: summary.exists() or assessment.exists() )
  • con-2 : On Condition.evidence: evidence SHALL have code or details (xpath on f:Condition/f:evidence: exists(f:code) or exists(f:detail) : On Condition.evidence: evidence SHALL have code or details ( expression on Condition.evidence: code.exists() or detail.exists() )

4.3.3.3 9.2.3.3 Use of Condition.code Use of Condition.code Many of the code systems used for coding conditions will provide codes that define not only the condition itself, but may also specify a particular stage, location, or causality as part of the code. This is particularly true if SNOMED CT is used for the condition, and especially if expressions are allowed. The Condition.code may also include such concepts as "history of X" and "good health", where it is useful or appropriate to make such assertions. It can also be used to capture "risk of" and "fear of" in addition to physical conditions. When the Condition.code specifies additional properties of the condition, the other properties are not given a value - instead, the value must be understood from the Condition.code.

Many of the code systems used for coding conditions will provide codes that define not only the condition itself, but may also specify a particular stage, location, or causality as part of the code. This is particularly true if SNOMED CT is used for the condition, and especially if expressions are allowed.

The Condition.code may also include such concepts as "history of X" and "good health", where it is useful or appropriate to make such assertions. It can also be used to capture "risk of" and "fear of", in addition to physical conditions, as well as "no known problems" or "negated" conditions (e.g., "no X" or "no history of X" - see the following section for "No Known Problems" and Negated Conditions).

When the Condition.code specifies additional properties of the condition, the other properties are not given a value - instead, the value must be understood from the Condition.code.

4.3.3.4 9.2.3.4 Use of Condition.evidence "No Known Problems" and Negated Conditions The Condition.evidence provides the basis for whatever is present in Condition.code.

Conditions/Problems Not Reviewed, Not Asked

When a sending system does not have any information about conditions/problems being reviewed or the statement is about conditions/problems not yet being asked, then the List resource should be used to indicate the List.emptyReason.code="notasked".

Conditions/Problems Reviewed, None Identified

Systems may use the List.emptyReason when a statement is about the full scope of the list (i.e. the patient has no conditions/problems of any type). However, it may be preferred to use a code for "no known problems" (e.g., SNOMED CT: 160245001 |No current problems or disability (situation)|), so that all condition/problem data will be available and queryable from Condition resource instances.

Also note that care should be used when adding new Condition resources to a list to ensure that any negation statements that are voided by the addition of a new record are removed from the list. E.g. If the list contains a "no known problems" record and you add a "diabetes" condition record, then be sure that you remove the "no known problems" record.

STU Note: There are two primary ways of reporting "no known problems" in the current specification: using the CodeableConcept, as described above, or using the List resource with emptyReason. During the STU period, feedback is sought regarding the preferred approach.

4.3.3.5 9.2.3.5 Use of Condition.abatementRange Use of Condition.evidence A range is used to communicate age period of subject at time of abatement.

The Condition.evidence provides the basis for whatever is present in Condition.code.

4.3.3.6 9.2.3.6 Use of Condition.asserter Use of Condition.abatementRange If the data enterer is different from the asserter and needs to be known, this could be captured using a Provenance instance pointing to the Condition. For example, it is possible that a nurse records the condition on behalf of a physician. The physician is taking responsibility, despite the nurse entering it into the medical record.

A range is used to communicate age period of subject at time of abatement.

4.3.3.7 9.2.3.7 Use of Condition.clinicalStatus Use of Condition.asserter The Condition.stage and Condition.clinicalStatus may have interdependencies. For example, some "stages" of cancer, etc. will be different for a remission than for the initial occurrence.

If the data enterer is different from the asserter and needs to be known, this could be captured using a Provenance instance pointing to the Condition. For example, it is possible that a nurse records the condition on behalf of a physician. The physician is taking responsibility, despite the nurse entering it into the medical record.

4.3.4 Search Parameters 9.2.3.8 Use of Condition.clinicalStatus Search parameters for this resource. The common parameters

The Condition.stage and Condition.clinicalStatus may have interdependencies. For example, some "stages" of cancer, etc. will be different for a remission than for the initial occurrence.

9.2.4 Search Parameters also apply. See

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services. for more information about searching in REST, messaging, and services.

© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:43+1100. Links: Search | Version History | Table of Contents | Compare to DSTU1 | Propose a change
Name Type Description Paths
abatement-age quantity Abatement as age or age range Condition.abatement[x]
abatement-boolean token Abatement boolean (boolean is true or non-boolean values are present) Condition.abatement[x]
abatement-date date Date-related abatements (dateTime and period) Condition.abatement[x]
abatement-info quantity Abatement as a string Condition.abatement[x]
asserter reference Person who asserts this condition Person who asserts this condition Condition.asserter
( Patient , Practitioner , Patient )
body-site token Anatomical location, if relevant Anatomical location, if relevant Condition.bodySite
category token The category of the condition The category of the condition Condition.category
clinicalstatus token The clinical status of the condition The clinical status of the condition Condition.clinicalStatus
code token Code for the condition Code for the condition Condition.code
date-recorded context date reference A date, when the Condition statement was documented Encounter when condition first asserted Condition.dateRecorded Condition.context
( EpisodeOfCare , Encounter )
encounter date-recorded reference date Encounter when condition first asserted A date, when the Condition statement was documented Condition.encounter ( Encounter ) Condition.dateRecorded
evidence token Manifestation/symptom Condition.evidence.code
identifier token A unique identifier of the condition record A unique identifier of the condition record Condition.identifier
onset onset-age quantity Onsets as age or age range Condition.onset[x]
onset-date date Date related onsets (dateTime and Period) Date related onsets (dateTime and Period) Condition.onset[x]
onset-info string Other onsets (boolean, age, range, string) Onsets as a string Condition.onset[x]
patient reference Who has the condition? Who has the condition? Condition.patient Condition.subject
( Patient )
severity token The severity of the condition The severity of the condition Condition.severity
stage token Simple summary (disease specific) Simple summary (disease specific) Condition.stage.summary
subject reference | Who has the condition? Condition.subject
( Group , Patient try { var currentTabIndex = sessionStorage.getItem('fhir-resource-tab-index'); } catch(exception){ } if (!currentTabIndex) currentTabIndex = '0'; $( '#tabs' ).tabs({ active: currentTabIndex, activate: function( event, ui ) { var active = $('.selector').tabs('option', 'active'); currentTabIndex = ui.newTab.index(); document.activeElement.blur(); try { sessionStorage.setItem('fhir-resource-tab-index', currentTabIndex); } catch(exception){ } } });