Chart Sections

Chart sections are visual sections in the web app and iFrame methods; they do not apply to the API.

The Patient Chart organizes patient data into sections based on clinical category and record type. Each section represents a specific type of data and provides a consistent way to view, filter, and interact with records.

Section Organization

Chart sections are grouped by clinical category and are accessible through the sidebar. While available sections may vary based on data availability and configuration, they generally fall into the following categories:

• Overview sections: High-level entry points such as Patient Summary and Patient Profile
• Clinical sections: Structured data such as medications, allergies, diagnoses, vital signs, and procedures
• Documents and diagnostics: Unstructured documents, lab results, imaging, and related records
• Messaging and events: Referrals, messages, and admission, discharge, and transfer (ADT) activity where supported

Each section corresponds to a specific data type and displays only the records available for that category.

The Patient Chart also includes read-only Medical History sections for Goals, Health Concerns, Interventions, and Assessments, imported from source documents. For the United States Core Data for Interoperability (USCDI) v3.1 data classes and record-level detail, go to USCDI v3.1 Coverage.

Section Behavior

Chart sections share a consistent interaction model, with behavior varying slightly based on the data type.

• Sections load dynamically when selected
• Each section displays data using either a table or card layout
• Available filters, search options, and actions depend on the section and content type
• Records are scoped to the current section and do not affect other sections

Data Presentation

• Table-based sections: Present structured data with sortable columns and searchable fields
• Card-based sections: Present documents, messages, or events with metadata and preview options

Within each section:

• Records are displayed with relevant attributes such as dates, types, and source information
• Actions such as preview, download, or navigation to related records are available where supported

Section Availability

The presence and content of each section depend on the data available in the processed dataset.

• Sections may be empty if no corresponding records are available
• Available sections and records reflect prior workflows and system configuration