Clinical Resources
Symptoms
Overview
The Symptoms section captures the complaints and clinical findings a patient reports or a clinician observes during an encounter.
Structuring these findings gives downstream systems a clear picture of why the patient presented and what was noted, which supports triage, documentation quality, and clinical decision-making.
Clinical Data in Source Documents
Symptoms are most often documented in the Chief Complaint, History of Present Illness, or Review of Systems sections of a clinical note.
They usually appear as short narrative phrases, for example “substernal chest pain radiating to the left arm” or “shortness of breath on exertion”, and may include qualifiers such as onset, duration, and severity.
JSON Output
During processing, the platform extracts each symptom into a structured JSON entry that records the finding and where it was documented.
Each symptom includes:
- Name: The symptom or complaint.
- Description: Supporting detail such as location, quality, or timing.
- Section Reference: The document section the symptom was found under.
- Page Number: The source page, for traceability.
FHIR Output
Each symptom is mapped to a FHIR Observation resource categorized as a clinical finding, which links the finding to the patient and preserves the reported detail as a note.
Key mappings include:
- Name: Populated into
Observation.code.text. - Category: Set to
examso systems can distinguish reported findings from vital signs and labs. - Description: Captured in
Observation.note. - Patient Link:
Observation.subjectreferences the patient.