Skip to main content
Version: v0.0.3

Interface: BuildCcdaPlannedAct

A planned Act / Encounter / Procedure (…4.39 / …4.40 / …4.41). mood accepts the full Planned moodCode value set including the appointment moods (APT/ARQ), which are valid on these element domains. Default code system: SNOMED CT for an act/procedure, CPT for an encounter.

Example​

import type { BuildCcdaPlannedAct } from "@cosyte/ccda";
const visit: BuildCcdaPlannedAct = {
  kind: "encounter",
  code: { code: "99213", displayName: "Office outpatient visit 15 minutes" },
  mood: "APT",
};

Extends​

  • BuildCcdaPlannedItemBase

Properties​

code​

readonly code: BuildCode

The planned act/observation/drug code; default code system varies by kind.

Inherited from​

BuildCcdaPlannedItemBase.code

effectiveTime?​

readonly optional effectiveTime?: string

The planned time as an HL7 date string; emitted only when supplied, never fabricated.

[0..1] is the cardinality on five of the seven templates, not on all of them. Both substanceAdministration variants SHALL carry exactly one: Planned Medication Activity (…4.42, CONF:1098-30468) and Planned Immunization Activity (…4.120). BuildCcdaPlannedImmunization redeclares this field as required, which is why omitting it there is a type error; BuildCcdaPlannedOrder does not, so buildCcda will emit a Planned Medication Activity short that SHALL element if you leave it out. That gap is known and deliberately still open: closing it means making the field required on a published input type, which is a breaking change and a decision of its own rather than a patch.

Inherited from​

BuildCcdaPlannedItemBase.effectiveTime

kind​

readonly kind: "procedure" | "act" | "encounter"

mood?​

readonly optional mood?: PlannedActMood

The planned @moodCode; defaults to "INT". Appointment moods allowed here.