R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

9.2 JSON Schema for Condition

Patient Care Work GroupMaturity Level: N/ABallot Status: Informative Compartments: Encounter, Patient, Practitioner, RelatedPerson

This is a representation of the json schema for Condition, which is just a part of the full JSON Schema.

{
  "$schema": "http://json-schema.org/draft-06/schema#",
  "id": "http://hl7.org/fhir/json-schema/Condition",
  "$ref": "#/definitions/Condition",
  "description": "see http://hl7.org/fhir/json.html#schema for information about the FHIR Json Schemas",
  "definitions": {
    "Condition": {
      "description": "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.",
      "properties": {
        "resourceType": {
          "description": "This is a Condition resource",
          "const": "Condition"
        },
        "id": {
          "description": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
          "$ref": "id.schema.json#/definitions/id"
        },
        "meta": {
          "description": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.",
          "$ref": "Meta.schema.json#/definitions/Meta"
        },
        "implicitRules": {
          "description": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.",
          "$ref": "#/definitions/uri"
        },
        "_implicitRules": {
          "description": "Extensions for implicitRules",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "language": {
          "description": "The base language in which the resource is written.",
          "$ref": "#/definitions/code"
        },
        "_language": {
          "description": "Extensions for language",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "text": {
          "description": "A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
          "$ref": "Narrative.schema.json#/definitions/Narrative"
        },
        "contained": {
          "description": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
          "items": {
            "$ref": "ResourceList.schema.json#/definitions/ResourceList"
          },
          "type": "array"
        },
        "extension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "modifierExtension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "identifier": {
          "description": "Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.",
          "items": {
            "$ref": "Identifier.schema.json#/definitions/Identifier"
          },
          "type": "array"
        },
        "clinicalStatus": {
          "description": "The clinical status of the condition.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        },
        "verificationStatus": {
          "description": "The verification status to support the clinical status of the condition.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        },
        "category": {
          "description": "A category assigned to the condition.",
          "items": {
            "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
          },
          "type": "array"
        },
        "severity": {
          "description": "A subjective assessment of the severity of the condition as evaluated by the clinician.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        },
        "code": {
          "description": "Identification of the condition, problem or diagnosis.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        },
        "bodySite": {
          "description": "The anatomical location where this condition manifests itself.",
          "items": {
            "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
          },
          "type": "array"
        },
        "subject": {
          "description": "Indicates the patient or group who the condition record is associated with.",
          "$ref": "Reference.schema.json#/definitions/Reference"
        },
        "context": {
          "description": "Encounter during which the condition was first asserted.",
          "$ref": "Reference.schema.json#/definitions/Reference"
        },
        "onsetDateTime": {
          "description": "Estimated or actual date or date-time  the condition began, in the opinion of the clinician.",
          "pattern": "^([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?$",
          "type": "string"
        },
        "_onsetDateTime": {
          "description": "Extensions for onsetDateTime",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "onsetAge": {
          "description": "Estimated or actual date or date-time  the condition began, in the opinion of the clinician.",
          "$ref": "Age.schema.json#/definitions/Age"
        },
        "onsetPeriod": {
          "description": "Estimated or actual date or date-time  the condition began, in the opinion of the clinician.",
          "$ref": "Period.schema.json#/definitions/Period"
        },
        "onsetRange": {
          "description": "Estimated or actual date or date-time  the condition began, in the opinion of the clinician.",
          "$ref": "Range.schema.json#/definitions/Range"
        },
        "onsetString": {
          "description": "Estimated or actual date or date-time  the condition began, in the opinion of the clinician.",
          "pattern": "^[ \\r\\n\\t\\S]+$",
          "type": "string"
        },
        "_onsetString": {
          "description": "Extensions for onsetString",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "abatementDateTime": {
          "description": "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.",
          "pattern": "^([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?$",
          "type": "string"
        },
        "_abatementDateTime": {
          "description": "Extensions for abatementDateTime",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "abatementAge": {
          "description": "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.",
          "$ref": "Age.schema.json#/definitions/Age"
        },
        "abatementPeriod": {
          "description": "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.",
          "$ref": "Period.schema.json#/definitions/Period"
        },
        "abatementRange": {
          "description": "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.",
          "$ref": "Range.schema.json#/definitions/Range"
        },
        "abatementString": {
          "description": "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.",
          "pattern": "^[ \\r\\n\\t\\S]+$",
          "type": "string"
        },
        "_abatementString": {
          "description": "Extensions for abatementString",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "recordedDate": {
          "description": "The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.",
          "$ref": "#/definitions/dateTime"
        },
        "_recordedDate": {
          "description": "Extensions for recordedDate",
          "$ref": "Element.schema.json#/definitions/Element"
        },
        "recorder": {
          "description": "Individual who recorded the record and takes responsibility for its content.",
          "$ref": "Reference.schema.json#/definitions/Reference"
        },
        "asserter": {
          "description": "Individual who is making the condition statement.",
          "$ref": "Reference.schema.json#/definitions/Reference"
        },
        "stage": {
          "description": "Clinical stage or grade of a condition. May include formal severity assessments.",
          "items": {
            "$ref": "#/definitions/Condition_Stage"
          },
          "type": "array"
        },
        "evidence": {
          "description": "Supporting evidence / manifestations that are the basis of the Condition\u0027s verification status, such as evidence that confirmed or refuted the condition.",
          "items": {
            "$ref": "#/definitions/Condition_Evidence"
          },
          "type": "array"
        },
        "note": {
          "description": "Additional information about the Condition. This is a general notes/comments entry  for description of the Condition, its diagnosis and prognosis.",
          "items": {
            "$ref": "Annotation.schema.json#/definitions/Annotation"
          },
          "type": "array"
        }
      },
      "additionalProperties": false,
      "required": [
        "subject",
        "resourceType"
      ]
    },
    "Condition_Stage": {
      "description": "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.",
      "properties": {
        "id": {
          "description": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
          "$ref": "string.schema.json#/definitions/string"
        },
        "extension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "modifierExtension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "summary": {
          "description": "A simple summary of the stage such as \"Stage 3\". The determination of the stage is disease-specific.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        },
        "assessment": {
          "description": "Reference to a formal record of the evidence on which the staging assessment is based.",
          "items": {
            "$ref": "Reference.schema.json#/definitions/Reference"
          },
          "type": "array"
        },
        "type": {
          "description": "The kind of staging, such as pathological or clinical staging.",
          "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
        }
      },
      "additionalProperties": false
    },
    "Condition_Evidence": {
      "description": "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.",
      "properties": {
        "id": {
          "description": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
          "$ref": "string.schema.json#/definitions/string"
        },
        "extension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "modifierExtension": {
          "description": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
          "items": {
            "$ref": "Extension.schema.json#/definitions/Extension"
          },
          "type": "array"
        },
        "code": {
          "description": "A manifestation or symptom that led to the recording of this condition.",
          "items": {
            "$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
          },
          "type": "array"
        },
        "detail": {
          "description": "Links to other relevant information, including pathology reports.",
          "items": {
            "$ref": "Reference.schema.json#/definitions/Reference"
          },
          "type": "array"
        }
      },
      "additionalProperties": false
    }
  }
}