Exam Finding List
“In the context of an imaging exam, a list of the findings declared as present/absent on that exam.”1 It is the second level of the OIDM data structure hierarchy, grouping every observation from one exam under that exam’s identity.
The structure carries a diagnosticReportId, patientInfo, an examInfo block holding the study identifier, date and time, LOINC code and description, and a findings array. Each finding carries an observationId, a findingCode in OIFM_XXXX_###### form with its description, an attributes array of attribute code, value code, and display text, an optional anatomicLocation of locationId and locationDisplay, and an optional verbatim reportText.23
Two properties are stated as requirements rather than conveniences. The exam header must be keyed by a curated list of LOINC codes. And “the same finding type may be declared present multiple times; each time is a separate entry.”1 The deck adds that an Exam Finding List can be “sourced from dictation, AI tools, interpretation-time interfaces,” which is why each observation should carry a provenance marker.4
Synonyms and near-synonyms
- EFL is the abbreviation used throughout the source repository.
- FHIR DiagnosticReport is its documented interchange encoding.
- Report is the narrative document; the Exam Finding List is the structured result derived from or produced alongside it.
- Imaging Problem List is the patient-level aggregation of many of these.
Identifier form
None of its own beyond diagnosticReportId, a UUID string in the sample data.
Where it is used
Hierarchy, Exam Finding List, and Exam Finding List example.
Conflicts
The README abbreviates Imaging Problem List as “IFL” in one heading, a typographical error rather than a second name. The anatomicLocation field exists only on the development branch, so data produced against the stable specification will not carry it. No JSON Schema is published; the schema URL referenced in the sample files does not resolve.