Entity: Appointment

Class Diagram

Appointment

Display

Appointments appear in the Diary > Calendar page of the patient's record.

Please see the manual for more information.

Solutions

PKB solutions related to this data type:

Mappings

 

HL7 API

FHIR API

(Customer boxes support full CRUD)

Web

Custom REST API

 

 

Facade (STU3)

Aggregated (R4)

This is a summary. See the web spec for full details.

 

Summary of interactions

Create

S12/S13/S14/S15/S26
A05/A14

 

 

Appointments

 

Read

 

/Appointment

/Appointment

Appointments

 

Update

S12/S13/S14/S15/S26
A05/A14/A27/A38

 

 

Appointments

 

Delete

 

 

 

Appointments

 

Entity: Appointment - Extends: Data Point

Common ID String

An additional ID used only by appointments entities.

 

 

common-identifier

Not shown.

 

Type Coding

The type of appointment.

SCH-8
ZSC-8

 

serviceType

Type.Code is shown on the appointment details page.

Other elements are not shown.

 

Start Timestamp Timestamp

When the appointment starts.

SCH-11.4
EVN-3.1 (ADT)
PV1-44.1 (ADT)
PV2-8.1 (ADT)

start

start

Shown.

 

End Timestamp Timestamp

When the appointment ends.

SCH-11.5

end

end

Shown.

 

Subject String

A brief reason for the appointment.

SCH-7.2
PV1-2.1 (ADT)

reason

appointmentType

Shown.

 

Description String

A longer explanation of the appointment.

NTE-3.1 (SIU)

comment

comment

Shown.

 

Location String

Where the appointment is to be held.

PV1-3.9 (SIU)
PV1-3.9 (ADT)

participant

participant

Shown.

 

Status Enum

  • ACTIVE

  • CANCELLED

  • DNA

SIU

status

status

If the Status is not ACTIVE then a message in red will be displayed.

 

External Management URL String

A deep link URL to an external appointment interface, where this appointment can be managed.

SIU

 

 

If an External Management URL is present than a “Manage” button will be shown to allow the user to launch the URL.

 

Entity: Appointment Participant

User Public ID Ref : [[User.Public ID]]

The PKB user who is participating in the appointment.

When appointments are created via the HL7 API, the patient will be added as the only Appointment Participant.

Use the AIP segment to add External Appointment Participants; the names of these attendees will be added to the Appointment without any link to a PKB User.

participant

participant

Shown.

 

Status Enum

  • ACCEPTED

The status is always Accepted.

participant

participant

Not explicitly shown because always Accepted.

 

Entity: External Appointment Participant

Name String

The name of the participant (optionally including their role).

AIP-3
AIP-4

participant

participant

Shown.