Conceptual division of semantics among measurement observation model parts Model ID: Model to represent entire statement including context (date, setting, patient, etc.) Code: Test or question to measure observable concept. May include method, units. Erythrocytes [#/volume] in Blood Manual count Observable concept Erythrocyte volume

Erythrocyte volume (observable entity) Conceptual division of semantics among measurement observation model parts, with SCT & LOINC Model to represent measurement Test to measure observable concept: 790-6 Erythrocytes [#/volume] in Blood by manual count Observable concept: Erythrocyte volume (observable entity)

Conceptual division of semantics among measurement observation model parts, LOINC mapping Model to represent measurement Code with equivalent observable expression Observable concept Towards Population of all erythrocytes in portion of fluid (body structure) | 703062004 Property type Number concentration (property) (qualifier value) | 118550005 Inheres in Blood (substance) | 87612001 Direct site Blood specimen (specimen) | 119297000 Scale Quantitative (qualifier value) | 30766002 Process duration Single point in time (qualifier value) | 123029007

6/17 Contents Slots ? Semantics of whole model Viz., CIMI archetype name Semantics of observation process Viz., LOINC code Semantics of what the value describes Viz., SNOMED CT Observable Supported by LOINC code with SNOMED CT translation in some circumstances Model name: 1 Root node model binding Maybe not needed Common name for isosemantic models? Code: 2 Rename “Code” model binding Should define “code” itself, if used Value model binding Should define “value” itself, if used 3: New node: “Observation Result” model binding Structured?: corresponds to SCT observable model Observable? Referent? Predicand? ?

6/23 Contents Slots ? Semantics of whole model Viz., CIMI archetype name Semantics of observation process Viz., LOINC code Semantics of what the value describes Viz., SNOMED CT Observable Supported by LOINC code with SNOMED CT translation in some circumstances Model name: 1 Root node model binding Maybe not needed Common name for isosemantic models? Code: 3 Rename “Code” model binding = “Observable entity” Value model binding Should define “value” itself, if used New node: “Observation Result” model binding Structured?: corresponds to SCT observable model Observable? Referent? Predicand? ?