xCaliber healthCare Data Mesh

Condition

Overview

The Condition API empowers healthcare developers to manage and retrieve patient health condition data in a standardized manner, facilitating the integration of real-time and historical health information into clinical workflows. By leveraging this API, developers can enhance diagnostic accuracy, treatment planning, and overall patient care by accessing and updating precise condition-related data within healthcare applications.

Use Cases

  • Clinical decision support - Assess conditions to inform diagnosis, treatment, medication choices during care.
  • Problem lists - Maintain longitudinal records of patient's conditions and diagnoses over time.
  • Care planning - Develop care plans addressing a patient's chronic health conditions and issues.
  • Billing and reimbursement - Submit claims using coded conditions as justification for items and services.
  • Clinical trials - Identify patients with certain conditions to recruit for clinical trials.
  • Disease management - Monitor conditions over time to optimize health outcomes for defined populations.
  • Public health - Track incidence and prevalence of conditions at a population level.
  • Quality reporting - Report condition-specific quality measures to regulators and health plans.

EHR Data Model

EHRSupported?Mapped Source Object
AthenaDiagnoses, Problems, Medical History
ElationProblem, History
EpicDiagnosis Provider, Diagnosis Identifier, Diagnosis

Object Definition

{
  "resourceType": "Condition",
  "id": "example",
  "text": {
    "status": "generated",
    "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Severe burn of left ear (Date: 24-May 2012)</div>"
  },
  "clinicalStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/condition-clinical",
        "code": "active"
      }
    ]
  },
  "verificationStatus": {
    "coding": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
        "code": "confirmed"
      }
    ]
  },
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/condition-category",
          "code": "encounter-diagnosis",
          "display": "Encounter Diagnosis"
        },
        {
          "system": "http://snomed.info/sct",
          "code": "439401001",
          "display": "Diagnosis"
        }
      ]
    }
  ],
  "severity": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "24484000",
        "display": "Severe"
      }
    ]
  },
  "code": {
    "coding": [
      {
        "system": "http://snomed.info/sct",
        "code": "39065001",
        "display": "Burn of ear"
      }
    ],
    "text": "Burnt Ear"
  },
  "bodySite": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "49521004",
          "display": "Left external ear structure"
        }
      ],
      "text": "Left Ear"
    }
  ],
  "subject": {
    "reference": "Patient/example"
  },
  "onsetDateTime": "2012-05-24",
  "meta": {
    "tag": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
        "code": "HTEST",
        "display": "test health data"
      }
    ]
  }
}

Data Fields

Data FieldTypeDescription
resourceTypeConditionThis is a Condition resource
ididThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
metaMetaThe 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.
implicitRulesuriA 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.
languagecodeThe base language in which the resource is written.
textNarrativeA 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.
containedBackboneElementThese 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.
extensionExtensionMay 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.
modifierExtensionExtensionMay 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 and/or the understanding of the containing element's descendants. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
identifierIdentifierBusiness 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.
clinicalStatusCodeableConceptThe clinical status of the condition.
verificationStatusCodeableConceptThe verification status to support the clinical status of the condition.
categoryCodeableConceptA category assigned to the condition.
severityCodeableConceptA subjective assessment of the severity of the condition as evaluated by the clinician.
codeCodeableConceptIdentification of the condition, problem or diagnosis.
bodySiteCodeableConceptThe anatomical location where this condition manifests itself.
subjectReferenceIndicates the patient or group who the condition record is associated with.
encounterReferenceThe Encounter during which this Condition was created or to which the creation of this record is tightly associated.
onsetDateTimestringEstimated or actual date or date-time the condition began, in the opinion of the clinician.
onsetAgeAgeEstimated or actual date or date-time the condition began, in the opinion of the clinician.
onsetPeriodPeriodEstimated or actual date or date-time the condition began, in the opinion of the clinician.
onsetRangeRangeEstimated or actual date or date-time the condition began, in the opinion of the clinician.
onsetStringstringEstimated or actual date or date-time the condition began, in the opinion of the clinician.
abatementDateTimestringThe 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.
abatementAgeAgeThe 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.
abatementPeriodPeriodThe 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.
abatementRangeRangeThe 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.
abatementStringstringThe 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.
recordedDatedateTimeThe recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.
recorderReferenceIndividual who recorded the record and takes responsibility for its content.
asserterReferenceIndividual who is making the condition statement.
stageBackboneElementClinical stage or grade of a condition. May include formal severity assessments.
stage.idstringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
stage.extensionExtensionMay 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.
stage.modifierExtensionExtensionMay 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 and/or the understanding of the containing element's descendants. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
stage.summaryCodeableConceptA simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific.
stage.assessmentReferenceReference to a formal record of the evidence on which the staging assessment is based.
stage.typeCodeableConceptThe kind of staging, such as pathological or clinical staging.
evidenceBackboneElementSupporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.
evidence.idstringUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
evidence.extensionExtensionMay 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.
evidence.modifierExtensionExtensionMay 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 and/or the understanding of the containing element's descendants. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
evidence.codeCodeableConceptA manifestation or symptom that led to the recording of this condition.
evidence.detailReferenceLinks to other relevant information, including pathology reports.
noteAnnotationAdditional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.

