Laboratory Panels &Tests Discussions

(a.k.a. Observation Groups verses Atomic Observations)

Option 6 – Compound & Indivis. Statements

• Specialise Entry into 2 new reference model classes:– Compound Entry

• Used for panels, and may contain data elements, compound statements or atomic statements; Contains shared context.

– Indivisible Entry• Used for individual tests, and represent indivisible unit of

information about the patient; All context is self-contained or derivable.

• Pros– Consistent query paths– Identifies indivisible units of information– Allows arbitrary levels of nesting– Allows context derivation rules to be applied

• Cons / Implications– Requires reference model to be changed– Requires the implementation to ensure atomic statements are

complete, and independently queryable

Option 6 – Compound & Indivis. Statements

INDIVISIBLE ENTRY Hematocrit Result

Information Subj:** 7549ELEMENT:

Date**: 27th June 2013ELEMENT:

Test Name: |Hematocrit|ELEMENT:

Result Value: 42%ELEMENT:

Interpretation: |Normal|ELEMENT:

COMPOUND ENTRY Complete Blood Count

Information Subjct: 7549ELEMENT:

Date: 27th June 2013ELEMENT:

INDIVISIBLE ENTRY Hemoglobin Result

Information Subj**: 7549ELEMENT:

Date**: 27th June 2013ELEMENT:

Test Name:|Hemoglobin|ELEMENT:

Result Value: 14.2 g/dLELEMENT:

Interpretation: |Normal|ELEMENT:**: Derived

Panel Interpretation: …ELEMENT:

I think this example mixes in elements of the physical model and the logical model. I don’t think there is a need to create logical models like this.

The Reference Model should allow both of the next two styles of modeling

Another example of iso-semantic models

INDIVISIBLE ENTRY Hematocrit Result

ELEMENT:

ELEMENT:

Test Name: |Hematocrit|

ELEMENT:

Result Value: 42%

Interpretation: |Normal|

COMPOUND ENTRY Complete Blood Count

Information Subjct: 7549ELEMENT:

Date: 27th June 2013ELEMENT:

INDIVISIBLE ENTRY Hemoglobin Result

ELEMENT:

ELEMENT:

Test Name:|Hemoglobin|

ELEMENT:

Result Value: 14.2 g/dL

Interpretation: |Normal|

Panel Interpretation: …ELEMENT:

Another example of iso-semantic models

INDIVISIBLE ENTRY Patient ABO&Rh Type

Information Subj: 7549Modifier:

Date: 27th June 2013ELEMENT:

Test Name: [ABO&Rh]ELEMENT:

Result Value: A NegELEMENT:

Interpretation: |Normal|ELEMENT:

COMPOUND ENTRY Transfusion Reaction

INDIVISIBLE ENTRY Unit ABO&Rh Type

Information Subj: Unit 1Modifier:

Date: 27th June 2013ELEMENT:

Test Name:[ABO&Rh]ELEMENT:

Result Value: A PosELEMENT:

Interpretation: |Normal|ELEMENT:

Panel Interpretation: …ELEMENT:

Modeling Guideline

• If the contextual element applies to everything in the panel, place the element at the panel level

• If the contextual element applies to only some items in the panel, place the contextual element in each member of the panel to which it applies

Proposed RM for Compound and Indivisible Entries