Entry

Identifier

Unique identifier for the ISO-13606 Entry.

DisplayName

Label used when selecting the Entry

Hint

Description displayed when the user hovers over the Entry

Alert

Text displayed in a distinctive style with the Entry. Can be used as a dynamic alert by setting Conditions on the Entry.

Extension

The extension to the Identifier. The purpose of the extension is to allow for specialization of identified Entries.

The Entry Identifier is used to define the structure of the health record, but the Extension is used in calculations. This means that the same Entry (same extension) can be defined with different behaviours (specified for Entries with different Identifiers, referring to the same Extension)

Selected from the existing Entry Identifiers.

If no Extension is specified for an Entry then it defaults to be the same as the Identifier

Information

An Entry displayed in the Information pane of the user interface that can contain additional information about the Entry to which it is associated.

The Information Entry is displayed as Read Only but can include calculations. This could be used (for example) to display a different URL to external information, depending on the values of Elements in the associated Entry.

EntryRelationship

Used to define additional information about an

• Encounter - details of the booking

• SubstanceAdministration – details of the medication being prescribed

• Supply – details of the test being ordered.

Subject

The Composition that is the subject of an Act. Only selectable if the Entry has an EntryType of Act.

EntryType

The HL7 CDA entry type. This determines the SectionContext in which the Entry can be selected. If the EntryType is not set, then the Entry cannot be used, since it won't appear in the drop down selection for the Contents of any Section. The EntryType also determines the HL7 CDA element that is generated.

• Observation - used in SectionContext of Composition

• Act - used in SectionContext of Pathway

• Supply - used in SectionContext of Order

• SubstanceAdministration - used in SectionContext of Prescription

• Encounter - used in SectionContext of Booking

CRUD

How the Entry is instantiated when the Composition is loaded

• CRUD - no restriction - Create, Read, Update, Delete

• R - Read only. The contents are displayed but the user cannot interact.

• CR - Create and Read. New Entries can be added to a multiple entry (as determined by its Occurrence) but and existing pre-filled Entries are read-only.

• CRU - Create, Read and Update

• CRD - Create, Read and Delete

• UL - Lookup in directory and then Update. The complete Entry is retrieved from the Directory of Entries for that identity using the key Element specified in the

• L - Lookup in directory (fixed value)

Occurrence

The cardinality of the Entry (one or many)

• Single - one instance of the Entry

• MultipleEntry - multiple instances of the Entry can be created

InitialValue

How the Entry is instantiated when the Composition is loaded

• Empty – all Element values are empty (blank, not set)

• Pre-filled – set with the most recent values in the patient record (for both Single and MultipleEntry)

• DistinctValues – for MultipleEntry, set with the set of distinct Entries ever recorded

• AllValues – for MultipleEntry, set with the set of every Entry ever recorded

• Default – the initial value is calculated from the expression in DefaultValue

• Transient – set with the most recent values in the patient record for initial calculations, then reset to Empty once the Composition is loaded.

Sequence

Determines the layout of Clusters and Elements contained in the Entry.

• Ranked - sequentially, one after the other, laid out vertically

• Unranked - concurrently, in parallel, laid out horizontally

SortOrder

For a Multiple Entry only (Occurrence = MultipleEntry)

• Ascending - entries are sorted in ascending order (using the SortCriteria Element or the first Element in the Entry, if no SortCriteria)

• Descending- entries are sorted in descending order (using the SortCriteria Element or the first Element in the Entry, if no SortCriteria)

SortCriteria

The Element used to sort a MultipleEntry or as the key to look up the value of a directory Entry.

CategorizationCriteria

The Element used to categorize a MultipleEntry. The multiple entries are split into categories – one category for each value of the Element specified as the CategorizationCriteria. This Element must exist as content of the Entry.

Rendition

The way in which the Entry is rendered on screen for user interaction

• Form - regular interaction using form-based controls (default)

• ImageMap - graphical interaction using an image map (which must be loaded through the Administration page)

• Image - displayed as a static image (which must be loaded through the Administration page)

• Denoted - form-based with each Element preceded by a bullet point icon

• Enumerated - form-based with each Element preceded by a number

• Standalone - displayed in a pop-out (not yet supported) and printed on a new page

• Chart - displayed as a chart generated from historic values of each Element

• Highlighted - form-based, emphasized

• Hidden - not displayed to the user, but recorded in the record when the Composition is committed

Scope

For Multiple Entry (Occurrence = MultipleEntry) or Element

• Defined - the user selects from the set of available values, which are not displayed until the user interacts

• Full - all available values are displayed for selection

CohortSearch

• Searchable - is listed for selection in the Cohort Search page

• PrimarySearch - is listed in the primary selection in the Cohort Search page

• NotSearchable - is not available for searching in the Cohort Search page

EvaluationContext

Conditions used to constrain the Compositions in the record from which default values for any Elements in the Entry are calculated when the Composition is loaded.

Pre-conditions

Result of the expression is cast to xs:boolean

These pre-conditions are evaluated once, when the Composition is loaded; any out-of- scope Entry is removed from the Composition before any user interaction begins.

Conditions

The Condition is evaluated continuously as the containing Composition is edited by the user. If the Condition evaluates to true then the entry is in-scope, if the Condition evaluates to false then the Entry is out-of-scope.

Any out-of-scope Entry has its visibility set to false, is hidden from the user, does not get used in other calculations and is removed from the Composition before it is committed to the patient record.

Content

Set of Clusters and Elements contained in the Entry