Glossary

FHIR resources

Appointment: The scheduling anchor for a visit. Booked through POST /v1/appointments; carries the visit modality and links to the care plan.

CarePlan: An instance of a governed protocol for one patient. draft when proposed, active once its first task is released.

CareTeam: A queue. A practitioner Task is assigned to a team first, then claimed by an eligible member.

Encounter: A materialized visit, created lazily when a scheduled Appointment is picked up, not up front.

EpisodeOfCare: The umbrella that spans a patient's whole journey for one entry; the single join key tying intake, appointments, tasks, and care plan together.

HealthcareService: A public catalog offering. Tagged public so patients can read it; links to the protocol or intake it fronts.

Observation: A stored measurement (a vital sign, a lab result). Written by the platform when a capture task completes, never assembled by the client.

ObservationDefinition: The template for one measurement (its code and valid units). The capture writer validates readings against it.

PlanDefinition: A governed template, discriminated by type into an assessment, a clinical protocol, or a program.

QuestionnaireResponse: A patient's completed form. Version-pinned to the Questionnaire it answered.

RequestGroup: The order envelope. Its children (MedicationRequest, ServiceRequest) are intent=proposal until placed, then intent=order.

Task: A unit of work. Patient-facing tasks are tagged patient; the rest are clinician workflow.

Palamond concepts

Assessment: The standalone entry ("what brings you in"): one-time data gathering with no treatment and no future scheduling. A patient never picks a drug or program at the door.

Clinical spine: The governed decision path an episode follows: intake, provider review and condition assignment, eligibility, selection, informed consent, active protocol.

Compartment: The platform account (meta.accounts, _compartment=Organization/<id>) that scopes a resource to its tenant. Data integrity, not UX.

ConditionTemplate: A versioned catalog unit carrying a diagnosis code, the data required to assign it, and which protocols it gates.

Consent bundle: A proposal composed against pinned versions (protocol, treatment option, condition) that the patient accepts, declines, or counters.

Lazy encounter: The rule that an Encounter is created on pickup (a claim or a patient starting work), so the spine is Appointment plus Task, not pre-created encounters.

Modality: Whether a visit is sync (a live call on the calendar) or async (store-and-forward work the patient does on their own time).

Platform automation: Palamond's internal machinery that produces and advances the record (materializing observations, issuing tasks, syncing statuses). Internal only; apps reach it exclusively through the workflow endpoints.

Program: An optional longitudinal wrapper around one or more protocols plus non-clinical services. Never a clinical gate and never the entry.

Protocol: The universal clinical primitive a condition gates: treatment options plus monitoring that may recur.

Reschedule: Cancel plus rebook. The original Appointment is cancelled with reason rescheduled and a fresh booked one is created and linked.

Tenant: An Organization. Palamond is multi-tenant inside one project; access is scoped per tenant by AccessPolicy parameter.

Treatment option: One of the small, governed set of choices a protocol enumerates; the guideline-preferred one is a label, never a preselection.

Workflow endpoint: A named /v1 action (POST /v1/appointments, POST /v1/tasks/{id}/complete) that performs one workflow atomically. The only way anything beyond the patient's own writes changes the record. See Endpoints.

Worklist: The clinician queue of claimable tasks. A task sits on a CareTeam queue until an eligible member claims it as owner.