Problem Record List

ProblemRecordList is a list of a patient's problems and conditions, whose status is never blank. It renders as a <ul>. Every word is the consumer's.

Status: experimental — new, implemented and unit-tested in every headless library; not yet exercised in a composed flow.

Example

  • Type 2 diabetes Active Confirmed Moderate
  • No known problems
Show demo markup
<ul class="problem-record-list" data-status="known" aria-label="Problems"><li class="problem-record-list-item" data-clinical-status="active" data-verification-status="confirmed"><span class="problem-record-list-item-condition">Type 2 diabetes</span> <span class="problem-record-list-item-clinical-status">Active</span> <span class="problem-record-list-item-verification-status">Confirmed</span> <span class="problem-record-list-item-severity">Moderate</span> <time class="problem-record-list-item-onset" datetime="2019-06-01">Since June 2019</time> <time class="problem-record-list-item-abatement" datetime="2024-01-15">Resolved 15 Jan 2024</time></li></ul><ul class="problem-record-list" data-status="none-known" aria-label="No known problems"><li class="problem-record-list-status">No known problems</li></ul>
Usage example
<ProblemRecordList
  status="known"
  statusLabel="Problems"
>
  <ProblemRecordListItem
    condition="Type 2 diabetes"
    clinicalStatus="active"
    clinicalStatusLabel="Active"
    verificationStatus="confirmed"
    verificationStatusLabel="Confirmed"
    severityLabel="Moderate"
    onset="2019-06-01"
    onsetLabel="Since June 2019"
    abatement="2024-01-15"
    abatementLabel="Resolved 15 Jan 2024"
  />
</ProblemRecordList>

<ProblemRecordList
  status="none-known"
  statusLabel="No known problems"
/>
Show Svelte source
// In your Svelte component:
import ProblemRecordList from "lily-design-system-svelte-headless/components/ProblemRecordList/ProblemRecordList.svelte";

<ProblemRecordList>
  <!-- content -->
</ProblemRecordList>

Usage

<ProblemRecordList
  status="known"
  statusLabel="Problems"
>
  <ProblemRecordListItem
    condition="Type 2 diabetes"
    clinicalStatus="active"
    clinicalStatusLabel="Active"
    verificationStatus="confirmed"
    verificationStatusLabel="Confirmed"
    severityLabel="Moderate"
    onset="2019-06-01"
    onsetLabel="Since June 2019"
    abatement="2024-01-15"
    abatementLabel="Resolved 15 Jan 2024"
  />
</ProblemRecordList>

<ProblemRecordList
  status="none-known"
  statusLabel="No known problems"
/>

Props

  • status: "known" | "none-known" | "not-recorded" | "unavailable" | "omitted" | "not-applicable" (required) — rendered as data-status
  • statusLabel: string (required) — the status in words; names the list, and is its one item unless status is known
  • label: string (optional) — the accessible name, when it should differ from statusLabel
  • children: slot (optional) — problem-record-list-item items
  • ...restProps: any — additional HTML attributes spread onto the root

Keyboard Interactions

None. This is not an interactive component.

ARIA

  • A <ul> named by aria-label; the status is text, never an icon or a colour alone

When to Use

  • Use for a patient's problems, wherever a missing list could be misread.
  • Use with none-known, not-recorded, unavailable or omitted when there is nothing to list: each is a different fact.

When Not to Use

  • Do not leave the list empty for "none": set status instead.
  • Do not use for a list that is not part of a patient's record — use list or summary-list.
  • For another part of the record, use its own record list, or record-list.

Headless

This headless component ships zero CSS and decides nothing visual. The consumer provides all styling targeting the .problem-record-list class hook, and every word.

Styles

.problem-record-list, .problem-record-list-status and [data-status].

Testing

  • Each of the five statuses renders its consumer text; known renders only its items
  • label overrides the accessible name
  • A missing status raises a development warning

Advice

  • Take every word from your own translation, including the status words; Lily ships none.
  • Map FHIR codes to these values in your code; Lily does not read FHIR resources.
  • Format dates with Intl.DateTimeFormat, with the month as text so they cannot be read two ways.

Implementation Notes

  • Renders <ul class="problem-record-list"> named by aria-label (label, else statusLabel)
  • status is required and renders as data-status: known, none-known, not-recorded, unavailable, omitted, not-applicable
  • For any status but known, statusLabel is the list's one item, li.problem-record-list-status, so the list is never blank
  • Holds problem-record-list-item items when the status is known
  • A missing status or statusLabel raises a development warning (Svelte, React, Vue, Angular)

Related components

  • problem-record-list-item — one problem or condition in a problem record list, with its clinical and verification status, severity, onset and resolution
  • record-list and the other record lists — the same status contract for each part of a record

References


Lily™ and Lily Design System™ are trademarks.

Canonical contract

Generated from this component's canonical metadata — the machine-checked source the implementations are held to.

Metadata

  • Component: problem-record-list
  • PascalCase: ProblemRecordList
  • Description: a list of a patient's problems and conditions, whose status is never blank
  • Status: experimental — new, implemented and unit-tested in every headless library; not yet exercised in a composed flow
  • HTML tag: <ul>
  • CSS class: .problem-record-list
  • Interactive: no

ARIA

  • A <ul> named by aria-label; the status is text, never an icon or a colour alone

Keyboard

  • Not interactive

Props

  • status: "known" | "none-known" | "not-recorded" | "unavailable" | "omitted" | "not-applicable" (required) — rendered as data-status
  • statusLabel: string (required) — the status in words; names the list, and is its one item unless status is known
  • label: string (optional) — the accessible name, when it should differ from statusLabel
  • children: slot (optional) — problem-record-list-item items
  • ...restProps: any — additional HTML attributes spread onto the root

Markdown

This page as Markdown, for people and AI tools: problem-record-list.md