• Content
• Detailed Descriptions
• Examples
• Example operations
• XML
• JSON

StructureDefinition: ehealth-appointment

Introduction

An Appointment is a booking of a healthcare event among ehealth patients, practitioners, related persons, and locations. This may be either a virtual or physical meeting. Even though a meeting may span a number of participants, only one physical Appointment resource must be created. Participant status (approved, declined etc.) is handled using the AppointmentResponse resource.

Scope and Usage

In the eHealth Infrastructure the Appointment resource is used in conjunction with the following resources:

• Patient
  • If the appointment contains a participant of type Patient
• Practitioner
  • If the appointment contains a participant of type Practitioner
• RelatedPerson
  • If the appointment contains a participant of type RelatedPerson
• Location
  • If the appointment contains a participant of type Location

Formal Views of Profile Content

The official URL for this profile is:

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-appointment

This profile models an ehealth appointment. It is only necessary to create one appointment even though it spans more than one participant. Allowed appointment participants are patients, practitioners, relatedpersons, and locations

This profile builds on Appointment.

This profile was published on Fri Jun 07 11:10:06 UTC 2019 as a draft by ehealth.sundhed.dk.

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

 

Terminology Bindings

Path	Name	Conformance	ValueSet
Appointment.language	Common Languages	extensible	Common Languages
Appointment.status	AppointmentStatus	required	AppointmentStatus
Appointment.serviceCategory	ServiceCategory	example	ServiceCategory
Appointment.serviceType	ServiceType	example	ServiceType
Appointment.specialty	Practice Setting Code Value Set	preferred	Practice Setting Code Value Set
Appointment.appointmentType	AppointmentTypeCodes	extensible	AppointmentTypeCodes
Appointment.reason	Encounter Reason Codes	preferred	Encounter Reason Codes
Appointment.participant.type	ParticipantType	extensible	ParticipantType
Appointment.participant.required	ParticipantRequired	required	ParticipantRequired
Appointment.participant.status	ParticipationStatus	required	ParticipationStatus

Constraints

Id	Path	Details	Requirements
dom-2	Appointment	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	Appointment	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	Appointment	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3	Appointment	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty()
app-3	Appointment	Only proposed or cancelled appointments can be missing start/end dates : (start.exists() and end.exists()) or (status in ('proposed' | 'cancelled'))
app-2	Appointment	Either start and end are specified, or neither : start.empty() xor end.exists()
ele-1	Appointment.participant	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
app-1	Appointment.participant	Either the type or actor on the participant SHALL be specified : type.exists() or actor.exists()

.