Skip to documentation
ReferencePatient

Patient

Physical examination

General findings and detailed examination by system.

Format definition

Use findings for symptoms, examination findings, and measurements, with collection, availability, interpretation, and disclosure separated.

Scenario standard · Execution capabilities

Parameters

findings[].id

string

Optional; omitted means unspecified

Stable finding or measurement identity; a repeat collection creates a new finding ID.

findings[].patientId

string

Optional; omitted means unspecified

Patient to whom the finding belongs.

findings[].code

string

Optional; omitted means unspecified

Namespaced concept, such as usim:general-appearance; codes do not imply external terminology certification.

findings[].kind

"symptom" | "finding" | "measurement"

Optional; omitted means unspecified

Separates reported experience, observed findings, and measured values.

findings[].status

"known"

Optional; omitted means unspecified

Known requires a value. Other statuses prohibit a value rather than using zero or an empty string as a sentinel.

findings[].value

number

Optional; omitted means unspecified

Type must match the registered concept. Qualitative findings can be text or explicit booleans.

findings[].unit

string

Optional; omitted means unspecified

Fixed by the concept definition; no inferred conversions.

findings[].collectedAtSeconds

number

Optional; omitted means unspecified

Time of authored assessment or acquisition, possibly before baseline.

findings[].availableAtSeconds

number

Optional; omitted means unspecified

Earliest simulated time for release; disclosure conditions must also be satisfied.

findings[].method

string

Optional; omitted means unspecified

Method, location, or equipment used to obtain the finding.

findings[].disclosure

object

Optional; omitted means unspecified

Select one of the declared Disclosure alternatives; use the fields belonging to that alternative.

Behavior and validation

  • Display standard ROS and examination system codes using authoringProfiles.usim:age-based-normal-findings.systems labels in both authoring and learner views (for example ent is Ears, nose and throat). Preserve custom system labels verbatim; never title-case a code to invent a clinical label.
  • Author-selected normal findings use usim:age-based-normal-findings@1.1.0 in authoringProfiles. Select by age in years: infant [0,1), child [1,12), adolescent [12,18), adult [18,65), older adult [65,infinity); missing or invalid age uses age-neutral text. Materialize selected text as explicit authored findings linked to the system. Preserve existing values, including blanks, unknown and not assessed. Age changes never rewrite saved findings. Omission never implies normal; do not inject templates during import or playback. Selected templates are stored as canonical findings: symptom entries for ROS and finding entries for examination, linked by patientId and system code.
  • Pending results do not expose their future value in learner outputs. Underlying authored values and runtime release status must remain distinct.
  • A numeric concept has one declared unit and value type in the profile. New concepts require definitions under extensions until standardized.

Shared format conventions · All format elements · Download specification