Extensions

NameURL
BESTMATCHICD10CODEhttp://xcaliber-fhir/structureDefinition/best-match-icd10-code
DEACTIVATEDDATEhttp://xcaliber-fhir/structureDefinition/deactivated-date
DEACTIVATEDUSERhttp://xcaliber-fhir/structureDefinition/deactivated-user
DELETEDDATEhttp://xcaliber-fhir/structureDefinition/deleted-date
LASTMODIFIEDBYhttp://xcaliber-fhir/structureDefinition/last-modified-by
LASTMODIFIEDDATETIMEhttp://xcaliber-fhir/structureDefinition/last-modified-datetime
MOSTRECENTDIAGNOSISNOTEhttp://xcaliber-fhir/structureDefinition/most-recent-diagnosis-note
LATERALITYhttp://xcaliber-fhir/structureDefinition/laterality
RANKINGhttp://xcaliber-fhir/structureDefinition/ranking
SUPPORTSLATERALITYhttp://xcaliber-fhir/structureDefinition/supports-laterality
PROBLEMSTATUShttp://xcaliber-fhir/structureDefinition/status
EVENTTYPEhttp://xcaliber-fhir/structureDefinition/event-type
ENCOUNTERDATEhttp://xcaliber-fhir/structureDefinition/encounter-date
SOURCEhttp://xcaliber-fhir/structureDefinition/source
ONSETDATEhttp://xcaliber-fhir/structureDefinition/on-set-date
ENCOUNTERDATETIMEhttp://xcaliber-fhir/structureDefinition/encounter-datetime
SECTIONNOTEhttp://xcaliber-fhir/structureDefinition/section-note
TYPEhttp://xcaliber-fhir/structureDefinition/type
RANKhttp://xcaliber-fhir/structureDefinition/rank
SERVICEDATEhttp://xcaliber-fhir/structureDefinition/service-date
BILLINGDATEhttp://xcaliber-fhir/structureDefinition/billing-date
BILLINGSTATUShttp://xcaliber-fhir/structureDefinition/billing-status
LOCATIONIDhttp://xcaliber-fhir/structureDefinition/location
EVENTTYPESTARThttp://xcaliber-fhir/structureDefinition/event-type-start
EVENTTYPEENDhttp://xcaliber-fhir/structureDefinition/event-type-end
EVENTTYPEFILLhttp://xcaliber-fhir/structureDefinition/event-type-fill
EVENTTYPEREACTIVATEDhttp://xcaliber-fhir/structureDefinition/event-type-reactivated
EVENTTYPEHIDEhttp://xcaliber-fhir/structureDefinition/event-type-hidden
EVENTTYPEENCOUNTERhttp://xcaliber-fhir/structureDefinition/event-type-encounter
STATUShttp://xcaliber-fhir/structureDefinition/status

Operations & APIs

Condition-GET

Condition-POST

Condition ID-GET

Condition ID-PUT

Condition ID-DELETE

Condition Export-POST