R2.1. Plans

The table below show the intended use of the plan statement to represent intended or planned actions.

PlanStatement (PlanStatement)

A Plan statement represents an intention or planned action such as a recall for a particular intervention.

[1..1] classCode (CS){ Fixed="OBS " }

Indicates that the plan is for an observation or action.

[1..1] moodCode (CS){ Fixed="INT " }

Indicates that this is an intention to carry out a planned action

[1..1] id (II)

An instance identifier of this statement represented as using the Identifier Global flavour of the II data type.

[1..1] code (CD) {CWE:EhrPlanCode}

A code specifying a the nature of the plan.

  • The code is taken from a clinical coding scheme approved for use in the realms in which the message is used.
  • This will be a code or concept identifier from the Read Codes, CTV3 and in future SNOMED CT).

[0..1] text (ED)

The description of an act as a piece of free text or multimedia data.

[1..1] statusCode (CS) {CNE:EhrActState}

Indicates whether the component is complete (current), obsolete (replaced) or nullified (deleted).

[0..1] effectiveTime (TS)

This is the time when the action is planned to happen.

[1..1] availabilityTime (TS)

System date and time when this plan was recorded on the originating system.

[0..1] participant (EhrStatement/participant)

[1..1] typeCode (CS) {CNE:PRF}

[0..1] time (IVL<TS>)

The time at which the plan was made.

[1..1] AgentRef (AgentRef)

[1..1] classCode (CS){ Fixed="AGNT " }

[1..1] id (II)