EncounterDiagnosis

Associates a clinical diagnosis with a specific healthcare encounter, capturing the role, context, and priority of the diagnosis. Essential for clinical documentation, medical coding, billing, and quality measurement.

Overview

EncounterDiagnosis links coded diagnoses to encounters with context about how each diagnosis relates to the visit. Diagnoses are ranked by priority (principal vs secondary), categorized by use (admission, discharge, billing), and timestamped for clinical timeline reconstruction. This supports accurate coding, quality metrics, and clinical decision-making.

Key Concepts

Diagnosis Use

How the diagnosis relates to the encounter:

UseDescriptionWhen Assigned
admissionDiagnosis at time of admissionAt admission
dischargeFinal diagnosis at dischargeAt discharge
billingDiagnosis used for claimsDuring coding
chief-complaintPrimary reason for visitAt registration
comorbidityPre-existing conditionThroughout
complicationProblem arising during careWhen identified
pre-opDiagnosis for planned surgeryPre-operative
post-opDiagnosis after surgeryPost-operative

Diagnosis Ranking

The rank field indicates priority:

  • Rank 1 = Principal diagnosis (primary reason for visit)
  • Rank 2+ = Secondary diagnoses

Proper ranking is critical for:

  • DRG assignment and reimbursement
  • Quality reporting
  • Clinical severity assessment

Coded Conditions

The condition field uses Coding:

  • ICD-10 for billing and statistics
  • SNOMED-CT for clinical detail
  • ICD-11 for newer implementations

Diagnosis Timeline

The onsetDateTime field captures:

  • When diagnosis was identified during encounter
  • Supports clinical progression analysis
  • Distinguishes pre-existing from hospital-acquired

Attribution

The recordedBy field links to the Practitioner who documented the diagnosis.

Use Cases

Admission Diagnosis

When patient is admitted:

  1. Document admission diagnosis with use: "admission"
  2. Set as rank 1 if principal reason
  3. Code using ICD-10
  4. Timestamp when identified
  5. Record documenting provider

Comorbidity Documentation

For pre-existing conditions:

  1. Add each comorbidity with use: "comorbidity"
  2. Rank as secondary (2+)
  3. Include conditions affecting care
  4. Important for severity adjustment

Complication Recording

When problem arises during care:

  1. Create diagnosis with use: "complication"
  2. Set onsetDateTime when identified
  3. Distinguish from admission conditions
  4. Document in clinical notes

Discharge Coding

At discharge:

  1. Finalize diagnoses with use: "discharge"
  2. Confirm principal diagnosis (rank 1)
  3. Sequence secondary diagnoses
  4. Ensure specificity for billing

Quality Reporting

For quality measures:

  1. Query diagnoses by ICD-10 code
  2. Filter by encounter type and timeframe
  3. Calculate measure numerator/denominator
  4. Track hospital-acquired conditions

Related Entities

EntityRelationshipDescription
EncounterBelongs toParent encounter
CodingContainsCoded diagnosis (ICD-10, SNOMED-CT)
PractitionerReferencesProvider who recorded the diagnosis

Enums

use

ValueDescription
admissionDiagnosis identified at time of admission
dischargeFinal diagnosis documented at discharge
billingDiagnosis used for insurance claims and reimbursement
chief-complaintPrimary symptom or concern prompting the visit
comorbidityPre-existing condition that affects care
complicationProblem that arose during the encounter
pre-opDiagnosis documented before surgical procedure
post-opDiagnosis documented after surgical procedure
7 properties
Schema

Properties

PropertyTypeModeDescriptionRequired
encounterEncounter
stored

Reference to the healthcare encounter during which this diagnosis was identified, confirmed, or became clinically relevant. Links the diagnosis to the specific clinical context and timeframe.

Example: "encounter-12345"

Required
conditionCoding
stored

The coded diagnosis using standard medical classification systems such as ICD-10, ICD-11, SNOMED CT, or other recognized coding standards. Represents the clinical condition identified during the encounter.

Example: {"system":"http://hl7.org/fhir/sid/icd-10","code":"E11.9","display":"Type 2 diabetes mellitus without complications"}

Required
usestring
stored

Categorizes how the diagnosis is being used within the context of the encounter, distinguishing between clinical, billing, and documentation purposes. Determines the role and application of the diagnosis in workflow and reporting.

Values: admission, discharge, billing, chief-complaint, comorbidity, complication, pre-op, post-op

Example: "discharge"

Optional
ranknumber
stored

Priority ranking of the diagnosis within the encounter context, where 1 represents the principal or primary diagnosis. Lower numbers indicate higher priority, supporting proper sequencing for billing, quality reporting, and clinical documentation.

Example: 1

Optional
onsetDateTimeDateTime
stored

The date and time when the diagnosis was first identified, documented, or became clinically relevant during the encounter. Supports timeline reconstruction and clinical progression analysis.

Example: "2024-03-15T10:30:00Z"

Optional
recordedByPractitioner
stored

Reference to the healthcare practitioner who documented or recorded this diagnosis during the encounter. Supports accountability and clinical workflow tracking.

Example: "practitioner-789"

Optional
notestring
stored

Additional clinical narrative or context about the diagnosis specific to this encounter, including clinical reasoning, severity observations, or documentation notes that support the diagnosis.

Example: "Patient presented with elevated HbA1c of 8.2%, diagnosis confirmed during annual physical"

Optional

Examples

Example 1

{
  "@type": "EncounterDiagnosis",
  "encounter": "encounter-12345",
  "condition": {
    "system": "http://hl7.org/fhir/sid/icd-10",
    "code": "J18.9",
    "display": "Pneumonia, unspecified organism"
  },
  "use": "admission",
  "rank": 1,
  "onsetDateTime": "2024-03-15T10:30:00Z",
  "recordedBy": "practitioner-101",
  "note": "Principal diagnosis - Community-acquired pneumonia confirmed by chest X-ray showing right lower lobe infiltrate"
}

Example 2

{
  "@type": "EncounterDiagnosis",
  "encounter": "encounter-12345",
  "condition": {
    "system": "http://hl7.org/fhir/sid/icd-10",
    "code": "I10",
    "display": "Essential (primary) hypertension"
  },
  "use": "comorbidity",
  "rank": 2,
  "onsetDateTime": "2024-03-15T10:30:00Z",
  "recordedBy": "practitioner-101",
  "note": "Pre-existing condition, currently managed with lisinopril 10mg daily"
}

Example 3

{
  "@type": "EncounterDiagnosis",
  "encounter": "encounter-12345",
  "condition": {
    "system": "http://hl7.org/fhir/sid/icd-10",
    "code": "E87.6",
    "display": "Hypokalemia"
  },
  "use": "complication",
  "rank": 3,
  "onsetDateTime": "2024-03-17T14:45:00Z",
  "recordedBy": "practitioner-102",
  "note": "Hospital-acquired complication - Developed on day 3 of hospitalization, likely related to diuretic therapy. Potassium level 2.9 mEq/L"
}